Definition #
The instance-level contract signed by the operator and the Cast at each shift. Contains three elements: offer (role, hours, compensation, working conditions, development, standards), acceptance (Cast member shows up to execute), and either Consideration (Road 2 form — deposited above compensation as development, tenure trust, participation in the operation’s future) or compensation only (Road 1 form — settled at pay period, nothing accumulates by design). Which parent Contract form governs — [The Hospitality Contract] or [The Service Contract] — determines whether [The Cast Contract] is relational or transactional in substance. Signed at every shift.
Family #
Canon — MAJOR. Cast-side instance contract. Inherits from [The Hospitality Contract] as parent form when the operation runs Road 2, from [The Service Contract] as parent form when the operation runs Road 1 alone. Corollary counterparty to [The Guest Contract] and [The Customer Contract] on the Guest side. Signed at every shift.
Note on Cast Contract split — deferred to next workshop: symmetry with the Guest-side split ([The Guest Contract] under Hospitality, [The Customer Contract] under Service) argues that [The Cast Contract] should split into two entries by parent form. Workshop question deferred 08.11.2026. For this redraft, [The Cast Contract] stays unified with parent-form dependency named inside the Mine/Theirs/Ours and [Reciprocity Test] blocks.
Why Behind the Thinking #
Most operators think of Cast relationships as employment relationships governed by employment law and compensation structures. The frame’s move is to name the Cast relationship as a Contract with the same three-element structure as [The Guest Contract] and [The Customer Contract], and to observe that the parent Contract form choice governs both the Guest-side and the Cast-side. An operator running [The Hospitality Contract] with Guests but [The Service Contract] with Cast produces Cast who cannot produce hospitality because they have not received hospitality. The parent Contract form choice must be consistent across counterparties or the mechanics break down.
Cross-counterparty consistency is the load-bearing discipline. Road 2 [Hospitality Contract] cannot run with Road 1 [Cast Contract] underneath. This is the most common [Reciprocity Test] failure in the industry — operator claims Road 2 to Guests through marketing while paying Cast Road 1 wages, offering Road 1 development, treating shifts as transactional. The Guest is being asked to fund Road 2 experience the operator will not pay Cast to actually deliver. [Operator Arbitrage] running through the Cast Contract as much as through the Guest Contract — Cast subsidizing the arbitrage through under-compensated labor delivering against Road 2 demands.
The operator is the accountability party. Cast execution failures often trace to what the operator did or did not give Cast to work with — bad tools, bad standards, bad training, bad schedules, bad development. Blaming Cast for failures rooted in operator-side gaps is one of the two blindnesses named in [Operator Arbitrage]: either the operator cannot see the causal chain, or he can see it and will not name it. Both hold him accountable.
The operator produces hospitality inward to Cast the same way Cast produce hospitality outward to Guests. Same substance, same weight, same discipline. Presence (the operator shows up, is knowable, is available). Memory (the operator remembers who the Cast member is beyond their role). Recognition (the operator sees the Cast member’s work, growth, and contribution and reflects it back). Care (the operator treats the Cast member’s wellbeing as consequential, not disposable). Growth (the operator invests in the Cast member’s development because standing still is why people leave). Standards (the operator holds Cast to a standard because standards are hospitality — no standard is indifference dressed as flexibility). What Cast owe in return: the same presence, attention, memory, and discipline turned outward to the Guest under Road 2, or the same technical execution discipline against standards under Road 1.
[Never Treat A Guest Better Than An Employee] is the enforcement mechanism. The operator who hosts Guests warmly and treats Cast transactionally has a split posture the Guest reads eventually. The Cast Contract failing eventually produces the Guest Contract failing. The two Contracts are structurally linked.
Mine / Theirs / Ours (Ownership Map) #
Written from the operator’s seat.
Mine — the operator’s:
The offer signed at this specific shift. The standards. The training that made the standards executable. The systems and equipment that let Cast execute reliably. The scheduling that matches the work to the capacity. The feedback given during and after the shift. The consequences enforced when standards are not met. The environment that makes the shift worth showing up for. The pace and clarity of the operator’s own communication. On Road 2 specifically: the Consideration deposited inward — development, tenure trust, participation in the operation’s future. On Road 1 specifically: the honest transactional Contract with Cast — clean pay, clean hours, clean expectations, no relational demands the compensation does not support.
Theirs — the Cast member’s:
Whether they accept the offer this shift. Whether they execute to standard. Their preparation, presence, effort, and behavior during the shift. Their willingness to be developed. Their willingness to meet feedback with change. The consequences they face when they do not meet the offer they accepted.
Ours:
The shift itself. The execution of the operation together. The trust built across shifts. The Cast-to-operator relationship that compounds or erodes based on both parties holding their side. On Road 2: the accumulating Consideration bank that produces tenure, capability, and cultural continuity. On Road 1: the honest transactional exchange that closes at each pay period without pretense of relational carry-forward.
Failure vector: the operator absorbing Cast-side execution failures — picking up dropped balls, covering shifts, rescuing outcomes that would have been the teaching moment. Every rescue steals the development. The inverse — blaming Cast for failures rooted in operator-side system, training, standard, or scheduling gaps — steals accountability from the operator’s own side. Both collapse the Contract.
Reciprocity Test (Manifest Level) #
Written from the operator’s seat.
What the operator must manifest to hold [The Cast Contract] under [The Hospitality Contract]:
Road 2 wages. Road 2 development investment. Road 2 tenure trust. Road 2 Consideration deposited inward at parity with what the operation asks Cast to produce outward. Working equipment. Clear standards. Honest feedback. Recognition. The operator manifesting hospitality inward is the precondition for Cast manifesting hospitality outward.
What the operator must manifest to hold [The Cast Contract] under [The Service Contract]:
Road 1 wages honestly paid. Clean transactional terms. Working equipment. Clear execution standards. Training that builds technical capability. Systems that support execution. Honest feedback against the standards. No relational demands the Contract does not compensate for.
What Cast must manifest under Road 2:
Hospitality produced outward — presence, memory, recognition, care, standards. Not scripted service. Not “customer experience.” Rehearsed hospitality of a Cast that has been developed to produce.
What Cast must manifest under Road 1:
Technical competence held to standard. Clean, fast, accurate execution. No pretense of Road 2 service where the Contract is Road 1.
Asymmetry failure — the dominant cross-contract failure.
Operator runs [The Hospitality Contract] on the Guest side while running Road 1 [Cast Contract] on the Cast side. Road 2 marketing to Guests, Road 1 wages and development to Cast. Cast is being asked to produce hospitality without receiving hospitality — asked to manifest Road 2 outward on a Road 1 offer inward. The Contract fails immediately at the manifest level because Cast cannot produce what they have not experienced. The Guest feels the failure on the visit. [Operator Arbitrage] running through the Cast Contract, funded by Cast under-compensation.
Asymmetry failure — Road 2 tips extracted against Road 1 Cast Contract.
Operator pays Cast Road 1 wages, calls them tipped Cast, and structures the operation so that Cast income depends on Road 2 tip generation the operator has not built the Cast Contract to support. Cast is under-paid on the operator side and asked to close the gap by extracting Road 2 compensation from a Guest population the operation may or may not be manifesting Road 2 to. Contract asymmetry compounds — Cast subsidizes operator, Guest subsidizes Cast, operator collects the spread.
Pairs with #
[The Hospitality Contract], [The Service Contract], [The Guest Contract], [The Customer Contract], [The Operator Contract], [Reciprocity Test], [Operator Arbitrage], [Never Treat A Guest Better Than An Employee], [Real Team Work], [The Lead Family], [Discipline Architecture], [Role As Verb], [Accountability Demand], [Authority To Execute], [Consent Erosion], [Two Roads], [Lost Opportunity Tax]
