Write · saved and checkable

Provenance for every timeline entry

• EXECUTED BY ZAMBOZambo ran the tool call itself.
• OBSERVED VIA GATEWAYA Zambo gateway observed request and response bytes from the named external executor. Zambo did not run that external action.
• LOGGED BY AGENTAn agent or local hook reported the action. Zambo attests that the record is unchanged since logging, not that the action happened as described.

Private agent reasoning, built-in client actions, and direct calls to unrelated MCP servers are not included unless an agent or gateway reports them.

What is an execution receipt?

An execution receipt is a public record of a reported AI agent tool call. Its byte commitment and provenance claim can be checked independently; neither alone authenticates the issuer. Read the canonical definition of an AI agent execution receipt.

What is this?

Zambo's receipt store reports a tool call and records its result. The SHA-256 commitment covers the exact canonical bytes. The provenance label is bound to v0.4 receipt bytes when that check passes, but no pinned signature or trusted issuer key is checked. An anchor can timestamp a fingerprint; it does not authenticate the issuer.

Verification checks

• SHA-256 commitment: Checked independently against the exact decoded bytes
• Provenance binding: PASS; The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
• Metadata binding: PASS; metadata_hash matches the canonical metadata block.
• Issuer authentication: NOT CHECKED; no pinned signing key or trusted issuer was supplied
• Signature: NOT CHECKED; no Ed25519 signature or pinned key is supplied
• Chain: NOT CHECKED; no append-only chain proof is validated
• Stored timestamp: 2026-11-04T06:33:09.896Z; external immutability is not checked

Committed provenance claim

EXECUTED BY ZAMBO

The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.

Receipt ID

b1b6a8a9-1f91-4b40-9e0c-e3967ee4f926

SHA-256 output hash

sha256:4b9f9d87f65c25bfd72c5f0d02343f2a37a84af3e894285833dc82c7118a7246

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NGE3MThiYWRlYTI0MjkzNjkwOTExZjIyZjEwZTk2MzRjYzJiNzNiYTQyZjE4YmY0NDZiMDNmMjFiYjdlZDVjMiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlXG5cbkhleSBbTmFtZV0sXG5cblphbWJvIGp1c3QgbGF1bmNoZWQuXG5cbldlIGJ1aWx0IGl0IGZvciBjb250cmFjdG9ycyBhbmQgbG9jYWwgc2VydmljZSBidXNpbmVzc2VzIHdobyBuZWVkIGxlYWRzIGZhc3QsIHdpdGhvdXQgdGhlIGZyaWN0aW9uIG9mIGNvbXBsZXggc29mdHdhcmUuIFlvdSBwaWNrIGEgdHJhZGUgYW5kIGEgY2l0eS4gV2UgcmV0dXJuIGZpdmUgcXVhbGlmaWVkIHByb3NwZWN0cyB3aXRoIGNvbnRhY3QgaW5mbyBpbiB1bmRlciA2MCBzZWNvbmRzLlxuXG5JdCBzdXBwb3J0cyAyNCB0cmFkZXMgYWNyb3NzIHRoZSBVUy4gTm8gc2lnbnVwLiBObyBBUEkga2V5LiBObyBhdXRoLiBKdXN0IHRocmVlIGZyZWUgc2VhcmNoZXMgcGVyIGRheSBwZXIgSVAuXG5cbldlIHRlc3RlZCB0aGUgZW5naW5lIGluIEF1c3RpbiwgVFgsIGZvciB3ZWIgZGVzaWduLiBUaGUgc3lzdGVtIHJldHVybmVkIHplcm8gc291cmNlLWJhY2tlZCBsZWFkcyBhdCB0aGF0IG1vbWVudC4gVGhhdCBpcyB0aGUgY29ycmVjdCBiZWhhdmlvci4gV2UgZG8gbm90IGhhbGx1Y2luYXRlIGRhdGEgdG8gbWFrZSBhIGRlbW8gbG9vayBnb29kLiBJZiB0aGUgc291cmNlIGRvZXNuJ3QgaGF2ZSBpdCwgd2UgdGVsbCB5b3UgaXQgZG9lc24ndCBoYXZlIGl0LiBBIHJlY2VpcHQgcHJvdmVzIHRoZSBieXRlcyBzYXZlZCwgbm90IHRoZSBjb3JyZWN0bmVzcyBvZiB0aGUgbGVhZCwgYnV0IHRoZSB0cmFuc3BhcmVuY3kgaXMgdGhlIHBvaW50LlxuXG5XZSBhcmUgbm90IHNlbmRpbmcgdGhlc2UgdG8gYW55b25lIHlldC4gVGhpcyBpcyBhIHF1aWV0IGxhdW5jaC5cblxuVHJ5IGl0IHlvdXJzZWxmLiBHbyB0byBbTGluayB0byBaYW1ibyBTdGFja10gYW5kIHJ1biBhIHNlYXJjaCBmb3IgYSB0cmFkZSB5b3Uga25vdyBpbiB5b3VyIGNpdHkuIFNlZSBpZiBpdCByZXR1cm5zIHJlYWwsIHZlcmlmaWFibGUgY29udGFjdHMuIElmIGl0IGRvZXMsIHlvdSBoYXZlIGEgdG9vbCB0aGF0IHNhdmVzIHlvdSBob3VycyBvZiBtYW51YWwgZGlnZ2luZy4gSWYgaXQgZG9lc27igJl0LCB5b3Uga25vdyBleGFjdGx5IHdoeS5cblxuTm8gcGl0Y2guIE5vIHdlYmluYXIuIEp1c3QgYSB0b29sIHRoYXQgd29ya3Mgb3IgZG9lc27igJl0LlxuXG5MZXQgbWUga25vdyB3aGF0IHlvdSBmaW5kLlxuXG5bWW91ciBOYW1lXSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-11-04T06:33:09.896Z

Bound call context

Receipt schema

0.4

Tool name

write

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:4a718badea24293690911f22f10e9634cc2b73ba42f18bf446b03f21bb7ed5c2

Caller-reported label

zambo-home-demo (caller_reported, not authenticated team ownership)

Declared side effects

none

Side-effects schema

zambo-side-effects/1

Declaration hash

sha256:45aad38f3aa982b9aafe92ecb416ebe98791eddbaf8ab6df0bd08605b7c1bfee

This records what the server-side tool contract declared at call time. It does not independently verify that a downstream side effect happened.

Bound upstream evidence

Status

empty

Evidence SHA-256

unavailable

Byte length

unavailable

Upstream provenance

This receipt is independently auditable against the named upstream source. This is not a mathematical correctness claim.

• Source: · queried at: · raw response hash:

Neutral Nostr anchor

Event ID

a80abb5fdee849394839b82875a3ca9d6353a3f1da5dae1a0cc8fcbea4e09f6c

Anchor status

published

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.damus.io · wss://nos.lol · wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-04T06:33:09.896Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:4b9f9d87f65c25bfd72c5f0d02343f2a37a84af3e894285833dc82c7118a7246","receipt_uuid":"b1b6a8a9-1f91-4b40-9e0c-e3967ee4f926","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

Check this hash yourself

Receipt commitment: commitment matched; issuer, signature and chain not checked. This checks the saved bytes, not whether the answer was correct. Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. See the Nostr anchor event on a public viewer. The fingerprint is timestamped outside Zambo too.