“If an AI makes a mistake, the algorithm isn’t sued—the bank is. Yourinput_hashandsignatureprovide Non-Repudiation.”
Verification receipts
Every verification generates a tamper-proof receipt:Receipt fields
Cryptographic signature
Audit log
Aggregate receipts for regulatory reporting:Query failed verifications
Regulatory alignment
Adversarial defense
We test against “jailbroken” LLMs:Test suites
For compliance officers
When a regulator asks: “How do you verify AI decisions?” Show them:- Input Hash — Proof of what the LLM said
- Timestamp — When verification occurred
- Engine Signature — Which solver verified (Z3/SymPy)
- Proof Steps — Symbolic derivation of truth
- Receipt Signature — Tamper-proof integrity
Related pages
- Previous: The 10 Guards — Deep dive into each verification guard
- Next: QWED UCP: transaction verification for AI commerce — Connect finance verification to AI-driven commerce flows
- See Also: QWED Open Responses: verified tool calls for AI agents — Add runtime verification to agent tool calls
:::info GitHub Repository Source code and adversarial tests: github.com/QWED-AI/qwed-finance :::