Reframe Governance

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.

Open the stable status-quo page · Browse every retained chapter

CHAPTER INDEX

Read by chapter.

Every chapter remains available. Labels describe its relationship to the current operating position; they do not erase the historical record.

00Abstract Reference 01Reading Index Current index 02Development History and Retained Lessons Reference 03Current State and Refactoring Problem Reference 04Target Architecture Reference 05Extended Grounding Contract Reference 06Refactoring Program Reference 07Operating Guide for `.claude` and `.codex` Current operating guide 08Validation and Acceptance Current acceptance 09Compatibility and Future Evolution Reference 10Copilot Implementation Extension Reference 11Grounding as a Given — the Canonical Manifesto and Conversational Authoring Reference 12Animating Truth — Foreshadowing and Perceived Performance Reference 13Storage and Performance — What Persists Where, and Why Reads Are Fast Reference 14The Beat and Its Arrangements — One Object, Three Views, One Firing Reference 15The Situated Copilot — One Copilot, Differently Placed Reference 16The Timeline Is the Machine Room — What You See Is What You Get Reference 17The Score — Reframe's Performance Space, and the One Surface That Folds the Others Reference 18The Stage Presents the Act — Legibility Over Density Reference 19Apple's Human Interface Guidelines — the Baseline We Build On Reference 20Paid-First Copilot, and the Writer's Key — Quality-First Lane Selection Reference 21Training Perspectives — Teaching the On-Device Model the Writer's Work Reference 22No Preferences, Only Reasoning Reference 23One Reasoning — The Single Front Door of a Turn Reference 24The Reasoning Is an Uncertainty Map Reference 25The CoPilot Is the Surface Reference 26Internals Tune Themselves — the Disposition of the Preferences Panel Reference 27Parse Before You Ask Reference 28A Beat Is the Question It Raises Reference 29NaturalLanguage Measures, Storify Interprets Reference 30The Living Gazetteer Reference 31Compiled Knowledge — the Cloud Teaches, the Device Remembers Reference 32Referenced Knowledge — What the World Knows Outside the Book Reference 33A Want Is a Gap in a Ledger Reference 34A Question That Leaves the Work Reference 35Deep Search Reference 36Every Gap Keeps Its Address Reference 37Copilot Capability Governance — From Transport Contract to Trustworthy Action Reference 38Copilot Capability Audit Skill — From Boundary to Empowerment Reference 39A Model Cannot Be Told What It Cannot Do Reference 40A Citation Is a Promise Someone Can Check Reference 41One Retrieval, Two Directions Reference 42What Is Already Recorded Is Read, Never Re-Derived Reference 43The Released Surface Is a Named Build Current release boundary 44Public Publication and Private Source Policy Current publication boundary 45Copilot Reading Surface and Typography — Situated, Legible, and Reframe-Native Reference 46Dynamic Grounding: From Default Reading to Writer-Accepted Lens Reference 47Situated, Mixed-Initiative Interaction Reference 4848. A Service Is a Fact, Not a Symptom Reference 4949. One Definition, Two Projections Reference 5050. Text Is Stored So It Can Be Pointed At Reference 5151. One Decision Decides the Lane Reference 5252. The Pencil Belongs to the Writer Reference 5353. A Selection Snaps to Meaning Reference 54The Writer Does Not Manage the Projection Reference 55One Store Authority Across Repositories Reference 56The Book Library Is Reframe's Sole Reading Provider Reference 57The Writer Enters by Intention Reference 58Open-Turn Mediation Protocol Reference 59The Fountain-Coach Git Library and Reframe Project Flow Reference 60The Fountain Editor Is the Project Surface Reference 61The Fountain Project Round Trip Reference 62Reframe Maintenance Control Plane Reference 63FountainMaintenanceKit — Portable Swift Maintenance Contract Reference 64FountainProjectKit — Durable Fountain Project Custody Reference 65The Copilot as Writing Coach Reference 66FountainImagePublicationKit — Reframe Image Cloud and Publication Boundary Reference 67FountainComposerKit — Remote Attachment Custody and the Composer Boundary Reference 6868 — The Reframe E2E Scenario Is the Publication Unit Reference 69The Book of Reframe Is a Dual Projection Current publication model 7070 — External MIDI2 Control of Reframe Reference 7171 — Reframe-to-Reframe Software-Peer Acceptance Reference 7272 — MIDI2 Peer Projections and Capacity Admission Reference 7373 — The Reframe Scenario Development Cycle Current development cycle 74Private Image Prompt History Reference 7575 — Scenario Run Ownership and Non-Interference Reference 76Beat Movement and the Uncertainty Overlay Reference 7777 — The Scenario Runtime Is Swift and MIDI2-Native Reference 7878 — Scenario-Driven Development Is Org Infrastructure Current infrastructure 7979 — The Default Semantic Manuscript Projection Current product projection 8080 — Independent Governance Publication Current publication target ·Reframe — How the App Must Flow Reference