Replace 'gastown' with 'greenplace' in user-facing docs/examples

Using "greenplace" (The Green Place from Mad Max: Fury Road) as the
canonical example project/rig name in documentation and help text.
This provides a clearer distinction from the actual gastown repo name.

Changes:
- docs/*.md: Updated all example paths and commands
- internal/cmd/*.go: Updated help text examples
- internal/templates/: Updated example references
- Tests: Updated to use greenplace in example session names

Note: Import paths (github.com/steveyegge/gastown) and actual code
paths referencing the gastown repo structure are unchanged.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Steve Yegge
2025-12-30 18:02:45 -08:00
parent 708cdb2b24
commit 91fa5e63dc
31 changed files with 187 additions and 187 deletions

View File

@@ -23,7 +23,7 @@ Full work unit reference (HOP protocol):
```
hop://entity/chain/rig/issue-id
hop://steve@example.com/main-town/gastown/gt-xyz
hop://steve@example.com/main-town/greenplace/gp-xyz
```
Cross-repo reference (same platform):
@@ -36,9 +36,9 @@ beads://github/acme/backend/ac-123
Within a workspace, short forms are preferred:
```
gt-xyz # Local (prefix routes via routes.jsonl)
gastown/gt-xyz # Different rig, same chain
./gt-xyz # Explicit current-rig ref
gp-xyz # Local (prefix routes via routes.jsonl)
greenplace/gp-xyz # Different rig, same chain
./gp-xyz # Explicit current-rig ref
```
See `~/gt/docs/hop/GRAPH-ARCHITECTURE.md` for full URI specification.
@@ -80,7 +80,7 @@ Distribute work across workspaces:
{
"type": "delegation",
"parent": "hop://acme.com/projects/proj-123",
"child": "hop://alice@example.com/town/gastown/gt-xyz",
"child": "hop://alice@example.com/town/greenplace/gp-xyz",
"terms": { "portion": "backend", "deadline": "2025-02-01" }
}
```
@@ -94,17 +94,17 @@ complete BD_ACTOR format convention.
```bash
# Set per agent session
GIT_AUTHOR_NAME="gastown/crew/joe"
GIT_AUTHOR_NAME="greenplace/crew/joe"
GIT_AUTHOR_EMAIL="steve@example.com" # Workspace owner
```
Result: `abc123 Fix bug (gastown/crew/joe <steve@example.com>)`
Result: `abc123 Fix bug (greenplace/crew/joe <steve@example.com>)`
### Beads Operations
```bash
BD_ACTOR="gastown/crew/joe" # Set in agent environment
bd create --title="Task" # Actor auto-populated
BD_ACTOR="greenplace/crew/joe" # Set in agent environment
bd create --title="Task" # Actor auto-populated
```
### Event Logging
@@ -115,8 +115,8 @@ All events include actor:
{
"ts": "2025-01-15T10:30:00Z",
"type": "sling",
"actor": "gastown/crew/joe",
"payload": { "bead": "gt-xyz", "target": "gastown/polecats/Toast" }
"actor": "greenplace/crew/joe",
"payload": { "bead": "gp-xyz", "target": "greenplace/polecats/Toast" }
}
```
@@ -131,7 +131,7 @@ Each workspace has identity metadata:
{
"owner": "steve@example.com",
"name": "main-town",
"public_name": "steve-gastown"
"public_name": "steve-greenplace"
}
```
@@ -161,7 +161,7 @@ bd list --org=acme.com
bd list --project=proj-123 --include-delegated
# Agent's full history
bd audit --actor=gastown/crew/joe
bd audit --actor=greenplace/crew/joe
```
## Implementation Status

View File

@@ -205,7 +205,7 @@ attached_at: <timestamp>
Examples:
```
POLECAT_DONE nux
MERGE_READY gastown/nux
MERGE_READY greenplace/nux
HELP: Polecat stuck on test failures
🤝 HANDOFF: Schema work in progress
```
@@ -222,9 +222,9 @@ Format: `<rig>/<role>` or `<rig>/<type>/<name>`
Examples:
```
gastown/witness # Witness for gastown rig
beads/refinery # Refinery for beads rig
gastown/polecats/nux # Specific polecat
greenplace/witness # Witness for greenplace rig
beads/refinery # Refinery for beads rig
greenplace/polecats/nux # Specific polecat
mayor/ # Town-level Mayor
deacon/ # Town-level Deacon
```
@@ -314,8 +314,8 @@ Witness-N ──┘
gt mail send <addr> -s "Subject" -m "Body"
# With structured body
gt mail send gastown/witness -s "MERGE_READY nux" -m "Branch: feature-xyz
Issue: gt-abc
gt mail send greenplace/witness -s "MERGE_READY nux" -m "Branch: feature-xyz
Issue: gp-abc
Polecat: nux
Verified: clean"
```

View File

@@ -43,7 +43,7 @@ bd create --type=event --event-type=patrol.muted \
# System entered degraded mode
bd create --type=event --event-type=mode.degraded \
--actor=system:daemon --target=rig:gastown \
--actor=system:daemon --target=rig:greenplace \
--payload='{"reason":"tmux unavailable"}'
```
@@ -230,10 +230,10 @@ Boot specifically:
```bash
# System entered degraded mode
bd create --type=event --event-type=mode.degraded \
--actor=system:daemon --target=rig:gastown \
--actor=system:daemon --target=rig:greenplace \
--payload='{"reason":"tmux unavailable"}'
bd update role-gastown --add-label=mode:degraded --remove-label=mode:normal
bd update role-greenplace --add-label=mode:degraded --remove-label=mode:normal
```
## Configuration vs State

View File

@@ -31,7 +31,7 @@ Gas Town routes beads commands based on issue ID prefix. You don't need to think
about which database to use - just use the issue ID.
```bash
bd show gt-xyz # Routes to gastown rig's beads
bd show gp-xyz # Routes to greenplace rig's beads
bd show hq-abc # Routes to town-level beads
bd show wyv-123 # Routes to wyvern rig's beads
```
@@ -42,7 +42,7 @@ prefix maps to its beads location (the mayor's clone in that rig).
| Prefix | Routes To | Purpose |
|--------|-----------|---------|
| `hq-*` | `~/gt/.beads/` | Mayor mail, cross-rig coordination |
| `gt-*` | `~/gt/gastown/mayor/rig/.beads/` | Gastown project issues |
| `gp-*` | `~/gt/greenplace/mayor/rig/.beads/` | Greenplace project issues |
| `wyv-*` | `~/gt/wyvern/mayor/rig/.beads/` | Wyvern project issues |
Debug routing: `BD_DEBUG_ROUTING=1 bd show <id>`

View File

@@ -50,13 +50,13 @@ independent tasks, a swarm lets you:
```bash
# Create swarm from existing epic
gt swarm create gastown --epic gt-abc --worker Toast --worker Nux
gt swarm create greenplace --epic gp-abc --worker Toast --worker Nux
# Create and start immediately
gt swarm create gastown --epic gt-abc --worker Toast --start
gt swarm create greenplace --epic gp-abc --worker Toast --start
# Specify target branch (defaults to main)
gt swarm create gastown --epic gt-abc --worker Toast --target develop
gt swarm create greenplace --epic gp-abc --worker Toast --target develop
```
The epic should already exist in beads with child tasks. The swarm will track
@@ -66,7 +66,7 @@ which tasks are ready, in-progress, and complete.
```bash
# Start a previously created swarm
gt swarm start gt-abc
gt swarm start gp-abc
```
This transitions the swarm from `created` to `active` and begins dispatching
@@ -76,10 +76,10 @@ tasks to workers.
```bash
# Human-readable status
gt swarm status gt-abc
gt swarm status gp-abc
# JSON output
gt swarm status gt-abc --json
gt swarm status gp-abc --json
```
Shows:
@@ -96,11 +96,11 @@ Shows:
gt swarm list
# Swarms in specific rig
gt swarm list gastown
gt swarm list greenplace
# Filter by status
gt swarm list --status=active
gt swarm list gastown --status=landed
gt swarm list greenplace --status=landed
# JSON output
gt swarm list --json
@@ -110,10 +110,10 @@ gt swarm list --json
```bash
# Auto-dispatch next ready task to idle polecat
gt swarm dispatch gt-abc
gt swarm dispatch gp-abc
# Dispatch in specific rig
gt swarm dispatch gt-abc --rig gastown
gt swarm dispatch gp-abc --rig greenplace
```
Finds the first unassigned ready task and assigns it to an available polecat.
@@ -123,7 +123,7 @@ Uses `gt sling` internally.
```bash
# Manually land completed swarm
gt swarm land gt-abc
gt swarm land gp-abc
```
This:
@@ -139,7 +139,7 @@ This:
### Cancel a Swarm
```bash
gt swarm cancel gt-abc
gt swarm cancel gp-abc
```
Marks the swarm as cancelled. Does not automatically stop sessions or clean up
@@ -197,22 +197,22 @@ If code is at risk, landing blocks and notifies Mayor.
```bash
# 1. Create epic with tasks in beads
bd create --type=epic --title="Add authentication" --id gt-auth
bd create --title="Add login form" --parent gt-auth
bd create --title="Add session management" --parent gt-auth
bd create --title="Add logout flow" --parent gt-auth
bd create --type=epic --title="Add authentication" --id gp-auth
bd create --title="Add login form" --parent gp-auth
bd create --title="Add session management" --parent gp-auth
bd create --title="Add logout flow" --parent gp-auth
# 2. Create swarm
gt swarm create gastown --epic gt-auth --worker Toast --worker Nux --start
gt swarm create greenplace --epic gp-auth --worker Toast --worker Nux --start
# 3. Monitor progress
gt swarm status gt-auth
gt swarm status gp-auth
# 4. Dispatch more as tasks complete
gt swarm dispatch gt-auth
gt swarm dispatch gp-auth
# 5. Land when complete
gt swarm land gt-auth
gt swarm land gp-auth
```
## Troubleshooting

View File

@@ -272,7 +272,7 @@ Digests feed into the activity feed for observability:
```json
{
"type": "digest",
"agent": "gastown/witness",
"agent": "greenplace/witness",
"timestamp": "2025-12-30T10:00:00Z",
"summary": "Patrol cycle 47 complete",
"metrics": {