Best for
- Decisions that change product rules or architecture
- Teams (human or AI) that keep relitigating settled questions
- Audits that ask 'who decided this and when?'
What you give it
- The decision in the decision-maker's words, and its context
What you get back
- A numbered decision record in your project's standard form
- A supersession list: each overridden statement, named and located
- Cross-references updated so old documents point to the new truth
How it works
- Captures the decision verbatim, then structures it: context, decision, consequences.
- Searches the project for statements the decision overrides.
- Lists every superseded statement with its location.
- Marks the old statements in place as superseded, preserving the text.
- Files the record in sequence and updates the index.
Example
You: Record: we will support one language at launch; the multilingual requirement moves to phase two.
Result: A record with the decision, date, decider and rationale; three superseded statements listed with their documents; each marked in place with a pointer to the record.
Limits — please read
- It records decisions that were made; it does not make them.
- Supersession search is thorough but text-based — name known spots.
- Reversals are new records, never edits to old ones.