Evidence Protocol
AEA
Versioned operational evidence artifacts. Schema-specific signing, identity/runtime binding, and independent verification.
Artifact Semantics
Versioned Schema
Each AEA artifact is identified by schema version. Different schema versions may use different signing algorithms, canonicalization methods, and evidence structures.
Identity Binding
Each AEA binds the identity of the producing system, the execution context, and the organizational tenant to the evidence artifact.
Runtime Binding
The execution runtime context — including workload identity, lease, and policy decisions — is bound to the AEA.
Signer & Algorithm
Signer identity and algorithm are specified per schema version. Not all AEAs use the same algorithm — the artifact registry defines the exact algorithm per schema.
Verification
AEA artifacts can be independently verified without trusting the producing service. The verifier checks signature, schema compliance, and evidence chain integrity.
Limitations
A valid AEA proves that the evidence was produced and signed as specified. It does not prove correctness of the underlying action or guarantee absence of errors.