Receipt publication · 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-11-08T06:45:22.997Z; 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

a3a112db-62d4-56ab-a4e9-098d9886bd83

SHA-256 output hash

sha256:253290f4ebcbb33c5ea88ddd24b09f9143d8db73859b8c4439f060b885e2672e

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OGNlZTZkNjljZGE2NDczZTE1ZGE3YTdhYTZkMjIyMGM4ZTM1YTA2YzA5MWY4NmI0MTQ0ZjE4Njg1ODg2OWNmNiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJva1wiLFwidGhyZWFkX25hbWVcIjpcInNlbGYtdGVzdC0yMDI2LTEwLTA5XCIsXCJldmVudHNcIjpbXSxcImhhbmRvZmZfdGV4dFwiOlwiTm8gdmVyaWZpZWQgd29yayBpcyBzYXZlZCBmb3IgdGhpcyBqb2IgeWV0LlxcblJ1biBhIFphbWJvIHRvb2wgd2l0aCB0aGUgc2FtZSBqb2IgSUQgdG8gYWRkIGEgcmVjZWlwdC1iYWNrZWQgc3RlcC5cXG5BIG1hdGNoaW5nIHJlY2VpcHQgc2hvd3MgdGhlIHNhdmVkIHJlY29yZCB3YXMgbm90IGNoYW5nZWQuIEl0IGRvZXMgbm90IHByb3ZlIHRoZSBhbnN3ZXIgaXMgcmlnaHQgb3IgdGhhdCBhbiBvdXRzaWRlIGFjdGlvbiBoYXBwZW5lZC5cXG5BbnkgQUkgY2xpZW50IGxhYmVsIHNob3duIGhlcmUgd2FzIHJlcG9ydGVkIGJ5IHRoZSBjYWxsZXIgYW5kIGlzIG5vdCBpbmRlcGVuZGVudGx5IHZlcmlmaWVkLlwifSIsInB1YmxpY2F0aW9uX25vdGljZSI6IlRoaXMgaXMgYSBuZXdseSBjb21taXR0ZWQgcmVkYWN0ZWQgcHVibGljYXRpb24gY29weSwgbm90IHRoZSBvcmlnaW5hbCB0b29sIG91dHB1dC4gVGhlIG9yaWdpbmFsIGNvbW1pdG1lbnQgaXMgdW5jaGFuZ2VkIGFuZCBpdHMgcHJpdmF0ZSBieXRlcyBhcmUgd2l0aGhlbGQuIiwicmVkYWN0ZWRfcHJvamVjdGlvbiI6dHJ1ZSwic2NoZW1hIjoiemFtYm8ucmVkYWN0ZWQtcmVjZWlwdC1wdWJsaWNhdGlvbi8xIiwic291cmNlX291dHB1dF9oYXNoIjoic2hhMjU2OmJhYmFhOWIzYjAzZDgxMWYyMmVmM2YyMGQ0ODRkOTY4ODc5ZmIzMWUyYzg4NDg0OTY1YzI4MDljMDQ5MjNjNDIiLCJzb3VyY2VfcmVjZWlwdF9pZCI6ImE5MTRlMTY4LTJjMzgtNDUxZS1hNjljLWE3MTEzOGU1YjRkZCIsInNvdXJjZV90b29sIjoiY29udGludWl0eV9vcGVuX3RocmVhZCJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJyZWNlaXB0X3B1YmxpY2F0aW9uIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-11-08T06:45:22.997Z

Bound call context

Receipt schema

0.4

Tool name

receipt_publication

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:8cee6d69cda6473e15da7a7aa6d2220c8e35a06c091f86b4144f186858869cf6

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

empty

Evidence SHA-256

unavailable

Byte length

unavailable

Neutral Nostr anchor

Event ID

015cba02ed8bd4d227e638210c28666ff1ecbe2462307009c6ecc50fee57944f

Anchor status

published

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-08T06:45:22.997Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:253290f4ebcbb33c5ea88ddd24b09f9143d8db73859b8c4439f060b885e2672e","receipt_uuid":"a3a112db-62d4-56ab-a4e9-098d9886bd83","schema_version":"zambo-receipt-anchor/1"}

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

Relay publication is separate from receipt integrity. When the original signed event is available, Zambo retries pending, partial, or failed anchors about once a minute. Relay acknowledgements are external, so there is no guaranteed completion time; the receipt remains checkable from its saved bytes and verification link.

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.