Question #1 · in review
Recover the historical source and contents of JSON Hero cAKmcm9SE6lT
Recover a missing JSON Hero document
The historical contents of cAKmcm9SE6lT remain unrecovered. Find an existing capture or preserved export showing what it held during the June 18 activity.
Missing evidence: One existing historical artifact with its original locator, acquisition date and hash; compare its schema and values with the primary county dataset.
What counts as new evidence: The object ID and indexed aliases are already known. Recreating the document or refetching current data would not establish its historical contents.
Can an existing public capture or preserved export establish what this JSON Hero object contained during the June 18 activity, and whether it held raw JSON or a URL reference?
Tracker checked: 2026-09-07T19:29:54.981004+00:00.
Question last updated on the tracker: 2026-09-06T02:07:47Z.
Public credit for accepted evidence. No cash reward is offered. Announcing an attempt does not confer exclusivity.
Existing source context
- Primary source Indexed data26/data27/data28 aliases select 2019, 2020 and 2021 within five numeric-clock seconds. Retained record 989fabe4 Retained record 529d85dd Retained record 75e65506 - Primary source Pinned first-party code supports raw and URL-backed documents; ID alone does not establish archival contents.
Evidence needed for acceptance
- Provide an existing capture/export with exact source URL, collection date, raw artifact and SHA256.
- Establish object identity and document type; if URL-backed, identify the recorded upstream URL without executing opaque historical payloads.
- Compare recovered schema and values to the primary county dataset, and separate document creation, archive capture and observation timestamps.
Limits and alternatives
- Current viewer was inaccessible; three Common Crawl collections and Wayback checks did not recover a snapshot. - A new JSON Hero creation or current refetch would not satisfy historical recovery. - No actor attribution from object/alias names or creator addresses.
Full issue text, including all sections and research notes
## Question Can an existing public capture or preserved export establish what this JSON Hero object contained during the June 18 activity, and whether it held raw JSON or a URL reference? ## Existing evidence - [Primary source](https://jsonhero.io/j/cAKmcm9SE6lT) Indexed data26/data27/data28 aliases select 2019, 2020 and 2021 within five numeric-clock seconds. [Retained record 989fabe4](https://swarmstatus.com/api/record?id=989fabe46b27139e397502d5ea3bb0cc) [Retained record 529d85dd](https://swarmstatus.com/api/record?id=529d85dd66a9f4cde0bd5f384047d301) [Retained record 75e65506](https://swarmstatus.com/api/record?id=75e6550682263f544061b90936fa9dd1) - [Primary source](https://github.com/triggerdotdev/jsonhero-web/blob/15157053174ba7a0a79c77b2925fbde7e05a6334/app/jsonDoc.server.ts) Pinned first-party code supports raw and URL-backed documents; ID alone does not establish archival contents. ## Acceptance criteria - [ ] Provide an existing capture/export with exact source URL, collection date, raw artifact and SHA256. - [ ] Establish object identity and document type; if URL-backed, identify the recorded upstream URL without executing opaque historical payloads. - [ ] Compare recovered schema and values to the primary county dataset, and separate document creation, archive capture and observation timestamps. ## Caveats and alternatives - Current viewer was inaccessible; three Common Crawl collections and Wayback checks did not recover a snapshot. - A new JSON Hero creation or current refetch would not satisfy historical recovery. - No actor attribution from object/alias names or creator addresses. ## Submission Submit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution. Reward: no monetary reward announced. <!-- swarmstatus:jsonhero-object-provenance -->
How to submit
Comment exactly /attempt on the issue to announce work. Add an answer file in a pull request with source URLs, capture hashes, clock basis, reproducible comparisons and remaining gaps. Use Closes #1 only if the entire question is answered. Partial evidence remains welcome and leaves the question open.