Plans

plans/ holds dated implementation checklists grouped by topic.

Plans should stay executable and reviewable:

• checklist-oriented
• tied to one spec
• updated as implementation status changes

Always check the document's Status before treating a plan as current. Superseded plans may remain here only while they are still safe to read as context. If a stale plan could be executed by mistake, move it to docs/reference/history/ and leave a topic README behind.

Current topic groups:

• documentation/
• migrations/
• multi-brand/
• recon/
• wallet/
• worker-health/

Plan Status Index

Use this table before acting on any dated checklist. A plan with open checkboxes can still be correct when its status is Active rollout or Backlog; it is stale only when the current status contradicts the served system behavior.

Plan	Status	How to Treat Open Checkboxes
documentation/2026-04-23-rgb-docs-site-implementation.md	Implemented with deferred follow-up backlog	Product/platform follow-ups, not blockers for the docs site
migrations/2026-04-22-admin-v2-route-compatibility.md	Superseded	Historical context only; do not execute
multi-brand/2026-04-27-multi-brand-isolation-plan.md	Active rollout	Current Phase 16 release gates
multi-brand/2026-05-05-event-brand-scoping.md	Completed/superseded by later multi-brand phases	Historical event-scoping context
multi-brand/2026-05-05-phase-4e-dual-read-sunset.md	Completed/superseded by later multi-brand phases	Historical migration context
recon/2026-04-22-recon-service-implementation.md	Implemented with follow-up backlog	Historical cutover plus explicit recon backlog
wallet/2026-04-23-ruby-wallet-split-implementation.md	Active rollout/backlog	Current wallet topology backlog
wallet/2026-05-05-agent-balance-into-wallet.md	Backlog	Future wallet-domain migration
worker-health/2026-04-22-worker-health-and-settlement-hardening.md	Active hardening / partially implemented	Current production hardening context; verify current code before executing remaining checklist items