Direct answer

Problems a zambo receipt solves

A zambo receipt proves the saved result was not changed since it was saved. It never proves the answer was right. What it removes is the argument about what happened, and that argument is the expensive part of six everyday problems for freelancers, operators, and teams running agents. Each problem below is solved completely on its own page: the shape of the fix, a no-code paste that runs it, and a real run with every receipt linked, all inside the free tier.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup. New here? Add Zambo to your AI in one step. Reading as an agent? This index has a plain markdown twin, same content, no styling.

Updated November 2, 2026. First published November 2, 2026. The worked example is a real run executed against the live service on November 2, 2026, with every receipt read back the same day. Sample material in the runs is labeled a sample inside the records themselves.

The six problems

1. My client says I never delivered the work

The sent folder proves a message left, not which version was inside it. Deliver inside one record and answer the claim with a link: the brief, the draft, and the delivered revision as receipted steps in one handover the client already signed off on. Worked run: a sample delivery, 4 steps, 4 of 4 receipts checked, status accepted.

Solve it: the delivery record that answers the claim · the run's delivery handover

2. My AI said the task was done, but was it

Agents summarize themselves generously, and you cannot audit a paragraph. Split the done report into claims and check each against the record: backed by a step whose receipt verifies, or absent, and absent counts as not done. Worked run: a three-claim report, two claims backed, the email claim absent, verdict saved in the same record.

Solve it: check the report against the record · the run's done-check handover

3. Two agents disagree about what the data said

Every hand-off can mutate a number, and confidence is not evidence. Rule from the saved record: the original call's receipt holds what the data said, and the retelling that drifted is corrected to it. Worked run: $76,703.00 in the record against $80,538.15 in circulation, ruled in one record.

Solve it: let the saved record settle it · the run's ruling handover

4. My boss needs an audit trail of what the agent did

A chat scroll is not a trail and a screenshot convinces nobody. Run the job in one record and the trail assembles itself: every call and decision a step with a receipt, wrapped as one packet an auditor walks. Worked run: a 9-step packet, walked by a second identity, 9 of 9 receipts verified.

Solve it: hand them one link · the run's audit packet

5. The agent watched the price, but I cannot prove what it saw

An alert is a claim about a moment that no longer exists, and a quiet stretch proves nothing either. Save every reading with its receipt, baseline and rule included, and what the watcher saw becomes a list anyone can check. Worked run: baseline $76,708.00, check $76,743.00, +0.046 percent, no flag, both readings receipted.

Solve it: make the watch provable · the run's watch handover

6. I switched AIs and lost the thread of the job

The thread lives in the chat you left, and re-briefing loses a qualifier every round trip. Keep the job's record outside both chats: wrap at the pause, and the next AI picks it up free and continues the same job. Worked run: started in one AI, finished in another, 17 steps reading as one thread.

Solve it: pick the job up instead · the run's completion handover

The patterns underneath, as installable packages

Each problem above is one shape of a small set of patterns. The patterns ship as downloadable agent packages, each one teaching an agent the pattern by doing it, with Zambo as the mechanism inside:

Swarms: many agents, one shared job, a receipt per contribution. pip install zambo-swarm or npm install zambo-swarm · the swarm guide
The daily loop: recall, work, remember, wrap, so an agent comes back tomorrow knowing yesterday. npm install zambo-loop · the daily loop guide
The verify pass: check another agent's work from its receipts before you build on it. pip install zambo-verify-pass or npm install zambo-verify-pass · the verify pass guide
Delivery proof: client work as one checkable record, pickup as sign-off. pip install zambo-delivery or npm install zambo-delivery · the delivery guide
Signal watch: baseline, checks, a stated rule, and a digest with receipts. pip install zambo-watch or npm install zambo-watch · the signal watch guide

What a zambo receipt is, exactly

A zambo receipt proves the saved result was not changed since it was saved. It never proves the answer was right, the work was good, or the agent chose well: those stay human judgments. What it removes is the argument about what happened. Every page in this index is that one property, aimed at a problem where the argument about what happened is the expensive part. Check any receipt from any run here at zambo.dev/verify, and start free at zambo.dev/add: 20 calls + 1 wrap-up free every day, picking up in another AI is always free.

Frequently asked questions

What problems does a zambo receipt solve?

The ones where the argument about what happened is the expensive part: a client denying delivery, a done report nobody can check, two agents holding two versions of a figure, an audit with no trail, a watch nobody can prove, and a job whose thread dies in a chat you left. Each page in this index solves one completely, with a real run.

What does a receipt actually prove?

That the saved result was not changed since it was saved. Never that the answer was right or the work was good. The six problems here are all settled by the first property alone, which is why they were chosen.

What does it cost to start?

Free: 20 calls + 1 wrap-up free every day per identity, picking up in another AI always free, at zambo.dev/add. Past free, a Day Pass is $0.99 for 24 unlimited hours and the Zambo Pass is $29 for 30 days; both are one-time payments, never subscriptions.