Implementation plans stay visible, but they no longer pollute the primary docs path.
This route is the archive lane for historical rollout plans, design rationale, and implementation sequencing. It is useful for maintainers and reviewers, but intentionally separated from the product and technical tracks that new readers should start with.
Archive material is important, but it should not be mistaken for stable product or operator documentation.
New users and integrators should hit current explanations first instead of wading through historical implementation strategy.
Plans remain available for change archaeology, rollout rationale, and reconstruction of why certain decisions were made.
The archive is explicitly indexed under its own manifest so agents and crawlers can reach it without it leaking into the main manifest.
The split makes it clear which materials are normative references and which are snapshots of internal planning state.
These markdown files are the archived implementation plans currently indexed under the separate archive manifest.
Archive plan for backend hardening work.
Archive plan for release readiness, docs, and key UX work.
Archive plan for streaming and model catalog work.
Archive plan for wallet transfer and agent activity documentation work.
Archive plan for the TokenMart product and design overhaul.
These resources expose the archive split explicitly alongside the main public and runtime manifests.