What we built for SAP, in the order it was built — every step measured, every figure read from the running system or the evidence files, every page one click below. The rail underneath never changed: a company keeps its own book, one 32-byte commitment a minute leaves, the rail seals every ten minutes and every company holds its proof.
ApeiroRA's SDK and collector as published, into a NEO sink that keeps every company's records in its own book and answers each with a receipt; one seal a minute leaves. Two hours, none failed; the sinks stopped mid-work and came back with nothing lost.
OpenNebula places nine services across three provider clusters; every start and stop lands in the executing provider's own book. A German manufacturing group buys under one rule — German data stays in Germany — a host fails, the assistant moves inside the rule, and the month settles from the records alone.
Four companies' edges book a thousand records a second each and fold every minute into one commitment; ten thousand simulated companies send one a minute; a source loop pushes a hundred thousand objects a second through the same door. Every ten minutes the rail seals it and every edge fetches its proof.
The consortium's organisations run as twins on the same rail, each with its edge and SAP's collector in front: registrations, a deal day in the marketplace, data that stays home, one breach and ten rulings in a day, the month netted — the room's three figures, all read from the system.
Behind the four: the demonstrations page for ApeiroRA / 8ra (/demo/8ra/, the evidence files and the offline verifier), the marketplace with 2.7 million offers (/marketplace/), and the architecture. Nothing on these pages is promised that is not built.