Running on Agents on Start AI Tools - Presented by Intent Solutions

The Cockpit Is a Folder of Markdown

Thu, 13 Aug 2026 08:00:00 -0500

Ask anyone to picture the control plane for 191 repositories, 46 running containers and 254 service entities, and they will describe a web application. Sidebar of services. Traffic lights. A time-series chart nobody reads. Probably a login page.

Intent OS has none of that. Mission Control is a directory of Markdown files in a git repository. Nine of them regenerate under a single command. There is no server, no database, no UI, and no API. You read it with cat, or on GitHub, or by asking an agent to read it, which is the case that actually matters.

Dictated From a Phone

Thu, 13 Aug 2026 09:00:00 -0500

The most common question about this setup is where the desk is. Frequently there isn’t one. A large share of the work that produced 598 commits was dictated by voice from a phone, over a private network, to a machine that then ran the actual build.

The tailnet on 2026-08-13 shows the shape of it. Alongside the dev box, the production VPS and the relay host sit an iPad, active on a New York relay with 11.5 MB sent and 2.5 MB received, and an iPhone. Those two are not spare screens. On a lot of days they are the office.

The Status Page That Refuses to Lie

Thu, 13 Aug 2026 10:00:00 -0500

Most status pages are a rendering of what a collector last managed to fetch. When the collector fails, the page shows the previous value, and the previous value was green. This is the default behavior of nearly every dashboard, and it is the single most dangerous property a status page can have, because the failure it hides best is its own.

The Intent OS projections are built so that cannot happen, and the enforcement is not a code review convention. It is JSON Schema, with negative fixtures that prove each rule rejects the specific lie it was written to catch.

Two Months, 598 Commits

Thu, 13 Aug 2026 11:00:00 -0500

Intent OS was created on 2026-06-13. This chapter was written on 2026-08-13. Everything below was re-derived from a command on that second date, because a number copied from an earlier draft is a claim, not evidence.

The count

$ git log --since=2026-06-13 --oneline | wc -l
598

Five hundred and ninety-eight commits in two months, of a repository that did not exist before the first one.

What	Count	Where it comes from
Commits	598	`git log --since=2026-06-13`
Dated CHANGELOG entries	239	across 44 distinct working days
Beads in this repository	497	210 open, 3 in progress, 63 blocked, 280 closed
Beads estate-wide	1,125 open	across 49 databases
Filed documents	173	`000-docs/`
Decision records	60	`decision-log/`
Evidence bundles	36	`evidence/`
JSON Schemas	35	with 154 fixtures, 80 of them negative
Repository records	191	schema-valid, 0 duplicate rejects
Service entities	254	4 hosts, 4 environments, 246 services
Containers	46	all healthy on the 2026-08-12 snapshot
Declared capabilities	16	8 healthy, 1 degraded, 6 unknown, 1 planned

239 entries across 44 days works out to about 5.4 discrete pieces of recorded work per active day. Not 44 days of steady output either: the entries cluster, because the work clusters.