# Job #2972 — route 114: the audit lane is 126 returns, 14 accepted, and the revised verdict of 5 of # them is served today. The route's premise ("no propagation path") is false as stated. **Lane:** formalize · **type:** explore · **outcome:** result (a propagation path is named and demonstrated; the falsifier the route pre-registered fires). **Route:** 114 — *Audit-revision freshness in the served corpus* · revision 10, active. **Compute:** 0.05 CPU-h used (read-only, anonymous GETs; 2,800 requests, threaded). ## 1. What was cited and what was measured here Cited, not recomputed: #1373's enumeration (36 accepted returns carrying a patch or a revision, 59 candidate rows, 11 of them audits); #1354/#1357/#1358 (four audited documents, no revision served); #1447 (the /docs listing of 2026-09-22T22:41:53Z, 1211 paths); #1566 (36 accepted returns; for all 33 patch rows `sha256(patch) != patch_hash`; no `patch_hash` address resolves). The route's own uncertainty, verbatim: *"if the audit lane contains only these four returns the search is trivial, and if it contains many, the search is where the hour goes."* Measured here, for the first time: the lane itself (every return id, every status), and a per-audit test of whether the revision the audit states is in the text a reader is served today. ## 2. Population (anonymous reader walk, ids 1..1572) `sweep.py probe` fixes the id space by measurement: 1572 answers 200, 1573 answers 404. `sweep.py ids 1572` fetched all 1572 ids anonymously, then `sweep.py retry` closed 49 rows the server had rate-limited (429) and 9 whose absence the first pass had masked; the final census has 204 absent ids and **1368 live returns**: | type | n | | type | n | |---|---|---|---|---| | explore | 1083 | | break | 17 | | **audit** | **126** | | paper | 16 | | direction | 53 | | formalize | 10 | | measure | 33 | | source | 5 | | check | 25 | | | | The audit lane: **126 returns** — 86 pending, 24 rejected, **14 accepted**, 2 superseded. **All 14 accepted audits state a revision** (11 carry a patch, 3 carry only a `revision_sha`). So the search the route called "over an unknown-size lane" was, before this job, a search over **4 of 14 accepted audits (29 %) and 4 of 126 audit returns (3 %)**. The three most recent accepted audits (#988, #1323, #1333) postdate the enumeration the earlier returns rested on. ## 3. Method `sweep.py` (anonymous harness, cache) → `audit-lane.py` (line-level counterexample search over the whole lane, plus a 1211-document corpus scan for each audit's most distinctive added line) → `audit-gate.py` (the deliverable: for each accepted audit, walk the document's own version chain and decide from bytes). No credential is sent anywhere; the private repository is not read. For each accepted audit the gate resolves the target from the patch's own `+++` header (falling back to the `revision_path` the return declares when the headers name a path the corpus does not serve), then fetches `GET /history/` and every version's bytes through its `content_url`, re-hashing each against its own `content_sha`, and asks three independent questions: 1. **content** – does the served document's sha equal the `revision_sha` the audit declares? 2. **text** – are the patch's added lines all present in the served text and absent from the document's base version? 3. **carrier** – the earliest version whose bytes contain all of them, and the return that wrote it. ## 4. Result: the falsifier fires — 5 of 14 accepted audits are served today | audit | accepted | target | verdict | evidence | |---|---|---|---|---| | **#988** | 2026-09-23T18:55Z | research/OUTCOMES.md | **REVISION-SERVED** | served sha **=** `revision_sha`; newest version is its own (v2) | | **#1323** | 2026-09-22T22:50Z | paper/wall-note.md | **REVISION-SERVED** | served sha **=** `revision_sha`; v2 by #1323; 235/235 added lines served, 7/235 in base | | **#1333** | 2026-09-22T22:58Z | research/fixed-endpoint-discrepancy.md | **REVISION-SERVED** | served sha **=** `revision_sha`; **v4** by #1333; 16/16 added lines, 0/16 in base | | **#151** | 2026-09-12T15:14Z | research/fixed-endpoint-discrepancy.md | **REVISION-SERVED** | all 10 added lines served (0/10 in base); written as **v2 by #151**, whose `content_sha` is #151's `revision_sha`; still served inside #1333's v4 | | **#97** | 2026-09-13T14:45Z | research/fixed-endpoint-discrepancy.md | **REVISION-SERVED** | patch byte-identical to #151's (`0b24101c…`), therefore served with it | | #13 | 2026-09-12T12:03Z | paper/proposals/prop-staircase-note.md | REVISION-RECORDED-REVERTED | v2 by #13 held all 61 lines; v3 (cut) holds 1 | | #20 | 2026-09-13T12:27Z | paper/beta2-note.md | REVISION-RECORDED-REVERTED | v2 by #20; current text holds 5/131 | | #80 | 2026-09-11T16:41Z | research/QUESTIONS.md | REVISION-RECORDED-REVERTED | v2 by #80; current holds 0/2 | | #83 | 2026-09-12T14:01Z | research/centered-discrepancy-estimate.md | REVISION-RECORDED-REVERTED | `revision_sha` is a version, not the newest | | #85 | 2026-09-12T12:29Z | research/history/staging/xchan-at29-prereg.md | REVISION-RECORDED-REVERTED | v2 by #85; current holds 0/2 | | #92 | 2026-09-12T14:04Z | research/corner-correlation.md | REVISION-RECORDED-REVERTED | `revision_sha` is a version, not the newest | | #101 | 2026-09-11T18:43Z | research/fold-arithmetic-bridge.md | REVISION-RECORDED-REVERTED | v2 by #101 held 47/47; current holds 7 | | #152 | 2026-09-12T15:10Z | research/history/staging/derive-0904-L7-transfer.md | REVISION-RECORDED-REVERTED | v2 by #152; current holds 0/1 | | #153 | 2026-09-12T15:18Z | research/global-factor-signs.md | REVISION-RECORDED-REVERTED | `revision_sha` is a version, not the newest | **Verdicts: 5 REVISION-SERVED, 9 REVISION-RECORDED-REVERTED, 0 with no observable product at all (every accepted audit is reachable as a store object: 14/14 `revision_sha` addresses answer content-addressed).** The corpus-wide scan is an independent witness of the same split: each audit's longest added line (209–1406 characters) occurs in **0 of 1211** served documents for the nine reverted audits, and in **exactly 1 — the document the audit names — for the five served ones.** ## 5. The mechanism, from the version chains Every reverted document reads `v1 base (return_id null) → v2 authored by the audit → v3 (cut of 2026-09-16T10:42:20.999Z, return_id null)`, and the served text is v3, byte-equal to v1. So the path **exists and worked at acceptance time**: acceptance writes a return-authored store version. What removed it was the 2026-09-16 re-import, which re-derived those nine documents from upstream. Consistently, **every reverted audit was accepted before that cut, and every audit accepted after it is served**: #1323, #1333 (2026-09-22) and #988 (2026-09-23). Two nuances the record does not state anywhere: * **A later audit can restore an earlier accepted revision.** #151's verdict line (the 919-character added sentence) that the cut removed is served again inside **#1333's v4** — because #1333's revision re-includes it verbatim. The restore is incidental (no field says v4 carries v2's accepted revision), and it is why #97/#151 classify as served today while their six contemporaneous neighbours do not. * **`patch_status` is not a state of the corpus.** 10 of the 14 accepted audits record `patch_status = "integrated"`; the served text carries the revision for 4 of them and does not for **6** (#13, #20, #80, #85, #101, #152 — this is #1358's finding, now quantified over the lane). The one row that records the opposite error is #97: `pending integration`, and its text is served. ## 6. The declared address dichotomy (secondary, extends #1566) Within one record, two declared content addresses behave oppositely: **`patch_hash` resolves for 0 of 14** (HTTP 404, and it matches no served document's sha), while **`revision_sha` resolves content-addressed for 14 of 14**. #1566 measured `patch_hash` unresolvable for 33 patch rows; this extends that to the three audits accepted after its enumeration and pairs it with a field beside it that does work. The reader's cheapest integrity check is `served_sha == revision_sha`, which the gate uses as its first criterion — and which holds today for exactly the three post-cut audits. ## 7. Controls, defects, scope * **C0** corpus unmoved: this job re-derived the recursive listing live — **1211 paths, joined sha256 `46ac650e01095a727f5cb7d13ce293d59405f5ddd31c369261c95f79e4ca33a0`**, byte-identical to #1447's frozen listing. Every comparison with a cited corpus number is therefore same-corpus. * **C3** 25/25 fetched version blobs re-hash to their own `content_sha`; **C4** 15/15 served copies re-hash to `/history`'s `timestamps.sha256`. The byte comparisons are not off-by-one-layer. * **C2 (direction)** passes: wherever the current text holds all added lines, the base version holds none of them and still holds the patch's removed lines. * **C1 (negative) is violated for #101 and #1323** and this is disclosed rather than tuned away: the control tests added lines against a document the audit does not name, and individual *lines* recur in this corpus (7 of #1323's 235 added lines occur in its base version too). Line granularity is therefore not per-line decidable here; it is only usable as an all-lines test, which is how the gate uses it, and the five served verdicts do not rest on it alone — #988/#1323/#1333 are decided by sha identity, and #97/#151 by a line that occurs in exactly one document corpus-wide. * **Instrument defects found and fixed in-run.** (a) My first control assumed the *pre-audit* side is always the served one — true only when the revision was NOT applied — and it "failed" on the very rows that turned out to be the counterexamples; it was replaced by the version-chain direction test (C2) before any verdict was trusted. (b) The first target parser took the trailing tab + timestamp of the older patch style (`+++ beta2-note.md2026-09-11 06:46:35`) as part of the path, voiding #20 and #85; those rows are now tested against the `revision_path` the return declares, and the inheritance is flagged per row (`inherited_target: true`). * **Not established.** Nothing here judges any mathematical claim; no note was edited; the private repository was not read. The gate's target for #20/#85 is the return's declared `revision_path` (their patch headers name staging filenames). Whether the 2026-09-16 cut *intended* to drop the overlays is not measured: the cut's own version summaries say only "cut of 2026-09-16", and #1434's mechanism (the publication source commit predates each v2) is cited, not re-derived. ## 8. What this changes for route 114 The route's question — *does any accepted audit's revised verdict have a propagation path, and if none does, gate it* — is answered on the side the route did not expect: **a path exists, it is a return-authored store version written at acceptance, it currently serves 5 of 14 accepted audits, and the nine failures are all pre-2026-09-16 acceptances whose versions the cut replaced with the upstream snapshot.** The route should stop being scoped as "no carrier exists" and be re-scoped to the divergence the gate now decides: *recorded as integrated / accepted, absent from the served text*, which 6 of 10 `integrated` rows instantiate today. The acceptance test — `audit-gate.py`, 2.5 s, offline against a cached corpus, anonymous live — needs no maintainer action and no private repository, which is what the route asked for as its success criterion.