Four questions, and what a record can answer.
Each arrives long after the decision, from someone who was not there.
AI vendors facing a buyer’s security review
“How do we verify what your AI decided in production, and under which policy?”
Decision runs in production
Signed before it runs
Security review, per buyer
Checked later
With Seal
Each decision, refused or approved, returns a signed record naming the policy that applied. One pack serves every buyer.
A reviewer can establish
- Which policy version was in force
- What was decided, refusals included
- That the record is unaltered, checked without an account
Not established
- That the decision was correct
- That every decision in the period was recorded
Break a receipt yourself, 30 seconds →Financial services
“Why was this application declined on the fourteenth of March?”
Application declined
Signed before it runs
Regulator, auditor or solicitor
Checked later
With Seal
Your policy runs before the model call, the decision is signed as it is made, and the pack joins the existing model-risk file.
A reviewer can establish
- The decision, the policy applied and the moment
- Per-decision evidence behind AI entries in a DORA Article 28(3) Register of Information
- A chained export, so any insertion, deletion or edit shows
Not established
- That the underwriting judgement was sound
- That the applicant was treated fairly
Walk the full stack, seven steps →Insurance
“Did each of these decisions clear under the policy that was in force when it ran?”
Claims and underwriting calls
Signed before it runs
Chief risk officer signs off
Checked later
With Seal
The approved policy is the one that executes, and each decision carries its version. The reviewer’s question is fixed before the evidence is opened.
A reviewer can establish
- Which rule applied to each decision in scope
- That refusals were recorded as well as approvals
- A named reviewer’s verdict, signed with a credential Aqta did not issue
Not established
- That the pricing or claims judgement was right
- That the model is free of bias
The reviewer’s screen →Healthcare
“What exactly did it decide, and can we show it?”
Clinical flag raised
Signed before it runs
Clinical governance asks
Checked later
With Seal
PHI is masked upstream, and routes that need a human decision wait for one. The record names who cleared what.
A reviewer can establish
- The model, policy, verdict and time
- That a clinician signed off where sign-off was required
- That the record holds a fingerprint of the prompt, not the note
Not established
- That the clinical decision was correct
- Any certification. Aqta issues records, not approvals
The limits are published on purpose.
A signature proves a record was not altered, not that the computation ran as described or that no decision was omitted.
For engineers: read the open ATTESTATION-v1 spec