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-30T16:33:55.001Z; 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

104da5dd-b918-49c6-8170-781be52b6d48

SHA-256 output hash

sha256:72d8347526bf78f8031f6a300c94d1c92c8041ddf8f72d4b6ec3abe7f3afc9ac

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MGNhM2ZiMGVlM2U0NTU0MjNmNjUyNWQ4NzM3MGNmZWEyNjUzOWU5OTA2YzkxMTNiNmY1ODk4NDVlNTMwM2JiZSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYXR0ZXN0cyI6IlphbWJvIGF0dGVzdHMgdGhhdCB0aGlzIHJlY29yZCB3YXMgcmVjZWl2ZWQsIHJlZGFjdGVkLCB0aW1lc3RhbXBlZCwgYW5kIGNoYWluZWQuIiwiZG9lc19ub3RfYXR0ZXN0IjoiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLiIsImVudHJ5Ijp7ImNvbXBsZXRlZF9hdCI6IjIwMjYtMTAtMzBUMTY6MzM6NTQuODk5WiIsImRlbGV0ZWQiOmZhbHNlLCJkdXJhdGlvbl9tcyI6MCwiZW50cnlfaGFzaCI6InNoYTI1NjphMDJiODg4NDU1MzhjMjM0YmZkNGExY2E5ODc5ZTIwZTQzMGU2Y2ZhMjc1N2IyZDU2MGUwMDZmNGRiNjNmYTZhIiwiZW50cnlfaWQiOiIwMWZlZTk1My0wNjkwLTQzY2YtYTU1OS1kNjYwMWNiYjA4NWYiLCJleGVjdXRvcl9pZGVudGl0eSI6ImFjY2VwdGFuY2UtcHJvYmUiLCJleHRlcm5hbF9leGVjdXRvciI6bnVsbCwibWV0YWRhdGEiOnt9LCJwcmV2X2hhc2giOm51bGwsInByb3ZlbmFuY2VfY2xhc3MiOiJMT0dHRUQgQlkgQUdFTlQiLCJyZWRhY3RlZF9pbnB1dHNfaGFzaCI6bnVsbCwic2VxdWVuY2UiOjEsInN0YXJ0ZWRfYXQiOiIyMDI2LTEwLTMwVDE2OjMzOjU0Ljg5OVoiLCJ0b29sX25hbWUiOiJleHRlcm5hbF90b29sIn0sInByb3ZlbmFuY2VfY2xhc3MiOiJMT0dHRUQgQlkgQUdFTlQiLCJzdGF0dXMiOiJsb2dnZWQiLCJ2ZXJpZnlfdXJsIjoiaHR0cHM6Ly96YW1iby5kZXYvYXBpL2pvdXJuYWwvW3ByaXZhdGVdL3ZlcmlmeSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiam91cm5hbF9sb2ciLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-10-30T16:33:55.001Z

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:0ca3fb0ee3e455423f6525d87370cfea26539e9906c9113b6f589845e5303bbe

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

08a8fcc3d6c1c46facfa1116d183e47e534015087097c61e84b3d6ec8bee2ee9

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-30T16:33:55.001Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:72d8347526bf78f8031f6a300c94d1c92c8041ddf8f72d4b6ec3abe7f3afc9ac","receipt_uuid":"104da5dd-b918-49c6-8170-781be52b6d48","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.