Decisions and ADRs

Every consequential choice in a package accumulates into one decision log on the Decisions & Value segment, so "why is it built this way?" has an answer months later, in diligence, or on handover.

Where Decisions Come From

Source	What Gets Recorded
Every design run	The run's architecture decisions: what was chosen, the rationale, and the alternatives considered
Design Chat	ADRs you capture conversationally (Medium plan and above)
Gap decisions	The technologies you approved per capability, visible in the catalog and on the components they fill
Scope guard	Accepted and discarded boundary proposals, in the audit log

Generation also records its assumptions and constraints alongside the decisions, so the reasoning context survives, not just the conclusions.

Why It Matters Downstream

• The decision log is part of the approval evidence: reviewers see what was decided and why before signing.
• Exports carry it: the solution design document includes decisions with rationale and alternatives.
• On re-runs, prior decisions remain visible even as the design iterates, which is exactly the trace an assessor asks for.

Write Decisions Once

If a decision was made outside the tool (a steering meeting, an email thread), capture it through the chat in one sentence. A decision that lives only in someone's inbox does not survive the person leaving.