I think we might need some elaboration here. If the WS is enabled (chosen), it shouldn’t be violating it.

Today, enabling a WS overrides the user’s plan, so (as you note) by definition it can’t be violated. I’m proposing an alternative way to apply the WS – call it “watch mode” – where the WS is used as a benchmark, not a controller.

How watch mode would work:

• Run Monte Carlo unchanged (use the user’s configured expenses/cash flows; no WS overrides).
• After each trial, compute the WS allowance per year (per the chosen WS formula) and compare to the trial’s actual simulated expenses.
• If any year’s expenses exceed the WS limit, mark that trial as a WS breach.
• Report a new Outcome Category (Kind of Failure): Exceeded Withdrawal Strategy = % of trials that breached the WS.

Two alternative approaches for surfacing this option:

1. Add a toggle in the WS panel: Override (current behavior) vs Watch (new). This would apply in both MC (as described above) and the main plan view, by adding icons to any year where the plan is breached.
2. Alternatively, add a Monte Carlo-specific setting for Override vs. Watch behavior. This would only affect MC, leaving the main plan UI unchanged.

One might note that this is strict/brittle, with one over-cap year resulting in failure. That’s deliberate and pairs naturally with the existing request for Flex % expenses in MC: in Watch mode, flexing would trigger precisely when a breach is imminent, reducing discretionary spend to stay within the WS cap.