Decision model

Steps

1. 1Choose a stable decisionKey that callers can reuse when the wording changes.
2. 2Record the Decision text and rationale as the meaning-bearing, immutable statement.
3. 3Attach source provenance when evidence is available; do not copy evidence into an editable note.
4. 4Use a DecisionCandidate instead when the proposed meaning still requires review.

CLI from this repository

pnpm decision-log decisions create \
  --key architecture/database \
  --title "Use Postgres for the system of record" \
  --decision-text "Decision data is stored in Postgres." \
  --rationale "Transactions protect append-only writes."

Steps

1. 1Send the stable decisionKey, plus a Project context when the key is scoped to a Project.
2. 2Treat the returned Decision as the current answer for that key and context.
3. 3Follow its supersession history when the reason for change matters.

GraphQL, CLI, and MCP

GraphQL query: currentDecision
pnpm decision-log decisions current architecture/database
MCP tool: decision_log.get_current_decision
MCP resource: decision-log://current/{decisionKey}

Steps

1. 1Retrieve the current Decision and confirm it is the record being replaced.
2. 2Create the replacement with the new Decision text, rationale, and reason for change.
3. 3Verify the replacement is current and the prior Decision remains retrievable in history.

Supported surfaces

GraphQL mutation: supersedeDecision
pnpm decision-log decisions supersede {decisionId}
MCP tool: decision_log.supersede_decision