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-22T16:28:12.901Z; 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

a5dcfeba-8bdb-4d2f-8871-af982751866a

SHA-256 output hash

sha256:871873f8db23d6ec0d97517a8b79eba73728ff66332863882aca498f040005ae

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZGJlNjBlODhlZWIwODQzMDdkMzI2MDlhNDU0MzZiNzcwMmE1NWEyY2Q3MzZiNzRkNWFjMTgyNWY1N2RjYTgyZiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYXR0ZXN0cyI6IlphbWJvIGF0dGVzdHMgdGhhdCB0aGlzIHJlY29yZCB3YXMgcmVjZWl2ZWQsIHJlZGFjdGVkLCB0aW1lc3RhbXBlZCwgYW5kIGNoYWluZWQuIiwiZG9lc19ub3RfYXR0ZXN0IjoiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLiIsImVudHJ5Ijp7ImNvbXBsZXRlZF9hdCI6IjIwMjYtMTAtMjJUMTY6Mzg6MDAuMDAwWiIsImRlbGV0ZWQiOmZhbHNlLCJkdXJhdGlvbl9tcyI6NTg3MTkzLCJlbnRyeV9oYXNoIjoic2hhMjU2OmI0MzNlYzdiYmVhZTdlMDBhY2RhOWFlYmUyZDc1OTkwNzI2MDMxMmEzYzA5ZGUyMzI3MmJiMGRiNmFkMDE5MWQiLCJlbnRyeV9pZCI6IjlhODg0NjBmLWRmNWUtNDI2MS04MzBlLTNhNmQwZmZmNzg2YSIsImV4ZWN1dG9yX2lkZW50aXR5IjoicmFtYm8iLCJleHRlcm5hbF9leGVjdXRvciI6bnVsbCwibWV0YWRhdGEiOnsiY2hlY2tzIjoiYXV0aG9ycyBtYXRjaDsgbW9kZWxzIG1hdGNoOyB0YXNrIG1hdGNoOyA3MiUgTWlzdHJhbC03QiBhbmQgNzclIEdQVC1PU1MtMjBCIG1hdGNoIGFic3RyYWN0IHZlcmJhdGltIiwic291cmNlIjoiaHR0cHM6Ly9hcnhpdi5vcmcvYWJzLzI2MDMuMjY4MzB2MSJ9LCJwcmV2X2hhc2giOm51bGwsInByb3ZlbmFuY2VfY2xhc3MiOiJMT0dHRUQgQlkgQUdFTlQiLCJyZWRhY3RlZF9pbnB1dHNfaGFzaCI6bnVsbCwic2VxdWVuY2UiOjEsInN0YXJ0ZWRfYXQiOiIyMDI2LTEwLTIyVDE2OjI4OjEyLjgwN1oiLCJ0b29sX25hbWUiOiJhcnhpdl9wcm9tcHRfcmVncmVzc2lvbl9zb3VyY2VfY2hlY2sifSwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInN0YXR1cyI6ImxvZ2dlZCIsInZlcmlmeV91cmwiOiJodHRwczovL3phbWJvLmRldi9hcGkvam91cm5hbC9bcHJpdmF0ZV0vdmVyaWZ5In0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJqb3VybmFsX2xvZyIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-10-22T16:28:12.901Z

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

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

a912fe1a93b6610255b8789f693f2c77016eef16902300223ce0408fc67a8fd8

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-22T16:28:12.901Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:871873f8db23d6ec0d97517a8b79eba73728ff66332863882aca498f040005ae","receipt_uuid":"a5dcfeba-8bdb-4d2f-8871-af982751866a","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.