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-05T01:51:52.915Z; 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

f6113b0e-a7c5-491a-9ed3-c8ada57155b0

SHA-256 output hash

sha256:2f496bffbfc4023ea2457c1a13921c3a1f9b454c7351c54025a840209e15ce9e

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MDZmYjEzOWFmMWE3Y2NkMjRiMjNmYzc1MjAzNDUxYTU3OTZjODVmNmQzZTc5OTQyMDllYjI0ZTQ2NjcwYjE2YSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYXR0ZXN0cyI6IlphbWJvIGF0dGVzdHMgdGhhdCB0aGlzIHJlY29yZCB3YXMgcmVjZWl2ZWQsIHJlZGFjdGVkLCB0aW1lc3RhbXBlZCwgYW5kIGNoYWluZWQuIiwiZG9lc19ub3RfYXR0ZXN0IjoiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLiIsImVudHJ5Ijp7ImNvbXBsZXRlZF9hdCI6IjIwMjYtMTEtMDVUMDE6NTE6NTIuODIxWiIsImRlbGV0ZWQiOmZhbHNlLCJkdXJhdGlvbl9tcyI6MCwiZW50cnlfaGFzaCI6InNoYTI1NjoyZDMyZThmMWRkYmM3ZGNiODVmNDI5ODFmYWRiMGNmYTk4MTVkMDJmNjgzMjQwZjgwZjIwM2IwMmI2MzgxNTM5IiwiZW50cnlfaWQiOiI1OTJjOGQ4My0xYTQ4LTQ4ZTktODYxYi0xY2NiNTA3M2Y4YmIiLCJleGVjdXRvcl9pZGVudGl0eSI6Imhlcm1lcy1zbW9rZS0wODE5NTQiLCJleHRlcm5hbF9leGVjdXRvciI6Imhlcm1lcy1zbW9rZS0wODE5NTQiLCJtZXRhZGF0YSI6eyJkdXJhdGlvbl9tcyI6MTgsImhlcm1lc190b29sIjoid3JpdGVfZmlsZSIsInJlc3VsdF9ieXRlcyI6MTUsInJlc3VsdF9zaGEyNTYiOiIyMzFmZWYxY2E2NmYyZTZiNTRkMjljMmY4ODdkMDM0OTJiNDNmMjM2ODk0MGEwZDc4ZDdkNTNmNzEzODg0NDRjIn0sInByZXZfaGFzaCI6InNoYTI1NjoyNzU4NzRiMjYxMjk2MGY3NmY5MzM0MTc4ZTgzZDVlNjQ5ZmM1NWZlNTg3YmM5YWU4ZjI0MzFlYTQ2YjQyYzMyIiwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInJlZGFjdGVkX2lucHV0c19oYXNoIjpudWxsLCJzZXF1ZW5jZSI6Mywic3RhcnRlZF9hdCI6IjIwMjYtMTEtMDVUMDE6NTE6NTIuODIxWiIsInRvb2xfbmFtZSI6IndyaXRlX2ZpbGUifSwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInN0YXR1cyI6ImxvZ2dlZCIsInZlcmlmeV91cmwiOiJodHRwczovL3phbWJvLmRldi9hcGkvam91cm5hbC9bcHJpdmF0ZV0vdmVyaWZ5In0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJqb3VybmFsX2xvZyIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-11-05T01:51:52.915Z

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:06fb139af1a7ccd24b23fc75203451a5796c85f6d3e7994209eb24e46670b16a

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

779c62ff568b109b8493720cebccf4124c7e5ee0af4c00397abeea8d538f6e5d

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-05T01:51:52.915Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:2f496bffbfc4023ea2457c1a13921c3a1f9b454c7351c54025a840209e15ce9e","receipt_uuid":"f6113b0e-a7c5-491a-9ed3-c8ada57155b0","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.