The Book
of Reframe
How a source becomes a reading, a governed action, an observed result—and, when admitted, a publication.
This is a book about Reframe. It is not the Reframe Bookshelf, a substitute for a manuscript, or a promise that development features have shipped.
Four ways into the work.
Read in sequence, or enter at the evidence that interests you. These are existing public pages, not invented Bookshelf volumes.
- IThe methodFrom a source to a governed scenario and its criteria
- IIThe journeysWhich scenarios have evidence, and what it does not yet establish
- IIIThe observable behaviorA dated command inventory, not a list of shipped product features
- IVSound in spaceCsound, Teatro, Ear and the boundary between score and hearing
Book is not Bookshelf.
This Book
A reviewed, public narrative about Reframe's development. Its claims remain tied to dated records and checked evidence.
A manuscript
An authored source with its own identity and custody. Having a file, a PDF or a cover does not make it an admitted reading edition.
The Reframe Bookshelf
The writer's collection of explicitly admitted works and editions. Fountain Press composes their measured reading pages; this website does not grant admission.
A separately published reading, such as First Reading, is another kind of object—not a chapter of this Book.
Five acts, five different claims.
- SourceIdentify the material and its provenance.
- ScenarioName what must happen and what would count as evidence.
- ImplementBuild bounded behavior against that contract.
- AcceptWitness actual results, interfaces and persistence.
- PublishRelease only the separately reviewed public projection.
What the records establish.
These are the retained, checked technical records from the 15 August 2026 Book snapshot. They are useful evidence, not a measure of current product availability.
Open the quantitative records and evidence notes
Four records answer four different questions.
Keeping these records separate prevents a command count, a ready state, or a successful scenario from becoming an accidental product claim.
What entries exist?
95 command entries in the verified development catalog. Aliases count as entries, not new powers.
Read verified behavior →What is governed?
55 capability identities, with policy, ownership, proof, and acceptance tracked separately.
Read the capability atlas →What has been proven?
6 named scenarios are live-accepted in the current snapshot; 4 command pages are eligible.
Read scenario coverage →What may the App promise?
No named distribution build is recorded. The release allow-list is empty.
Read the release surface →These values are generated from the checked publication projection, not inferred from conversational or UI wording.
Claims stay attached to evidence.
Read the status as a chain, not a badge. Each step answers a narrower question.
Scenario first
A named scenario defines prerequisites, terminal predicates, and the evidence needed before a command page is eligible.
Open scenario coverage →Acceptance is not release
AX, visual capture, FountainStore, telemetry, and provenance can establish a result without creating a released App surface.
Check the release boundary →Development inventory is not a promise
The command atlas records what the development runtime exposes. It is not a marketplace, product catalogue, or capability allow-list.
Open the command atlas →The orientation layer.
Use these records as the stable map. The Book explains; the integration runtime and persisted Store remain operational authority.
A Fountain Coach publication projection. The current Reframe runtime and the author's Bookshelf remain independent of this static Book.