Compliance & Auditing
QWED-Finance generates cryptographic proof of every verification for regulatory compliance.“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
| Field | Description | Example |
|---|---|---|
receipt_id | Unique identifier | "a1b2c3d4-..." |
timestamp | ISO 8601 UTC | "2026-01-18T14:30:00Z" |
input_hash | SHA-256 of LLM output | "7f83b1657..." |
engine_used | Verification engine | "Z3" |
verified | Pass/fail | true/false |
proof_steps | Symbolic derivation | ["amount=15000", "threshold=10000", "15000>=10000"] |
Cryptographic Signature
Audit Log
Aggregate receipts for regulatory reporting:Query Failed Verifications
Regulatory Alignment
| Regulation | QWED Feature |
|---|---|
| RBI FREE-AI | Audit trail with receipts |
| BSA/FinCEN CTR | AML threshold verification |
| OFAC | Sanctions screening |
| SOC 2 | Immutable verification logs |
| ISO 27001 | Input hashing & signatures |
Adversarial Defense
We test against “jailbroken” LLMs:Test Suites
| Suite | Tests | Coverage |
|---|---|---|
test_sql_jailbreaks.py | 20+ | SQL injection, UNION, comments |
test_math_compliance_jailbreaks.py | 15+ | Float precision, AML boundaries |
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 5 Guards — Deep dive into each verification guard
- Next: UCP Integration — Connect to Universal Commerce Protocol
- See Also: Open Responses Integration — Agentic tool call verification
:::info GitHub Repository Source code and adversarial tests: github.com/QWED-AI/qwed-finance :::