The verifiable layer — from the doorstep to the monolith.
The code your computer runs. The creations your humans make. A self-hosting compiler with zero C dependencies, every release signed against a live MHD plasma beacon, verifiable in 143 lines of Rail. Built in the open.
Rail v5.1.0 · 141 tests green · Self-hosting since 2026 · Detroit, MI
The compiler you run is the compiler you read.
Rail · ~1.0 MB · No backdoor · No ICE between you and your tools
The compiler. The MHD simulation that becomes the beacon. The TLS stack carrying signatures from a Pi over Tailscale. 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.0 MB seed binary you can read end to end. No npm. No Python. No runtime.
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.
One record, one chain, "ok" in your browser. Pick any file from the archive — your browser re-derives the Ed25519 signature against fleet0's public key and the live entropy pulse.
FleetLive mission control. Every node's state signed every minute by a Pi witness sitting on its own key.
ArchiveByte-for-byte mirror of the Dept. of War PURSUE UAP archive. Every file Ed25519-signed against the beacon, browser-verifiable per record.
MonolithWhere this goes next. A signed lineage for every AI-touched artifact — what was written, when, by whom, anchored to physics nobody owns.