Afrimintel · Insights · Methodology · Audit Log
June 2026 · Nikesh Patel · Every factual claim below is Sourced or Derived per the Quality Standard; where evidence is one data point, it is presented as one data point.
African mining assets are systematically discounted — in valuation, in cost of capital, in insurance pricing — not primarily for what they are, but for what cannot be cheaply verified about them. The major intelligence platforms cover African assets; what they do thinly is verification depth: field-level provenance, current-status confirmation, disclosure-document reconciliation. Where verification is thin, sophisticated capital does the rational thing: it assumes the worst case and prices accordingly.
The EU's Carbon Border Adjustment Mechanism, in its definitive regime since 1 January 2026, prices the embedded emissions of covered imports. Where an importer cannot present verified producer data, the regulation assigns default values: country-average intensity plus an escalating mark-up — 10% in 2026, rising to 30% from 2028 — and where reliable country data is lacking, the average of the ten highest-emitting exporting countries. Absence of verifiable data is priced as worst case, by statute. That is the verification discount made explicit, and the same logic operates informally across project finance, M&A comparables, and political-risk insurance every day.
The raw disclosure infrastructure in African mining jurisdictions is stronger than its reputation. Twenty-eight African countries implement the EITI Standard; their summary data is published in a standardised, USD-normalised, IMF-GFS-classified format, centrally and under open-data terms. Zambia pioneered the G-Factor — a one-page, transparent-formula metric of mining fiscal contribution published through its EITI process. Tanzania's Kabanga nickel project declared maiden reserves in a July 2025 feasibility study filed with the SEC. Mali's Loulo-Gounkoto complex emerged from its 2025 settlement with the settlement's material terms — payments, permit extension, ownership structure — on the public record. The documents exist. What has been missing is the layer that reconciles them, states their vintage, and says plainly where the record is silent.
The discount persists partly because most data products treat missing data the way the market fears it: silently. A field left blank is indistinguishable from a field never checked. The alternative is a three-state discipline — every value either Sourced (named document, dated), Derived (published methodology over sourced inputs), or Absent (stated as such, never estimated). Under that discipline, absence becomes a finding rather than a void: a capital committee learns more from "asset-level AISC: Absent — operator discloses group-level only" than from a confident number with no provenance. One illustrative pair from our comparable-transactions set: the nearest like-for-like contrast between an African and an international gold acquisition — same stage, near-contemporaneous — shows a multiple gap consistent with the thesis. It is one pair, and we present it as one pair, not a statistic. That restraint is the point.
Verification claims are cheap; correction records are not. A platform asserting decision-grade data should be able to show, publicly and in order, every error it caught, who caught it, and how fast it was fixed. Afrimintel's audit log carries that record — including same-day correction chains where our own checks caught our own work. The discount closes one verified field at a time, and the institutions doing the discounting are precisely the readers equipped to check.
Sources: EU CBAM Regulation and Implementing Regulation 2025/2621 (default values); EITI implementing-countries register and Summary Data documentation, eiti.org (retrieved June 2026); Lifezone Metals Kabanga FS TRS (SEC Form 6-K, July 2025); Loulo-Gounkoto settlement disclosures (November 2025, public record); Afrimintel comparable-transactions set (25 transactions, normalisation methodology published). Claims about Afrimintel's own data layer are verifiable at /api/v1 and /audit-log.