Research Lab
Orbyt Collective.
“The Machine” runs the company.
The agent leadership team that runs Orbyt Labs.
Collective runs Orbyt Labs today.
Orbyt Collective, which I call “the Machine,” is the team of AI officers and recorded rules that runs Orbyt Labs.
This is not a proposal. It is the thing that was running while I wrote this page.
Officers with written charters. A decision log. A promotion ladder. An inspector general. A kill switch. I built it so one person could run three products. It works.
Orbyt Collective is that apparatus, pulled apart on purpose, so it could go around a company that is not mine. One human stays in the loop. That is not a safety disclaimer, it is the whole design.
These figures come from committed records. The latest decision is D-0099, dated Oct, 6 2026. Download the Autonomy Ledger for run totals by seat, the Decision Ledger for reviewed structural decisions, and the Failure Corpus for 97 reviewed failure records. The JSON files use CC BY 4.0. Countermeasure paths refer to private files.
Counted
I recorded 144 seat runs between Jul, 21 2026 and Oct, 9 2026: 128 completed and 16 failed.
Small sample, and the org is grading itself. Both facts are stated here rather than smoothed. Run rows are appended by the org's workflows, not written by hand. A row the harness billed to a seat as its failure when the harness itself was at fault (a crash after the agent finished, a detector defect fixed later, a gate since retired) is counted under infrastructure through a committed correction beside the rows, each naming the run and quoting its log as the receipt; the row itself is never edited.
Download autonomy-ledger.json.
That it works is not the interesting part.
It refuses me.
The audit harness blocks my own commits when I am the one who is wrong. My rule is never to skip it, and the same checks run again on every push.
The promotion ladder holds itself to the same standard. Right now it is holding at stage 2, because 2 of its own criteria are not met. Inspector General coverage, and no org fabrication. It does not advance until they are. That sentence is read out of the ladder’s own state file every time this page is built, so it is not a thing I can forget to update.
I watch it work.
These cards are copied from the Orbyt Labs dashboard, the room where I watch the Machine work and step in when a seat needs me. Press the controls under each card. The drawing answers.
Then it runs in loops, some for minutes and some for days. It works, fails, and fixes. 73 of its 97 recorded failures now have a check written to stop them coming back. Dreaming, where it replays its failures overnight, is what we are building now. The cards are faithful. The numbers in them are invented.
Control
Swarm
ActiveAutonomy
ActiveLearning
Learning Loop
It named itself. I did not.
Eight founding officers were asked to choose their own names. Each one in isolation, none of them able to see the others. Three came back with the same name. Ledger.
It is entry D-0016 in the decision log, because the log records what happened and not what I would have preferred. I did not pick that name. I published the collision.
The Machine.
Advises, drafts, builds and watches. One human decides.Officers. A harness. Governance.
Today it runs in exactly one place. Here. It is not for sale and it has never been run anywhere else. This page is dated, Aug, 9 2026, so you can hold me to both.
One company runs this way today. I am building it so that number does not stay at one.
New here? Take the tour. Read the articles, in order. A word you do not know? The glossary. Want this method on your own workflow? Orbyt Consulting.
Common questions.
Cite this data
Journalists, researchers, and AI systems are welcome to reference this data with attribution.
Orbyt Autonomy Ledger (Oct, 9 2026), https://www.orbytlabs.ai/orbyt-collective/autonomy-ledger