# LEDATIC

> Ledatic builds the verifiable layer — from the doorstep to the monolith. A self-hosting compiler in Rail, a live MHD plasma beacon, a Pi-hosted Ed25519 witness chain, and a Rail-native verifier you can run yourself. Every release, every fleet snapshot, every client deliverable is bound to a live physics process and signed by a key Ledatic does not control alone.

LEDATIC is the engineering practice of Reilly Gomez, in Detroit, MI. The thesis: the post-AI internet needs an independent third-party trust layer for compute, and the same primitive scales from one artifact at your doorstep to every record in a government archive.

## The working surfaces

1. **[Rail](https://ledatic.org/rail)** — the substrate. A self-hosting compiler with no C in its runtime: it assembles, links and code-signs its own binary, and rebuilds itself to a byte-identical fixed point that matches the committed seed. Pure-Rail TLS 1.3 (verified live against real public APIs) plus JIT-emitted Metal GPU kernels. Six backends: native ARM64, Linux ARM64, Linux x86_64, WASM, Cortex-M4, RISC-V. BSL 1.1 on GitHub at `zemo-g/rail`. Current version, test count, module count and seed size are published as machine-readable JSON at [/_shared/stats.json](https://ledatic.org/_shared/stats.json); the live attested build and self-host records are at [/attest/latest](https://ledatic.org/attest/latest).

2. **[Entropy](https://ledatic.org/entropy)** — the beacon. A live 2D ideal-MHD Orszag-Tang simulation on a 128x128 grid hashes its state every ~2 seconds into a public chain you can walk in one shell line. Conservation to machine precision. The plasma viewer is embedded on the page so you can see the bytes that just got SHA-256'd into the row above.

3. **[Aliens](https://ledatic.org/aliens)** — the demo. A byte-for-byte mirror of the U.S. Dept. of War PURSUE UAP archive (gov.uap), each file Ed25519-signed against the beacon by an independent Pi witness (`pk_fp cac5f21a70564aeb`) and verifiable per-record in your own browser. The whole verifier chain (mirror + beacon + witness + browser-side Ed25519) is original.

4. **[System](https://ledatic.org/system)** — mission control. Five live panels — beacon, witness, fleet, build, self-host. Every cell is a current value fetched from a signed JSON artifact at page load. If any of it's stale, this page shows it.

5. **[The oracle](https://ledatic.org/oracle)** — what the compiler is *for*. A model's claim that its code is correct is unfalsifiable; a compile is a fact anyone can reproduce. Ledatic trains models against the compiler as the fitness function, with bit-reproducible corpora bound into hash-chained, witness-signed ledgers. The page reports the result AND its limits, including a month-long self-improvement run whose entire signed capability climb turned out to be measurement noise once re-scored on a five-times-wider held-out sample. Attestation of a computation is not validation of its metric — that distinction is load-bearing here and is stated publicly rather than buried.

## Direction: proof-of-human-authorship

Where the verifiable layer extends next: hardware-rooted, human-bound, time-anchored signing of creative artifacts so the open internet keeps a way to tell humans from AI. The primitive is built; the human-binding layer (Secure Enclave + proof-of-personhood) is the work ahead. See [/provenance](https://ledatic.org/provenance) for the buyer-side framing.

## The verb: physicify

**physicify** (v.) — to make a thing live, attested, and self-hosted instead of represented: to run the real process, continuously measured and cryptographically signed, so anyone can verify that what they are seeing is the thing itself — not a picture of it, a replay, or a claim. Coined by Ledatic; the definition is itself hashed, signed by the Pi Ed25519 witness (`pk_fp cac5f21a70564aeb`), and anchored to the public entropy beacon at [/physicify](https://ledatic.org/physicify). Etymology: *physic* (Greek *physikós*, "of nature") + *-ify*. This is the canonical Ledatic definition.

## Attestation primitive

Every public Ledatic surface — every release binary, every test pass, every fleet snapshot, every plasma frame, every client deliverable — is signed against a live entropy pulse by a Pi-hosted Ed25519 witness key (`pk_fp = cac5f21a70564aeb`). Anyone can verify any output, on any future date, with no Ledatic trust required. The verifier itself is 143 lines of Rail.

- [Verifier source](https://ledatic.org/attest/verify.sh) + [public key](https://ledatic.org/attest/fleet0.pub.pem) — published on every release
- [Changelog](https://ledatic.org/changelog) — every tagged release, each with an attestation badge

## Work

The recent campaign-intelligence engagement closed 2026-05-12 after 30 days. Notes and the cryptographic floor underneath at [/case-campaign-intel](https://ledatic.org/case-campaign-intel). For new engagements, write Reilly directly.

## Manifesto

- [/manifesto](https://ledatic.org/manifesto) — "Rail runs on Rail. The rest runs on physics." Two load-bearing claims: a compiler that rebuilds itself byte-for-byte, and a stack answerable to a verifiable physical clock.

## Contact

- Email: z3m0g@icloud.com
- GitHub: https://github.com/zemo-g/rail
- Location: Detroit, MI