Turn the truth into a plan. Never let the match rewrite it.
Match Ops is the match-facing engine. It takes the governed player and team truth and turns it into what a staff actually uses across a match week: a prematch opposition report, a disciplined live layer, a halftime packet, and a postmatch audit. The prematch plan is built from the opponent's own structural gaps, not from opinion. The live layer is capped so it stays a plan a manager can read at a glance, not a firehose. And after the match, the engine knows the difference between a performance and a proof, so one loud game never moves a rating. It reads the truth. It does not rewrite it.
Attack, deny, stress, fragility. All drawn from their structure, not our opinion.
The prematch report does not editorialise about the opponent. It reads their Missing Demands and Fragility Flags straight from the Team Intelligence diagnostics and turns them into a concrete leverage plan: where to attack, what to deny, where to apply stress, and what breaks if a key man is booked or withdrawn. Composite opponent, the four-part plan.
Every line traces back to a specific diagnostic on the opponent: an uncovered demand, a single-point-of-failure flag, a primary initiator. The plan does not say attack the left because someone has a feeling; it says attack the left because their left centre-back is the uncovered pace demand. This is diagnose-before-optimise pointed at the opposition: 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.
A manager glances and decides. He does not read a dashboard mid-match.
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 so nothing spams the manager, and his overlay is three lines maximum, each one sentence and one action. It runs at whatever coverage the club has, from all-manual tagging up to live camera automation.
Every alert is a repetition, a danger, a constraint, a mismatch, or a fragility trigger, never noise for its own sake, 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 a manager has none of during a match, which is 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.
One loud match does not move a rating. The engine reads the process, not the score.
After the match, Truth Separation asks the question 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 a single match is never enough.
The engine will not update a player 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 bias and 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.
Match Ops is the action layer, and its whole discipline is that it consumes the truth without ever becoming it. Before the match, it turns the opponent's own diagnosed gaps into a plan, so every instruction traces to a real structural weakness rather than a hunch. During the match, it caps itself hard, because a plan a manager cannot read at a glance is not a plan. After the match, it refuses to let one performance masquerade as proof, reading the process under the result and moving a rating only on sustained, corroborated evidence. The referee is a condition on the match, never a change to who anyone is. The ratings sit upstream, governed and stable; Match Ops reads them, plans with them, and learns from every match, but it never reaches back and rewrites the truth it was given.
Plan the match. Read it honestly.
Match Ops turns governed truth into a prematch plan built from the opponent's gaps, a disciplined live layer, and a postmatch read that separates performance from proof.