Workflow integrity
Fresh local tests
Attempted is not completed.
I require a matching receipt and file-integrity check before the workflow records an action as completed.
01 THE PROBLEM
What needed to change
A workflow can look finished after an attempted action without valid confirmation. Later decisions may then rely on a false completion record.
02 THE IMPLEMENTATION
What I built and directed
I developed a persistent workflow requiring a validated receipt associated with the same case. It checks the stored SHA-256 hash before recording completion and rejects missing, unrelated or changed receipts. Source-linked claim checks remain a separate layer so evidence acceptance is not confused with execution success.
03 THE CHECK
What the evidence establishes
18 application-engine tests passed locally on 9 October 2026 using in-memory databases and temporary receipts. Those tests submitted no real applications.
Scope of this example
Local workflow tests cover case identity, file integrity and state transitions using temporary fixtures.
04 THE LESSON
The judgement behind the code
Define completion through evidence another person can inspect, not the confidence of the last message.
Public references
I can walk through a sanitised example without sharing private source archives or client material.