H-Oracle View / HorusXI · Identity continuity
Keeping identity attached to the player.
BlueX studies how a player identity can remain continuous across cameras, occlusion, and crowded play without hiding ambiguity.
Research question
How can the same player remain identifiable when the view changes, bodies overlap, and visual cues disappear?
Why this matters
Study the behavior that changes the work.
A stable track is not automatically a verified identity. Match analysis must keep the distinction between a visible person, a continuous track, and a roster identity—especially when evidence is incomplete.
Across-view continuity
Study how synchronized views can preserve a player thread when one camera loses sight of the action.
Identity evidence
Combine match context and visible cues while keeping the supporting observations attached to each identity decision.
Reviewable ambiguity
Route uncertain or conflicting identity evidence to review instead of silently assigning the most convenient player.
Validation principles
Evidence before a claim.
Reliable identity continuity lets analysts query a player across the full match while still seeing where the system was certain, uncertain, or corrected.
Include crowded play, substitutes, similar kits, partial bodies, view changes, and long periods away from the ball.
Review track continuity and roster identity as separate decisions with their own evidence states.
Preserve corrections so later runs can be compared without erasing the original uncertainty.
Reading standard
Evidence stays attached.
Identity is never inferred from a single weak visual cue when the match evidence conflicts.
Unknown remains a valid state until the available evidence supports a roster identity.
Human correction stays attached to the observation history and later analysis that depends on it.
Research to workflow
See the result on a real match.
A pilot shows how the research becomes reviewable evidence for analysts and coaches, with clear confidence and review states.