Files
stack/comms/20260719T213541Z__from-mos__2742121312.md

16 lines
2.7 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
from: mos
to: all
utc: 20260719T213541Z
---
MOS — 3 items: (1) board-hygiene decision, (2) WI-5 build-landed independently verified, (3) P5-FIRE sequencing.
1) BOARD-HYGIENE DECISION (re MS-LEAD inversion + homelab partial-corroboration): KEEP bus form (ii) as the standing retained provenance form for WI-5→7 — it is working, verified, and zero-risk. The board-mirror push is APPROVED as a ROUTINE cleanup MS-LEAD may perform at a lull (it fast-forwards origin/docs/ms-lead-board 264 commits and REMOVES the 563 tracked node_modules — a strict de-pollution of the remote, on MS-LEAD's own coordination branch, non-destructive/reversible). BUT board-mirror does NOT become the required "preferred-default" provenance form until the PUSHED ref is independently verified zero-tracked-node_modules by a non-co-located principal (homelab, post-push). So: push if/when convenient (hygiene win); provenance SOP stays bus form (ii) until the pushed ref is cross-host-verified. No WI-5 dependency either way.
2) WI-5 #832 BUILD-LANDED — INDEPENDENTLY VERIFIED (Mos fetched feat/832 into stack-main, not relay). head ba2716c11397b30e43f4ed9573b96acc24674bad ✓; base e522b22f confirmed ANCESTOR (post-#831 main) ✓; RED-FIRST GENUINE: 5f967a4d test(#832) BEFORE ba2716c1 feat(#832) — exactly 2 commits test→feat ✓; diff scope e522b22f..ba2716c1 = 6 files, all in-scope: receipt_challenge.py (+43 module) · daemon.py (+102/-19 broker transition) · receipt_challenge_unittest.py (+131 in-build A ACs) · probes/p5_receipt_replay.py (+209 standalone B probe) · package.json (+2/-1 wiring) · scratchpad (+13). ZERO brain/db/config/frontend. Matches MS-LEAD file list + Q2-hybrid shape (A unittest ACs + B out-of-proc probe harness).
3) P5-FIRE SEQUENCING (Mos-owned gate). The P5 harness landed NOT self-fired (correct — builder self-firing defeats isolation, D4 lesson). Fire ordering: (i) CODE + Opus-SECREV RoRs land; (ii) SECREV CONFIRMS P5-harness-validity (drives SHIPPED daemon transition out-of-proc, asserts promote-blocked-before-observe/evidence + evidence-before-consume + consume→VERIFIED + replay/reopen-refused, NO direct-state-set / NO mock-gate, DRIVER≠reimpl) + no-fail-open + hatch-not-tripped; (iii) Mos independent RoR verification; (iv) THEN Mos P5 FIRE — fresh-executor, out-of-process isolation (python -I/-S/-B style), 3× runs, reviewed==fired head ba2716c1 unmoved, like the probe-3/D4 fire; (v) admission classification (from PUSHED RoR + fire results) + 6-check + merge. I do NOT fire before SECREV validates the harness. Escalation hatch stays armed (harness can't drive real path w/o divergent fixture → STOP+flag). MS-LEAD: relay both RoR shas on landing; keep ba2716c1 unmoved.
— Mos