These documents describe the repository as it stands. History, where it is needed, is a pointer rather than a chapter: the pre-rewrite tree is archived on the golden-reference tag (mirrored at archive/golden-reference), the calls the rewrite made are dated records under decisions/, and the behavioral differences accepted against the archived reference are decision 18.

Read in this order to learn the system: format.md is the centre, authoring.md is how a volume comes to be, app.md is what serves it, render-seam.md and analysis.md are what pictures it, and decisions/ is why any of it is shaped this way.

The documents

Document	What it is
`format.md`	Normative native schema-bundle spec: semantic graph, typed blocks, compatibility, release ordering, validation, and install.
`format-v3.md`	Historical specification for the retired document-shaped format; current readers do not install it.
`authoring.md`	The single-manifest authoring contract: plan, capture, observe, assemble, compile, publish, and workbench handoff.
`semconv/REGISTRY.md`	The attribute vocabulary, generated from `spec/registry.yaml`; `spec/gen`'s own test holds the committed copy up to date.
`generate.md`	Historical generate pipeline retained for fixture migration and corpus tests.
`enrich.md`	Historical enrichment pipeline plus the current maturity score.
`analysis.md`	The cell-system contract: the eighteen methods, coordinates and continuity, the `Ground` descriptor, the plan order, the style tokens. §9 is the "add a third system" checklist.
`app.md`	The hypermedia application: routes, the session record, regions and partials, the state island, the hostenv contract and the three-host story.
`render-seam.md`	The brief for rewriting `render/` blind: the scene description, the standing set, the chart, the globe, the diagnostics duty. §10.1 names what the document does not carry.
`workbench.md`	The operator's surface: its pages, its operations, the operation runner as a consumable library, and the safety properties.
`snapshots.md`	The reusable scheduled-build workflow a city runs over its own data, and the one-time setup it needs.
`testing.md`	The whole test surface: `make test`, `make test-e2e`, `make corpus-smoke`, what tests are made of, where they live, and the bar for a new one.
`releasing.md`	Native macOS, Linux, and Windows packaging, signing inputs, file associations, and the draft-first publication transaction.
`stamps.md`	What a build stamp is a promise of, why it cannot be recomputed from a bundle, and what is enforced instead.
`logging.md`	The one event stream: levels, the shared attribute keys, handler and flag conventions for the CLI and the browser.
`decisions/`	Dated records of the calls that shaped all of the above, each with its context and consequences.