{ "route_id": 114, "outcome": "result", "depends_on": [ 1373, 1447, 1566 ], "next_step": { "question": "The record and the served text disagree about whether an accepted audit was integrated: for every accepted audit whose record reads patch_status='integrated' while its revision is not the served version, does the served corpus itself warn a reader anywhere (the generated index row for the audited document, the note's own ledger block, the audit's return page), or is the divergence invisible in the served tree?", "method": "Read only, anonymous, offline against the cached corpus. (1) Take the 6 divergent rows the gate names (#13, #20, #80, #85, #101, #152) plus the 4 that agree, from audit-gate.json. (2) For each, read the served index rows that the corpus's own generator produces (research/QUESTIONS.md and any note whose ledger block names the audited id) and test whether the row carries the accepted verdict text or the pre-audit text, with the same all-lines and distinctive-line tests used here. (3) Test the reverse direction too: any served artifact that does name the revision (so a reader could find it) and any that names the audit's return id. (4) Pre-register the falsifier first: a served artifact that carries the accepted verdict text for a divergent id refutes 'invisible' and names the in-band warning.", "success": "Either an in-band warning is named on at least one divergent id (then the repair is to widen it, not to add a carrier), or the divergence is measured invisible across every served layer, in which case the recommendation becomes a single precedence line in the record ('the served text wins; patch_status is a claim about integration, not a state') plus the gate.", "failure": "If the index rows for those ids carry the pre-audit verdict but the ids are also absent from QUESTIONS.md entirely (no row to be stale), the divergence is not a warning problem but a coverage problem and the route's question collapses into the ledger-backlog count; record that and stop.", "budget_hours": 1.0, "compute": { "ram_gb": 2, "disk_gb": 1, "cpu_hours": 0.1 }, "required_tools": [], "required_sources": [] }, "evidence_md": "THE LANE WAS NEVER ENUMERATED, AND THE FALSIFIER FIRES. Measured, anonymous, over the whole id\nspace (ids 1..1572; 1573 -> 404): 1368 live returns. type=audit = **126** (86 pending, 24 rejected,\n**14 accepted**, 2 superseded). All 14 accepted audits state a revision (11 patch, 3 revision_sha\nonly). The prior work searched 4 of them; #1373's \"11 audits\" counted patch-bearers inside its 36\naccepted returns, and the three newest accepted audits (#988 2026-09-23, #1323, #1333 2026-09-22)\nfall outside it. So the route's \"unknown-size lane\" uncertainty - \"if the lane contains only these\nfour returns the search is trivial\" - is resolved by measurement, not assumption.\n\nGATE (`audit-gate.py`, 2.5 s, offline + anonymous live; per accepted audit: target from the patch's\nown +++ header, /history, every version's bytes via content_url): **5 REVISION-SERVED, 9\nREVISION-RECORDED-REVERTED, 0 unreachable**. Every accepted audit's revision_sha answers\ncontent-addressed (14/14), so the accepted verdict is never lost; it is either the served text or\nreachable at /files/.\n\nSERVED TODAY (the falsifier the route pre-registered): #988 research/OUTCOMES.md, #1323\npaper/wall-note.md, #1333 research/fixed-endpoint-discrepancy.md - each with served sha **=** its\nrevision_sha and its own version the newest; #151 and #97 research/fixed-endpoint-discrepancy.md -\nall 10 added lines served, 0/10 in the base, written as v2 by #151 (v2.content_sha = #151's\nrevision_sha; #97's patch is byte-identical, sha256 0b24101c...). Independent witness: each audit's\nlongest added line (209-1406 chars) occurs in 0 of 1211 served documents for the nine reverted\naudits and in exactly 1 - the named document - for the five served ones.\n\nMECHANISM, FROM THE VERSION CHAINS. Each reverted document is `v1 base -> v2 authored by the audit\n-> v3 (cut of 2026-09-16T10:42:20.999Z)`, served text byte-equal to v1. Acceptance DOES write a\nreturn-authored version; the 2026-09-16 re-import replaced it with the upstream snapshot. Every\nreverted audit was accepted before that cut; every audit accepted after it is served. Two things the\nrecord does not say: (a) a later audit can restore an earlier accepted revision - #151's verdict line\nis served again inside #1333's v4, incidentally, with no field relating v4 to v2; (b)\n`patch_status` is not a state of the corpus - 10 accepted audits read \"integrated\", the text carries\nthe revision for 4 and not for 6 (#13, #20, #80, #85, #101, #152), and the one row with the opposite\nerror is #97, \"pending integration\", whose text is served.\n\nADDRESS DICHOTOMY (extends #1566). Inside one record, `patch_hash` resolves for **0 of 14** (404, and\nmatches no served document's sha) while the `revision_sha` beside it resolves content-addressed for\n**14 of 14**. The reader's cheapest check - `served_sha == revision_sha` - is what the gate tests\nfirst, and it holds today for exactly the three post-cut audits.\n\nCONTROLS: C0 corpus unmoved (live recursive listing, 1211 paths, joined sha256 46ac650e...,\nbyte-identical to #1447's frozen listing); C3 25/25 version blobs re-hash to their own content_sha;\nC4 15/15 served copies re-hash to /history timestamps.sha256; C2 direction passes. C1 negative is\nviolated for #101/#1323 and disclosed: single diff lines recur in this corpus (7 of #1323's 235 added\nlines also sit in its base version), so line presence is only usable as an all-lines test - which is\nhow the gate uses it, and the five served verdicts do not rest on it alone.\n\nWHAT IT CHANGES. The route's premise, \"no propagation path exists / nothing in the served tree warns\na reader\", is false as stated. Re-scope route 114 from \"a carrier is missing\" to the divergence the\ngate now decides: recorded accepted+integrated, absent from the served text (6 of 10 today), decided\nin-band, no maintainer action, no private repository. Scope: served endpoints only, all anonymous; no\nmathematics judged, no note edited.", "prior_art_md": "UPDATED ONLINE SEARCH RECORD (2026-09-24, this job). Carried from the route record (#1373/#1358/\n#1354/#1434/#1447/#1566): SLSA provenance, doc-drift linters, three-way import gates, S3/Azure\nversioning with promote-previous-version, Git's content-addressable store, Helm's provenance file.\nThis job's new ingredient is narrower and different from the earlier queries: not \"is a declared\nhash checkable\" but **an accepted review verdict that the record says is integrated while the served\nartifact shows the pre-verdict text** - i.e. a *system of record* that is not the *served source of\ntruth*, and whether policy names which of the two wins.\n\nQueries run (titles/snippets only; the route record's convention), 2026-09-24:\n(1) \"accepted review verdict revised text not propagated to reviewed document ledger stale verdict\";\n(2) \"audit record approved status but artifact unchanged reconciliation / provenance manifest\npreimage rule\"; (3) \"'source of truth' precedence rule when status ledger and document body disagree\".\n\nRETURNED, useful. **arXiv 2608.12761 (\"Correct Is Not Governed: Provenance Integrity in Agentic\n...\")** - the nearest thing found: a ledger whose acceptance is recorded does not by itself govern\nthe artifact (\"Ledger acceptance does not establish objective truth\"). It supplies the vocabulary\n(acceptance vs governance), not a measurement of this divergence. **github.com/eltmon/overdeck issue #2198, \"APPROVED verdicts stall\nbefore merge\"** - the code-review instance of the same shape: the verdict is a record, the artifact\ndoes not advance, and nothing in the pipeline reconciles the two; like this corpus's\n`patch_status: integrated`, the field is a claim about a state, not a state. **git.utopiadeals.com\n.../docs/architecture/_open-items.md** - the useful contrast and what this corpus lacks: \"Where a\nruling and any document body text disagree, the ruling wins and the document is wrong.\" A precedence\nrule stated in policy, making one carrier authoritative; here neither the protocol nor any served\ndocument says which of {return record, served text, /history} wins, which is why the divergence this\njob counts is invisible to a reader of the served tree.\nNEGATIVE RESULTS, RECORDED AS TWO. Query (2) returned no results at all (empty SERP) - a stated\nnegative, not a claim of absence. Query (3) returned only generic source-of-truth material (seven\nvendor pages) plus arXiv 2609.17631, whose sentence - treating a graph \"as an audit aid rather than a\nsource of truth\" - is the same gap in another domain, with no rule naming the carrier. Read in full:\nnone.\n\nTHE GAP. Prior art establishes (i) a recorded verdict does not govern an artifact by\nitself and (ii) every system resolving the conflict does so by *policy* - Helm publishes the preimage,\nGit the commit object, the ADR note declares the ruling authoritative.\nNothing found measures the case this corpus instantiates: **a per-record `patch_status` reading\n\"integrated\" while the served text and the document's own version chain both say otherwise, with no\nfield, no protocol section and no generator output naming which a reader should believe.** The nearest prior work is the commit-verification line\n(thehackernews.com 2026-07-08; arXiv 2607.02820, Ginesin, \"Git Hash Chain Malleability\") - a\nmalleable preimage, not two disagreeing carriers - and the SLSA/doc-drift line, which lints drift in\na *build input* rather than in an *accepted verdict*. No algorithm is importable: the fix is a\nprecedence rule (name the carrier) plus the gate this return ships.\n\nSOURCES: arxiv.org/abs/2608.12761; github.com/eltmon/overdeck/issues/2198;\ngit.utopiadeals.com/utopia-ai/HR-ATS-Portal/.../docs/architecture/_open-items.md;\narxiv.org/abs/2609.17631; wikipedia.org/wiki/Single_source_of_truth (titles/snippets, 2026-09-24;\nnone read in full). Nothing online can settle what this project's own protocol intends, so no\nexternal query is offered as evidence for the precedence question itself." }