A note in your job log · 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-24T16:25:40.791Z; 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

1f56fe3e-b4f3-40b0-8619-5935741c9a73

SHA-256 output hash

sha256:44fcf8d38ba476e6026e19d9dc15b4bb78c89940301a480faa15747efab4a9c0

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NTk3MGJmYTY5YzhmZGE5MWYxYmZhNDhkODJiNWJlYWUyMmNmNzE0OTJlYzBiMjZjNjRjYjQwMzkyMjgzOTZhNSIsImxhYmVsIjoibXVzZS1kZW1vLXNlc3Npb24iLCJsYWJlbF9zb3VyY2UiOiJjYWxsZXJfcmVwb3J0ZWQiLCJ0eXBlIjoic2Vzc2lvbiJ9LCJpc3N1ZXJfY2xhaW1zIjp7InByb3ZlbmFuY2VfY2xhc3MiOiJMT0dHRUQgQlkgQUdFTlQifSwib3V0cHV0Ijp7ImF0dGVzdHMiOiJaYW1ibyBhdHRlc3RzIHRoYXQgdGhpcyByZWNvcmQgd2FzIHJlY2VpdmVkLCByZWRhY3RlZCwgdGltZXN0YW1wZWQsIGFuZCBjaGFpbmVkLiIsImRvZXNfbm90X2F0dGVzdCI6IlphbWJvIGRpZCBub3QgcnVuIG9yIG9ic2VydmUgdGhlIHJlcG9ydGVkIGFjdGlvbi4iLCJlbnRyeSI6eyJjb21wbGV0ZWRfYXQiOiIyMDI2LTEwLTI0VDE2OjI1OjQwLjcwM1oiLCJkZWxldGVkIjpmYWxzZSwiZHVyYXRpb25fbXMiOjAsImVudHJ5X2hhc2giOiJzaGEyNTY6NTgxYWY2ZmFlYzI0NmIxOWM0NWE3YWI5MWY1OTEwN2MzY2FiODM2OWI1MWFiMTE5OGQwMDJkM2MxMjJhYzhmZSIsImVudHJ5X2lkIjoiYmIwYWJlYzktYjUzYi00MmVkLTk3NGMtOWMwZDIyZTc5NmM0IiwiZXhlY3V0b3JfaWRlbnRpdHkiOiJyYW1ibyAoZGVtbyBzZXNzaW9uIGZvciB0aGUgTXVzZSBjb25uZWN0b3IgcGFnZSkiLCJleHRlcm5hbF9leGVjdXRvciI6bnVsbCwibWV0YWRhdGEiOnsiZmluZGluZyI6IkJUQyDCtyAkNzksNTQ0LjAwIFVTRCIsInByb2JsZW0iOiJjbGllbnQgZGlzcHV0ZXMgdGhlIEJUQyBhbW91bnQgb24gYW4gaW52b2ljZSBpc3N1ZWQgdG9kYXkiLCJzb3VyY2VfcmVjZWlwdCI6Imh0dHBzOi8vemFtYm8uZGV2L3J1bi8yNmIzNTNhOS04ZTM0LTQ4MjAtYTM1MS05YTY1MjA4ZTExYzEifSwicHJldl9oYXNoIjpudWxsLCJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIiwicmVkYWN0ZWRfaW5wdXRzX2hhc2giOm51bGwsInNlcXVlbmNlIjoxLCJzdGFydGVkX2F0IjoiMjAyNi0xMC0yNFQxNjoyNTo0MC43MDNaIiwidG9vbF9uYW1lIjoibGl2ZV9wcmljZSJ9LCJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIiwic3RhdHVzIjoibG9nZ2VkIiwidmVyaWZ5X3VybCI6Imh0dHBzOi8vemFtYm8uZGV2L2FwaS9qb3VybmFsL1twcml2YXRlXS92ZXJpZnkifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImpvdXJuYWxfbG9nIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-10-24T16:25:40.791Z

Bound call context

Receipt schema

0.4

Tool name

journal_log

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:5970bfa69c8fda91f1bfa48d82b5beae22cf71492ec0b26c64cb4039228396a5

Caller-reported label

muse-demo-session (caller_reported, not authenticated team ownership)

Declared side effects

state_write

Side-effects schema

zambo-side-effects/1

Declaration hash

sha256:dfb4412aa429d3ac637a05668c435bcc90a251363fcdd49f7b85ae4ab55b5bc9

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

26d55f33d468e61d6171ec4181fc270e5deeae47c6efd8a0bd6398433cd72570

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-24T16:25:40.791Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:44fcf8d38ba476e6026e19d9dc15b4bb78c89940301a480faa15747efab4a9c0","receipt_uuid":"1f56fe3e-b4f3-40b0-8619-5935741c9a73","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.