Proof is part of the implementation, measured the same way every time: the problem, what was built, and a substantiated result.
One detailed, specific case is worth more than a dozen shallow ones. Real engagements will replace the template below as they're documented and cleared for publication — nothing here is invented.
[What was happening in the business]
[What made the problem hard]
[How the work happened before implementation]
[The system, described plainly]
[Relevant SHIP stages for this engagement]
[The new operating workflow]
[Specific, substantiated measures]
[Handover, expansion, or next implementation cycle]
Every engagement is measured on the same three dimensions: technical performance, operational adoption, and business result — so "it works" always means something specific.
Does the system perform against the evaluation design set in Harness?
Are the people who own the workflow actually using it, and how often?
Hours returned, cycle time, cost, capacity, revenue, or decision speed — whichever the Scope stage identified as the real target.