DOCUMENT ASSURANCE · REPORT RECHECK

Do not just archive a PASS. Re-verify the original delivery and check whether its evidence reproduces.

After re-verifying the original ZIP or Trusted Folder, strictly compare the fresh recipient report with the previously saved report locally. FileNest compares privacy-bounded evidence without treating the report itself as a digital signature.

Strict FileNest report contract Unknown fields rejected Batch ZIP / Trusted Folder

Back to Document Assurance Re-verify Batch ZIP Re-verify Trusted Folder

CORRECT ORDER

Original delivery → Re-verify → Fresh report → Compare with baseline

An old JSON file by itself is not independent verification. First use the existing Batch ZIP Verifier or Trusted Folder Verifier to recalculate the original delivery, then place the fresh and baseline recipient verification reports here.

Strict browser-local parsing · Reports are not uploaded Compares privacy-bounded evidence summaries only

1. Load the previously saved recipient verification report

This is the baseline report. FileNest strictly validates its schema, evidence fields, counters and trust boundary; unknown fields or upgraded trust claims are rejected.

Choose baseline report JSON

2. Re-verify the original delivery, then load the newly generated report

First return to the Batch ZIP or Trusted Folder verifier and re-run the original delivery, then download a new recipient verification report. Do not duplicate the same old JSON as a substitute for re-verification; FileNest will not display two exactly identical reports as reproduced.

Choose fresh re-verification report JSON

Boundary: neither the reports nor the reproducibility receipt are self-authenticating evidence, a trusted timestamp, legal certification or delivery receipt. Independent verification still requires re-checking the original delivery ZIP or Trusted Folder; this tool checks whether the privacy-bounded evidence left by two FileNest local verification runs is reproducible and can save a summary receipt of that comparison.

COMPARISON SCOPE

Ignore rerun time, not evidence that changes the conclusion.

Each report naturally has a different generatedAt, so report-generation time is excluded from evidence comparison. Verification outcome, Manifest/Ledger summaries, PDF/receipt counts, reviewability, processing boundary and trust boundary are compared. A different delivery mode or any changed evidence category prevents a reproduced result.