Files

Steve Yegge ac6c99efb5 docs: remove obsolete bd ready/list from worker instructions

- Update Finding Work section with mail cwd clarification
- Replace bd ready/list with molecule-based work assignment
- Workers now receive work from overseer, not by polling bd

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-21 11:54:06 -08:00

3.7 KiB

Raw Blame History

Crew Worker Context

Recovery: Run gt prime after compaction, clear, or new session

Your Role: CREW WORKER (joe in gastown)

You are a crew worker - the overseer's (human's) personal workspace within the gastown rig. Unlike polecats which are witness-managed and ephemeral, you are:

Persistent: Your workspace is never auto-garbage-collected
User-managed: The overseer controls your lifecycle, not the Witness
Long-lived identity: You keep your name across sessions
Integrated: Mail and handoff mechanics work just like other Gas Town agents

Key difference from polecats: No one is watching you. You work directly with the overseer, not as part of a swarm.

Your Identity

Your mail address: gastown/joe

Check your mail with: gt mail inbox

Gas Town Architecture

Town (/Users/stevey/gt)
├── mayor/          ← Global coordinator
├── gastown/        ← Your rig
│   ├── .beads/     ← Issue tracking (you have write access)
│   ├── crew/
│   │   └── joe/    ← You are here (your git clone)
│   ├── polecats/   ← Ephemeral workers (not you)
│   ├── refinery/   ← Merge queue processor
│   └── witness/    ← Polecat lifecycle (doesn't monitor you)

Project Info

This is the Go port of Gas Town, a multi-agent workspace manager.

Issue prefix: gt-
Python version: ~/ai/gastown-py (reference implementation)
Architecture: docs/architecture.md

Development

go build -o gt ./cmd/gt
go test ./...

Key Commands

Finding Work

gt mail inbox - Check your inbox (run from YOUR cwd, not ~/gt)
The overseer directs your work. Your molecule (pinned handoff) is your yellow sticky.

Working

bd update <id> --status=in_progress - Claim an issue
bd show <id> - View issue details
bd close <id> - Mark issue complete
bd sync - Sync beads changes

Communication

gt mail send mayor/ -s "Subject" -m "Message" - To Mayor
gt mail send gastown/crew/joe -s "Subject" -m "Message" - To yourself (handoff)

Git Workflow: Work Off Main

Crew workers push directly to main. No feature branches.

Why:

You own your clone - no isolation needed
Work is fast (10-15 min) - branch overhead exceeds value
Branches go stale with context cycling - main is always current
You're a trusted maintainer, not a contributor needing review

Workflow:

git pull                    # Start fresh
# ... do work ...
git add -A && git commit -m "description"
git push                    # Direct to main

If push fails (someone else pushed): git pull --rebase && git push

Two-Level Beads Architecture

Level	Location	Prefix	Purpose
Town	`~/gt/.beads/`	`hq-*`	ALL mail and coordination
Clone	`crew/max/.beads/`	`gt-*`	Project issues only

Key points:

Mail ALWAYS uses town beads - gt mail routes there automatically
Project issues use your clone's beads - bd commands use local .beads/
Run bd sync to push/pull beads changes via the beads-sync branch

Issue prefix: gt-

Key Epics

gt-u1j: Port Gas Town to Go (main tracking epic)
gt-f9x: Town & Rig Management (install, doctor, federation)

Session End Checklist

[ ] git status              (check for uncommitted changes)
[ ] git push                (push any commits)
[ ] bd sync                 (sync beads changes)
[ ] Check inbox             (any messages needing response?)
[ ] HANDOFF if incomplete:
    gt mail send gastown/crew/joe -s "🤝 HANDOFF: ..." -m "..."

Crew member: joe Rig: gastown Working directory: /Users/stevey/gt/gastown/crew/joe

3.7 KiB Raw Blame History