Prerequisites
A dependent command cannot start until its source, reading, confirmation, or other declared predecessor has reached its own terminal state.
Evidence registry · development story
Scenario coverage makes the method inspectable.
A scenario is the contract between implementation and publication. This registry records which named journeys have reached the evidence state required for a public Book record.
Read the source projection → · Open generated publication manifest → · Chapter 68
Three authorities
One journey, separate proof.
AX proves what the writer-facing surface exposed and accepted. FountainStore proves what happened. A CoreGraphics window-ID capture proves what the surface looked like. Telemetry explains the run but cannot replace those authorities. Codex uses the governed reframe-scenario-work-session entry point to keep source work, execution, witnessing, and publication in one bounded loop.
State-based waits
Scenarios wait for semantic AX or Store predicates. Timeouts are recorded as failures or blockers; arbitrary sleeps are not evidence.
One binding
Every result is bound to one PID, window ID, managed Store, executable, and source commit.
Maintainer capability
Reframe owns the reusable journey.
reframe.e2e.scenario.run discovers scenarios, checks prerequisites, executes typed behavior, and records FountainStore receipts. It is not writer-facing and cannot approve itself. This public page is the human reference; a future maintainer snapshot may add internal procedure context only from the same reviewed Book commit and digest.
Internal proof
Runtime receipts and FountainStore establish behavioral truth.
Independent witness
Live Drive independently proves AX, the CoreGraphics window ID, and visual fidelity.
Publication rule
The Book publishes only the sanitized intersection of both evidence sets.
Coverage matrix
Named scenarios decide page eligibility.
Legacy notes remain linked as history. A command route is eligible only when its named scenario is live-accepted and its reviewed page exists; accepted scenarios without pages remain visible but unpublished.
/commands
commands-discover · Live-accepted · page eligible.
/pipeline status
pipeline-status · Live-accepted · page eligible.
/threads
threads · Live-accepted · page eligible.
/ground
ground-after-reading · Executable · pending live witness.
/readings
readings-comparison · Live-accepted · page eligible.
/world
world-after-storify · Live-accepted · accepted, but no command page yet.
System capability coverage
MIDI2 can carry a governed operation between Reframes.
reframe-to-reframe-peer-projection is live-accepted for software-peer acceptance. It exercises the existing storify.source.start operation and does not add a writer-facing command.
Open the MIDI2 software-peer capability record → · Read the development method → · Machine-readable coverage manifest →
Instrument scenario
The Csound path is a named record.
csound-auv3-instrument-boundary connects the scenario method to the Csound AUv3 capability record. Follow the record for the exact host boundary, evidence obligations, and authoritative Governance chapter.
Open the Csound AUv3 boundary record → · Open the Instruments catalog record → · Read Governance Chapter 133 →