docs

Template-driven generation maintains reference docs and prevents architecture decisions from going stale by applying standardized templates during creation, audits, and reviews to reflect current project signals.

Structuring architecture decision records and guides requires enforcing one-topic-per-doc with cross-references using @docs links. This centralized, update-friendly workflow prevents guidance from diverging across teams.

Validate cross-references and check documentation freshness through health audits. These audits ensure constancy by verifying cross-references and confirming evergreen docs reflect current architecture, data models, and APIs.

You can integrate ADRs with existing architecture and data model documentation using standard references. The templates facilitate ADR integration and linking with related docs across architecture, APIs, and scripting documentation.

Project guidance diverges across teams without a centralized documentation workflow because docs decay and ADRs go stale. Template-driven generation and cross-reference validation solve this by enforcing consistent updates.