signatures array (one Ed25519 entry and one
ML-DSA-65 entry, dilithium3) is verified over the message for its schema
version. Version 3 (whole-record) covers every top-level field except the
signatures, the schema version, verifications and receipts. Verifying
ML-DSA-65 needs cryptography 47.0.0 or later.
verify_execution_trust_record_offline
trust_record is a plain dict, exactly as json.load() would
produce from a Trust Record JSON file or API response body, or the
ExecutionTrustRecord that client.trust_record() returns.
public_keys maps keyId -> PEM-encoded public key text.
Schema version 3 only (decision D24): the signatures array covers the
whole record. A record with one valid entry is accepted, unless it was
created at or after hybrid_required_from (ADR-0016), where both hybrid
entries are required.
verify_execution_intent_offline
intent is a plain dict, exactly as json.load() would produce from the
intent field of GET /execution-intents/:id, or the ExecutionIntent at
client.execution_intent(id).intent. public_keys maps keyId to
PEM-encoded public key text.
A valid result proves the intent was signed by the holder of that key and
has not been altered. It does NOT prove the action was released, or what its
result was: an intent is written BEFORE release.