{ "route_id": 140, "outcome": "result", "evidence_md": "POPULATION: #1373's served returns index (sha256 bf804151...d5, pin verified): 1370 ids, 1200 answering, 170 absent; all 1200 pages walked anonymously, 0 transport failures. Pre-registered in prereg-2849.md (sha256 372e0dbb...c5) before the census ran. Checker verify-2849.py: 6/6 claims, ok true, 4b3e947b...42.\n\nT1 THE POPULATION. 807 distinct checkers on the record at 930 declaration sites (a plan.checker sha, or a declared file whose name marks it a checker). All 807 fetch anonymously by sha with 0 not found, so the route's strongest failure branch fires nowhere.\n\nT2 THE PRE-REGISTERED CLASS, COUNTED. 22 module-level 64-hex constants in 17 of the 807 checkers; 20 are compared against something other than the literal itself, 2 are not (check1090.py MAPS/GLOBAL). Of the 20 compared, 19 resolve and 1 does not: 18 as STORE OBJECTS (/files/ -> 200, sha256(body)==c), 14 of those also declared as files by a DIFFERENT return, 1 only by hashing a document the checker names.\n\nT3 THE ONE THAT DOES NOT. job1679-checks.py (return #883) bakes HASH = 79eda0d5370d7b9a1984d1381a08cbd053d9ac4481de5115612524b94b11206a and compares it at line 85 as f78.get(\"/patch_hash\") == f80.get(\"/patch_hash\") == HASH. That value is return #80's patch_hash: it answers 404 at /files/ and no return declares it as a file, so a reader can neither fetch nor compute it. Route 114's census (return #1566, this session) measured that patch_hash is served in the record yet matches none of seven candidate derivations of the served patch text on 29 of 33 rows, and that its preimage rule is stated nowhere. So this checker pins two record FIELDS to a constant that is itself unverifiable: it can only agree with the record about a value the record does not let anyone compute.\n\nT4 THE CLASS IS NARROW, AND THE ROUTE'S WORKED EXAMPLE IS OUTSIDE IT. freshness-triager.py's four constants are entries of a module-level container (lines 68-74), not NAME = literal bindings, so the specified class cannot see the example that motivated the route; re-checked directly (C2b) it fetches by sha (b91f88a8..., 200, 14591 B) and all 4 literals resolve as store objects. The extension over quoted 64-hex literals anywhere bounds the gap: 117 of 807 checkers carry literals, 561 rows / 328 distinct, 297 resolve as store objects, 156 are declared by another return, 264 do not -- and those 264 must NOT be read as broken checkers: they are dominated by EXPECTATION TABLES (expected sha256 values in registry-check.json, \"l03.out\": \"911d0671...\" in a log), claims about outputs a worker computes, not about served bytes.\n\nT5 A NEGATIVE RESULT. 0 of the 807 checkers carry a code-sha256 header, so #1461's self-provenance defect could not be re-found here. P6 fails.\n\nPREDICTIONS: P1 PASS (1200/1200, 170 absent, 0 failures); P2 PASS (807 > 1); P3 PASS (17/807 = 2.1% < 40%); P4 PASS (18/20 = 90% > 60%); P5 PASS (1 unresolved); P6 FAIL. Falsifier F4 is the one to keep: 182 of 807 checkers do not parse under the language detected from name and head, so all counts are scoped to what parsed; the constant total is a lower bound.\n\nCONTROLS. C1 index pin and its own 1200/170 counts. C2 (positive, as coded) FAILED and the CONTROL was wrong, not the resolver: its filter looks for verif|check|verify in a file name and freshness-triager.py contains none, so the worked example was never in the population. C2b reproduces the known case (return #1454). C3 a fabricated constant answers 404 and is declared by nobody -> UNRESOLVED. C4 the unresolved checker re-fetched and byte-compared: identical.\n\nSCOPE. Served endpoints only, all anonymous; private repo not read; population frozen at the served index sha. Not established: checkers not on the record; the true constant count (182 unparsed); that an unresolved expectation-table digest is a defect (most are not); and qc.js, named by research/qc/embed.js as the checker for the self-provenance defect, is absent from the record. No mathematics is judged and no rung moves.", "prior_art_md": "UPDATED ONLINE SEARCH RECORD (2026-09-24, this job). Carried from the route record (#1454/#1461): RO-Crate package provenance, SWHID content identifiers, reproducible-build tooling, the project's own code-sha256/out-sha256 and inputs: path@sha conventions, and the route's own earlier query whose nearest formal analogue was ZK fine-tuning proofs bound to a published commitment.\n\nThe route's prior_art_md already states the gap this job closes empirically: prior art covers pinning inputs, outputs, tools and metadata with content hashes (RO-Crate, SWHID, reproducible builds), and it covers committing to a value and verifying against that commitment -- but none of it measures a provenance convention's COMPLIANCE RATE over a live corpus, and none of it poses the circularity question for checkers ON THE RECORD. This job adds the measurement, and one thing more: the population of checkers on the record is now bounded (807 distinct, 930 declaration sites, all retrievable), so the question 'how many of those constants trace to an independent record' has a denominator rather than an anecdote.\n\nEXACT REMAINING GAP, in three parts. (a) The measured partition is 19 of 20 compared constants anchored, with the one exception being a checker that compares two record FIELDS (patch_hash values) to a baked constant; no prior art was found that distinguishes anchoring a constant to a STORE OBJECT from anchoring it to another FIELD of the same record -- the second is circular in a way the first is not, and that distinction is what the route needed. (b) Nothing in the prior art covers a checker whose constant cannot be verified because the field it compares has no stated preimage rule; that is a schema observation arising from this corpus (route 114, return #1566), and its fix belongs to the publisher, not to an algorithm. (c) qc.js, named by the corpus's own embed.js as the static checker for exactly the self-provenance defect class, is still absent from the record, so no census can test whether that half of the route has any population at all. A further search on the field-vs-object distinction returned only the generic \"pin and compare\" literature already carried, so no new sources are claimed.\n\nSOURCES (carried, read as titles/snippets on the dates in the route record, none in full): researchobject.org/ro-crate and the RO-Crate 1.3 minimal-crate guide; swhid.org/faq; CRAN gp3ml (RO-Crate-oriented export with SHA-256); the route record's ZK item arXiv 2510.16830; adaptivearts.ai (2026-07-10) on checking preserved blobs against a pre-merge manifest. No source was found that measures compliance rates, so none is cited for that.", "next_step": { "question": "If the unanchored member's cause is removed -- i.e. patch_hash gets a stated preimage rule (or checkers stop baking it and read it from the return) -- does the pre-registered class become 20 of 20 anchored, and does the 182-checker parse gap turn up further unanchored constants once those files are parsed in their own languages?", "method": "Two bounded passes, endpoints only, no new walk. (1) Re-parse the 182 checkers that did not parse under the detected language, by classifying each from its own first line and shebang and adding an ESM/shell reader (three were already shown to be .mjs, .sh and extension-less ESM on the first pass), then re-resolve every newly found constant against the same three records. (2) After the maintainer states patch_hash's preimage rule, re-run the C2 block of verify-2849.py over all 33 patch rows of route 114's population AND re-resolve job1679-checks.py's HASH against store object and declared-file records; report whether the constant becomes anchored, and if not, which record it would need to exist.", "success": "The parse gap closes with no new unanchored member (the class is then bounded and anchored), or it closes with further members named by checker sha and quoting line -- either way the route's rule stops resting on a class of one. Secondary: patch_hash acquires a stated preimage rule and the field-level circularity disappears from the record.", "failure": "The 182 unparsed checkers yield constants that cannot be resolved either way (i.e. the ambiguity is in the languages, not the record), in which case the census is scoped to parsed files for good and the recommendation narrows to the two field-level repairs. A second failure mode: no preimage rule is stated, in which case the field-vs-field circularity is a permanent property of the record and should be documented as such rather than re-measured.", "budget_hours": 0.5, "compute": { "ram_gb": 0.5, "disk_gb": 1, "cpu_hours": 0.05 } }, "depends_on": [ 1454, 1461, 1566 ] }