This page is the documentation front door. Choose the path that matches what you are trying to do instead of beginning in the experiment archive.
| Audience | Read in this order |
|---|---|
| New user | Project README -> Deployment quickstart -> Concepts |
| Application integrator | Architecture -> Registry specification -> Threat model |
| Cake author | Cake authoring -> Registry specification -> Contributing |
| Scientific reviewer | Project status -> Claims -> Phase status -> Verification and limits |
| ABI artifact integrator | External artifact handoff -> Project status |
| Contributor or coding agent | Repository map -> Contributing -> AGENTS.md |
- Project status distinguishes the sealed release from current post-release development.
- Concepts defines core, host, cake, registry, router, ABI, and evidence terminology.
- Architecture maps concepts to implementation modules.
- Deployment quickstart contains commands that can be exercised from a checkout.
- Claims maps bounded claims to evidence.
- Verification and limits states what has and has not been established.
- Repository map explains the source, evidence, artifact, configuration, and historical-research trees.
When documents disagree, use this order:
- immutable Git tag and content hashes;
moonshot/campaign.yaml, frozen contracts, and phase seals;- raw observations under
results/moonshot/; - generated certificates derived from those observations;
- current canonical documentation listed above; and
- historical research notes.
Prose never promotes a scientific claim by itself. Current development code never inherits a tagged-release claim merely because an interface name is similar.
LayerCake preserves unsuccessful branches and superseded experiments as part
of its scientific record. Files named NORTHSTAR_*, BYTE_*,
BREAKTHROUGH_*, older training plans, and docs/MOONSHOT_V2_REPORT.md are
historical unless a current certificate explicitly imports their evidence.
Use the repository map to find them.