Essay · notes
A small stack
Field kit · professional day only
A stack is a field kit for professional judgment under load — not a warehouse of apps, and not a system for the whole of a life.
Most stacks grow by anxiety: a new tool for every leak. Optimization culture worships volume — more capture, more throughput, more motion. I want the opposite: a small kit for work, one job per instrument, able to survive a hard professional day without the pack bursting open.1
That is a capacity stance, not a hustle one. Protect decision quality under load, not events processed. Sequence before inventory. Return, don’t collect. Instruments you pick up and put down — not feeds that never leave your hand.
The scope is deliberate. What follows is how I run professional life only. Family, play, and the rest sit outside the kit on purpose. Breath and body signal appear only as readiness for the workday — never as a lifestyle program wearing the mask of productivity.
A day has four movements. Check reads the ground. Aim sets time and priority. Work is judgment and co-owned output. Pack closes so tomorrow can open. The map below shows the instruments and how they hand off to each other.
Four stages · few tools · choose a stage or an instrument
Choose an instrument to see its job and how it connects to the rest of the kit.
Pack leads into the next Check · co-pilot output lands in files, not only in chat
How the day runs
You do not start with the inbox. You start with readiness for the workday, then priority, then judgment, then close. Deep work can enter at Work; unclear priority enters at Aim. The default is never “open mail and hope.”
Check is field work on the phone. Open starts the day on purpose; Whoop reports readiness. The signal informs how much load is wise. It never authorizes guilt, and it never decides whether anyone “deserves” a softer day.
Aim separates time from tasks. Calendar holds the day in blocks. Todoist is the sole system of record for the week — one map. A second task app is two maps arguing; under load, you will trust neither. Calendar is not a task list with colors. Todoist is not a place to fake a schedule.
Work happens at base, on the MacBook. SuperGrok co-pilots in the terminal so the co-work stays an instrument in the kit, not another feed in the pocket. When output is co-owned, it lands in Docs or Sheets. Chat is a channel, not the logbook and not the archive.
Pack closes so tomorrow’s Check is not taxed. It is a short ritual, not a second inventory: about five minutes, or sixty seconds when the day went wrong. Settle calendar and Todoist — done, carry, or kill. Land co-pilot output if it is co-owned. Clear Gmail and Slack by handling what matters and parking the rest in Todoist. Close readiness with Whoop and, if useful, Open. Then the day can end.
Base and field
I separate where from what. The MacBook is base: depth, terminal, co-owned files — the room where judgment can hold. The phone is field: readiness, light aim, capture, and close. It is not a second desk for unfinished work that needs real attention. Tools live in the kit; they do not become the room. Do not ask an app to be a place.
Three rules
The kit stays small because the rules are few. Everything else is preference or fashion.
First: one map for the week. Calendar owns time for the day; Todoist owns the week. They hand off to each other, but neither pretends to do the other’s job.
Second: use, then stow. SuperGrok is for Work. Co-owned results leave the co-pilot and land in a file people can open without replaying the chat.
Third: know the room. Deep work lives on the MacBook. The phone opens and closes the professional day; it does not host the middle of it when judgment is required.
When the kit fails
A kit that cannot bend becomes a purity cult. Under stress, lighten the pack — do not turn the rules into a verdict on the person carrying them. If the day collapses, use the sixty-second Pack and move on.
Some professional days are availability: rooms, agencies, partners. On those days Aim is presence, not a deep Work block. That is different ground, not failure. Whoop still informs load; it still does not judge character.
Keep the scope honest. This kit is for professional life only. Stretching it over the whole of life turns capacity into control over play and rest. I am not my kit. It serves professional judgment under load. A life is not a proof that the kit was perfect.
The only useful test: under load, does the kit support the next hard call — or accuse me for an imperfect pack?
Reading
- Simon, H. A. (1971). Designing Organizations for an Information-Rich World. In Computers, Communications, and the Public Interest. Johns Hopkins. — Attention as the scarce resource. ↩
- Meadows, D. H. (2008). Thinking in Systems. Chelsea Green. — Structure over frantic fixes.
- Newport, C. (2016). Deep Work; (2024). Slow Productivity. — Depth, fewer simultaneous obligations.
- Burkeman, O. (2021). Four Thousand Weeks. FSG. — Against infinite optimization of a finite life.