Verifiable receipt 2529b648 - journal_log result | Zambo

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-16T17:11:45.697Z; 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

2529b648-71f2-46fe-9361-a2cc593c3b40

SHA-256 output hash

sha256:9b1ed2116adfc1cb7ac2643b30a1b1d40301367b51043f582f7bc77a0517aaea

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NDYyNDY0YTUyZGRkZWZhNjQ0YWM5ZjFkM2Q0NjE0YzYzZTgwZDk4NzdiOTE2NzM1MzY1NGM4MDg2OWQwMTczZCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYXR0ZXN0cyI6IlphbWJvIGF0dGVzdHMgdGhhdCB0aGlzIHJlY29yZCB3YXMgcmVjZWl2ZWQsIHJlZGFjdGVkLCB0aW1lc3RhbXBlZCwgYW5kIGNoYWluZWQuIiwiZG9lc19ub3RfYXR0ZXN0IjoiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLiIsImVudHJ5Ijp7ImNvbXBsZXRlZF9hdCI6IjIwMjYtMTAtMTZUMTc6MTE6NDUuNTk5WiIsImRlbGV0ZWQiOmZhbHNlLCJkdXJhdGlvbl9tcyI6MCwiZW50cnlfaGFzaCI6InNoYTI1NjpiYWZlNjgyNzM1ZjVjYmYwNDk5YzcyYzRlNzc2NDI2MTc1ODllYTIzMWFlNmRhMTRlMjc4ZDgyMzJhOGRiNDk0IiwiZW50cnlfaWQiOiJlYmM2ODAyNC1lZDNjLTQ5NTctYTU4ZC04ZjQzN2FlMmEyNzEiLCJleGVjdXRvcl9pZGVudGl0eSI6Imdyb2stYm90LWNhcG1hcCIsImV4dGVybmFsX2V4ZWN1dG9yIjpudWxsLCJtZXRhZGF0YSI6e30sInByZXZfaGFzaCI6bnVsbCwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInJlZGFjdGVkX2lucHV0c19oYXNoIjpudWxsLCJzZXF1ZW5jZSI6MSwic3RhcnRlZF9hdCI6IjIwMjYtMTAtMTZUMTc6MTE6NDUuNTk5WiIsInRvb2xfbmFtZSI6InJlc2VhcmNoIn0sInByb3ZlbmFuY2VfY2xhc3MiOiJMT0dHRUQgQlkgQUdFTlQiLCJzdGF0dXMiOiJsb2dnZWQiLCJ2ZXJpZnlfdXJsIjoiaHR0cHM6Ly96YW1iby5kZXYvYXBpL2pvdXJuYWwvW3ByaXZhdGVdL3ZlcmlmeSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiam91cm5hbF9sb2ciLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-10-16T17:11:45.697Z

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:462464a52dddefa644ac9f1d3d4614c63e80d9877b9167353654c80869d0173d

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

806169d15177c24cde517249bba1992c0b75b90d79a8787805019cca045b7c62

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-16T17:11:45.697Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:9b1ed2116adfc1cb7ac2643b30a1b1d40301367b51043f582f7bc77a0517aaea","receipt_uuid":"2529b648-71f2-46fe-9361-a2cc593c3b40","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

API v2 status: verified. This status summarizes the v2 commitment and provenance checks; it does not prove 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.