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 proposes a common way to inspect control conflicts across SRIPs.
It does not override precedence rules declared in canonical proposals. Any
conflict between this review model and an SRIP is a finding requiring a separate
normative review.
Several SRIPs can legitimately produce different recommendations for one
runtime state. For example:
The architecture needs a stable distinction between evidence, recommendation,
authorization, execution, and post-effect audit.
| Class | Meaning | Representative SRIPs |
|---|---|---|
| Evidence | Observes or measures state without granting authority | 03, 07, 08, 16, 21, 27 |
| Assembly | Selects, compresses, or structures context | 11, 14, 18, 25 |
| Recommendation | Proposes regulation, perturbation, or candidate state | 10, 15, 16, 23 |
| Boundary | Allows, limits, quarantines, or rejects influence | 06, 13, 20, 26 |
| Domain authority | Owns deterministic state within a declared domain | 12 |
| Governance authority | Evaluates legitimacy, capture, contestability, and promotion | 22 |
| Effect execution | Represents authorized contact with an external target | 05, 17, 24, 25 |
| Recovery | Preserves or restores valid state after conflict or instability | 06, 09, 13, 19 |
| Admission transaction | Selects one candidate for delivery before persistence | 28 |
One SRIP may occupy more than one class, but each individual output should state
which class it represents.
The following order is a review hypothesis, not a new normative rule:
SRIP-06.SRIP-20, with identity scope from SRIP-13 and externalSRIP-21.SRIP-22.SRIP-14 andSRIP-26.SRIP-12.SRIP-19 and applicableSRIP-06, SRIP-09, and SRIP-13.SRIP-27 supplies evidence andSRIP-28 owns the pre-persistence commit point within all higher boundaries.SRIP-03, SRIP-07,SRIP-08, SRIP-10, and SRIP-15.SRIP-18, SRIP-23, and non-normative style mechanisms.Higher precedence generally limits lower-precedence action. It does not permit a
higher layer to fabricate missing evidence or silently assume authority outside
its declared scope.
Precedence is not temporal ordering. Generation may occur before measurement,
but a generated candidate remains non-canonical until SRIP-27 evidence and the
SRIP-28 transaction are evaluated. SRIP-28 owns the commit point; it does not
override safety, authorization, governance, or deterministic domain authority.
For any proposed state transition or effect:
Missing authority fails closed for effects. Missing evidence should produce an
unknown or deferred state rather than an invented authorization.
SRIP-14 may retrieve relevant material. SRIP-26 may still limit or reject
its influence because relevance does not establish current scope, consent, or
authority.
SRIP-10 may recommend variation and SRIP-15 may propose perturbation.
SRIP-06 can block the transition when recursion, instability, or containment
constraints apply.
SRIP-16 may report a recurring control mismatch. That report is evidence.
SRIP-20 evaluates whether any boundary adjustment is authorized; the
self-model cannot authorize its own expansion.
SRIP-23 may generate a candidate from contradiction preserved by SRIP-19.
The candidate does not delete the contradiction and cannot become canonical
solely because it is coherent. Applicable governance remains required.
SRIP-27 may measure its target membership, but only SRIP-28 may select it
for accepted delivery and downstream influence.
SRIP-10 may report stable dynamics while SRIP-27 reports a displaced or
collapsed trajectory. Stability does not override membership. SRIP-28 must
contain a candidate that lacks qualified admission evidence.
SRIP-18 may improve grounding and candidate assembly. SRIP-12 retains
deterministic authority over valid commerce transitions and rejection rules.
SRIP-24 owns effect staging, current-authority validation, release, retry,
compensation, and escalation. SRIP-25 separately represents authorization,
attempt, outcome observation, and verification. A successful tool or transport
call does not retroactively establish valid authority or prove external
outcome. SRIP-28 candidate admission does not authorize the effect.
A future machine-readable control decision envelope should be able to expose:
This review document does not define that schema. A schema would require a
separate normative or machine-readable-artifact decision.
SRIP-22 govern only institutional legitimacy, or runtime-local controlSRIP-25 event, or only implementations claiming