Case study
Five calls. Five matches.
Verisuff, an independent evidence-review engine, came to Zambo inbound and built a pilot around a hard question: after a versioned AI workflow changes, which earlier conclusions still stand, which one needs fresh review, and what must stay on hold? It evaluated two linked Zambo handovers and matched all five decision calls Brennan Zambo had set in advance for AER-1 evidence continuity.
Technical execution completed November 13, 2026. Brennan Zambo sent written confirmation on November 14, 2026.
Why Handover was the test surface
Handover is the flagship surface of Zambo, the verifiable work layer for AI built by Brennan Zambo, creator of AER-1, the agent execution receipt standard. A handover carries a job's goal, steps, outputs, and decision state to the next AI or human as one public record. That made it the right pilot target: the record already separates claims from the receipts that support them, so an outside reviewer can decide claim by claim instead of grading a summary.
Revision A was accepted by the client on October 16, 2026. Hop 2 chained from it and changed exactly one material fact: the Bitcoin claim received fresh price evidence. The other three claims were not rerun, edited, or reasserted. They stood on their Revision A receipts.
The claim map
| Question | Verisuff decision | What the record shows |
|---|---|---|
| C1, BTC | REASSESS | Revision A recorded BTC at $82,212.68 on receipt c7e596e9. Hop 2 replaced that evidence with BTC at $73,804.35 on receipt b015d14c. The $8,408.33 drop is the worked example below. |
| C2, ETH | REUSE_SCOPED | The ETH claim stayed inside its original scope: $2,472.76 as of October 16, 2026, on receipt 647bbf66. |
| C3, SOL | REUSE_SCOPED | The SOL claim stayed inside its original scope: $106.17 as of October 16, 2026, on receipt 2b9a1121. |
| C4, PromptShield | REUSE_SCOPED | The original prompt safety result stayed on receipt 51dfbf1e: recommendation safe, injection risk 0, risk level low. The original 18-pattern result was retained; a later 21-pattern scan in Hop 2 is a separate run and does not rescore C4. |
| Q5, Hop 2 release | BLOCK_RELEASE | Revision A's client acceptance is on receipt 14cb8b21 and binds Revision A's Merkle root only. Hop 2 has its own root and no client acceptance of its own yet, so release stays blocked. The chain's later pickup is recorded on receipt b5dea3ca; pickup is continuation, not acceptance. |
The $8,408.33 movement is why REASSESS exists
Revision A's Bitcoin claim was an as-of claim: BTC was $82,212.68 when its receipt was saved. Hop 2 did not declare that sentence false. It replaced the evidence underneath the claim with a fresh live price: $73,804.35. The difference is $8,408.33.
That distinction is the pilot in one example. A conclusion built on the first price cannot quietly ride forward on the second receipt. REASSESS says: keep the old claim readable in Revision A, but derive any conclusion for Hop 2 from the new evidence before relying on it. The other claims did not need the same treatment because their evidence did not change.
What the decision words mean
REUSE_SCOPED means the claim's receipt is unchanged across the revisions, still verifies in public, and the reuse stays inside the claim's stated scope. For the ETH and SOL claims, that scope is the price as of October 16, 2026, never a claim about the current price.
REASSESS means the evidence was substituted, so conclusions drawn from the old evidence must be derived again against the new receipt before they are relied on.
BLOCK_RELEASE means stop. In this pilot, release against Hop 2 is blocked until Hop 2 receives its own client acceptance. An earlier revision's acceptance does not authorize a later revision merely because most of its evidence carried over.
How the run was checked
Verisuff 0.2.4.dev1 produced the five decisions before comparison with the predefined criteria. All five matched Brennan Zambo's scored calls exactly. Each decision passed Verisuff's native checker and a separate source-binding check: five of five on both. Verisuff then reproduced the same result through a clean-install replay in a separate environment.
Revision A's Merkle root is 002e64ec909f535c90f965e8b110372c4685499c029fda041cb33c29798da10d. Hop 2's Merkle root is 41d91c0b92511a2ec7315bb898d62ad9877be6148944f63bab4d075bfeaeb548. The AER-1 conformance corpus behind the receipt format currently carries 143 vectors and 146 checks at zambo.dev/aer1/corpus.json.
A verifiable AER-1 receipt proves that the saved result has not changed since it was saved. It does not prove that the result was right. The pilot used that boundary on purpose: Verisuff decided what the unchanged or changed evidence could support, claim by claim.
Run the pattern on your own work
Connect an AI to Zambo at https://zambo.dev/mcp, run the job, and wrap it into a handover addressed to the person or AI who receives it. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. A Day Pass is $0.99 and unlimited for 24 hours. Ongoing use is the Zambo Pass at $29 for 30 days, or $19 for 30 days for $ZAMBO holders. A Lifetime Pass is $250, one payment for good.