Current Reframe Governance Status
Reviewed: 17 August 2026 · Publication: independent, public, OS-aware governance projection
Reframe is governed as a writing instrument with one continuous manuscript surface, semantic navigation beside it, Copilot mediation on the right, and MIDI2 peer projections below. This site is the current maintainer-facing map of that position. It is readable by people, addressable by machines, and deliberately separate from runtime authority.
What is current
- Operational authority: the MIDI backplane IDL, generated facts and reasoning manifest, live FountainStore state, and the governed runtime. This publication explains those boundaries; it does not replace them.
- Product projection: a continuous Courier/Fountain reading surface with adjacent Questions, Movements, and Read coverage—not a card gallery, A4 page browser, or horizontal timeline.
- Development method: every new command, capability, system boundary, and projection begins with a versioned E2E scenario and is accepted through focused tests, AX, visual evidence, and persisted Store proof.
- Publication boundary: the public Book and this governance site expose reviewed, sanitized contracts and evidence-backed claims. Private source, secrets, manuscript material, and Store data remain out of the public projection.
Begin here
- Read the maintained reading index to select only the chapters relevant to a task.
- Read the agent operating guide and validation and acceptance before changing or driving Reframe.
- For the current product surface, read the default semantic manuscript projection.
- For scenario-led implementation, read the scenario development cycle and scenario infrastructure.
- For publication decisions, read the public/private publication boundary and independent governance publication.
Historical material is retained
No chapter is deleted or silently rewritten by this status page. “Reference” means that a chapter remains available because it explains an architectural era, vocabulary, or retained constraint. “Current” identifies the small set of chapters that currently orient implementation and publication. A chapter will be marked “Superseded” only when a reviewed replacement is named explicitly; no such claim is made here without that evidence.
The development history explains why older assumptions remain useful as history while the current-state analysis describes contradictions that still require live code and Store verification.
Machine-readable status
The publication generator emits the same status model in chapter-status.json, adds status labels to the chapter rail and index, exposes canonical URLs and JSON-LD metadata, and keeps every page keyboard navigable. Status labels are navigation aids—not runtime readiness claims.
This page is a navigational status statement, not a replacement for the governed chapters or runtime evidence.