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 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-22T10:16:11.550Z; 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

f7fe4d46-6e1c-46c9-904e-dedab1b1ffbb

SHA-256 output hash

sha256:1ed5d5214282f52068adb18d17a928c550221aad058c2d9eee456630077d96c4

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6N2MwYjZiMzM4NGFmODNhZDZhMWNjMGNjNzk4YmRjZmU5ZGQ3OTkxOTU3Y2NkNjhmN2JjYjMwYjYwYTZkNGQ3OSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiY2hpbGRyZW4iOlt7ImlkIjoiNWYzM2FjYTQtZWE5MS00YmQ3LTg1MTEtMTRiNTZiMjk0NmNhIiwib3V0cHV0X2hhc2giOiI1NjZiYmFmYTI3ZDg4YzkwY2ViZTZlZWRkODA4MmUyN2RiZWMwYjMxY2RjM2EwYjJlNzVjMzQwM2ZjOWRkZTQwIn1dLCJjb3VudCI6MSwiZGVsaXZlcmFibGVzIjpbeyJuYW1lIjoiU3VwcGxpZWQgd29yayIsInNoYTI1NiI6ImUxYmRhMTkyMWE1Mjk5MmU5NDY0ZmZlZjZkMjEwMDY2MmM5ZGEzOTE2MzczMzJlNjYyY2QxNzBlYTI1NGVlMGEifV0sImhhbmRvdmVyX2lkIjoiMzY2MjdmYzQtM2MyMS00ZTk4LTljNzEtYzEwZGEwNThjM2UxIiwiaXNzdWVyX2F1dGhlbnRpY2F0ZWQiOmZhbHNlLCJtZXJrbGVfcm9vdCI6IjYwNjRlMTYxNDExYWJhODRlOTBlOTdhOWI5N2IzOWMxMjhhZjNhNmY0MzRkYTBjNTI3ODE1NWNiZTIzZjU5MTMiLCJuZWdhdGl2ZV9yZWNvcmQiOnsibm90X2NoZWNrZWQiOlsiUGFzdGVkIHdvcmsgd2FzIHN1cHBsaWVkIGJ5IHRoZSB2aXNpdG9yLiBJdHMgYWNjdXJhY3kgd2FzIG5vdCBpbmRlcGVuZGVudGx5IGNoZWNrZWQuIiwicHJvbXB0X3NoaWVsZCIsIlRoZSBzdXBwbGllZCB3b3JrIHdhcyBzYXZlZCwgbm90IGluZGVwZW5kZW50bHkgZXhlY3V0ZWQgb3IgY2hlY2tlZC4iXSwibm90X3J1biI6W119LCJzdGVwc19kaWdlc3QiOiI2MDY0ZTE2MTQxMWFiYTg0ZTkwZTk3YTliOTdiMzljMTI4YWYzYTZmNDM0ZGEwYzUyNzgxNTVjYmUyM2Y1OTEzIiwidmVyaWZpY2F0aW9uX3N0YXR1cyI6Im5vdF92ZXJpZmllZCJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3b3JrZmxvd19jbG9zZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-10-22T10:16:11.550Z

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:7c0b6b3384af83ad6a1cc0cc798bdcfe9dd7991957ccd68f7bcb30b60a6d4d79

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

257a3e7548a5a47bf2ec87ef77ef44930a2935e987806b69dd07e60a993d9979

Anchor status

published

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-22T10:16:11.550Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:1ed5d5214282f52068adb18d17a928c550221aad058c2d9eee456630077d96c4","receipt_uuid":"f7fe4d46-6e1c-46c9-904e-dedab1b1ffbb","schema_version":"zambo-receipt-anchor/1"}

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

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.