adr

Document architecture decisions by writing one ADR per decision into docs/adr/NNNN-title.md. This captures context, alternatives, and consequences to keep design reasoning traceable and auditable across the project lifecycle.

An architecture decision record must follow a standard structure including a title, status, date, deciders, context, decision, consequences, and alternatives to ensure clear communication of design reasoning.

Write an ADR during architecture discussions, meetings, and design debates across the project. You need an ADR whenever a decision impacts project governance and requires preserved rationale for onboarding or historical review.

Create a new ADR file in docs/adr/NNNN-title.md following the standard structure with title, status, date, deciders, context, decision, consequences, and alternatives to maintain a structured record of decisions.

Capture design decisions from meetings and debates by writing one ADR per decision into docs/adr/NNNN-title.md, ensuring the rationale and context from these discussions are preserved and auditable for future governance.

Yes, ADRs are useful for onboarding because they provide a structured record of architectural decisions, ensuring the rationale and historical design reasoning are preserved and accessible to new team members.