Overview#
A serious crime prosecution is preparing disclosure under the Criminal Procedure and Investigations Act. The case has 3,000 exhibits. Every document needs sequential Bates numbering. Some contain PII that must be redacted before the defence receives them. The Brady material review must be systematic. Getting any of this wrong creates appeal grounds.
The Disclosure domain handles all of it: generating court-compliant bundles, numbering exhibits consistently, embedding QR verification tokens so any recipient can confirm a document's authenticity, and running Brady material analysis to identify disclosure obligations before a human reviewer misses them.
Key Features#
- Court-compliant disclosure pack generation with exhibit management.
- Bates numbering for evidence documents with configurable prefixes.
- QR code verification for document authenticity.
- Brady material analysis for identifying disclosure obligations.
- Document integrity verification with hash-based checking.
- Dynamic watermarking with recipient information.
- Disclosure bundle versioning and tracking.
- Recipient-specific access controls for disclosure packs.
Use Cases#
Crown Prosecution Service and district attorney offices generate court-compliant disclosure packs for prosecution and defence, with consistent Bates numbering and complete exhibit inventories that satisfy procedural requirements in both common law and civil law jurisdictions.
Defence counsel verify document authenticity using QR code-embedded tokens, confirming that materials received from the prosecution have not been altered since disclosure was made.
Legal teams run Brady material analysis on case records to systematically identify exculpatory evidence that must be disclosed to the defence, reducing the risk of missed disclosure obligations that could endanger a conviction.
Prosecutors apply dynamic watermarking with recipient information to sensitive disclosure materials, maintaining traceability if restricted documents are shared beyond their intended recipients.
Integration#
Integrates with evidence management, case management, and court filing domains for end-to-end legal disclosure workflows.
Open Standards#
- ISO 19005-3:2012 (PDF/A-3): Disclosure bundle index documents and produced evidence PDFs are generated as PDF/A-3 archival files, ensuring long-term preservation and court admissibility.
- CMS/PKCS#7 (RFC 5652): Each bundle manifest is digitally signed using a CMS detached signature stored in DER format, enabling offline integrity verification without the originating system.
- Internet X.509 PKI Time-Stamp Protocol (RFC 3161): Every exported bundle obtains a Time-Stamp Authority token that provides a cryptographically verifiable proof of the time at which the manifest existed, supporting chain-of-custody requirements.
- X.509 Public Key Infrastructure (RFC 5280 / ITU-T X.509): Bundle signing certificates are X.509 structures; certificate fingerprints are recorded in bundle metadata alongside the CMS signature.
- SHA-256 (FIPS PUB 180-4): All evidence files, the bundle manifest, CMS signature, TSA token, and the ZIP package itself are individually hashed with SHA-256; hashes are published in a manifest and a Merkle tree root is embedded in bundle metadata.
- HMAC (RFC 2104): QR verification tokens embedded in produced documents are integrity-protected with a keyed HMAC, allowing recipients to confirm that a document has not been altered since disclosure was made.
- ISO/IEC 18004 (QR Code): QR codes conforming to the ISO/IEC 18004 matrix barcode standard are embedded in produced documents so recipients can independently verify document authenticity against the platform.
- GraphQL: All disclosure operations, including Brady and Ward material analysis, bundle management, and QR verification, are exposed through a typed GraphQL API.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14