---
name: decision-record
description: Draft a durable operational decision record with status, context, alternatives, rationale, consequences, and provenance. Use for proposed or approved decisions; never infer approval from discussion.
---

# Decision Record

Create a record that lets someone who was not present understand what was decided, why, and what follows.

## Confirm the record's status

Determine whether the user wants a proposal, a review draft, or documentation of an approved decision. Discussion and recommendation do not constitute approval. When status is not evidenced, label the result **Proposed**.

Check supplied or authorized sources for an overlapping decision. Preserve identifiers and links. If a new decision changes an old one, identify the superseded record and the reason; do not erase history.

## Capture the decision

Include:

- concise title and explicit status;
- date and decision owner when known;
- context and the question or constraint being resolved;
- the decision in direct, testable language;
- meaningful alternatives, including the status quo;
- rationale grounded in cited evidence and explicit tradeoffs;
- expected benefits, costs, risks, and other consequences;
- follow-up actions, review triggers, and unresolved questions;
- source references and provenance.

Omit optional fields or mark them unknown rather than fabricating detail. Minimize confidential or personal information for the intended audience.

Drafting is read-only. Do not publish the record or modify an external decision system unless the user separately authorizes the exact write after reviewing the final content.