Original record
The submitted bytes and their digest metadata remain the reference point for later work.
Evident Technologies flagship
Keep the record whole.
Evident ICU is evidence-conscious infrastructure designed for traceable, reviewable, and reproducible work with complex records. It keeps source material, derivatives, annotations, and summaries in distinct lanes so people can review what happened without losing where each claim came from.
Private beta
This is a public product-information surface. General availability of accounts, uploads, storage, billing, dashboards, and exports is not represented as verified here.
The record model
Different kinds of truth stay visibly different.
A source file is not the same thing as text extracted from it. An annotation is not an observed fact. A summary is not the record. Evident ICU is designed to preserve those distinctions.
Derived artifact
Extracted text, transformed media, or other outputs retain a documented relationship to their source.
Human annotation
Notes, corrections, disputes, and review decisions remain attributable rather than silently replacing history.
Assisted summary
Machine-assisted or human summaries are labeled as interpretation and remain subject to source review.
A review-oriented method
From source intake to a package another person can inspect.
The current architecture defines a controlled sequence. Some stages are implemented internally; public service availability remains subject to verification and review.
Register the source
Record file identity and byte-level digest metadata without claiming the digest proves authenticity.
Create traceable derivatives
Keep transformed outputs linked to one or more sources and a documented process.
Build chronology with uncertainty
Organize events while retaining source links, date precision, conflicts, and missing records.
Review before export
Require human review and carry unresolved limitations into any assembled package.
Source-to-output traceability
A digest can show change. It cannot decide truth.
Integrity checks help compare bytes and expose unexpected change. They do not establish who created a record, whether its contents are accurate, or whether a court will admit it. Those questions require context, foundation, and human judgment.
Byte-level comparison
A recorded SHA-256 value can be recomputed to test whether a file’s bytes changed.
Source relationships
Derivatives are designed to point back to the source material and transformation that produced them.
Visible limitations
Disputes, uncertainty, missing records, and assisted analysis remain visible for the reviewer.
Synthetic example
Chronology without manufactured certainty.
A useful chronology distinguishes the time recorded by a source, the time inferred by a reviewer, and the precision actually supported by the material. Conflicts stay linked to the records that created them.
Example only: the identifiers and values shown here are synthetic and do not represent a real person, matter, or evidence file.
- event_id
- SYN-EVT-0042
- source
- SYN-SRC-0007
- time_precision
- minute
- observation
- recorded timestamp
- review_state
- human review required
- conflict_state
- one unresolved source conflict
Transparent limitations
The system supports review. It does not replace it.
- Evident ICU does not determine truth, credibility, intent, liability, or guilt.
- Hash agreement does not prove authorship, authenticity, completeness, or lawful collection.
- No page promises admissibility, court acceptance, legal compliance, or a legal outcome.
- Machine-assisted output is interpretation and requires source-based human verification.
- Availability, retention, deletion, storage, billing, and integration behavior must be verified before reliance.
Current availability
Private, review-led access.
Evident ICU is not represented here as a generally available self-service SaaS. For a factual conversation about the current private-beta surface, contact the operator directly.