Skip to content

When AI gets it wrong

When your AI writes a report, changes a file, or makes a recommendation, you need to know what happened. AskQP gives you the record — signed, sealed, and stored.

For grants. For journals. For investors. For your own sanity at 2 a.m.

Audit trail

Prove what your AI did.
In court if needed.

Every meaningful AI action is sealed into a tamper-evident, hash-chained record. Reasoning is captured before execution, not after. The audit trail proves itself.

What's in a record

Six sections. Every time.

A logged action is a chat transcript. A sealed record is contemporaneous evidence. The difference matters when someone asks what happened.

Trigger

What started this action? Who or what requested it?

Context

What did the AI know at the time? What files and rules were active?

Reasoning

Why did it choose this approach? What alternatives did it consider?

Authority

Who approved this action? What policy allowed it?

Execution

What tools were called? How long did it take? What resources were used?

Outcome

Did it succeed? What changed? Were there side effects?

Hash-chained

Modify any record. The chain breaks.

Each record carries the SHA3-256 hash of the previous record. To tamper with anything, you'd need to recompute every hash from that point forward and re-sign every record.

Without the signing keys, that's mathematically impossible. With the keys, you'd still leave a fingerprint. Tampering is detectable.

capsule chain
#12846
hasha3f7c2
prev 8d1e4b
#12847
hashb8e1d4
prev a3f7c2
#12848
hashc2a9f6
prev b8e1d4
#12849
hashd5b3e1
prev c2a9f6
Chain verifiedEd25519 + ML-DSA-65

The cryptography

Safe today. Safe tomorrow.

Every record gets dual signatures. If one algorithm is ever broken, the other still protects you. No deprecated crypto, ever.

SHA3-256

FIPS 202

Content hashing for every record. Identifies tampering at the byte level.

Ed25519

FIPS 186-5

Classical digital signatures. The current gold standard for authenticity.

ML-DSA-65

FIPS 204

Post-quantum signatures. Safe against attacks from machines that don't exist yet.

No MD5. No SHA-1. No RSA. No DES. No 3DES. No deprecated algorithm ever appears in the AskQP signature chain.

Three privacy layers

Detail decays. Accountability remains.

Right to erasure works. Layer 3 can be deleted while Layer 1 preserves the audit trail. Designed for GDPR, HIPAA, and financial recordkeeping.

Layer 1

Forever

Summary

Record ID, type, timestamp, status, outcome. Proves something happened.

Layer 2

90 days

Detail

Anonymized reasoning, redacted tool calls. For operational review.

Layer 3

7 days

Full context

Complete reasoning, full prompts. Encrypted at rest. Auto-deleted.

Evidence that proves itself.

The Capsule format is open. The verification runs offline. Auditors, regulators, and your own engineers can confirm any chain without asking us anything.