Scoring
Scoring fingerprint
A derived value identifying the scoring constants a result was produced under, so two assessments can be told apart from a methodology change.
What it is
A short value derived from the scoring constants in force when an assessment ran, stored with the assessment snapshot.
Why a version number is not enough
A version number tells you the code changed. The fingerprint tells you whether the change affected the calculation this pack performed, which is the question a comparison actually turns on.
An engine release that changes rendering does not change the fingerprint. One that changes a threshold does.
How it is used
The next assessment compares fingerprints. If they differ, composite and domain scores are not compared, because the two numbers were produced by different rules.
Control-level movement continues to be reported, because control identifiers are stable across engine versions.
What this prevents
A methodology change being presented to a board as an improvement in their environment. Without the fingerprint, lowering a threshold would look exactly like getting better.
What it does not mean
It is not a checksum of the pack, and not a signature. It identifies the rules, not the result.