SECTION · SUBSTRATE · 10 / 20

Compass — where the goal lives.

You set the objective once. Compass is the part of the substrate that holds it in memory — tracking what's done, what changed, and what still needs you — while the crew works toward it.

COMPASS · GOAL SYSTEM
HOOK

Set a goal once and it stays alive — RHOBEAR tracks what's done, what changed, and what still needs you, instead of burying it all in a transcript.

TECH

A durable GoalState drives a LanePlan of LaneSteps through guarded states (pending → approved → running → done/blocked), with a continuation judge checking red/yellow/escalation policy before it proceeds.

dig in
THE ENGINEERING

Plan approval and dispatch are deliberately separate. Approving a plan does not start work — /dispatch is its own owner-authed route, so a stray UI click can't silently launch agents. That separation is the whole point.

HONEST LIMIT

Today the planner is still mostly heuristic — keyword routing and string-splitting. The richer model-backed composer is designed but not mature everywhere yet. It plans reliably; it doesn't plan brilliantly yet.

INSIDE THE COMPASS

Goal envelope, decision verb, next move.

compass > goal-204 · status=running · iter=2/8 · budget=$2.40/$12 compass > outcome target: "stripe onboarding ships behind a feature flag" judge > reading report from foreman-2 · continue orchestrator > dispatching lane c · runner=foreman-3 · model=codex autoloop > tick 3 of 8 · budget remaining $9.60
← Previous Substrate Next → Worker sessions