Can I buy Orbyt Collective or run it at my company?

No. As of August 2026 Orbyt Collective runs in exactly one place, at Orbyt Labs itself. It is not for sale and has never been run at another company. It is being separated into something another company could adopt.

What does one human in the loop mean?

It means one person is accountable for every decision and makes every decision the machine is not authorized to make on its own. At Orbyt Labs this is a design principle rather than a safety disclaimer. The agents concentrate the founder's attention and never replace the call.

Does the system ever refuse its own founder?

Yes. Orbyt Labs' audit harness blocks the founder's own commits when they fail a guard, and there is no override flag. The promotion ladder applies the same rule to itself and does not advance while any of its own criteria are unmet.

How did the agents get their names?

Orbyt Labs' founding agent officers were each asked to choose their own name in isolation, unable to see the others. Three independently chose the same name, Ledger. The collision is recorded as entry D-0016 in the company decision log.

Research Lab

Orbyt Collective.

Q: Does an AI actually run Orbyt Labs?

An agent leadership team runs Orbyt Labs today. It consists of officers with written charters, a decision log, a promotion ladder, an inspector general and a kill switch. One human stays in the loop and makes every decision that matters.

Q: What runs without a human today, and what does not?

As of September 2026, the seats' scheduled runs, the guards, the daily pulse, the evaluator's second reads and the promotion ladder's checks run unattended, and the evaluator or the ladder can halt a seat on its own. Pausing, resuming, or reconfiguring a seat is a recorded command from the founder. Pushing to production, force pushes, destructive database changes, credential rotation, and money movement are human-only. Fully unattended operation is the stated research goal, not the current state.

“The Machine” runs the company.

The agent leadership team that runs Orbyt Labs.

Collective runs Orbyt Labs today.

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.

Generated out of the repository, not typed by hand. Every number describes this company, running now. The decision log’s most recent entry is D-0054, dated September 11, 2026. And the records behind these tiles are published whole, raw JSON, CC BY 4.0: the Autonomy Ledger holds every run with its failures, the Decision Ledger every governance decision, the Failure Corpus every documented failure mode.

Officer seats, none of them people

Decisions logged

113

Guards in the harness

82.4%

Runs completed, failures counted

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, and there is no flag to wave it through.

The promotion ladder holds itself to the same standard. Right now it is holding at stage 2, because 3 of its own criteria are not met. Ig runs, ig 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.

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.

Always watching, learning and building on its own.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, August 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.

See how it works.Meet the officers.

New here? Read the articles, in order. Want this method on your own workflow? Orbyt Consulting.

Common questions.

An agent leadership team runs this company today. Officers with written charters, a decision log, a promotion ladder, an inspector general and a kill switch. It is not a proposal. It was running while this page was being written.

Not today. It runs in exactly one place, here. It is not for sale, and it has never been run anywhere else. It is being pulled apart on purpose so that it could one day go around a company that is not this one.

One person is accountable for every decision, and makes every one the machine is not written to make. That is not a safety disclaimer added afterwards. It is the whole design. The agents concentrate his attention. They never replace the call.

As of September 2026: the seats' scheduled runs, the guards, the daily pulse, the evaluator's second reads and the promotion ladder's checks run unattended, and the evaluator or the ladder can halt a seat on its own. Pausing, resuming, or reconfiguring a seat is a recorded command from the founder; resuming a halt the machine wrote requires acknowledging that it was the machine's. Pushing to production, force pushes, destructive database changes, credential rotation, and money movement are human-only and refused to every agent. Fully unattended operation, where every failure is caught by the machine itself, is the research goal, not the current state.

Yes. The audit harness blocks the founder's own commits when he is the one who is wrong, and there is no flag to wave it through. The promotion ladder holds itself to the same standard and will not advance while any of its own criteria are unmet.

The founding officers were each asked to choose their own name, in isolation, none of them able to see the others. Three came back with the same name. Ledger. Nobody designed that, and it is recorded as entry D-0016 in the decision log.