ADR Lifecycle and Index
Lifecycle
Section titled “Lifecycle”Every ADR uses same frontmatter fields:
status: decision lifecycle:proposed,accepted,deprecated, orsuperseded.idandscope: stable decision identity anddomain,platform, orcross-cuttingownership class.contexts,terms,authorities, andgaps: stable ids resolved throughapps/docs/ontology.json.technicalOwner: platform fallback owner only; never a substitute for domain ownership.date: original decision date.lastReviewed: latest architecture/evidence audit date.supersedes: prior ADR ids replaced by this decision.supersededBy: current successor ADR id, ornull.implementation: observed evidence state:not-started,partial,implemented, orhistorical.
Decision status and implementation state are independent. accepted means
target remains current; it does not mean every path is implemented. partial
requires linked code/config evidence plus named gaps. Dated stage or E2E results
are historical snapshots unless rerun against current revisions.
ADR references use exact ADR-### format. Supersession is bidirectional: old
ADR names successor in supersededBy; successor lists old ADR in supersedes.
Superseded ADR text stays available as history.
| ADR | Decision | Status | Implementation | Relationship |
|---|---|---|---|---|
| ADR-001 | Repository ownership boundaries | accepted | implemented | - |
| ADR-002 | Backend DDD and feature boundaries | superseded | historical | superseded by ADR-029 |
| ADR-003 | Colocated test naming | accepted | partial | - |
| ADR-004 | pnpm-only JavaScript tooling | accepted | implemented | - |
| ADR-005 | uv-only Python tooling | accepted | implemented | - |
| ADR-006 | Supabase only | superseded | historical | superseded by ADR-018 |
| ADR-007 | Starlight documentation surface | accepted | implemented | - |
| ADR-008 | Strapi content administration | superseded | historical | superseded by ADR-019 |
| ADR-009 | Migration evidence control loop | accepted | partial | - |
| ADR-010 | Service-use contract render source | accepted | partial | - |
| ADR-011 | Booking service-term side-effect assembly | accepted | partial | - |
| ADR-012 | Frontend static Atomic Design shell | accepted | partial | - |
| ADR-013 | Settlement component acknowledgement | accepted | partial | - |
| ADR-014 | Settlement data-room readiness | accepted | partial | - |
| ADR-015 | Refreshable preview E2E runners | accepted | implemented | - |
| ADR-016 | Branch settlement board projection | accepted | partial | - |
| ADR-017 | Financial decision authority | accepted | partial | - |
| ADR-018 | Platform authority boundaries | accepted | partial | supersedes ADR-006 |
| ADR-019 | Directus content administration | accepted | partial | supersedes ADR-008 |
| ADR-020 | Reservation payment obligation and actor snapshot | accepted | partial | - |
| ADR-021 | Family-sponsored reservation contract acceptance | accepted | partial | - |
| ADR-022 | Bounded on-demand Starlight runtime | accepted | implemented | - |
| ADR-023 | Project-owned remote image build | accepted | implemented | - |
| ADR-024 | Reservation care-history read model | accepted | implemented | - |
| ADR-025 | Payment-change secure handoff | accepted | implemented | - |
| ADR-026 | Payment cash-receipt handoff snapshot | accepted | partial | - |
| ADR-027 | Payment refund settlement reversal | accepted | partial | - |
| ADR-028 | Authenticated mother booking submission | accepted | partial | - |
| ADR-029 | Layer-first context feature slices | accepted | partial | supersedes ADR-002 |
| ADR-030 | Branch onboarding and own-profile authority | accepted | partial | - |
| ADR-031 | Server-authoritative customer reservation creation | accepted | partial | - |
| ADR-032 | Customer reservation contract acceptance evidence | accepted | not-started | - |
| ADR-033 | Strict sequential actor workflow acceptance | accepted | implemented | - |
| ADR-034 | Mother account identity, profile, and consent authority | accepted | partial | - |
| ADR-035 | Customer authenticated session and account-link proof | accepted | partial | - |
| ADR-036 | Customer session recovery audit | accepted | implemented | - |
| ADR-037 | Reservation booking party authority binding | accepted | implemented | - |
Audit Rule
Section titled “Audit Rule”Update implementation only with pinned repository evidence or dated runtime
evidence. Never infer deployment, provider health, or end-to-end behavior from
file presence alone.