Docs hub
Find the right Nexus Origins document before you infer from the shell.
This hub groups the public, architecture, readiness, and operations documents that already govern repo truth. It is a navigation surface, not a live dashboard and not a sovereign control plane.
Public-safe
Use this surface to orient visitors and operators without inventing readiness, live state, or roadmap certainty.
Operator-useful
Active evidence, restart pointers, handoffs, and intake guidance stay grouped so future lanes can restart cleanly.
Conservative by default
The docs linked here are canonical sources. UI presence alone should not be treated as proof of maturity or ownership.
Public overview
Start with the repo boundary and public-shell role
Use these docs when you need the shortest public-safe explanation of what Nexus Origins is, what it is not, and how shell claims should stay disciplined.
Architecture
Read the canonical Forge and trust-boundary docs
These are the main architecture sources for what Forges are, how admission works, and where Nexus Origins stops and sovereign Nexus begins.
Readiness
Check proof, blockers, and safe next lanes
Use readiness docs when the question is not just what a Forge is, but whether it is proven, candidate-stage, or only mentioned in shell context.
Operations
Follow current evidence, ownership, and handoff truth
These docs are for operators and bounded verification lanes. They track active evidence, repo-boundary decisions, and downstream-owned problems without inventing live state.
Restart and intake
Resume work without rediscovery
Use these documents when the goal is to restart a bounded lane, preserve governance, and avoid rebuilding context from memory.
Next step
Use the docs hub to orient first, then choose the right surface.
Start with the README if you need the repo boundary, the architecture index if you need Forge truth, and the live evidence index if you need current operational status and restart pointers.