Verifiable receipt abe8d767 - workflow_close 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-19T20:57:33.204Z; 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

abe8d767-b176-4c98-81a2-2c171e2ee8f9

SHA-256 output hash

sha256:f7639266e864f601ef0dec93b602fd46fc1aea1a7acbe047d3a1050312a20038

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6Nzg4MjEwODU0NmExZjE2MDY3MDU3NWNlNDZlNzE4OGI1YmNlNDE1ZmNiOGU4N2M2MGIwMGQ2YzUwNThiOTk3ZCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiY2hpbGRyZW4iOlt7ImlkIjoiMmVlZmE5NWQtNzc3YS00NWU4LTg4NmEtMDkwMTM4ZDNkZGMxIiwib3V0cHV0X2hhc2giOiI0ZWIxMmE3MGRiNWY5MzE0YjdkODJkOWYxZjAxYzBjNWE0MzcyYmNmZWEzMWY4ZmVjMDM5MjU5ZDg1MGNlMTM4In1dLCJjb3VudCI6MSwiZGVsaXZlcmFibGVzIjpbeyJuYW1lIjoiU3VwcGxpZWQgd29yayIsInNoYTI1NiI6ImNlYmRjZjFjZWJhNzBmNWU4YjkyMzFkMWJkYTcxYTJhMWFiY2VmNjNkYzNkOWE2MDUzM2JlMjljY2I5NjM1ZmQifV0sImhhbmRvdmVyX2lkIjoiODgyMzA5ODgtNGZmMC00NjU0LWIzNjItY2M4ZDA2ODhkMWMzIiwiaXNzdWVyX2F1dGhlbnRpY2F0ZWQiOmZhbHNlLCJtZXJrbGVfcm9vdCI6ImI4MGIwYjZmZWU4MWFmN2U1NzYyYTE4OTVlYTExZTY4ZTQwZDA3ZDFjMGVhNWY3YTRiZjgyYTNjNjIyMmM5YzciLCJuZWdhdGl2ZV9yZWNvcmQiOnsibm90X2NoZWNrZWQiOlsiUGFzdGVkIHdvcmsgd2FzIHN1cHBsaWVkIGJ5IHRoZSB2aXNpdG9yLiBJdHMgYWNjdXJhY3kgd2FzIG5vdCBpbmRlcGVuZGVudGx5IGNoZWNrZWQuIiwicHJvbXB0X3NoaWVsZCIsIlRoZSBzdXBwbGllZCB3b3JrIHdhcyBzYXZlZCwgbm90IGluZGVwZW5kZW50bHkgZXhlY3V0ZWQgb3IgY2hlY2tlZC4iXSwibm90X3J1biI6W119LCJzdGVwc19kaWdlc3QiOiJiODBiMGI2ZmVlODFhZjdlNTc2MmExODk1ZWExMWU2OGU0MGQwN2QxYzBlYTVmN2E0YmY4MmEzYzYyMjJjOWM3IiwidmVyaWZpY2F0aW9uX3N0YXR1cyI6Im5vdF92ZXJpZmllZCJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3b3JrZmxvd19jbG9zZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-10-19T20:57:33.204Z

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:7882108546a1f160670575ce46e7188b5bce415fcb8e87c60b00d6c5058b997d

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

b894e2bf0bfcfacdd057a4b3960ad93d128dfab69fa150c82101c56f4d616613

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-19T20:57:33.204Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:f7639266e864f601ef0dec93b602fd46fc1aea1a7acbe047d3a1050312a20038","receipt_uuid":"abe8d767-b176-4c98-81a2-2c171e2ee8f9","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.