Real Seal evidence packs are generated from live gateway traffic for a specific tenant, refreshed continuously, signed at the chain head, and accessible only to that tenant. Your version of this page lives at /compliance/certificate after sign-in.
Sample evidence pack
Seal · signed evidence from live gateway traffic. Updated continuously.
Acme Industries (sample)
6 April 2026 to 6 May 2026
This view maps verifiable Seal evidence to defined evidence requirements for this scope. It is not a compliance score and not a finding of conformity: it does not assess legal compliance, safety, model correctness, or the completeness of unobserved activity.
Generated 6 May 2026. Next automatic review 6 June 2026.
Chain hash: a7d4f1c3e9b2a5d8…e7b0a3d6
The chain, stage by stage
Every count below opens the artefact behind it. This is the object a reviewer walks, not a score.
Seal coverage
Two articles where Seal is the load-bearing control. Receipts are signed at runtime and verifiable offline against the published key.
Deployer obligations, Seal evidence supports
These articles are obligations on the deployer of the high-risk AI system, not on Seal. The receipt evidence below supports the deployer’s readiness work; Seal is not a substitute for deployer accountability.
Verify a receipt yourself
The check runs entirely in your browser, against Aqta's published key. Nothing is sent to us. If Aqta disappeared, this would still work.
Prefer your own tools? The identical check is pip install aqta-verify-receipt or npm i aqta-verify-receipt. This widget is a faithful port of that package.
Generate yours from your own gateway traffic.
Real evidence reports are generated from your own gateway traffic. Every inference goes through Seal and your report refreshes continuously, each entry carrying a receipt you can verify the way you just did above.