SECTION · SUBSTRATE · 07 / 20

Type /goal. Walk away. Come back to ship.

This is the one feature that actually justifies leaving a chat window behind — your fleet keeps building while you go live your life.

COMPASS GOAL SYSTEM + AUTOLOOP

HOOK · GOAL SYSTEM

Set a goal once, and RHOBEAR remembers what matters, what changed, and what still needs to happen.

TECH

Persistent goal state with status, budgets, continuation counters, owner-action flags, outcomes, and resumable execution context.

HOOK · AUTOLOOP

RHOBEAR can keep making progress in bounded loops without running wild.

TECH

Owner-gated autonomous continuation with iteration caps, state reloads, pause/clear checks, and judge-controlled stopping conditions.

A · WHAT YOU DO

Your part is the sentence.

Type /goal and describe the outcome in plain language — "ship the Stripe onboarding flow," not a ticket list.
Pick which agents are allowed to run while you're away (Architect, Foreman, Guardian, Spark — toggle each).
Set the iteration cap and the budget ceiling, then hit go.
Close the laptop. Telegram will buzz if it needs you.

B · WHAT THE FLEET DOES

The crew owns the verbs.

Architect decomposes the goal into lanes, writes the gate, drops the plan on the Board.
Foreman picks up each lane in order, opens worktrees, ships PRs, reports back with diffs.
Guardian reviews every diff against the gate and the safety registry before anything lands.
The Judge reads every report and decides whether to fire the next iteration or stop.

C · WHAT YOU CAN STEP AWAY FROM

Real scenarios the loop owns end-to-end.

Overnight feature builds — wake up to merged PRs and a Telegram summary.
Bulk refactors across 40+ files where the diff would drown you on screen.
Test-coverage backfills that nobody on Earth enjoys writing by hand.
Long media renders — Spark queues the takes through the same loop.

D · WHERE IT STOPS

Bounded, not blind.

Iteration cap hits — loop pauses, summary lands in your inbox.
Budget ceiling tripped — every model call is metered, the loop halts before it burns past your number.
Judge emits needs_owner — anything outside the gate waits for you.
You hit pause or /clear from anywhere — Telegram, the hub, the CLI — and the loop drops to a clean stop on the next checkpoint.

ONE GOAL, FIVE HOURS, ZERO BABYSITTING

A real autoloop trace, captured.

you > /goal ship the stripe onboarding flow · cap=8 · budget=$12 compass > goal accepted · id=goal-204 · status=running architect > decomposing into 3 lanes [--gate strict] lane a · stripe webhook handler foreman-1, ~22 min lane b · onboarding form + persistence foreman-2, ~35 min lane c · test coverage + docs foreman-3, ~18 min foreman-1 > opened PR #88 · +142 -8 · 4 files · tests green guardian > PR #88 review-ready · 14 checks pass · gate satisfied judge > verdict: continue · lane a done · lanes b,c running --- autoloop iteration 1 complete --- foreman-2 > opened PR #89 · +287 -22 · 7 files · tests green guardian > PR #89 review-ready · 12 checks pass · gate satisfied judge > verdict: continue · lane b done · lane c running --- autoloop iteration 2 complete --- foreman-3 > opened PR #90 · +94 -3 · 3 files · tests green guardian > PR #90 BLOCKED · "stripe key referenced in docs example" judge > verdict: needs_owner · scope: secret-leak suspicion openclaw > telegram fired · "goal-204 paused · review needed" --- autoloop paused · 3 PRs ready · 1 owner question ---