Architecture Decision Records

adr/ contains durable decisions that should remain stable across multiple implementation cycles.

Use an ADR when we need to record:

• service ownership or boundary changes
• deployment or operational safety rules
• data-model decisions that should outlive one feature branch
• workflow requirements that AI workers and human reviewers must follow

Current ADRs:

• ADR-001-document-driven-backend-change-workflow.md
• ADR-002-recon-service-boundary.md
• ADR-003-background-worker-health-must-reflect-forward-progress.md
• ADR-004-settlement-jobs-must-fail-loudly-on-non-delivery.md
• ADR-005-wallet-topology-bucket-ledger-model.md
• ADR-006-observability-baseline.md
• ADR-007-wallet-topology-policy-atomic-activation.md
• ADR-008-coupon-saga-rolling-contract.md
• ADR-009-multi-brand-domain-routed-isolation.md
• ADR-010-agent-balance-single-money-writer.md