Evidence
Measured on real hardware
The run-level detail behind the latency figures: how each number was measured, on what, with the attribution behind it — including the gaps we log rather than hide.
The reference kernel result
Measured December 2025 · GIDE benchmark corpus
A single closed-form continuous-time (CfC) cell — the reference inference kernel — completes one forward pass in 0.767 µs on average.
Methodology
Arithmetic mean over 10,000 sequential inference calls after 1,000 warmup iterations, nanosecond-precision monotonic timing with compiler barriers.
Environment
x86_64 with AVX2; compiled with zig cc (Clang) at -O3 -march=native -ffast-math on the Zig 0.14.0-dev toolchain current at the time of measurement. The run predates our hardware-attribution harness, so the exact CPU model behind this figure is not on record — a gap we log rather than hide.
Independent re-runs
ARM (attributed)
A fully hardware-attributed run on a Neoverse-N2 (Clang 21.1.0) measures 0.75 µs mean with 0.76 µs p99 — within a few percent of the reference figure.
x86 (committed)
Committed x86 re-runs land between 0.81 and 0.91 µs mean.
The deployed controller
A deployed end-to-end controller measures ≈52 µs p50 / ≈94 µs p99 — the figure to cite for whole-controller latency. It clears the 10 ms real-time budget by roughly 190×.
Artifacts
The benchmark harness, per-run logs, and a hardware-attribution ledger live in the GIDE repository; nightly CI re-runs the suite on attributed runners and publishes the results.