adr-workflow

Automating the Architectural Decision Records lifecycle involves scaffolding new records, managing status transitions, and maintaining an index. This workflow enforces immutability of accepted records and uses atomic frontmatter mutations for auditability.

Tracking ADR status transitions and maintaining an index is managed through dedicated automation commands. The workflow handles status shifts from Proposed to Accepted or Superseded and automatically regenerates index documentation to keep records synchronized.

Scaffolding a new Architectural Decision Record with automatic numbering is done by running the creation command. This initializes the record using standardized templates and assigns the next sequential identifier automatically.

Enforcing immutability of accepted ADRs is a core constraint of this workflow. Once a decision record reaches the Accepted state, the system prevents direct modification, requiring any changes to be made by superseding the original record.

Resolving refinement-todo entries is handled by linking them directly to accepted Architectural Decision Records. The workflow provides a specific command to map these pending todos to their corresponding resolution records for tracking.

Atomic frontmatter mutations ensure ADR auditability by applying status changes as single, indivisible operations. This prevents partial updates to the document metadata, guaranteeing that the state tracked in git remains consistent and verifiable.