Mission control

System

Bound to physical time.

Nothing in these panels is a deploy snapshot (only the footer's figures are stamped at deploy). Each panel cites the public endpoint it reads, ages are denominated in pulses of the entropy beacon (wall clock is the italic translation), and a chip only says a surface is alive after this page has actually confirmed it. If a surface cannot be confirmed from here, the chip says that instead.

Beacon — entropy/pulse checking…

pulse_id
…
value_hex
…
timestamp
…

The plasma instrument publishes a hash-chained pulse every 2 s. The clock in the corner of every page is this feed.

Witness — fleet0 chain head checking…

pulse_id
…
age
…
chain_verified
…
pk_fp
…
witnessed
…

A witness on separate hardware (a Raspberry Pi that Ledatic runs) signs pulse_id|value_hex|witnessed_at for each pulse it sees; it does not check the links yet. The fields above are its own latest record, shown raw.

Fleet — witnessed snapshot checking…

surfaces
…
snapshot pulse
…
snapshot age
…
witness pk_fp
…

Build — last attested test run checking…

commit
…
pass / total
…
status
…
pulse window
…
log sha256
…

Self-host — fixed point checking…

commit
…
fixed_point
…
seed_match
…
seed sha256
…
pulse window
…

Verify any of this yourself

The prove buttons above run the proof in this tab — fetch, hash, pinned key, Ed25519, pulse anchor — and print a pasteable receipt. Nothing executes server-side. The shell recipe below is the out-of-band path: same checks, your machine, no browser.

# Pull the verifier and a release attestation, then verify locally.
curl -sf https://ledatic.org/attest/verify.sh -o /tmp/verify.sh && chmod +x /tmp/verify.sh
curl -sf https://ledatic.org/releases/v5.5.0/rail_native -o /tmp/rail_native
curl -sf https://ledatic.org/releases/v5.5.0/rail_native.attestation.json -o /tmp/rn.att.json
/tmp/verify.sh /tmp/rail_native /tmp/rn.att.json
# → ok artifact=rail_native pulse_id=… pk_fp=cac5f21a70564aeb