⇩ Markdown

Term -- The Town
Term -- The Town

The Town: This is your HQ. Mine is ~/gt, and all my project rigs go beneath it: gastown, beads, wyvern, efrit, etc.. The town (Go binary gt) manages and orchestrates all the workers across all your rigs. You keep it in a separate repo, mostly for the configuration.

Work Level -- Town

Backlinks

Annotated version of 'Welcome to Gas Town'

⤢
^ Term -- The Town

The Town: This is your HQ. Mine is ~/gt, and all my project rigs go beneath it: gastown, beads, wyvern, efrit, etc.. The town (Go binary gt) manages and orchestrates all the workers across all your rigs. You keep it in a separate repo, mostly for the configuration.

Work Level -- Town

see in context
Glossary

Term Description Kind

Term -- The Town Your HQ directory that orchestrates all workers across rigs place

see in context
Places

Place Description

Term -- The Town Your HQ directory that orchestrates all workers across rigs

see in context
Roles

Role Description

The Deacon Patrol agent that keeps Term -- The Town running in a loop

see in context
Term -- The Deacon

Term -- The Town level character

see in context
Work Level -- Town

^ Work Level -- Term -- The Town

see in context
spaced repetition prompts - blog section 12 - Patrols

What level of plugins does The Deacon run? ? Term -- The Town-level plugins.

see in context
spaced repetition prompts - blog section 4 - Gas Town 101

What does Term -- The Town orchestrate? ? All agents — workers, patrols, and management — across all Rigs.

see in context

Where does Term -- The Town live on disk? ? A directory like ~/gt, with project Rigs underneath it.

see in context

What is Term -- The Town implemented as? ? A Go binary called gt, kept in its own repo.

see in context

How does a Rig relate to a git repo? ? Each Rig is a git repo placed under Term -- The Town management.

see in context

Term -- The TownTerm -- The Town

Term -- The Town
Term -- The Town