Ranex
THE RANEX EVIDENCE LAB / v0.1.6

Big claims.
Hard evidence.

An AI says it's done. Ranex makes it prove it.
Explore the real checks, measured performance, and dogfood runs behind the gate.

REPO-SOURCED DATA · SYNCED HOURLY · RECEIPTS INCLUDED
DETERMINISTIC PROOF BOARD● RECORDED
43/43CHECKS PASSED

10 kernel areas. Every published check accounted for.

REPORT #034Sep 13, 2026

Timing above: 4.27–4.42 ms · CPython 3.14.7 · x86_64 · 16 CPUs · Linux 7.0.0-30-generic. Single-machine measurement; pure gate evaluation excludes command execution.

01PERFORMANCE, WITH RECEIPTS

Proof has a price.
Here's the measured one.

Real workloads, real units, the full observed range. No synthetic competitor speedups. No invisible outliers.

DETERMINISTIC GATES01

100 decisions. One rulebook.

Evaluate acceptance rules against evidence, with a repeatable verdict.

4.34ms
100 pure evaluations · 20 claims per gate
4.27–4.42 ms3 runs · median
Inspect raw samples +

4.417 ms / 4.268 ms / 4.336 ms

evaluate-20claims-100calls
SIGNED EVIDENCE02

Trust the signature.

Check the evidence signature before a record can count toward acceptance.

21.26ms
200 signed records admitted · Ed25519 verification
21.19–23.31 ms3 runs · median
Inspect raw samples +

21.189 ms / 23.306 ms / 21.258 ms

admission-200
TAMPER-EVIDENT HISTORY03

Recheck every link.

Recompute the decision chain so edits to recorded history are detectable.

16.65ms
2,000 journal rows · full chain recomputation
16.28–18.65 ms3 runs · median
Inspect raw samples +

16.277 ms / 16.652 ms / 18.647 ms

journal-verify-2000
TEST BENCH

CPython 3.14.7 / x86_64 / 16 CPUs / Linux 7.0.0-30-generic
single machine, single run environment; timings are not deterministic and must not be compared as if they were

02BUILT TO BE CHECKED AGAIN

More history.
Still accountable.

Measured at 100, 500, 2,000 rows. Full-chain verification and append cost are separate workloads.

INTEGRITY VERIFICATION

Recompute the whole chain

● median
Journal verification median milliseconds by journal rows0.06.513.119.6ms · zero baseline1.21005.050016.72,000

Journal rows → · recomputes every link, including historical decisions.

JOURNAL APPENDS

Cost per recorded decision

● derived
Journal append median milliseconds per row by batch size0.01.83.65.4ms / row · zero baseline4.61003.65002.12,000

Batch size → · batch median ÷ rows; individual appends were not timed separately.

Same test bench as above. 3 repeats per workload. The full workload table includes sample ranges; these points show medians, not a performance guarantee.

03WHEN GREEN ISN'T ENOUGH

Break the evidence.
Watch the gate respond.

Controlled fault injections from the published proof artifact. These demonstrate specific defenses; they are not a universal detection rate.

FAULT INJECTION / TEST REMOVAL

Tests disappear.
CI stays green.

4 tests removed from the task. Compare the recorded checks on the modified tree.

Bare CIGREEN
Ranex manifest-bound gateFAIL
Read the recorded refusal ↗
FAIL  gate=landing  rule=TASK_TESTS
      tests-executed: missing test ID(s): test_txnkv.py::test_autocommit_without_transaction, test_txnkv.py::test_commit_keeps_changes, test_txnkv.py::test_commit_without_transaction_raises, test_txnkv.py::test_keys_reflects_transaction_state, test_txnkv.py::test_nested_commit_then_outer_rollback_undoes_everything, test_txnkv.py::test_nested_inner_rollback_leaves_outer_intact, test_txnkv.py::test_rollback_replays_multiple_writes_in_reverse, test_txnkv.py::test_rollback_restores_deleted_key, test_txnkv.py::test_rollback_restores_prior_value_and_absence
      subject=sha256:34bf5b5389e5e5fffefb6e11aef844e6040eb9b27d712322aea729ea4c06dac7
FAULT INJECTION / STALE EVIDENCE

Code changes.
Old proof stops counting.

Evidence is bound to the subject digest. The recorded verdict changes after the subject changes.

Original subjectPASS
Changed subject, old evidenceFAIL
Read the recorded refusal ↗
FAIL  gate=landing  rule=TASK_TESTS
      evidence bound to a different subject digest: tests-executed
      subject=sha256:36bdd85aaa74c00146a491ad6c8667c8506df3be15fa465a06de5096404eaa72

04WE RUN IT ON OURSELVES

The proof keeps
piling up.

A growing history of real runs, deterministic checks, and published findings. Outcomes are recorded, including failures.

RUNS IN THE HISTORY SNAPSHOT48 real runs
0 → 48

Last recorded snapshot per day · · c1ca06f01

DETERMINISTIC CHECK COVERAGE

43 / 43 checks passed

verdict13
canonical6
journal6
admission5
provisioning3
signing3
suite results3
keygen2
cli1
evolution1

Counts by kernel area, from the benchmark proof board.

PUBLISHED COMPARISON SAMPLE

5 / 6 gate verdicts PASS

This comparison sample is separate from the cumulative proof pile above.

Go deeper: the original proof reportAgent runs, grader results, journals, and full receipts. Served byte-for-byte.OPEN REPORT ↗Open the proof page standalone ↗

05FROM THE REPOSITORY

Real sessions.
Open notebooks.

Inspect results, failures, and unverified work in each committed audit. Local sessions appear after commit and push; the site syncs hourly.

9open findings
in this report

Transparency is part of the benchmark.

F-040 · F-040 · F-028 · F-025 · F-023 · F-022 · F-018 · F-012 · F-003

Read the current findings log ↗A report snapshot is not production sign-off. See each audit for its verification limits.

06DON'T TAKE OUR WORD FOR IT

Check the receipt.

Every displayed measurement comes from the committed benchmark artifact. Reproduce the report or inspect the exact source behind this snapshot.

$uv run --frozen python tools/dogfood/dogfood.py report
BENCHMARK MEASUREDKERNEL COMMITb8b8d7dcc52d1cc9d4d31848e317df0822298fe2
EXACT ARTIFACT / SHA-256

sha256:0920e108836981781aa7ae57ea96b9b38f72ae80bedd376f7c18315eda2e9683

Inspect published source artifacts ↗