Verifiable receipt 7275dabd - 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:16:15.789Z; 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

7275dabd-d388-4354-90e0-fc6af872c16e

SHA-256 output hash

sha256:094cb5f1914ac70a862f58a0437ae36e92b48ca51f9e01a607ff1c7a72207435

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YzBjNDA2MWRjZmRiNjc2YmI2MzM1MzlkYmQ2OWE5YzlkOTQ0MTRjNTI5NDY2NjJkNTQ0MDI5NGNkZWJlNGVjMCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiY2hpbGRyZW4iOlt7ImlkIjoiOTlmN2MyNGQtMGZlOS00ODQzLWJiY2ItNjAyMjQ3NzZlNzMxIiwib3V0cHV0X2hhc2giOiI1MzRiNjUyMzdmYmUzNDk4NjkyNjg5MWEzNDkzZjJlZWM5OGY2MjUzM2RhYTFkMzk3ZTI3YzU5YTk2NzE1MDVlIn1dLCJjb3VudCI6MSwiZGVsaXZlcmFibGVzIjpbeyJuYW1lIjoiU3VwcGxpZWQgd29yayIsInNoYTI1NiI6ImI0ZDQ3MTdkYTljNDc5ZDUyZTcyNjU2NGYwMzJiNDQ3MzJjNzRiOTZmMjYyNzQwMzhlOWNlNWIwM2QwNmUzNzYifV0sImhhbmRvdmVyX2lkIjoiYzc5YTBiYmEtMDc4Mi00ZmNkLTkwMjItYzY4MDcwOGQzNjY4IiwiaXNzdWVyX2F1dGhlbnRpY2F0ZWQiOmZhbHNlLCJtZXJrbGVfcm9vdCI6IjBhNjU5YjBkYTYwZTk5MDNlYmUxMmIzNmRiMzg5OGNlMGZkZDUyNjc0MTY1NWIwNjJjY2Y0OTkzOTM4MjdjZDkiLCJuZWdhdGl2ZV9yZWNvcmQiOnsibm90X2NoZWNrZWQiOlsiUGFzdGVkIHdvcmsgd2FzIHN1cHBsaWVkIGJ5IHRoZSB2aXNpdG9yLiBJdHMgYWNjdXJhY3kgd2FzIG5vdCBpbmRlcGVuZGVudGx5IGNoZWNrZWQuIiwicHJvbXB0X3NoaWVsZCIsIlRoZSBzdXBwbGllZCB3b3JrIHdhcyBzYXZlZCwgbm90IGluZGVwZW5kZW50bHkgZXhlY3V0ZWQgb3IgY2hlY2tlZC4iXSwibm90X3J1biI6W119LCJzdGVwc19kaWdlc3QiOiIwYTY1OWIwZGE2MGU5OTAzZWJlMTJiMzZkYjM4OThjZTBmZGQ1MjY3NDE2NTViMDYyY2NmNDk5MzkzODI3Y2Q5IiwidmVyaWZpY2F0aW9uX3N0YXR1cyI6Im5vdF92ZXJpZmllZCJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3b3JrZmxvd19jbG9zZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-10-19T20:16:15.789Z

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

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

5de622b11222002e68411299d7d22524c181c497144e31cd82ae4b6e1dc12571

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:16:15.789Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:094cb5f1914ac70a862f58a0437ae36e92b48ca51f9e01a607ff1c7a72207435","receipt_uuid":"7275dabd-d388-4354-90e0-fc6af872c16e","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.