FCIS · REFRAME REFACTORING · PUBLISHED PROJECTION
PUBLIC FCIS PROJECTION · STATUS QUO

Reframe Governance

Reviewed: 6 September 2026 · Publication: independent, public, OS-aware governance projection

Last reading: Chapter 156 — FCIS 156 — The Writer Never Operates EstatePublisher.

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.

Read by intention

Chronology is retained, but it is no longer the primary way into the system. Start from the question you are carrying, then follow the smallest governed path that answers it.

Begin here

  1. Read the maintained reading index to select only the chapters relevant to a task.
  2. Read the agent operating guide and validation and acceptance before changing or driving Reframe.
  3. For the current product surface, read the default semantic manuscript projection.
  4. For scenario-led implementation, read the scenario development cycle and scenario infrastructure.
  5. For publication decisions, read the public/private publication boundary and independent governance publication.
  6. Latest reading: Chapter 151 — Csound Teatro: Speaking Sound in Space.

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.

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 Reference01Reading Index Current index02Development History and Retained Lessons Reference03Current State and Refactoring Problem Reference04Target Architecture Reference05Extended Grounding Contract Reference06Refactoring Program Reference07Operating Guide for `.claude` and `.codex` Current operating guide08Validation and Acceptance Current acceptance09Compatibility and Future Evolution Reference10Copilot Implementation Extension Reference11Grounding as a Given — the Canonical Manifesto and Conversational Authoring Reference12Animating Truth — Foreshadowing and Perceived Performance Reference13Storage and Performance — What Persists Where, and Why Reads Are Fast Reference14The Beat and Its Arrangements — One Object, Three Views, One Firing Reference15The Situated Copilot — One Copilot, Differently Placed Reference16The Timeline Is the Machine Room — What You See Is What You Get Reference17The Score — Reframe's Performance Space, and the One Surface That Folds the Others Reference18The Stage Presents the Act — Legibility Over Density Reference19Apple's Human Interface Guidelines — the Baseline We Build On Reference20Paid-First Copilot, and the Writer's Key — Quality-First Lane Selection Reference21Training Perspectives — Teaching the On-Device Model the Writer's Work Reference22No Preferences, Only Reasoning Reference23One Reasoning — The Single Front Door of a Turn Reference24The Reasoning Is an Uncertainty Map Reference25The CoPilot Is the Surface Reference26Internals Tune Themselves — the Disposition of the Preferences Panel Reference27Parse Before You Ask Reference28A Beat Is the Question It Raises Reference29NaturalLanguage Measures, Storify Interprets Reference30The Living Gazetteer Reference31Compiled Knowledge — the Cloud Teaches, the Device Remembers Reference32Referenced Knowledge — What the World Knows Outside the Book Reference33A Want Is a Gap in a Ledger Reference34A Question That Leaves the Work Reference35Deep Search Reference36Every Gap Keeps Its Address Reference37Copilot Capability Governance — From Transport Contract to Trustworthy Action Reference38Copilot Capability Audit Skill — From Boundary to Empowerment Reference39A Model Cannot Be Told What It Cannot Do Reference40A Citation Is a Promise Someone Can Check Reference41One Retrieval, Two Directions Reference42What Is Already Recorded Is Read, Never Re-Derived Reference43The Released Surface Is a Named Build Current release boundary44Public Publication and Private Source Policy Current publication boundary45Copilot Reading Surface and Typography — Situated, Legible, and Reframe-Native Reference46Dynamic Grounding: From Default Reading to Writer-Accepted Lens Reference47Situated, Mixed-Initiative Interaction Reference4848. A Service Is a Fact, Not a Symptom Reference4949. One Definition, Two Projections Reference5050. Text Is Stored So It Can Be Pointed At Reference5151. One Decision Decides the Lane Reference5252. The Pencil Belongs to the Writer Reference5353. A Selection Snaps to Meaning Reference54The Writer Does Not Manage the Projection Reference55One Store Authority Across Repositories Reference56The Book Library Is Reframe's Sole Reading Provider Reference57The Writer Enters by Intention Reference58Open-Turn Mediation Protocol Reference59The Fountain-Coach Git Library and Reframe Project Flow Reference60The Fountain Editor Is the Project Surface Reference61The Fountain Project Round Trip Reference62Reframe Maintenance Control Plane Reference63FountainMaintenanceKit — Portable Swift Maintenance Contract Reference64FountainProjectKit — Durable Fountain Project Custody Reference65The Copilot as Writing Coach Reference66FountainImagePublicationKit — Reframe Image Cloud and Publication Boundary Reference67FountainComposerKit — Remote Attachment Custody and the Composer Boundary Reference6868 — The Reframe E2E Scenario Is the Publication Unit Reference69The Book of Reframe Is a Dual Projection Current publication model7070 — External MIDI2 Control of Reframe Reference7171 — Reframe-to-Reframe Software-Peer Acceptance Reference7272 — MIDI2 Peer Projections and Capacity Admission Reference7373 — The Reframe Scenario Development Cycle Current development cycle74Private Image Prompt History Reference7575 — Scenario Run Ownership and Non-Interference Reference76Beat Movement and the Uncertainty Overlay Reference7777 — The Scenario Runtime Is Swift and MIDI2-Native Reference7878 — Scenario-Driven Development Is Org Infrastructure Current infrastructure7979 — The Default Semantic Manuscript Projection Current product projection8080 — Independent Governance Publication Current publication target8181 — The Universal MIDI2 Command Plane Current MIDI2 migration boundary8282 — Remote MIDI2 Reading Rooms Current collaboration boundary8383 — Conversational Scenario Authoring Is the Development Surface Current authoring boundary8484 — The Reframe Design Mock Is a Governed Projection Current design-reference boundary8585 — Storify Source Auto Reads a Defined Whole Current Storify reading boundary8686 — The Apple-Native Semantic Pipeline Is One MIDI2 Graph Current semantic pipeline refactoring8787 — The MIDI2 Monitor Is the Live Event Mirror Current MIDI2 monitor boundary8888 — CodexKit Is a Governed Codex App-Server Boundary Current CodexKit boundary8989 — The Codex Auth Instrument Is the Copilot Login Surface Current auth-instrument boundary9090 — Independent Security Review Is a Separate Acceptance Boundary Current security-review boundary9191 — The FCIS-KIT Instrument Store Is the Capability Plane Current capability-plane boundary9292 — Fountain Coach Publication Estate: Semantic Domain and CI Governance Current publication-estate boundary93Instrument Creation Is a Governed Promotion Path Current instrument-creation boundary94Credentialed Infrastructure Operations and Provider Adapters Current infrastructure-authorization boundary95FountainStore Is the Headless Linux Persistence Authority Reference96Chapter 96 — SwiftACMEKit Is a Provider-Neutral Certificate Automation Boundary Current certificate-automation boundary97Provider-Neutral Host Bootstrap and Enrollment Reference98Apple-Native Markdown Presentation and Transferable Engraving Rules Reference99Decoupled Manuscript Instruments — Navigation, Source, and Uncertainty Reference100Semantic Scenographer — Think with the Work in Space Current spatial-thinking boundary101TeatroStageEngine Is the Stage — Semantic Scenography Extends It Current stage-engine boundary102Semantic Inference Execution, Session, and Latency Governance Current semantic-execution boundary103FCIS-KIT Semantic Factory and the Wired Instrument Event Stream Current semantic-factory boundary104MIDI2 Event Time, Jitter, and Asynchronous Completion Governance Current event-time boundary105Semantic Scenographer — One Spatial Thought in Reading Order Current spatial-thought boundary106Teatro MIDI2 Monitor — Canonical Runtime Projection Current Teatro monitor boundary107Creating the Canonical Teatro Stage Composition Layer Current Teatro composition boundary108Reframe Is a Swift-Native Cross-Platform Runtime Current portability boundary109NaturalLanguage Measurement Is a MIDI2 Instrument Current semantic-measurement instrument boundary110Three-Run Semantic Drift Is a Governed Measurement Principle Current three-run drift boundary111Evidence Cohorts Are the Publication Units of the Fountain Coach Estate Current evidence-publication boundary112Skill and Maintenance Capabilities Are Kit-Owned Reference113Governance Becomes an Executable Scenographic Policy Current scenographic-policy boundary114Server-Side Semantic Proposals — Mac and Linux as One Reframe Runtime Reference115Semantic Browser Is a Governed MIDI2 and FountainStore Instrument Reference116116 — FountainStore-Owned Estate Edge and ACME Promotion Current estate-edge boundary117117 — FountainStore Snapshot Export and Git Recovery Projection Reference118118 — European Cybersecurity Profile: Authority, Continuity, and Recoverability Current cybersecurity profile119119 — The Scenario Pipeline Factory Reference120120 — The Internal Triadic Peer Dialogue Reference121121 — The Dynamic MIDI2 Instrument Factory Current dynamic-instrument boundary122122 — The Governed Semantic Transformation Instrument Reference123Commands Must Be Legible to Reasoning124MIDI2-Timed WebKit Transitions125The Store Publication Graph126The Fountain Coach Organization Web Projection127The Estate Template Is the Publishing Path128The Deployed Estate Is a Read-Only WebKit Mirror Authority129Native Animated SVG Is a Governed Publication Projection130Human–Machine Scenario Naming Is a Governed Identity Boundary131Remote SecretStore Authorization and Approval Sessions132Reframe AudioUnit as an AUv3 Estate Instrument Current133Csound AUv3 Is a Fountain Instrument Boundary Current134EstatePublisher Is the Publication Authority Current135Reframe iPad as a Scenario-Driven Creative Host Current136Reframe Web, Native, Headless, and Audio Runtime Boundary Current137Teatro Web Is Reframe's Governed Materialization Surface Current materialization boundary138Ear Is the Web Audio Graph's MIDI2 Listening Boundary Current listening boundary139Owner Trust Root, SecretStore Custody, and Recovery Current owner-trust boundary140EstatePublisher Is Codex’s Governed IP-Network Topology Mutator Current topology boundary141Each Joining Machine Is a Governed MIDI2 Instrument Current chapter142FountainAuthKit: Fountain Coach Is Its Own Governed OAuth/OIDC Authority Latest chapter143Simplicity Is Key: One Bootstrap, One Trusted Session Latest chapter144Fountain Media Service Is the Governed Media Plane Latest chapter145One Estate, One Publication State: EstatePublisher and Reframe as a Governed Semantic Browser Latest chapter146Local FountainStore, Remote Caddy: The Production Static Estate Latest chapter147Local Route Materialization: EstatePublisher Preview Before Check-In Latest chapter148Production Runtime Nodes Are Artifact-Only Latest chapter149Remote CodexKit: Reframe and Codex Meet as Governed MIDI2 Peer Instruments Latest chapter150One MIDI2 Instrument Plane, Multiple Governed Transports Current transport boundary151Csound Teatro: Speaking Sound in Space Latest chapter152The Host Is the Instrument Latest chapter153Domain Admission and Edge Binding Are Separate Governed Capabilities Latest chapter154Domain-Neutral Local-Model Reasoning Testing Latest chapter155The Matrix and EstatePublisher Are One Governed REST Projection156FCIS 156 — The Writer Never Operates EstatePublisher