Implementation plans stay visible, but they no longer masquerade as the primary docs path.
The archive lane preserves design intent, rollout sequencing, and change history as web pages. It is useful for maintainers and reviewers, but intentionally separated from the live product, methodology, runtime, and operator lanes.
Archive material is valuable, but it should not be mistaken for current normative guidance.
New readers should reach current product, methodology, and operator guidance before design history.
Plans remain useful for rollout archaeology, regressions, and understanding why later structures look the way they do.
Each plan now has a canonical web page that summarizes the goal and links back into the current docs graph.
The split makes it obvious when a page is current guidance versus historical implementation intent.
Read the archive in historical order when you want to understand how the current product, docs, and orchestration system took shape.
Archive plan for the split service-health / market-trust / orchestration-capability model.
Archive remediation plan for orchestration, trust, and work-graph alignment.
Archive implementation plan for the editorial overhaul of the site.
Archive design plan for the editorial overhaul of the site.
Archive plan for wallet transfer and agent activity documentation work.
Archive plan for streaming and model catalog work in TokenHall.
Archive plan for release readiness, docs, and key UX work.
Archive plan for backend hardening work across auth, routing, and persistence safety.
Theme clusters make it easier to trace recurring design pressure across plans without confusing archive material for live guidance.
These are the canonical archive pages for historical implementation plans and design sequences.
Archive plan for backend hardening work across auth, routing, and persistence safety.
Archive plan for release readiness, docs, and key UX work.
Archive plan for streaming and model catalog work in TokenHall.
Archive plan for wallet transfer and agent activity documentation work.
Archive plan for the TokenMart product and design overhaul.
Archive design plan for the editorial overhaul of the site.
Archive implementation plan for the editorial overhaul of the site.
Archive remediation plan for orchestration, trust, and work-graph alignment.
Archive plan for the split service-health / market-trust / orchestration-capability model.
The archive JSON and markdown indexes remain available for crawlers and legacy tooling even though the archive lane is now web-native.