Working definition
An ADR is four lines that freeze a consequential choice — context, decision, expected impact, and whether you honoured it later.
How it works
You often decide in motion and remember only the outcome. When the outcome disappoints, the story rewrites. If you log decisions builds a traceable chain — the same discipline software teams use for architecture forks, applied to personal operating choices.
Minimum viable ADR (personal):
| Field | Prompt |
|---|---|
| Context | What was true when you chose? |
| Decision | What did you commit to? |
| Expected impact | What should move on the lead within seventy-two hours? |
| Review date | When will you mark honoured / broken? |
Distinction from Manual Of Me: the Manual holds patterns; ADRs hold dated forks. Distinction from Accountability Check: accountability audits fidelity to your promises; ADR captures the promise at birth.
Signature
The image is the mini-ADR on the call — Yann models what · why · expected impact live on 2026-04-13 while members journal edges in parallel. The WOW: one decision logged beats ten pages of mood.
More room passes mention this doctrine in replay narrative — search the Codex for Architecture Decision Record (ADR) or start from the latest entry on Weekly Sessions.
Your move this week
This week’s micro-action (24–72 hours):
- Pick one decision you already made this week (or must make before Friday).
- Write four lines — Context · Decision · Expected impact · Review date.
- Read it aloud once — if Expected impact is vague, rewrite until it names a lead behaviour.
- On the review date, mark honoured or broken in one word.
- If broken, add one line: what the failure strategy was (see Failure Strategy).