Purpose
Make the basis of a decision inspectable before it is repeated, challenged, or operationalized.
When to use it
- Nobody remembers why a rule exists.
- A meeting references a prior decision.
- You need to brief someone without relitigating the whole history.
Inputs
- Search results
- Meeting notes
- Docs
- Known decision terms
Outputs
- Decision summary
- Evidence trail
- Unresolved objections
Steps
- Identify the decision statement and its date range.
- Collect source events before, during, and after the decision.
- Separate final decision from rationale and implementation tasks.
- Flag conflicting evidence or missing approvals.
Quality checks
- The final decision is not inferred from a single weak source.
- Evidence is chronological and linked.
Failure modes
- A proposal is mistaken for approval.
- Missing systems hide the final source of truth.
Privacy notes
- Decision histories can include sensitive disagreement.
- Sanitize before sharing outside the decision group.
Example prompt
Reconstruct this decision thread. Return the final decision, rationale, source evidence, unresolved objections, and confidence.
Example structured output
{"decision":"Use landing DC from item location","confidence":"medium","evidence":["meeting:s18","email:thr_9"],"openQuestions":["Who approved exceptions?"]}