---
name: record-decision
description: Record an approved, durable decision in Decision Log with rationale and provenance. Use only after a decision has actually been made; do not use for drafts, tasks, notes, or meeting transcripts.
---
# Record an approved decision

Use Decision Log when an approved choice must remain retrievable with its rationale, actor, evidence, and later supersession history.

## Preconditions

- Confirm a decision was made and identify the approving human or agent actor.
- Separate the decision from discussion, proposals, tasks, and unresolved questions.
- Gather concise decision text, rationale, scope, and source evidence.
- Check whether this changes an existing decision. If so, supersede it; never overwrite it.

## Procedure

1. Retrieve the current decision for the same decision key or scope.
2. If no prior decision exists, call the create-decision MCP tool or the corresponding REST operation.
3. If a prior decision changes, call supersede-decision and state why.
4. Attach available source provenance without copying secrets.
5. Return the new decision identifier and whether it is current.

## Safety

Do not silently activate AI-extracted candidates. Do not claim approval, evidence, or actor identity that was not supplied. Treat credentials as secrets and follow server authorization errors.