← Back to software selection · Find a listing
Every number here is a judgement, not a measurement. A marketing claim is worth 0.60 because somebody decided it was. The honest thing to do with a number like that is not to defend it — it is to make it movable, show exactly what moves when it moves, and publish where it was left.
Nothing you change here takes effect until you publish it. Move the dials, watch the ranking, then export the calibration file and rebuild. A deployment's calibration is a short readable list of deliberate decisions, sitting in the open next to the engine.
The multiplier applied to a claim, given how it is evidenced. These are the most consequential numbers in the project.
Regulatory and certification claims are raised to this power, so a page counts for less there than it does for a feature claim. 2 means squaring: a 0.60 marketing claim becomes 0.36.
Publishing writes the calibration to the registry and every page picks it up on next load. The previous calibration is archived, never overwritten — a scoring change is exactly the kind of thing that must not be quietly reversible.
The full catalog under a representative regulated-buyer weighting, scored with your current dials against the defaults. Rank changes are the point: if a number can be nudged until a particular product wins, that is visible here rather than buried.