Corrections Log
When a number or a counting rule changes, we write down when, what and why. An empty log is a claim, not a promise — check the date below.
How this log works
This page records two kinds of change: verified data corrections (a wrong amount, date, round label, investor or classification) and counting-rule changes (a different way of merging reports, converting currency, or treating public-market programmes). Routine daily additions of new events are not corrections and are not listed here; they appear in the funding timeline and in the event ledger, whose Git history is the complete audit trail.
Each entry states the date, the affected scope, what changed and the evidence. We do not silently rewrite history: if a change makes older published figures non-comparable, that is called out in the entry.
Log
| 2026-11-05 · Counting rule | Publication-layer de-duplication of syndicated reports introduced. Multiple outlets covering the same financing within a short window now render as one editorial event, with the number of merged reports disclosed on the note. The raw event ledger is unchanged, so no previously reported amount was deleted. Reason: repeated near-identical headlines were inflating the visible event count and were being mistaken for separate rounds. |
|---|---|
| 2026-11-05 · Editorial | Funding-event notes stopped reproducing raw news headlines. Published notes now state amount, stage, named investors and a hedged interpretation. Reason: aggregated headline text is low-value content and obscures which figures are actually verified. |
| 2026-11-05 · Transparency | Visible byline and separate data-cutoff / page-generation dates added to every indexable page. Sitemap lastmod switched from build time to content-hash-based dating. Reason: a daily build timestamp on an unchanged table implies freshness the data does not have. |
| — · Data corrections | No verified data corrections have been recorded since this log opened. New entries will be appended above this line with a date and a source link. |
Requesting a correction
Email [email protected] with the page URL, the exact field, the primary source and the value you believe is correct. The contact page lists the full format and response times. Confirmed errors are applied in the next daily build (normally within 24 hours) and then added here.
If we disagree
We will keep the existing figure and explain the reasoning in our reply. Conflicting sources are not averaged. Where a credible dispute remains unresolved, we would rather mark the record as disputed than present a false consensus; persistent disputes about a counting rule are escalated to a dated entry on this page so all readers see the same caveat.