Choose one six-page path. Each journey moves from the doctrine into mechanisms you can run, inspect, challenge, or verify.
Move from the execution model to a working decision, then inspect claims, current posture, replay instructions, and the briefing path.
Trace the runtime model, exercise its gates, score unresolved evidence, verify a receipt, and reach the exact replay and source surfaces.
Move from the binding contract to its doctrine map, adversary model, public challenge surface, bounded claims, and source corpus.
Move from the concise thesis to a working demonstration, inspect the evidence boundary, see the wider practice, and reach a scoped briefing.
The request satisfies the visible governance path and can proceed.
A gate rejects the request before execution continues.
Execution pauses and hands off because ambiguity or risk is too high.
Replay a receipt and confirm the governing constitution hash.
The request is read-oriented, provenance-backed, and ends with a signed replay path.
Public reviewer context is sufficient.
Verification is an allowed read capability.
The replay references a known constitution hash.
A stable receipt can be reproduced and inspected.