Case 06 · Lab8ra-inspired community · Synthetic end-to-end

A month of
shared work.
Every balance closed.

Three providers contribute edge, compute and AI services. Follow the entire business cycle: useful work, a disputed delivery, shared accounting and confirmed simulated settlement before expiry.

Run the business month ↓

24service deliveries recorded

1.10Maccepted gross · µCLU

180Knet amount · µCLU

6 / 6claims settled in simulation

An executive walkthrough

Good collaboration survives a difficult day.

Move through the month or jump directly to a business event. Each scene comes from the executed test.

Jump to

The completed month
Every accepted delivery recorded. Every claim discharged before expiry in the simulator. No duplicate payment. No remaining book balance. NEOai exits after its account is reconciled.

NEOedge: paid 180,000 µCLU-equivalent in simulated settlement.
NEOcompute: received 60,000 µCLU-equivalent in simulated settlement.
NEOai: received 120,000 µCLU-equivalent in simulated settlement.

This is a synthetic operating demonstration: scripted providers, simulated payment confirmations and no real bank transfer. The 30 business-day labels tell the story; deadlines are counted only by live folds carrying a heartbeat. A real payment provider and partner services are the next integration step.

Work first. Accounting follows acceptance.

NEOedge, NEOcompute and NEOai exchange six services in each of four rounds. One delivery is disputed; a synthetic Chamber ruling reduces its value before posting. The records retain the outcome and its origin.

A disruption does not become a duplicate payment.

First, the payment simulator becomes unavailable: the claim stays open. Then a payment succeeds but its response is lost. The runner reconstructs the book and reopens the durable payment store. Retrying with the same payment identity recovers the confirmation without paying again.

A member can leave with its contribution respected.

NEOai requests an exit on day 25. The scenario schedules no more work for it and checks outstanding authorizations, claims and debt. Its account is reconciled on day 26. This demonstrates the exit condition; it is not yet an automated membership service.

Bring one shared service workflow. We can show how its records become an agreed community balance—and what remains to be paid.

The next real pilot has a concrete starting point.

Select interested providers, one service and an agreed period. Connect their accepted delivery records, agree the settlement arrangements and compare the result with their present process. The accounting and audit role covers the records supplied by members.

Tested through the full cycle

24 unique deliveries and three non-empty netting cycles.
A pre-posting Chamber ruling and a heartbeat outage.
Unavailable provider, lost response and restart recovery.
Six claims discharged at age four or five of an eight-live-fold window.
Book replay and net member positions reconcile exactly.

The implementation boundary

No real services, bank transfers, FX conversion or new public rail anchoring.
Payment scheduling and the exit scenario are explicit pilot assumptions.
Persistent payment failure still requires operational intervention before the deadline; this test does not guarantee funding or payment availability.
Existing CLU expiry rules remain unchanged. An unconfirmed or expired claim is never relabelled paid by the settlement adapter.

The whole month.
One inspectable result.

The aggregate report includes the timeline, payment confirmations from the simulator, retry outcomes, checks and fingerprints of the resulting book.

Download the month’s results · JSON↓Start with the six-exchange Lab8ra example↗

Run fingerprint

01394724e8e070c653e6c52b7ee0e4608c86649e437511a276f476feade4fa40

Existing CLU engine; simulated participants and provider. Company-style aliases do not indicate endorsement or participation by Lab8ra members.