Article I · Verifiable Architecture
The Transparency Log
Every ledger entry is a leaf in an RFC 6962 Merkle tree. We sign the root and publish it. If we ever rewrote history, we would have to sign two contradictory roots under the same key — and you would hold both.
Bitcoin anchors (live)
reading the chain…
Tree size
—
Key id
—
Origin
sovereign-ai.services/ledger
Signature
Ed25519
Current
Signed checkpoint
Reading the tree…
Prove it yourself
Inclusion proof
Give a receipt id. You get the leaf hash, the sibling path and the signed root. Recompute upward; if it matches, that receipt is in this exact tree.
A transparency log proves what was recorded and that the record has not been reordered or removed. It does not prove that any sealed statement is true. Integrity proven. Truth not verified.
Machine surface
Fetch it without us
Every endpoint is public, unauthenticated and signed with the seal of state.
Signed checkpoint (JSON)
curl https://sovereign-ai.services/api/public/v1/checkpoint
C2SP tlog-checkpoint (text)
curl 'https://sovereign-ai.services/api/public/v1/checkpoint?format=text'
Inclusion proof
curl https://sovereign-ai.services/api/public/v1/proof/{receipt_id}Nation public key (JWKS)
curl https://sovereign-ai.services/api/public/v1/jwks.json