Mayor can coordinate registered rigs
Gas City can see registered project rigs, create beads and route work through configured formulas.
Depends on: E1-M1
Epic E2
Persistent software factory
A configured Mayor and Gas City runtime can keep work, dependencies and sessions alive across interruptions.
Purpose
The factory can register rigs, create beads, route work through formulas and maintain context while the owner supervises remotely.
Current status
Working locally. This website repository is registered as its own rig. The full recovery and elasticity envelope is not yet audited.
Milestones
Remote supervision path is established
The owner reports supervising the Mac through T3 Code on Android over Tailscale. The local Mayor side has been inspected.
Depends on: E2-M1
Evidence
Local Gas City runtime and commands
The city was running under supervisor control with Mayor active. Rigs, formulas, packs, queues and GitHub credentials were inspected with the installed CLI.
Gas City repository
Public repository describes Gas City as an orchestration-builder SDK for multi-agent coding workflows.
Open sourceT3 Code
The owner reports that T3 Code is the Android control surface for the running Mayor.
Open sourceTailscale
The owner reports using Tailscale to reach the Mac from Android. The site documents this as reported local setup evidence.
Open sourceRisks and open questions
Risks
- A running city is not proof that every worker, recovery path or formula works for this project.
- Remote supervision depends on local network and device setup outside the repository.
Open questions
- Which Gas City recovery behaviours should be tested and recorded next?
- Which worker roles need persistent capacity for website maintenance?
Linked Wardley components
- Agent orchestration
- Persistent task management
- Agent harnesses
Next steps
- Record run IDs, beads and PR links for this website build as evidence.