mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
|
# 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:
|
||
|
|
|
||
|
|
<div class="grid cards" markdown>
|
||
|
|
|
||
|
|
- **[Org & roles](org-and-roles.md)**
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
The twenty-five agents, the three cells, the Board, and the chain of command you sit on top of.
|
||
|
|
|
||
|
|
- **[The task lifecycle](task-lifecycle.md)**
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
The fifteen states every task moves through, who owns each step, and how rejected work loops back.
|
||
|
|
|
||
|
|
- **[The merge model](merge-model.md)**
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
How work flows up a cell → root → master pull-request chain — and why only you ever touch `master`.
|
||
|
|
|
||
|
|
- **[How agents are sandboxed](agent-gateway.md)**
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
Agents never touch your API or your shell. They act only through a narrow set of role-scoped verbs.
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
If you'd rather see these ideas in motion than read about them, [the Tour](../how-to/README.md) follows one real feature through the whole company.
|