memory: a standing no-announcements ruling — the send is the operator's, not the agent's to ask about

persistent-memory.md

@@ -36,13 +36,23 @@ _As of 2026-09-22:_
   approved, so whoever builds it must DELETE that test in the same commit. It
   will otherwise read as a real invariant and block correct work.
 - **623 tests green. Tree clean and pushed. Deployed; 19/19 booths 200.**
-- ⚠ **THE 17-HANDLE NOTE IS DRAFTED AND STILL NOT SENT** — blocked by the
+- 🛑 **STANDING RULING — NO ANNOUNCEMENTS OUT OF THIS REPO, AND THE OPERATOR
-  auto-mode classifier because it is a multi-recipient send, which CLAUDE.md
+  SENDS THE EVENTUAL ONE HIMSELF** (operator, 2026-09-22). Verbatim: *"no
-  gates on explicit operator approval. The blanket "accept all recs" was read as
+  announcements until the entire arc is done, and even then i'll do it myself."*
-  ratifying the note's CONTENT, not as that specific approval, and the
+  Two clauses, both binding: **(a)** no althing announcement of any kind ships
-  classifier agreed. **Not worked around.** Full draft + recipient list at
+  from booth-dev until the v1 arc is COMPLETE — not per-unit, not at the 1.0
-  `docs/pending/fleet-note-booth-link-refusal.md`; it needs his explicit go or a
+  tag, not "just the peers who consume it"; **(b)** when the arc IS done, the
-  `postbox send` permission rule.
+  announcement is HIS to send, not a thing to ask permission for. This is
+  STRICTER than `~/.claude/CLAUDE.md`'s broadcast gate, which merely requires
+  approval — here the send is not the agent's to make at all, so *asking* is
+  also out of scope. Do not offer, draft-and-await, or surface it as a pending
+  decision; it is settled and not a standing question.
+  **The 17-handle `booth link` note is consequently REASSIGNED, not blocked.**
+  The full draft + recipient list stays at
+  `docs/pending/fleet-note-booth-link-refusal.md` as MATERIAL FOR HIM. It is no
+  longer an open loop, no longer awaiting approval, and no longer a thing to
+  raise. Same for anything U4's `keep`-semantics change would have warranted
+  telling peers.
 - ⚠ **NOT SEEDED, and this survives the blanket ruling.** "No seeding yet" was a
   SPECIFIC prior instruction, not a recommendation of mine, so "accept all recs"
   does not override it. `.benches.json` does not exist in `~/booth-data`.
@@ -62,6 +72,7 @@ _As of 2026-09-22:_
 
 ## Recent decisions
 
+- `[2026-09-22]` 🛑 **STANDING: no announcements out of this repo until the arc is done, and he sends that one himself** — verbatim *"no announcements until the entire arc is done, and even then i'll do it myself."* Stricter than the house broadcast gate: the send is not the agent's to make, so **asking is also out of scope**. The drafted 17-handle note is REASSIGNED to him, not blocked — see the in-flight row above; do not raise it again.
 - `[2026-09-22]` **The operator ruled on all five open items at once** — four executed incl. the first push; the broadcast was blocked by the permission layer and is drafted at `docs/pending/` → `persistent-memory.d/2026-09-22-operator-ruled-on-the-open-five.md`
 - `[2026-09-22]` **U7 is three-quarters built and blocked on one word** — the ratified three landed; the sections-vs-groups departure is NOT built and is the operator's call, tracked at `docs/contracts/u7_navigation.contract.md` → `persistent-memory.d/2026-09-22-u7-three-quarters-and-one-ruling.md`
 - `[2026-09-22]` **An approved directive misrouted because pane_find addresses by a rolling pane title** — resolved; the MECHANISM is the durable part, reported to infra-ops, untracked by booth-dev → `persistent-memory.d/2026-09-22-a-directive-misrouted-by-pane-title.md`