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-14T16:10:54.933Z; 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

b862cc95-9d3a-41cb-b99b-3be4daa36d52

SHA-256 output hash

sha256:d90b7ff1f0896c69f30bca45149d710a7e3a19ed146cb57e8ab4fd5daa5f92c8

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZDUyMDQzMGY4NTJhMzk2ZWE4ZDI4ODU5ZDA3MzI4ZjA5ZjI5Yjg4MzMwNDYyYWY2NzFjYWY0YWQ4NTQyZTcwZSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYXR0ZXN0cyI6IlphbWJvIGF0dGVzdHMgdGhhdCB0aGlzIHJlY29yZCB3YXMgcmVjZWl2ZWQsIHJlZGFjdGVkLCB0aW1lc3RhbXBlZCwgYW5kIGNoYWluZWQuIiwiZG9lc19ub3RfYXR0ZXN0IjoiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLiIsImVudHJ5Ijp7ImNvbXBsZXRlZF9hdCI6IjIwMjYtMTEtMTRUMTY6MTA6NTQuNjA4WiIsImRlbGV0ZWQiOmZhbHNlLCJkdXJhdGlvbl9tcyI6MCwiZW50cnlfaGFzaCI6InNoYTI1Njo3YTMyZWVjZjRkNGNiMzY2NzkzMDllZjIzZjI2MjU3M2RiMzEyMTM5YzFiNzc1NDUwNTg1NzAxNDFiYjg5ZmI3IiwiZW50cnlfaWQiOiIyYWNlYWViOC1mZjIzLTQ1ZGUtYjJiMy03ZGI1MTdlN2VlOTQiLCJleGVjdXRvcl9pZGVudGl0eSI6InBlcnNvbmEtZ2F1bnRsZXQtZXhlY3V0b3IiLCJleHRlcm5hbF9leGVjdXRvciI6bnVsbCwibWV0YWRhdGEiOnsiY3VzdG9tZXIiOiJOb3J0aGdhdGUgRGVudGFsIiwiY3VzdG9tZXJfa2V5IjoiTkQtMjA3In0sInByZXZfaGFzaCI6InNoYTI1NjphZTEzYzNiZGFmODliMWU2NzZkNWI0NjE3MzhhZGQyYjRlMjYwNzg0NzIzYmM2ZDhiZDUxNzdjMWE2OWY1YjgzIiwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInJlZGFjdGVkX2lucHV0c19oYXNoIjoic2hhMjU2OmIwYTM5YzdmNTcyN2NiZGRkNGQ4NTc0Zjk0NTdhYjhjZTNmOWU4OTEyOGE3Y2Q2YTMxMWNkMDdkNTllNTcxNjciLCJzZXF1ZW5jZSI6Miwic3RhcnRlZF9hdCI6IjIwMjYtMTEtMTRUMTY6MTA6NTQuNjA4WiIsInRvb2xfbmFtZSI6InNlbmQgc2VydmljZSBjaGVjayBmb2xsb3ctdXAifSwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInN0YXR1cyI6ImxvZ2dlZCIsInZlcmlmeV91cmwiOiJodHRwczovL3phbWJvLmRldi9hcGkvam91cm5hbC9bcHJpdmF0ZV0vdmVyaWZ5In0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJqb3VybmFsX2xvZyIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS40In19

Timestamp

2026-11-14T16:10:54.933Z

Bound call context

Receipt schema

0.4

Tool name

journal_log

Tool version

4.1.4

Permission scope

public

Caller type

session

Caller ID

sha256:d520430f852a396ea8d28859d07328f09f29b88330462af671caf4ad8542e70e

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

2c3ad1004278d1a05c24d08b0529c9dd315769a1d12a19e5c76056f6c6978891

Anchor status

published

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-14T16:10:54.933Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:d90b7ff1f0896c69f30bca45149d710a7e3a19ed146cb57e8ab4fd5daa5f92c8","receipt_uuid":"b862cc95-9d3a-41cb-b99b-3be4daa36d52","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.