A personal operating system, drawn
Most diagrams of these show boxes for the parts. The parts are not the interesting bit. What matters is the arrows, and specifically one of them.
The whole system on one screen
WHAT ARRIVES WHERE IT LANDS WHAT RUNS OVER IT
------------ -------------- -----------------
email ---.
calendar ---| projects/ weekly review
meetings ---+--- [ 1 ]-- people/ ----[ 3 ]---- morning brief
what you read---| filing decisions/ follow-up sweep
conversation ---' reference/ status pass
| |
| |
'---------[ 4 ]--------------'
acting ahead:
prepares reversible work,
waits for your approval
[ 1 ] the arrow that decides everything. If a PERSON is standing here,
the system rots. If an ASSISTANT is standing here, it does not.
[ 2 ] the structure. Deliberately small. Four ideas, not forty.
[ 3 ] routines, each written once as a file and invoked by name,
so they improve permanently instead of degrading.
[ 4 ] every correction you make is written back into [1] and [3],
which is what makes the system get sharper over time.
Reading it
Left column is what the world sends you and it never stops. Middle column is the record. Right column is the work that runs across the record on a rhythm. Everything anyone has ever built in this genre has those three columns, whether it is a Notion dashboard, a bullet journal, or a folder of markdown.
The difference between the versions that survive and the versions that get abandoned is entirely arrow [ 1 ]. That arrow is a person in almost every system ever designed, and a person is exactly the component that fails in a busy week. Move that one arrow to an assistant that reads your mail and your conversations, and everything downstream stays true whether or not you had a good month.
This is why swapping tools rarely helps. Changing app changes the middle column's format. It does not move arrow one, so the same thing happens again about eleven weeks in.
What each box actually contains
| Box | Contents |
|---|---|
| projects/ | One file per project. Status, open questions, the decision log, next action. Every dashboard is derived from these and never maintained beside them. |
| people/ | One file per person. How you know them, recent history, the open move. Separate from the deal on purpose. |
| decisions/ | The choice and the reasoning. The reasoning is the part nobody records and the part you will want. |
| reference/ | What you read, filed by the question it answers rather than by its subject. |
The full layer-by-layer build order is at how to build a personal operating system, the copyable structure is at the template, and the same diagram scaled to a team is at an AI operating system for companies.
The diagram, built
The book builds every box and every arrow in four tiers, in plain files you own, with the prompts printed.
Get the bookSee the filing happen without a person
Mail and meetings landing in the right project, with nobody doing the landing. Try the demo.
See the demo