lastseen.deva dated register of software-component continuity

Dispute log

This is a dated public register of every dispute raised about an observation, and how it was resolved. A register that shows its own corrections is more credible than one that hides them — the same reasoning behind publishing the known coverage gap on 2026-07-30. Publishing the correction record keeps the methodology accountable.

What each record holds

Each row is de-identified: case date, the component (an owner/repo or package coordinate — not a person), the registry, what was disputed, our assessment on re-reading the public source, the action taken, and the response date. It holds no name, no email, no address, and not the message text. The correspondence itself is processed only to respond and then deleted (see /privacy); the de-identified case is what remains, so the evidence chain is preserved without keeping personal data.

Register (1 case, append-only)

Case dateComponentRegistryWhat was disputedOur assessmentAction takenResponse date
2026-08-14lastseen.dev observation hash chainlastseen-notaryThe published bootstrap chain anchor (Zenodo version 2026-08, head d1c0babc) sealed the then-current day's slice prematurely, before that day was complete.Confirmed. Caught by the chain's own monotonicity guard on 2026-08-14 when it refused to advance a chain whose sealed 2026-08-13 slice had changed after being sealed mid-day. Root cause: a day's slice is not sealable until the day is over.Corrected pre-launch. The chain now seals only completed days (date < today); the current day is never sealed. Rebuilt 2026-07-22 to 2026-08-13 with the complete 2026-08-13 slice; new head 4e165c74. Corrective Zenodo version 2026-08.1 (record 21933009) carries the new head; the bootstrap version 2026-08 (record 21920195, DOI 10.5281/zenodo.21920195) is retained in concept-DOI 10.5281/zenodo.21869879 lineage as the dated, tamper-evident record of this correction.2026-08-14