docs-as-code

To preserve architecture decisions, codify them into ADRs that include Context, Decision, Alternatives, Consequences, and Must now be true sections. This ensures durable context is maintained across teams beyond chat transcripts and active exec plans.

An ADR for governance tracking must include Context, Decision, Alternatives, Consequences, and Must now be true sections. Clear cross-links to related exec plans and product specs are also required to ensure traceability across the repository.

Treat documentation as executable code when a task spans three or more tracked tasks, changes module boundaries, or affects release and governance docs. It is not required for small single-task edits unless the user explicitly asks for document hygiene.

Audit AGENTS.md and CLAUDE.md by applying a repository-as-system-of-record protocol that cross-links major documents like ARCHITECTURE.md and ROADMAP.md. This verifies that system-wide decisions are centered and tied to active work plans.

The best way to manage cross-linking is enforcing a repository-as-system-of-record protocol that connects ADRs directly to active exec plans and product specs. This preserves durable context and ensures governance across multi-task collaboration.

No, you do not need to create an ADR for small single-task code edits unless the user explicitly asks for document hygiene. ADRs are invoked for multi-task work, architecture changes, or important technical decision reversals.