BlueDocumentation
repo.blue ↗
Solutions

Guaranteed multi-party outcomes

Sell risk removal rather than a loose bundle by making confirmations, timing, substitutions, partial settlement, refunds, and disputes part of one coherent promise.

The problem#

A customer may avoid a complex purchase not because the components are expensive, but because coordinating several independent providers is risky. A coach trip, family event, renovation milestone, or multi-provider service can fail when one participant cancels, runs late, or disputes completion.

A collection of bookings does not automatically become one guaranteed outcome.

The Blue pattern#

A customer-facing Order represents the whole promise. Supplier Agreements or Offers define accepted capacity and fallback. Provider Orders record each concrete leg. A PayNote governs the customer transaction and any participant settlement. Process rules define required confirmations, deadlines, substitutions, partial completion, cancellation, and dispute.

The documents remain connected but bounded. A guide's failure does not let the restaurant rewrite its own confirmation. A substitution is an explicit process, not an invisible operator edit.

Example: Coach Stop Guarantee#

A 45-person group must park, use facilities, eat within a defined window, complete a museum or route experience, receive a local product, and return to the coach on time.

The Root can require confirmations from transport, restaurant, guide, and distributor. If the guide cancels, the process may select a substitute, switch to an accepted audio route, or refund that component. Payment completion waits for the required outcome evidence.

Agents and human control#

Agents are ideal for monitoring state, chasing missing confirmations, finding permitted substitutions, and proposing exception paths. The document can reserve material scope changes, final dispute decisions, and high-risk settlement actions for principals or named providers.

What can be proved#

Participants can inspect the exact promise, each provider fact, which fallback rule ran, how the amount changed, why capture or refund was requested, and which provider confirmed the rail outcome.

Why this matters#

The product is trust unlock. Removing coordination risk can create demand that never existed, rather than merely discounting existing demand.