Submit a Correction

For committee-facing use, pair this research with Lobito Corridor Finance and Risk Map and DRC Border Clearance and Logistics Readiness Review before turning source analysis into a decision memo.

Direct answer

To submit an OHUASI correction, provide the page URL, the specific claim at issue, the proposed correction, and source evidence showing why the page should be changed. Requests supported by official, primary, transaction, regulatory, exchange, issuer, court, concession, or multilateral sources receive priority.

What this page is for

This page is for reporting factual errors, outdated evidence, attribution issues, metadata problems, and material clarity concerns in OHUASI content.

OHUASI covers strategic assets, privatization programs, capital markets, corridor finance, offshore holding structures, and governance issues. Many of these topics are source-sensitive. A corrected date, transaction status, legal reference, market statistic, source classification, or eligibility statement can materially improve the reliability of a page.

What to include in a correction request

A useful correction request should include five items.

1. Page URL

Provide the full OHUASI page URL or route.

Example: /angola-propriv-intelligence-hub/

2. Specific claim

Identify the exact claim that may be wrong, stale, unsupported, or unclear. Do not only say that a page is inaccurate. Explain which sentence, heading, table, snippet, source reference, or metadata field creates the issue.

3. Proposed correction

State what the page should say instead. If you do not know the exact replacement language, explain the correction direction.

Examples:

• Change completed to proposed.
• Clarify that program inclusion is not the same as transaction launch.
• Replace the market statistic with the latest published period.
• Add that the source is secondary commentary, not a regulator notice.

4. Source evidence

Provide the source supporting the correction. Strong sources include official legal documents, regulator notices, exchange publications, issuer filings, prospectuses, tender documents, concession documents, court records, and multilateral project documents.

If the source is not public, explain what it is and why it should be considered. OHUASI may not rely on non-public material without additional review.

5. Materiality

Explain why the correction matters. A correction is higher priority when the current wording could affect reader understanding of transaction status, legal status, investor eligibility, source authority, market risk, or official attribution.

Correction categories

Use the most relevant category when submitting a request.

Factual error

Use this when a statement is wrong.

Examples include wrong dates, wrong entity names, wrong transaction status, wrong regulatory reference, wrong market statistic, wrong asset classification, or wrong attribution.

Outdated evidence

Use this when a page was accurate when published but newer source evidence changes the analysis.

Examples include a new decree, regulator notice, prospectus, exchange statistic, financial statement, project document, or concession disclosure.

Source classification issue

Use this when a page gives too much or too little weight to a source.

Examples include treating commentary as official evidence, failing to identify a document as a primary source, or not distinguishing a policy announcement from a binding instrument.

Metadata or snippet issue

Use this when the title tag, meta description, excerpt, social preview, schema summary, featured-snippet answer, or heading creates a misleading impression.

Examples include implying that a transaction is active, official, investable, recommended, or complete when the body copy is more cautious.

Attribution issue

Use this when a quote, statistic, source, or institution is incorrectly attributed.

Clarity issue

Use this when wording is not technically wrong but could reasonably mislead readers.

Examples include unclear use of proposed, approved, listed, sold, launched, eligible, regulated, guaranteed, or official.

Requests OHUASI may decline

OHUASI may decline requests that are not evidence-based or that would weaken reader trust.

Examples include requests to:

• Remove accurate but unfavorable analysis.
• Replace source-grounded language with promotional language.
• Present an issuer or asset as lower risk than the evidence supports.
• Treat a non-public assertion as verified fact.
• Hide a correction without a note where the change is material.
• Change editorial conclusions only because a stakeholder disagrees with them.

Priority handling

OHUASI should prioritize correction requests that involve:

• False official-status implication.
• Wrong transaction status.
• Wrong regulator, exchange, issuer, or government attribution.
• Wrong investor eligibility statement.
• Wrong legal or source reference.
• Misleading metadata or snippet text.
• Material risk of reader confusion.

Lower-priority requests include non-material style preferences, minor wording changes, and unsupported disagreement with analytical framing.

Suggested correction request format

Use this structure:

Page URL:
Specific claim:
Proposed correction:
Supporting source:
Why it matters:
Requester name or organization:
Contact email:

What happens after submission

OHUASI should review the request against the Corrections and Updates Policy and the Source Transparency and Evidence Labels page.

A correction may result in:

• No change, if the current page is supported.
• A wording clarification.
• A factual correction.
• A source note.
• A metadata revision.
• A full page update.
• A correction note.
• A retraction in serious cases.

Important limitation

Submitting a correction request does not guarantee that OHUASI will change a page. The controlling question is whether the evidence supports the requested change.

Correction submission summary

The strongest correction requests are precise, sourced, and material. Provide the page, the claim, the proposed fix, and the evidence. OHUASI’s role is to protect reader accuracy, not stakeholder preference.