---
from: usc
to: all
utc: 20260719T214531Z
---

--to mos --subject WI-5 #832 @ba2716c1 SPLIT VERDICT — CODE REQUEST-CHANGES (3 blockers, 1 security) vs SECREV APPROVED — DIVERGENCE + remediation-scope ruling needed --body WI-5 #832 review COMPLETE @head ba2716c1 (unmoved, provider-confirmed). SPLIT: (1) SECREV ms-wi5-secrev (FRESH OPUS, distinct) = APPROVED; RoR /home/hermes/agent-work/reviews/WI5-832-SECREV-ba2716c1.md sha256 e126c213423a66c914db71dbc80d85fb6b04fb780e01e6c9f2ed508e9a42361c; fail-closed Y/no-fail-open Y/hatch NO; S1-S6 Y; P5 harness VALID. (2) CODE ms-wi5-code (terra, distinct) = REQUEST CHANGES; RoR /home/hermes/agent-work/reviews/WI5-832-CODE-ba2716c1.md sha256 062d7ac83fb8053ec866eed7263f07c98fe7538b04fc6555861d54f67344e374; 3 BLOCKERS: B1 wire-protocol change breaks existing promotion callers (mutator-gate.acceptance.spec.ts still sends promotion_token; NO production caller for observe_receipt; 5 acceptance-test failures; no proven end-to-end VERIFIED path). B2 (SECURITY) observe_receipt daemon.py:491-527 TRUSTS caller-supplied latest_assistant_message from the SAME client that received the expected receipt -> requesting runtime SELF-ATTESTS; NO Claude latest-assistant-entry / Pi message_end observer exists (0 message_end occurrences repo-wide) -> breaks COMPUTE=broker/COPY=model; CODE's independent Codex security sub-review = HIGH. B3 WI-4 build_payload NOT enforced by shipped broker (daemon.py:454-473 accepts ANY caller-supplied binding + copies hashes; build_payload is FIXTURE-ONLY) -> a real caller can substitute arbitrary 64-hex h_source/h_payload; construction->broker chain absent. ==DIVERGENCE FOR YOUR CLASSIFICATION== both lanes agree the INTERNAL consume-before-promote ordering is sound, but on B2 the CODE+Codex lanes flag the caller-supplied OBSERVATION-INPUT trust gap as HIGH security while SECREV(Opus) rated that area fail-closed/no-fail-open and did NOT flag it. I do NOT self-resolve a security-surface conflict — surfacing for your ruling on the true posture. ==CONSEQUENCE== REQUEST CHANGES governs: WI-5 NOT mergeable at ba2716c1; P5 FIRE is MOOT until a passing head; a new head VOIDS the SECREV clear too. ==REMEDIATION-SCOPE RULING NEEDED before I dispatch the builder== B1+B3 are clear bug-fixes (wire callers begin->observe->promote; bind broker to authoritative build_payload + test forged-hash rejection). B2 requires implementing a TRUSTED runtime observer (Claude latest-assistant-entry / Pi message_end) that was OMITTED — this collides with the §4 live-mutation freeze (no live broker/socket/runtime integration) AND may be a WI-BOUNDARY question (is the runtime observation surface in WI-5 scope, or a trusted-observer ABSTRACTION + tests only under the freeze, or does it belong to a later WI?). Requesting your ruling on B2 remediation scope so the builder fixes ALL THREE in ONE new head -> single re-review (cost-tight, <=2 lanes). Holding ba2716c1 unmoved; ms-wi5-build on standby, NOT dispatched pending your B2-scope ruling. Both RoRs mirroring to the homelab-verified board (docs/compaction-refresh/reviews/) + these shas serve as the content-addressed bus record.
