Category #
Perspective — Contract Family
Definition #
The whole system of contracts a restaurant runs. Not a single contract. The architecture that holds every contract the operation runs with every counterparty, organized by form, ordered by counterparty, and coupled across the whole business. The choice of form the architecture runs in is the whole-business choice [Two Roads] names.
Explanation #
The operator does not choose contract form per counterparty. The operator chooses form for the architecture, and every counterparty contract inherits the form the architecture is running in. Guest-side, People-side, vendor-side, community-side — every contract inherits the architecture’s form.
The architecture runs in one of two forms. Not both. Not sometimes-both. One.
The [Transactional Contract] is the spot form. Present-tense exchange settled at close-out. Nothing accumulates. The contract terminates at the transaction boundary. Road 1. What a business designed for throughput and settled exchange runs.
The [Hospitality Contract] is the relational form. Consideration deposited above compensation. Accumulates across engagements. The contract exists AS the relationship. Road 2. What a business designed for belonging and compounded return runs.
The counterparty contracts couple. Guest-side relational contracts require People-side relational contracts to sustain — a cast that is not being invested in cannot produce the hospitality a Guest under relational contract expects. Break one and the other breaks with it. The operator running a [Hospitality Contract] with Guests while running a [Transactional Contract] with staff is not running mixed forms — they are running a broken architecture drifting toward transactional.
The most common failure is not choosing a form deliberately. The operator inherits transactional architecture from the industry default, adds hospitality signaling on top, and wonders why counterparties audit the mismatch. Guests read as customers. Cast reads as staff. The [Guest Contract] the operator thought they were running was never actually built, because the architecture underneath it was transactional.
Naming the current architecture honestly is the first move. Deciding which architecture the business is designed to run is the second. Building the coupling that holds the chosen form under pressure is the third.
