What happens when you certify a filing?
- Resolve — every cited authority is matched against live case-law for existence; quoted passages are matched against the published opinion; good-law standing is overlaid from your firm’s citator.
- Verdict — each citation is marked clean, flagged (fabricated, misquoted, or bad law), or incomplete, with the coverage of the check recorded honestly.
- Sign — the certification is signed with composite post-quantum signatures (ML-DSA + SLH-DSA, NIST FIPS 204/205).
- Seal — the result is appended to an RFC 6962 Merkle transparency log, making any later alteration detectable.
- Verify — anyone with the receipt can independently check the inclusion proof; no trust in RankShield required.
How is privilege handled along the way?
Privileged material takes a parallel path: it is withheld, redacted, tokenized, or processed only on a local model — never transmitted to a third-party AI in retrievable form — and the attestation binding that interaction to the approved tool, the policy, and the client’s informed consent is signed and sealed the same way. Notably, the certification itself stores digests, not content: your filing’s substance never enters the log.
Why the transparency log matters
A record you keep in your own database is a claim — it can be edited, and a skeptic must trust you. An append-only Merkle log is evidence: each entry is hash-chained, so deleting or editing the past breaks the chain visibly, and third parties can verify inclusion without access to our systems or yours. This is the same transparency-log construction (RFC 6962) the web’s certificate infrastructure relies on, applied to legal AI accountability.
