One language under everything you just verified.
The compiler. The MHD simulation that becomes the beacon. The TLS stack carrying signatures from an independent witness. The 143-line verifier behind the button up top. The site you're reading. All of it Rail. All of it compiles to a single ~1.2 MB seed binary you can read end to end. No npm. No Python. No runtime.
the compiler you run is the compiler you read
Same primitive. Every scale.
A signature you can re-derive in your browser, anchored to a public physics process nobody controls, witnessed by an independent key. That primitive runs from one artifact at your doorstep all the way out to every record in a government archive. Same chain. Different scope.
Verify
One record, one chain, "ok" in your browser. Pick any file from the archive — your browser re-derives the Ed25519 signature against the witness's public key and the entropy pulse it was anchored to.
FleetSystem
Mission control, sentinel-checked. Every surface renders unknown until a signed check passes — nothing glows that hasn't proven itself.
ArchiveAliens
Byte-for-byte mirror of the Dept. of War PURSUE UAP archive. Every file Ed25519-signed against the beacon, browser-verifiable per record.
MonolithProvenance
Where this goes next. A signed lineage for every AI-touched artifact — what was written, when, by whom, anchored to physics nobody owns.
45 tagged releases and counting.
the release figure above is a working prove button — press it and your browser fetches the tagged binary, hashes it, and checks the witness signature itself
No one can retro-fabricate a heartbeat.
The beacon ticks every ~2 s. Kept up, that is roughly 220 million unbroken pulses by 2040 — a hash chain nobody can fabricate after the fact, with every deploy of this site signed into it. It starts here.
fourteen years from now, this page will be able to prove what it said today