agentic engineering scorecard→Gas Town→Annotated version of 'Welcome to Gas Town'→Steve Yegge's AI adoption Chart→Term -- pack

Term -- pack
Term -- pack

Composable, declarative building blocks. You can use these to assemble arbitrary agent topologies, deploy them, sit back, and watch them work from a rich console.

Backlinks

Steve Yegge's AI adoption Chart

Level 10: of the AI Adoption is where you’ve deployed a bunch of agent Term -- packs, each with its own little world it’s managing. They have identities, consoles, you can check in on any of them, tweak their standing orders, you name it. They’re starting to be a handful. But you don’t need to build an orchestrator for them, since Gas City is the orchestrator.

see in context
blog post - welcome to Gas City - 2026-04

Gas City has deconstructed the entire Gas Town stack into composable, declarative building blocks called Term -- packs. You can use these to assemble arbitrary agent topologies, deploy them, sit back, and watch them work from a rich console. (Or tmux, if that floats your boat. That still works in Gas City!)

Gas City is the supervisor plane that connects, manages, and coordinates these deployed mini-factories.

see in context

You should almost never deploy a single-agent pack for a real business process. The reality is that any agent can go temporarily insane, at any time, and make a bad call. No matter how smart they are. We know now that hallucinations and false memories and forgetting are baked mathematically into all memory systems; there’s no avoiding it. So you should never just have one coding agent managing a piece of infrastructure. Not even for a low-stakes part of your business. You should always have at least two or three working together on a little crew.
...
agent problem - a single agent by itself cannot be trusted to reliably perform its job

This is exactly why dark factories are so attractive. With Gas City you can build any sort of adversarial group structure you like, for a team of collaborating agents. They can watch over each other. By catching each other’s mistakes, the agent group reaches a far more reliable consensus and outcomes than you can get from a single agent. That’s why we think of deployed orchestration as being fundamentally made of multi-agent teams: factories. Define your Term -- pack, deploy it, et voila — you are officially on the path to being an AI-native shop.
...
This helps answer the question: what is an AI company?

see in context

A deployed Gas City Term -- pack is an AI-native business process automation. Once your pack is running, Gas City’s supervisor agent system will keep it going, even on remote machines.

At this point, with one deployment, you are officially at Level 9 on the AI Adoption Chart.

see in context