Team KR is not the sum of the players. It is the squad read through the club's actual scheme, weighted by who drives each phase and who is on the pitch, with the fit of the system driving everything. The engine reports the raw talent and the real team side by side, and the gap between them is the story: talent the scheme cannot get out, or a side punching above its talent through fit and coaching. When a system lacks a load-bearing piece, the loss is not one position, it is the whole shape. And a Team KR that floats free of the actual results gets flagged, not trusted.
Talent KR is the fit-blind aggregate, each player's OVERALL weighted by minutes and nothing else. Team KR reads that same talent through the actual scheme, coverage, and fit. The engine reports both, because the difference between them is the single most useful thing you can know about a squad. Two composite clubs, similar talent, opposite gaps.
Same neighbourhood of talent, opposite teams. Club A is a warning: pay for stars, field a lesser side, because the scheme cannot use them. Club B is the model: a squad worth more than the sum of its parts. A rating that reports only one number hides which club you are, and the gap is exactly the thing a sporting director needs to see. Talent is what you bought. Team is what you built. The distance between them is the coaching and the fit.
Illustrative engine read on the real Talent-KR-versus-Team-KR structure (Talent KR fit-blind minutes-weighted; Team KR read through the scheme; the gap surfaces fit quality). Composite clubs, demonstration figures.
When a system needs a load-bearing piece the squad lacks, the value is not lost at that one spot. A high press with no ball-winning midfield is not just a weak holding role: the press gets bypassed, the back line is exposed, and the whole structure leaks. Per-player adjustments cannot express that. The cascade fires a structural override and penalises every player's value in the scheme. Composite high-press side, no rotation ball-winner.
A system that only docked the holding midfielder would badly under-read the damage. The whole shape depends on the ball-winner who is not there, so the whole shape pays. The cascade is diagnose-before-optimise at squad scale: it names the structural gap and prices its true, compound cost, rather than pretending the loss is contained to one position. A team is a structure, not a list, and a structure fails where it is load-bearing.
Illustrative engine read on the real Scheme Fit Cascade (a critical-missing structural override applying a compound penalty across every dependent position, not just the missing role). Composite squad, demonstration figures.
Before the Team KR is trusted, the engine checks it against the club's actual record. The scheme-fit cascade corrects fit mismatches, but it is bounded, so a gap larger than its reach is not a fit problem, it is a signal the player ratings are inflated, and the fix is upstream, not a bigger cascade. And the diagnostics that follow never move the number, they expose how it breaks. Composite side, a Team KR running ahead of its results.
The number is never allowed to drift away from what actually happened. A gap the cascade cannot reach is a flag to fix the inputs, not a licence to fudge the output, and the fragility diagnostics sit alongside the headline so a strong Team KR never hides a squad that breaks the moment one player is missing. A team rating you cannot check against the table, and that hides how it breaks, is not worth having.
Illustrative engine read on the real Pre-Cascade Reality Check (record-mapped tier band, the inflation flag) and the Fragility diagnostics (single point of failure, over-reliance, thin squad). Composite squad, demonstration figures.
A squad is not a list of ratings to add up. It is a structure read through a scheme, and the engine keeps the raw talent and the real team as two separate numbers so the distance between them can speak: talent the system cannot get out, or a side worth more than its parts. When a structure lacks a load-bearing piece, the loss cascades across every position that depended on it, because a team fails where it is load-bearing, not where the ratings are lowest. And the whole thing stays tethered to the results, flagged when it floats free and honest about the single points of failure a headline number would otherwise bury. The best roster and the best team are different objects. The engine is built to show you both, and the gap that separates them.
Team Intelligence separates raw talent from the real team, prices scheme breakdown as the compound loss it is, and keeps the number tethered to the table.