Arc 2 — Business Cases by Sector

The KPOP Musical and the Pre-Arrangement Declaration

TS
Tom Sato Founding Maintainer, Activity Travel Protocol Contact →

Forty hotels, four agreements

A KPOP musical is announced for Broadway. The producers have the rights, the cast, the theatre. And they know the audience will travel — from Seoul, Tokyo, London, all over the world. Within a week, every luxury hotel in Midtown Manhattan calls. Every high-end tour operator sends an email. Forty potential partners, all wanting ticket allocation, concierge packages, preferred access.

The producers want to say yes to all forty. By opening night, they have signed formal agreements with four. The other thirty-six are still in email threads.

This is not a failure of relationships or intent. It is a failure of infrastructure. Every partnership agreement involves legal review, manual allocation tracking, a separate negotiation about cancellation policy, and a separate question about what happens if the show is cancelled. And even when a contract is finally signed, it is a PDF. The hotel's booking system cannot read it. When a guest at the concierge desk asks to add show tickets to their package, someone has to check a spreadsheet, make a phone call, and manually record the transaction. The agreement is real. It is completely invisible to every system that needs to act on it.

This is not a failure of relationships. It is a failure of infrastructure.

What the Pre-Arrangement Declaration does

The Activity Travel Protocol introduces the Pre-Arrangement Declaration: a structured, machine-readable B2B agreement that captures exactly what a contract captures — allocation rights, commercial terms, Duty of Care assignment, and disruption protocol — in a form that every booking system in the network can read, verify, and act on in real time.

Diagram — The four components of a Pre-Arrangement Declaration
Allocation

How many units are available, at what price, with what booking window and minimum lead time. Tracked in real time against confirmed bookings.

Commercial Terms

Commission structure, payment schedule, invoicing terms, refund policy. Agreed once. Operative in every booking that references the declaration.

Duty of Care

Who holds Duty of Care at each handoff point. Agreed in advance. Not resolved after an incident.

Disruption Protocol

What each party does if the event is cancelled, postponed, or disrupted. Automatic. Not negotiated in a crisis.

Once filed, the declaration is operative in every booking that references it. No phone call required.

How the booking flow works

Diagram — Booking flow and cancellation cascade
1
Guest requests hotel package with show tickets. Concierge system or AI agent initiates booking.
2
Security Kernel verifies Pre-Arrangement Declaration. Confirms it exists, is current, and allocation is available. Partner credentials verified in Party Registry.
3
Booking Object created. Duty of Care assigned per PAD terms. Allocation decremented. Booking confirmed without a phone call.
4
If show is cancelled: Disruption protocol activates across all active Booking Objects referencing the PAD. Each affected party receives notification per agreed terms. No manual coordination required.
The Security Kernel enforces the declaration at every state transition. If no current, valid PAD exists, no booking proceeds.

The distribution network: before and after

Diagram — The forty hotels
Today — four agreements
Partners reachedFour hotels and tour operators with signed PDF contracts
Other thirty-sixEmail threads, verbal commitments, informal arrangements
Booking processConcierge checks spreadsheet, calls producer's office, manually records transaction
CancellationEach partner contacted individually. Terms disputed.
With the protocol — forty partners
Partners reachedAll forty hotels and tour operators with filed Pre-Arrangement Declarations
Each declarationMachine-readable, verified, immediately operative in every booking system
Booking processSecurity Kernel validates PAD, Booking Object created, allocation confirmed automatically
CancellationDisruption protocol fires across all active Booking Objects simultaneously. Agreed terms applied.

Who benefits

For the Broadway producer, the Pre-Arrangement Declaration converts forty email threads into forty structured, machine-readable business relationships. The distribution network that took months to assemble for four partners can be extended to forty in the same time it took to sign four PDF contracts.

For the hotel concierge team, the declaration is the authorisation that makes the package bookable. Not a spreadsheet to check. Not a producer's assistant to call. A verified, current declaration that tells the booking system exactly what terms apply and what allocation is available.

For the fan flying in from Tokyo, the declaration is invisible — as it should be. What they see is a package with clear terms, a cancellation policy, and the confidence that if something goes wrong, someone agreed in advance to be responsible for making it right.

The Pre-Arrangement Declaration is not a mechanism built for Broadway musicals. It is a general-purpose B2B trust artefact. A ski resort building a network of local activity suppliers. A museum creating preferred partner packages with nearby hotels. A music festival coordinating accommodation, transport, and experience partners across an entire city. Any situation where one principal wants to build a structured, accountable, machine-readable network of business relationships at scale.

The forty hotels are now forty verified partners with operative terms and bookable allocation — without a single additional phone call.