Every data correction Afrimintel has made since April 2026 · Last updated: 18 May 2026 · Editorial responsibility: Nikesh Patel, geochemist
Afrimintel publishes every data correction it has made. Every source we have replaced. Every assumption we have retracted. Every error caught by us or flagged by a reader. We do this because most commercial mineral intelligence platforms do not, and the distinction matters to anyone making capital decisions on African minerals.
Filter by type, scope, or date. Every entry names the original claim, the correction, and the source that drove the change. If you spot something we have not caught, email nikesh@afrimintel.com.
This is not an apology page. Corrections are not weaknesses — they are evidence that the platform is operating on primary-source discipline rather than aggregated secondary sources. A platform that never corrects is not a platform that is verifying.
Disclosure on "editorial sign-off" — added v1.0.61. Audit-log entries carry an editorial_signoff field naming Nikesh Patel. For the rapid-cycle entries v1.0.55 through v1.0.61 (a sequence of forward-build and corrective-patch deploys), "editorial sign-off" means the work was executed under direct editorial instruction and direction — not that each entry's every line was independently reviewed and ratified before deploy. Editorial responsibility for the platform is real and sits with Nikesh Patel; the distinction this disclosure draws is between directed execution and line-by-line ratification. A hostile contrarian audit flagged that the unqualified "editorial sign-off" phrasing could be read as the latter when the rapid-cycle reality was the former. The forcing-function verification cycles (27 May, 13 June, 18 July 2026) recorded in sources-verification-log.json are where line-by-line editorial verification of the substrate is scheduled to occur.
Earlier corrections are reflected in the current data but are not individually logged here. The log begins from the point at which this discipline became continuous.
Entries fall into five classes. A correction is logged when any of the following is true:
Release-level technical refactors, cosmetic styling work, and new feature additions are NOT logged here — they appear in the release CHANGELOG files. This page is specifically for changes where a reader would be entitled to know the claim has moved.
If you read any Afrimintel record or output and believe it is wrong, send the specifics and a citable source to nikesh@afrimintel.com. Corrections from external readers are acknowledged in the Source field of the relevant entry. The platform's data discipline gets better when people who know more than we do tell us.
Afrimintel · Africa Mineral Intelligence · Methodology · Roadmap · About