Nexus Origins is the public portal for the Forge network.
It is where people orient themselves, review what is publicly available, and enter safe evaluation surfaces. Sovereign control, state, and operator workflows remain in Nexus core.
Shell overview
Professional entry points, without pretending the whole system is public.
Nexus Origins should help visitors understand where to start, what is live today, and how public evaluation differs from internal Forge operations.
Advisory by design
Public experiences in Nexus Origins are guides and sandboxes. They do not operate sovereign Nexus state on your behalf.
Evidence stays inspectable
This shell exists to expose status, pathways, and context clearly enough for people to review what is live and what is still being shaped.
The hub stays honest
Only registry-backed Forge paths are presented as live entry points. Internal and developing work remains clearly separated from public access.
Status surface
What is public, what is candidate, and what stays operator-facing.
Nexus Origins can acknowledge the current Forge landscape without turning shell copy into a fake status dashboard. These categories are conservative, registry-aware, and meant to help visitors understand boundaries before they click deeper.
How to read this
The shell can reflect surface categories and registry-backed visibility. Canonical readiness, admission gates, and architecture truth still live in the repo docs and indexes.
Public surfaces
Registry-backed public shell entry points currently exposed for bounded evaluation.
Candidate surfaces
Mentioned or developing Forge paths that remain candidate-stage until docs and gates say otherwise.
Operator-facing
Shell-visible but non-public surfaces that should be treated as operator context, not open access.
Docs hub
One hub for architecture, readiness, operations, and restart guidance.
The public shell now has a dedicated navigation surface for the documents that govern repo truth. Use it when you need the right source faster than you need another homepage paragraph.
Why it matters
Public-safe orientation and operator restart work now live in one reachable place. The hub improves discoverability without turning the shell into a live control surface.
README-level repo role, public-shell boundaries, and copy guardrails.
Forge model, reference truth, and architecture reading order.
Proof, blockers, missing gates, and safe next bounded lanes.
Evidence index, repo-boundary handling, and restart-safe intake guidance.
Public entry points
Public-access Forge surfaces
These are the registry-backed routes currently exposed through the shell. If a Forge is not listed here, it is not being presented as a public entry point. The current public preview still opens through the alpha surface while route naming catches up.
Operator context
Internal and developing Forges stay visible, but clearly bounded
Some Forges are already part of the wider Nexus system but remain operator-facing or otherwise non-public. The shell can acknowledge them without implying public readiness.
Guide layer
Archie gives the shell a human voice.
Archie is the orientation layer for Nexus Origins: a calm guide that helps visitors understand what they are looking at, where they can safely go next, and what still belongs to operator-only systems.
The role of the shell is clarity, not mystique. If a surface is experimental, internal, or advisory-only, the presentation should say so plainly.
Next step
Start with the live public surface, then review the limits.
The strongest public impression comes from a shell that is navigable, explicit, and measured about what is currently available. Explore the live Forge path, then read the guardrails that shape it.