Specs

specs/ holds dated feature and migration specifications grouped by topic.

Always check the document's Status before treating it as current truth. Superseded specs may remain here only while they still help active topic discovery. If a stale spec is likely to be mistaken for current design truth, move it to docs/reference/history/ and leave a topic README behind.

Use a spec when:

• a change spans multiple services
• compatibility requirements must be frozen
• acceptance criteria need to be explicit before implementation

Current topic groups:

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