Verifiable receipt ffb650d5 - handover_accept result | Zambo

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 this receipt?

This is a verifiable receipt for a journal entry. It confirms receipt, redaction, timestamping, and chaining. It does not attest to execution.

What is this?

Zambo's receipt store reports a journal entry from an agent or local hook. The SHA-256 commitment covers the receipt bytes. The provenance label is only a claim, not proof of issuer identity or that the reported action happened.

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-10-18T11:08:00.854Z; external immutability is not checked

Committed provenance claim

LOGGED BY AGENT

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

Receipt ID

ffb650d5-d4b7-49c3-91ff-ef1da4ebe0c0

SHA-256 output hash

sha256:bb5396ed6f10c2387f96f249dd81c98642381cde60a86ff0bc70c9297687d46b

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NmRmYWVlNGEzMmZlMWEzMjk2MzU3ZWRmOWNiMjlhN2MxOTNiZDQ3MWRmN2ZmNTQ0ZGMyZGI5YWJmZTQzZTllNiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1widmlzaWJpbGl0eVwiOlwicHJpdmF0ZVwiLFwibWVzc2FnZVwiOlwiUHJpdmF0ZSBkZWxpdmVyeSBjcmVhdGVkLiBVc2UgdGhlIGNsaWVudCBvciBvd25lciBsaW5rIHJldHVybmVkIHRvIHRoZSByZXF1ZXN0aW5nIHNlc3Npb24uXCJ9IiwicmVkYWN0ZWRfcHJvamVjdGlvbiI6dHJ1ZSwic291cmNlX2NvbW1pdG1lbnRfY2hlY2tlZCI6dHJ1ZSwic291cmNlX291dHB1dF9oYXNoIjoic2hhMjU2OjY4NWY3NTJjYmYyMTU4ZjVlZDUwMTVhZDhiZTY2MTBhY2M4YTg0ZGEzY2ZhMmEyODdmZDgxNmFkYTZkY2ZiZWEiLCJzb3VyY2VfcmVjZWlwdF9pZCI6ImVkZjczZDhhLTYwOWQtNGFkMC1hMmJiLTVlODg0NTJlYjU5MyJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiaGFuZG92ZXJfYWNjZXB0Iiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-10-18T11:08:00.854Z

Bound call context

Receipt schema

0.4

Tool name

handover_accept

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:6dfaee4a32fe1a3296357edf9cb29a7c193bd471df7ff544dc2db9abfe43e9e6

Declared side effects

state_write

Side-effects schema

zambo-side-effects/1

Declaration hash

sha256:dfb4412aa429d3ac637a05668c435bcc90a251363fcdd49f7b85ae4ab55b5bc9

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

no_upstream_bytes_captured

Evidence SHA-256

unavailable

Byte length

unavailable

Neutral Nostr anchor

Event ID

0bb114aae06005bf20f54c359b56b0a3cab3cca931559b70b4e4231742c168dd

Anchor status

partial

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-10-18T11:08:00.854Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:bb5396ed6f10c2387f96f249dd81c98642381cde60a86ff0bc70c9297687d46b","receipt_uuid":"ffb650d5-d4b7-49c3-91ff-ef1da4ebe0c0","schema_version":"zambo-receipt-anchor/1"}

Anchor status "partial": Published to some configured relay targets; publication was not confirmed by every configured relay.

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.