Every governed action produces an Ardyn Evidence Artifact (AEA) — a signed, chain-recorded, and independently verifiable cryptographic record. No trust in Ardyn required to verify.
{
"aea_id": "b63dad6f-358f-...",
"artifact_type": "AEA",
"artifact_id": "b63dad6f-358f-...",
"signatures_valid": true,
"chain_valid": true,
"policy_valid": true,
"ddc_type": "tier_b",
"entry_hash": "5c1652...",
"ddc_payload": {
"kind": "governed_tool_decision",
"governance_decision": "ALLOW",
"tool_name": "safe_read",
"issuer_signature": "0ba02a...",
"issuer_public_key": "80bac1..."
}
}
The Ardyn issuer signs the AEA. The Hermes principal signs authorization decisions. The verifier confirms independently — no single key does everything.
Every signed operational artifact produced by the platform is an AEA. The kind reflects what was verified.
Anyone can verify any AEA. Use POST /v1/verify/artifact with the AEA ID to get full verification status: artifact type, signature validity, chain validity, and policy validity — all independently re-derivable.
AEAs can be verified without any Ardyn servers. The ardyn-verify tool re-derives entry hashes, verifies signatures against pinned keys, and validates chain integrity — all from the artifact bytes alone. Zero network calls.
Any modification to the AEA or its evidence is mathematically detectable. The hash chain ensures integrity from genesis to the latest entry.
No trust in Ardyn required. AEAs can be verified offline using the entry hash, chain linkage, and pinned issuer keys — all carried in the artifact.
Every AEA carries every byte needed for re-derivation — no external fetches, no whispered trust. Hardware AEAs embed their certificate chain in the artifact.
Use the public verification endpoint to inspect any AEA, or contact the Ardyn team to deploy evidence-backed verification inside your enterprise environment.