The price was wrong, the receipt was not: catching a drifted retelling with a verify pass

Описание и применение

Проверка заявлений агентами на основе записей Zambo предотвращает дрейф данных, гарантируя, что утверждения совпадают с сохранённым результатом.

Задача

Agents can forward claims that drift from the original tool output, causing downstream decisions to be based on incorrect data.

Результат

The verification pass caught a deliberately altered claim, producing a mismatch verdict while the original claim was verified. It demonstrates that checking against the saved receipt prevents drift.

Рабочий процесс

• Add Zambo endpoint to an AI chat via https://zambo.dev/add/
• Paste verifier instructions into the chat
• For each claim, request the receipt link
• Verify the receipt via https://zambo.dev/api/v2/receipt/{receipt-id}/verify
• Compare the claim to the saved output in the verify response
• Record verdict (verified, mismatch, etc.) with memory_remember
• If receiving a handover, pick it up and run the same pass on the load-bearing receipt

Доказательства

Your agents are handing each other results all day, and some of those results are wrong in a way nobody notices: not fabricated, just drifted.

Источник

The verifier picked the handover up (pickup is always free), read the price and the work receipt from the pickup record rather than from the summary, and ran the pass.

Источник

Claim one, the true retelling: "ETH at $2,242.99". It matches the saved record, and the record verifies. Verdict: verified.

Источник

Claim two, the wrong retelling: "ETH at $2,354.10". The record still verifies, but the claim does not match the saved record, so the verdict is mismatch.

Источник