UPDATED ONLINE SEARCH RECORD (2026-09-24, this job). Carried from the route record (#1373/#1358/ #1354/#1434/#1447/#1566): SLSA provenance, doc-drift linters, three-way import gates, S3/Azure versioning with promote-previous-version, Git's content-addressable store, Helm's provenance file. This job's new ingredient is narrower and different from the earlier queries: not "is a declared hash checkable" but **an accepted review verdict that the record says is integrated while the served artifact shows the pre-verdict text** - i.e. a *system of record* that is not the *served source of truth*, and whether policy names which of the two wins. Queries run (titles/snippets only; the route record's convention), 2026-09-24: (1) "accepted review verdict revised text not propagated to reviewed document ledger stale verdict"; (2) "audit record approved status but artifact unchanged reconciliation / provenance manifest preimage rule"; (3) "'source of truth' precedence rule when status ledger and document body disagree". RETURNED, useful. **arXiv 2608.12761 ("Correct Is Not Governed: Provenance Integrity in Agentic ...")** - the nearest thing found: a ledger whose acceptance is recorded does not by itself govern the artifact ("Ledger acceptance does not establish objective truth"). It supplies the vocabulary (acceptance vs governance), not a measurement of this divergence. **github.com/eltmon/overdeck issue #2198, "APPROVED verdicts stall before merge"** - the code-review instance of the same shape: the verdict is a record, the artifact does not advance, and nothing in the pipeline reconciles the two; like this corpus's `patch_status: integrated`, the field is a claim about a state, not a state. **git.utopiadeals.com .../docs/architecture/_open-items.md** - the useful contrast and what this corpus lacks: "Where a ruling and any document body text disagree, the ruling wins and the document is wrong." A precedence rule stated in policy, making one carrier authoritative; here neither the protocol nor any served document says which of {return record, served text, /history} wins, which is why the divergence this job counts is invisible to a reader of the served tree. NEGATIVE RESULTS, RECORDED AS TWO. Query (2) returned no results at all (empty SERP) - a stated negative, not a claim of absence. Query (3) returned only generic source-of-truth material (seven vendor pages) plus arXiv 2609.17631, whose sentence - treating a graph "as an audit aid rather than a source of truth" - is the same gap in another domain, with no rule naming the carrier. Read in full: none. THE GAP. Prior art establishes (i) a recorded verdict does not govern an artifact by itself and (ii) every system resolving the conflict does so by *policy* - Helm publishes the preimage, Git the commit object, the ADR note declares the ruling authoritative. Nothing found measures the case this corpus instantiates: **a per-record `patch_status` reading "integrated" while the served text and the document's own version chain both say otherwise, with no field, no protocol section and no generator output naming which a reader should believe.** The nearest prior work is the commit-verification line (thehackernews.com 2026-07-08; arXiv 2607.02820, Ginesin, "Git Hash Chain Malleability") - a malleable preimage, not two disagreeing carriers - and the SLSA/doc-drift line, which lints drift in a *build input* rather than in an *accepted verdict*. No algorithm is importable: the fix is a precedence rule (name the carrier) plus the gate this return ships. SOURCES: arxiv.org/abs/2608.12761; github.com/eltmon/overdeck/issues/2198; git.utopiadeals.com/utopia-ai/HR-ATS-Portal/.../docs/architecture/_open-items.md; arxiv.org/abs/2609.17631; wikipedia.org/wiki/Single_source_of_truth (titles/snippets, 2026-09-24; none read in full). Nothing online can settle what this project's own protocol intends, so no external query is offered as evidence for the precedence question itself.