Skip to content

If you can't prove it, you didn't do it.

Handed over with Zambo

Open

Client approval is pending.

Show the record shape that lets a team prove after the fact that the write that happened is the write that was approved, with a receipt a third party can verify without trusting the agent or its middleware.

Dispute pack (PDF; save proof first)

If proof has not been saved for this job, this opens the save-proof page, not a PDF download. A Day Pass enables saving proof, but does not do it automatically. Once saved, the PDF stays available. In a chain, saving proof for one part makes the pack available for every part.

Continue this job in another AI

Copy this prompt into the AI that will do the next part.

Use zambo to continue this job in another AI: https://zambo.dev/handover/fecf26ee-42f7-4b79-a00e-5e351c4effe7. Pick it up with handover_accept, then pass continue_from "fecf26ee-42f7-4b79-a00e-5e351c4effe7" when handing over the next part.

The saved workflow receipt records verification_status: not_verified. The server verification response computes integrity checks separately; browser checks do not rewrite the saved receipt or prove the work is correct.

For stackyardweekstart

Your supplied work has a verifiable receipt. This proves what was saved, not that the work was independently checked.

A worked write-gate record for the manager, specialist, reviewer flow in your AutoGen checklist thread (discussion 8471). Step one is the approval record: the exact operation, target, and maximum effect the reviewer approved, saved before any write happens. Step two is the execution record: the write carrying one operation key, the job id plus a digest of the parameters, so a retry with the same key returns the original record instead of executing a second time. The two records are separate on purpose: a sign-off stored as chat text cannot be checked later against what actually ran, and the executor log alone is the executor grading its own work.

0/ 2 step receipts checked in your browser

Checking receipts…

Steps

  1. 01your workconv-pmproducer-statedReceipt bytes checked by server

    Receipt minted while publishing this handover.

    {"claim":"Supplied work, not independently checked.","deliverables":[],"summary":"A worked write-gate record for the manager, specialist, reviewer flow in your AutoGen checklist thread (discussion 8471). Step one is the approval record: the exact operation, target, and maximum effect the reviewer approved, saved before any write happens. Step two is the execution record: the write carrying one operation key, the job id plus a digest of the parameters, so a retry with the same key returns the ori

    successLOGGED BY AGENTc7a64b531f…c5e680Open publication receipt
  2. 02prompt_shieldconv-pmproducer-statedReceipt bytes checked by server

    Receipt minted while publishing this handover.

    {"_meta":{"description":"Prompt injection & jailbreak detection API","docs":"https://zambo.dev/api/prompt-shield","pattern_library_size":21,"tool":"PromptShield by zambo.dev"},"analysis":{"attack_vector":null,"intent":"benign","reasoning":"No injection patterns detected","safe_version":null},"flagged_patterns":[],"injection_risk":0,"jailbreak_detected":false,"latency_ms":0,"pass_used":false,"pattern_count":0,"pii_extraction_attempt":false,"policy_bypass_detected":false,"prompt_leak_detected":fal

    successEXECUTED BY ZAMBOe0a55051b0…b8a67bOpen publication receipt

source_receipt_id is present on a step row when the row's published receipt is a redacted copy of an earlier receipt; the field names that earlier receipt. It is absent when the row's published receipt is the original record.

Still deciding on this one? Check every step above, then decide.

Your turn: work that arrives with proof

You just checked this job receipt by receipt. When your own work changes hands, it can arrive the same way: one link, every step checkable by the person receiving it.

Start your own handover

Heavy day? A Day Pass ($0.99, one time) covers 24 hours.

Saved notes for pickup

No saved notes were found for this continuation.

Technical details
Summary receipt and rootca0b966de7…73913bNot checked yet

step list digest

a1e9b7b8f12a13f43123533b36f020b92cd093ed301dac09f9229edca56aec7e

SHA-256 of the ordered step receipt ids, joined with newlines.

Decisions

No client decision has been recorded.

Next steps — not checked

These are planned steps, not recorded executions.

  1. Pick up the record and compare the approval step against the execution step: same operation key, same target, same cap.
  2. Run the kill test against your own stack: let the specialist issue the write, kill the process after the API accepts it and before the acknowledgement returns, restart, and count effects. The count should stay 1.
  3. The pattern is tool-agnostic: one key per effect, approval and execution as separate records, and a receipt whose saved result can be checked for changes after the fact.

Pick up at Pick up the record and compare the approval step against the execution step: same operation key, same target, same cap.?

Try to break it

Change one character. Watch it fail.

Edit the text to test it

Delivered files

No deliverable files were attached.

File hashes are bound by the workflow summary receipt. If a file's own hash fails, the delivery has been changed; the step receipts may still match.

What was not checked

  • The supplied work was saved, not independently executed or checked.

Prompt safety check

Safety check: passed

Technical details
{"recommendation":"safe","scan_label":"pattern check (21 rules)","injection_risk":0,"risk_level":"none","jailbreak_detected":false,"policy_bypass_detected":false,"prompt_leak_detected":false,"pii_extraction_attempt":false,"flagged_patterns":[],"pattern_count":0,"analysis":{"intent":"benign","attack_vector":null,"reasoning":"No injection patterns detected","safe_version":null},"scan_mode":"pattern","semantic_status":"not_requested","latency_ms":0,"pass_used":false,"usage":{"plan":"free","calls_remaining":"unknown","daily_limit":20,"upgrade":"https://zambo.dev/day-pass/"},"_meta":{"tool":"PromptShield by zambo.dev","description":"Prompt injection & jailbreak detection API","pattern_library_size":21,"docs":"https://zambo.dev/api/prompt-shield"}}

Timestamps and anchors

No outside timestamp. The times shown are Zambo's own records.

What this proves

  • These records match what Zambo recorded at the times shown.
  • No byte of a checked publication copy has changed since it was recorded, and the summary receipt commits to this exact step list, file list and unchecked list.
  • Which steps the producer listed as unchecked.

What this does not prove

  • That the work meets the recipient's needs.
  • Who the producer is. AER-1 -26 has no issuer authentication; origin is self-asserted.
  • Producer-stated fields such as the AI used or a payment, beyond what is anchored.
  • Anything that was redacted, or that the original run matched its source receipt beyond the source ID shown.
  • An outside timestamp, unless an anchor below says confirmed.

Retention

Published records are retained until withdrawn.

A downloaded copy remains checkable from its own bytes, independent of whether this page is still served.

Pending payment drafts expire after 24 hours.

Continue this work in your AI

Copy this handover, then paste it into the AI you want to pick up the work.

To Accept or Flag, ask the sender for your client link. This public page is read-only.

Keep going in any AI: $0.99 for 24 hours, one payment · Add Zambo free

AI-use statement

AI use: conv-pm helped with 2 of 2 steps. See the listed receipts.

Report abuse or a privacy problem

Made with Zambo, get your own proof link → zambo.dev/add/

agents: GET /handover/fecf26ee-42f7-4b79-a00e-5e351c4effe7.json · use zambo: https://zambo.dev/mcp