File integrity
Checks the declared format against the file bytes, records a SHA-256 fingerprint, preserves the original and detects exact duplicates.
Document Trust runs a reproducible control pipeline on every submitted file. It preserves and fingerprints the original, validates the actual format, then analyses PDF structure, revisions, signatures, graphic objects and available provenance. A versioned policy aggregates the findings, records checks that could not be completed and produces a traceable analyst-review file.
Each level produces a separate result: file integrity, structural analysis, cryptographic evidence, then comparison with configured business rules or approved references.
Checks the declared format against the file bytes, records a SHA-256 fingerprint, preserves the original and detects exact duplicates.
Examines pages, revisions, fonts, images, metadata, text collisions, graphic overlays and elements added after a signature.
Verifies cryptographic integrity and byte coverage when a signature exists, and checks C2PA Content Credentials when available.
Compares document rules, issuer references or approved official sources only when those connections are configured and authorised. Otherwise the result remains inconclusive.
The intake layer accepts native and scanned PDFs plus common raster formats. Document profiles, required fields and validation rules are configured per workflow.
Accepting a file format never means declaring the document authentic. Issuer references, business rules and source connections are validated separately for every deployment.
Each signal is localised in the file, assigned an explicit control result and presented to the analyst with its technical context. The platform does not make a legal finding of fraud.
AI-generation and editing traces: Document Trust can validate C2PA Content Credentials and report declared AI creation or editing actions. The absence of a credential does not prove that AI was not used, and declarative metadata alone remains a weak signal.
Specialised engines execute their controls independently and return structured findings. The policy engine aggregates those results without masking disagreement, missing evidence or unavailable checks.
Validates the file envelope, preserves the original and records its fingerprint.
Inspects objects, revisions, fonts, overlays, signatures and rendering order.
Assesses raster quality and technical image signals without inferring missing evidence.
Separates a visual signature from verifiable integrity and measures what bytes are covered.
Reads and validates available credentials and distinguishes verified provenance from declared metadata.
Combines explained findings, records unavailable checks and routes the file to accountable human review.
A result without an alert is not an authenticity certificate. Manipulations that leave no conclusive trace in the submitted file require an original, an issuer reference or another authorised source.
When the evidence is missing, conflicting or outside the configured scope, the system returns an inconclusive result and keeps the decision with the analyst.


