Change Proof
A Change Proof binds the source change, the affected artifact, the delivery receipt, the verification chronology including the failure, a completion timestamp, a proof id and a content hash.
This is the verified Change Proof artifact from the recorded pilot run, served from the evidence pack that ships with this service. It is not generated on demand, and this page cannot create, alter or complete a proof.
The proof
| Change | DZ-001 |
| Source procedure | PACKING-SOP |
| Source version | v14 |
| Affected artifact | WI-114 |
| Previous value | LEFT |
| Current value | TOP_RIGHT |
| Delivery status | DELIVERED |
| Verification result | PASS |
| Verification event | vev-session-001-001 |
| Completion timestamp | 2026-08-26T19:31:50.347551Z |
| Workflow | wf-dz-001-001 |
| Proof id | act-generate_proof-c54abbfcde29299f0a3cf3a24ee1867e |
Content hash
5c66dd80ca882602c7a263cdb6435c66b4462cbc0c24d43ac542511ca95a0c5e
What this hash is — and is not
The proof content hash is a SHA-256 over the canonical Change Proof JSON,
excluding its own content_hash field. It establishes content identity
and detects alteration of the proof.
It is not a digital signature, not an attestation, not a trusted timestamp, not non-repudiation, and not a blockchain or ledger entry.
Because the stored file contains content_hash, the SHA-256 of
the whole file is expected to differ from it. That is arithmetic, not a discrepancy.
Why it exists at all
Seven completion conditions must hold before a Change Proof is generated. There is no override, no force-complete, and no path by which a client can assert one. In the recorded run the first verification returned FAIL and no proof was produced — which is the point. A verification system that only works when the worker gets it right the first time verifies nothing.