docs: clarify stream engine model, reduce swarm terminology (gt-wexr)
Gas Town is a stream engine, not a swarm engine. Polecats can start and land independently at any time. "Swarm" is used lightly for batch coordination, but there are no swarm IDs or batch boundaries. Changes: - architecture.md: Add stream engine intro paragraph, update references from "swarming" to "parallel polecats" or "batch" - prompts.md: Rename SWARM_* messages to BATCH_*, update terminology - crew.md.tmpl: Replace "swarm" references with "transient worker pool" and "batch work" The gt swarm command and internal/swarm/ package remain as-is since they provide the tooling for batch operations. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -18,7 +18,7 @@ Delivered via `gt prime` command. These establish agent identity and capabilitie
|
||||
|
||||
| Role | Template | Purpose |
|
||||
|------|----------|---------|
|
||||
| Mayor | `mayor.md` | Global coordination, swarm dispatch, cross-rig decisions |
|
||||
| Mayor | `mayor.md` | Global coordination, work dispatch, cross-rig decisions |
|
||||
| Witness | `witness.md` | Worker monitoring, nudging, pre-kill verification, session cycling |
|
||||
| Refinery | `refinery.md` | Merge queue processing, PR review, integration |
|
||||
| Polecat | `polecat.md` | Implementation work on assigned issues |
|
||||
@@ -27,16 +27,16 @@ Delivered via `gt prime` command. These establish agent identity and capabilitie
|
||||
|
||||
### 2. Mail Templates (Structured Messages)
|
||||
|
||||
Parseable messages for swarm pipeline communication.
|
||||
Parseable messages for worker coordination.
|
||||
|
||||
| Template | Flow | Purpose |
|
||||
|----------|------|---------|
|
||||
| `SWARM_STARTED` | Refinery → Mayor | Swarm initialized, workers ready |
|
||||
| `BATCH_STARTED` | Refinery → Mayor | Batch initialized, workers ready |
|
||||
| `WORKER_READY` | Worker → Refinery | Worker setup complete |
|
||||
| `WORK_COMPLETE` | Worker → Refinery | Task finished, ready for merge |
|
||||
| `MERGE_CONFLICT` | Refinery → Worker/Mayor | Merge failed, needs resolution |
|
||||
| `SWARM_COMPLETE` | Refinery → Mayor | All tasks done |
|
||||
| `SWARM_FAILED` | Refinery → Mayor | Swarm failed, needs intervention |
|
||||
| `BATCH_COMPLETE` | Refinery → Mayor | All tasks done |
|
||||
| `BATCH_FAILED` | Refinery → Mayor | Batch failed, needs intervention |
|
||||
|
||||
### 3. Spawn Injection (Work Assignment)
|
||||
|
||||
@@ -86,7 +86,7 @@ Templates for session cycling and handoffs.
|
||||
- Polecat management commands
|
||||
- Work management and sync commands
|
||||
- Workflow steps (inbox → ready → spawn → monitor → report)
|
||||
- Swarm management commands
|
||||
- Worker management commands
|
||||
- Session end checklist
|
||||
|
||||
**unknown.md.j2** (~20 lines)
|
||||
@@ -420,7 +420,7 @@ Unlike polecats, crew workers have no Witness oversight:
|
||||
|
||||
### Phase 2: Mail Templates
|
||||
1. Define mail template format in Go
|
||||
2. Port swarm pipeline templates
|
||||
2. Port worker coordination templates
|
||||
3. Add handoff and escalation templates
|
||||
|
||||
### Phase 3: Spawn & Lifecycle
|
||||
|
||||
Reference in New Issue
Block a user