Merchant joins
A merchant joins the city market without surrendering its name, shop, assortment or existing customer relationship.
Merchants, hospitality, events, vouchers and delivery connect without flattening local identity.
A merchant joins the city market without surrendering its name, shop, assortment or existing customer relationship.
One resident basket can create multiple independent sales and one explainable payment across local stores and services.

Follow one authorised result from the first signal to durable evidence.
Buys from two shops in one basket.
Splits operational fulfilment.
The resident confirms each shop, item, fulfilment promise and total before one city basket becomes two sales.
OPS hands CORE the approved split basket and payment allocation; browsing context and unchosen shops remain private.
Creates two sales and one explainable payment.
Each shop retains its own responsibility.
Evidence keeps one customer confirmation while preserving separate sellers, stock, fulfilment, receipts and responsibility.
System boundaryOPS keeps the operational context. NUMA may assist inside that context. Only the approved, scoped and attributable result crosses into CORE.
A city voucher carries purpose, audience, validity and eligible spend so public or community value follows its mandate.
Local pickups can be bundled for efficiency while custody, service promise and revenue remain separate per merchant and order.
Open a scenario to see the operational action and ledger event.