adr

An architectural decision record (ADR) captures critical project decisions to ensure accountability and future auditability. You need an ADR for material decisions within governance workflows that require documented context, alternatives, and formal record.

To document architectural decisions for traceability, file a new ADR under the _decisions/ directory using a fixed structure. The system enforces sections for Context, Decision, Consequences, Alternatives, and Follow-ups, while automated indexing through INDEX.md tracks lifecycle status transitions.

Yes, the ADR system integrates cross-skill with vision, OKR, gates, and meeting minutes to preserve governance context. This integration ensures that architectural decisions remain linked to overarching objectives and governance workflows throughout the project lifecycle.

A fixed structure is required for decision records. The system enforces standardized documents containing specific sections: Context, Decision, Consequences, Alternatives, and Follow-ups, ensuring consistent auditability and preventing custom formats that break governance traceability.

The limitation of fixed structure ADRs is the strict format requirement, which mandates sections for Context, Decision, Consequences, Alternatives, and Follow-ups. This rigidity ensures audit compliance but may not accommodate informal decisions outside material governance workflows.