---
name: owl-replyto-forbidden
description: "NEVER use `$OWL send --reply-to` — from-attribution broken (stamps REPLY_TO as sender); plain `$OWL send <target> <self-id>` always"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: d8460aba-1a48-401d-a0c9-4e89c12d5eec
---

`$OWL send --reply-to <sender> <target>` on legacy owl 1.11.25 mis-stamps the FROM attribution:
the recipient sees `from=<REPLY_TO value>` (their own id), not the actual sender. Pinned 2026-07-01
with doyle via a controlled pair (reply-to ack arrived from="doyle" to doyle; explicit-FROM plain
send arrived from="perri" correctly). doyle: the path is BINDING-forbidden on this rig — it also
historically loops messages back to sender.

**Why:** misattributed sender identity corrupts multi-agent coordination (doyle burned an
orchestration round believing a peer authored my ack).

**How to apply:** always `$OWL send <target> <your-id>` with FROM explicit; never pass --reply-to.
The /spt:live skill prose still recommends --reply-to — ignore that recommendation on this rig.
Related: [[v0100-digest-fetcher-shipped]] (same-day arc).