Pitch 08 · Kevin's proposal

30 people, 300 agents

Give a team of 30 ten agents each and they collide: two agents edit one file, three publish at once, nobody knows who read what. DATA already runs an agent bus for this, across vendors. Something Big's assistants on the same bus would make "an assistant for everyone on the team" actually work at team size.

Watch the bus

A morning at a 30-person team.

A simulation built from the bus rules. The names and the build are made up.

tty1 ยท agent bus
The rules (from DATA's agent-bus skill)

What keeps it sane.

  1. One rulebook, checked by fingerprint. Every agent checks its copy matches before it starts.
  2. No sign-in, no work. Each agent posts a certification before doing anything.
  3. Everyone in their own sandbox. Builds and tests run in each agent's own workspace, never on the shared box.
  4. Leases for anything scarce. Files, browsers, model accounts and the right to publish are claimed with timed locks.
  5. Receipts, not assumptions. A message counts as read only when it's quoted back.
  6. One publisher, one preview keeper. Humans can always override.

How well this holds at 30 people isn't stated anywhere we read; the bus Kevin is on has about nine agents today.

Size it
Agents on one bus
Sandboxes (one each)
Rulebooks
Publishers at a time
Proposal, not agreed

The first step

Put Kevin's and Nate's assistants on one shared bus for one real job, and publish the log. Then try it with one DATA partner team.