Justin Bartak · AI Org · · 5 min read
The Machine. It Runs the Company.
TL;DR
Orbyt Collective is the machine that runs Orbyt: 12 officer seats, none of them people, held together by guards that check the org the way tests check code. The org is not managed. It is versioned, audited, and promoted on evidence. Here is the machine, part by part.
Orbyt is run by a machine. I built the machine, I hold its one lever, and most mornings it has already done its work before I sit down.
That is not a metaphor stretched for effect. Orbyt Collective is 12 officer seats, none of them people, each with a written charter, connected by guards that check the organization the way tests check code. It files reports, logs decisions, proposes lessons, corroborates each other's findings, and gets stopped at gates.
The org is not managed. It is versioned.
What is the machine, exactly?
Take the parts one at a time, because each one replaces something a human org does with meetings.
Charters instead of job descriptions. Every seat has a written charter in the repository. Not aspirational prose: lanes. What it may do autonomously, what requires a gate, what it may never touch. 29 autonomous lanes, 40 gated ones, and zero seats that can merge to the branch that deploys.
A decision log instead of institutional memory. 40 logged decisions and counting. When three agents independently chose the same name for the finance seat, Ledger, that went in the log as decision 16. When a convergence rule was waived, the waiver and its evidence went in. Nothing load-bearing lives in anyone's head, including mine.
A promotion ladder instead of performance reviews. Seats earn authority through ratified, deterministic criteria: check results, committed artifacts, never self-assessment. The ladder currently holds at stage two because two of its own criteria are unmet. It does not care that I want it to advance, which is precisely the point.
An inspector general and a kill switch. An independent adversary seat, and a stop that halts the fleet. The kill switch is checked before any push by an ordering law, not a convention, because a convention is what you have instead of enforcement.
How do you put an org under test?
Here is the part I have not written about before, and it is the part that makes the rest survivable.
The wiring between the agents is itself guarded. A mechanical check runs on every commit and enforces the invariants no single seat can see: no seat runs on a model it is not pinned to. Metered API keys are scoped to individual workflow steps, never to a whole run. Cron hours are staggered rather than stacked. The roster on disk matches the roster in the code. A halt check precedes any push, in that order.
A second law governs memory. Every seat loads its own charter and its own lessons, and never a peer's. That sounds antisocial. It is drift control. 12 agents reading each other's operating instructions converge into one agent with twelve names, and the whole value of separate seats is that they fail separately.
And the numbers are counted honestly. 51 recorded runs, 43 completions, 30 discards at gates. An 84.3% completion rate where nearly a third of produced work gets thrown away rather than waved through. The discard pile is the cost of the gates, and I publish it because it is the number that argues against me.
I described how I direct this fleet day to day in I Manage AI Agents Now, Not People, and how the seats named themselves. This post is the layer underneath both: the machine that keeps the fleet honest when I am not looking.
What did the machine produce without me this month?
A weekly quality run that corroborated Engineering's security findings and caught one Engineering missed. A daily pulse that reads every department's committed output and names the one thing that needs me. Lessons proposed, quarantined, and held behind a gate that opens on evidence rather than enthusiasm. 35 of 58 recorded failures mechanized into permanent guards, so the same mistake cannot ship twice.
None of that required a standup. All of it left a committed artifact I can audit after the fact.
The boundary, stated plainly
Collective runs in exactly one place: here. It is not for sale, and it has never been run anywhere else. The only company operated by an agent org like this is the company that built it, and I am pulling it apart in public so that one day another company could adopt the pattern with its eyes open.
One human stays in the loop, and that is not a safety disclaimer. It is the whole design. The machine compounds capability. It does not compound judgment, taste, or accountability, and every guard exists to keep that division honest. On anything touching money, customer data, public claims, or the machinery itself, the machine produces a recommendation and I decide.
What to do Next
You do not need 12 seats. You need one invariant enforced in code.
Pick the agent workflow you already run and write down its lanes: what it may do alone, what needs your sign-off, what it must never touch. Then enforce one line of that mechanically, a check that fails loudly, rather than a paragraph in a prompt.
A prompt is a request. A guard is a law. Orgs run on laws.
The company that runs on committed artifacts can be audited. The company that runs on meetings can only be remembered.
Related reading:
-
I Manage AI Agents Now, Not People the operator's view of directing the fleet
-
My C-Suite of Agents Named Themselves. how the seats came to be, and what they chose to be called
-
391 Yeses and Not One No. the access model underneath the lanes
-
AI Builds AI. I Found the Ceiling. what the machine can and cannot improve about itself
-
When Do I Get to Leave the Loop? which gates open on evidence, and the four that never do
Originally published on orbytlabs.ai on Aug 30, 2026.
Frequently asked questions
What is Orbyt Collective?
Orbyt Collective is the agent leadership team that runs Orbyt: 12 officer seats with written charters, a decision log, a promotion ladder, an inspector general, and a kill switch. It runs in exactly one place, it is not for sale, and it has never been run anywhere else. One human stays in the loop by design.
How do you stop an AI org from drifting?
The same way you stop code from drifting: guards that run on every change. The org's own wiring is checked mechanically, every seat loads only its own charter and lessons, a halt check must precede any push, and authority advances only on committed check results. The org is versioned like source, because it is source.
Do the agents in an AI org get more authority over time?
Only by earning it through a ratified ladder. Promotion criteria are deterministic and evidence-based, never self-assessed, and the criteria file is hash-pinned so changing the bar resets every streak earned under the old bar. The ladder currently holds at stage two because two of its own criteria are unmet.
What does the human actually do in a machine-run company?
Sets intent, holds the bar, and makes the final call on anything touching money, customer data, public claims, or the machinery itself. The machine produces recommendations, reports, and shipped work inside its lanes. The human is not a rubber stamp at the end. The human is the whole design.
