Claim verification map
SHA-256 at intake
Implemented in the pipeline hash stage and the integrity chain-hash service. The hash is stored in the managed database
files.sha256
and displayed in the document viewer metadata panel.
Append-only custody log
Implemented in the custody service. Entries are SHA-256 chained to the previous entry hash. No update or delete API exists for custody records.
Chain hash between stages
Each pipeline stage output receives a chain hash computed from input_sha256 + output_sha256 + stage_name + previous_chain_hash + timestamp. Formula documented in the integrity chain-hash service.
Tier-gated features
Feature flags are enforced in route middleware and checked at stage runtime. The tier matrix is published in the internal tier specifications.
Observed facts vs. machine-assisted signals.
The pipeline produces two categories of output, handled differently throughout the record:
- Observed / reproducible record data — hash values, file size, extracted source metadata fields, extracted timestamps, and custody log entries. Hashes, file size, metadata, and timestamps are derived from the source file using fixed procedures. Under the same input and pipeline version, those file-derived outputs are reproducible and independently verifiable. Custody log entries record system and review events in the chain of custody and are independently auditable.
- Machine-assisted review signals — transcription, object detection, speaker attribution, classification, and AI-assisted analysis summaries. These outputs carry confidence scores, may vary across model versions, and are flagged for human review. They are not presented as conclusions and are not reproducible in the same sense.
The export packet is designed to distinguish between these two categories, with confidence metadata included for machine-assisted outputs where applicable.
How to verify independently of this platform.
Hash the file yourself
Run sha256sum ORIGINAL_FILE on any file from your export packet and compare
the result against the hash manifest included in that packet.
If the values match, the file is unchanged from what was recorded at intake.
No platform access required.
Read the custody log offline
Every export packet includes the custody log as a plain-text file. You can read the full sequence of recorded actions without platform access. The log is a copy of the append-only record — it is not generated at export time.
Reproduce from the source
Given the original file and the pipeline version recorded in the export, the reproducible outputs can be verified independently. The export is a derivation of the source file — not an artifact that requires this service to interpret.
These methods apply to reproducible record data: hash values, file size, source metadata fields, timestamps, and custody log entries. Machine-assisted signals — transcription, object detection, speaker attribution, classification, and analysis summaries — carry confidence scores and require human review. They are not reproducible in the same reproducible sense.
What we do not claim
Evident ICU is a record-preserving and review-support platform. It does not determine admissibility, credibility, legal merit, liability, or outcome. Outputs are review aids and should be verified against original records before use in legal, administrative, safety, housing, employment, or advocacy settings.
- We do not guarantee admissibility. Courts decide admissibility based on case-specific context.
- We do not guarantee identical output for AI-assisted stages (transcription, object detection, LLM analysis). We log confidence scores and flag outputs for human review.
- We do not claim 100% local processing. Core stages run locally when possible; cloud routing is used for GPU-dependent workloads based on tier and configuration.
- We do not provide legal advice. The platform is a technology tool, not a law firm.
Inspect the pipeline yourself.