Court-evidence record system
CourtChain™ the evidence record behind every sealed bundle.
CourtChain is the append-only evidence record for sealed CREB, AREB, PIEB and RREB packages. Each entry binds a content hash to the hash of the entry before it, carries hybrid Ed25519 + ML-DSA-65 signatures and RFC 3161 time, and is written to object storage in the customer or engagement bucket.
Evidence Brief · CourtChain
Append-only record. Hybrid post-quantum signatures. FRE 902 posture.
Sealed Determination Proof Records and CREB/AREB/PIEB/RREB covers hash-anchor here: customer bucket, AES-256-GCM, Object Lock recommended. Hybrid Ed25519 + ML-DSA-65.
Anyone holding a package's public CourtChain link can re-check record integrity and confirm that a court filing matches its entry by hash, without decrypting the bundle.
Record
Append-only
Cryptography
Post-Quantum
Custody
Customer bucket
Writes
Write-limited
Section 01 · The thesisWhy a purpose-built evidence record
Evidence that legal and procurement can approve.
Evidence has to be immutable, integrity-checked, and held in a custody model the customer controls. CourtChain delivers that on object storage, so counsel and procurement can approve custody without taking a dependency on any public network or third-party consensus.
Post-quantum by default
Hybrid signing that survives the quantum transition
Every record carries both a classical Ed25519 signature and a lattice-based ML-DSA-65 (Dilithium) signature. Both must verify. A harvest-now-decrypt-later adversary gains nothing.
Customer custody
Your bucket, write-limited access
CourtChain lives in an S3 bucket or dedicated prefix, in the customer's own account when required. The JIL CourtChain service is the only principal that may append, using least-privilege credentials with no delete. Authorized customer and auditor roles keep read access for verification.
Purpose-built record
A court-evidence schema, not a general-purpose platform
Each entry records the bundle type (CREB, AREB, RREB or PIEB), a SHA-256 content hash, the prior entry's hash, and an entry hash that binds them to the subject. Deterministic, append-only, and no general-purpose attack surface.
Evidentiary record
Output that authenticates itself
A sealed record is a Court Ready Evidence Bundle: hash-anchored, signed, independently verifiable at a public endpoint, and built to support self-authentication under Federal Rule of Evidence 902(14). Admissibility remains the court's decision.
Section 02 · The recordFour parts, one evidence record
How CourtChain is built.
Entries
Each entry carries its bundle type, the package content or a sealed payload reference, the SHA-256 hash of that content, and the prior entry's hash. Altering any earlier entry breaks every hash after it.
Storage and retention
Object storage in the customer or engagement bucket, under a dedicated prefix. S3 Object Lock in compliance mode is recommended for WORM retention aligned to CMS audit look-back, and the location is snapshotted and backed up on a schedule that meets engagement retention.
Encryption and public link
The full bundle is stored as AES-256-GCM ciphertext, and the decryption key is never published with it. Each package embeds a public CourtChain link where anyone can re-check record integrity and prove a filing matches its entry by hash, without decrypting the body.
Bundle integration
CREB, AREB, PIEB and RREB packages append to CourtChain after they are drafted or sealed. A failed write is never reported as court-ready custody in a customer report.
CourtChain is the evidence record under every bundle the platform seals. If you are evaluating JIL as a fraud, waste, and abuse detection platform, start at the Platform.
Section 03 · The audienceWho relies on this
Built for the people who have to defend the evidence.
Counsel and litigation teams
Court-ready by design
Sealed bundles carry hash anchors, hybrid signatures and RFC 3161 time, so a filing can be matched to its CourtChain entry and re-checked at the public endpoint.
Security and procurement
Custody you can approve
Customer-owned buckets, write-limited JIL credentials with no delete, read access for auditors, and recommended Object Lock retention. No dependency on a public network.
Payers, providers and investigators
One record across the bundles
CREB for court and enforcement referral, AREB for provider audit readiness, PIEB for payer integrity, and RREB for risk adjustment and recovery. Each one anchors to the same evidence record.
Section 04 · The depthDocs, patents, knowledge base
Everything under the hood, documented.
CourtChain is documented end to end: the record format, the storage and access requirements, the evidence bundle covers, the patent portfolio, and a technical knowledge base.
Specifications
Technical specifications
The CourtChain record format, storage requirements, verification endpoints, and how each evidence bundle anchors to it.
CourtChain technical spec
CourtChain field guide
Evidence bundle covers
Evidence bundles and FRE 902 →
Patents and bundles
The patent portfolio and the bundle family
Filed claims behind self-authenticating evidence and post-quantum signing, all provisional and patent pending, plus how the four evidence bundles compare.
The 177-claim patent portfolio (filed)
CREB, AREB, PIEB and RREB compared →
Knowledge base
The evidence knowledge base
A searchable library across payment integrity, court-ready evidence, cryptography and verification, for the analysts and counsel who go deep.