Skip to content
P‑AIProject‑AI
Doctrine · Iron Path

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.

Governance Contract · binding invariants

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.

contract
  1. point 01
    Admissible

    The contract requires every request to be evaluated against the current governance configuration. Unevaluated requests are inadmissible under the contract.

  2. point 02
    Invariant-Preserving

    Execution proceeds only when all registered invariants are at or below WARN. BLOCK / HALT / ESCALATE stop execution unconditionally.

  3. point 03
    Continuity-Maintaining

    The governance state chain is hash-linked. Predecessor hash must match the current chain head; forks are rejected.

  4. point 04
    Cryptographically Bound

    The contract requires signed authorizations, authenticated capability tokens, and content-hashed evidence bundles.

  5. point 05
    Auditable

    The contract requires evidence for terminal execution verdicts and for non-terminal health, gate, and policy states; those state namespaces are not interchangeable.

  6. point 06
    Authorized at Instance Level

    Type-level permits are not enough. Each execution instance needs a scoped, valid CapabilityToken naming the actor and operation.

  7. point 07
    Semantically Coherent

    Conflicts between concurrent decisions are detected before execution. Semantic collisions force adjudication, not first-write-wins.

  8. point 08
    Sovereign-Bound

    The Sovereign contract makes the Iron Path, configuration snapshots, and audit linkage mandatory. End-to-end non-bypassability is not yet verified.

  9. point 09
    Policy-Anchored

    The contract requires each binding decision to reduce to an externally governed PolicyRecord; the kernel must not author its own policy.

  10. point 10
    Deterministically 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.

Gate 04 · Policy · Ethics · Consistency

ExecutionGate

gate

The documented contract's intended gate for each in-scope admissible action. It evaluates policy, ethics, and consistency against the current constitution before an execution warrant may issue; complete call-site coverage remains unverified.

Inputs
  • Capability
  • Active policy bundle
  • Consistency snapshot
Outputs
  • Execution warrant
  • Required reflex bounds
Failure mode

Policy / ethics conflict → DENY or escalate to Triumvirate quorum.