Running AgentOps on Gas City (gc)

This guide GUIDES agents on the gc CLI — exactly like the bd protocol guides them on bd. ao does NOT wrap gc; gc is a guided out-of-session dependency. AgentOps is the opinions (the rpi/evolve loops, the ratchet rules, the skill corpus, the .agents/ context compiler); Gas City is the substrate (controller/supervisor, Orders, the bead/dolt queue, the Event Bus, runtime providers, mayor/worker agents). The seam: gc (orchestration) invokes ao (the loop) as a subprocess.

When to use gc. In-session, you run the loop yourself (/rpi, /evolve) — you do not need gc. Reach for gc when you want the loop to run out of session: scheduled maintenance, autonomous bead drain, a long-lived team-lead agent that dispatches work and drives PRs to merge. The reference pack at packs/agentops/ is the canonical AgentOps-on-GC config. North-star framing: docs/3.0.md.

gc Availability Pattern

gc is an optional, out-of-session dependency. Skills must degrade gracefully when it is absent (see the shared fallback table).

if command -v gc &>/dev/null; then
  # Out-of-session orchestration available — see the dispatch loop below.
else
  echo "Note: gc not installed. Run the loop in-session with /rpi or /evolve."
  # Fallback: drive the loop yourself; gc adds out-of-session orchestration only.
fi

gc Primitives (the vocabulary)