Signal score
The Signal score is the 0–100 number on every bug. It’s the priority anchor — what decides where a bug sits in your inbox. Higher means “look at this sooner.”
What goes into it
The score blends two things you can see, gated by how confident the classification is:
| Dimension | What it captures |
|---|---|
| Severity | How damaging the bug is — a Critical bug starts far higher than a Low one. |
| Frequency | How often this issue keeps coming back. A repeat report raises the score, but with diminishing returns — the tenth re-report doesn’t drown out a brand-new critical bug. |
The detail panel shows these as a breakdown so you can see why a bug scored the way it did. Two more dimensions — Novelty and Sentiment — appear locked for now; they’re reserved for a future release.
The score also carries a confidence marker — a small × conf next to it.
When a report is thin and the read is less certain, that marker damps the
score down. It’s never zeroed, just held back until there’s more to go on.
Frequency, in plain terms
A bug reported once already counts. Reported again, it climbs. But the curve flattens as the count grows, so a noisy, often-repeated low-severity issue can’t out-rank a fresh critical one on volume alone. Severity stays the dominant signal.
Provisional vs calibrated
While your inbox is still small, scores carry a [ PROVISIONAL ] tag — they work, but they’re still settling in. As you route more bugs, Qalibr calibrates the scoring to your team and the tag drops away. See Calibration.