Model versions and what changes between them
Every score names the model version that produced it. What a version is, where the release notes live, and what happens to old scores when a model changes.
What a version is
A model version fixes the components, weights, driver mappings and adjustment rules for one lens or all five. Every anatomy names the version that produced it.
Where the release notes are
The methodology page lists every version with its date, the lens it applies to, a summary and the specific changes. The changelog links to the same entries under Scoring.
What changes in a version
Typically a component or driver is added, weights are rebalanced, or a gate or confidence rule changes. We never add a field that reads a protected characteristic, and each version is reviewed for proxies before release.
What happens to old scores
Properties are re-scored on their next refresh with the current version, so your shortlist always reflects one model. Rank history on the property page keeps the version on each point, so a jump caused by a model change is labelled as such rather than looking like the property changed.
Telling us a score looks wrong
Use the data-correction topic on the contact page with the address and what you expected. We inspect the drivers and source fields behind the anatomy and reply with what we found.