SECTION · SUBSTRATE · 09 / 20

The agents are the easy part. The substrate is the hard part.

The substrate is the coordination layer underneath the crew — the goal memory, the message bus, the permission contracts, the session logs. The agents themselves (Claude, Codex, Pi, Ollama) are free and easy to get. Making seven of them behave like one coordinated crew — instead of seven strangers in seven tabs that lose context, clobber each other's files, and run wild while you sleep — is the part that's actually hard. That's what this is.

RHOBEAR SUBSTRATE
HOOK

You set a goal once and it stays alive — the crew coordinates the right workers and keeps moving even when you step away.

TECH

A durable goal-orchestration layer that tracks objectives, worker state, inter-agent messages, events, and results across multiple model runtimes — on one box.

THE CREW, MID-HANDOFF

Every line is one piece of the substrate firing.

This is the only place on the page where the crew is shown doing something instead of described. Everything else here is caption.

compass > goal accepted · lanes [a,b,c] · judge: passbus > handoff · architect → foreman · ticket #42 · ackedsessions > session 17B-04 · +108 -15 · 2 files · transcript: 4.1kbsafety > gate: writes-allowed · no shell-escape · no net-egresscontract > role: foreman · scope: repo:write/PR · authorizedopenclaw > drift detected on main · re-aligning lanes a,b
THE SIX PIECES · WHAT BREAKS WITHOUT EACH
Compass →

Holds your goal in memory and decides what happens next.

Without it: agents finish a task and forget why they started — no goal survives the session.

Worker sessions →

A durable, replayable record of every worker's work.

Without it: parallel agents are loose chats you can't audit, replay, or trust.

Handoff bus →

Agents claim and hand off work atomically — no babysitting, no daemon.

Without it: two agents grab the same ticket and clobber each other's files.

Safety registry →

Per-role tool permissions enforced at the boundary, not in a prompt.

Without it: "read-only" is just a sentence the model can ignore when it drifts.

Hub contract →

One authorized hub to see and control every worker.

Without it: nothing stops a stray request from mutating your goals or plans.

OpenClaw →

The swappable local bridge to your machine, tools, and agents.

Without it: every integration is bespoke glue that breaks on the next update.

YOU COULD BUILD THIS YOURSELF

You could build this yourself.

A skilled solo dev can wire Claude + Codex + Ollama together over a few weekends. What you'll get wrong is the unglamorous infrastructure that bites in month two — the atomic job-claim you skipped, so two agents grab the same ticket; the permission contract that lived in a prompt instead of at the tool boundary; the retry daemon that dies at 3am and leaves work in limbo. It's the layer where building it yourself buys zero competitive advantage and costs you weeks. We already paid that tax.

Spin it up →
← Previous Judgment loop Next → Compass