​
Execution evidence

Every runtime job produces an execution evidence bundle — a structured record of what ran, where, and what came back — attached to the job as the artifact execution_evidence.json.

​
Sealed vs. signed — two different guarantees

These words are not interchangeable, and the bundle says explicitly which one you are holding:
  • Sealed — the bundle’s items are hashed into a SHA-256 Merkle structure computed in-process at execution time. The seal proves integrity: if any byte of the sealed content changes, the digest no longer matches. It cannot prove origin — whoever controls the content could recompute a hash over it.
  • Signed — a signature over the sealed digest produced by the Trust Plane with a key this execution process never holds. That is what proves origin.
The bundle’s trust section (attached outside the sealed payload, because it did not exist when the digest was computed) carries one of two statuses:
Current production status: bundles are sealed_unsigned. The Trust Plane signing service is not yet enabled in production, and QCOS never fabricates a signature-shaped object: a trust failure degrades the status, it never invents an envelope. When signing is enabled, origin_attribution distinguishes trust_chain (verifiable to a published root) from key_only.

​
Verify a bundle offline

The verifier is open source and installable by anyone — verification does not require trusting SoftQuantus infrastructure:
It checks, in order:
  1. Structure — the bundle parses and every required section is present.
  2. Item integrity — each item’s SHA-256 over its canonical JSON matches.
  3. Seal — the Merkle root recomputed from the items equals the recorded sealed_bundle_digest.
  4. Signature — only when you supply a public key, and only for bundles whose status is signed.
A bundle that passes 1–3 is intact; whether you trust its origin is a decision the trust section makes explicit instead of hiding.

​
What is inside the sealed payload

  • Job identity, backend identity and provider routing decision
  • Circuit fingerprint and execution parameters (shots, mitigation, QEC config)
  • Provider response metadata and result digests
  • Timing and technical metering (cost_basis: provider_technical_cost)
Credentials never enter a bundle: token-, secret- and authorization-shaped values are redacted before anything is persisted, including inside free-text provider error messages.
  • POST /api/v1/evidence/verify and GET /api/v1/public-key — anonymous portal endpoints for evidence verification.
  • Glass-Box — compilation evidence with audit trails.
  • Bench — benchmark reports with verifiable bundles.
  • QuantumLock evidence — the licensing product’s own evidence authority with a Merkle transparency log and real ML-DSA signatures.