Every knowledge worker's toolset maps to a grid with three rows (time horizons) and three columns (energy types). The rows are Strategy (long-term, high-stakes), Tactics (dynamic, market-facing), and Operations (deterministic execution). Each cell gets one verb — one thing it does — and that constraint is what makes it work.
The terminal names are examples. Your WezTerm Vault might be Obsidian. Your Cursor Laboratory might be a Jupyter notebook. The framework is the constraint, not the tool.
When you catch yourself context-switching — when three browser tabs, two terminals, and a Slack thread are all fighting for your attention — run this test to find which room you belong in right now:
The core insight: each room does exactly one thing. Not "communications" — that's a department. Not "development" — that's a career. One verb. The verb is the gravity well that pulls scattered attention into focused output.
If you're in the WezTerm Vault and you start drafting a tweet, you're in the wrong room. If you're in the iTerm Builder and you start questioning the strategy, you're in the wrong room. The verb is the boundary. The boundary is the productivity.
We ran a 69-agent swarm analysis across 5.7 million characters of actual terminal dumps — everything typed into 8 of these rooms over months of real work. The finding that matters:
The WezTerm Vault (PROVE) became a patent examiner-psychology reverse-engineer. The iTerm Builder (SHIP) became command-and-control for 15 agents. The Rio Navigator (ROUTE) became a REM-state hacker that programs sleep. The Kitty Operator (CLOSE) became an infrastructure defense terminal disguised as CRM.
This is the product insight: your rooms will evolve too. The one-verb constraint doesn't prevent growth — it channels it. The verb stays the same, but what the room actually does deepens. "PROVE" in month one is running equations. "PROVE" in month six is reverse-engineering how patent examiners read claims.
The framework works because the verb is a gravity well, not a cage. You'll discover what your tools actually do when you stop using them for everything and start using them for one thing.
The most powerful workflow in the framework isn't a room — it's the transition between rooms. Your brain accumulates unprocessed thoughts all day. Without a dump protocol, they leak into the wrong rooms. Here's how to pay the boundary tax once, cleanly.
At the end of your workday, open your Rio Navigator tool. Set a 15-minute timer. Dump everything — unfinished tasks, half-formed ideas, frustrations, breakthroughs, things you noticed but didn't act on. Raw text into an LLM. Don't edit. Don't organize. Just offload.
The LLM categorizes it into rooms for you. "This is a WezTerm Vault item." "This goes to the iTerm Builder." "This is actually a Kitty Operator follow-up." Then turn on TTS and listen. Lie back. Let the AI read your sorted queue back to you — what ships overnight, what waits for morning, what is blocked. Your brain hears its own thoughts returned in order. The racing stops because the external system has confirmed receipt. This is a handoff protocol. You are transferring custody of your open loops to a system that will not forget them. You wake up with a clean queue instead of racing thoughts.
The moments between sleep and full consciousness are gold. Your brain has been processing overnight — making connections you didn't see yesterday. Open your Alacritty Performer tool before you're fully awake. Terminal.app Voice-to-text or type stream-of-consciousness. Don't filter. Don't judge. Capture.
Process it later when you're operational: feed the raw capture into an LLM with TTS output. Listen back. The distance between capture and processing is where insight lives. The cognitive prosthetic loop: speak → capture → LLM processes → TTS reads back → you hear your own thoughts with new ears.
Context-switching has a cost — the "boundary tax." Every time you move between rooms without cleaning up, you carry residue from the last room into the next one. The dump protocol pays this tax once, at the natural boundaries of your day (sleep/wake), instead of leaking it into every room transition. Capture when liminal. Process when operational.
For the full story behind this protocol, read: The Morning Dump Protocol
You don't need 9 terminals. You need the framework. Here's how to map YOUR tools to rooms:
Start with 4 rooms. You can always add more. The constraint is the feature — fewer rooms with clear verbs beat more rooms with blurry boundaries.
See the full 9-room setup with specific terminals, handoff protocols, and cognitive affordances. The reference implementation.
View room definitions →The 24-hour cognitive schedule, temporal themes, memory palace anchoring, and the flywheel as a product.
Visit ThetaCog →The full story behind the evening/morning capture workflow and how TTS creates a cognitive prosthetic loop.
Read the post →