NexusCoach — evidence view prototype

Single-replay review: suggestions linked to a timeline and sparse spatial evidence
prototype build · synthetic raw loops only

Step 1 · selected participant (gate)

Identity cannot be inferred. The decoder yields an anonymous common-participant candidate present in every sampled match; the product must ask and never auto-select.
Personalized death/positioning claims are withheld until you confirm. Confirming still does not establish hero identity (see limits).

Step 2 · report (max 3 suggestions + 1 strength, no padding)

Evidence timeline

lifecycle
positions
stats/score
loop —
Raw tracker loops only. No seconds conversion, no pause/speed assumption, no client-clock alignment.

Step 3 · sparse spatial evidence at selected loop

tracker position observation lifecycle point (unresolved unit) uncertain / review prompt no observation — unknown
 
Coordinate-scale warning: in 53 sampled same-loop coincidences the documented *4 tracker convention did not hold; tracker and lifecycle points are kept on separate raw grids and are never mixed or fitted. Raw grid, not a tactical map — no lanes, terrain, pathing, vision, distance-blame or soak overlay.

What the data can and cannot say

Available as evidenceNot established
Raw loop ordinals, stream + event familySeconds / client clock alignment
Typed unit lifecycle markers (unresolved)Hero or player deaths, revive reconciliation
Sparse position observations with source/scaleContinuous movement, current position, “alone”
Stat/score label namesValues, units, player association
Gaps between observationsAbsence, missed soak, missed XP, lane blame
No build-matched hero/body semantic table exists in the inspected decoder runtime, so generic player-controlled-unit lifecycle cannot be promoted to hero/player deaths or score reconciliation.