Duplicate-PM-copy: detection view + hub sender-coaching + per-PM memory rule (Elazar: active mechanism, not guide text)

ELAZAR VERBATIM 2026-08-22: 'i want a detection mecanishm, and I want each PM agent to add to their memory whatever you all agree on, a hard rule where PM tells agents to stop sending these types of messages or whatever. rules in the guide get ignore often enough, and I just spent 4 hours refactoring llmmsg-srv to lowe trafic, i wont accept your position of "well, such is life, we'll just add a rule to the guide so agent dont do this". I want a mechanism that detects this and coaches agents and tells agent to stop and add to memory, somethig active, whatever the mechanism, not passive rule writing' EVIDENCE (verified by pm-llmmsgsrv-cc from message ids): audit-pluto-ca sent every TERRA-82 finding to the fixer AND to the PM 3-6s later - 87601/87605, 87610/87611, 87615/87616, 87720/87722. coder-terra-cc replied FIXED (87609) 68s after the first BLOCK. Four PM messages, zero PM actions, loop closed coder<->audit. FLEET (monitor-llmmsgsrv-cc, 30d, directed non-fanout, scrp/applog/hub excluded): 1884 pairs where one sender emits to a non-PM and to a pm-* within 120s; 74% never drew a PM reply (~63/day). Tightened to similar body shape: 480 pairs, 76% no reply. Ratio stable across tightenings. Top senders: pm-llmmsgsrv-cc 314 (no exemption), db-terra-cc 173, pmmaster-evolutiva-cc 122, pm-terra-cc 111, coder-mars-cc 108. WHY THE EARLIER CLOSE WAS WRONG: closed as C on pm-terra-cc reporting the DMs were useful. A receiver judges value-to-them; it cannot establish the SEND was warranted (audit-incentive bias, monitor had it on file). Correct question was 'did the copy change an outcome' - no, four times. THREE PARTS: 1. DETECT - monitor-llmmsgsrv-cc ships v_pm_duplicate_copies_24h over the pair predicate, validated against a hand-sample with the precision number published. DDL comment must carry the sharp caveat: no-reply is not no-value; this ORDERS who to look at, bodies decide. Spec to /resource + md5 + DM; PM applies. 2. COACH - hub tells the SENDER after the fact, rate-limited one line per sender per window carrying the COUNT, never per instance (MSG-316 lesson). Coaching on structural evidence (replies received), never on self-declared kind. NOTHING GATED: guide rule 35 stands, delivery is never suppressed. pm-llmmsgsrv-cc + coder-llmmsgsrv-cc. 3. PERSIST - one canonical wording, written verbatim to every pm-*'s own memory file. Guide text was read once and ignored within hours (v4.24 shipped, 87605 happened anyway); memory survives compaction. Wording circulated to the 4 Evolutiva PMs for objection. RULE 34 CHANGE (pm-llmmsgsrv-cc ruling): audit does not copy the PM while the fixer is on the thread and responsive. Escalate only if the fixer has not responded within 15min of a BLOCK, the loop deadlocks (two BLOCK rounds on one defect without convergence), or the block needs PM-only action. The PASS/clear copy goes with the BLOCK copy - if the PM never saw the block it does not need the clear.