# Postgame Audit: Mexico vs England Status: settled Prediction lock local: `2026-07-05 10:02 AM EDT` Kickoff ET: `2026-07-05 8:00 PM ET` Lock scope: `Pregame lock: generated before scheduled kickoff from pre-cutoff ledgers.` Official source used for settlement: Guardian live report, Mexico 2-3 England. ## Locked Card - SCORE 1: `1-1` - SCORE 2: `0-1` - SCORE 3: `0-2` - SCORE 4: `2-2` Score convention: first score is Mexico, second score is England. ## Settlement - Final score: `2-3` - Four-score card result: `MISS` - Four-score result: `MISS` - Closest locked state: `2-2` was one England goal short and was broken by the late winner. - Support settlement: - `Over 1.5 YES`: correct. - `Over 2.5 NO`: incorrect. - `Over 3.5 NO`: incorrect. - `BTTS YES`: correct, though it was only optional at a discounted price. ## Timeline - England 1-0: Foden, 14'. - England 2-0: Bellingham, 18'. - Mexico 1-2: Jimenez, 26'. - England red card: Quansah, 44'. - England 3-1: Kane penalty, 79'. - Mexico 2-3: Jimenez, 84'. - Full time: Mexico 2-3 England. ## What Turtle Got Right England as the stronger side was not a bad branch. The locked card contained two England-win scores, `0-1` and `0-2`, and the pregame model correctly resisted a Mexico-favorite interpretation even with venue pressure and Mexico tournament form. The draw/high-total warning also existed. The score 4 `2-2` was not random; it was the fourth C4 score branch and it became live after the red card and Mexico's second goal. The problem is that Turtle underweighted it in support-market logic rather than allowing it to discipline support-market logic. The high floor for goals was visible. The model gave `Over 1.5` a strong fair probability and the match crossed that line by the 26th minute. ## What Failed The official score cloud was too low-total and too clean. `1-1`, `0-1`, and `0-2` described a controlled knockout match. The actual game became an open five-goal state with both sides scoring multiple goals. The support-market layer contradicted part of the four-score card. `Under 3.5` can support most of the card, but it cannot honestly be called full-card support when C4 contains `2-2`. A support market that opposes a C4 score is partial-card support and must be labelled as such. The star and game-state volatility layer was too small. England's elite rescue profile, especially Bellingham/Kane/Foden, made the `3` in England's column more reachable than the count model admitted. Mexico's venue and transition pressure made the `2` in Mexico's column more reachable than the clean-sheet thread admitted. The red-card state exposed a missing live-analysis rule. The pregame card cannot be rewritten after Quansah's red card, but the postgame audit can say that a 10-man favorite with elite finishers creates a wider, not narrower, high-chaos tail: `2-2`, `2-3`, and `3-2` must be re-evaluated in a live-state file. ## Rule Correction R-SUPPORT-four-score: If any C4 score has four or more total goals, no `Under 3.5` support note may be described as protecting the full card. It may be labelled only as `partial-card low-total support`. A public support market is allowed to oppose part of C4 only if the page says that explicitly. R-STAR-RESCUE: If a favorite has at least two elite late-game scorers or creators and the underdog has a live venue/transition path, the model must compute a bounded rescue-volatility modifier before finalizing `0-1`/`0-2` as the only favorite-win branches. This modifier does not create a score by prose; it changes the `score-family` and `total` threads before exact-score selection. R-LIVE-RED-CARD: After a red card before minute 60, a live-state audit must rebuild totals and BTTS branches rather than carrying the pregame totals support forward. This rule is for live analysis only and does not rewrite the locked pregame card. ## Carry Forward Mexico-England is a real Turtle loss: - Four-score accuracy: miss. - Four-score accuracy: miss. - Support layer: split, with the score low-total support wrong. The usable lesson is not "avoid England control." The lesson is: when C4 contains `2-2`, the support layer must respect that score, and when elite players plus red-card volatility enter the game, Turtle needs a named high-chaos family rather than pretending every favorite game resolves as `1-0`, `2-0`, or `1-1`.