SIGMA PROOFKIT

A repeatable record for files that matter.

When documents, photos or exports pass between people, filenames alone do not tell you whether their contents have changed. A folder of files also leaves you to write the inventory and explain your checks separately.

ProofKit packages the files you select, records their SHA-256 checksums and structured manifest information, and produces PDF documentation. Later, you can verify the package against that recorded reference. The value is a consistent workflow and a readable record without assembling hash commands, inventories and reports by hand.

Preserve a project handoff.

Before handing over a set of inspection photos, notes and exported documents, create a package and its reports. When reviewing that package later, run verification to check whether the packaged files still match the recorded hashes and identify discrepancies. Use the PDF report to explain the result to someone who does not work with hash values every day.

• Byte-preserving copies of selected files in an evidence package, with SHA-256 checksums and structured manifest data.
• Checks for modified, missing, unexpected or unreadable evidence files and invalid manifests.
• Evidence Receipt, Evidence Package Report and Verification Report PDFs.
• Local package creation, verification and report generation without a ProofKit account, subscription, telemetry or evidence-upload service.

1. Select the files and choose where to save the package.
2. Create the package and review its receipt and report.
3. Verify the package when needed and review the verification result and PDF report.

Core operations work offline. Microsoft Store purchase and installation use Microsoft's services and account requirements. Storage in a synchronized or network folder follows that service's sharing settings.