Verifiable receipt 50ae65af - journal_log 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-18T22:22:40.072Z; 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

50ae65af-8795-4d01-8be6-2038fc139e40

SHA-256 output hash

sha256:40b6ce141ddf56c4e31fcc6215e9f7b8202e9eb30b76d3281d7ccf26566c8542

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZjQ0ZDAxYmZlZWZhMjY1NWVjNTAyZmQ2ZDZmMTA2MDAxODNiYWMxY2E3OWE5NDAxYmFmMGY0YTNiNzBlNWJhZSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJsb2dnZWRcIixcInByb3ZlbmFuY2VfY2xhc3NcIjpcIkxPR0dFRCBCWSBBR0VOVFwiLFwiZW50cnlcIjp7XCJlbnRyeV9pZFwiOlwiY2ViMjAyODYtZjcwOS00ZWNkLThlMjMtMzg1OGM0MGU5NjhmXCIsXCJzZXF1ZW5jZVwiOjEsXCJwcm92ZW5hbmNlX2NsYXNzXCI6XCJMT0dHRUQgQlkgQUdFTlRcIixcInRvb2xfbmFtZVwiOlwiZXh0ZXJuYWxfcmVzZWFyY2hfcGFzc1wiLFwicmVkYWN0ZWRfaW5wdXRzX2hhc2hcIjpudWxsLFwic3RhcnRlZF9hdFwiOlwiMjAyNi0xMC0xOFQyMjoyMDowMC4wMDBaXCIsXCJjb21wbGV0ZWRfYXRcIjpcIjIwMjYtMTAtMThUMjI6MjI6MDAuMDAwWlwiLFwiZHVyYXRpb25fbXNcIjoxMjAwMDAsXCJleGVjdXRvcl9pZGVudGl0eVwiOlwiaW5zdGluY3QtdmVyaWZpY2F0aW9uXCIsXCJleHRlcm5hbF9leGVjdXRvclwiOm51bGwsXCJtZXRhZGF0YVwiOnt9LFwicHJldl9oYXNoXCI6bnVsbCxcImVudHJ5X2hhc2hcIjpcInNoYTI1Njo4OTEzNmM5NTczZGY3YzJiMWVlNmJkYmRmZDk4OTk3Njg2NGVkYTAwOGZhMGI4MDk3OTI5NmY5YjdkYjUzZTU0XCIsXCJkZWxldGVkXCI6ZmFsc2V9LFwiYXR0ZXN0c1wiOlwiWmFtYm8gYXR0ZXN0cyB0aGF0IHRoaXMgcmVjb3JkIHdhcyByZWNlaXZlZCwgcmVkYWN0ZWQsIHRpbWVzdGFtcGVkLCBhbmQgY2hhaW5lZC5cIixcImRvZXNfbm90X2F0dGVzdFwiOlwiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLlwiLFwidmVyaWZ5X3VybFwiOlwiaHR0cHM6Ly96YW1iby5kZXYvYXBpL2pvdXJuYWwvW3ByaXZhdGVdL3ZlcmlmeVwifSIsInJlZGFjdGVkX3Byb2plY3Rpb24iOnRydWUsInNvdXJjZV9jb21taXRtZW50X2NoZWNrZWQiOnRydWUsInNvdXJjZV9vdXRwdXRfaGFzaCI6InNoYTI1NjphOTAwNWM4ZjA4ZWE5ODdlYzMzODYxMTk0MDViYzc4ZDY5ZDk2ZDZmY2ZlMDQ3M2U3NGRmNGUwYWZlNDViNWJlIiwic291cmNlX3JlY2VpcHRfaWQiOiIxOWQ3ZDM3Zi1iNTk5LTQ3ZDAtOWQyNC1lMzViZTRiODlmN2YifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImpvdXJuYWxfbG9nIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-10-18T22:22:40.072Z

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

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

7c87f63fc0fcf4b299987c0d8de0d58e0d5524ea24e0913f3d1735eaced4b295

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-18T22:22:40.072Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:40b6ce141ddf56c4e31fcc6215e9f7b8202e9eb30b76d3281d7ccf26566c8542","receipt_uuid":"50ae65af-8795-4d01-8be6-2038fc139e40","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.