Match Ops

Turn the truth into a plan. Never let the match rewrite it.

It turns governed truth into a prematch plan, a disciplined live layer, and a postmatch audit, never rewriting the rating.

Case 01 · the plan is built from the opponent's own gaps

Attack, deny, stress, fragility. From their structure, not our opinion.

The prematch report does not editorialise. It reads the opponent's Missing Demands and Fragility Flags straight from the Team Intelligence diagnostics and turns them into a leverage plan: where to attack, what to deny, where to apply stress, and what breaks if a key man is booked or withdrawn.

Attack
Their centre-backs have no recovery pace, so play in behind the high line. The space between the lines opens once the first press is broken.
from their defensive Missing Demands
Deny
Their creation runs through one number 10. Screen him and the secondary creator does not exist, so cut the supply line to the front three.
from their primary initiators
Stress
Press their build-out and force the non-progressive centre-back onto his weak foot. Target the near-post marking weakness at corners.
from their pressure points
Fragility
If their holding midfielder is booked and plays cautious, their press has no screen and the whole first phase is exposed for the rest of the match.
from their Fragility Flags

Every line traces to a specific diagnostic: an uncovered demand, a single-point-of-failure flag, a primary initiator. The plan does not say attack the left on a feeling; it says attack the left because their left centre-back is the uncovered pace demand. Name the structural gap, then build the plan on it. A game plan is the opponent's own weaknesses, read back to you as instructions.

Illustrative engine read on the real Prematch Opposition Report leverage plan (Attack, Deny, Stress, Fragility drawn from the opponent's Missing Demands, primary initiators, pressure points, and Fragility Flags). Composite opponent, demonstration figures.

Case 02 · the live layer is signal, not a firehose

A manager glances and decides, not a dashboard.

In-match, the temptation is to drown the bench in data. Match Ops does the opposite. The panels are locked and role-owned, the alerts are hard-capped, and the manager overlay is three lines maximum, each one sentence and one action. It runs at whatever coverage the club has, from all-manual tagging to live camera automation.

Situation
Score, clock, cards, momentum, subs left
Shape & marking
The XI, assignments, live mismatches
Card / risk
Who is on a yellow, the referee threshold
Pattern feed
Repetition detection on their sequences
1
new alert per 90 seconds
3
active alerts, maximum
3 min
each alert expires unless re-triggered
Manager overlay, capped at three
Overload-left x3 in ten minutes. Their winger keeps isolating our right-back.Double up wide right
Their number 6 is on a yellow. He is the screen in front of the back four.Run at him

Every alert is a repetition, a danger, a mismatch, or a fragility trigger, never noise, and it expires if it stops mattering. The manager sees at most three things, each already turned into an action. The discipline is the product: a live layer that respects the one resource he has none of during a match, attention. The point of the live layer is not to show everything. It is to surface the one thing worth acting on.

Illustrative engine read on the real In-Match Live Ops layer (the locked panels, the anti-spam caps, the three-alert manager overlay in "they are doing X, do Y" form). Composite match, demonstration figures.

Case 03 · a hat-trick is performance, not proof

One loud match does not move a rating.

After the match, Truth Separation asks what a box score cannot: was this performance also evidence? A hat-trick updates a rating only if the finishing execution was genuinely elevated, not if a striker converted a normal chance load above his expected goals, which is variance. Process over outcome, and one match is never enough.

Performance
The hat-trick itself
Three goals, logged. It goes in the sample and tightens the confidence band, but it does NOT move the finishing KR on its own, because a good return can be a normal process running hot.
Evidence
The execution underneath
New evidence only if the finishing quality and movement were genuinely elevated over expectation, corroborated by the process data and the recent comparable matches, not the scoreline alone.
PatternWhat updates
Single matchSurfaces as an anomaly. No automatic update.
2 to 3 matchesA possible trait update if the process data corroborates. Still no KR movement.
4 to 5 matchesA confidence-weighted trait update and a possible KR movement if several traits shift.
Season-longA full trait recalibration and a standard KR re-evaluation.

A player is never updated on the strength of one night, however loud, because the same discipline that governs the ratings governs the match reads: believable over impressive, process over outcome. A hat-trick against a poor opponent while the process stayed ordinary is a no-action item, disclosed as such. The referee is handled the same honest way, as a condition on the match, never a change to anyone's rating. A match is evidence to be weighed, not a verdict to be obeyed.

Illustrative engine read on the real Postmatch Truth Separation (performance versus evidence, process over outcome, the multi-match thresholds) and the referee-as-condition rule. Composite player, demonstration figures.

The law underneath
Turn the truth into a plan. Never let the match rewrite it.

Match Ops plans with the ratings and learns from every match, but it never reaches back and rewrites the truth it was given.