Community Protection & Advocacy

Our Position

The Community Protection programme is a framework for tracking how corridor decisions affect local communities and for routing readers toward recognized standards, source-backed records, and practical accountability pathways. The site should distinguish clearly between verified facts, policy positions, and future programme capabilities.

Legal Support Network

Legal-support pathways are a staged capability, not a live referral service. The current public surface should point readers toward recognized standards, rights explainers, and public records under the Mining Code, IFC Performance Standards, and applicable frameworks. Any named partnership or case support requires a source record and permission to publish.

Community Benefit Agreements

CBAs are treated as an important corridor governance tool. The site will maintain explainers, source packs, and template references for community benefit agreements where reliable public material is available. Any claim that a specific CBA has been facilitated, verified, or breached requires a dedicated source record.

Community Verification Records

Who legitimately represents affected communities? The planned verification layer will document public community-organization records, governance documents, and engagement history where available. It does not certify representation until an assessment process and source pack have been published.

Displacement Response

Displacement records should be handled through a staged protocol: public-record capture, standards mapping, source confidence assessment, right-of-reply where adverse claims are made, and long-term tracking of compensation and livelihood-restoration claims where reliable data exists.

Fair Investment Advocacy

African resources for African benefit. Local jobs, not imported labour. Local ownership, not 100% foreign control. Revenue sharing, not pure extraction. We do not oppose investment — we demand it be fair.

Implementation Approach

Implementation begins with source mapping, standards explainers, and public-record tracking. Direct field documentation and community reporting should remain staged until source-protection controls, consent protocols, and legal review workflows are complete.

Documentation is organized through source packs with clear provenance, confidence levels, and update dates. Sensitive records should not be described as verified unless the verification basis is public or independently auditable.

Impact and Outcomes

Programme success is measured through the quality of source records, clarity of standards analysis, correction speed, and usefulness to communities, investors, journalists, and policymakers.

Programme activities will generate explainers, source packs, review files, and policy notes. Community voice material remains queued for verification unless a supporting source pack is attached.

Community Partnership Model

The proposed partnership model treats affected populations as stakeholders in the evidence process, not as objects of analysis. Community-organization records, representation claims, and testimony should be reviewed through consent, source-protection, and verification protocols before they are described as partnership outputs.

Information sharing should be designed around accessibility, language, source safety, and disclosure boundaries. Monitoring findings, analysis, and research products should not be represented as community-validated unless the validation process is documented.

Sustainability of community engagement is a design principle, not a claim of current coverage. Programme activities should build public records, local capacity, and accountability mechanisms only where the supporting partnerships, permissions, and safeguards are in place.