Sigma Runtime Standard - Public Specification Notice
This document is part of the Sigma Runtime Standard (SRS) public specification layer.
Specification License: CC BY 4.0.
Implementation Safe Harbor: independent implementation permitted under public SRS/SRIP terms.
Machine-readable artifacts: Apache License 2.0 where explicitly marked.
Marks / Certification: governed by Sigma Marks and Certification Policy.
Proprietary Runtime Assets: not licensed by this SRIP.Independent implementations of public SRS/SRIP normative requirements are welcome under the public specification terms.
Product assets, protected Sigma marks, official certification, compatibility badges, CC BY-NC commercial use, and patent commitments use the relevant policy or explicit covenant. Independent implementation, attribution, or citation does not imply certification, endorsement, partnership, official compatibility, or permission to use Sigma marks as product identity.
Semantic Units of Governed Runtime-Environment Contact
| Field | Value |
|---|---|
| SRIP | SRIP-25 |
| Title | Interaction Event Model (IEM) |
| Version | Public Draft v0.2 |
| Status | Public Draft |
| Date | 2026-06-27 |
| Authors / Contributors | Sigma Stratum Research Group (SSRG) |
| Owning Layer | Integration Boundary / Event Semantics / Runtime Control / Governance |
| Parent Specs | SRIP-05, SRIP-22, SRIP-24 |
| Related Specs | SRIP-01, SRIP-04, SRIP-13, SRIP-14, SRIP-17, SRIP-19, SRIP-20, SRIP-21 |
| Specification License | CC BY 4.0 |
| Implementation Safe Harbor | Independent implementation permitted under public SRS/SRIP terms |
| Machine-Readable Artifacts | Apache 2.0 where explicitly marked |
| Marks / Certification | Governed by Sigma Marks and Certification Policy |
| Proprietary Runtime Assets | Not licensed by this SRIP |
| Independent Implementation | Permitted under the public specification terms |
| Commercial Runtime Boundary | Relevant policy or explicit covenant for protected Sigma marks, official certification, managed deployment, white-label, resale, CC BY-NC commercial use, and patent commitments |
| Information Class | Open |
| Change Class | Mixed SRS+SRD |
| Normative Status | Defines a public draft semantic model for interaction events crossing the Environment Interface Layer boundary. It does not define an event bus, database schema, serialization format, provider API, transport protocol, workflow engine, replay system, or production implementation. |
| Conformance Level | Public Draft / No runtime conformance claim |
| SRD Synchronization Action | Initial SRD synchronization completed in /srd/environment-interaction-and-events; broader synchronization for EIL, tool/action boundaries, memory/retrieval, governance, event/evidence, replay, and runtime architecture explanation remains deferred follow-up. |
| Release Alignment Status | Public draft architecture proposal; no runtime enablement, production behavior, schema serialization, event bus, replay system, or conformance claim is made by this document alone. |
Independent implementations of the public normative requirements in this SRIP are welcome under the applicable public specification terms.
No Sigma commercial runtime license is needed solely because an independent implementation follows these public normative requirements.
Product assets, protected Sigma marks, official certification, compatibility badges, CC BY-NC commercial use, and patent commitments use the relevant policy or explicit covenant. Independent implementation, attribution, or citation does not imply certification, endorsement, partnership, official compatibility, or permission to use Sigma marks as product identity.
SRIP-25 defines the Interaction Event Model (IEM): a public draft semantic model for representing contact between a Sigma runtime trajectory and an external environment at the Environment Interface Layer boundary.
SRIP-24 defines where governed runtime-environment contact occurs.
SRIP-25 defines the smallest semantic unit of that contact:
Interaction Event
An interaction event is a bounded, attributable, evidence-bearing interaction between a runtime trajectory and an external environment. It is independent of transport, provider, tool framework, SDK, or orchestration system.
This SRIP is a public draft architecture contract. It does not claim that IEM is implemented in any current Sigma Runtime release.
Many agent frameworks model external interaction primarily as:
Sigma Runtime uses a different architectural abstraction.
The relevant question is not only:
Which tool was called?
The deeper runtime-governance question is:
Which interaction event occurred?
IEM exists to make external contact technology-independent and governance-visible. Tools, APIs, transports, filesystems, databases, humans, providers, sensors, and agents are implementation surfaces. The public semantic unit is the interaction event.
| Field | Disposition |
|---|---|
| Source material | Open public-draft candidate derived from sanitized architectural formation material |
| Affected SRS surface | SRIP registry / EIL / interoperability / governance / memory-retrieval / event semantics |
| Affected SRD surface | Runtime architecture, EIL, tool/action, memory/retrieval, governance, event/evidence, replay, and long-horizon interaction explanations |
| SRD synchronization | Deferred follow-up |
| Normative impact | Public draft semantic model for observation events, effect events, interaction-event fields, invariants, and technology-independent runtime-environment contact |
| Runtime implementation impact | None by this document alone |
| Release alignment | Draft; initial SRD explanation added; no runtime enablement, production behavior, schema serialization, event bus, replay system, or conformance claim |
This document abstracts the formation proposal into public specification language. It does not expose proprietary runtime internals, hidden prompts, deployment topology, private telemetry, private evaluation corpora, implementation-specific control overlays, internal task labels, production operations, or private event schemas.
IEM applies whenever material crosses the Environment Interface Layer boundary as either:
IEM does not define:
Those belong to future implementation-specific or future specification work.
An Interaction Event is the smallest governed unit of contact between Sigma Runtime and external reality, carrying sufficient semantic, authority, provenance, and evidence information to reconstruct, audit, replay, or contest that interaction independently of implementation technology.
Public-safe short form:
Interaction events represent contact.
They do not produce cognition.
They do not authorize themselves.
SRIP-24 EIL governs whether and how runtime-environment contact may occur.
SRIP-25 IEM governs what that contact means once represented as a public semantic unit.
EIL = boundary and governance of contact
IEM = semantic unit crossing the boundary
IEM is therefore a refinement of EIL, not a replacement for EIL.
IEM defines two primary categories.
An observation event represents environment-to-runtime contact.
Examples:
Observation events may influence runtime interpretation.
Observation events must not directly authorize behavior, memory persistence, external action, or truth claims.
An effect event represents runtime-to-environment contact.
Examples:
Effect events may alter external reality.
Effect events require stronger governance than observation events and must not authorize themselves.
A public IEM-compatible event should preserve:
| Field | Meaning |
|---|---|
| Direction | Observation or effect direction. |
| Source | Origin of the contact. |
| Target | Entity, system, channel, store, participant, or surface affected or addressed. |
| Scope | Boundary in which the event is valid. |
| Time | Temporal placement of the event. |
| Authority | Permission, legitimacy, or authorization state. |
| Effect Class | Whether the event is observation-only, effectful, mutating, notifying, costly, or otherwise externally consequential. |
| Evidence Status | Whether the event is traceable, replayable, witnessed, redacted, missing, or uncertain. |
| Provenance | Source chain or lineage supporting the event. |
| Trace Identifier | Identifier sufficient to connect evidence without exposing private payloads. |
Optional or future-extension fields may include:
A conformant IEM implementation must preserve these invariants:
Behavior creates stabilized trajectories and interaction candidates.
Behavior does not directly create external effects.
Illustrative flow:
Behavior
-> Interaction Candidate
-> EIL Review
-> Interaction Event
-> External Environment
Memory may consume observation events and may be updated by authorized effect events according to memory-layer policy.
IEM does not allow memory to bypass provenance, temporal validity, retrieval policy, or persistence authorization.
Governance determines whether an effect event is authorized, contestable, auditable, reversible, blocked, or escalated.
IEM records the semantic event surface. It does not decide legitimacy by itself.
| Dependency | Type | Notes |
|---|---|---|
| SRIP-24 EIL | Parent | Defines the boundary that interaction events cross. |
| SRIP-05 Interoperability Interface | Parent | Provides public interface context for external contact. |
| SRIP-22 GRC | Parent | Governs authority, evidence continuity, contestability, and effect authorization. |
| SRIP-14 RMI | Related | Required when events involve retrieval, memory reads/writes, provenance, or persistence. |
| SRIP-21 EIB | Related | Required when events involve external participants, agents, sources, or referents. |
| SRIP-20 ANS | Related | Required when events apply autonomy or boundary pressure. |
| SRIP-19 RCB | Related | Required when events carry contested evidence or unresolved contradiction. |
| SRIP-17 MAE | Related | Required for multi-agent exchange events. |
| SRIP-13 RIS | Related | Required when events affect relational or identity boundaries. |
| SRIP-04 Memory Layer | Related | Provides memory architecture context. |
| SRIP-01 Runtime Loop | Related | Provides runtime continuation context. |
Backwards compatibility: this public draft does not modify existing SRIPs. It refines SRIP-24 by defining the public semantic unit crossing the EIL boundary.
IEM is safe only if it remains a semantic model rather than a self-authorizing action mechanism.
Required safety posture:
The central safety invariant is:
Contact must be representable.
Representation is not authorization.
Initial SRD synchronization is provided by
Environment Interaction and Events.
Broader SRD synchronization is still required before any release or public
communication claims full alignment with SRIP-25.
Likely affected SRD areas:
Until synchronization is complete, public alignment must be stated as:
Public draft only; no runtime enablement, production behavior, schema
serialization, event bus, replay system, or conformance claim.
This public draft does not define implementation APIs, SDKs, schemas, transports, event buses, provider integrations, replay engines, rollback systems, or production behavior.
Future implementation-readiness work should define:
Any implementation should default to evidence-only or observation-only operation until separate governance enables stronger effects.
SRIP-25 is additive.
This draft does not deprecate or supersede existing SRIPs. It refines SRIP-24 EIL by defining a public semantic model for interaction events.
| Version | Date | Author | Description |
|---|---|---|---|
| 0.1 | 2026-06-27 | SSRG | Formation draft. |
| 0.2 | 2026-06-27 | SSRG | Public draft normalization with boundary, dependency, non-goal, conformance, and SRD synchronization fields. |