From 2ae379e6642c9ed4fdaf6cf6d5ccf4c8b3c22faa Mon Sep 17 00:00:00 2001
From: mos-orchestrator <mos-orchestrator@mosaic.local>
Date: Sat, 18 Jul 2026 18:30:49 -0500
Subject: [PATCH] evidence-integrity: mark v7 co-attest SUPERSEDED (homelab
 FAIL @f609a449, B7+B8 raised)

---
 .../reviews/GATE0-PROBE3-MOS-COATTEST-v7.md   | 36 +++++++++++++++++++
 1 file changed, 36 insertions(+)

diff --git a/docs/compaction-refresh/reviews/GATE0-PROBE3-MOS-COATTEST-v7.md b/docs/compaction-refresh/reviews/GATE0-PROBE3-MOS-COATTEST-v7.md
index cf412ad..af6ecfa 100644
--- a/docs/compaction-refresh/reviews/GATE0-PROBE3-MOS-COATTEST-v7.md
+++ b/docs/compaction-refresh/reviews/GATE0-PROBE3-MOS-COATTEST-v7.md
@@ -93,3 +93,39 @@ assertion-FAIL / isolation-FAIL → possible Case-C → STOP + escalate to Jason
 
 **Mos verdict: v7 full-closure byte-scope + mechanism + hygiene PASS. Co-attestation of record —
 committed.**
+
+---
+
+## ⚠️ SUPERSEDED — homelab v7 third-principal FAIL @f609a449 raised a stricter bar (evidence-integrity note)
+
+This co-attestation was **byte-clear on the v7 full-closure bar ONLY** and self-limited above to
+*"byte-clear NOT fire-authorization; FIRE remains gated on homelab third-principal re-verify."*
+Homelab (the required third principal) subsequently returned **FAIL @f609a449** (static verify, no
+code run), and Mos **UPHELD** it after independently confirming both findings in source — so the v7
+byte-clear this document records is **SUPERSEDED** and does **NOT** authorize FIRE.
+
+Two residual isolation/binding holes WITHIN the materialized closure (both independently reproduced
+by Mos in the harness source; accepted as gate-**strengthening**, not softening):
+1. **Broker child env not isolated.** `launch_verified_broker` (`:551`) calls `Popen` with **no
+   `env=`** (only `PiRpc.__init__` `:50` passes an allow-listed `env`) → the broker child inherits
+   ambient `os.environ` (PYTHONPATH/PYTHONHOME/PYTHONPYCACHEPREFIX). `closure_import_guard` is a
+   static AST check and cannot bind the child's runtime stdlib resolution.
+2. **Executed bytecode-cache outside the pin.** No `PYTHONDONTWRITEBYTECODE`/`-I`/`-B`/`__pycache__`
+   handling anywhere. `exec_module` on the pinned helper writes derived `.pyc` the pin never covers;
+   only the `.py` is re-hashed → executed bytecode ≠ pinned-source-hash.
+
+Both break "hashed==executed on the FULL executed closure" on **fidelity** grounds even in a
+non-adversarial fixture. Mos **authorized the bounded repair** (broker `Popen` with strict
+allow-listed `env=` + `-I` + `PYTHON*` stripped; bytecode-cache suppressed via
+`PYTHONDONTWRITEBYTECODE=1`/`-B` + reject stray `__pycache__`/`.pyc` fail-closed before each
+consumer; launcher sibling-import binding to the pinned helper preserved). This **rides the existing
+(ii)-full-closure authorization + R1 + Mos adjudication** — it deepens isolation/binding of an
+already-authorized touch, stays inside the fixture temp root, no fresh Jason owner-window. It is
+**NOT a Case-C escalation** (no probe fired, no evidence produced — a static pre-fire catch, exactly
+what the review gate is for). Added review bars **B7** (broker child env-isolated) and **B8**
+(executed bytecode pinned-or-suppressed) on top of B5+B6+all priors.
+
+**Live target = v8** (env-isolated + bytecode-pinned harness, forthcoming). `f609a449` /
+`2bba933f` / this co-attestation (`e08ad03`) are **SUPERSEDED**. A fresh Mos co-attestation will be
+committed on v8 byte-verify PASS. WI-3 #830 remains HELD at `f4008307`; nothing banked; C-hatch
+armed; NO FIRE.