The client asks why we built it this way
Decisions are records with their reasons, and every change keeps who made it and why.
For: Product owner, Project lead
What happened
A client or an auditor asks why the system behaves the way it does, and nobody remembers.
Why it happens
Reasons live in heads and chats. By the time someone asks, they are gone.
What Corpole does
- Keeps decisions (ADRs) with their context and consequences, linked to what they govern.
- Keeps an append-only history: who changed what, when, and the reason for every Authority change, whether a person, an agent, GitHub or CI.
- Traces a requirement to its criteria, tests, work items and pull requests.
What you do
- Open the requirement: its decisions, relations and history answer most of the question.
- Open the change history for the period in question.
Keep it from happening again
- Ask agents to propose a decision whenever a design choice is made.