The governed request pipeline: eight visible runtime stages inside the nine-gate execution model.

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.

Closes the 'flat gap'. Any action that crosses a discontinuity in agent state must produce a signed continuity attestation before the ExecutionGate will admit it.

Reconstructs the authority chain from the action back to the constitution. No action may execute that cannot present a complete, signed authority path.

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.

Where a Triumvirate warrant is required, Galahad, Cerberus, and Codex Deus Maximus must all authorize it: 3/3 modules. No two may overrule the third in its domain.

The normal server receipt path writes hash-linked entries for later inspection. The current storage boundary does not yet prove that every row was produced by that path or that every external effect is represented.

Terminal refusal state. SAFE_HALT is a positive decision: the system explicitly recorded that the action cannot be admitted. There is no implicit consent path.

The contract's intended execution route. It requires capability, policy, and an audit anchor before an effect is admitted; complete non-bypassability remains to be demonstrated.