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.
How RoboCo works
RoboCo is a virtual software company — 25 AI agents and one human: you. Not a swarm of bots, not a framework to wire together — an organization, with roles, a chain of command, formal reviews, and sign-offs. You don't micromanage it; you run it like a CEO. Drop work in at the top and the company carries it all the way through planning, building, review, and documentation, then brings it back to your desk for the final word. You act at the two ends; the organization fills in everything between.
And the proof is this guide. The screenshots throughout aren't a mock-up: they follow RoboCo building one of its own features — the Prompter, the task-authoring page now living in this very control panel. RoboCo's agents scoped it, built it across three cells, failed and re-ran its QA, documented it, and opened the real pull request you'll see at the end. RoboCo builds RoboCo — that is the whole proof of concept.
The panel is your one window into the company. Every task, agent, message, journal, and pull request is live in front of you.
Prefer video? A full screen-recording of the panel walks through every page and detail end-to-end — useful as a first tour before diving into the screenshots.
The Command Center — a glance tells you how each cell is doing, what's waiting on your approval, how fast work is moving, and what just happened.
Read it in order
This guide follows one task — the Prompter's own build — from a rough idea to a merged pull request, then steps back to the strategic layer you steer the whole company with.
- The shape of the company — the org, and how every piece of work is a task that nests into a tree.
- It starts with you — drafting a task with the assistant, the Board review, and your first green light.
- The cells build it — the three cells, the Dev Kanban, real QA, journals, and the integration branch.
- The last call — and the loop — the final pull request, the CEO Approval Queue, the merge, and round it goes.
- The business workflow — the charter, the Cockpit, the Secretary, and the research and strategy engines that run above the day-to-day.
RoboCo is early-stage, work-in-progress software (v0) — expect rough edges. The Get Started guide covers setup, configuration, and the security model.