Ten departments running at once will pull you in ten directions. This chapter builds the one room you steer from: a cockpit that sits above every folder, where you see the whole operation on one screen and decide what matters this week.
3.4.1One hub steers it all
Create a single top-level folder, the cockpit, that sits above every department. Give it an obvious name so it sorts to the top:
operating-base/
_control/
planner.md (what we're doing right now)
decisions.md (every call, with the reason)
todos/ (the priority list)
marketing/
sales/
...
It does no work. It points at the work. Every other folder is an employee; this one is your desk, and it is where you stand to run everything.
3.4.2Set the current focus and priorities
The heart of the cockpit is one planning file that answers a single question: what are we actually doing right now.
# Planner
## Focus (this week)
- Get the first 10 paying users.
## Roadmap
- Now: onboarding emails. Next: pricing page test.
## Numbers
- 41 signups, 6 paying, $174 MRR.
Agents read it to know what to prioritize when they have a choice. You read it to remember what you decided. When everything feels urgent, this one file is what makes a single thing win. The todos/ folder next to it holds the committed work the plan produces, each task one small file.
3.4.3Keep a decision log
Every meaningful call gets one line in a decision log, newest first, with the reason attached:
# Decisions (newest first)
- 2026-07-08: Price at $29/mo, not $19. Room to discount later.
- 2026-07-06: Dropped the LinkedIn channel. No signups in 6 weeks.
This is not bureaucracy. It is what stops you and your agents from relitigating the same decision every month, or quietly reversing a choice you made for a reason you have since forgotten.
3.4.4Drive it with one command
The whole point of the cockpit is that it can be read in one move. It is laid out so a single command can pull the state of every area into one briefing, instead of you opening ten folders by hand.
In a running system that briefing has a fixed shape: the numbers that moved, what landed since you last looked, and the decisions waiting on you. You build that command later, when you set up reporting. For now, know that the cockpit is the thing it reads: one screen in, one decision out.
This prompt stands up the whole cockpit for you:
Act as a senior engineer setting up my operating system.
At the top of my operating base, create a _control folder
with: planner.md (my focus, roadmap, key numbers, money),
decisions.md (a dated log, newest first, each line with its
reason), and a todos/ folder. Seed planner.md from what I
tell you below.
My focus and top priorities right now:
Do this now: paste the prompt and describe your current focus, so your agent builds the cockpit and seeds it.
