EpochCore Sovereignty Loop

Discover → Seal → Write-back → Pull → Verify offline — proven against a live IBM COS bucket.

dataplane · standby

Sovereign Dataplane

object store × PQC signer × WORM ledger — keys and bytes stay in-region

region us-south · RAS 40668c787c463ca5

IBM Cloud Object Storages3.us-south…appdomain.cloud

PQC signer · FIPS-204/205ml-dsa-87 · slh-dsa-128f

WORM provenance ledgerappend-only · 7-year

Offline verifierno egress required

Bucket

epochcore-sovereign-demo

Endpoint

s3.us-south.cloud-object-storage.appdomain.cloud

Operation

ListObjectsV2 → seal → PUT sidecar

Originals

never mutated — sidecar only

Signatures

Ed25519 · ML-DSA-87 · SLH-DSA-128f

Verify

offline · network severed

5 stages · ~12s · real crypto in your browser

Sovereignty receipt View WORM ledger →

Runs entirely in your browser — object bytes and signing keys never leave the region; only the manifest hash is anchored.
The offline verifier severs the network and probes example.com to prove no egress is needed — 3/3 signatures still validate.