Lane Discipline
In a fleet, two agents touching the same file = merge conflicts, duplicated work, and a muddy history. The check is cheap; the collision is expensive.
The move
- Know your lane. Read the fleet/team rules at session start (e.g.
AGENTS.md, .cursor/rules/00-fleet-team.mdc, .claude/TEAM.md). Know what you own and what each other agent owns.
- Before starting a task, check the lane. Does this file / service / package belong to your lane?
- Yes → proceed, and say so: "instrumenting the training script — within my designated lane".
- Another agent's lane → defer. Surface the task to the owning agent or the user; don't do it yourself.
- Shared / ambiguous → coordinate. Post the intent, get a nod, then proceed. Mark the work as coordinated in your response.
- Make the check audible. State the lane check out loud when you start the task. This makes the boundary visible to the user and to any other agent reading the transcript, and it stops the work from being flagged as out-of-lane later.
- Keep changes non-invasive to other lanes. Prefer guarded, optional, additive changes ("guarded, optional") over rewrites of shared files. A change that another lane can ignore is a change that doesn't collide.
What "lane" means here
A lane is a documented ownership boundary — a set of files, services, or topics one agent is responsible for. Lanes are usually listed in the team rules. Examples from this fleet:
- Cursor: sites, api, scripts, UI, orchestrator patches.
- Claude (terminal):
training_loop.py edits per the delegate doc.
- Eve (worker): fleet ops, hill-climb, weakest-slice retrain.
- Operator: Neon, Railway, Vercel, disk, prod.
If a file touches two lanes (e.g. a shared client used by sites and by the trainer), the change is cross-lane — coordinate.
When to defer even though you "could do it faster"
- The owning agent is active and on the same task. Let them finish.
- The work is in another agent's designated lane, even if they're idle. Surface it; don't grab it.
- The work requires prod credentials or prod state you don't own.
Anti-patterns
- Silent cross-lane edit. You touch
training_loop.py without checking — Claude was mid-edit; merge conflict.
- Grabbing idle-lane work "because it's easy". Easy work in someone else's lane is still their lane.
- Stating the lane check as a question. "I guess this is my lane?" — know your lane; state it.
- Big rewrite of a shared file. Shared files get small, additive, guarded changes; not rewrites.
Pair with
session-orient — recon reads the team rules so the lane map is loaded.background-failure-triage — a failed op in another lane is surfaced, not silently re-tried by you.
1---2name: lane-discipline3description: In a multi-agent fleet, verify a piece of work is in your designated lane before doing it, and state the check out loud. Defer to the owning agent when the work belongs to another lane. Use whenever the repo has documented agent/team role boundaries (AGENTS.md, .cursor/rules/, .claude/TEAM.md, fleet-team rules) and the task touches a shared area.4---56# Lane Discipline78In a fleet, two agents touching the same file = merge conflicts, duplicated work, and a muddy history. The check is cheap; the collision is expensive.910## The move11121. **Know your lane.** Read the fleet/team rules at session start (e.g. `AGENTS.md`, `.cursor/rules/00-fleet-team.mdc`, `.claude/TEAM.md`). Know what you own and what each other agent owns.132. **Before starting a task, check the lane.** Does this file / service / package belong to your lane?14 - **Yes** → proceed, and say so: "instrumenting the training script — within my designated lane".15 - **Another agent's lane** → defer. Surface the task to the owning agent or the user; don't do it yourself.16 - **Shared / ambiguous** → coordinate. Post the intent, get a nod, then proceed. Mark the work as coordinated in your response.173. **Make the check audible.** State the lane check out loud when you start the task. This makes the boundary visible to the user and to any other agent reading the transcript, and it stops the work from being flagged as out-of-lane later.184. **Keep changes non-invasive to other lanes.** Prefer guarded, optional, additive changes ("guarded, optional") over rewrites of shared files. A change that another lane can ignore is a change that doesn't collide.1920## What "lane" means here2122A lane is a documented ownership boundary — a set of files, services, or topics one agent is responsible for. Lanes are usually listed in the team rules. Examples from this fleet:23- Cursor: sites, api, scripts, UI, orchestrator patches.24- Claude (terminal): `training_loop.py` edits per the delegate doc.25- Eve (worker): fleet ops, hill-climb, weakest-slice retrain.26- Operator: Neon, Railway, Vercel, disk, prod.2728If a file touches two lanes (e.g. a shared client used by sites and by the trainer), the change is cross-lane — coordinate.2930## When to defer even though you "could do it faster"3132- The owning agent is active and on the same task. Let them finish.33- The work is in another agent's designated lane, even if they're idle. Surface it; don't grab it.34- The work requires prod credentials or prod state you don't own.3536## Anti-patterns3738- **Silent cross-lane edit.** You touch `training_loop.py` without checking — Claude was mid-edit; merge conflict.39- **Grabbing idle-lane work "because it's easy".** Easy work in someone else's lane is still their lane.40- **Stating the lane check as a question.** "I guess this is my lane?" — know your lane; state it.41- **Big rewrite of a shared file.** Shared files get small, additive, guarded changes; not rewrites.4243## Pair with4445- `session-orient` — recon reads the team rules so the lane map is loaded.46- `background-failure-triage` — a failed op in another lane is surfaced, not silently re-tried by you.
jcdavis131