Exit OS / Control Room
Install the loop before you run it.
Control Room uses the same browser-local state as the 30-Day Control Sprint. Start the Sprint once; return here to operate it.
Start the 30-Day Control Sprint →EXIT OS // CONTROL ROOM
Decision surface · low-capacity firstSTATE → INTERPRETATION → DECISION → ACTION
NOW
Set today's operating state and one next action.
State → priority → one bounded action → evidence.
CLEAR
No active constraint named.
Noise does not earn screen space.
One active constraint
Next useful move:
LATEST EVIDENCE
Where you left off.
No check-in recorded yet. Start with what is true today.
CAPTURELeave enough context for the next return. OPEN CHECK-IN ↓
Use the same daily evidence model as the Sprint. No second journal. No catch-up debt.
Your Exit state is saved on this device first. Sign in only if you want to carry it across devices.
Runtime rule
Continuity over compliance.
If you disappear for three days, Control Room does not ask you to repay them. It restores the last useful context, shows today's state, and asks for one realistic move.