From 59da73c01364558ccf634e45f9a51ac0115efdcb Mon Sep 17 00:00:00 2001 From: mollusk Date: Fri, 7 Aug 2026 22:15:03 -0400 Subject: [PATCH] docs: the phase-5 gate passed, so stop telling phase 6 it is blocked MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The plan's two status lines both predated the gate's second run. The header still read "approved to start Phase 0a" nine phases in, and the DAG note still claimed the re-run had not happened and that phase 6 waits on a passing results file. That file has existed since 2026-07-26 โ€” screenshare-audio-exclusion-phase5-results.md records GATE PASSED on run 2 with all 13 ยง5.1 rows, including rows 4 and 5 at the real tagging sites. Both lines now state what actually blocks phase 6: the 0c -> 0d -> 6 edge, with 0c step 2 still open (S1/S2 merged, S3a built but unmerged, S3b/S4/S5 not started) and 0d unbuilt. The superseded 2026-07-25 note is kept for the trail rather than deleted. Docs only; no code or gate changes. Co-Authored-By: Claude Opus 5 --- docs/screenshare-audio-exclusion-impl-plan.md | 30 +++++++++++++------ 1 file changed, 21 insertions(+), 9 deletions(-) diff --git a/docs/screenshare-audio-exclusion-impl-plan.md b/docs/screenshare-audio-exclusion-impl-plan.md index c66393a..3fe55d5 100644 --- a/docs/screenshare-audio-exclusion-impl-plan.md +++ b/docs/screenshare-audio-exclusion-impl-plan.md @@ -1,7 +1,12 @@ # Implementation plan: whole-desktop screen-share audio without self-echo -**Status:** ๐ŸŸข **v4 โ€” three review rounds applied. Approved to start Phase 0a.** -**Date:** 2026-07-21 +**Status:** ๐ŸŸข **v4 โ€” three review rounds applied.** *Progress as of 2026-08-07:* phases 0a, 0b, +0c step 1, 1, 2, 3, 3r, 4 and 5 are merged, and the **phase-5 major gate PASSED on 2026-07-26** +(ยง1). The current front is **0c step 2**, sliced S1โ€“S5: S1 and S2 merged, **S3a built but +unmerged** (pixelpass `s3a-module-ledger`), S3b/S4/S5 not started. **0d and phases 6โ€“9 are not +built** โ€” nothing merged to date mutates the graph, so the feature has no user-visible behaviour +yet. Phase 6 is the first mutation. +**Date:** 2026-07-21 (v4); status line refreshed 2026-08-07 **Design of record:** [`screenshare-audio-exclusion-plan.md`](screenshare-audio-exclusion-plan.md) v3.4 (`8768cd2`), converged round 7. **Scope:** *ordering, gates and acceptance criteria only.* @@ -100,13 +105,20 @@ if it differs, failing closed. 1 (r8 carriers) โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ–บ 5 (re-run) ``` -โš ๏ธ **Status 2026-07-25 (evening): 3r is BUILT AND MERGED; the re-run has not happened yet.** -The phase-5 gate failed on its first live run and put 3r into the DAG; 3r's own four-part -gate now passes, including the live prop-recovery row on this host. Phase 5's machinery is -built and correct โ€” it is the audit that found the defect, twice โ€” so "5 (re-run)" is a -*re-run of the matrix*, not a rebuild. **Phase 6 still does not start** until a passing -results file exists. **Phase 1 is a hard prerequisite of the re-run for both carriers** -(plan ยง3). +โœ… **Status 2026-07-26: the phase-5 gate PASSED on run 2 โ€” all 13 ยง5.1 rows completed.** +Record: [`screenshare-audio-exclusion-phase5-results.md`](screenshare-audio-exclusion-phase5-results.md) +(audit build pixelpass `main` @ `91c4ded`, release profile). Phase 1 was the hard prerequisite +of the re-run for both carriers (plan ยง3) and was satisfied โ€” rows 4 and 5 passed at the real +tagging sites. **Phase 6 is no longer blocked by this gate.** What still blocks it is the rest +of the DAG: `0b โ†’ 6` is satisfied and merged, but `0c โ†’ 0d โ†’ 6` is not โ€” **0c step 2 remains +open** (S1 and S2 merged; S3a built but UNMERGED on pixelpass `s3a-module-ledger`; S3b, S4 and +S5 not started), and **0d has not been built at all**. + +โš ๏ธ **Superseded, kept for the trail โ€” status 2026-07-25 (evening): "3r is BUILT AND MERGED; the +re-run has not happened yet."** The phase-5 gate failed on its first live run and put 3r into +the DAG; 3r's own four-part gate then passed, including the live prop-recovery row on this host. +Phase 5's machinery was built and correct throughout โ€” it is the audit that found the defect, +twice โ€” so "5 (re-run)" was a *re-run of the matrix*, not a rebuild. Run 2 is that re-run. โš ๏ธ **A smoke run of the audit against the fixed observer immediately found a second defect (design v3.6 ยง6.8): a fail-closed `unresolved-ancestry` mark was being promoted to permanent