Reference
Generated facts for the refactor (#170, under #167). These pages answer questions whose answers move
with code. Each starts with <!-- generated: … -->; test/docs-gate.test.ts runs its generator and
fails when the checked-in page differs. Regenerate with bun <generator> > <page> and review the diff.
| Page | Question answered | Generator |
|---|---|---|
| HTTP routes | What routes exist; what crosses each; what can build, mutate or log? | scripts/docs/routes.ts |
| Observations | What produces every observation kind; what the browser derives; who consumes it? | scripts/docs/observations.ts |
| Core exports | What @enso/core exposes; is it wire, host contract, policy or node-only; who imports it? |
scripts/docs/core-exports.ts |
| Environment and configuration | What enters by environment, committed config, .enso/ path or harness manifest; when is it read? |
scripts/docs/env-and-config.ts |
| Code-local decisions | Which leading source headers record a decision, which issues own it, and what sentence opens it? | scripts/docs/decisions.ts |
| Verification inventory | What every gate enforces; what ratchets; which reusable test double drives which seam? | scripts/docs/verification-inventory.ts |
Generated does not mean inferred. Where behavior cannot be derived safely, a generator carries an
explicit checked metadata record. Two contracts, and the difference is deliberate. In decisions,
env-and-config, routes, core-exports and verification-inventory, an UNCLASSIFIED row means
the detector and the metadata have stopped agreeing, so the page would be wrong: generation
fails, and there is no page to check in. In observations, an unmapped kind means the repository
grew an observation the adapter does not handle: the generator prints it as an UNCLASSIFIED
cell and names it under Diagnostics, because the inventory’s job is to survey what exists — see
the observation seam. Either way UNCLASSIFIED is never an omitted row.
Generators are deterministic: sorted rows, no timestamp, machine path, Git state, network or GitHub
call.
Read the reference after the relevant seam page: a seam explains the boundary and pivot cost; the reference lists the current facts at that boundary.