documentation-and-adrs

To write an architecture decision record, draft your file in docs/decisions/ADR-XXX-Title.md conforming to ADR templates, then reference it from relevant OpenSpec or main contract documentation to ensure traceable governance and preserve durable decisions.

Keeping documentation navigation aligned with OpenSpec changes requires docnav synchronization guidance, outlining how to keep doc navigation, OpenSpec changes, and contract surfaces aligned to maintain durable architectural decisions and contextual documentation.

You need inline documentation when providing guidance on when to add inline notes, reference ADRs, and link related docs. A full ADR is needed to capture rationale, constraints, and trade-offs for long-term durable architectural decisions and governance.

Link OpenSpec changes to architectural decisions by conforming to ADR templates, linking OpenSpec changes, and referencing schemas, examples, and tests within your documentation to ensure traceable governance across the project context.

Yes, you can use ADR templates to capture durable architectural decisions and essential project context, applying ADR drafting and inline documentation guidance to guide future engineers and AI agents through architectural changes and governance.

Docnav synchronization matters because it outlines how to keep doc navigation, OpenSpec changes, and contract surfaces aligned, ensuring that durable architectural decisions and contextual documentation remain traceable and accessible for future engineers and agents.