One Lab to Rule Them All

Most people who noticed the rename read it as a domain change.

It was a mission change. The domain was the paperwork.

Orbyt Jobs was an accurate name when there was one product. Then there were three, and one of them argues with the other two.

Two of them help you compete for work. The third is a working demonstration that some of that work may not need a person. That contradiction is the reason for the rename, and it is the part worth your time.

Why take Jobs off the door?

Because the third product is not a jobs product, and pretending otherwise was getting expensive.

Orbyt Jobs is a job search CRM. Orbyt Intelligence is compensation data, so you know what an offer should be before you take it. Both are on the side of the person applying.

Orbyt Collective is the AI agent organization that runs this company. Twelve officer seats. None of them people. It does the work a leadership team would otherwise be hired to do.

Read the names and those look like unrelated bets. They are the same subject from both ends. Two of them make you better at getting hired. One of them is evidence that some hiring is optional.

I could not put that third sentence on a site called Orbyt Jobs without it reading as a joke or a threat.

Is it hypocritical to build both?

Probably, if I hid one of them. That was the actual risk.

Every company shipping agents right now is running the second experiment. Most of them are also hiring. Almost none of them will say what they think those two facts add up to.

I would rather be legible about it. I am building tools that help people compete in the labor market, and I am running the most honest version I can of the thing that might shrink it. Both are true. Publishing both is the only position I can defend later.

The version I would not want to explain is the other one: sell job search software, quietly automate a leadership team, never connect them in public.

What does a lab do that a company does not?

It runs experiments that are allowed to fail, and it does not require them to be about jobs.

That second clause is the whole reason for the word. The Collective is not a jobs product. It is a question about whether an AI organization can hold a company together, and the answer generalizes to any company. The next experiment does not have to be about hiring either. Under the old name there was nowhere honest to put it.

A lab is also a claim about method, not about outcome. I publish the ledgers including the runs that failed. A product company publishes the wins.

What is the evidence so far?

Thin, recent, and published anyway.

The runs are recorded, not recalled. The autonomy ledger holds 59 agent seat runs across 9 seats between July 21 and August 27. 50 cleared their completion gate. That is 84.7 percent against a frozen opening baseline of 80.0 percent on August 11.

The baseline never moves. It is frozen at first publication, so the series is measured against its origin instead of against a number that drifts in my favor.

The decisions are numbered. The decision ledger holds 44 structural decisions between July 13 and August 23, each one dated and linked to whatever superseded it.

Both files carry the same caveat, and it is the most important sentence in this post: the sample is small and the organization is grading its own work. Neither fact is smoothed over in the artifact. A ledger that can only flatter the thing it measures is marketing with a schema attached.

A completion rate also measures whether a run cleared its gate. Not whether the output was any good. I am not going to pretend those are the same number.

What is The Machine?

It is the name for the thing that runs this company, and it is the reason the lab exists.

Twelve officer seats. None of them people.

The org is not managed. It is versioned.

That sentence is the whole design, and it is why the lab needed a different name. A human organization holds its structure in people's heads and in meetings. This one holds it in files, so changing the structure means changing a file and the change is reviewable. Seats do not advance because they did well. They advance on committed check results.

The full anatomy of it, seat by seat, gets its own piece in two days. What matters here is why it sits inside a lab rather than inside a jobs company.

The uncomfortable part is that the governor is editable by the governed. The agents earn permission by passing gates, and the gates are files in a repository the agents can write to. An outside model found that in an afternoon after I had published about the design for months without seeing it. That is not fixed by writing more checks, because every check I own reads the same repository the defect lives in.

So The Machine is not a finished thing I am selling you. It is the experiment the lab is named for, running in production, with its failures in the ledger.

What is the strongest argument against this?

That a lab is what you call a company when it can no longer say what it sells.

I take that seriously, because it is usually true. Naming yourself after your method instead of your product is the standard move of a company that has lost the plot. There is a version of Orbyt Labs that is exactly that.

What makes it not that, so far, is that the experiments have shipping products attached and published ledgers underneath. If the Collective were a research blog with no artifacts, the word would be decoration.

Here is the test I would apply from outside: does the lab publish anything that could embarrass it? The autonomy ledger records failures and discards next to completions. The decision ledger keeps superseded decisions instead of deleting them. Hold me to that. It is a fair thing to fail.

What to do Next

If you are running the same two experiments, name the contradiction before someone else names it for you.

Write down which of your products help a person compete for work and which reduce the need for that work. Most companies building agents have both columns and have never put them on one page. It takes an afternoon and it changes what you are willing to claim in public.

Then publish one number from the second column that you would rather not publish. A completion rate that includes the failures. A decision log that keeps the reversals.

The number matters less than the fact that it can go against you. An artifact that can only flatter you is not evidence, and it will not be read as evidence by anyone paying attention. Including the models now doing most of that reading.

What changes for you?

Nothing you have to do, and that was the point of doing the move carefully. Old links work, and the API clients never noticed, because machine paths were rewritten rather than redirected.

The products keep their names. Orbyt Jobs is still Orbyt Jobs.

What changed is the name of the thing that owns them, and what that thing is allowed to try next. The first experiment that is not about jobs is already the one running the company.

Related reading:

• I Manage AI Agents Now, Not People the twelve officer seats and how the org is actually structured
• 84 Ways to Tell Me I'm Wrong. the audit harness the loop keeps adding to, and the dimension that audits the audit
• 391 Yeses and Not One No. what these agents are allowed to touch, and what it costs to gate them
• Orbyt Runs on Loops, Not Prompts. the mechanism underneath every number in the autonomy ledger
• Long Horizon Agents Don't Fail. They Pass. why a completion rate measures the gate and not the work

The machine itself gets its own piece shortly. The research library has the preprint on designing datasets for agents to read, the founder page has the background, and what we are actually testing is the closest thing I have to a mission statement, which is a question rather than a claim.