Developer / pilot maturity

The AI era will be governed by what can be proven.

Policy-aware coordination, portable evidence and public intelligence — so institutions can inspect what was evaluated, refused and unproven.

Today: offline verification, refusal receipts and ZambiaMacro. Next: governed data custody, storage, compute and locally operated edge capacity — staged behind verified demand.

Open ZambiaMacro Explore verification

Illustration: how a receipt is produced. In the developer / pilot system, decisions — including refusals and not_proven outcomes — are recorded as signed receipts for offline inspection. What verification can prove

Institutional collaboration

NISIR and CopperCloud sign Letter of Intent

CopperCloud and Zambia’s National Institute for Scientific and Industrial Research have signed a Letter of Intent and NDA covering sovereign compute infrastructure, research digitisation, joint digital systems development and capacity building. A bounded first pilot is to be defined, with scientific review of the developing Zambia Energy Stress Engine proposed as the initial focus.

Read the joint announcement

What is CopperCloud?

A neutral coordination and evidence rail for governed work today, designed to grow with the data custody, storage, compute and edge infrastructure that real institutional systems require. Policy evaluation, signed receipts and explicit not_proven boundaries keep each step inspectable.

Governed computation

Workloads are classified against policy packs. The system can route or refuse. Decisions leave a signed evidence trail a counterparty can inspect offline.

Maturity: developer / pilot

Portable evidence

The first surface presented for external evaluation is the verifier and refusal receipt — not a compute-platform sale. Ambiguity stays visible instead of collapsing into a false “valid” stamp.

Maturity: offline verifier v0

Public intelligence

ZambiaMacro is the live public research surface today. Selected artifacts can carry cryptographic integrity evidence. Broader national energy-stress forecasting (ZESE) is under development.

Live product: ZambiaMacro

Proof ledger

What works today, and what is not yet proven

Current, checkable capabilities — labelled by maturity, not ambition. Explicit truth boundaries sit in the same ledger. CopperCloud is not a standards authority, government body, production cloud, data-centre operator, or proven national compute exchange.

Live public and running
Pilot developer / pilot maturity
Not proven explicit limit today

Capability

Status

What that means

ZambiaMacro public research surface

Live

Public hydrology-led Power Stress Index. Visit zambiamacro.ai.

Policy evaluation & refusal

Pilot

Developer/pilot-grade orchestration can evaluate policy packs and refuse work that fails declared constraints.

Signed evidence / receipts

Pilot

Signed receipt artifacts record orchestration decisions for offline inspection. Trust tier and canonical status remain distinct.

Offline verification

Pilot

Selected artifacts can be verified offline. Outcomes may be valid with warnings; many properties stay not_proven.

Cryptographic integrity evidence

Pilot

Selected public artifacts can carry cryptographic integrity evidence. External-work attestation does not prove CopperCloud node execution.

Current limits

No institutional-grade authority

Not proven

Sandbox and pilot receipts are not procurement-grade compliance proof.

No hardware attestation claim

Not proven

Offline verification does not confirm TPM/Nitro/TEE execution unless a verified attestation document is present and checked.

No independent node-location proof

Not proven

Jurisdiction intent in policy is not the same as verified physical geography.

No national forecast track record yet

Not proven

ZESE is under development. Public Forecast-class claims wait on scored, contract-bound outputs.

NISIR has not validated the engine

Not proven

A Letter of Intent establishes collaboration intent. Scientific review of the developing Zambia Energy Stress Engine is proposed as a first pilot focus — not completed validation, certification, or endorsement.

External-work attestation ≠ CopperCloud node execution

Not proven

Attesting an external artifact does not prove the work ran on a CopperCloud node.

Zambia's AI moment

“Technology must serve the people, and not the reverse.”

President Hakainde Hichilema, address at the official opening of the First Session of the Fourteenth National Assembly, 9 October 2026. Official text, National Assembly of Zambia.

A standard like that needs evidence.

The same address set out what AI in Zambia's public services must be: transparent, accountable and free from bias, on stronger data infrastructure. A standard only holds if a counterparty can check it. Making that evidence portable and verifiable, offline and with an honest not_proven, is the work CopperCloud does.

Accountability Receipts record what was evaluated, refused and left unproven.
Data infrastructure Governed custody, storage and compute, staged behind verified demand.
Energy ZambiaMacro tracks the power stress an AI-ready economy runs on.

Quoted from the public record. CopperCloud holds no government mandate, partnership or procurement, and is not part of any national programme.

What a visitor can inspect

Public artifacts and requestable diligence materials — without private evidence dumps.

ZambiaMacro

The live public research surface. Start there for current outputs and product context.

Visit ZambiaMacro

Verification boundaries

What the offline verifier can and cannot confirm, including signed vs registry-verified vs institutionally authorised evidence.

Read verification page

Claims discipline

Public summary of trust tiers, canonical status, and universal anti-claims.

Open claims discipline

Selected ZambiaMacro attestation artifacts have been verified offline with warnings (signature and survivability checks; institutional claim not permitted on those artifacts). Qualified counterparties may request the current verification packet — see the verification page. Private receipts, key registries, and NDA materials are not published here.

Direction of travel

The verifier is the trust wedge, not the limit of the company. Expansion is sequenced from real institutional needs and labelled by maturity.

Concept render C0: a dark 40-foot high-cube container carrying the CopperCloud mark, doors open onto a lit interior, on a concrete pad at dusk. The caption burned into the image reads: Concept C0, ISO 40-ft high-cube shell, internal layout illustrative, not reviewed. — Concept C0 concept render of a containerised edge node. Not a built facility, not a site and not a reviewed design; the internal layout is illustrative. Shown as direction, not capability.

Demand edge

Institutional systems and data

As organizations digitise real operations, they need durable data custody, storage, hardware and compute choices designed around their authority and constraints. CopperCloud is intended to help architect that path; current public proof remains bounded.

Status: design and pilot context

Developer / pilot

Policy-aware compute and storage

CopperCloud's orchestration software can evaluate declared workloads, route or refuse jobs and produce evidence. Developer components for node selection, storage policy and replication point toward harder institutional infrastructure; they are not a hardened public utility.

Status: developer components / hardening ahead

Longer horizon

Locally operated edge capacity

Over time, verified institutions, operators and local builders could contribute eligible compute and storage through interoperable edge nodes — creating a path from underused capacity to more capable, locally owned infrastructure.

Status: architectural direction / not a live network

Near-term work remains the Zambia Energy Stress Engine, stronger institutional verification pathways and pilot-level sovereign compute. Open participation, marketplace economics, field reliability and independent node verification remain to be proven.