Qalibr docs — your guide to bug intake intelligence. Start a free trial →
Core conceptsCalibration
Core concepts

Calibration

Calibration is Qalibr being honest about how settled a reading is. It shows up in two places, and neither one asks anything of you.

Scores that settle in

When you’re just starting there aren’t many routed bugs behind a score, so Signal scores carry a [ PROVISIONAL ] tag — scores calibrate to your inbox as you route more bugs. The tag is a caveat on the reading, not a different reading: a provisional score is computed exactly the same way as a settled one.

As you approve and route bugs, the count climbs. Once it crosses the threshold the tag quietly disappears, and Reports shows you how far along you are. Calibrated is the silent, steady state.

The scoring itself is the same for everyone — Qalibr doesn’t learn a per-workspace formula. What changes is how much history sits behind the number, which is what the tag is telling you.

Honest markers

Calibration also shows up on individual severities. A ~ marker means Qalibr is hedging — offering a starting point rather than a firm call. A marker means a deterministic rule held the severity at High or above for a critical production surface. A § means one of your rules set it, and a Δ means you did.

Together they tell you, at a glance, which calls to trust, which to double-check, and which were already yours. See Severity.

Where you see it

The [ PROVISIONAL ] tag sits next to the Signal score in the detail panel, and the row anchor in your Inbox mutes to ~ Signal while it applies. The calibration marker rides on the severity pill everywhere severity is shown. Reports carries a Calibration chip with your progress toward the threshold — the one figure on that page that ignores the window entirely, because it’s a lifetime count.

There’s nothing to configure. Working your inbox is the whole mechanism.