Search
Running on Agents
A four-chapter look inside an AI-operated company: the Markdown cockpit that governs 191 repositories, the phone that dictates the work, the status page built so it cannot show green without evidence, and what two months of it produced.
Twelve posts on this site mention Intent OS. Not one of them describes it as a system. A reader who lands here has to read six posts to infer the spine, and the spine itself stays invisible. This feature is the spine.
Intent Solutions is one operator and a fleet of agents. The estate they govern is real and countable: 191 repositories in the registry, 254 service entities, 46 containers, 16 declared capabilities, 49 beads databases holding 1,125 open issues. It was built between 2026-06-13 and 2026-08-13, which is two months, in 598 commits.
The four chapters are ordered by surprise. The cockpit turns out to be a folder of Markdown with no server and no database behind it. The operator is often not at a desk, and is talking rather than typing. The status page is engineered so that showing green without fresh evidence is a schema violation, not a judgment call. And the output is large enough to be worth counting.
Every number here was re-derived on 2026-08-13 from a command, not copied from an earlier draft. Where a claim did not survive that check, it was cut rather than softened. One was.
Chapters
- The Cockpit Is a Folder of Markdown Nine generated pages, four cron collectors, no server, no database, no UI, and a write guard that keeps a failed generator from ever replacing a good page.
- Dictated From a Phone What the loop actually is when the operator is on the move: talk, agents build, deterministic gates catch what the agents get wrong, receipts land in the repo.
- The Status Page That Refuses to Lie Twenty-two schema conditionals, 80 negative fixtures, and a rule that decides what the word operational means.
- Two Months, 598 Commits What one operator plus agents produced, and what it is all for.