Verify signed evidence

Obtain the run's evidence bundle through authorized owner orchestration. It contains ordered, hash-chained records covering tasks, grants, proposals, decisions, permits, transactions, receipts, lifecycle events, and verification. It also records attempt starts, executor outcomes, provider refusals, classified stops, and owner recovery actions. Private provider continuation is excluded.

Obtain the signer's public key through an independently trusted channel from your integration operator. A key embedded in the evidence bundle cannot establish its own trust.

Validate the bundle envelope, individual record hashes and Ed25519 signatures, and the ordering and links in the record chain. Reject modified records, broken chains, modified envelopes, and substituted keys. Keep the original bundle intact for review.

Signatures establish record integrity. They do not establish current permission, prove a model's explanation, or prove that a remote order exists. Execution rechecks live authority and state; hosted order completion requires hosted receipt evidence.

Match the run, attempt, observation, action, and transaction references before attributing a receipt to a proposal. Distinguish a pre-dispatch stop from an uncertain external outcome. Local authorization records alone do not prove that a remote effect committed.

Use the evaluation guide to distinguish decision quality, runtime enforcement, and missing evidence. A valid signature is not a quality score, and a scripted replay is not a measurement of live model behavior.