Reference index¶
Reference material is factual, terse and — where possible — generated from evidence rather than written by hand.
Glossary¶
Terms used consistently across this site, with the component that owns each definition.
Capability register¶
Generated from the evidence packets. Every documented capability, its status token and its evidence anchors, in one table.
API and schema navigation¶
Generated from the backend's own route tables at the pin. Two API generations, which operations are deferred, and which routes are deliberately withheld.
Health and status contract¶
The public half of the health model: what liveness, readiness and status surfaces mean, and what they deliberately do not tell you.
Venue capability matrix¶
Generated per venue. Keeps upstream adapter presence, ONIX profile presence, focused test conformance, deployment and production observation apart instead of collapsing them into one word.
What "generated" means here¶
Three pages in this section are produced by a tool rather than typed.
The capability register is built from the machine-readable evidence packets that the frontend, backend and native documentation lanes each produce. Every row carries the status token, the availability token and the evidence anchors the originating lane recorded, and each claim carries a falsifiable check — an exact command an independent reviewer can run to try to disprove it. The register is deliberately a filtered view: each claim carries an explicit publication decision, a claim with no decision fails the build, and claims whose subject is withheld from this site do not appear.
API and schema navigation and the venue capability matrix are rendered from surfaces extracted once from the application repositories at the recorded pins and vendored here. That vendoring is deliberate: it means this repository builds and verifies on its own, with no application source present, in the same way the 61-row classification input is vendored rather than fetched.
The build verifies that every generated page still matches its inputs. If an evidence packet or a vendored surface changes and the page is not regenerated, the drift check fails and the release stops — and it checks before anything is regenerated, so the drift is still there to be found. This is the same mechanism that keeps navigation, the redirect map and the page census in agreement; see the documentation platform.
What reference material is not¶
Reference pages do not explain motivation. If you want to know why a boundary exists, read design principles or architecture decisions. If you want to know who is allowed to be right about something, read the authority model.
Evidence and source pins for this page
Verified. Current behaviour, confirmed in source at the pinned commit.
Verified on against the following immutable sources:
onix-docs:manifest/page-route-contract.jsononix-docs:tools/gen_reference.py
Status tokens are defined on the documentation and status model page. Every pin on this site is listed under versions and source pins.