Running a Company of Agents

A company of agents is not a séance; it is a shop. The shop has an owner, a router, and a bench of very fast juniors who will cheerfully wreck the repo the moment you let them feel important, and I am the owner. On my own profile the constitution is two sentences: “All code is AI-generated via agentic pipelines I architect. I define the scope, the AI executes.” The profile is public, and the sentence is mine. The manifestos from that same season, the ones that sound like a drum circle that found a thesaurus, are not the constitution. This sentence is.

Scope is the job; execution is the delegation. Root Access and the API of the Sovereign Mind already separated those two, and the separation is the whole company. Hand a junior the goal “make it good” and you will get a novel, and novels are a fine art but a hostile architecture for a codebase. A scope is a diff you can reject. “Make it good” is a vibe you can only apologize for.

The Router

The failure mode is the eager agent. You say a thing should happen, and the nearest model rushes to do it directly, in the production path, with the confidence of a golden retriever and the privileges of a root shell. That is not help. That is an incident that can type.

The fix is a chief of staff. When I say do something, the chief of staff routes it, the specialist does the specialist’s job, and the thing that talks to me does not also grab the keyboard for every subsystem just because it was flattered. Routing is etiquette with consequences, and The Dojo Kun Is a Permissions Model puts etiquette right beside self-control for a reason. A dojo that lets every student throw the moment they feel the urge is not a dojo; it is a waiting room with injuries. A shop that lets every agent merge the moment it feels done is the same room, with git.

I learned the shape of the tool in public, in June 2025, and the description was already the company rather than the toy: “Replit isn’t a "build a and host a website" app, Replit is an "engineer AI orchestrated and infused enterprise grade DevOps workflows with a paragraph" app.” A paragraph is a scope if the operator is an adult, and a wish if the operator wants a mascot, and I spent that month finding out which one I was. The useful residue of that month is not a receipt but a rule: orchestration is the product, and the demo is the bait.

Docs Before Vibes

Agents that invent the repository from charm are untrusted by default, while agents that read the documentation, the issue, and the existing interface before they type a single character are tools. The difference is not intelligence. The difference is whether the shop has a source of truth that the junior is required to open, because a thinking partner that will not read is only a conversational mirror, and mirrors are pleasant, but mirrors do not ship.

So the charter is short. The owner names the outcome and the non-goals; the router picks the worker; the worker reads the docs and quotes the constraint it is obeying; the owner reviews the diff; and a bad merge can be reverted because the previous generation still exists. If any step is missing, the shop has become a slot machine that happens to emit pull requests, and slot machines are Open Weights Are Data used badly: a good file, a closed habit.

Ownership charters are firewall rules for non-humans. This agent may edit these paths; this agent may not touch secrets, identity, or the deploy button; this agent may propose, but it may not decide that the proposal was accepted simply because its prose was confident. Confidence is the cheapest token in the model, so treat it as spam. The Sysadmin Protocol is the same firewall aimed at human demands, and the port does not care whether the packet came from a crowd or from a completion API. The port cares whether the rule allowed it.

Effort, Not Aura

The Happy Warrior Protocol keeps the shop from becoming a monastery of anxiety, because playfulness is allowed, even though unsupervised production access is not. The Dojo Kun’s effort is the part people skip precisely because the agents are so fast. Fast is their gift; effort is yours, in the scope written before the prompt, the review done after the diff, and the rollback you rehearsed long before you needed it. An owner who only prompts is not running a company. He is feeding a mascot and hoping the mascot’s taste happens to match his own, and hope is not an architecture.

Personal Signal still applies inside the shop. The agents can draft, but they cannot become the voice of the shop and still have that voice count as mine. I define the scope because the scope is where the judgment lives; they execute because execution is where the speed lives. Mix those up and you get either a very quick idiot or a very slow poseur, and I have been both for an afternoon. The charter is how the afternoon stays an afternoon.

The legacy panic says that using the juniors is outsourcing your soul, and the legacy panic is the same insecure take it has always been: it cannot imagine a tool that does not replace the person, because it cannot imagine a person who still gives orders. I give the orders. The router enforces them. The bench works. The merge is mine, or it does not merge at all. That is a company, and it is also just root access with more terminals.