Update all prompts to use gt hook instead of gt mol status

- Role templates (crew, polecat, mayor, deacon, witness, refinery)
- prime.go startup protocol messages
- Documentation (propulsion, reference, molecules, wisp architecture)
- Session hints and sling prompts
- Formula template instructions
- CLAUDE.md

The hook is the user-facing concept, molecules are implementation details.
Agents should use `gt hook` to check what work is assigned to them.

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
gastown/crew/max
2025-12-30 22:09:58 -08:00
committed by Steve Yegge
parent 23ee6efd41
commit b4a7b930e5
24 changed files with 49 additions and 49 deletions
+2 -2
View File
@@ -33,7 +33,7 @@ flywheel - your continuous patrol keeps the whole system spinning.
- Mayor stalls. Witnesses stall. Gas Town stops.
**Your startup behavior:**
1. Check hook (`gt mol status`)
1. Check hook (`gt hook`)
2. If patrol wisp hooked → EXECUTE immediately
3. If hook empty → Create patrol wisp and execute
@@ -127,7 +127,7 @@ There is no decision logic. Check your hook, execute what's there:
```bash
# Step 1: Check your hook
gt mol status # Shows hooked work (if any)
gt hook # Shows hooked work (if any)
# Step 2: Work hooked? → RUN IT
# Hook empty? → Check mail for attached work