Deals fail.
Context stays.
Payments have retries. This local lab asks what an agent-to-agent deal needs when verification or payment breaks: a trace, a reason, and a path back.
Transaction flow
Advance the local state machine, then simulate recovery.
Discover
Agents find each other before they can coordinate a deal.
Recovery trace
A deal should leave evidence behind.
Infrastructure is also what happens after “no.”
Verify
Identity and interoperability create enough trust for agents to meet.
Pay
Payments turn an agreement into a completed exchange.
Recover
A failed deal needs a retryable state, not a vanished relationship.
Local deal states and trace evidence
Read the explanation
The initial local state is Discover at index zero with no trace. One advance changes to Verify and appends one event. A second changes to Pay and appends another. At seventy pixels per trace event the first bar spans one hundred forty. Advancing while in Pay appends a Paid event but leaves the state at Pay, giving three events and a two hundred ten pixel bar. The label describes a local scenario; no payment, identity verification, protocol negotiation, or agent discovery occurs. Repeated Pay advances can append repeated Paid events, so the trace is an authored action log rather than deduplicated settlement evidence. After the three-event sequence, Simulate failure sets current state to Failed and the failed flag true, and appends a Failure event. Retry when that flag is true sets current to Recovered and failed false and appends Retry succeeded. The trace grows from three to five events, represented by one hundred fifty and two hundred fifty pixel bars. The failure note always says it stopped at payment even if failure was clicked from another state. Recovery does not perform a payment retry or replay verification. It is a local state transition that preserves previous notes and is useful for inspecting the difference between a state label and evidence of an external action. The five step buttons can directly select any state without appending an event. A fresh lab can therefore display Recovered with an empty trace. Conversely selecting another step after failure leaves the failed flag true until a real Retry or reset changes it. The bars compare an empty trace with the five-event sequence at sixty pixels per event. JSON export includes the displayed state, failed flag, complete local trace, and an explicit source boundary saying no live payment, identity, interoperability, or GenLayer integration is claimed. Reset removes this page local storage key and returns to Discover with no events. Inspect exported evidence and flag together rather than treating a chosen label as successful settlement.