A strategy that is optimal for one payoff matrix can perform badly when the matrix changes. If a player must choose before learning which of several payoff scenarios applies, solving each scenario separately does not produce one usable guarantee. The right reader question is: which single mixed strategy protects the best worst-case payoff across every declared scenario and opposing response?
This article answers that question with original two-by-two examples. It extends the Zero-Sum Games subject guide beyond its fixed-matrix minimax calculation. The scenarios here are stipulated teaching models, not estimates of real people or instructions for conflict. The route remains connected to Learning That Transfers into Life and the How X Works hub.
eduKateSG · Zero-Sum Games
Find your next learning step
Keep one mixed strategy fixed while every declared payoff scenario and opposing action is tested.
ROUTE 2 · CHAPTERS 6–10
Solve each scenario
Build payoff lines and expose incompatible individual optima.
ROUTE 3 · CHAPTERS 11–15
Find one surviving strategy
Take the lower envelope and verify every constraint.
ROUTE 4 · CHAPTERS 16–20
Compare interpretations
Distinguish worst-case, weighted and changed-context solutions.
Chapter contents
Define the robust game · Chapters 1–5
1. State the timing before solving the game
2. 1. Write the two original payoff scenarios
3. 2. Solve Scenario A by itself
Solve each scenario · Chapters 6–10
6. 5. Test the Scenario B optimum in Scenario A
7. 6. Expand the uncertainty into four constraints
8. 7. Solve the robust intersection
Find one surviving strategy · Chapters 11–15
11. 10. Distinguish robust value from expected value
12. 11. Preserve the source of scenario probabilities
13. 12. State when an adaptive policy is allowed
Compare interpretations · Chapters 16–20
16. 15. Formulate the linear programme
17. 16. Understand what the dual side represents
18. 17. Bound performance when p is implemented imprecisely
Audit and continue · Chapters 21–25
21. 20. Test three common misconceptions
22. 21. Build an evidence table another reader can audit
23. 22. Frequently asked questions
24. 23. Connected reading routes
25. 24. Final transfer: report the guarantee and its boundary
CHAPTER 1 OF 25 · Define the robust game
1. State the timing before solving the game
The row player chooses one distribution before the scenario is known. The column player is allowed to select a response after the row distribution is declared, and the guarantee is evaluated across both declared payoff scenarios. The realised row action remains concealed until choices are complete.
This timing creates a robust security problem. It differs from a policy that may choose one distribution in Scenario A and another in Scenario B after the scenario is observed. It also differs from an expected-payoff problem that assigns probabilities to scenarios.
The short answer is to treat every scenario–column pair as a separate constraint on the row player’s protected payoff. Then maximise the smallest of those expected payoffs. A scenario-specific optimum is evidence about one matrix, not automatically a feasible robust solution.
The gateway check
Ask when the scenario becomes known, whether scenario probabilities are supplied, who controls the uncertainty, and whether the same mixed strategy must be used throughout. Those decisions define the optimisation problem before any matrix arithmetic begins.
Draw a timeline with four labels: scenario information, distribution choice, realised action and opposing response. A change in any ordering creates a different game. This diagram prevents a later paragraph from quietly granting information that the calculation denied, or concealing information that the stated application would reveal.
CHAPTER 2 OF 25 · Define the robust game
2. 1. Write the two original payoff scenarios
Scenario A gives the row player the matrix with Upper–Left payoff 4, Upper–Right 0, Lower–Left 1 and Lower–Right 3. The column player seeks to reduce the displayed row payoff.
Scenario B uses Upper–Left 2, Upper–Right 1, Lower–Left 0 and Lower–Right 4. The action labels are shared across scenarios, but the payoffs change. One row distribution must be chosen before the scenario is revealed.
Let p be the probability of Upper, so Lower has probability 1−p. The allowed interval is 0 ≤ p ≤ 1. The robust value attached to p is the smallest expected row payoff across both columns in both scenarios.
These matrices are fictional and dimensionless. Their purpose is to show how correlated payoff scenarios become constraints. They do not claim that uncertainty in a real decision can always be represented by two matrices.
The matrix entries should use one orientation throughout. If a source lists column-player losses while the worksheet treats entries as row-player gains, every inequality direction can be reversed. Copy the meaning of one representative cell into words before manipulating the matrix, and check that zero-sum opposition matches the stated sign convention.
Against Left in Scenario A, expected payoff is 4p + 1(1−p) = 1 + 3p. Against Right, it is 0p + 3(1−p) = 3 − 3p.
The row player protects the smaller expression. Their intersection solves 1 + 3p = 3 − 3p, giving p = 1/3 and value 2. At that mixture, each pure column gives expected payoff 2.
This is the fixed-matrix calculation already developed by the root. The result is correct when Scenario A is the game. It is not yet a robust result because Scenario B has not constrained p.
Check the endpoints: p = 0 protects min(1,3)=1; p = 1 protects min(4,0)=0. The intersection improves the lower envelope to 2.
The Scenario A optimum is unique in this two-line calculation because the lower envelope rises before the intersection and falls after it. In a larger matrix, several distributions may achieve the same value. Report the value separately from the set of optimal strategies so uniqueness is not assumed merely because one solver returns one vector.
Against Left in Scenario B, expected payoff is 2p. Against Right, it is p + 4(1−p) = 4 − 3p.
Equalising the two expressions gives 2p = 4 − 3p, so p = 4/5 and the protected value is 8/5, or 1.6. Each pure column gives 1.6 at this scenario-specific mixture.
The Scenario B optimum puts much more weight on Upper than Scenario A’s optimum. The two recommendations cannot both be followed when one distribution must be chosen before the scenario is known.
This is the first ownership test for the new reader job. The root explains minimax for one matrix; the child question begins when several valid matrices demand incompatible mixtures.
Scenario B also shows why a visually balanced fifty-fifty mixture need not be strategically balanced. At p=0.5, the Left and Right expectations are1 and2.5, so the protected value is1. Balancing the binding responses requires p=0.8. The relevant symmetry comes from payoff lines, not equal action frequencies.
CHAPTER 5 OF 25 · Define the robust game
5. 4. Test the Scenario A optimum in Scenario B
Use p = 1/3 in Scenario B. Against Left, the expected payoff is 2/3. Against Right, it is 4 − 1 = 3. The protected Scenario B payoff is therefore 2/3.
Across all scenario–column pairs, the Scenario A optimum protects only 2/3. Its value of 2 applied to Scenario A, not to the changed payoff system.
This check prevents a common error: solving a preferred or nominal matrix and then reporting its value as if it survived uncertainty. A robust claim must be tested in every declared scenario.
The poor response is identifiable. Scenario B–Left becomes the active constraint. The useful question is how p can move to strengthen that constraint without damaging another scenario too far.
A scenario-specific result should carry its matrix identifier into every later table. Writing only p=1/3 can become ambiguous once several games appear. Use labels such as pA and pB for analysis, then distinguish them from the single robust p that must remain common across scenarios.
CHAPTER 6 OF 25 · Solve each scenario
6. 5. Test the Scenario B optimum in Scenario A
Use p = 4/5 in Scenario A. Against Left, expected payoff is 1 + 12/5 = 17/5, or 3.4. Against Right, it is 3 − 12/5 = 3/5, or 0.6.
The protected Scenario A payoff is 0.6. Thus the strategy optimal for Scenario B performs even worse under Scenario A’s Right response than the Scenario A strategy performed under Scenario B’s Left response.
Neither scenario-specific optimum dominates the other across the full uncertainty set. Choosing between them by their individual values would ignore the scenario in which each is fragile.
The robust solution must therefore consider all four response lines at once rather than select one of the two completed fixed-matrix solutions.
Cross-testing should be automatic. Each candidate strategy is evaluated in the matrix that produced it and every alternative scenario. This small discipline scales: a model-selection workflow should include out-of-model stress cases rather than display only the conditions under which the candidate was optimised.
CHAPTER 7 OF 25 · Solve each scenario
7. 6. Expand the uncertainty into four constraints
For a chosen p, the four expected payoffs are A–Left: 1+3p; A–Right: 3−3p; B–Left: 2p; and B–Right: 4−3p.
The protected payoff is g(p)=min(1+3p, 3−3p, 2p, 4−3p). Maximising g(p) gives the best single guarantee under the declared robust timing.
Two constraints are never the smallest on the allowed interval. Since 2p ≤ 1+3p for every p≥0, B–Left is no larger than A–Left. Since 3−3p ≤ 4−3p, A–Right is no larger than B–Right.
The lower envelope therefore reduces to min(2p, 3−3p). Removing a constraint here is justified by an inequality that holds over the whole feasible interval, not by looking only at one candidate p.
Keep all four expressions until dominance has been proved. Deleting apparently generous constraints too early can miss an interval where they become limiting. The inequalities used here are simple because one line exceeds another by a positive constant or by1+p across the entire feasible set.
Set the remaining active candidates equal: 2p = 3 − 3p. This gives 5p = 3, so p = 3/5. The robust value is 2p = 6/5, or 1.2.
Check all four constraints at p = 0.6. A–Left gives 2.8, A–Right 1.2, B–Left 1.2 and B–Right 2.2. The minimum is 1.2, reached by two different scenario–response pairs.
The solution deliberately sacrifices the higher scenario-specific values of 2 and 1.6. In return, it improves the full-set guarantee from 2/3 or 0.6 to 1.2.
This trade-off is the meaning of robustness in the stated problem. It is not proof that p = 0.6 is best for every criterion or every uncertainty model.
The equality of two active constraints is a candidate-generation step, not a universal theorem that every optimum equalises exactly two responses. An endpoint can be optimal, several constraints can bind, or a flat segment can contain multiple optima. Verification of the full feasible set remains necessary.
The robust row problem can be written as one matrix with two rows and four columns. The columns are A–Left, A–Right, B–Left and B–Right. Upper has payoffs 4,0,2,1; Lower has 1,3,0,4.
The column side of this enlarged security model chooses whichever scenario–response pair is most damaging. Solving the row maximin of the enlarged matrix reproduces the four-constraint calculation.
This representation is useful when the uncertainty set contains a finite list of complete scenarios. It preserves correlations within each scenario rather than mixing entries that cannot occur together.
The specialist paper Robust Game Theory develops a broader robust-optimisation view and warns that payoff uncertainty can change game structure. The small enlarged matrix here is an original teaching construction.
The enlarged matrix separates modelling from computation. Modelling decides which scenario–response combinations are allowed; computation finds the lower envelope. If the enlarged columns are wrong, an exact linear-program solution is exactly wrong for the intended decision. Preserve the mapping between each column and its real meaning.
CHAPTER 10 OF 25 · Solve each scenario
10. 9. Do not create an impossible entrywise matrix
Scenario A and Scenario B are complete packages. The worst entry in each cell across scenarios would produce the matrix [[2,0],[0,3]]. That entrywise combination is not one of the declared scenarios.
Solving the entrywise matrix may be appropriate only if the uncertainty set truly allows every cell to vary independently within the stated bounds. If the entries move together through a shared scenario, the rectangular set adds payoff combinations that were never allowed.
A robust analysis can be conservative by design, but the source of conservatism should be explicit. Enlarging the uncertainty set can lower the guarantee because it gives the adverse side more possible combinations.
Record whether uncertainty is scenario-coupled, entrywise independent, probabilistic or otherwise structured. The same numerical endpoints can support different robust problems.
Entrywise uncertainty can be appropriate when measurement errors genuinely vary independently. Scenario-coupled uncertainty can be appropriate when one physical condition moves several payoffs together. Neither form should be chosen because it produces a preferred value. The uncertainty set is an evidence claim and deserves its own justification.
CHAPTER 11 OF 25 · Find one surviving strategy
11. 10. Distinguish robust value from expected value
Suppose Scenario A has probability 3/4 and Scenario B probability 1/4, and the row player seeks expected payoff against the column after averaging the matrices. This is a different objective from guarding against the worst scenario.
The probability-weighted matrix is [[3.5,0.25],[0.75,3.25]]. Against Left, expectation is 0.75+2.75p. Against Right, it is 3.25−3p.
Equalising gives p = 10/23, approximately 0.4348. The expected-matrix value is 179/92, approximately 1.9457. Yet its robust payoff against B–Left is only 20/23, approximately 0.8696.
Neither answer is a correction of the other. The expected model uses trusted scenario probabilities; the robust model asks for a guarantee without averaging away the adverse scenario.
The expected-matrix calculation also assumes linear averaging of payoffs is meaningful. If outcomes have nonlinear utility, thresholds or catastrophic constraints, averaging raw scores can answer the wrong decision question. The article retains linear dimensionless payoffs so the contrast between expectation and protection remains transparent.
CHAPTER 12 OF 25 · Find one surviving strategy
12. 11. Preserve the source of scenario probabilities
A probability-weighted solution is only as meaningful as the probability model. Frequencies from past observations, subjective beliefs and a deliberately adversarial test suite have different interpretations.
Do not infer scenario probabilities merely because two scenarios were listed. Equal listing does not imply equal chance. If probabilities are absent, report a robust result, a range or separate scenario results according to the decision question.
If probabilities are estimated, preserve uncertainty and possible change. A precise expected value from weak probabilities can be less useful than a transparent sensitivity analysis.
The Probability root provides the wider route. Here the critical move is to keep scenario weighting separate from worst-case protection.
A sensitivity table can vary the Scenario A probability from zero to one and solve the corresponding expected matrix. The robust mixture need not appear at any particular probability. This demonstrates that robust optimisation is not secretly an average with an unknown but conveniently chosen weight.
CHAPTER 13 OF 25 · Find one surviving strategy
13. 12. State when an adaptive policy is allowed
If the scenario becomes known before the row distribution is chosen, a contingent policy can use pA = 1/3 in Scenario A and pB = 4/5 in Scenario B. The policy is a pair of rules, not one fixed mixture.
Its scenario values are 2 and 1.6. Comparing these with the robust value 1.2 would be unfair unless the information timing is also compared. Adaptation uses information that the robust fixed strategy was denied.
If a noisy signal about the scenario arrives first, the problem becomes richer. A policy can condition on the signal, and its performance depends on signal reliability. The current article does not invent such a signal.
Write the information available at each decision point. Strategy quality cannot be separated from the information rules under which the strategy operates.
Adaptive policies require enforceable observation. If the scenario label is delayed, noisy or disputable, the policy may choose the wrong branch. State what evidence triggers each branch and what happens when the evidence is missing. Otherwise the apparent value of adaptation relies on perfect information that the application cannot supply.
CHAPTER 14 OF 25 · Find one surviving strategy
14. 13. Keep realised actions concealed
The mixed strategy protects an expected payoff when the opposing response cannot condition on the realised row action before choosing. Publishing p = 0.6 is not the same as revealing whether Upper or Lower was drawn on a particular round.
If the actual action is visible first, the column can select the least favourable response for that row and scenario. The information structure changes, and the mixed-strategy guarantee need not survive.
A deterministic schedule with 60% Upper can also be exploitable if its next action is predictable. Long-run proportions alone do not reproduce concealed randomisation.
The root article develops this distinction for one matrix. The same rule remains essential when scenario uncertainty is added.
Randomisation also needs a source independent of the adversary under the model. A predictable pseudo-random sequence known to the responder can behave like a schedule. The mathematical distribution describes uncertainty from the responder’s perspective at decision time, not merely the long-run histogram printed after play.
CHAPTER 15 OF 25 · Find one surviving strategy
15. 14. Check the guarantee at nearby mixtures
At p = 0.5, the four payoffs are 2.5,1.5,1 and2.5, so the robust minimum is1. At p =0.6, the minimum is1.2. At p =0.7, the values are3.1,0.9,1.4 and1.9, so the minimum falls to0.9.
The active constraint switches near the intersection. Below0.6, B–Left=2p limits the guarantee. Above0.6, A–Right=3−3p limits it.
This nearby-point check confirms that the intersection is a maximum of the lower envelope rather than merely a crossing. It also shows which scenario punishes movement in each direction.
A plot can make this visible, but the equations and tabulated points should remain available so the conclusion does not depend on visual resolution.
The nearby mixtures give a local sensitivity slope. Moving p one hundredth below0.6 reduces the B–Left constraint by0.02; moving one hundredth above0.6 reduces A–Right by0.03. The asymmetric slopes explain why an equal implementation interval produces a slightly worse upper-side endpoint.
Introduce a variable v for the protected payoff. Maximise v subject to v≤1+3p, v≤3−3p, v≤2p, v≤4−3p and0≤p≤1.
This is a linear programme because every constraint is linear in p and v. The robust solution p=3/5, v=6/5 satisfies all constraints and has the two active equalities already identified.
For larger games, use one probability per row, require probabilities to be nonnegative and sum to one, and add a payoff constraint for every declared scenario–column pair.
The Operations Research root supplies the wider optimisation route. A solver output still needs checks for normalisation, orientation, active constraints and scenario definition.
A linear-program implementation should retain every original constraint even if preprocessing identifies redundancy. Solver logs or a separate verification pass can confirm the returned distribution against the uncompressed set. This prevents an error in screening from disappearing behind a successful optimisation status.
CHAPTER 17 OF 25 · Compare interpretations
17. 16. Understand what the dual side represents
In the enlarged matrix, the minimising side can mix over scenario–column pairs. That mathematical mixture supports the dual bound in the robust security model.
It should not automatically be interpreted as a literal probability distribution over real scenarios. Dual weights can identify binding constraints and support the value without describing how nature generates events.
This distinction matters because the physical uncertainty may be exogenous rather than controlled by a strategic opponent. The robust optimisation uses adversarial selection as a protection device.
The conclusion should therefore say “guaranteed across the declared scenario set” rather than claiming to have discovered the true scenario frequency.
Dual interpretation is especially easy to overstate. A positive dual weight can show that a constraint supports the optimum, but it does not prove the corresponding scenario is frequent, likely or causally important. Use dual values to understand the optimisation, then return to domain evidence for physical interpretation.
CHAPTER 18 OF 25 · Compare interpretations
18. 17. Bound performance when p is implemented imprecisely
Suppose the intended p=0.6 can be implemented only within ±0.02. For p in [0.58,0.60], B–Left=2p is the active lower line, giving a minimum at p=0.58 of1.16.
For p in [0.60,0.62], A–Right=3−3p is active, giving a minimum at p=0.62 of1.14. Across the full implementation interval, the guaranteed payoff is at least1.14.
This sensitivity result is lower than1.2 but still stronger than the guarantees of the two scenario-specific optima under the opposite scenario. It translates numerical precision into decision impact.
Do not report p to many decimals without considering whether the procedure can realise that precision. A robust strategy can also be evaluated for robustness to its own implementation error.
If p is implemented by a finite sequence, exact60% frequency may be impossible for some horizons. A five-round block can contain three Upper actions, but its order must also preserve concealment. For a short one-off decision, the selected action remains random and the guarantee is expected rather than a deterministic score.
CHAPTER 19 OF 25 · Compare interpretations
19. 18. Add a dominated scenario carefully
Suppose a third scenario produces expected payoff lines that are everywhere above existing constraints for every p. It cannot reduce the robust lower envelope and therefore does not change the solution.
To remove it from computation, prove the dominance over the whole feasible set. A comparison at p=0.6 alone is insufficient because a line that is inactive there could become active elsewhere.
Scenario screening can simplify a large problem while preserving the guarantee. Keep a record of the inequality or optimisation used to establish redundancy.
Conversely, adding one new scenario can change the solution sharply if it cuts below the current lower envelope. Re-run the full constraint check after the uncertainty set changes.
Redundancy can be checked by maximising the difference between a candidate new constraint and the current lower envelope, or by direct inequalities in a small case. The proof method should match complexity. Never discard a scenario solely because its payoff is high at the existing optimum; model updates can move the optimum elsewhere.
Scenario C is [[3,0],[1,2]], giving lines 1+2p and2−2p. Scenario D is [[2,1],[0,3]], giving lines2p and3−2p.
Across all four constraints, 2p is no larger than1+2p, and2−2p is no larger than3−2p. The robust envelope reduces to min(2p,2−2p).
Equalising gives p=1/2 and robust value1. Check all four: C–Left2, C–Right1, D–Left1 and D–Right2. The result is balanced by C–Right and D–Left.
This transfer uses new matrices and a new optimum while preserving the same reasoning sequence: derive, screen globally, equalise active constraints and verify every original constraint.
The changed-context transfer should be solved before consulting the original answer. If the learner simply substitutes new numbers into the old p=0.6 result, the method has not transferred. Re-deriving the four lines and screening relations reveals the new symmetry and p=0.5 optimum.
Misconception one: choose the scenario with the smallest individual value. Scenario B’s individual value1.6 is smaller than Scenario A’s2, but playing its optimum p=0.8 protects only0.6 in Scenario A.
Misconception two: average matrices when no probabilities are supplied. Averaging inserts a scenario model that was not part of the problem.
Misconception three: take the worst entry in every cell. That changes a coupled scenario set into independent cell uncertainty and can invent an impossible matrix.
Each misconception answers a different problem. The remedy is to write the timing, uncertainty set and objective before computing.
Another misconception is that robustness predicts what will happen. It does not. It establishes a lower bound within the declared model. Realised payoffs can be higher, and events outside the uncertainty set can be lower. A guarantee is conditional on model coverage and information rules.
CHAPTER 22 OF 25 · Audit and continue
22. 21. Build an evidence table another reader can audit
Use one row per candidate p and columns for all scenario–response expected payoffs, followed by their minimum. Include scenario-specific optima, the robust optimum and nearby values.
Keep exact fractions where useful: p=1/3,4/5 and3/5. Decimal displays support comparison, but exact values expose equality checks and prevent small rounding differences from selecting the wrong active constraint.
Label payoffs as row-player values and state that the column side minimises them. A reversed orientation can produce a mathematically consistent solution to the wrong game.
Preserve the source and version of every scenario matrix. If one entry is revised, create a new table and compare the change rather than overwriting the evidence chain.
The table should include the identity of the minimum in each row. Two candidates with similar numerical minima can be vulnerable to different scenarios. That information guides monitoring, model refinement and explanation even when the final strategy stays unchanged.
Is the robust strategy an equilibrium of every scenario? No. It is one fixed strategy maximising a joint worst-case guarantee. Each scenario may have a different equilibrium strategy.
Is worst-case analysis always best? No. It matches decisions that require protection across a justified uncertainty set. Expected value, regret or adaptive policies answer different questions.
Can the column player choose the scenario in reality? Not necessarily. Adversarial selection is a mathematical device for the guarantee. Interpret it according to the application.
Why not use the most likely scenario? Because likelihood and consequence are different inputs. A most-likely policy can be reported, but its performance in other declared scenarios must remain visible when robustness matters.
A robust strategy can be evaluated with regret as a separate metric: compare its payoff in each scenario with the value achievable if that scenario had been known. Regret and security value need not rank strategies identically. Do not switch objectives mid-analysis without naming the change.
Return to Zero-Sum Games for fixed-matrix minimax, mixed strategies, linear programming and information rules. Use Game Theory for broader strategic models.
Use Probability when scenario weights are evidence-based, Statistics when payoffs or frequencies are estimated, and Decision Theory when objectives and risk attitudes need explicit treatment.
The MIT-hosted primary paper Robust Game Theory supplies specialist context for games with payoff uncertainty. The matrices and calculations in this article are original teaching examples.
The transferable habit is to preserve timing, uncertainty structure and objective. Those three choices determine which optimisation deserves to be called correct.
Readers moving into applications should also ask whether the interaction is truly zero-sum. Payoff uncertainty can expose costs or benefits not captured by opposite scores. If both sides can gain or lose together, a zero-sum matrix may be an analytical slice rather than the full decision model.
CHAPTER 25 OF 25 · Audit and continue
25. 24. Final transfer: report the guarantee and its boundary
A complete result can be concise: “With one distribution chosen before the scenario and evaluated against both columns in both declared matrices, p=3/5 on Upper maximises the worst expected payoff. The four expectations are2.8,1.2,1.2 and2.2, so the protected value is1.2.”
Add the comparison: “The Scenario A and B optima are p=1/3 and p=4/5, but their cross-scenario guarantees are2/3 and0.6. They do not solve the one-strategy robust problem.”
Add the boundary: “If scenario probabilities or advance scenario information are available, an expected or adaptive policy may be appropriate and can produce a different answer.”
That is the gold standard: one explicit strategy, every declared constraint checked, and no claim that the robust answer solves a different information problem.
The final result should preserve the uncertainty-set version. Adding Scenario C tomorrow creates a new optimisation problem even if the two old matrices are unchanged. Versioned scenario sets let reviewers reproduce the guarantee that was available when the decision was made.
A further audit can compare the security value with every pure row. Always Upper protects the minimum of 4,0,2 and1, which is0. Always Lower protects the minimum of1,3,0 and4, also0. The robust mixture raises the guarantee to1.2. This confirms that randomisation has a concrete job in the enlarged game rather than serving as decorative complexity.
The four-column account also shows why each scenario contributes selectively. Scenario A supplies the binding Right response, while Scenario B supplies the binding Left response. Their other columns remain slack at the optimum. Removing either complete scenario would change the available guarantee, even though only one column from each is active.
If payoffs are measured with intervals, run a second layer of sensitivity. A small change to an active entry can move the value or mixture more than the same change to a slack entry. Report which entries support the optimum, but do not assume slack entries are permanently irrelevant; a larger revision can make them active.
A decision record should distinguish mathematical feasibility from operational feasibility. The distribution p=0.6 is a valid probability vector. An application may still face limits on randomisation, repeated implementation or auditability. Those limits belong in the model as constraints rather than being discovered after publication.
The robust conclusion should not be marketed as certainty. It is a conditional promise: if one of the declared matrices applies, the payoff orientation is correct, the opposing response follows the model, and the realised action remains concealed, then the expected lower bound holds. Listing these conditions makes the promise testable.
Finally, a learner can reverse the task. Given a proposed p and target value v, check every scenario–column inequality directly. This verification problem is often easier than finding the optimum and is useful when reviewing a solver result, a published strategy or a hand calculation from another person.
One final counterfactual clarifies the timing. If Scenario A is announced before the row chooses, using p=1/3 is rational for that branch; if Scenario B is announced, p=4/5 is rational. The lower robust value is the price of committing before that announcement, not evidence that the fixed strategy is badly calculated.
When presenting the result, place the two scenario matrices, the four constraint formulas and the final check close together. A reader should not need to search across sections to reconstruct the guarantee. Good layout supports good reasoning because it keeps every possible adverse response visible at the moment the conclusion is assessed.
This final reconstruction check makes the article usable as a model review, a classroom proof and a transparent decision record.
It also keeps future revisions anchored to the exact evidence and assumptions that produced the published guarantee.