peer-sessions
Peer Sessions
Split work across a few peers, each reading a brief by path and writing one structured reply by path. The run directory is the ledger, not the transcript: it survives a restart, and native messages only wake the coordinator. The smallest coherent shape is one local worker or one bounded check; add peers, two to four with disjoint ownership, only when independent work saves time or improves evidence.
Plan
Pick one pattern unless a dependency needs two:
| Need | Pattern |
|---|---|
| Inspect independent files, claims, or hypotheses | Fan out and synthesize |
| Challenge a high-impact result | Adversarial verification: give the verifier the evidence and rubric, not the worker's conclusion |
| Generate options, then rank them | Generate and filter, or a tournament |
| Search an unknown amount of work | Loop in batches until done |
Give each peer a narrow objective, an absolute working directory, a disjoint write scope, and a deadline; use a worktree when parallel edits could collide. External side effects and destructive operations stay with the coordinator.
Route each peer with python3 shared/scripts/model_routing.py resolve <route> --provider <host> for its kind of work (routes lists them), unless the user names models. Show the pattern, each peer with its scope, model, effort, and host route, the deadline, and the batch ceiling. Ask: "Approve this plan, or specify changes."