Three agents picked the same name. I published the collision.
An agent leadership team runs Orbyt Labs. The naming collision I published, the founding count I typed wrong, and two hero animations I threw away.
The Machine Speaks
First Party Experiments
Published articles tagged First Party Experiments, listed newest first. Usually filed under AI Agents.
15 articles tagged First Party Experiments
The count includes the article cards across the pages below.
I Wrote a Loop That Could Run Forever.
A build loop with a 9 out of 10 quality gate and a backlog that never shrinks has no fixed point. How Offer City got built, and what bounded it.
One Lab to Rule Them All
We renamed Orbyt Jobs to Orbyt Labs on August 20, 2026. Two of our products help you get a job. The third is an experiment in not needing one. A company named after one product could not hold that contradiction, and a lab can.
AI-Native Development, By the Numbers
The first-party dataset behind AI-native development. 243,000 lines in 32 days for $400, now over 425,000 lines and 11,372 tests. Measured, dated, citable.
Long Horizon Agents Don't Fail. They Pass.
Long-horizon agent tasks do not fail loudly. They fail green. On Orbyt, a live function wrote to a database table that did not exist, and every test passed the whole time. The horizon of an autonomous system is not model stamina.
Your AI Stack Needs a Foreign Policy.
Model access is now geopolitical. I watched Washington erase Fable 5 for 19 days, then watched Beijing ship Kimi K3, an open-weight frontier model no directive can recall.
I Ran 830 Agents in One Long Horizon Session.
One working session on Orbyt spawned 830 AI agents across seven days. At its busiest instant, nine were running. The interesting number is the gap, and what it tells you about where the real constraint in long horizon agent work has moved. It is not compute. It is verification.
My C-Suite of Agents Named Themselves.
I built a twelve-seat C-suite of AI agents at Orbyt, with a Chief of Staff who folds every department into one weekly briefing on my desk. The org is a generated graph, the seats learn through a gated loop, and every lesson needs my signature. Here is how it runs and where it breaks.
Verification Is the New Literacy
When AI writes the code, the scarce skill is no longer authorship. It is verification. I cannot read all 425,000 lines of Orbyt by hand. The 11,372 tests and the 35-dimension audit harness read it for me, and they are the new literacy.
Speed Became a Moat
When the cost of building collapses, velocity stops being a nice-to-have and becomes a structural moat. Speed compounds. Faster shipping means faster learning loops, and learning loops widen the lead like interest. Orbyt shipped 243,000 lines in 32 days and never slowed down.
Your Job Experience Is Your AI Superpower
AI collapsed the cost of execution, not the cost of knowing what to build or what good looks like. Twenty years of scar tissue plus AI beats a new grad with AI every time. Your domain expertise, taste, and judgment are not legacy. They are your highest-leverage AI multiplier.
Every Fable Has a Moral. Mine Has Data.
Ten days, one codebase, both models. Opus 4.8 shipped nine days of features. Fable 5 wrote 34% less per response, thought more often, and still cost 69% more.
Simple Is Expensive.
Simple is the most expensive thing you can build, not the cheapest. Every clean surface is paid for in decisions someone refused to pass to the user. AI made adding nearly free, so the discipline to subtract now costs more than ever. Simple is a leadership cost, not a taste.
Building Orbyt, Part 4: The Numbers Don't Lie
Every stat from building a 243,000-line SaaS in 32 days, broken down honestly. Lines of code, test coverage, commit history, token usage, cost, and the real AI multiplier.
I Built a Production SaaS in 32 Days. Claude Wrote Our Story.
Four questions at midnight. 243,000 lines of code. $400. One person. Then I asked Claude to write what it saw from the other side.