The core problem: you can't trust what you can't prove
An LLM will hand you a confident answer whether or not it is correct, and by default it leaves no durable record of how it got there. When something goes wrong, or when an auditor, regulator, or customer asks you to show your work, you are stuck. Which model version answered? What documents were in the context window? What retrieval results, tool calls, and system prompt shaped the output? Was the log tampered with afterward? If you cannot answer those questions with evidence, you do not have a trustworthy system — you have a plausible one.
"Trust me, the logs say so" is not proof. Application logs can be edited, truncated, or reconstructed after the fact, and they rarely capture the full decision context. In regulated settings that gap is disqualifying. Trust has to be constructed, not asserted — and construction means cryptographic provenance plus measured quality.
The approach: sign, anchor, and independently audit every decision
The design principle is simple to state and hard to fake: production AI whose every decision is signed, anchored, and independently auditable. Every time the system produces an output that matters, it captures the full decision context and commits it to a tamper-evident record that a third party can verify without trusting you at all.
Concretely, an auditable decision record captures:
- Inputs — the user request, the system prompt, and the model/version that ran.
- Context — the exact retrieval results and documents placed in the window, and any tool calls made.
- Output — the answer or action the model produced.
- A cryptographic signature over all of the above, anchored so that any later edit is detectable.
Because the record is signed and anchored, an auditor does not have to take your word for anything. They can recompute the hash, verify the signature, and confirm the record has not changed since it was written. That is the difference between saying a decision was made a certain way and proving it.
The mechanism: a tamper-evident audit trail signed with post-quantum crypto
Hibiscus Consulting builds this as a tamper-evident audit trail signed with post-quantum cryptography. The signatures use ML-DSA (the NIST-standardized Module-Lattice Digital Signature Algorithm), and a provisional patent has been filed on the approach.
Why post-quantum (ML-DSA) matters here
An audit trail is a long-lived asset. A signature you write today may need to hold up years from now, in a dispute or an audit that happens well after the fact. Classical signature schemes are vulnerable to future quantum attacks, which would let an adversary forge a signature and undermine the whole record retroactively. Signing with a lattice-based scheme like ML-DSA means the provenance you establish today stays defensible against tomorrow's cryptanalysis. For records meant to survive an audit horizon, that longevity is the point.
"Tamper-evident" is the operative property. The goal is not to make records impossible to touch — it is to make any touch obvious. If a single byte of a signed decision changes after it was written, verification fails, and everyone can see it failed. The record either verifies clean or it does not; there is no quiet middle ground for a bad actor to hide in.
Pair signing with evaluation: prove quality, don't assume it
Provenance answers "what happened and can you prove it." It does not, on its own, tell you the answer was good. A perfectly signed wrong answer is still a wrong answer. That is why signing has to be paired with an evaluation harness that backtests output against historical ground truth.
Instead of shipping a prompt or model change on a hunch, you replay it against a corpus of past cases where the correct answer is already known, and you measure how often the system gets it right. A "better" prompt becomes a claim you can prove or disprove with numbers, not a vibe. When you change the model, the retrieval strategy, or the instructions, the harness tells you whether quality actually went up — before your users find out the hard way.
A practical order of operations
- Instrument the decision, not just the response. Capture inputs, model/version, retrieval context, and tool calls as a single structured record at the moment the output is produced.
- Sign and anchor each record. Compute a signature over the full record with ML-DSA and anchor it so any later modification breaks verification.
- Build an evaluation harness. Assemble a ground-truth set from historical cases and backtest every model, prompt, or retrieval change against it before it ships.
- Give auditors an independent verifier. Let a third party recompute and check signatures themselves, so trust does not depend on trusting you.
- Gate releases on the evidence. No prompt or model change goes live unless the harness shows quality held or improved, and every production decision lands in the signed trail.
Why this matters for fintech, healthcare, and federal buyers
If you sell AI into regulated markets, "our model is really good" is not an answer your buyer can act on. Their compliance, risk, and legal teams have to be able to show their work under audit — and that means your AI has to produce evidence, not just output.
- Fintech — a decision that touches money, credit, or a customer's account needs a defensible record of the inputs and reasoning behind it, one that holds up when an examiner asks.
- Healthcare — outputs that inform clinical or operational decisions have to be traceable and tamper-evident, because "the system said so" is not a defensible position when it is wrong.
- Federal — provenance, integrity, and independent verifiability are table stakes, and post-quantum signatures line up with where standards are heading.
In all three, the buyer is not asking whether your model is clever. They are asking whether they can defend a decision it made, months later, in front of someone with authority. Signed, auditable AI is how you say yes.
Want AI you can actually prove?
For a signed, auditable AI build — where every decision is captured, cryptographically anchored, and independently verifiable, and where quality is backtested against ground truth — get in touch.
Email blake@hibiscus.buzz