Containment must precede governed effects.
internal designation — The Iron Path
10 doctrine points map to 9 documented execution gates. The contract requires every governed effect to pass them; complete runtime entry-point coverage remains an open assurance claim.
The Ten Points
The contract requires each in-scope governed execution to satisfy all ten points and defines HALT or ESCALATE for violations. Complete runtime coverage remains unverified.
- point 01Admissible
The contract requires every request to be evaluated against the current governance configuration. Unevaluated requests are inadmissible under the contract.
- point 02Invariant-Preserving
Execution proceeds only when all registered invariants are at or below WARN. BLOCK / HALT / ESCALATE stop execution unconditionally.
- point 03Continuity-Maintaining
The governance state chain is hash-linked. Predecessor hash must match the current chain head; forks are rejected.
- point 04Cryptographically Bound
The contract requires signed authorizations, authenticated capability tokens, and content-hashed evidence bundles.
- point 05Auditable
The contract requires evidence for terminal execution verdicts and for non-terminal health, gate, and policy states; those state namespaces are not interchangeable.
- point 06Authorized at Instance Level
Type-level permits are not enough. Each execution instance needs a scoped, valid CapabilityToken naming the actor and operation.
- point 07Semantically Coherent
Conflicts between concurrent decisions are detected before execution. Semantic collisions force adjudication, not first-write-wins.
- point 08Sovereign-Bound
The Sovereign contract makes the Iron Path, configuration snapshots, and audit linkage mandatory. End-to-end non-bypassability is not yet verified.
- point 09Policy-Anchored
The contract requires each binding decision to reduce to an externally governed PolicyRecord; the kernel must not author its own policy.
- point 10Deterministically Replayable
The contract requires identical inputs, configuration, and chain state to produce the same outcome and hash. Cross-host replay evidence is not yet published.
User / Request
The documented architecture normalises an externally proposed action into a governance ticket before downstream gate evaluation. End-to-end gate coverage remains an assurance claim, not a verified property of every execution path.
- Raw user intent
- Tool invocation
- Scheduled job
- Normalised ticket
- Provisional capability claim
Malformed ticket → reject at ingress, no audit cost incurred downstream.