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-11-08T22:39:44.384Z; 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

cf12cecd-7020-4e77-9b38-2e6afd2fcb66

SHA-256 output hash

sha256:392ad5313b1c7993cf05a8d57da0a59e7ad14ba60c009d981a7a2a5a51048ead

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NmFkNWM4NDMxNzFkN2U1NTA4MTRhOGNlNjBlYWYwNzhjNzcwYTYxMDc3MWE4YzFjNzNlOTQ4MTI4ZjVjMDVjMCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJsb2dnZWRcIixcInByb3ZlbmFuY2VfY2xhc3NcIjpcIkxPR0dFRCBCWSBBR0VOVFwiLFwiZW50cnlcIjp7XCJlbnRyeV9pZFwiOlwiNTljMGNmNDQtNTYzNi00YzY2LThhNjgtMzAwZGFkZTczYzkzXCIsXCJzZXF1ZW5jZVwiOjEsXCJwcm92ZW5hbmNlX2NsYXNzXCI6XCJMT0dHRUQgQlkgQUdFTlRcIixcInRvb2xfbmFtZVwiOlwibGl2ZV9wcmljZVwiLFwicmVkYWN0ZWRfaW5wdXRzX2hhc2hcIjpudWxsLFwic3RhcnRlZF9hdFwiOlwiMjAyNi0xMS0wOFQyMjozOTozNC4yNzlaXCIsXCJjb21wbGV0ZWRfYXRcIjpcIjIwMjYtMTEtMDhUMjI6Mzk6MzQuMjc5WlwiLFwiZHVyYXRpb25fbXNcIjowLFwiZXhlY3V0b3JfaWRlbnRpdHlcIjpcInJhbWJvXCIsXCJleHRlcm5hbF9leGVjdXRvclwiOm51bGwsXCJtZXRhZGF0YVwiOnt9LFwicHJldl9oYXNoXCI6bnVsbCxcImVudHJ5X2hhc2hcIjpcInNoYTI1NjpmNTA3YzZmN2VkYWRjNDAwYzJiZmE1YzU0MWNlMDQzYTYxZDg4NWI1OWQ0NTYzMmNiMDBhYTRiZGFiYjBjMTBiXCIsXCJkZWxldGVkXCI6ZmFsc2V9LFwiYXR0ZXN0c1wiOlwiWmFtYm8gYXR0ZXN0cyB0aGF0IHRoaXMgcmVjb3JkIHdhcyByZWNlaXZlZCwgcmVkYWN0ZWQsIHRpbWVzdGFtcGVkLCBhbmQgY2hhaW5lZC5cIixcImRvZXNfbm90X2F0dGVzdFwiOlwiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLlwiLFwidmVyaWZ5X3VybFwiOlwiaHR0cHM6Ly96YW1iby5kZXYvYXBpL2pvdXJuYWwvW3ByaXZhdGVdL3ZlcmlmeVwifSIsInJlZGFjdGVkX3Byb2plY3Rpb24iOnRydWUsInNvdXJjZV9jb21taXRtZW50X2NoZWNrZWQiOnRydWUsInNvdXJjZV9vdXRwdXRfaGFzaCI6InNoYTI1Njo4YWIzNGY1ZTk3OTVlNWM5ZDMyZDM2MTk2NWRlYWRjYzc0MTU5MThhYmRhNzRmMTcwN2ZjOWM4YTFhZDRhYmVlIiwic291cmNlX3JlY2VpcHRfaWQiOiI3NjQwZDQyYS01ODVjLTQ4YmEtYThlNi0xMjE0ZjU1NDY3ZTUifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImpvdXJuYWxfbG9nIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-11-08T22:39:44.384Z

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:6ad5c843171d7e550814a8ce60eaf078c770a610771a8c1c73e948128f5c05c0

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

empty

Evidence SHA-256

unavailable

Byte length

unavailable

Neutral Nostr anchor

Event ID

fe077ce61e3d67545e458c840fca88e537a348f6dbd918be562097b5fea2c038

Anchor status

published

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-08T22:39:44.384Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:392ad5313b1c7993cf05a8d57da0a59e7ad14ba60c009d981a7a2a5a51048ead","receipt_uuid":"cf12cecd-7020-4e77-9b38-2e6afd2fcb66","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.