Case 04 · Lab8ra-inspired cloud & edge community

Trade more.
Settle less.

An edge provider, a compute provider and an AI service provider help one another deliver. CLU turns their accepted work into a clear community balance, so only the remainder needs external settlement.

Explore the six exchanges ↓

280,000accepted gross · µCLU

200,000bilateral residual · µCLU

50,000community residual · µCLU

75%less residual vs bilateral

Three members. One shared picture.

NEOedge provides local execution. NEOcompute provides processing capacity. NEOai provides analysis. Each participant buys and supplies services across six agreed exchanges. These are synthetic roles chosen to make a shared cloud and edge economy tangible.

In this example, settling each pair separately leaves 200,000 µCLU outstanding. Considering the whole community leaves 50,000. That is 75% less value left for external settlement than the bilateral baseline, with every member’s net position preserved.

The contribution stays. The balance gets smaller.

Each accepted delivery remains in the record. Netting offsets reciprocal obligations; it does not erase anyone’s earned net position. In a real pilot, the residual can be paid through agreed money settlement arrangements.

These results measure the amount left to settle. They do not measure revenue, profit, cash already paid or operating-cost savings. All amounts use µCLU, the lab’s accounting unit.

Follow the work

From six exchanges to a net balance.

Step through the accepted deliveries, then compare pair-by-pair and community netting.

What we tested

The same accepted records under bilateral and community netting.
Every participant’s net position remains the same.
Replaying the events reproduces the same state.
Across both pilots: eight scenario variants and 56 checks passed; six regression tests passed.

Make the next test yours

Bring one reciprocal service exchange to a Lab8ra working session. Agree participants, accepted delivery records and settlement rules, then replay the same comparison using partner-approved data.
The proposed operating model keeps business data with partners and provides accounting and an audit trail of their records.
This test uses scripted synthetic participants and values. No real payment, new public anchoring or member endorsement is claimed.

A result you can
inspect.

The report records the amounts, checks and event hashes. It includes one-way trade, a fully balanced cycle and a pre-posting Chamber ruling. Late tariff corrections and real partner integrations are future pilot work.

Download aggregate test results · JSON↓Continue through a complete business month↗

Run fingerprint & method

Event hash for this scenario: 99ecce794dc5a60c0532931a5211582a10e481645cb6f07ae86f4bd1538ab60e

Report SHA-256: 74c12ff275f9644e1f9bf8f95824d0ab9023dfeb1c30ff8bbbb0eeaa2c4b5d1e

Executed with the existing CLU engine. This view presents recorded outputs, rather than executing the engine in your browser. A hash identifies the tested record; it is not itself independent verification of business truth. Company-style names are illustrative aliases; these are NEO’s synthetic cases inspired by Lab8ra and GSMA ecosystems.