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-05T15:23:26.396Z; 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

0408f1e7-a847-4466-9f42-4a1b47fecd2e

SHA-256 output hash

sha256:1faaec65853c51cc32dbf1b6f221bcc2050f9e75fae4313a46a972ba2913f519

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MTNmMmRjNzM1OTk0NTRiZDc1ZDBmMThjMTI2ZjIxZjBkZDU1ODFjZGZiZDg4ZDVhY2ZhOTg5MjA4ZTE2M2JmYSIsImxhYmVsIjoibGVhay0xMTA1LXdhbGwyIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIn0sIm91dHB1dCI6eyJhdHRlc3RzIjoiWmFtYm8gYXR0ZXN0cyB0aGF0IHRoaXMgcmVjb3JkIHdhcyByZWNlaXZlZCwgcmVkYWN0ZWQsIHRpbWVzdGFtcGVkLCBhbmQgY2hhaW5lZC4iLCJkb2VzX25vdF9hdHRlc3QiOiJaYW1ibyBkaWQgbm90IHJ1biBvciBvYnNlcnZlIHRoZSByZXBvcnRlZCBhY3Rpb24uIiwiZW50cnkiOnsiY29tcGxldGVkX2F0IjoiMjAyNi0xMS0wNVQxNToyMzoyNi4yMDNaIiwiZGVsZXRlZCI6ZmFsc2UsImR1cmF0aW9uX21zIjowLCJlbnRyeV9oYXNoIjoic2hhMjU2OjljMmExOTM3NWIyNjE3Yzk5Y2RjMDgzMmQwM2JhNmY0ZDA5NmQ1OTVmNTM0MTZjMWI5NWUzMzJkOTEzMmM2Y2EiLCJlbnRyeV9pZCI6IjliNjExYzcxLWViODAtNGQwNC04NjczLTRjNDI0ODE1ZGYxYyIsImV4ZWN1dG9yX2lkZW50aXR5IjoibGVhay0xMTA1LXdhbGwyIiwiZXh0ZXJuYWxfZXhlY3V0b3IiOm51bGwsIm1ldGFkYXRhIjp7fSwicHJldl9oYXNoIjoic2hhMjU2OmNlMzg5ZWM1MWNlMWUyMGI3OTVmODk0MTFkMzgzMTZlYWQyMmQ2OWI3ZTQxYWY5ZTI1OTcxNzNmNTg5ZWMwZDAiLCJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIiwicmVkYWN0ZWRfaW5wdXRzX2hhc2giOm51bGwsInNlcXVlbmNlIjoxMCwic3RhcnRlZF9hdCI6IjIwMjYtMTEtMDVUMTU6MjM6MjYuMjAzWiIsInRvb2xfbmFtZSI6IncxOSJ9LCJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIiwic3RhdHVzIjoibG9nZ2VkIiwidmVyaWZ5X3VybCI6Imh0dHBzOi8vemFtYm8uZGV2L2FwaS9qb3VybmFsL1twcml2YXRlXS92ZXJpZnkifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImpvdXJuYWxfbG9nIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-11-05T15:23:26.396Z

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:13f2dc73599454bd75d0f18c126f21f0dd5581cdfbd88d5acfa989208e163bfa

Caller-reported label

leak-1105-wall2 (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

empty

Evidence SHA-256

unavailable

Byte length

unavailable

Upstream provenance

This receipt is independently auditable against the named upstream source. This is not a mathematical correctness claim.

• Source: · queried at: · raw response hash:

Neutral Nostr anchor

Event ID

6071f4a2067cb79399d1869a78ec3b77fbf8ba219a5211cdf7e664ca39a73379

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-11-05T15:23:26.396Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:1faaec65853c51cc32dbf1b6f221bcc2050f9e75fae4313a46a972ba2913f519","receipt_uuid":"0408f1e7-a847-4466-9f42-4a1b47fecd2e","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.