Full record — 2,324 characters, 0 sources
2026-08-23 observation 1 of 2 Bing Copilot · signed in · paste + frame evidence · sources not captured
STALE-INDEX CANDIDATE, CAUSE PROBABLY LOCAL — RECORDED AS A CANDIDATE AND NOT AS A CLASS. The operator states that the archive's own READMEs and documentation surfaces were themselves stale until a batch update on 2026-08-22, one day before this capture. The ordinary explanation therefore precedes the interesting one: the layer may be reporting faithfully what the archive's surfaces said until the day before. A drafting instance initially proposed a 'ghost host' class here — the deleting platform retaining credit while the erasure event is itself erased — and that proposal is WITHDRAWN pending re-run. RE-RUN CONDITION: if this address still returns Zenodo as host after 2026-09-23, a month past the surface update, the local explanation fails and the finding is live. NOT VERIFIED: crawl date of the underlying sources.
2026-09-28 observation 2 of 2 Bing Copilot · incognito, signed out · paste evidence · 1 sources · PER 0.75
Set beside the 23 August record at the same address, the composition keeps the archive's stale state and loses its person. The host sentence is carried over unchanged ('a decade-long, DOI-anchored … over 480 deposits hosted on CERN's Zenodo repository … a working laboratory for Compression Studies'); the Space Ark, the Encyclotron, the Semantic Economy Institute and the Journal of Compression Studies drop out of the component list; the author and his city are replaced by 'independent scholars'. The collision widens at the same time: where 23 August split the string two ways, colour and archive, this one splits it three ways and places the defunct firm between them.
- colorhexa.com third_partyCrimson / #dc143c hex color - ColorHexa
STALE-INDEX CANDIDATE, CAUSE PROBABLY LOCAL — RECORDED AS A CANDIDATE AND NOT AS A CLASS. The operator states that the archive's own READMEs and documentation surfaces were themselves stale until a batch update on 2026-08-22, one day before this capture. The ordinary explanation therefore precedes the interesting one: the layer may be reporting faithfully what the archive's surfaces said until the day before. A drafting instance initially proposed a 'ghost host' class here — the deleting platform retaining credit while the erasure event is itself erased — and that proposal is WITHDRAWN pending re-run. RE-RUN CONDITION: if this address still returns Zenodo as host after 2026-09-23, a month past the surface update, the local explanation fails and the finding is live. NOT VERIFIED: crawl date of the underlying sources.