Signed
A receipt carries a cryptographic signature. Verification may succeed using an embedded key, with survivability warnings if no independent registry is supplied.
Offline verifier v0 · Pilot / diligence surface
What verification can prove
CopperCloud’s offline verifier checks signed receipt artifacts without requiring CopperCloud to be online. It reports what passed, what failed, and what remains explicitly unproven. It does not issue institutional endorsement.
What the verifier can confirm
- Orchestrator signature validity against the supplied or embedded verification material
- Canonical signed-payload semantics for supported receipt types
- Binding-envelope consistency where the receipt version requires it
- Verifier claim rows and claims-discipline interpretation (including
not_proven) - Whether a key registry was supplied and whether it was applied to signature trust
What the verifier cannot confirm
- Runtime network egress validation or packet-level enforcement
- Real-world node location or hardware attestation
- PHI absence, regulatory compliance, or workload correctness
- Full custody-chain reconstruction across storage, retrieval, egress, and deletion
- That external-work attestation proves CopperCloud node execution — it does not
Evidence strength ladder
These are different claims. Do not collapse them.
Registry-verified
Signature checks use a supplied public-key registry snapshot. Stronger diligence posture than embedded-key-only — still not institutional authorisation by itself.
Institutionally authorised
Requires canonical policy-pack authority and an authorised trust tier under claims discipline. Sandbox and many pilot receipts explicitly do not permit institutional claims.
ZambiaMacro verification note
Selected ZambiaMacro daily-inference attestation artifacts have been verified offline with warnings. Example outcome class: VALID WITH WARNINGS — core signature checks can pass while survivability gaps remain open (for example: missing Proof Profile reference, non-archival audit snapshots, no hardware-rooted attestation, and the standing rule that external-work attestation does not prove CopperCloud node execution). Institutional claim permitted: no on those verified examples.
This page does not publish private receipts, key registries, NDA material, or internal evidence bundles. Public product context lives at zambiamacro.ai.
Request a verification packet
Qualified counterparties (institutional diligence, scientific review scoping, or security review) may request the current verification packet: receipt identifiers in scope, verifier command shape, expected warning classes, and claims-discipline framing.
Request packet — hello@coppercloud.ai