Differences

This shows you the differences between two versions of the page.

--- provenance:design:ownership_resolution [2026/09/11 22:40] – Section L: untruncated residue notes, post-correction route counts, and the full reviewer log including the generic pass's 15 findings (14 accepted, 1 rejected). Authored by Claude karel.kubicek.claude
+++ provenance:design:ownership_resolution [2026/09/11 22:45] (current) – Section L.9: the third sweep and the two 2026-09-05 judgement-call bullets it found still stating 69.9%/93.9% in the present tense; dated rather than refreshed. Authored by Claude karel.kubicek.claude
@@ Line 785: / Line 785: @@
 also named the ''%%<WRAP todo>%%'' that still asked for the thing this sitting did;
 that one was **not** yet fixed and has been.
+=== A second sweep, after the generic pass's fixes were published ===
+''sweep_moved_figures.py'' was re-run over a **fresh export of all 182 pages**
+taken after publishing, with five pairs added for figures that carry no ''%'' —
+the class the generic pass showed the sweep was blind to (''42–49''→''54–56'',
+''69.9 vs 73.7''→''69.2 vs 73.9'', ''29 of the 525''→''30 of the 525'',
+''All four were found'', ''9 of 13''→''10 of 12'').
+**69 suspect lines, 68 legitimate and one real.** The content page's
+methodology bullet still said **"29 of the 525 verdicts were changed"**: the
+page carried that figure **twice**, round four fixed the copy in the section it
+was editing, and ''check_tail_figures.py'' could not see the other because it
+asserts a figure is *present* and a correct copy was. The other 68 are
+before/after columns, the published mutation harnesses' own output, the
+-09-05 estimator run this family deliberately preserves as the "before",
+and one coincidental match on an unrelated rater-agreement figure.
+Closed with code rather than with an edit: the guard now derives the total from
+''owner_tail_corrections-output.txt'''s own ''actions: ... rescore=N'' line plus the
+first sitting's 29, asserts both that the right value is present and that the
+superseded one is absent, and the mutation harness reverts **one** copy to prove
+it bites. Control: run against the pre-fix export, it fails on exactly that
+line.
+**This is the same shape as the defect three reviewers found earlier in the
+sitting** — a presence check blessing a page with one stale copy — and it
+recurred inside the fix for it. The harness header now states the limit plainly
+and points at the sweep as the tool that covers it.
+=== A third sweep, and the last two stale figures ===
+Re-run once more over a fresh export after publishing the guard fix. **68 hits,
+all legitimate except two**, both on ''provenance:programming:crawler:webxray''
+and both in the //judgement calls// section written by the 2026-09-05 sitting:
+  * "webXray at 69.9% domain-level and 93.9% encounter-weighted" — stated in the present tense about figures that are now 69.2% and 93.8%;
+  * "93.9% encounter-weighted is a flattering number … and Disconnect is better on the measured axis anyway" — the second clause is now **metric-dependent**, which is the finding the generic pass produced two sections above.
+Both were **dated rather than refreshed**: a record of a judgement made on a
+particular day should keep the figures it was made on. Each now carries the
+-09-11 value beside the 2026-09-05 one, and the "better on the measured
+axis" claim names both metrics and both p-values.
+The remaining 66 were read and are all one of: a //before// column, a
+struck-through open question quoting its own superseded text, a reviewer-log
+entry quoting the old page, the published mutation harnesses' own output, a
+''-'' line in the committed unified diff, the 2026-09-05 estimator run that
+''provenance:programming:crawler:webxray:random_sample'' exists to preserve, and
+one coincidental match of an unrelated inter-rater figure (76.5%).
+**Three sweeps were needed and each found something the one before did not**,
+because each round of edits moved figures the previous pair list did not name.
+The pair list is now 28 entries and is committed at ''out/moved_figures.json'';
+the next sitting should extend it rather than rebuild it.