Definition #
The instance-level contract signed by the operator and the Customer at each visit under [The Service Contract]. Contains three elements: offer (what the operator presents), acceptance (Customer chooses to engage), and compensation (Road 1 form — settled at close, nothing carries forward by design). Signed when the Customer walks in seeking transactional fulfillment and the operator’s operation is designed to facilitate the exchange. Parties are the Customer and the operator, mediated by Cast on human-delivered Road 1 operations and mediated increasingly through tech on Transaction+ operations where tech is a party to the Contract. The exchange is the point; there is no hosting layer on top. Signed at every visit.
Family #
Canon — MAJOR. Guest-side instance contract for Road 1. Inherits from [The Service Contract] as parent form. Corollary counterparty contract to [The Guest Contract] (which inherits from [The Hospitality Contract]). The transactional contract Road 1 operations sign each visit.
Why Behind the Thinking #
[The Customer Contract] is a legitimate contract, not a lesser one. Operators built to facilitate transactional fulfillment cleanly are serving a real Customer population well when they deliver on the exchange. Counter service, QSR, quick service, take-out, delivery-primary — all real businesses running honest [The Customer Contract]. Naming this Contract in canon, at parity with [The Guest Contract], closes an old argument in the framework: if [The Hospitality Contract] has [The Guest Contract] as its instance-level counterparty contract, [The Service Contract] must have [The Customer Contract] as its instance-level counterparty contract. Symmetric architecture. Same structural role. Different Contract terms.
The problem is not [The Customer Contract] itself. The problem is operators running [The Customer Contract] on the delivery side while marketing [The Guest Contract] on the acquisition side. That is [Operator Arbitrage]. The Customer attributes relational value to a Contract that only carries transactional value; the operator extracts transactional value while accepting the relational-value attribution the Customer offered. [Consent Erosion] runs from that gap — most visibly when the operator changes terms of the transaction layer (dynamic pricing surprises, subscription-plan changes, tip-prompt insertion at counter) and the Customer feels the breach on the relational value they had attributed to what they thought was more than a transaction. Naming [The Customer Contract] cleanly, in canon, lets the honest Road 1 operator run it without pretending, and lets the Road 2 operator avoid running it accidentally under Guest Contract language.
The Customer is the native instrument for [Reciprocity Test] on Road 1. Same felt read the Guest runs under [The Hospitality Contract], run against the terms of [The Service Contract]. The Customer feels transactional value delivered or not delivered on the visit. Where the Contract is honest, the felt read matches the marketing. Where the operator has inserted Road 2 compensation extraction (tip at counter without Road 2 service) or Road 2 marketing (relational language against transactional delivery), the Customer feels the mismatch even if they cannot name it. The current tip-prompt backlash is the aggregate felt read of a Road 1 Customer population refusing an asymmetric claim inside their transactional Contract.
Mine / Theirs / Ours (Ownership Map) #
Written from the operator’s seat.
Mine — the operator’s:
The offer signed at this specific visit. The clarity of what the exchange is. The clean, fast, reliable delivery of the exchange. The tech that mediates the exchange honestly, or the Cast that delivers it cleanly, or both. The pricing that matches Road 1 cost structure. The refusal to insert Road 2 extraction points (relational marketing, tip prompts against transactional execution, subscription-term drift) into a Road 1 Contract. Honest naming of the Contract on the acquisition side.
Theirs — the Customer’s:
Whether they accept the offer this visit. Whether they compensate as agreed. Their satisfaction with the specified exchange. Their honest attribution of transactional value to what is a transactional Contract. Whether they return for the next transaction on transactional terms.
Ours:
The transaction itself. The clean settle at close. The Contract expires at close by design — nothing carries forward, no Consideration bank, no relational obligation. The next visit signs a fresh Contract. That is not a failure of the Contract. That is what the Contract is.
Failure vector: the operator inviting relational-value attribution (through marketing, through tip prompts, through subscription-plan language) that the Contract’s transactional terms cannot honor. The Customer signs believing they are in a richer Contract than the Contract actually is; the operator extracts against the misattribution. [Operator Arbitrage] running against the Customer, one visit at a time.
Reciprocity Test (Manifest Level) #
Written from the operator’s seat.
What the operator must manifest to hold [The Customer Contract] under [The Service Contract]:
Road 1 architecture actually built. Clean transactional execution. Clear pricing that matches Road 1 cost structure. Marketing that describes the operation as transactional fulfillment done cleanly. No Road 2 tip architecture inserted at settle. No relational language inviting misattribution. Tech that mediates the exchange transparently if tech is the mediator.
What the Cast (or tech) must manifest:
Technical competence held to the standard. Clean, fast, accurate execution of the exchange. No pretense of Road 2 service where the Contract is Road 1.
What the Customer must manifest:
Presence in the exchange. Compensation at Road 1 level for the exchange as specified. Honest attribution — not tipping under coercion against a Road 1 delivery, and not expecting Road 2 relational benefits inside a transactional Contract.
Asymmetry failure — the counter-service tip prompt.
Operator runs [The Customer Contract] cleanly on the delivery side. Then inserts a tip prompt at settle asking the Customer to compensate at Road 2 level. Cast did not manifest Road 2 service. Operator did not architect Road 2. The Customer arrived to sign [The Customer Contract] and is being asked to fund [The Hospitality Contract] compensation for a Contract that does not exist. [Operator Arbitrage] running from the Road 1 direction. The current national backlash is the Customer population running [Reciprocity Test] on this pattern in aggregate and refusing the asymmetric claim.
Asymmetry failure — subscription and dynamic pricing.
Operator alters terms of the transactional Contract mid-relationship — dynamic pricing surprises, subscription-plan changes, loyalty program terms shifting. Customer signed the original Contract; operator changed it unilaterally. [Consent Erosion] on the transactional layer.
Pairs with #
[The Service Contract], [The Hospitality Contract], [The Guest Contract], [The Cast Contract], [The Operator Contract], [Reciprocity Test], [Operator Arbitrage], [Consent Erosion], [Consent Arbitrage], [2P Arbitrage], [Loyalty Arbitrage], [Amplification Principle], [The Affordability Lie], [Two Roads], [Lost Opportunity Tax], [Marketing as Architecture Amplification]
