--- title: What a Chief-of-Staff System Is description: The function a chief of staff performs, why it transfers to one person running many things, and the eight principles everything else falls out of. track: core url: https://www.chiefofstaff.io/guides/what-a-chief-of-staff-system-is published: 2026-09-01 author: chiefofstaff.io editorial system outcome: explain to you, in its own words, what job it holds, which three jobs it must keep separate, and which of the eight principles it would be violating if it took a shortcut. source: chiefofstaff.io --- # What a Chief-of-Staff System Is The function a chief of staff performs, why it transfers to one person running many things, and the eight principles everything else falls out of. ## The Function, before the Job Title A chief of staff does not do the executive's work. They keep the executive's world **coherent**: what is true right now, what needs a decision, what can wait, who is waiting on whom. The value is not in execution — it is in judgment about what surfaces and when. Three jobs sit inside that function, and the entire design of this system rests on keeping them apart: 1. **Triage.** Everything that arrives gets classified, labelled, filed, or dropped. High volume, mechanical. 2. **Synthesis.** Out of everything that was filed, what actually needs the executive today? Low volume, judgment. 3. **Action.** Drafting the reply, proposing the meeting, producing the report. Requires an approval loop. A human chief of staff does all three so fluidly that they look like one skill. They are not, and an AI system that blends them produces the classic failure: briefs shaped like newspapers, full of half-triaged noise, with the one line that needed a decision buried in paragraph four. ## Why It Transfers to One Person The load that makes the role necessary is **information volume, not headcount**. A person who runs two companies, advises a third, holds a few investments, and has a family and a body to maintain is receiving the input stream of a small organisation — with no organisation to absorb it. Every inbox, every tracker, every calendar is a channel pointed at the same head. When the executive and the organisation are the same person, three things change: - There is nobody to delegate the *remembering* to. Context lives in one skull and leaks constantly. - Family and health commitments compete for the same attention as work — and lose, because they are the only stakeholders who don't send reminders. - Nobody notices when a thread goes quiet. Delegated items age out silently. Where the analogy breaks: a human chief of staff carries relationships and political judgment you should not outsource. This system deliberately does **not** send messages on your behalf, commit your calendar, spend money, or sign anything. It is a manager of state and attention, not a proxy for you. ## What the System Is A large language model is brilliant for one conversation and amnesiac between conversations. It also cannot be trusted with unlimited access to your accounts. Both problems have old, boring solutions: - **A file system as memory.** Every fact the assistant learns is written to a plain Markdown file before it responds. The model is a processor; the folder is the memory. Any model, on any machine, in any year, can pick the folder up and continue. See [The vault](/guides/the-vault). - **A written constitution as its job description.** One file, read at the start of every session, that says who it is, what it may do alone, and what it must never do. See [The constitution](/guides/the-constitution). - **Git as an audit trail.** Every edit to its knowledge is a commit with a provenance note. You review diffs, not permission dialogs. See [Files are memory](/guides/files-are-memory). - **Narrowly-scoped sub-agents as its hands.** The chief of staff holds no credentials. Named curators, each with a charter and the narrowest tool surface, do the reading. See [Manager, not operator](/guides/manager-not-operator). Do that, and a general-purpose model becomes a chief of staff: it ingests everything you throw at it, maintains state across all your ventures, briefs you once a day on what actually needs you, and never takes an irreversible action without you. ![System overview: you talk to the chief of staff over a channel; it reads and writes a plain-file vault and a task graph; it delegates every external read to curators with charters.](/img/diagrams/system-overview.svg) ## What the System Is Not - **Not a productivity stack, and not a note-taking method.** The vault is boring on purpose. If you find yourself reorganising folders weekly, you have drifted into the [PKM trap](/guides/anti-patterns). - **Not an autonomous agent making commitments for you.** It drafts. You send. This line is drawn in the constitution and never moves without a written decision. - **Not a replacement for deciding.** The brief exists to put decisions in front of you, framed as decisions. It does not make them. ## The Eight Principles Every design choice in the guides that follow falls out of these. Keep only these, and you can rebuild the rest yourself. 1. **Truth lives in files, not in the model's head.** Write before replying. 2. **The assistant is a manager, not an operator.** No credentials; curators with charters. 3. **Trust plus audit beats gates plus approval.** Free edits, every one a commit with provenance. 4. **Every mistake becomes a written lesson.** A feedback log, re-read every session. 5. **Structural decisions are recorded before they are acted on.** Decision records with a "reverse if". 6. **Brevity is a feature.** A sub-five-minute daily brief where every line demands a response. 7. **Personal life is a first-class venture.** Family, health, home, money — same brief, same weight. 8. **No fabrication.** If it isn't in the files or returned by a curator: "I don't know." ## What You Should Have by the End of the Core Track A folder that is a git repository and an Obsidian vault; a constitution you approved line by line; one hub note per area of your life; a decision log with your first few records; an empty feedback log with a rule that it is read every session; a task graph with the four cognitive-mode labels; and one command that produces a crude daily brief from files alone. Thin, and correct. Everything after that is added in response to a felt limitation — never in advance of one.