Evidence Trust Fabric Overview
A concise explanation of the referral boundary, provenance model, chain of custody, and package architecture.
Request the brief →Resources
Evidence integrity, explained.
Operational, technical, and legal materials for teams evaluating the referral workflow.
Architecture & Security Review
Control mapping, data flows, deployment options, identity, logging, and verification design.
Request a review →FRE 902(14) Readiness Checklist
Questions for agency counsel and evidence custodians when designing a certification process.
Request the checklist →Frequently asked questions
Is IntegrityHawk an e-discovery platform?
No. It is positioned upstream, at the boundary between a validated fraud finding and downstream investigative or prosecutorial intake.
Does IntegrityHawk determine whether evidence is admissible?
No. Courts determine admissibility. The platform is designed to preserve integrity, provenance, and certification data that may support legal authentication workflows.
Can it work without LedgerHawk?
Yes. LedgerHawk can produce the analytic finding, but IntegrityHawk can also receive validated output from other fraud analytics, case intake, audit, or program-integrity systems.
Does the platform store sensitive evidence on a public blockchain?
No. The intended architecture uses protected off-chain storage for sensitive content while recording integrity and audit events in a controlled ledger environment.
Can agencies configure the package?
Yes. Required artifacts, review gates, certification language, metadata, and delivery formats should be configured to agency policy and counsel requirements.