Changelog

Append-only and versioned. Every published score records the version it was computed under, so a number can always be traced to the exact formula behind it.

What it means

The changelog is the durable record of every version of the methodology. No row is ever edited or removed — only appended. A brand's score snapshot carries its methodology version; the changelog entry for that version is the full audit trail. Version bumps are classified as patch (formula unchanged, parameter correction), minor (additive change, no re-computation required), or major (formulas changed, full re-computation triggered).

Inputs & data fields

FieldTypeMeaning

methodology_versionsemverThe version string (e.g. v4.0.0) — major.minor.patch.

applied_attimestampWhen this version became the active methodology.

bump_classenumpatch · minor · major — determines re-computation scope.

summarytextOne-sentence description of the change. Append-only.

Process & formula

score.methodology_version = active_version at compute_timemajor bump → re-computation of all scores · no silent overwrites

Each score snapshot records the methodology version at the moment of computation.
A major bump triggers a full re-computation; minor bumps are recorded but do not force re-computation.
The prior version and its snapshots stay on record — the history of a methodology is part of the index.

How it affects public pages

major bumptriggers re-computation; all scores carry the new version string.

patch / minorrecorded in changelog; existing score versions unchanged until next recompute.

Worked example

VersionDateChange

v4.0.02026-01Independent-source floor formalised; freeze policy added. Locked.

v3.2.02025-09Crypto-exchange scale promoted to staging.

v3.0.02025-03Per-vertical scales; cross-vertical comparison removed.

v2.1.02024-08Cluster counting — clusterer v1.3.0.

No row is ever edited or removed — only appended.

Publication states →When we are wrong →Methodology overview →