Verifiable receipt 91c9a15c - handover_submission 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-17T01:01:07.926Z; 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

91c9a15c-6202-454f-81ea-bb01c86006b0

SHA-256 output hash

sha256:1edba70e2d12cb7f3ab43ac21caae99fb6afdc8f804b39dee297f841795cf04a

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YzQ2ODA1NjQyNDVjY2MyY2Y0MDgzZGRlOGU3NGEwZDFkNWY5NDQ2ZTdlYTZmNTQwYTRhYWIwY2RjMTMxNDJmYiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiY2xhaW0iOiJTdXBwbGllZCB3b3JrLCBub3QgaW5kZXBlbmRlbnRseSBjaGVja2VkLiIsImRlbGl2ZXJhYmxlcyI6W3siY29udGVudCI6IkNsYWltIDE6IHN0YW5kaW5nIHJlZHVjZXMgc2l0dGluZyB0aW1lIChodHRwczovL3d3dy5jZGMuZ292LykuIENsYWltIDI6IG1heSByZWR1Y2UgYmFjayBwYWluIChodHRwczovL3B1Ym1lZC5uY2JpLm5sbS5uaWguZ292LykuIENsYWltIDM6IGRlYWQgbGluayBzb3VyY2UgKGh0dHBzOi8vZXhhbXBsZS5pbnZhbGlkL25vcGUpLiIsIm5hbWUiOiJTdXBwbGllZCB3b3JrIiwic2hhMjU2IjoiM2FhYmI2MTgwMjc3OWYzOTAxMDQ3MWVmNzI3NGY5MTE5ZjhkY2YwMDRjNWExMjRkZDgyOTFkZGU3NzdjMmVkNiIsInZlcmlmaWNhdGlvbiI6ImJyb3dzZXJfY2hlY2thYmxlIn1dLCJzdW1tYXJ5IjoiIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImhhbmRvdmVyX3N1Ym1pc3Npb24iLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-10-17T01:01:07.926Z

Bound call context

Receipt schema

0.4

Tool name

handover_submission

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:c4680564245ccc2cf4083dde8e74a0d1d5f9446e7ea6f540a4aab0cdc13142fb

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

no_upstream_bytes_captured

Evidence SHA-256

unavailable

Byte length

unavailable

Neutral Nostr anchor

Event ID

9cd2e3c6440d091daf0ac6d8b5f0a8b3504a76b3a8bc41e7f7ce3ce1c3d1332b

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-17T01:01:07.926Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:1edba70e2d12cb7f3ab43ac21caae99fb6afdc8f804b39dee297f841795cf04a","receipt_uuid":"91c9a15c-6202-454f-81ea-bb01c86006b0","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

API v2 status: verified. This status summarizes the v2 commitment and provenance checks; it does not prove 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.