mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
docs(how-to): reframe the walkthrough around RoboCo building itself
Recast the how-to as a single thesis: RoboCo is an organization — not a swarm and not a framework — and because it is a real organization (roles, a chain of command, a gated lifecycle, reviews and sign-offs) it can build real software, shown by it building one of its own features. The walkthrough now follows that real feature end to end with screenshots from the actual run: the Board scoping it (Product Owner + Head of Marketing review), the Approve & Start decision, a genuine QA failure and re-run, the three cells' verified, agent-co-authored commits converging, and the integrated pull request — its description, its diff, and the Approve & Merge decision — coming back for the CEO's sign-off, with the final task tree at the end. The human acts at only the two ends; the organization fills in everything between. Adds the new walkthrough screenshots and places them across the lifecycle.
This commit is contained in:
Renn F
+96
-16
@@ -1,11 +1,26 @@
|
||||
# How RoboCo works
|
||||
|
||||
RoboCo is a virtual software company — 18 AI agents and one human: you. You don't
|
||||
micromanage it; you run it like a CEO. Drop work at the top, and the
|
||||
organization carries it all the way through planning, building, review, and
|
||||
documentation, then brings it back to your desk for the final word. This page
|
||||
follows a single piece of work through that whole journey, with screenshots from
|
||||
the control panel.
|
||||
RoboCo is a virtual software company — 18 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.
|
||||
|
||||
What keeps eighteen 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 lifecycle
|
||||
— built, QA'd, documented, PM-reviewed, approved — each step gated by role. The
|
||||
structure is the point. It is what turns a roster of models into a company that
|
||||
actually ships.
|
||||
|
||||
And the proof is this page. The screenshots below 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.
|
||||
@@ -71,6 +86,13 @@ nothing is implicit and nothing is lost.*
|
||||
*The Product Owner working a task over — pinning down the requirements and the
|
||||
must-haves before anyone writes a line of code.*
|
||||
|
||||
|
||||
|
||||
*Two seats at the table. The Product Owner and the Head of Marketing review the
|
||||
same task from their own angles and put their reasoning on the record — this is
|
||||
the Board building the actual spec for the Prompter, the feature this whole
|
||||
walkthrough follows.*
|
||||
|
||||
### 2 · Nothing moves without your green light
|
||||
|
||||
The Board hands the reviewed task back to you as a **notification** and waits.
|
||||
@@ -82,6 +104,13 @@ PM** picks it up, splits it across the cells, and sets them running.
|
||||
*The Board's verdict lands in your notifications and pauses there. A single
|
||||
approval is what turns the whole company on.*
|
||||
|
||||
|
||||
|
||||
*The notification itself, spelled out: the Board has finished, the task is
|
||||
recorded, and nothing happens until you say so — Approve & Start hands it to the
|
||||
Main PM; reject it and it goes back. This is the first of the only two moments
|
||||
the company needs you.*
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -109,6 +138,13 @@ cold. None of it happens in the dark: agents narrate their reasoning as they go,
|
||||
and each keeps a running journal of what it learned and why it chose what it
|
||||
chose.
|
||||
|
||||
|
||||
|
||||
*QA earning its seat. On this Prompter task it read the work, marked it
|
||||
**failed**, and sent it back — the developer's notes and the QA verdict sit side
|
||||
by side on the record, with the Auditor watching the whole exchange. Real review,
|
||||
not a rubber stamp; the gate only opens when the work is right.*
|
||||
|
||||
|
||||
|
||||
*Every agent keeps a journal — reflections, decisions, and lessons. Between that
|
||||
@@ -126,24 +162,68 @@ along with it:
|
||||
*One finished unit — branch, pull request, commits, and docs all attached. This
|
||||
is the thing that travels up the merge chain.*
|
||||
|
||||
|
||||
|
||||
*Three streams becoming one history. Each cell's work lands as its own
|
||||
**verified** commit, co-authored by the agent that wrote it — the UX/UI design,
|
||||
the backend endpoint, the frontend page — folded together into the single pull
|
||||
request that comes back to you.*
|
||||
|
||||
### 6 · The last call is yours
|
||||
|
||||
With everything merged, the Main PM opens the **final pull request** and lets you
|
||||
know it's ready. The decision comes back to where it started — with you. Merge it
|
||||
and it ships, or send it around for another lap. You're the only one who ever
|
||||
touches `master`, and anything waiting on you sits in the **CEO Approval Queue**
|
||||
on the Command Center until you act.
|
||||
The cells' work is folded up, the Main PM opens the **final pull request** into
|
||||
`master`, and the company goes quiet. The decision comes back to exactly where it
|
||||
started — with you. You're the only one who ever touches `master`, and anything
|
||||
waiting on you sits in the **CEO Approval Queue** until you act.
|
||||
|
||||
|
||||
|
||||
|
||||
*The hand-off back to you. The integrated PR is open, every cell has delivered,
|
||||
QA is green — and it waits. Nothing reaches `master` without your word.*
|
||||
|
||||
|
||||
|
||||
*And it is a real pull request, on the real repository — not a simulation. The
|
||||
company's work shows up exactly where any engineer would look for it.*
|
||||
|
||||
|
||||
|
||||
*Open it and the whole brief is there — the objective, what was built, the
|
||||
board-led split across the three cells, and the company's own notes — written by
|
||||
RoboCo, for you to read before you decide.*
|
||||
|
||||
|
||||
|
||||
*The real diff, laid out for you to inspect — the migrations, the endpoints, the
|
||||
panel components. This is the substance you are signing off on.*
|
||||
|
||||
|
||||
|
||||
*Your two words. **Approve & Merge** and it ships to `master`; **Request Changes**
|
||||
and it goes around for another lap. The last call has the same shape as the first
|
||||
— one decision, yours alone.*
|
||||
|
||||
---
|
||||
|
||||
## And round it goes
|
||||
|
||||
You handed the company a task; it scoped it, built it, reviewed it, documented
|
||||
it, and merged it; and it landed back on your desk for sign-off. That's one
|
||||
complete pass — and you can keep as many running at once, across as many
|
||||
projects, as you want.
|
||||
You handed the company a task; it scoped it, built it, failed and re-ran its own
|
||||
QA, documented it, and brought it back as a single pull request for your
|
||||
sign-off. That's one complete pass.
|
||||
|
||||
|
||||
|
||||
*The whole tree in its final state — the parent waiting on your approval, every
|
||||
cell's task done beneath it. One feature, start to finish, with you at only the
|
||||
two ends.*
|
||||
|
||||
And the feature in these screenshots is the proof. The **Prompter** wasn't built
|
||||
for a demo — it's a real page RoboCo's agents shipped to RoboCo's own control
|
||||
panel. A company building its own product, in front of you, is the whole point of
|
||||
RoboCo. What makes that hold together isn't a clever model or a lucky run; it's
|
||||
the **organization** — the roles, the gated lifecycle, the reviews and the
|
||||
sign-offs that keep eighteen agents moving as a company instead of a crowd. Run
|
||||
as many of these passes as you like, across as many projects as you like.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user