using-gc

# Using GC Use Gas City only when the caller explicitly selects it. Treat it as a replaceable execution adapter, not a correctness or completion boundary. The adapter cannot select AgentOps semantics, issue a binding verdict, or turn factory completion into delivery or validation proof. ## Choose the factory first AgentOps supports both Gas City and the [Agentic Coding Flywheel](https://agent-flywheel.com) as external software-factory runtimes. Use this skill only for Gas City. If the caller selects the Flywheel, follow its [native workflow](https://agent-flywheel.com/complete-guide) instead of wrapping it in Gas City. AgentOps supplies skills and evidence contracts to either factory. It does not need its own Gas City formula or role pack. Install or link AgentOps skills into the provider runtime before starting workers; the upstream Mayor, coordinator, and workers can then discover and select `plan`, `implement`, `test`, `validate`, and other AgentOps skills normally. ## Gas City 1.4 operating model Gas City 1.4 is run-centered. The supervisor serves the dashboard and typed, paginated session/run APIs. Every graph-owning city or rig scope needs its own `core.control-dispatcher`; that deterministic worker advances formula control beads. Agent workers claim routed work. The upstream `gc.mayor` skill is the guided coordinator; `gc.run-operator` launches and supervises formulas. The normal AgentOps path is: 1. Install and pin the upstream `gascity` workflow and rig-role ...