Sigma Runtime Standard - Public Integration Notice
This non-normative integration document is licensed under Creative Commons
Attribution 4.0 International (CC BY 4.0). It does not amend canonical
SRIPs or grant implementation, certification, or runtime authority.
Status: Non-normative review draft
This document audits two separate graph surfaces:
Parent Specs edges declared by SRIP-00It does not amend canonical SRIPs. A canonical dependency and an architectural
interpretation are never treated as the same evidence class.
| Status | Meaning |
|---|---|
confirmed |
Supported by canonical metadata, normative scope, or an explicit relationship/control section. |
inferred |
Architecturally plausible, but the exact type or direction is not normatively declared. |
needs_decision |
A relationship exists, but its authority or direction requires normative review. |
conflict |
Contradicts canonical source. |
Parent Specs confirms a dependency only. It does not by itself prove
extends, specializes, governs, or another semantic verb.
The graph contains 98 canonical parent edges. They are transcribed directly
from the proposal headers available on 2026-07-17.
Coverage includes the previously omitted dependencies for memory,
interoperability, AEP, phase, identity, multi-agent exchange, governance, MIL,
TMC, and TAL. No transitive shortcut is stored as a canonical parent edge.
SRIP-15 remains unchanged: SRIP-06 is a related specification with explicit
normative safety precedence, not a parent added by this review.
| # | Integration edge | Status | Evidence and boundary |
|---|---|---|---|
| 1 | 03 provides_evidence_to 02 |
confirmed | Drift observes movement relative to attractor state. |
| 2 | 06 constrains 01 |
confirmed | Safety can limit or stop runtime continuation. |
| 3 | 10 related_to 07 |
inferred | Density and entropy are coupled, but no direct dependency is declared. |
| 4 | 06 constrains 15 |
confirmed | ADP explicitly subordinates perturbation to safety. |
| 5 | 12 governs 18 |
confirmed | CDS retains deterministic commerce state authority. |
| 6 | 19 recovers 03 |
confirmed | RCB buffers unresolved instability rather than forcing convergence. |
| 7 | 20 governs 16 |
confirmed | Self-model evidence cannot authorize its own expansion. |
| 8 | 20 constrains 17 |
confirmed | ANS bounds exchanged influence and delegation. |
| 9 | 21 constrains 14 |
confirmed | Entity/mode authority constrains retrieval interpretation. |
| 10 | 21 feeds 19 |
confirmed | Unresolved mode evidence is handed to RCB. |
| 11 | 22 constrains 17 |
confirmed | GRC bounds MAE legitimacy and capture. |
| 12 | 22 governs 20 |
confirmed | GRC evaluates the legitimacy of autonomy authority. |
| 13 | 22 governs 23 |
confirmed | DGL cannot promote its own candidate to canonical state. |
| 14 | 22 constrains 24 |
confirmed | Environment effects remain governance-bound. |
| 15 | 22 constrains 25 |
confirmed | Event transport does not create effect authority. |
| 16 | 26 feeds 20 |
inferred | MIL evidence may create autonomy pressure; the exact handoff remains descriptive. |
| 17 | 27 provides_evidence_to 28 |
confirmed | TMC measures; TAL admits. TMC has no delivery authority. |
| 18 | 28 governs 23 |
confirmed | A generated candidate remains non-canonical before TAL admission. |
| 19 | 28 feeds 26 |
confirmed | Only admitted lineage may proceed to downstream memory influence. |
| Surface | Confirmed | Inferred | Needs decision | Conflict |
|---|---|---|---|---|
| Canonical parent edges | 98 |
0 |
0 |
0 |
| Selected integration overlay | 17 |
2 |
0 |
0 |
The integration overlay is not a substitute for canonical parent metadata and
does not claim complete control-flow coverage.
The repaired architecture includes the missing transaction boundary:
candidate generation
-> SRIP-27 target-membership evidence
-> SRIP-28 pre-persistence admission
-> selected admitted delivery and influence
Dynamic stability from SRIP-10 does not imply target membership. TMC evidence
does not admit or reject a candidate. TAL does not rewrite TMC measurement.
This review does not change any SRIP header. Canonical metadata changes require
a separate proposal-specific amendment with version, date, and change-history
handling. Inferred presentation relationships remain in the integration
overlay with their confidence explicit.