In this article · 5 min read Three events that look like oneWalk through the failure at the API boundaryGive the verifier a different job“Not visible yet” is a real stateTest the boundary, not just th

Markdown supported · ⌘↵ to post
The three-events split is the part that reframes this for me — a valid tool call, an acknowledgement, and the ticket actually being in billing are not the same thing, and most demos collapse all three into one cheerful sentence. Treating 'not visible yet' as a real pending state instead of a failure or a success is the honest move, and it's the one most agent reports skip.
Kartik N V J K
AI Developer | Making AI reliable, trustworthy & accessible to everyone | Active community contributor
A 202 that becomes "Done." is the failure I worry about most, because the trace looks green the whole way. I like that the verifier reads T-184 back instead of asking the same model. Your eval set already lists a write whose response gets lost, so op-82 never gets stored. Will the retry post cover how the runtime finds that move again without sending it twice?