decision-capture

To create a traceable decision record, you formalize the decision or deviation into a structured DEC record with frontmatter metadata. This record links upstream triggers to downstream documents, ensuring full auditability for governance workflows.

A deviation protocol records formal deviations when implementation diverges from blueprints or work orders. It links the deviation trigger to affected documents, capturing the context and ensuring the record is cross-linked for downstream governance audits.

Decision records ensure traceability by using frontmatter metadata and cross-linking to connect upstream triggers with downstream affected documents. This structured linking mechanism guarantees that every formal decision or deviation is auditable.

No, you can log direct decisions that change requirements or strategy independently. You only need existing blueprints or work orders when using the deviation protocol to record formal divergences during implementation.

Use a deviation record when implementation diverges from an existing blueprint or work order, linking the trigger to affected documents. Use a direct decision record when logging new decisions that change requirements or strategy independently.