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.
Sigma Runtime Improvement Proposal
| Field | Value |
|---|---|
| SRIP | SRIP-01 |
| Title | Canonical Runtime Loop |
| Version | Foundational Draft |
| Status | Draft |
| Date | 2026-04-17 |
| Authors / Contributors | E. Tsaliev |
| Owning Layer | Architectural / Runtime Semantics |
| Parent Specs | SRIP-00 |
| Related Specs | SRIP-02, SRIP-03, SRIP-04, SRIP-06, SRIP-08 |
| 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 | SRS-only |
| Normative Status | Defines the public canonical runtime loop and ordered execution phases without mandating a provider-specific backend implementation. |
| Conformance Level | Public Draft / Foundational |
| SRD Synchronization Action | Deferred review |
| Release Alignment Status | Foundational draft; no production conformance claim is made by this document alone. |
Public Note
This foundational document uses version-light runtime-boundary language.
EarlierSL0–SL6orSL0–SL7labels remain part of lineage history, but are not required as the active public vocabulary for the canonical runtime loop.
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 those 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-01 defines the canonical runtime loop (CRL) that governs all Sigma Runtime–compliant systems.
It specifies the ordered execution phases that maintain recursive coherence, identity persistence, and bounded correction across the runtime boundary.
Without a structured loop, LLM systems exhibit:
The canonical loop formalizes a deterministic, bounded process for recursive cognition.
The cyclical execution process through which cognitive state is ingested, interpreted, stabilized, and emitted.
A discrete operational window corresponding to one pass through the canonical runtime loop.
The re-integration of output into the cognitive field for the next iteration.
| Step | Layer Scope | Function |
|---|---|---|
| 1. State Ingestion | Runtime boundary | Acquire user input and current field state. |
| 2. Interpretation Pass | Interpretation layer | Parse input, extract semantics, generate symbolic projection (Πsym). |
| 3. Stabilization Pass | Control and stabilization layer | Evaluate drift, adjust attractors, enforce coherence thresholds. |
| 4. Memory Integration | Memory layer | Merge new data into semantic and symbolic memory layers. |
| 5. Attractor Alignment | Attractor alignment layer | Reinforce or dissolve attractors per stability metrics. |
| 6. Output Generation | Model generation layer | Produce new text or behavior via the backend model. |
| 7. Field Update | Feedback and field update layer | Integrate output into the runtime field and close the loop. |
The runtime loop operates primarily inside the runtime mediation boundary,
handling field management, coherence control, memory integration, and attractor regulation.
However, it coordinates with the input boundary as the inbound semantic source
and the model generation boundary as the generative output anchor.
I/O Anchors:
- Input boundary: encapsulates human input, context framing, and task goals.
- Model generation boundary: executes generation and emits symbolic output.
The runtime serves as the mediation channel between these two endpoints,
ensuring that all recursion remains bounded and semantically aligned.
An implementation conforms if it:
Later versions may extend the loop with adaptive control postures and semantic compression metrics (SCR).
References
Tsaliev, E. (2025). SIGMA Runtime Architecture v0.1 — DOI 10.5281/zenodo.17703667