[Relational Reward]

Definition #

[Relational Reward] is the Road 2 branch of [Reward Structure Architecture]. It names the class of reward mechanisms keyed to compounding outcomes across multiple operating cycles — rewards where the causal chain from action to full payoff runs longer than one cycle at the node’s cadence, and where the compounding payoff cannot be fully collected inside a single cycle.

Sits under [Two Roads] as the relational-side reward manifestation, running Road 2 through the incentive dimension. Pairs with [Transactional Reward] as the two branches held inside [Reward Structure Architecture]. Every operation runs some [Relational Reward] wherever compounding outcomes are being funded; the load-bearing question is whether the class holds load-bearing positions at compounding-outcome nodes or has been chronically underfunded by the natural weighting bias.

Not inherently superior to [Transactional Reward]. The class is coherent at nodes whose outcomes are compounding — cast development pathway, Guest recovery investment, positioning capital build, meaningfully differentiated value build, kitchen manager development. The class is incoherent when it fills nodes whose outcomes are themselves single-cycle. Produces compounding Profit when it holds load-bearing positions in the architecture — slower per-cycle numbers, but compounding across cycles as the compounding bases build.

Mechanism #

[Relational Reward] has a specific signature. Every mechanism in the class has a payoff window that runs longer than one operating cycle at the node’s cadence. Cast development pathway pays out in cast capability compounding over quarters and years. Kitchen manager development investment pays out in autonomy and judgment build across the manager’s tenure. Guest recovery investment pays out in Guest re-encounter over months and years. Positioning capital marketing spend pays out in category-of-one recognition across the operation’s lifetime. Meaningfully differentiated value build pays out in defensible margin sustained across every subsequent cycle. The reward completes across multiple cycles, not within one. If the payoff window closes inside a single cycle, the reward is not [Relational Reward] — it has moved into the [Transactional Reward] branch even if the vocabulary suggests otherwise.

The [Causal Read] confidence profile. [Relational Reward] runs on low-to-medium certainty + low-to-medium immediacy anticipations. The causal chain from investment to full payoff is not visible in a single cycle. The operator cannot see the chain by pattern-matching against short-cycle observation; they have to run disciplined [Causal Read] work — build the causal model explicitly, hold the anticipation through multiple cycles, update the model against partial observations as compounding accumulates. This is the confidence profile that makes [Relational Reward] feel irrational without disciplined design work. The mechanism reads as “cost with no visible return” to a [Causal Read] that has not been disciplined to see compounding chains.

The natural weighting bias against Relational. Per the physics locked in [Causal Read], the operator’s natural weighting bias systematically overweights high-certainty + high-immediacy anticipations and suppresses low-certainty + low-immediacy anticipations. [Relational Reward] mechanisms sit at the low-certainty + low-immediacy corner of the confidence space — exactly the corner the bias suppresses. This is why [Relational Reward] is chronically underfunded in defaulted architectures. The bias is running whether the operator sees it or not. Without disciplined override, the architecture starves the Relational branch at every node where the bias can suppress it, which is every node whose outcome is compounding rather than single-cycle. The undertunding is not a preference decision by the operator; it is the physics of the default architecture running unchecked.

The disciplined override requirement. [Relational Reward] does not install by intent. The operator can state relational intent — “I invest in my cast,” “I build for the long term,” “we care about Guest experience” — while running an architecture that starves every Relational node the intent claims to fund. Intent does not override the weighting bias. The only mechanism that overrides the weighting bias at Relational nodes is disciplined [Causal Read] work — the operator explicitly building the causal model from investment to compounding outcome, holding the anticipation at named confidence and named timeline, updating the model against partial observations across multiple cycles, and refusing the framing that suppresses the anticipation when it fails to arrive on Transactional-cadence expectations. Without the discipline, [Relational Reward] mechanisms get installed as line items and then defunded whenever this-cycle cash pressure hits, because the [Causal Read] cannot defend the anticipation against the visible pressure of the current cycle.

Where it is coherent. Every node whose outcome designed is compounding. Cast development pathway. Kitchen manager development and autonomy build. Cast promotion pathway when treated as compounding capability recognition. Guest recovery investment authority and budget. Guest re-encounter investment. Positioning capital marketing spend. Meaningfully differentiated value build. Operator draw structure components that fund compounding investments before extracting this-cycle cash. Vendor relationship terms structured for compounding partnership rather than transactional squeeze. Coherence is when the outcome designed at the node compounds across cycles and the reward’s payoff window matches the compounding timeline.

Where it produces incoherence. [Relational Reward] produces incoherence when it fills a node whose outcome designed is itself single-cycle. Cast base comp needs to hit per-shift because cast members live per-shift; “we’ll pay you when the operation compounds” is not a coherent base comp mechanism. Vendor payment discipline needs single-cycle reward because vendors bill per invoice cycle. Cash-cycle discipline components in the operator draw need to run per cycle because cash cycles run per cycle. The class is not the wrong branch for these nodes; [Transactional Reward] is the right branch. Relational-dominant configurations at single-cycle nodes starve the operational discipline that makes the operation function through today’s cycle so tomorrow’s cycle can compound.

The compounding Profit pattern. When [Relational Reward] holds load-bearing positions in the architecture — cast development funded, Guest recovery funded, positioning capital funded, meaningfully differentiated value funded, kitchen manager development funded — the operation produces Profit through compounding rather than through extraction. Cast capability accumulates and produces GX quality that pricing power tracks. Guest recovery investment produces Guest re-encounter compounding that raises the operation’s frequency baseline. Positioning capital builds category-of-one recognition that shifts the operation off price competition. Meaningfully differentiated value builds defensible margin sustained across every subsequent cycle. Compounding Profit reads slower per cycle than extraction Profit at the peak of an extraction run, but compounds across cycles instead of extracting from a finite base. The Profit curve is different in shape — flatter early, steeper later, sustained where extraction is depleting.

The cascade signature. [Relational Reward] at the operator layer is the enabling condition for [Relational Reward] at every downstream layer. When the operator’s own reward layer holds Relational components — the operator draw structure funds compounding investments before extracting this-cycle cash, the operator’s time allocation includes multi-cycle investments (positioning capital work, cast development work, meaningfully differentiated value work) — the operator’s [Causal Read] on Relational alternatives at downstream nodes runs with lived confidence rather than with abstract theory. The operator has seen their own Relational investments compound; they can see cast-layer Relational investments compound because the causal pattern is the same at different altitudes. The cascade runs downhill from operator posture through operator draw structure through operator time allocation through cast reward mechanisms through Guest experience investment through Profit configuration.

The recognizable moment. [Relational Reward] as a category becomes visible when the operator recognizes the underfunding pattern — the specific nodes where the operator’s intent is Relational but the installed mechanism is Transactional or absent. The moment often shows up when the operator maps the [Reward Structure Architecture] and finds that the “development budget” is a monthly line item that gets cut when this-cycle cash pressure hits, the “positioning” spend is measured on this-quarter attribution, the “loyalty” mechanism is keyed to weekly metrics. The vocabulary is Relational; the cadence is Transactional; the installed reality is Transactional starvation of the Relational branch at nodes where the operator believed they were investing.

Where it applies. Every node in the architecture whose outcome designed is compounding. Product-side nodes where compounding capability, GX quality, and MDV build determine the Product’s compounding curve. People-side nodes where cast and kitchen manager capability compound across their tenure. Performance-side nodes where cast behavior aligned to design outcomes requires the design outcomes to be funded. Profit-side nodes where compounding bases (positioning capital, Guest re-encounter, cast capability, meaningfully differentiated value) get built rather than extracted from.

The stakes. An operator who does not know [Relational Reward] is a class with a specific signature and a specific default-suppression pattern cannot diagnose the underfunding of their own compounding-outcome nodes. They read the underfunding as prudent management or as external constraint (“we can’t afford it”) when the underfunding is the natural weighting bias running unchecked. Naming the class as a class gives the operator the diagnostic — at each compounding-outcome node, is the reward class Relational or is Relational absent, and if Relational is absent, is the absence intentional or the bias’s default output.

Load-Bearing Distinction #

Not inherently superior to [Transactional Reward]. [Relational Reward] and [Transactional Reward] are structural pair, not opposed values. Each is coherent at nodes whose outcomes match the class’s cadence. [Relational Reward] at single-cycle-outcome nodes is as incoherent as [Transactional Reward] at compounding-outcome nodes. The framework does not teach Relational as the right side and Transactional as the wrong side. The framework teaches coherence between reward cadence and outcome cadence at every node, and mix at the architecture level.

Not [Reward Structure Architecture]. [Relational Reward] is a branch inside the architecture, not the architecture itself. The architecture holds both branches. Operators who read [Relational Reward] as the whole reward layer are missing the [Transactional Reward] branch and the architecture-layer question of mix and node placement.

Not [Incentive Recursion]. [Incentive Recursion] is the physics of how any reward — Transactional or Relational — produces behavior through anticipated rewards read through the operator’s [Causal Read]. [Relational Reward] is one class of reward mechanism that the recursion runs on. When [Relational Reward] holds load-bearing positions in the architecture, [Incentive Recursion] runs on compounding nodes and produces the compounding cascade. The class and the physics are load-bearing to each other but they are not the same term.

Not Road 2 [Two Roads] itself. [Two Roads] is the parent principle at the operating-philosophy layer. [Relational Reward] is one specific manifestation of Road 2 at the reward-architecture layer. Naming [Relational Reward] as its own term keeps [Two Roads] as the parent principle and lets [Relational Reward] hold the reward-dimension-specific mechanism, cadence signature, and coherence conditions.

Not intent. A stated Relational intent is not a [Relational Reward] installation. Operators state Relational intent constantly — “we invest in our cast,” “we build for the long term,” “we care about Guest experience” — while running architectures that starve every Relational node the intent claims to fund. Intent lives in the operator’s language; [Relational Reward] lives in the installed cadence of the mechanism. The two are not the same, and the mismatch is the load-bearing failure mode this class surfaces.

Not “long-term thinking.” The class is not a general disposition toward the long term. It is a specific reward mechanism with a specific cadence signature at specific nodes in the architecture. Operators who read [Relational Reward] as long-term-mindset teaching miss that the class is a mechanical installation at specific nodes, diagnosable by cadence, not a personality trait.

The term is load-bearing because operators who cannot see [Relational Reward] as a class with a signature — payoff cadence longer than one cycle, low-certainty + low-immediacy [Causal Read] profile, chronic underfunding by the natural weighting bias — cannot diagnose their own architecture’s Relational starvation. Without the class named, every compounding-outcome node runs under a Transactional-vocabulary or an intent-only mechanism, and the operator’s actual reward layer contradicts their stated design intent. With the class named, the operator has a specific diagnostic — at each compounding-outcome node, is [Relational Reward] installed or is the node running on intent, on Transactional-in-disguise, or on no mechanism at all.

Diagnostic Tests #

Test One — The Cadence Test. For each reward mechanism at a compounding-outcome node, the operator names the payoff cadence — how long between the investment and the compounding outcome fully paying out. If the cadence runs longer than one operating cycle at that node, the mechanism is [Relational Reward]. If the cadence closes inside one cycle, the mechanism has slipped into [Transactional Reward] territory regardless of the vocabulary carried. Vocabulary does not decide. Cadence decides. A “development pathway” whose reward completes each month is Transactional; a pathway whose compounding capability build pays out across quarters and years is Relational.

Test Two — The Compounding-Outcome Node Test. The operator lists every node in the architecture whose outcome designed is compounding — cast development, kitchen manager development, Guest recovery, Guest re-encounter, positioning capital, meaningfully differentiated value, cast promotion pathway (treated as capability recognition), operator draw structure compounding components. For each node, the operator asks whether [Relational Reward] is actually installed or whether the node is running on intent, on Transactional-in-disguise, or on no mechanism at all. Every node whose compounding outcome is unaccompanied by an installed [Relational Reward] mechanism is Relational starvation at that node.

Test Three — The Cash-Pressure Test. The operator identifies the [Relational Reward] mechanisms in the current architecture and asks what happens to each mechanism when this-cycle cash pressure hits. If the mechanism gets defunded, deferred, or reduced when cash pressure arrives, the [Causal Read] discipline on that node is not defending the Relational anticipation against Transactional-cadence pressure. The mechanism is installed as a line item without disciplined causal work behind it, and the underfunding pattern will surface every cycle cash pressure appears — which is most cycles.

Test Four — The Compounding Profit Read. The operator reads Profit at their operation and asks whether current Profit is being produced through compounding or through extraction. If Profit runs slower per cycle but the compounding bases are building — positioning capital growing, Guest re-encounter compounding, cast capability accumulating, meaningfully differentiated value strengthening — [Relational Reward] holds load-bearing positions in the architecture. If Profit runs strong through cost squeeze, labor pressure, vendor terms tightening, or capital reserve depletion, [Relational Reward] is being starved somewhere and extraction is running instead. The Profit-production pattern is the aggregate diagnostic of the architecture’s Relational strength.

Test Five — The Intent-Cadence Split Test. The operator lists every Relational intent they hold — cast development, Guest experience investment, positioning capital build, meaningfully differentiated value, kitchen manager development, Guest recovery — and matches each intent to an installed reward mechanism at the corresponding node. Every intent without a matching installed [Relational Reward] mechanism is intent running without architecture support. The intent will not produce the outcome; the reward layer will. This test surfaces the specific failure mode where operators believe they are running a Relational architecture because their stated intent is Relational, when the installed reward layer is Transactional-dominant with Relational absent.

Family Position #

Constituent of [Two Roads] applied to the incentive dimension. One of the two branches held inside [Reward Structure Architecture]. Sits inside Perspective at the design-layer altitude, cross-Fundamental in application — [Relational Reward] runs across Product, People, Performance, and Profit reward nodes wherever the class is installed.

Perspective application. Perspective on [Relational Reward] determines whether the operator can read the class as a class rather than as scattered “long-term” line items. The operator whose Perspective treats Relational rewards as individual costs to justify cannot see the class’s cadence signature and cannot diagnose the underfunding pattern. The operator whose Perspective reads the reward layer as a system with two branches can see [Relational Reward] as one branch operating across many nodes with a shared signature — longer than single-cycle payoff, low-certainty + low-immediacy [Causal Read] profile, systematic suppression by the natural weighting bias. Perspective is the entry point for the class becoming legible.

Product application. The Product — the Guest Experience — is a compounding outcome. Cast development produces cast capability that produces GX quality. Guest recovery investment produces Guest re-encounter that raises frequency. Meaningfully differentiated value build produces defensible margin and pricing power. All Product-side compounding requires [Relational Reward] at the funding nodes. An operation whose Product-side nodes run pure [Transactional Reward] cannot produce a compounding Product because the compounding mechanism is not being funded. The Product degrades to whatever [Transactional Reward] can produce inside a single cycle — a functional GX floor, not a compounding GX ceiling.

People application. [Relational Reward] holds load-bearing positions at every People-side compounding node — cast development pathway, kitchen manager development and autonomy build, cast promotion pathway when treated as compounding capability recognition, cast recognition patterns that reinforce compounding capability rather than single-cycle performance. The People fundamental cannot be designed without [Relational Reward] at these nodes because the People fundamental’s design outcomes (capability, discipline, judgment, ownership) compound across tenure and cannot be produced by single-cycle rewards. Operations whose People-side reward layer is Relational-starved produce cast members who show up per shift and turnover proportional to any comp differential in the market.

Performance application. Performance runs on cast behavior aligned to design outcomes. When design outcomes are compounding (cast exercising judgment, cast investing in Guest recovery without waiting to be asked, cast developing kitchen managers below them), [Relational Reward] is the mechanism that funds the behavior. Performance failures at compounding-behavior nodes point to Relational starvation in the reward architecture at those nodes. The behavior cannot be produced by Transactional rewards because the behavior itself is compounding.

Profit application. [Relational Reward] holding load-bearing positions produces compounding Profit. Positioning capital compounds and shifts the operation off price competition. Meaningfully differentiated value compounds and produces defensible margin. Cast capability compounds and produces GX quality that supports pricing power. Guest re-encounter compounds and raises the frequency baseline. Compounding Profit reads slower per cycle than extraction Profit at extraction’s peak but compounds across cycles while extraction is depleting the finite bases it runs on. The Profit curve produced by Relational-load-bearing architecture is flatter early and steeper later; the operator has to hold the [Causal Read] discipline through the flat early period without defunding the Relational nodes when short-cycle numbers make Transactional alternatives look more attractive.

Cross-References To Locked IP #

Parent:

• [Reward Structure Architecture] — the design-layer parent; [Relational Reward] is one of the two branches held inside the architecture

• [Two Roads] — the family-level parent principle; [Relational Reward] is Road 2 running through the reward-architecture dimension

Related:

• [Transactional Reward] — the pair; the Road 1 branch of [Reward Structure Architecture], structurally opposite in cadence and coherence conditions

• [Incentive Recursion] — the physics that [Relational Reward] runs on; when [Relational Reward] holds load-bearing positions, [Incentive Recursion] runs on compounding nodes and produces the compounding cascade

• [Causal Read] — the read discipline required to install [Relational Reward] against the natural weighting bias; without [Causal Read] discipline, the bias suppresses the anticipations that would fund Relational mechanisms

• [The Summers Principle] — the governing principle; [Relational Reward] is either designed by disciplined [Causal Read] work or absent by weighting-bias default

• [Meaningfully Differentiated Value] — a compounding outcome that requires [Relational Reward] at the funding nodes to build

• [Positioning Capital] — a compounding asset that requires [Relational Reward] at the funding nodes to accumulate

• [Guest Recovery Investment] — a specific Relational node inside the architecture

• [Predicted LTV] — the Road 1 opposite frame; where [Predicted LTV] extracts across the anticipated arc of Guest engagement, [Relational Reward] funds the compounding arc that Guest engagement can produce

• [The Operator’s Own Audit] — the applied practice of running [Causal Read] discipline inward, which is where the operator surfaces Relational starvation at their own operation’s nodes

Opposing patterns:

• [The Affordability Lie] — the framing that [Relational Reward] alternatives cannot be afforded; the lie hides that [Transactional Reward] dominance is producing the margin pressure being cited as the reason [Relational Reward] cannot be funded

• [Transactional Arbitrage] — the extraction pattern that runs when [Relational Reward] has been starved and [Transactional Reward] dominates the architecture

• [Static Decline] — the operator condition where the architecture has drifted to Relational starvation and the operator has stopped reading whether the drift matches their design intent

• [Hacksterism] — the shortcut posture that treats Relational investments as costs to minimize rather than as compounding-base construction

Why This Matters #

Operators do not fail at long-term thinking because they lack the intent. They fail because they cannot see [Relational Reward] as a class with a signature — payoff cadence longer than one cycle, [Causal Read] profile at low certainty and low immediacy, chronic underfunding by the natural weighting bias. Without the class named, every compounding-outcome node in the architecture runs on intent alone, on Transactional-in-disguise, or on no installed mechanism at all. The operator states relational intent while running an architecture whose installed reward layer starves the relational nodes the intent claims to fund. The mismatch is invisible to the operator because both sides — the intent and the underfunding — feel like the same operation to them.

The natural weighting bias is the physics that makes the mismatch invisible. High-certainty + high-immediacy anticipations dominate the operator’s [Causal Read] without disciplined override. Every Relational node’s anticipation runs at low certainty and low immediacy, which the bias systematically suppresses. The suppression does not feel like suppression to the operator; it feels like prudent management, like “we cannot afford it,” like “let’s revisit that when we can,” like the visible pressure of the current cycle taking priority over the ambient anticipation of a compounding outcome. Naming [Relational Reward] as a class does not eliminate the bias — the bias is physics — but it gives the operator the diagnostic to see when the bias is running and to install disciplined [Causal Read] work as the override mechanism at nodes where Relational is load-bearing.

The industry teaches Relational vocabulary and Transactional cadence. “Development” programs paid monthly. “Loyalty” mechanisms keyed to weekly metrics. “Positioning” spend measured on this-quarter attribution. “Career pathway” attached to monthly performance reviews. The vocabulary suggests compounding; the cadence delivers Transactional. Operators who consume this teaching believe they are running Relational mechanisms because the vocabulary is Relational, while the installed reality is Transactional at every node the vocabulary claims to cover. Naming the class as diagnosed-by-cadence-not-vocabulary is the tool operators need to see through the industry’s disguised-Transactional teaching.

[Relational Reward] is load-bearing across the framework because it is the reward-layer mechanism through which Road 2 gets built at the incentive dimension, through which [Incentive Recursion] runs on compounding nodes, through which [Meaningfully Differentiated Value] and [Positioning Capital] and cast capability actually accumulate rather than remaining as stated intent. Without [Relational Reward] named as a class, every compounding outcome in the framework runs uninstalled at the reward layer, and the framework’s compounding physics cannot be produced in the operation because the reward architecture that would produce it has not been built. With the class named, the operator has a specific installation target — Relational mechanisms at compounding-outcome nodes, defended by disciplined [Causal Read] work against the natural weighting bias and against this-cycle cash pressure.

Operating Consequence #

Diagnose by cadence, not by vocabulary or intent. The operator classifies every reward mechanism at every compounding-outcome node by its payoff cadence. Any mechanism whose payoff closes inside one cycle is [Transactional Reward] regardless of the vocabulary carried or the intent stated. Every compounding-outcome node without a longer-than-one-cycle reward mechanism is Relational starvation at that node.

Refuse the intent-only architecture. The operator refuses to accept stated Relational intent as a Relational installation. “We invest in our cast” without a [Relational Reward] mechanism at the cast development node is intent without architecture. “We build for the long term” without [Relational Reward] components in the operator draw structure is intent without architecture. The operator holds themselves and the operation accountable to installed mechanism at cadence, not to intent stated in language.

Install [Causal Read] discipline as the override mechanism at every Relational node. [Relational Reward] mechanisms cannot be defended against the natural weighting bias or against this-cycle cash pressure without disciplined [Causal Read] work at each node. The operator explicitly builds the causal model from investment to compounding outcome, names the confidence at each dimension (certainty and immediacy), holds the anticipation through multiple cycles, and updates the model against partial observations. The discipline is the installation. Without it, the Relational mechanism is a line item that will get defunded.

Fund Relational at the operator layer first. The operator’s own reward layer sets the cascade. If the operator draw structure is pure this-cycle cash extraction, downstream Relational mechanisms cannot hold because the operator’s [Causal Read] on downstream Relational alternatives runs abstract — the operator has not seen compounding pay out in their own reward layer, so cannot trust it at cast, kitchen manager, or Guest layers. Fund Relational at the operator draw structure first — positioning capital build, meaningfully differentiated value investment time allocation, compounding investment reserves — before installing Relational mechanisms downstream.

Read cash pressure as the Relational-installation stress test. When this-cycle cash pressure hits, the operator watches which mechanisms get defunded first. Every Relational mechanism defunded under cash pressure is a mechanism that was installed as a line item without [Causal Read] discipline behind it. The pressure moment is the diagnostic — Relational installations defended by disciplined causal work hold; Relational installations installed on intent alone collapse.

Read compounding Profit as the aggregate diagnostic. When Profit runs slower per cycle but positioning capital is building, cast capability is accumulating, Guest re-encounter is compounding, meaningfully differentiated value is strengthening, the Relational architecture is holding load-bearing positions. When Profit runs faster per cycle through cost squeeze, labor pressure, and vendor terms tightening, Relational is being starved somewhere. The Profit-production pattern is the operator’s aggregate architecture diagnostic across cycles.

Refuse [The Affordability Lie] when it appears at Relational nodes. When the framing arrives that a Relational mechanism cannot be afforded, the operator recognizes the pattern — the Transactional-dominant architecture is producing the margin pressure being cited as the reason the Relational alternative cannot be funded. The affordability framing is not a neutral observation about current cash; it is the natural weighting bias speaking through the operator’s language. The operator asks instead what the architecture would look like if the compounding bases were being built rather than extracted from, and whether the current “cannot afford” state is the architecture’s default output rather than a genuine constraint.

Install [Relational Reward] symmetrically across compounding nodes. The operator does not install one flagship Relational program and leave the other compounding-outcome nodes starved. The class runs across every compounding node — cast development, kitchen manager development, Guest recovery, Guest re-encounter, positioning capital, meaningfully differentiated value, operator draw compounding components. Asymmetric installation leaves the architecture Relational at one visible node and Transactional-defaulted across the rest, which produces neither compounding Profit (too few nodes compounding) nor extraction Profit (the one Relational node is a cost drag) and reads as failure to the operator when the failure is asymmetric installation, not the class itself.

What Changes Tomorrow #

Tomorrow the operator takes their [Reward Structure Architecture] node map and runs the compounding-outcome node read. For every node whose outcome designed is compounding — cast development, kitchen manager development, Guest recovery, Guest re-encounter, positioning capital, meaningfully differentiated value, cast promotion pathway if treated as capability recognition, operator draw compounding components — the operator names what [Relational Reward] mechanism is currently installed. Not intent. Not vocabulary. Installed mechanism, diagnosed by cadence.

For nodes where a Relational mechanism is installed, the operator runs the cash-pressure test. What happens to this mechanism when this-cycle cash pressure hits? If the mechanism gets defunded, the [Causal Read] discipline behind it is not defending the anticipation, and the mechanism will collapse the next cycle pressure arrives. Those mechanisms get [Causal Read] discipline installed as the defense — the causal model built explicitly, the confidence named at both dimensions, the anticipation held across cycles.

For nodes where no Relational mechanism is installed, the operator names the Relational starvation and picks the three highest-impact starved nodes as the design work for the coming period. Each starved node gets a [Relational Reward] mechanism installed with cadence matching the compounding outcome, and disciplined [Causal Read] work sitting behind it as the defense.

For the operator’s own reward layer, the operator asks whether their own draw structure holds any Relational components at all. If the answer is no, the operator installs the first Relational component in their own layer before installing anything downstream — because the operator’s own layer sets the ceiling and the operator’s own [Causal Read] on Relational alternatives needs to be lived rather than abstract for the downstream installations to hold.

The frame the operator now runs is that [Relational Reward] is a class installed by cadence-matching at compounding-outcome nodes, defended by disciplined [Causal Read] work against the natural weighting bias and against this-cycle cash pressure. Intent does not install. Vocabulary does not install. Cadence-matching mechanism at compounding-outcome nodes, defended by causal discipline, is the installation. Every compounding outcome the operator designs for either has this installation or it does not; where the installation is absent, the outcome will not produce, regardless of what the operator intends.