PURSUE — attested mirror

Aliens

The Presidential Unsealing and Reporting System for UAP Encounters, mirrored byte-for-byte and walked across time.

Drag the handles on the timeline to scrub across the years the records cover. Each card is a real declassified file from war.gov, hashed on arrival and signed against ledatic.org/entropy/pulse at the moment we mirrored it. Press prove on any record to replay that check in your own browser.

Snapshot, not a current mirror. These 219 records were mirrored in May 2026 (release dates 5/8/26 to 5/22/26) and signed between pulse 741 341 and pulse 1 273 795. The source has not been re-checked since, so what you can prove here is that these bytes are the bytes we mirrored then, not that the archive still looks like this.

unknown unknown records: — agencies: — signed: — span: —

This archive renders in your browser from the signed manifest. Without JavaScript you can still fetch manifest.jsonl directly — every line carries the record's sha256, its beacon pulse, and a fleet0 Ed25519 signature, and check any record's signature with OpenSSL against the published key (verify.sh expects a different record shape and does not read these lines).

Timeline — incident date (release date for records lacking one) —

Sort Agency showing 0

How we keep this honest

Every record in this archive is a byte-for-byte copy of what war.gov published. As bytes flowed to disk we computed their SHA-256 (the files came through Safari, the only client war.gov's bot wall let through, and a Python relay hashed them) and bound each digest to a live entropy beacon pulse, signed by the fleet0 Ed25519 witness, a Pi that Ledatic runs. The prove button on every record replays that check here in your browser, verifying the signature against the pinned public key.

We hold the mirrored bytes; we no longer republish the documents themselves. That is a cost decision, stated plainly: the archive runs to about ten gigabytes with a single half-gigabyte file in the tail, and we are not spending that to re-host what a government already hosts. What you can still do is the part that matters — every digest, pulse and signature above is live, so anyone holding a copy of one of these files can check it against an attestation we published in May. We hold the witness key; what stops us from altering one is that every saved copy would show the change. Thumbnails are served, and each one was byte-checked against its own attested digest before we put it up; the handful that no longer match theirs are withheld rather than quietly reshot.

The recurring comparison against the war.gov source is currently paused — the status chip above says so honestly. The signed digests don't pause: if the source ever quietly changes a file, re-checking against these attestations will show it, and if we ever quietly change one, you can prove it.

The tool built for this is a single Rail binary called pursue: pure Rail TLS 1.3, streaming SHA-256, JSON, no curl, no SQLite, no libcrypto. This May snapshot was not made with it, because war.gov let only a browser through. Source is public. Run your own copy.

github → entropy beacon → signed manifest → verify yourself → fleet0 pubkey → about Rail →