Coordinate two businesses around one order
Combine Alice's MyOS Timeline and Bob's bank-backed Timeline into one complete, deterministic Order history.
This quickstart shows why Blue separates provider-backed histories from document execution. Two independent businesses contribute actions through different providers, while one Root reaches one reproducible result.
Define the shared Order#
Create a Dinner and Flowers Order with one florist Channel backed by MyOS and one restaurant Channel backed by a bank or business provider. Each operation is bound to the Channel that represents that business role.
The document does not have one generic provider setting. Provider identity remains visible per Channel.
Submit both confirmations#
Bob's provider timestamps the dinner confirmation slightly before Alice's bouquet confirmation. Alice's notification happens to reach the feeder first.
Notification arrival is only a wake-up hint. It does not establish processing order.
Close a common completeness frontier#
The feeder asks every active provider to reveal the complete history before a boundary after Alice's timestamp and to commit that no future entry will be placed before that frontier.
Bob's delayed earlier entry is returned during this step. The common safe frontier is limited by the slowest required Timeline.
Order the complete window#
The feeder sorts the complete set by timestamp and the published deterministic tie-breaker for equal timestamps across independent Timelines. Network arrival, thread scheduling, and database row order never participate.
The safe order is Bob first, Alice second.
Process one entry at a time#
PROCESS(Root0, BobEntry) produces Root1 with dinner confirmed. PROCESS(Root1, AliceEntry) produces Root2 with both legs confirmed.
A Root workflow can now emit the payment-capture Request because the condition is satisfied in one committed reality.
Add another provider without changing the model#
Add a government permit Channel, a payment guarantor, or a KYA agent Channel. The feeder includes each active Timeline when closing the window and applies the provider's claim only to the role it can credibly attest.
A bank need not own the conversation. MyOS need not declare settlement. A government registry need not own the Order.
Verify independent replay#
Run the same initial Root, provider-verified entries, completeness frontiers, ordering profile, registry, and runtime in another implementation.