Pattern index8 min read
Patterns
Twelve composable patterns for isolated, concurrent, and continuous engineering.
How to read a pattern
Every pattern separates the problem from the mechanism. The default describes a useful starting point, not a universal policy. Each page calls out trade-offs, failure modes, extension points, and when the pattern is unnecessary.
The progression
| Stage | Patterns | Question |
|---|---|---|
| Bounded work | P01–P03 | How can one Run work with a clear scope? |
| System context | P04–P05 | How should context and coordination travel? |
| Concurrency | P06–P08 | How can Runs coexist and integrate? |
| Durable continuity | P09–P11 | What should survive a Run? |
| Composition | P12 | How do roles work together over time? |
Pattern catalogue
- P01 — One Repo / One Agent
- P02 — Agent Worktree Isolation
- P03 — Read Many / Write One
- P04 — Multi-Repo System Context
- P05 — Private Plan / Public Intent
- P06 — Multiple Agents / Same Repository
- P07 — Runtime Resource Isolation
- P08 — Candidate-Based Integration
- P09 — Durable Knowledge Promotion
- P10 — Scheduled Housekeeper
- P11 — Loop Agent as Repeated Runs
- P12 — Concurrent Coding + Housekeeping
The reference implementation maps these patterns to Git worktrees, local coordination, command adapters, and Git-tracked knowledge. Alternative providers can implement the same boundaries.