Working definition
Ninety-ninety-one is the contract: one priority owns ninety minutes a day for ninety days — not twenty games at once.
How it works
You often run many projects at low heat. You feels busy; the lag barely moves because energy stayed diffuse — like sun on skin instead of light through a lens.
The container is deliberately narrow:
| Element | Rule |
|---|---|
| 90 days | Long enough for Cumulative effect to show; short enough to audit weekly |
| 90 minutes | One protected opening slice — not the whole day |
| 1 priority | One named Battle-linked outcome — not a portfolio |
Distinction from SAP: SAP can start with five-minute legitimacy cards; ninety-ninety-one is the heavy lane once the real domino is named. Distinction from Battle: the Battle names the adversity; ninety-ninety-one names the calendar container that protects reps.
Signature
The image is the magnifying glass in the sun — Yann on 2026-05-08: diffuse sun warms; focused sun burns. Acting everywhere is acting nowhere — Aurélien’s line in the same block — sits on the same picture.
Spatial split — diffuse (many projects at low heat) versus 90-90-1 (one priority through the lens + first 90 minutes at day start, protected 90 days on the calendar). Your move: Your move this week.
More room passes mention this doctrine in replay narrative — search the Codex for 90-90-1 or start from the latest entry on Weekly Sessions.
Your move this week
This week’s micro-action (24–72 hours):
- Write the one priority ninety-ninety-one protects this month (one line).
- Block ninety minutes tomorrow before inbox on a calendar you will see.
- Name whether Sunday is in or out of the streak — decide consciously, do not drift.
- At session end, state the priority aloud once — if the sentence wobbles, shrink scope until it holds.
- Log one sentence after the block: what moved on the lead, not the lag.