---
name: dont-solo-across-role-lines
description: "BINDING — doyle gates, todlando builds, deployah publishes; don't solo another agent's lane even when they look parked"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: e989445c-9ed7-41d4-83f3-742e31355ca5
---

BINDING (operator corrected doyle TWICE in one session, 2026-07-08): honor the role division — **todlando builds, doyle gates, deployah publishes for release.** doyle soloed the BUILD (wrote the fix edits) then later soloed the RELEASE cut; operator caught both.

**Why:** the division is deliberate. doyle drifting into build/release work isn't efficiency — it erodes the separation the operator set up, and it repeats a bad default. The 0.29.0 "doyle drove the whole cut solo" was an EXCEPTION (deployah genuinely offline + operator-waved for that cut), NOT a standing precedent to fall back on.

**How to apply:**
- Diagnosis + design ruling + gating = doyle's lane. Turning a ruling into landed code = todlando. Bump/tag/sign/publish = deployah.
- When a fix is diagnosed: hand the BUILD to todlando with a spec (revert any draft edits so authorship is clean), then gate.
- When gated + operator says "publish": hand the RELEASE to deployah (merge→tag→sign→publish→ping perri), flag any dependency (e.g. the signing seed — was doyle-env for 0.29.0). Do NOT drive it yourself.
- A parked/offline target is NOT license to solo — `spt send` QUEUES for their next listen; wait for them to pick it up, or ask the operator to wake them. Only solo if the operator explicitly waves it for that instance.

Related: [[agent-roles]], [[dont-wait-proceed-autonomously]] (proceed autonomously WITHIN your lane, not across lanes).