Sandbox

## The gap The Compare screen currently promises an 'average IAMS' figure that is not rendered (P0 bug #17, per `docs/SESSION_AGENT_INDEX.md`). Even once that number lands, it tells a sporting director *how good* two players are — not *whether they blend*. A club weighing two midfielders for the same slot needs to know if signing both creates a Camelot clash (±6 wheel distance = maximally dissonant) or a complement (same-number opposite-letter = ideal texture pair). ## The idea Add a **Harmonic Compatibility banner** to the `/compare` screen. When two players are loaded, compute the Camelot wheel distance between their keys using the locked 24-key pitch-geometry mapping (per `docs/camelot_deep_dive.md` §3.0). Render one of three states: - 🟢 **Harmonic** (distance ≤ 1 or same-number opposite-letter) — "These two blend. Safe to co-sign." - 🟡 **Neutral** (distance 2–4) — "Workable. Monitor role overlap in training." - 🔴 **Clash Alert** (distance 5–6) — "Tonal clash. One may suppress the other's natural role." Below the badge, show the wheel mini-graphic with both player keys highlighted and the arc between them coloured accordingly. ## Why now The Camelot wheel distance formula is already implemented (`harmonic[]` array in `data.js`). This is pure UI assembly — no new ML, no new data. It reuses the `posToNumber` + letter derivation already in production. Shippable in <2 days. ## Success metric Track `compare.clash_alert_shown` events via `event_log`. If >30% of compare sessions trigger a Clash Alert view and dwell time on compare rises >20 s vs baseline, the feature is surfacing genuine decision value.

**Problem:** `docs/camelot_deep_dive.md §3.1` currently assigns the A/B letter purely via `flair = (Technique + Pace) / 2` vs `structure = (Decisions + Intelligence) / 2`. This binary split ignores…

**Problem:** Clubs can find individual players whose Camelot key is harmonic with the club profile, but there is no surface that shows the *squad as a whole* — whether the 25-man roster is…