The projection is the start. Game Ops turns it into a plan, an adjustment, and a lesson.
Simulation shows what happens and why; Game Ops does something with it, a scouting plan before, live counters during, and an audit after that sharpens the next plan. And it remembers more than the roster: the coach across programs, the crew profiled like a coach.
The trace becomes a plan you can actually run.
A scout is more than a plan. It is what the opponent runs and how often, the shots they live on, the film to watch, and only then the calls. Game Ops assembles all of it off the simulated matchup. Here is the scout on Duke.
Every call traces back to a specific clash in the simulation, with the projected value attached. This is the scout the sim produces: not "you win 29%," but the four things to do about it, in priority order.
Real Duke engine read turned into an illustrative plan on the real Game Ops scout structure. Demonstration figures.
The plan updates on the fly, powered by a live simulation.
KVision tags actions and coverages live and tracks matchups, so the plan is not frozen at tip-off. When a trigger fires, Game Ops surfaces the counter, and prices it against a live re-simulation.
The halftime adjustments are powered by the live simulation: the engine re-runs the rest of the game under each option and surfaces the one that moves win probability most. A staff corrects the read rather than building it from scratch, in the minutes it actually has.
Illustrative live feed on the real live-tagging and re-simulation structure. Demonstration figures.
After the game, it audits itself, then remembers.
The postgame packet audits whether the plan was run and whether the flags it called actually played out, and it reads the game grades against the plan, who delivered on the assignment, pulling those from Game Grades rather than grading here. Then it feeds the next scout, so playing Duke again starts sharper. And it tracks the people the roster does not capture.
A one-off tool gives you a plan and forgets it. This one grades its own plan, reads the game grades against what it called, and carries the coach and the crew forward, so every game you play against an opponent, the engine knows them better than the last time.
Illustrative audit and loop on the real postgame, coach-profiling, and crew-profiling structure. Coach and crew shown generically. Demonstration figures.
A projection tells you what should happen. Game Ops is what you do about it: the plan before, the counter during, the audit after. Each pass feeds the next, so the second plan against an opponent is sharper than the first, and the tenth is sharper still. And the engine holds what a roster sheet cannot, the coach followed across programs, the crew profiled like a coach, so you do not just scout the team in front of you. You scout everything that decides the game.
Plan it, adjust it, then know them better next time.
Game Ops closes the loop between the projection and the sideline, and keeps the memory.