gastownhall/gascity: README-based editorial guide

gastownhall/gascity describes itself in the README as "Orchestration-builder SDK for multi-agent coding workflows". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: Gas City is an orchestration-builder SDK for multi-agent systems. It extracts the reusable infrastructure from Gas Town into a configurable toolkit with runtime providers, work routing, formulas, orders, health patrol, and a declarative. That establishes the project's stated boundary, not a production test.

The README's "What You Get" section gives a useful starting point for deciding whether the project fits: Beads-backed work tracking, formulas, molecules, waits, and mail. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Multiple runtime providers: tmux, subprocess, exec, ACP, Kubernetes, and herdr. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "Quickstart". The source evidence includes: See the full install guide at docs/getting-started/installation.md.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: brew install gascity gc version When the README contains no runnable command, this article does not invent one. Open its "Coming from Gas Town?" section and confirm system dependencies, default ports, and first-run initialization before using a public server.