CurveSpotter Corrections register
Corrections on record.
Every correction to this site is recorded here. Entries are appended with a timestamp and never removed.
- Two calls published with an open date in the future LATEST ENTRY CS-COR-2026-0813-002
- What was wrong
- Both entries were drafted expecting publication on 2026-08-14 and carried calledAt 2026-08-14T00:00:00Z. They were signed and published on 2026-08-13, so for several hours each page stated an open date that had not yet arrived, in its header, its facts table and its citation block.
- Magnitude
- The open date was one day ahead of publication. The baselines the calls are measured against were unaffected: both cite the 2026-08-12T18:00:01Z snapshot, and the rating counts (832 and 1,714) were correct as published.
- What changed
- Both entries now open on 2026-08-13, the day they were published, and their resolution dates moved with them — D+21 from 2026-09-04 to 2026-09-03, D+42 from 2026-09-25 to 2026-09-24. The methodology now states the convention the entries were written against: open times are recorded at day granularity, the baseline carries the exact snapshot timestamp it came from, and no entry opens later than the day it publishes.
- Scope
- /calls/ziggy and /calls/scrollfit, from their publication on 2026-08-13 until this correction the same day.
- Detected
- Internal pre-announcement review, before the site had been announced to anyone.
The dates a call is opened and resolved are the mechanism by which this ledger can be checked. A reader who cannot trust the open date cannot trust anything derived from it, including the claim this site exists to make — that the call preceded the outcome.
Editing a published entry is itself a change to the record, which is why it is recorded here rather than made quietly. Nothing else in either entry was altered: the evidence, the baselines, the mechanism quotes and the stated risks are as they were signed.
- Growth rates published from sub-daily observation windows CS-COR-2026-0813-001
- What was wrong
- Published growth rates were computed from the two most recent adjacent snapshots with no minimum observation window. Collection ran twice on 2026-08-12, so 57 of 60 ranked rows normalised a 6.85-hour observation to a per-day rate.
- Magnitude
- Libre by Abbott published +1,098.1/day against a windowed figure of +360.2/day (3.05×). Brainrot: Screen Time Control published +603.4/day against +183.5/day (3.29×). Welmi published +336.8/day against +121.6/day (2.77×).
- What changed
- Published rates now come from a window of at least 20 hours — the floor the project's own scorer already applied internally and the site's data path was bypassing. Where no qualifying window exists, no rate is published at all.
- Scope
- /rankings, every /niches/* page, and the growth figure on every /apps/* page, from the site's launch until 2026-08-13.
- Detected
- Internal review, before the site had been announced to anyone.
App Store rating counts arrive in batches. A sub-daily window does not measure a rate; it measures where a batch boundary fell. Libre by Abbott’s rating count was unchanged for the 17 hours before the affected window, then moved 313 inside 6.85 hours. Normalised to a day, that boundary published as +1,098.1/day where a 20-hour window measures +360.2/day.
The Worker scorer already enforced a 20-hour minimum observation window internally. The site’s data path read the two most recent adjacent snapshots directly and bypassed that floor. Published rates now pass through the same floor, and rows without a qualifying window carry no rate.