Verify

Check the download, and read this box out loud.

Two things you can check for yourself. The published tarball checksum, so you know the bytes you run are the bytes we shipped. And this reference box's own live self-report, straight from its read-only API, so the armed mechanisms and residency are not a claim on a slide.

How to read this page
  • Own absolute numbers only. Everything here is measured on this box. We publish no vendor benchmarks and no head-to-head numbers against other systems.
  • Dataset sizes are declared reference counts. Node and edge counts for the public SNAP graphs are the datasets' declared counts. Any throughput or latency is measured live on this box.
  • Value-log source of truth, bounded re-derivable indexes. Truth is the append-only value log; indexes are bounded and rebuilt from it. The bet is bandwidth, scan and fuse at the drive's sequential ceiling.
  • Local by default, no phone-home. The loop runs entirely on this box. Nothing here calls out to a third party, with or without a network.
Verify the download

Match the bytes before you run anything with sudo.

Fetch the checksum file and the tarball from the same host, then let sha256sum -c compare them. A pass prints semurg-r11-installer.tar.gz: OK.

curl -fsSLO https://one.semurg.io/dl/SHA256SUMS && curl -fsSLO https://one.semurg.io/dl/semurg-r11-installer.tar.gz && sha256sum -c SHA256SUMS

Published SHA256SUMS

d38d5bbc44b099e9e988a72f310a72f6e9b72f1666c47825b440ec23999a56e5  semurg-r11-installer.tar.gz

This is the exact content served at /dl/SHA256SUMS. Open it in another tab and confirm the line matches character for character.

This box, live

Armed mechanisms and residency, from the box's own API.

The values below are baked from this box's last read of its own read-only /api/health and /api/dashboard. Your browser then re-reads the same endpoints and overwrites them with the current figure. If the box is not reachable from where you are, the last-measured values stay, with a stamp that keeps aging. No spinner, no invented number.

showing last-measured values

Mechanisms (GET /api/health)

mechanisms armed
engine reports its mechanisms live
armed
hot set resident
working set pinned in RAM
13.85 GiB
fast disk path
direct, high-throughput reads
on
direct writes
no OS write cache in the path
on

Residency (GET /api/health)

resident bytes
14874841088 (13.85 GiB)

Hardware (GET /api/dashboard)

measured live on
semurg-research-cdg2 (8 physical cores)

The engine build is chosen per CPU at install time and is not exposed as a field on these endpoints, so it is not shown here rather than guessed.

Last measured on this box: just now. Baked read taken 2026-08-11T00:55:29Z. Read the raw JSON yourself at /api/health and /api/dashboard.
What is not on this page. No fresh, after-churn, or recovered read figures are quoted yet; those are still being measured and will be published together. For how an edited store ages between checkpoints, see Storage and the aging store in the docs.