- What is verifiable execution provenance? Verifiable execution provenance is a portable, third-party-verifiable record of what an agent did, in what order, and under what authority. A definition, and where it sits among C2PA, MCP, A2A, and agent identity.
- What makes an implementation Provetrail-conformant? An implementation is Provetrail-conformant if it accepts every valid record in the published vector suite and rejects every tampered or malformed one. Conformance is defined by the vectors, not by who wrote the code.
- Signed vs proven: what a runtime record can and can't prove A signature proves who emitted a record and that it was not altered afterward. It does not, on its own, prove the work behind it was real. Where the line falls, and the frontier we are building toward.
- How third-party verification works You verify a Provetrail record by rehashing its events into a Merkle root, checking the signature on that root against a published key, and confirming each outcome is bound to committed evidence. All of it runs client-side, in any language, against public conformance vectors.