# Decision Process

> How architectural/product decisions are made and recorded in this project.

_Governance layer. Verified 2026-07-23._

---

## When a decision record is required
- Any architectural change (boundary, layer, contract) — see [`ai-workflow.md`](ai-workflow.md) "must ask before changing".
- Superseding or amending a **locked decision** in [`../06-history/decisions-log.md`](../06-history/decisions-log.md).
- Introducing a new domain or first-class entity (e.g. a future `Deal` — [`../02-business/deals.md`](../02-business/deals.md)).
- Adding/widening AI actions, tools, scopes, or a new integration.

## Decision template
Copy this block into [`../06-history/decisions-log.md`](../06-history/decisions-log.md):

```
Decision ID:        DR-<NNN>            # continue the sequence; next available is DR-009
Date:               <YYYY-MM-DD>
Status:             Proposed | Accepted | Superseded by DR-<NNN> | Deprecated
Context:            <situation that forced the decision>
Problem:            <the specific question being decided>
Options considered: <option A — pros/cons; option B — pros/cons>
Decision:           <what was chosen, plainly>
Reason:             <why this option over the others>
Impact:             <what it enables, what it costs, risks accepted>
Affected files:     <code + docs/ai files touched>
```

## Rules
- **Recording location is fixed:** all decisions live in [`../06-history/decisions-log.md`](../06-history/decisions-log.md). The log is **append-only** — supersede, never rewrite.
- A decision is not "done" until the record is written **and** the affected KB files are updated (per [`change-management.md`](change-management.md)).
- Decisions are proposed by AI but **accepted by a human accountable owner** — especially for business, security, execution-ownership, and deployment matters.
- If the reasoning or an input is not yet known, record it as **`Unknown - requires confirmation`** rather than guessing.