Valahigh  ·  Clearifi  ·  In transition

A recruiting-intelligence layer for men's basketball.

A case study of the 2025–26 build, which paired a cross-level talent-evaluation score with Webster, a computer-vision film engine. Built transparency-first and abstain-first: every score and report explainable, versioned, and confidence-tagged.

Clearifi was built as a recruiting-intelligence platform for men's basketball that normalized fragmented player data (high school, club, college, and transfer) from public and provided sources, and brought game film into one consistent, coach-facing view. An intelligence layer, not a directory or a highlight service.

At its core was a transparent talent-evaluation score that aimed to place players from different levels on a single comparability scale, with cross-level translation still developing, and a computer-vision engine, Webster, in development to turn raw game film into structured, play-level evidence attached to a player's card.

The design ethos throughout was transparency-first and augmentation-not-replacement: every score and report explainable, versioned, and confidence-tagged, built to support a coach's judgment rather than override it.

A short walkthrough of the 2025–26 coach-facing view: the cross-level comparability score, and how Webster was being built to turn film into confidence-tagged, human-reviewable play-level evidence.
Clearifi · Deep dive

The box score loses the player. We give it back, honestly.

A deeper look at the market, the build, the engine, and where it goes.

01 / 14

The score

A transparent talent-evaluation score that put players from different levels (a high-school recruit, a club standout, a college transfer) onto one common comparability scale so they could be viewed side by side, with cross-level translation treated as developing and unvalidated.

It was explicitly a comparability measure, not a prediction of future outcomes. That was a deliberate design call: it was scoped as a cross-level comparability measure rather than an outcome forecast, and shipped as an auditable, versioned score instead of a black-box "will succeed at the next level" number.

Webster, the film engine

Webster was designed as a computer-vision engine to turn game film into structured, play-level evidence (proposing who did what and when where the footage supports it, and abstaining otherwise), plus a per-skill profile on each player card. It orchestrated well-understood open-source building blocks (object detection, multi-object tracking, scoreboard reading, jersey-number reading, pose, and appearance embeddings) into a single pipeline rather than leaning on one proprietary model.

It was abstain-first and human-in-the-loop by design: it proposed rather than asserted, reported an explicit confidence with every output, and abstained when uncertain instead of guessing. Results routed through a human correction step; those corrections were captured so they could inform model training once rights-cleared, labeled data was available.

The output format was designed so that every analysis shared the same structured, versioned shape, making two reports directly comparable, and it was built to reduce the analyst-to-analyst subjectivity, fatigue, and drift of ad hoc scouting. Identity was approached in a privacy-respecting, BIPA-conscious way, using jersey number, team color, on-court position, and roster context as evidence rather than asserted identity, and abstaining when the footage was not clear enough. No facial recognition, no biometric identifiers anywhere.

Under the hood it was a modern web stack (React / TypeScript front end, a Postgres-based backend) plus a GPU-accelerated cloud vision pipeline, with a clean architectural boundary that separated the scoring engine from any single data source, so the same engine could run on different underlying feeds. The rights posture was deliberate: any model training would use only openly licensed footage (Creative Commons / public domain), shipping models would never be trained on copyrighted broadcast footage, and only permissively licensed open-source components (MIT / BSD / Apache) would ship in the product.

Clearifi is in transition: the next chapter is being scoped. The work shown here is the 2025–26 build. The data and scoring surfaces were built and operational; the computer-vision engine was still in development, and no CV models were trained or shipped.