Corrections
Which period was wrong, what was wrong, and when we fixed it. This page is append-only. Model version changes and panel adjustments are not errors; they are listed in the panel-changes table on the methodology page.
| Date | Scope | What was wrong | What we changed |
|---|---|---|---|
| 2026-09-02 | Public rankings of 11 evaluations (the latest period of the six pet-hardware rankings, aroma diffusers, luxury-car newcomers, and two Japanese CFD rankings) | The same company appeared as several rows on one ranking — different scripts (特斯拉 / Tesla), corporate suffixes (Monex / Monex Securities) and letter case (CATLINK / Catlink) were treated as separate brands, diluting scores and depressing ranks. 48 rows should have been merged. | From 2 Sep 2026 rankings are aggregated by brand entity at display time: deterministic rules merge case and spacing variants automatically; cross-language and subsidiary merges are confirmed by a person under published rules, with every decision logged. Raw rows in the database and issued certificates are untouched; earlier ranks are not directly comparable with merged ones, and the panel-changes table carries the matching entry. |
| 2026-09-01 | Two users' free diagnostic reports | A data migration back-filled English topic names by hard-coded topic id; on the production database those ids already belonged to two users' diagnostic submissions, so wrong English names were written into their report data | Data fixed the same day; the migration now matches on the question text, never on id; the lesson is recorded in the migration's code comment |
| 2026-08 | Verification emails for the free diagnostic | The site-address environment variable was unset, so the verification link in the email pointed at a local development address and did not open | Configuration fixed; every link that goes into an email, certificate or badge is now built from the same site-address variable, never from the incoming request |
Remediation policy
When we find that an evaluation contains calls that were not counted, we re-run that question and regenerate the certificate for every customer who bought one for that run. This is a policy commitment stated on this page, and every time we act on it the corrections log records it — you can check.