---
type: atlas-artifact
artifact_type: decision
project: "{{project}}"
status: draft
owner: "{{owner}}"
created: {{date}}
updated: {{date}}
source: "{{source}}"
reviewer: "{{reviewer|TBD}}"
tags: [atlas, artifact, decision]
---
# Decision: {{title}}

Parent project: [[{{project}}]]
Source: {{source}}
Supersedes: {{supersedes|N/A}}

## Decision summary

One sentence stating the decision.

## Context

Why this decision is needed now; include constraints and evidence.

## Options considered

| Option | Pros | Cons | Notes |
|---|---|---|---|
| A |  |  |  |
| B |  |  |  |
| C |  |  |  |

## Decision

Chosen option and rationale.

## Consequences

- Positive consequences: ...
- Tradeoffs/costs: ...
- Follow-up tasks: ...

## Revisit trigger/date

Revisit when ... or by YYYY-MM-DD.

## Owner

Owner responsible for revisiting and maintaining this decision.

## Decision-specific review checklist

- [ ] Decision is explicit and not just context.
- [ ] Alternatives and tradeoffs are fairly represented.
- [ ] Revisit trigger/date is present.

## Universal reviewer checklist

Before accepting this artifact, verify:

- [ ] Clear owner, status, date, source, and next action.
- [ ] Saved in the correct durable destination and named using the convention.
- [ ] Links back to the relevant project note and source task/issue/PR/session/incident.
- [ ] Claims are backed by evidence links, command output, or labeled assumptions.
- [ ] Risks, rollback, recovery, or revisit triggers are documented where relevant.
- [ ] No secrets, tokens, raw PII, private keys, or unredacted credentials are included.
- [ ] A new specialist can understand the artifact without rereading the whole chat.
