Sigma Stratum Documentation – License Notice
This document is part of the Sigma Runtime Standard (SRS) and the
Sigma Stratum Documentation Set (SRD).It is licensed under Creative Commons Attribution–NonCommercial 4.0
(CC BY-NC 4.0).The license for this specific document is authoritative.
For the full framework, see/legal/IP-Policy.
The Sigma Runtime Loop implements the core cognitive recursion cycle —
an evolution of the original F-Loop introduced in
∿ Neurosymbolic Scaffolding for Recursive Coherence (2025).
Originally formulated as:
G → Πsym → F → Semantic Graph → G
where:
This loop models recursive cognition —
each generation step is informed not only by the immediate text history,
but by the continuously updated field state, integrating meaning, memory, and attractor stability.
In the original Sigma Runtime Standard, the F-Loop was formalized
as the Recursive Control Loop (RCL) — the canonical execution cycle spanning SL0–SL6:
In current explanatory terms, the runtime loop is not only a turn processor.
It is the system’s bounded control cycle.
Each iteration can:
This is what allows the runtime to treat interaction as a controlled field rather than a stateless exchange of prompts and replies.
State Initialization
Context Assembly
Stabilization Pass
Generation Pass
Verification and Shaping
Memory Integration
Field Update
Self-Modeling Feedback
The Adaptive Entropy Protocol (AEP) contributes bounded entropy-regulation
evidence to the runtime loop.
At the SRD level, AEP should be understood as a control companion to the
stabilization, verification, and recovery stages. It helps the loop distinguish
between:
AEP evidence may influence context shaping, output verification, and recovery
posture, but it does not replace memory, safety, identity, or runtime authority.
It also does not require a public implementation to expose formulas, prompts, or
private telemetry paths. The public requirement is that AEP-related control
claims remain bounded, inspectable, and traceable.
The loop is not purely synchronous in the intuitive sense.
It has to reconcile:
This matters because many runtime failures are not visible at the prompt level alone.
They emerge only when the next cycle inherits the consequences of the previous one.
SRIP-17 exchange does not bypass the runtime loop. Incoming exchange artifacts
enter the receiving runtime as external evidence and must pass authorization,
provenance, memory, drift, and safety checks before they influence local state.
Outgoing artifacts should likewise be prepared from bounded runtime evidence
rather than raw private state unless explicit authorization permits a broader
export.
This keeps multi-agent exchange inside governed recursion instead of allowing
external artifacts to rewrite the field directly.
Publicly, the runtime loop is best understood as producing evidence in several families:
The exact implementation details may evolve, but the public contract remains:
The SIGMA Runtime Loop turns recursive interaction into a bounded control process.
By combining context assembly, drift-aware shaping, memory integration, verification, and field update, the loop supports:
This is the public architectural meaning of Sigma Runtime:
not just generation, but governed recursive interaction.
References:
Tsaliev, E. (2025). Neurosymbolic Scaffolding for Recursive Coherence — DOI: 10.5281/zenodo.17582941
Tsaliev, E. (2025). SIGMA Runtime Architecture v0.1 — DOI: 10.5281/zenodo.17703667