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.
This page provides conceptual reading paths for Sigma Runtime Improvement Proposals.
It is a navigation view, not a numbering authority.
SRIP numbers remain immutable public proposal identifiers. The numerical registry records proposal history. This page may change as the architecture evolves.
For the authoritative numerical registry, see /srs/registry.
This reading order is not a certification claim.
Reading or implementing SRS/SRIP documents does not imply official Sigma certification, endorsement, or use of Sigma marks.
For conformance terminology, see /srs/conformance/.
- SRIP numbers are assigned monotonically after public draft acceptance.
- SRIP numbers are not reassigned to improve conceptual order.
- Architecture relationships are expressed through
Parent Specs, Related Specs, Extends, Amends, and Supersedes.
- Conceptual reading order is maintained here and in other index views.
This preserves citation stability while still allowing readers to follow the architecture in the order that best fits a given stack.
Read these first when entering the public standard:
- SRIP-00 — Foundations and Scope
- SRIP-01 — Canonical Runtime Loop
- SRIP-02 — Attractor State Model and Metadata
- SRIP-03 — Drift Metrics and Stabilization Algorithms
- SRIP-04 — Memory Layer Architecture
- SRIP-05 — Interoperability Interface
- SRIP-06 — Safety and Recursion Boundaries
- SRIP-07 — Symbolic Density Layer
- SRIP-08 — Phase Vector Model and PRM
¶ Memory And Retrieval Sequence
Use this path for long-running memory, retrieval, and recall behavior:
- SRIP-04 — Memory Layer Architecture
- SRIP-09-LTM — Long-Term Memory and Structural Coherence Layer
- SRIP-11-CMT — Compression and Memory Topology
- SRIP-14-RMI — Retrieval and Memory Integration Layer
- SRIP-21-EIB — External Identity Binding and Mode Reconciliation, when retrieved or recalled material describes one external entity through conflicting observed modes
- SRIP-20-ANS — Autonomy Negotiation and Boundary Stabilization, when retrieved or recalled material applies pressure to runtime-local boundary state
- SRIP-18-CSI — Commerce Semantic Integration Layer, when commerce context must be assembled from memory and runtime state
Use this path for commerce-aware runtime behavior:
- SRIP-14-RMI — retrieval and memory governance
- SRIP-18-CSI — semantic commerce context assembly
- SRIP-12-CDS — deterministic commerce decision state
In this stack, CDS remains the deterministic authority for commerce state and transition decisions. CSI supplies bounded semantic context. RMI governs memory and retrieval boundaries used by the assembly process.
This order is conceptual. It does not change the public SRIP numbers.
¶ Runtime Control And Stability Sequence
Use this path for control, drift, stability, and response-shaping behavior:
- SRIP-03 — Drift Metrics and Stabilization Algorithms
- SRIP-06 — Safety and Recursion Boundaries
- SRIP-07 — Symbolic Density Layer
- SRIP-08 — Phase Vector Model and PRM
- SRIP-10-AEP — Adaptive Entropy Protocol
- SRIP-13-RIS — Relational Identity Stabilization
- SRIP-21-EIB — External Identity Binding and Mode Reconciliation, when identity/mode separation is needed before contradiction buffering
- SRIP-15-ADP — Attractor Dynamics and Controlled Perturbation Layer
- SRIP-19-RCB — Recursive Contradiction Buffering
- SRIP-20-ANS — Autonomy Negotiation and Boundary Stabilization
- SRIP-22-GRC — Governance Recursion and Collusion Boundary, when runtime control authority, certification, emergency override, or legitimacy state must be evaluated
- SRIP-16-RSM — Recursive Self-Modeling
¶ Multi-Agent And Interoperability Sequence
Use this path for system integration, agent exchange, and multi-agent coordination:
- SRIP-05 — Interoperability Interface
- SRIP-17-MAE — Multi-Agent Exchange
- SRIP-21-EIB — External Identity Binding and Mode Reconciliation, when agent disagreement describes the same external entity through conflicting observed modes
- SRIP-20-ANS — Autonomy Negotiation and Boundary Stabilization, when exchanged artifacts apply influence or authority pressure to local runtime state
- SRIP-19-RCB — Recursive Contradiction Buffering, when exchanged evidence or agent disagreement must remain unresolved without forced consensus
- SRIP-22-GRC — Governance Recursion and Collusion Boundary, when exchanged artifacts carry governance, certification, authority, or marks claims
¶ Governance, Certification, And Legitimacy Sequence
Use this path for governance authority, certification integrity, marks boundary, emergency override, capture visibility, and fork/exit analysis:
- SRIP-05 — Interoperability Interface, for lineage and compatibility boundaries
- SRIP-06 — Safety and Recursion Boundaries, for non-bypassable safety constraints
- SRIP-13-RIS — Relational Identity Stabilization, for participant and identity-boundary continuity
- SRIP-17-MAE — Multi-Agent Exchange, for exchanged attestations and agent-origin evidence
- SRIP-19-RCB — Recursive Contradiction Buffering, for unresolved governance evidence conflicts
- SRIP-20-ANS — Autonomy Negotiation and Boundary Stabilization, for authority pressure on local runtime state
- SRIP-21-EIB — External Identity Binding and Mode Reconciliation, for stable identity of governors, authorities, validators, auditors, certification bodies, forks, and legal entities
- SRIP-22-GRC — Governance Recursion and Collusion Boundary, for legitimacy states, collusion assumptions, capture handling, certification suspension, and fork/exit conditions
This sequence does not imply certification or production implementation. It is a review path for public specification readers.
SRIPs may be reviewed as architecture design artifacts when they define boundaries, contracts, conformance expectations, risks, non-goals, lifecycle state, and acceptance criteria.
TOGAF and similar enterprise architecture frameworks may be used as non-normative review lenses. They are not required dependencies for writing, citing, or implementing SRIPs.
The Sigma Runtime Standard remains open-standard-first and framework-independent.