A portable record of what the governed execution actually became.
EEE is the execution-evidence artifact, not an authorization token. CAPPO builds a signed envelope only after the authority path has done its job, binding the execution, authority context, policy decision, commitments, observed effects and verification material into one portable record.
EEE-Core v0.1.0 is implemented in CAPPO with RFC 8785 canonicalization, SHA-256/SHA-384 envelope roots, Ed25519 issuer signatures and an offline verifier that returns VALID, VALID_WITH_UNRESOLVED_REFS, INVALID or UNSUPPORTED_VERSION.
Power stays narrow on purpose.
The surface should tell you where the truth comes from.
Veklom does not promote a configured URL or a code path into a runtime claim. Interfaces are shown so operators can verify the actual boundary themselves.
EEE is still part of Veklom and it is implemented. Its job is narrower than the old marketing page implied: carry signed evidence about an already-governed execution without pretending the evidence artifact itself granted the authority.
