Forensics
Every QUORUM decision leaves a record that is written before the verdict is released and sealed into a signed, hash-chained ledger. Investigators and examiners can confirm what was decided, why, and that the record has not changed.
Decision Record
Verdict, score, fired rules, reference, time and a digest of the inputs. Raw inputs stay in the institution's own systems.
Decision Proof
Merkle path from the record to a ledger entry signed with Ed25519 and ML-DSA-65, optionally timestamped under RFC 3161.
Counterfactual Certificate
Signed, per block: what each fired rule contributed and the smallest change that would have altered the verdict.
Evidence Packages
PDF evidence packages for a case, generated on request in deployments with the forensics feature enabled.
AI Case Findings
Asynchronous AI tier verdicts with keyed HMAC integrity receipts — evidence for the analyst, not the decision itself.
Score Proofs
Bulletproofs zero-knowledge proof that a score was within policy bounds, for sharing without disclosing the score.
Evidentiary Integrity
The audit ledger is tamper-evident: any change to an anchored entry breaks a hash link or a signature, and a scheduled scan alerts on it. Verification needs only the public keys and standard algorithms, not access to QUORUM.
It is not immutable — the ledger is stored in PostgreSQL. Institutions should restrict write access and archive anchored roots and timestamp tokens outside the database. Whether this evidence meets a given legal or regulatory standard is for the institution and its counsel to assess.