Current control
Exit OS / Runtime
Control Room.
Open the system. See what is true. Know what matters. Take one useful action. Leave evidence for the next return.
No active Sprint
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 →Day 1 / 30 · STABILIZE
Current state.
OPERATING
Saved locallyCurrent priority
Protected base
Today / What matters now
Set today's operating state and one next action.
State → priority → one bounded action → evidence.
Active friction
What is stealing control?
No active friction named.
One active constraint
Next useful move:
Last check-in
Where you left off.
No check-in recorded yet. Start with what is true today.
Log / 60–90 seconds
Leave enough context for tomorrow.
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.