Live data
Everything recorded, and what was concluded from it.
Every event carries the verdict reached, the reasoning behind it, and the version of the discriminator that produced it. Nothing is deleted when the platform changes its mind: a re-run adds a verdict beside the old one and demotes it, so the history of how an opinion moved is part of the record.
Query
Filter, then take the URL
Filter
connectingGET /api/archive/events?catalogues=complete&limit=50
Querying the archive…
A catalogue that was down is not a catalogue that found nothing
Events whose catalogue checks could not all be performed are excluded by default. If the aircraft transponder feed was unreachable, every aircraft that night looks unexplained, and an archive that quietly counted those would manufacture mysteries out of its own outages. The filter is there if you want them, and the count of what it removed is always shown.
Take the whole thing
The full archive downloads as newline-delimited JSON, one table at a time, with a manifest carrying the row count and a SHA-256 of the content. An analysis can name the exact bytes it was computed from, and a later reader can check they have the same ones.