Two editions ago I told you I migrated off Notion. Last edition I told you I audited the agents.
What I never gave you was the after. Where the data went. Which agents lived. What the cull actually looked like.
Here is the after.
Where the data went
Google Cloud. Specifically, a managed PostgreSQL database.
(Postgres is a fifty-year-old idea done properly: tables with strict shapes, where every record has one address and the database refuses to pretend a missing record exists. Notion is a notebook. Postgres is a filing cabinet that argues back. After watching an agent confidently quote a record that was not there, a database that argues back was the entire point.)
The migration ledger says 2,026 records crossed over on the 11th of May, in under two minutes. I told you "roughly 2,400" at the time. Ledgers correct you like that.
Ten tables made it. One did not — the weekly log failed for the dullest possible reason: a missing configuration line. Noted, fixed later, life went on.
And the honest wrinkle: Notion is not gone. The data moved. The daemon whose job was keeping Notion's copy fresh is decommissioned. But the access token still works, and the files still mention Notion somewhere. Full retirement is a milestone on the roadmap, not a thing that has happened. I said "retired" when the accurate word was "read-only."
Which agents lived
The audit found more agents than I expected. Between the official manifest and the odd corners of the codebase, more than fifty agents were found. The triage collapsed them to about twenty-two, through four verdicts: keep, merge, demote, kill.
Merged: four different agents were each making me a briefing. A daily one. A weekly one. A cross-source one. An aggregated one. Four agents, one job. They are now a single Morning Intelligence Agent. The same consolidation hit the email triagers, the playbook watchers, the feedback collectors.
Demoted: the message bus, the state writers, the utility that posts to Slack. Useful. Necessary, even. But they make no decisions, and naming a pipe does not make it a colleague. They are listed as infrastructure now, which is what they always were.
Killed: my favourite detail in the audit. Two agents existed solely to serve Notion — one syncing state into it, one checking at night that the copies matched. When the database moved, their reason to exist moved with it. Decommissioned. (The polite engineering word for killed.)
The number that stung
Last edition I said five agents were genuinely autonomous. That is true — on the roadmap. Five are designed for Level 3: the chief of staff, the EA, the calendar agent, the pipeline steward, the proposal writer.
But the live registry — the file the system actually obeys — tells a different story. Exactly two agents hold Level 3 today. Forty-four others are pinned at observe-only.
The org chart says five. The registry says two. The registry wins, because the registry is the one with enforcement behind it.
That gap, between what I designed and what I currently trust to run, is the honest measure of where this system is.
What night school actually changed
Reading this back, the real shift is not the database or the agent count. It is the vocabulary.
A few months ago I called all of it agents. Fifty-plus agents. It felt like a fleet.
Night school did not hand me better technology. It handed me better words. Registry. Manifest. Infrastructure. Observe-only. Read-only, not retired. A scheduled job, not a colleague.
Notice what happened in this edition. Things I once called agents I now call pipes, utilities, jobs. The thing I called a migration I now call a cutover with a ledger. The thing I called done I now call a milestone on a roadmap.
Once I had the words, I could finally see the system as it was, not as I had named it. That is what the cull really was. Not deleting code. Renaming things truthfully — and letting the deletions follow.
You cannot triage what you cannot name.