Workflow close · 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-09T17:22:36.613Z; 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

147fc447-03cb-4259-88d1-29d4c388b6a8

SHA-256 output hash

sha256:659998bc8424968ad396c2aa97a867863bf9a0982948545d41432ede58dfb349

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NDIwNGNjZGM1N2YwZjZjZGNiMGU4ZWI4ZGMwM2RmN2YxYTcyM2RjMjY1NzQ1MjY2YmNhYzM5NzJkYWFmNGQzMSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJjaGlsZHJlbiI6W3siaWQiOiJhYzI5NDEzNi1mNTc2LTQyYzQtYjRhMC1lZTlkYTZlZjFjYzAiLCJvdXRwdXRfaGFzaCI6IjA3ZjdjNWQ0Y2I5NGFiNWVlMWJlMjFiNjE4NDhmYmVhMjY0ZWIwYzdmYTNkZTk5NjY2MTU5ODg2YmI2OTY5ZTkifSx7ImlkIjoiYTVhNTUyMzAtOTFmZS00YzMzLWI2NzEtMTYwOTRiNWM2MTk5Iiwib3V0cHV0X2hhc2giOiI5MWIzMzc0MzkzNzhlOWFjYTkzMjM2NGZhMTk1MTljNjcyOGE1NWEzZjdlYTgxYjlhMmI1ZTczNjY0NzQ2MzVmIn1dLCJjb3VudCI6MiwiZGVsaXZlcmFibGVzIjpbXSwiaGFuZG92ZXJfaWQiOiIyODU5Mjk5Zi0xZjc0LTRjNzEtOTcyZS02MjgzZGFmNWRhNmYiLCJpc3N1ZXJfYXV0aGVudGljYXRlZCI6ZmFsc2UsIm1lcmtsZV9yb290IjoiODJmZDcyMzQ0MWQzMmU1NjA2NDBlNzcyOWQ4ZjczMjk5YmJlMzEzM2FhNzg4NTM5OGY5MWI3ZWYzMGY5ZjU1YiIsIm1lcmtsZV92ZXJzaW9uIjoic2VxLW91dHB1dC12MSIsIm5lZ2F0aXZlX3JlY29yZCI6eyJub3RfY2hlY2tlZCI6W10sIm5vdF9ydW4iOltdfSwic3RlcHNfZGlnZXN0IjoiZmVlOTI0ZWMxZDEyNTFjNDU3NzY0MDFhNzlkNmU3M2U1NmVhZmY3MzU5ZTdmMDAzOWU1MDM0ZWRiZTM4MzhkYSIsInZlcmlmaWNhdGlvbl9zdGF0dXMiOiJub3RfdmVyaWZpZWQifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid29ya2Zsb3dfY2xvc2UiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-11-09T17:22:36.613Z

Bound call context

Receipt schema

0.4

Tool name

workflow_close

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:4204ccdc57f0f6cdcb0e8eb8dc03df7f1a723dc265745266bcac3972daaf4d31

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

Neutral Nostr anchor

Event ID

6e1eca1a78c3f60d772fdd4349cdfa8aefb799cbe4f1918afa554672cbab024c

Anchor status

published

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-09T17:22:36.613Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:659998bc8424968ad396c2aa97a867863bf9a0982948545d41432ede58dfb349","receipt_uuid":"147fc447-03cb-4259-88d1-29d4c388b6a8","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.