The Company

What keeps twenty-five agents from dissolving into noise is that RoboCo is relentlessly opinionated about how work happens. Everything is a task, no task moves without acceptance criteria, and every task walks the same strict, role-gated lifecycle — built, QA'd, documented, reviewed, approved. The structure is the point. It's what turns a roster of models into a company that actually ships.

This section explains the machinery:

Org & roles

The twenty-five agents, the three cells, the Board, and the chain of command you sit on top of.

The task lifecycle

The fifteen states every task moves through, who owns each step, and how rejected work loops back.

The merge model

How work flows up a cell → root → master pull-request chain — and why only you ever touch master.

How agents are sandboxed

Agents never touch your API or your shell. They act only through a narrow set of role-scoped verbs.

Branching strategy

The environment ladder — head, middle, and prod rungs — that decides where PRs land and how releases promote toward master.

Review & quality

Structured findings, the collision map, and PR org-structure labels — how every rejection stays traceable and resolvable.

When work bounces back — QA failing a review, the PR-review gate blocking a merge, a PM sending it back at merge time, or you rejecting an awaiting_ceo_approval task — it's never just a paragraph of prose to re-read blind. Every rejection is recorded as one or more structured findings: a file and line, a severity from blocker down to nit, what was expected against what actually shipped, and a suggested fix. Whoever picks the task back up has to name each open finding by id before resubmitting — vague "fixed it" doesn't clear the gate — and the next reviewer sees every prior round instead of re-deriving the history from scratch. The Auditor can waive a stray minor or nit finding straight from its own review queue with a required note; blocker and major findings can only be closed by an actual fix. It's why rework is a number the company can report, not a guess.

That same insistence on discipline extends to the tools agents use to do the work: on a project that ships a Makefile, an agent's raw uv / pip / conda / poetry package-management calls are denied outright and it's redirected to that project's own make quality / make test targets, so the gate an agent runs against is the same gate a human developer would.

If you'd rather see these ideas in motion than read about them, the Tour follows one real feature through the whole company.

llms.txt