How Amicus Makes Integrity Verifiable

When you work across teams and time zones, the facts of a Proposal can blur. Amicus makes those facts visible and verifiable. Each snapshot pairs a human‑readable record with a standard, machine‑readable data bundle, and it anchors both with a clear, public way to prove that nothing was altered. The result is a shared record you can trust without needing to trust any one person.

What a Proposal snapshot contains

Every Proposal snapshot includes two artifacts:

• A PDF for human review and filing.
• A standard data bundle that captures the exact Parties, Details, Terms, and signature records for that Proposal at the moment of the snapshot.

The data bundle is precise. It reflects the Proposal as it stood in its Case, including who the Parties are, the populated Details, the Terms in force, and the time‑stamped signature records. This keeps the human view and the structured record aligned.

Integrity by design: the SHA‑256 fingerprint

To make integrity visible, Amicus computes a SHA‑256 value for the data bundle at snapshot time. SHA‑256 is a cryptographic fingerprint for an exact set of data. If the data changes by even one character, the fingerprint changes. It proves that the content was not altered; it does not identify who created it.

Amicus prints this fingerprint in the PDF’s Audit trail, alongside timestamps and the relevant Case and Proposal references. The Audit trail also points to simple verification instructions and a recommended online SHA‑256 tool. You may use that link or any SHA‑256 tool you prefer; the result will be the same when the data is the same.

This distinction matters: the SHA‑256 fingerprint (a hash) confirms integrity. It is not a digital signature and does not prove authorship or identity. It tells you whether the standard data bundle still matches the state of the Proposal at the time the snapshot was taken.

Verify in minutes

1. Open the snapshot email — When a Proposal becomes an Agreement (all required Parties have signed), Amicus emails the snapshot. Download the attached PDF and the standard data bundle for the Proposal you are reviewing.
2. Open a SHA‑256 tool — Use the recommended link in the Audit trail or any SHA‑256 tool you prefer.
3. Generate the fingerprint — Load the data bundle into the tool and produce its SHA‑256 value.
4. Compare with the PDF — Locate the SHA‑256 line in the PDF’s Audit trail and compare it to the value you just generated.
5. Interpret the result — Match means the content is intact; mismatch means something changed.

Why this matters for operators

Operators need records that stand on their own. With Amicus, anyone can independently verify that a Proposal’s structured content—the Parties, Details, Terms, and signature records—remains exactly as it was at the snapshot. This reduces disputes by turning questions of memory into matters of fact.

The practical benefits are direct. Independent verification strengthens defensibility. Shared facts reduce friction between teams and counterparties. When integrity checks are built into the document itself—through a visible fingerprint in the Audit trail—review moves faster and objections give way to alignment.

This approach reflects our motto, Claritas et Integritas—Clarity and Integrity. We aim to provide records that do not ask for trust; they demonstrate it. The fingerprint, the timestamps, and the Case and Proposal references together create a stable reference point. You can proceed with confidence, knowing that what you see is what was agreed at that moment, and that anyone can confirm it without special tools or insider access.