A model-in-the-loop annotation platform spanning six sport-specific surfaces across cricket and badminton. Not a labelling tool. A data-flywheel — every keystroke produces a structured prediction/correction delta that feeds the next training cycle. The platform isn't measured by what it labels. It's measured by how much better the models get because of what it labels.
Sports CV models live or die by the quality of their training data. At KhiladiPro we ship trajectory, keypoint, and event-detection models across cricket and badminton — every one of them needs frame-level supervision: where is the shuttle in frame 247? Which four points define the bat? Did the ball pitch IN or OUT? Are these 10 court corners detected correctly?
Off-the-shelf annotators (CVAT, Labelbox, V7) are sport-agnostic. They treat a shuttle, a cricket ball, a bat quadrilateral, and a 10-point court grid as the same generic "draw a thing" task — which means a 90-second rally takes 40 minutes to label, and reviewers can't catch sport-specific errors. A "landing" frame that's physically impossible. A stumps box that doesn't enclose the wickets. A court corner placed off the singles line.
I built the KhiladiPro Annotator to collapse that loop. Model-first. Sport-aware. The model labels the video first — the annotator only corrects what's wrong — and every keystroke is shaped around the physics of the sport being labeled.
The architectural decision that turns annotation from a cost center into a continuously-improving training-data pipeline. Every label preserves both the model's prediction and the human's correction — and the delta becomes the next training signal.
Sample model improvement through multiple retraining iterations driven entirely by annotator-produced training data. Numbers reflect the shuttle tracker (TrackNetV5) across the platform's lifetime to date.
These aren't model-design numbers. They're infrastructure-driven numbers — the same model architecture, retrained on data the annotation platform produced over multiple cycles. The flywheel's design is what made the improvement compound rather than plateau.
Each tool ships with its own label schema, keyboard model, and sport-specific physics constraints — but they all share the same offline-first edit cache, model-in-the-loop schema, and retraining-signal infrastructure. Different stages of the flywheel; same underlying mechanism.
R = release, L = landing, C = contact, O = occlude. Shift+←/→ jumps to the next/previous frame the model actually detected something on — annotators only stop on frames that need attention. Landing classification and line-call tag are stored alongside the point, not derived after the fact.
predBowl, predBat, manBowl, manBat.R / L / C for release / landing / contact; B / Shift+B for bowler stumps corners; N / Shift+N for batter stumps; full Cmd+Z / Cmd+Shift+Z undo-redo bolted onto every surface.
1 / 2 / 3 / 4 cycle the active keypoint — no mode pickers, no dropdowns. Active keypoint is color-coded (red, orange, cyan, purple). Dashed lines = predictions, solid = manual edits — the visual contract makes it instantly obvious where the model is confident and where the human took over.
0–9 cycle through the 10 keypoints. Each has independent visibility flags — courts go partially off-screen during broadcast cuts and the model has to know which points are occluded vs. off-frame. Two annotation flows supported: label-first (pick a keypoint, then click) and click-first (click, then assign) — different annotators converged on different rhythms.
The platform-level choices that make six different sport surfaces coexist on one editor backbone without becoming an unmaintainable mess.
All edits write to IndexedDB with a 500ms debounce, then sync to the server via versioned patch ops with conflict detection on base_version. Two annotators can edit the same clip without clobbering each other. A flaky wifi connection doesn't lose 30 minutes of work.
Every label carries both a pred_* field (model output) AND a man_* field (human correction), plus an edited flag. The annotation isn't a replacement for the prediction — it's a measured correction of it. Models keep learning from the delta.
Each tool's frame schema encodes the events the sport actually cares about — contact, landing, release, rest for cricket; landing_area (near/far) and line_call (in/out/unclear) for badminton; det_conf + 4-point quadrilaterals for the bat. The schema rejects physically-impossible labels before the human sees them.
Exponential-backoff XHR PUT (1s → 2s → 4s) with progress callbacks and a 10-minute timeout. The retry budget exists because annotators work on real-world wifi, not labs — and losing a half-hour of corrected labels because of a network blip is unacceptable when those labels are the retraining signal.
The platform compounds. Every annotation session improves the next training cycle. Here's what the next cycle is targeting.