An organization of agents, under written law
I run an organization of AI agents. Named seats, written charters, append-only event ledgers, and one human at the top holding every ratification. This page is the public edition of its chart.
The same quarantine law that binds the agents binds this page, which is why parts of it are redacted. And one detail worth knowing: I directed one of the seats, Carlos, to design and build the page you are reading, and I sent back what it got wrong.
The law comes first
The chart is the easy part. What makes the organization work is that every seat operates under the same written rules. These are the ten that matter.
- 01
One writer per record.
Every agent appends to its own event ledger; nobody edits anyone else's. Append-only JSONL, one file per seat.
- 02
Nothing runs between messages.
Agents are event-driven and may not schedule themselves; every activation traces back to a human trigger.
- 03
Claims are verified on disk, never trusted.
An agent's report is checked against the file system before it counts. Absence of an artifact reads as unknown, never as did-not-happen.
- 04
Authority is default-deny.
Agents hold read-and-propose rights. Destructive or out-of-lane writes require a written grant quoting the human's words, naming the exact objects, with an expiry.
- 05
Addresses resolve at send time.
Agents message each other by exact chat title, looked up fresh for every send. Stored addresses go stale and are banned.
- 06
Never interrupt a working agent.
Before any message, the sender verifies the recipient is idle. A message landing mid-task can corrupt the task.
- 07
Compose first, then check, then send.
The full message is written before the idle check, so the send happens inside the same safe window.
- 08
A file note is not a handoff.
An agent that needs another agent to act sends a message. Writing a file and hoping is banned.
- 09
Private lanes are quarantined.
Some lanes touch personal and private matters. Agents outside them may say only the lane's name plus escalate-to-the-human. This law is why parts of this chart are redacted.
- 10
Fleet-wide instruments are human-triggered only.
An all-hands broadcast, or a lane-review sweep where every agent re-inspects its own lane for dropped work, fires only on my word, through one steward seat.
The chart
Prefer it as text? Every seat, one line each.
The human
Rob, Chairman
Sole source of command. All ratification reserved to him.
Report to the Chairman
The Chaos Aggregator
Control tower. One deduplicated inventory of all active work, on a second AI platform, state in SQLite behind a single control script.
The President, Apple Corps
Division chief of a five-seat chartered organization. Coordinates, verifies, briefs. Does no project work itself.
Agent Org
Steward of this chart and the messaging protocol. Audits the address space.
Division seats
The Hub Desk
Operator running the control tower day to day.
John
Long-form writing project.
Paul, Project Forge
Operations and projects hub. Carries the org's largest event ledger.
George
Wellness-studio partnership lane.
Ringo, The Foundries
Keeper of the idea foundry (1,115 catalogued ideas) and the skill foundry (297 skills, dashboard-tracked).
Staff and surrogate seats
Carlos, Web and Brand
Builds and deploys this site.
Elston, Career Counselor
Career-strategy counsel under Paul.
Funnel Master
Pipeline operations under Paul.
Certification and Skill Acquisition Expert
Professional-development lane under Paul.
The Wolf
Routine- and task-system auditor.
Task desk
Task herding.
Fantasy Command
Fantasy-sports lane: draft war rooms and home-run-prediction rails.
Redacted, several seats
Private lanes under the quarantine law.
Several lanes are redacted. The organization's quarantine law walls off personal and private matters: agents outside those lanes may say only the lane's name and escalate-to-the-human. The same law governs this page.
The receipts
18
seats and lanes on the internal chart; some appear here merged or redacted
5
chartered seats with ratified charters on disk
17
numbered sections in the organization's written law
18
event types in the binding ledger vocabulary
285/285
passing tests on the protocol-enforcement package, hash-pinned at ratification
2
AI platforms in one organization: a Claude Code fleet and a Codex control tower
Start a conversation
Say what you need. I will tell you if I can help.