Specification - v1.0 - 2026-04-22
Court-Ready Evidence Bundle (CREB)
A Court-Ready Evidence Bundle - CREB - is the canonical artifact produced by every JIL Sovereign verdict. One layout. One cryptographic seal. Independently verifiable without JIL's cooperation. This is the authoritative public specification.
Scope
A CREB is emitted for every decision JIL makes across all five product pillars (Pre-Settlement Attestation, Retroactive Verification, Asset Intelligence, Wallet Intelligence, Pre-Clearance) and every productized surface (Sovereign Stack, CourtChain, Regulator Attestation Network, Proof-of-Compliance Settlement, Time-Bound Sealed Escrow, Secure Data Vault). The layout is the same in all cases - only the subject, test profile, and data sources vary.
This specification is the canonical reference for external counsel, regulators, auditors, and system integrators. When a JIL-produced artifact is cited in evidence, pleadings, or audit response, the recipient may refer to this page for the layout, signing algorithm, retention policy, and verification path.
Canonical Layout
Every CREB contains exactly these eight sections, in this order:
| Section | Name | Contents |
|---|---|---|
| § 0 | Identifiers & Retention | report_id, creb_id, attestation_id, vendor_id, profile_id, date_completed, SHA-256 content hash, storage location (vendor-controlled SDV), retention period (15+ years minimum), retrieval index (trust.verdict_records in PostgreSQL, replicated to ClickHouse), retrieval API, retrieval SLA (under 2s hot, under 48h cold, under 24h regulator). |
| § 1 | Subject of Verdict | Request type (pre-settlement, retroactive, wallet, asset-intelligence, pre-clearance), counterparty, asset, origin/destination wallet, chain, purpose code, latency budget. |
| § 2 | Test Profile Applied | Profile name + version, compliance-officer sign-off, list of the 111 checks actually run within 15 signal categories, jurisdictions enforced. |
| § 3 | Vendor-Approved Data Sources | Every data source used, each with an attestation certificate ID, last refresh, update cadence. Includes OFAC SDN + CSL, EU, UK OFSI, UN, Swiss SECO, Chainalysis (when subscribed), OpenSanctions / Yente, OpenCorporates, GLEIF, JIL Wallet Intelligence Engine, JIL L1. |
| § 4 | Test-by-Test Result Matrix | Each of the 111 checks with check ID, name, method, source, result, evidence SHA-256 hash. Individual signatures rolled up into a Merkle root. Failing or unavailable checks appear here with explicit status codes - never silently omitted. |
| § 5 | Final Verdict | YES / NO / REVIEW + confidence score + structured reason codes. REVIEW is a first-class outcome: it records exactly which signals triggered it. |
| § 6 | Cryptographic Seal & Anchor | Ed25519 + Dilithium-III hybrid signature, 14-of-20 BFT validator quorum across 10 jurisdictions, JIL L1 block height + tx hash, Merkle root, QR verification code linking to the public /verify endpoint. |
| § 7 | Chain of Custody Timeline | Microsecond-precision event log from custodian request through sealed delivery and SDV write. Every state transition recorded, hash-chained back to the prior event. |
| § 8 | Authorized Evidentiary Uses | Federal Rules of Evidence 702 (expert testimony foundation) and 901 (authentication), OFAC blocked-transaction reporting, FinCEN SAR / CTR attachment, SEC investigative responses, SOC 2 / ISO 27001 / NYDFS Part 500 / HITRUST CSF audit evidence, Bank Secrecy Act recordkeeping. |
Cryptographic Seal
Every CREB carries a hybrid signature:
- Classical:
Ed25519(RFC 8032) - validates against 10+ years of cryptographic practice, widely accepted by existing PKI. - Post-quantum:
ML-DSA-65(NIST FIPS 204, formerly CRYSTALS-Dilithium-III) - records produced today remain cryptographically valid through Q-Day and beyond the 15-year retention horizon. - Consensus: 14-of-20 BFT validator quorum (70% threshold) across 10 jurisdictions. No single validator, operator, or cloud region can produce a valid CREB alone.
- Anchor: Merkle root of section § 0 through § 7 is written to JIL Layer-1 in a dedicated verdict block. The block height + tx hash are recorded in § 6 and are sufficient to locate the anchor on any JIL L1 replica.
A CREB is tamper-evident, not tamper-proof. Any modification to any byte of the artifact invalidates the seal on verification. The evidentiary property we need is that tampering is detectable - not that it is prevented.
Verification
A CREB can be verified by anyone, without JIL's cooperation, using only the artifact + the public JIL L1 anchor chain:
- HTML: jilsovereign.com/verify - paste a
report_idorcreb_id, get a signed verification report. FRE 702 / 901 foundation included in the response. - JSON API:
GET https://jilsovereign.com/api/v1/verify/{report_id}- machine-readable, CORS-enabled, no authentication. Intended for forensic experts, regulators, integrators, and opposing counsel. - Sample records: five pre-rendered CREBs published for integration testing, one per pillar. See /samples/verdict-record.
Storage & Retrieval
JIL does not hold the plaintext CREB. The sealed bundle is written to a vendor-controlled Secure Document Vault (SDV) - by default the customer's SDV instance. JIL stores only the content hash, retrieval locator, and L1 anchor. Retrieval happens against the customer's SDV; JIL never has custody of the evidence itself.
Retention: 15+ years minimum. Exceeds BSA (5 years), FATF (5 years), NYDFS Part 500 (3 years), HIPAA (6 years), most state attorney-client privilege retention rules, and the 10-year FRE 902(14) horizon. Customers on the Legacy Plus SDV tier get indefinite retention.
Naming Convention
Throughout JIL documentation and communications:
- On first use in any document, expand: "Court-Ready Evidence Bundle (CREB)".
- After first use,
CREB(acronym) or "court-ready record" (descriptor) are both acceptable. - Inside the sealed artifact itself, the canonical identifier is
creb_idwith formatJIL-CREB-{UUIDv4}. - The term "verdict record" remains valid and is equivalent - useful when writing for audiences who have not yet seen the CREB term.
Referenced Standards
FRE 902(14) FRE 901 FRE 702 NIST FIPS 204 (ML-DSA) NIST FIPS 203 (ML-KEM) RFC 8032 (Ed25519) RFC 6963 (Merkle) Apostille Convention (1961) 31 CFR § 1020.410 (BSA) NYDFS 23 NYCRR 500 HIPAA 45 CFR § 164.530(j) SOC 2 Type II ISO 27001:2022
"Court-Ready Evidence Bundle" and "CREB" are marks of JIL Sovereign Technologies, Inc. (Delaware). This specification is published for public reference and does not grant any license to reproduce, modify, or commercially exploit the underlying verdict-engine architecture or the marks. Patent pending - see 53-claim patent portfolio.