Two coding agents editing the same issue, no merge conflict. Here is how git refs make that work
Git refs resolve conflicts
SteadyWhy this scored 13
every term, weightedEngagement per hour, normalized against the fastest item on its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities are talking about the same entity
Decays to zero over 14 days
Subtracted once something is big and old — we rank what's next, not what's peaked
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement. Full methodology
Outlook
low confidence · estimate, not a guarantee7-day
~0
range 0–2
14-day
~0
range 0–0
30-day
~0
range 0–0
Signal history
7-day window (free)— — projected trajectory (estimate, not a guarantee)
Entities
Embed a live signal badge
[](https://www.signalcrest.app/topic/dev%3A4231828)
Drop this in a README or blog post — it updates automatically as the score moves.