Renn F
2fb63fed1f
Build a complete user-facing documentation site (MkDocs Material) under docs/, served at roboco.dev/docs via a new gh-pages deploy workflow. - Sections: Get Started, The Company, the Tour, Operating the Panel, Choosing & Running Models, Cost & Observability, Optional Subsystems, Configure & Deploy, API Reference, Troubleshooting & Security (55 pages). - mkdocs.yml (Material theme; excludes the agent-facing rag/ corpus, internal scratch, and orphaned stub trees) and .github/workflows/docs.yml (mkdocs gh-deploy to gh-pages). - Retire the stale root usage.md and deployment.md to redirect stubs into the site. - Fix the docs tooling: add the pymarkdownlnt dependency + .pymarkdown.json, run serve-docs/lint-docs/fix-docs under the docs extra, add a build-docs strict gate. - Fix the roboco console-script entry point (cli, not the un-awaited async main). - README: correct the project-structure tree (optimal.py, alembic) and link the docs site.
1.3 KiB
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:
-
The twenty-five agents, the three cells, the Board, and the chain of command you sit on top of.
-
The fifteen states every task moves through, who owns each step, and how rejected work loops back.
-
How work flows up a cell → root → master pull-request chain — and why only you ever touch
master. -
Agents never touch your API or your shell. They act only through a narrow set of role-scoped verbs.
If you'd rather see these ideas in motion than read about them, the Tour follows one real feature through the whole company.