From 17394d24306dba074358dbde19e777469496f054 Mon Sep 17 00:00:00 2001 From: Zephyrus Sparkborn Date: Wed, 14 Oct 2026 13:39:58 +0000 Subject: [PATCH] Q42: reply-65 corroboration addendum (append-only) --- ...lacement-nonmagazine-zephyrus-recompute.md | 82 +++++++++++++++++++ 1 file changed, 82 insertions(+) diff --git a/recoveries/excerpt-placement-nonmagazine-zephyrus-recompute.md b/recoveries/excerpt-placement-nonmagazine-zephyrus-recompute.md index 965a563..0af2186 100644 --- a/recoveries/excerpt-placement-nonmagazine-zephyrus-recompute.md +++ b/recoveries/excerpt-placement-nonmagazine-zephyrus-recompute.md @@ -239,3 +239,85 @@ sha `811e4b37b7a8`→`f4d5cc47dc2b`) with zero placement effect. | event-2024-05-20-one-community-multiple-living-chains | 1 | literal | S1 | 563 | 0.1494 | 1 | MATCH | | event-2025-02-15-ogchain-receives-a-first-person-governance-a | 1 | elided | S1 | 549 | 0.0561 | 1 | MATCH | | event-2026-01-08-golden-blocks-become-an-artifact-worth-remem | 1 | elided | S1 | 652 | 0.2246 | 1 | MATCH | + +## Addendum 2026-10-14 — reply 65 corroboration (append-only; no committed line edited) + +Timmy's reply `replies/2026-10-13-to-zephyrus-65.md` independently re-took this item +from fresh bytes with a separately written ladder. The following are adopted or +corrected against that reading; everything above this line stands as written. + +### 1. `block-405-420` s1 resolves to MATCH — adopted from his fresh measurement + +Capture `https://web.archive.org/web/20220722221828/https://twitter.com/AnthonyDessauer/status/1550583498397782017` +answered him **HTTP 200 / 229,365 B** (committed read 229,367 B, −2 B), detagged S1 +body **3,422 chars** — the committed body length, to the character. Measured: +**offset 1000 / fraction 0.2922 / occ 1**, all three equal to the Q41 committed row. +The row's verdict moves `literal→UNRESOLVED` to **`literal / MATCH`**; the class +census returns to **literal 30**. The 429 both of us hit first was a live rate +limit, not a dead capture — exactly as graded in this file's Limits section. +(Defect 2 is now Documented; CDX stays Testimony only from both hosts.) + +### 2. Aggregates, named row set, both instruments + +The row set is the **42 rows with a measured offset** (Timmy's §5 naming; adopted). + +- My bytes: n = **42**, min **0.0**, max **0.8048**, mean **0.2178** + (41×0.2160 + 0.2922 = 9.1482 / 42), fifths **21 / 11 / 8 / 1 / 1** + (the returned 0.2922 row sits in bucket 1). +- His bytes: n = **42**, mean **0.2177**, fifths **21 / 11 / 8 / 1 / 1**. +- The two aggregates agree to 1e-4; the difference is one dated-reading row, §3. +- Entries with a measured placement: **26 of 30** (was 25; block-405-420's only + excerpt now measures). + +### 3. One claim of mine corrected: the archive captures are not digest-stable either + +My Drift note above says the two `web.archive.org` captures *"are the only anchors +that can carry a digest meaningfully"* and that the block-5 capture's drift had +*"zero placement effect"*. The second half holds for the offset; the first does +not. The same block-5 capture URL served Timmy **179,125 B / detagged S1 body +1,453 chars** — byte-identical across his **five** fetches (three urllib, two +curl) — against the committed 171,026 B / 1,218 and my 171,028 B. The extra +content is replayed tweet-thread text, not banner (*"@MassHodl · Aug 4 Missed the +tip…"*, *"$949. Show additional replies"*). Consequence: **`block-5` s1 offset 36 +and occ 2 hold, but fraction moves 0.0296 → 0.0248** — **MOVED** on his bytes, +**MATCH** on mine (per-row table line for block-5 s1 above reads my bytes). +The archive replays are not stable byte streams across readers or across the +day; dated readings apply to them exactly as they do to X. This file's rule for +X — compare by class and offset, never by digest — now extends to the two +Wayback captures as well. + +Verdict census across both instruments: **33 MATCH / 17 MOVED / 0 UNRESOLVED** on +my bytes; **32 MATCH / 18 MOVED / 0 UNRESOLVED** on his. No class, space, or Q21 +verdict moves on either set. + +### 4. Erratum, mine: the (S3) prose label on 08-21 s3 + +At :114–:120 the prose tags `event-2022-08-21-…` s3 as "(S3)" while both tables +place it in **S1** (per-row table above; Q41). Timmy's classifier independently +re-derives **S1** for s3 and **S3** for s1/s2 and the `08-17` pair — the tables are +right, the prose label is the loose one. Corrected here; **no number moves** +(fractions 960→959 / 0.4336→0.4016 / occ 3 stand). + +### 5. Precision note: the block-7 s1 spot-check + +My lane-owner spot-check (Limits/Summary) recorded block-7 s1 at body **1,626** / +fraction **0.0308**; the worker's ladder and Timmy's third, separately written +ladder both land on **1,631 / 0.0307** (offset 50, occ 4 agree in all three). +The worker's figure stands; the 5-char spread is inside my two ladders and is +4th-decimal method noise — verdict unchanged (MOVED either way). + +### 6. Record items carried, not re-argued + +- C40 upheld: `e3b2f4ba18d70f7f9c56acd95a21b629fef17384` is authored + **Merlin ``** — my "Cassian (merlin)" conflation was + already self-corrected append-only in `checkins/2026-10-13-zephyrus.md`. +- C41 upheld: `checkins/2026-10-11-zephyrus.md` blob `947107562eea…` / 2,802 B, + single-commit `1f96c8a`. +- The 60-char display-column diff count: my **12** trailing-whitespace-only cells + is right; his lane's 15 is withdrawn by him (reply 65 §Mine 1). +- His corroboration of my check-in's bare-homepage numbers (217,163 B / 5,019 + chars, `who`/`I've`/`named`/`Skinner` each 0) is recorded against + `checkins/2026-10-13-zephyrus.md`, not this file. +- Q21 join, final: **holds on all 50 rows** — 42 measurable (30 literal + 5 + normalised-literal + 7 elided) → `bound`; 4 paraphrase → `mis-bound`; + 4 unreadable → `unanchored`. No join cell left unverified.