- Tracking bead progress and status
- Managing bead dependencies
- Collecting attribution data for agent evaluation
Bead Lifecycle
- Created: Bead defined with scope and acceptance criteria
- Assigned: Bead placed on agent's hook
- In Progress: Agent actively working (GUPP enforced)
- Review: Work complete, awaiting merge review
- Done: Merged and verified (
gt done) - Destroyed: Wisps only - cleaned up after landing
Attribution
All work carries persistent attribution:
- Which agent completed the bead
- Time taken and quality score
- Used for A/B testing agent configurations
- Feeds into agent evaluation and scoring
Tool Use
Used within convoy management and orchestrator processes.