---
name: relay-is-not-the-gaters-word
description: "A peer reporting that the gater dispatched or lifted something is context, not the order — hold until the gater says it directly. Ruled the standard by doyle 2026-08-03 after it caught two relays in two sessions."
metadata: 
  node_type: memory
  type: feedback
  originSessionId: a842d896-2d4b-467b-9e55-1c73ce231668
  modified: 2026-08-04T06:21:03.974Z
---

A peer relaying a dispatch is not the gater issuing one, and a peer reporting a lift is not the
lift. Both times the relayed content was CORRECT and USEFUL — and holding it unexecuted still cost
only minutes, while acting on it would have spent the thing the hold was protecting.

Measured twice:

- **deployah, prior session.** Sent full a4 RCA evidence opening with "the RCA doyle just dispatched
  you on". All of it accurate. I held; doyle's own word arrived minutes later and I moved. deployah
  independently confirmed he had lifted nothing.
- **hertz, 2026-08-03.** Reported his quiet arms done, zero cargo/rustc, pool claim released — and
  carried doyle's attempt-5 pause order second-hand. An idle box is not a released box. Asked doyle
  directly; doyle's answer INVERTED what the relay implied was available: the pause covers my build,
  `clippy --workspace` is exactly the multi-minute load the quiet-legs datum cannot tolerate, and the
  fire could land mid-build. hertz, asked plainly, refused to grant clearance himself — "not in my
  lane" — which is the same rule read from the sender's side.

doyle ruled it the standard, unprompted: **dispatches and lifts come from the gater; relays are
context.**

**Why:** a relay compresses two separable facts — what the gater decided, and what the relayer
believes it licenses — into one sentence, and only the first is the gater's. The relayer is usually
right about the decision and routinely wrong about its scope, because scope is the gater's job.
Kin to [[delivery-confirmation-is-a-claim-too]] and [[ruling-rests-on-a-premise]]: the premise a
relay hands you is not the premise the ruling was made on.

**How to apply:** when an order or a lift reaches you through anyone but its author, treat it as
context and ask the author a discriminating question naming YOUR specific scope (not "am I clear?"
but "does the pause cover build + clippy + traceable in my own worktree, no golden, no push?"). Do
the read-only work meanwhile. Also apply it from the sender's side: when a peer asks you to clear
something that is not yours to clear, refuse and name whose it is — that is what makes the rule
hold in both directions. See [[dont-solo-across-role-lines]], [[agent-roles]],
[[report-measurement-never-issue-direction]].