Case 07 · Two marketplaces, one rail

Trade across marketplaces.
Prove it from both books.

A buyer whose system hands over Ariba-shaped documents and a seller whose system hands over Alibaba-shaped documents traded for two hours on separate machines without exchanging a message. Each kept its own book and sent the shared rail one 32-byte commitment per second.

Follow one deal end to end ↓

15,984,163deals in the two books

14,400 / 14,400frames admitted at the door · 32 bytes each

15,550 / 15,550sampled deals proven in both books · same relation

476–716witnessed NEOva2 positions

Two vocabularies. One grammar. One rail.

A deal is a trading relation both edges derive from the contract number alone. The buyer's order arrives in cXML vocabulary, the seller's confirmation in trade-order vocabulary; the edge turns each into a record in the same grammar. Every second the period is sealed and only the 32-byte snapshot hash leaves the company. The door admits it, the ledger seals it, two independent witnesses sign a public position, and positions fold into public units.

Ten seconds to two hours.

rung	deals (both books)	frames admitted	proven in both books	positions	verdict
10 s	30,274	20 / 20	38 / 38	40	PASS
5 min	711,315	600 / 600	671 / 671	41–49	PASS
15 min	2,076,757	1,800 / 1,800	2,072 / 2,072	52–82	PASS
30 min	4,145,789	3,600 / 3,600	4,144 / 4,144	83–143	PASS
60 min	8,109,367	7,200 / 7,200	8,160 / 8,160	144–264	PASS
120 min	15,984,163	14,400 / 14,400	15,550 / 15,550	476–716	PASS

Mean rate over the two-hour window: 2,220 deals per second (min 1,891, max 2,694). Edge memory 40 → 200 MB per process over two hours, linear — the file is the book; memory holds only the unsealed tail.

One deal, three shapes — the Ariba-shaped document, the canonical record and the 32-byte commitment, and the same on the Alibaba side — is published as one_deal_three_shapes.json.

Follow the work

One deal, from two systems to one public position.

Step through what happens to a single deal — the example deal from the two-hour verification file.

What we tested

The same deal named from the contract number in two books on two marketplace vocabularies.
Every sampled deal recomputed offline from its record to its witnessed position — from the buyer's kit and from the seller's kit.
Every frame of every rung admitted at the door and answered by the ledger; 0 receipts missing.
The edge fails closed: in the first two-hour attempt the disks filled at minute 99 and the edge refused to append rather than write a book it could not make durable. The rung was rerun and passed.

Make the next test yours

Agree a bounded scenario with a marketplace: one document type, one period, real documents in the marketplace's own shape. Compare with its existing reconciliation.
Shapes, not connections: the documents are shaped like those networks' documents so the pairing across marketplaces is real; neither Ariba nor Alibaba is connected.
Sampled deals one side reached in a second the other did not are reported one-sided, never paired (two hours: 353 buyer-only, 180 seller-only). Not proved: business truth of the documents, the era seal, or any connection to Ariba or Alibaba themselves. We are the bookkeeper: this shows what was recorded and witnessed, and when.

A result you can
inspect.

The report records the ladder, the two-hour counts, the example deal and the fingerprints of the verification files. Both companies' kits and the reference verifier are downloadable and run with the network switched off.

Download case results · JSON↓Both kits + verifier · ZIP↓The demonstration page and live view↗Explore all NEO World tests↗

Run fingerprint & method

Verification file SHA-256 (verify_trade.json): aca8a71e22f90ee0ee6d5475b541f1f2043c0b9b38856608a8c83e5d6f6f44b4

Fleet summary SHA-256 (summary.json): 9b7c364d15b5ece92ab4ddf7002d8658d3e4131676ccd97fb4c15b69228554b2

Case results SHA-256: 9abf35dc1b6092b65d7079e9e66e155cae29b0829221b6e3f11ed8eee34a91ee

Executed on hvar1 and hvar2 (Telemach) against the production door on neo-7, the NEOCL2 ledger and the NEOva2 archive; verification ran on neo-7 and on a clean laptop. This view presents recorded outputs. A hash identifies the tested record; it is not itself independent verification of business truth. NEObuyer and NEOseller are illustrative aliases; the vocabularies are shaped like Ariba's and Alibaba's documents and connect to neither.