Purpose
Keep important decisions findable and auditable without writing a long memo every time.
When to use it
- A meeting or email confirms a project decision.
- A recurring operational rule needs a durable record.
- A future agent will need to know why a path was chosen.
Inputs
- Decision evidence
- Project context
- Decision owner
Outputs
- Decision entry
- Rationale
- Review trail
Steps
- State the decision in one sentence.
- Record date, owner, affected scope, and source evidence.
- Separate rationale, alternatives, and implementation tasks.
- Add reconsideration triggers if the decision is provisional.
Quality checks
- The decision is distinct from tasks and discussion.
- Evidence includes the approving source.
Failure modes
- A recommendation is logged as an approved decision.
- The entry omits conditions that make the decision valid.
Privacy notes
- Decision logs may expose internal strategy.
- Use sanitized summaries for public docs.
Example prompt
Create a decision log entry from this evidence. Include decision, owner, date, rationale, alternatives, source, confidence, and reconsideration triggers.
Example structured output
{"decision":"Use source-agnostic transcript ingestion","owner":"Atomic Bible","date":"2026-06-02","confidence":"high","reconsiderIf":["Need recorder-specific API features"]}