Nexus metric
Nexus Propagation™
How the signal crossed communities — from builders to press, visualized.
What it measures
Nexus Propagation is the lane-by-lane timeline of every real signal for a subject: eight ecosystem lanes (Primary, GitHub, Hacker News, Research, Models, Media, Commentary, Video), each dot a source-linked event, sized by engagement, placed at its true timestamp.
Trends are not points — they are journeys across communities. Propagation shows whether a subject stayed inside one lane (echo) or crossed lanes (genuine spread), and how long each crossing took. The GitHub-to-press gap alone is one of the best leading indicators we track.
How it's computed
Every window signal is mapped to its ecosystem lane and plotted at its published timestamp; dot radius is log-scaled engagement (points + 2× comments + log-scaled downloads). The visualization renders exactly the ingested signals — nothing interpolated.
The 8 tracked communities a signal can appear in.
Primary, GitHub, Hacker News, Research, Models, Media, Commentary, Video — each with its own authority profile.
How long the signal took to jump between lanes.
Read the horizontal gap between a lane's first dot and the next lane's first dot.
Which individual signals carried the most weight.
Dot radius grows with log-scaled engagement, so a 900-point HN thread reads instantly.
How to read it
4+ lanes
Broad propagation
The signal crossed most communities — a trend with general reach.
2–3 lanes
Crossing
Mid-journey: watch which lane it enters next.
1 lane
Contained
One community's conversation — could be early, could be an echo.
Lanes not yet ingested (search, X) are absent from the visualization by design; their absence is reported in Coverage rather than approximated.