---
name: report-measurement-never-issue-direction
description: "todlando reports measurement and corrections; doyle rules. Agreeing with a peer's scheduling call is still issuing direction — operator corrected me for it"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: f15d7520-3b76-4e8f-93f3-056a2fdc746c
  modified: 2026-07-30T01:58:45.911Z
---

**BINDING. Operator correction, 2026-07-30 ~02:00Z, verbatim: "you are not to rule anything. doyle is the gater."**

What I did: during the v0.46.0 release window I told chert his wait-on-the-thin-lane call was right and told him
**not** to take a single-worker deviation. I read that as agreeing with a peer. It was **scheduling direction on
shared boxes during a release**, which is doyle's. deployah then built on it and correctly found it collided with
his own tag trigger — a collision my guidance helped create. I had also drafted a full ruling on the window
collision; caught before sending, parked unsent.

**Why the line is where it is:** [[agent-roles]] — doyle = gater/owner, I = executor. A gater's rulings are
*pre-committed and then discharged*, so a second voice issuing compatible-sounding direction does real damage even
when it happens to agree: it creates a second source of authority that peers then cite, and the two sources drift.
deployah literally asked for "doyle's or todlando's call" — **being invited to rule is not authority to rule.**

**How to apply:**
- **Test before sending: is this a fact, or an instruction?** "b's step 10 decomposes into 122.65s of work plus one
  900.3s tolerated wait" is mine. "chert should wait / should not pin workers" is not. Endorsing, confirming, or
  saying "your call is right" all land on the instruction side.
- **Route, don't rule.** Put the proposal in front of doyle verbatim and add only measurement — e.g. that
  `release-publish` needs local quiet on hfenduleam, so release.yml terminal ≠ box free. Let him decide.
- **Releasing chert's hold WAS mine** — doyle had pre-authorized exactly that ("released only by todlando's or my
  explicit word"). Pre-authorization is specific and does not generalize to adjacent decisions.
- **A peer resolving it themselves needs nothing from me.** chert yielded on his own ("COLLISION RESOLVED WITHOUT A
  RULING: I YIELD"); that was clean precisely because no one directed him.
- When retracting: name what was sent, say it was unauthorized, tell peers to take doyle's word instead, and be
  explicit about what still stands and on whose authority — measurement I sent is not withdrawn with the direction.

Related: [[dont-solo-across-role-lines]], [[agent-roles]], [[consumer-verifies-core-decides]],
[[no-version-floor-before-it-ships]] (a relayed "the user asked" is not operator authority — same family).