The Integrity Pledge
Non-repudiation and tamper-evidence—what “immutable” means in agwitness.
Non-repudiation
Once a deed is accepted, the story of what was notarized should be stable and checkable—not editable folklore.
Our Non-Repudiation technology ties human-facing artifacts to cryptographic fingerprints. The goal is simple: change the record after the fact, and verification fails—not a hidden admin toggle.
At a glance
Short anchors for security reviews and customer diligence questionnaires.
Hash
SHA-256
Fingerprint before storage & verify
Verify
Public
Hash-based check without login
Mutability
After sign
Designed for tamper-evidence
Custody
You
Export & deletion paths
Cryptographic binding
Every deed is hashed with SHA-256 at creation. The hash anchors the narrative, parties, and machine context that were notarized. Tampering with the underlying record invalidates verification—recipients can detect drift.
We use standard algorithms so third parties can reproduce checks with their own tooling.
No backdoors
We do not offer silent edits to signed deeds. Integrity means a clear story: what was notarized, when, and under whose acceptance. Operational support cannot “patch” history without leaving traces incompatible with verification.
If a record must be superseded, that happens as a new deed—not a rewrite of the old one.
Tamper-evident storage
Deeds live in systems designed for durability and access control. The verification path compares presented content to the stored fingerprint—if storage diverges from what was notarized, checks fail.
Enterprise deployments may add private replicas or retention policies; the verification math stays the same.
Verification path
Any party can verify a deed using the hash and public verify flow. PDF artifacts can carry links or codes that resolve to the same check—recipients need not trust a screenshot alone.
Verification does not require faith in agwitness beyond the correctness of the published hash for that deed.
Technical & operational security
For headers, sessions, APIs, and webhook hardening, see the Security Protocol—not a substitute for this pledge, but complementary.