Decision Record Template

What makes a decision understandable later?

A decision-record page preserves why we made a public decision.

Apply this shape when the page job is decision-record.

Frontmatter

type: decision-record
template: decision-record-template
template_url: /playbook/standards/templates/decision-record-template
loop_phase: evolution
level: working

Shape

1. State the decision.
2. Name the context and forces.
3. List options we considered.
4. Explain the call.
5. Name consequences.
6. Set a review or kill signal.

Skeleton

TITLE

Decision: CALL.

## Context

What was true when the decision was made?

## Forces

- Force A
- Force B

## Options

1. Option A
2. Option B
3. Option C

## Decision

What did we choose, and why?

## Consequences

What becomes easier, harder, required, or forbidden?

## Review Signal

What would make us revisit this decision?

Checks

• The decision appears in one line.
• Rejected options stay visible.
• Consequences are concrete.
• Future readers can see why the call was made.

Failure Modes

• The page records the result but not the reasoning.
• The page hides tradeoffs.
• The review signal is missing.

Context

• Page Types - full page-type catalogue.
• Reference Migration Standard - use when a decision moves live references.
• Purpose - keep the decision tied to intent.

Questions

What future confusion should this record prevent?

• What forces made the decision hard?
• Which option did we reject, and why?
• What signal would make us revisit the call?