Purpose
A writing system with evidence
Reframe is not a generic chat assistant or an autonomous publishing system. It provides governed operations around a writer's work and explains what each operation can establish.
Public technical publication
What Reframe can do.
The Book of Reframe is a reviewed projection of the development runtime: commands, governed capabilities, evidence, and the boundary of what the App is allowed to promise.
Source policy: public projection · governance · runtime implementation is private
System overview
What is Reframe?
Reframe is a writer-facing studio for turning a manuscript into a structured, inspectable working space. It helps a writer read, question, reshape, and compose from source material while keeping decisions, uncertainty, and system effects visible.
System boundary
Source, reasoning, action
The runtime reads source material, reasons over the current working state, and dispatches owned capabilities. Persistent project state and operational proof remain separate from conversational wording.
Reader contract
Inspect before you trust
The Book documents the development surface as a set of checked projections: command inventory, capability registry, live acceptance, and named-build release status.
Operating model
From source to checked result.
Reframe separates the writer's material, the reasoning that interprets the current state, the operation that acts, and the evidence that makes the result reviewable.
- 01 · SourceA manuscript and its confirmed working context.
- 02 · ReadingStructure, questions, and uncertainty are made inspectable.
- 03 · CapabilityA governed operation is selected with its policy and preconditions.
- 04 · ResultThe action produces a visible, persisted application result.
- 05 · EvidenceAX, visual, telemetry, and store proof establish what happened.
At a glance
Four projections, four questions.
The command inventory, capability registry, live-accepted evidence, and named-build release surface answer different questions. This site keeps those questions distinct.
Values are generated from the checked release projection for no-released-build, not from runtime UI text.
How to read this
Claims stay attached to evidence.
Available is not the same as live-accepted. A command entry is not an independent capability. Live-accepted is not automatically released. The source files record those distinctions.
Start with commands
The runtime catalog is the broad development inventory. It includes aliases, compatibility routes, conditional entries, and maintainer tools.
Open the command atlas →Check capabilities
The governed registry is narrower. It records adapters, policy, proof, telemetry, AX, and live-acceptance status.
Open the capability atlas →Check release status
No named distribution build is recorded in this snapshot. The release allow-list is therefore empty.
Open the release surface →