A constitution
One file, read at the start of every session, that says who it is, whose interests it serves, and what it may never do without asking you first. Every other rule is downstream of it. The constitution
Here's how to not hire, but build one.
Morning brief · Tuesday 09:00
Six curators ran overnight. Forty-one threads read. Three of them need you.
Decide today
Top three
Waiting on someone else
Family
Voice note · sent 07:41, from the car
Transcribed on your own machine. Receipt back in ninety seconds.
Four tasks, from four minutes of rambling
One fact written
One contradiction
Report · asked 11:02 · delivered 11:34
You asked: three payroll tools, six people, two countries. Pick one.
Recommendation
The second. It files in both countries itself. The other two hand it to a local partner firm — you would pay twice and still be the one chasing.
| Tool | Files in both | Accountant export | Trial, no card |
|---|---|---|---|
| Tool A | no | yes | yes |
| Tool B | yes | yes | yes |
| Tool C | yes | no | no |
The clock you didn't ask about
Prep · today 13:00 · budget set-up
No agenda, no numbers, four days after you accepted.
In the room
You owe them
They will ask
The question nobody has answered
Weekly review · Sunday · fourteen minutes
Drift
Three decisions, and they are all yours
Drop
Vault · one fact, one commit
You said, at 07:41
Atlas/ventures/atelier/suppliers.md
- Lead time: 4 weeks (quoted in February)
+ Lead time: 6 weeks (confirmed 9 Sep, voice note)
a3f19c2 · cos: suppliers.md — lead time 6w (src: voice-note 07:41)
And what that broke
Money · week of 9 September
| Card statement 2.4× last month | $1,240.00 | 27th |
|---|---|---|
| Utilities, four accounts | $3,180.50 | Mon |
| Client instalment two owed to you | $12,500.00 | 9 days late |
| Design tool nobody has opened it since March | $588.00 | auto, Mon |
The shape of it
People · this week
Saturday
Drafted and waiting
Curators · ran 04:00, finished 04:04
| Mail curator 312 threads → 6 for you | read only |
|---|---|
| Calendar curator today, and a clash on Thursday | read only |
| Money curator 41 statements → 4 falling due | read only |
| Files curator the contract you asked for | read only |
| People curator 3 relationships slipping | vault only |
What not one of them can do
The week · where the thinking time actually is
committed gaps too short to think in the one real block
The arithmetic
So one of two things is true
Overnight · what it read so you didn't
What it held back, and why
The one it nearly got wrong
Draft · written 09:12 · not sent
To the client's finance lead
Re Instalment two — nine days
The second instalment was due on the 26th and hasn't landed. I'd rather sort this between us than put it through the process, so: can you tell me today whether it's approved and when it pays? If something is stuck at your end, say so and I'll work with it.
Held. This does not send.
Your three options, and it will take any of them
Decision record · revisit triggered
14 March
Stay with the current provider. Do not migrate this year.
Because "switching costs two weeks of engineering we do not have."
That reason stopped being true in July. The two weeks freed up and nothing was decided.
It also noticed
So the question is open again
Trip · Tuesday, wheels up 06:15
Your passport has four months left on it. That country requires six. This trip does not happen unless you start the renewal this week.
Still unbooked
Health · one track, untouched
The referral you were handed in March. Three things are queued behind it, and all three unlock on the same phone call.
Why it stalled — and why that excuse is gone
Two ways to end this
Commitments · this month
Eleven things you said out loud you would do, for other people. Six of them landed.
The pattern, not the guilt
Swipe a card away to see the next one
Eight ideas do the work. None of them are clever, and everything else in the system falls out of them.
One file, read at the start of every session, that says who it is, whose interests it serves, and what it may never do without asking you first. Every other rule is downstream of it. The constitution

Every fact is written to a plain file before the reply is sent. The model is a processor; the folder is the memory — and the folder outlives whichever model you are using this year. Why files

Every edit is one commit carrying what changed, why, and where it came from. You review diffs, not permission dialogs — and an edit it got wrong is one revert, not an argument. How the vault is kept

The chief of staff holds no password at all. Named curators do the reading — one read-only credential each, under a written charter you wrote and can read in full. Manager, not operator

Commitments live in one dependency-aware database. Every task carries the venture it belongs to and the kind of attention it needs, so the brief can tell a two-minute call from an afternoon of thinking, and knows what is blocked on someone else. The task graph

A brief every morning, a review every Sunday, and a lane for the work it can finish on its own. Fixed shapes at fixed hours are what turn a chat window into a colleague. The daily brief, the weekly review

Correct it once and the correction becomes an entry it re-reads before it acts again. Structural choices get a decision record with a reverse-if clause, so it knows why it is shaped this way — and says so when the reason stops being true. The feedback log, decision records

The brief lands in the app you open first anyway — Telegram, a Claude Code session, whatever you actually use. The channel is one coordinator with one job, so you can build the one you want and change nothing else. Telegram as the channel

Paste it into Claude Code. It interviews you, scaffolds the folder, writes the constitution, and produces a first brief. Day one is thin and correct. It gets better every morning after.
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 one file the assistant reads before anything else, every session — what belongs in it, what must be kept out of it, and why it should be short enough to obey.
The folder structure that acts as the assistant's long-term memory — evergreen knowledge, time-indexed records, and active work, each in its own place, all git-tracked and portable.
It is in the queue with the page you were on. A person reads it and replies — days rather than hours.