Corpus front door
The corpus front door is an executable atlas of the interior: every assertion resolves to an exact retained object, and every retained object is either reachable from a declared entrance or explicitly classified.
This is a generated atlas, not a claim of truth or completeness. Its machine-readable twin is 0 ; its declared roots live in 1 . Drill down from those roots to exact corpus objects, then use the canonical file manifest for path, byte and hash identity.
Authority boundary. This atlas reports repository structure and declared epistemic surfaces. It does not promote claims, replace source evidence, or grant publication, corpus-admission, runtime, or deployment authority.
Coverage. 16 declared roots across 4 routes; 6593 retained inventory objects; 5225 objects reachable through local links; 6593 objects explicitly classified; 0 unclassified. The atlas passes its structural checks.
Understand the present claim
Recover the corpus's explanatory order, current synthesis, vocabulary, and limits before following historical branches.
| Root | Status | Authority | Provenance |
|---|---|---|---|
| reading-contract | canonical interpretation | controls explanatory order; does not establish empirical truth | maintained corpus source |
| current-synthesis | current reader synthesis | summarizes typed results and open boundaries; cited evidence remains controlling | maintained corpus synthesis |
| explanatory-standard | editorial and reasoning standard | controls presentation discipline; does not promote claims | maintained corpus governance |
| glossary | working vocabulary | defines local usage; underlying claims retain their own status | maintained corpus source |
Find bounded work
Enter through a role, live topic, target, experiment, or detector rather than through chronology.
| Root | Status | Authority | Provenance |
|---|---|---|---|
| role-map | task navigation | routes readers to controlling objects; grants no research authority | maintained corpus source |
| open-topics | maintained research queue | describes live topics; Mission Control remains authoritative for scheduling | frontier-physics target programme |
| target-set | maintained target atlas | maps targets and gates; does not establish a physical result | frontier-physics target programme |
| experiment-atlas | experiment design atlas | records proposed discriminators and controls; does not report completed experiments unless cited | frontier-physics target programme |
Inspect claims and evidence
Move from a statement to its status, certificate, data, counterevidence, and reproducibility boundary.
| Root | Status | Authority | Provenance |
|---|---|---|---|
| evidence-spine | generated structural evidence index | joins exact observed references and marked inferences; does not promote scientific status or widen certificate scope | generated from the canonical manifest and current retained claim text |
| result-ledger | curated result ledger | reader index only; exact claims and certificates remain controlling | generated Edition 3 source |
| verification-guide | verification navigation | routes to executable certificates; a passing certificate has only its declared scope | repository verification layer |
| document-map | accretive provenance ledger | preserves chronology and links; not a standalone current synthesis | append-only claims ledger |
Audit authority and provenance
Inspect the exact inventory, publication boundary, repository history, and stewardship constraints.
| Root | Status | Authority | Provenance |
|---|---|---|---|
| corpus-manifest | canonical file inventory | records canonical paths, sizes, and hashes at its generation point | generated by tooling/audit/auditspin23corpus_manifest.mjs |
| publication-authority | publication authority contract | defines the repository/Claimipedia boundary | Claimipedia integration source |
| repository-proposal | repository governance record | describes repository structure and transition history | corpus governance source |
| license | license | controls reuse terms within its stated scope | repository root |
Minimum viable profiles
A minimum dataset is capability-specific, not one universal subset. The declared core contains the named roots and explicit resolution/execution dependencies. The discoverable closure follows every local Markdown link and is an upper bound for browsing, not a packaging dependency graph: citations, backlinks and navigation are deliberately richer than what execution requires. Displayed sizes are observed working-copy bytes so newly generated control surfaces remain visible; canonical bytes and unknown-manifest counts remain separate in the machine record.
| Capability | Roots | Declared core files | Observed core bytes | Discoverable files | Observed discoverable bytes |
|---|---|---|---|---|---|
| Interpret faithfully | reading-contract, current-synthesis, explanatory-standard, glossary | 4 | 212.7 KiB | 5418 | 83.0 MiB |
| Choose one bounded research task | reading-contract, role-map, open-topics, target-set | 6 | 158.7 KiB | 5418 | 83.0 MiB |
| Audit claims, provenance, and authority | reading-contract, evidence-spine, result-ledger, verification-guide, document-map, corpus-manifest, publication-authority | 11 | 15.1 MiB | 5418 | 83.0 MiB |
| Design a discriminating experiment | reading-contract, current-synthesis, experiment-atlas, target-set, verification-guide | 8 | 322.9 KiB | 5418 | 83.0 MiB |
These profiles are map-only candidates, not admitted packages. Before extracting one, add the selected capability's exact runtime, provenance and falsification dependencies, then independently qualify the derived artifact. Use the full sealed or canonical corpus when custody, exact release reproduction, history, or unknown future questions matter.
Interior zones
Reachability measures what the declared entrances actually expose through local links. Classification accounts for the rest without pretending that navigation alone proves relevance. A zero in the reachable column is therefore a map defect to inspect, not automatic permission to delete.
| Zone | Objects | Reachable | Canonical bytes | Explicit classification |
|---|---|---|---|---|
| automation | 1 | 0 | 1.7 KiB | repository workflow automation |
| claims | 1576 | 1567 | 15.5 MiB | append-only claim and provenance ledger |
| corpus-navigation | 11 | 11 | 120.1 KiB | canonical corpus navigation, vocabulary, and reading rules |
| evidence | 825 | 664 | 19.7 MiB | data, figures, and retained observations |
| generated-publication | 9 | 1 | 137.0 KiB | generated deployable reading surfaces |
| governance | 2 | 1 | 7.7 KiB | repository and publication governance |
| integrations | 275 | 5 | 19.9 MiB | application and publication boundary packets |
| legal | 2 | 2 | 54.0 KiB | legal notices and policy |
| programmes | 1055 | 778 | 41.6 MiB | bounded research programmes, registers, and closure work |
| reader-editions | 533 | 340 | 6.3 MiB | curated reader-facing editions |
| registers | 13 | 6 | 55.8 KiB | machine-readable inventory, state, and audit records |
| repository-front-door | 8 | 5 | 27.7 KiB | root navigation, machine retrieval, stewardship, contribution, legal, and text-identity surfaces |
| syntheses | 6 | 6 | 318.6 KiB | current and thesis-scale interpretive surfaces |
| tests | 15 | 3 | 99.7 KiB | repository and publication invariants |
| tooling | 130 | 19 | 10.5 MiB | generation, audit, migration, and publication utilities |
| verification | 2132 | 1817 | 6.9 MiB | executable certificates and verification navigation |
Structural contract
The generator fails its admission check when a declared root is missing, lacks epistemic status/authority/provenance, contains a broken direct local link, references an unknown profile root or required path, or leaves an inventory object unclassified. Broken links deeper in the closure remain visible in the machine diagnostics because historical material can contain intentionally unresolved or externally restored references.
Regenerate or check from the repository root:
node tooling/indexing/generate_corpus_front_door.mjs --write
node tooling/indexing/generate_corpus_front_door.mjs --check
node --test tests/repository/corpus_front_door.test.mjs