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-12T12:53:06.920Z; 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

69ae687a-68fc-410d-ab4a-82aa3c070033

SHA-256 output hash

sha256:f6d01d71d1cd03db022d41bbeee15e3a866adc282852bf8fe84af8223629a33a

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OGEzMDI4NjczZjc3MDA3ZTllNGU3MmUxZjJjN2Q5ZmExOTgxNTJhYzA5NjljZGQyMmU0N2NlNzVkMTk0NjMyYSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBNZWV0IFphbWJvIOKAkyBZb3VyIE5ldyBBSSBFZGdlICBcblxuSGkgW05hbWVdLFxuXG5aYW1ibyBpcyBsaXZlLiBXZeKAmXZlIGJ1aWx0IGFuIEFJIHBsYXRmb3JtIHRoYXQgYXV0b21hdGVzIHJvdXRpbmUgdGFza3MsIGJvb3N0cyBwcm9kdWN0aXZpdHksIGFuZCBzY2FsZXMgeW91ciBvcGVyYXRpb25zIHdpdGggemVybyBjb2RlLlxuXG5FeHBsb3JlIHRoZSBsYXVuY2ggYW5kIHNlZSBob3cgWmFtYm8gY2FuIHRyYW5zZm9ybSB5b3VyIGRheS10by1kYXkgd29ya2Zsb3c6IFtsaW5rXS5cblxuQmVzdCByZWdhcmRzLCAgXG5bWW91ciBOYW1lXSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS4wIn19

Timestamp

2026-11-12T12:53:06.920Z

Bound call context

Receipt schema

0.4

Tool name

write

Tool version

4.1.0

Permission scope

public

Caller type

session

Caller ID

sha256:8a3028673f77007e9e4e72e1f2c7d9fa198152ac0969cdd22e47ce75d194632a

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

bde0a48866db5d65d0124d5c17c0211504103c3d9ef71b6e34278107b19df2f9

Anchor status

published

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-12T12:53:06.920Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:f6d01d71d1cd03db022d41bbeee15e3a866adc282852bf8fe84af8223629a33a","receipt_uuid":"69ae687a-68fc-410d-ab4a-82aa3c070033","schema_version":"zambo-receipt-anchor/1"}

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

Relay publication is separate from receipt integrity. When the original signed event is available, Zambo retries pending, partial, or failed anchors about once a minute. Relay acknowledgements are external, so there is no guaranteed completion time; the receipt remains checkable from its saved bytes and verification link.

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.