Verifiable receipt ae2c069d - 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-20T18:58:22.268Z; 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

ae2c069d-bfb8-4cb8-914b-6ace413855c6

SHA-256 output hash

sha256:3c03fd6f346bb1aa2541a7b2d8280110305b3173817539826b5c2fecd767e018

Canonical bytes

eyJjYWxsZXIiOnsiYmFzaXMiOiJpcF91YV8zMGQiLCJpZCI6InNoYTI1NjpmMzEwZDljYTNmNWJlYWU4N2NkODU3MTBiNmIwNjAwMzBkYjVkYzY3NThlNmVlZjgxZmNkZjgwOGJmZTc1ZGZkIiwicm90YXRlc19hdCI6IjIwMjYtMTEtMDNUMDA6MDA6MDAuMDAwWiIsInR5cGUiOiJhbm9ueW1vdXMifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIn0sIm91dHB1dCI6eyJhdHRlc3RzIjoiWmFtYm8gYXR0ZXN0cyB0aGF0IHRoaXMgcmVjb3JkIHdhcyByZWNlaXZlZCwgcmVkYWN0ZWQsIHRpbWVzdGFtcGVkLCBhbmQgY2hhaW5lZC4iLCJkb2VzX25vdF9hdHRlc3QiOiJaYW1ibyBkaWQgbm90IHJ1biBvciBvYnNlcnZlIHRoZSByZXBvcnRlZCBhY3Rpb24uIiwiZW50cnkiOnsiY29tcGxldGVkX2F0IjoiMjAyNi0xMC0yMFQxODo1ODowMC4wMDBaIiwiZGVsZXRlZCI6ZmFsc2UsImR1cmF0aW9uX21zIjo2MDAwMCwiZW50cnlfaGFzaCI6InNoYTI1NjozOWM1NDFlMThmZjE1ZTg2MTBhMjM5MTVmYzQ2Y2QyYmU5ZjE5YjBlYTM0M2ZlYzZhNjg3NjQ1MjFkYjRiNzkzIiwiZW50cnlfaWQiOiJkYTlmNDQ0MS0wNDhmLTRmNDgtODA1YS04MjE1MmQ4NzM1MDkiLCJleGVjdXRvcl9pZGVudGl0eSI6InJhbWJvICh6YW1ibyBvcHMpIiwiZXh0ZXJuYWxfZXhlY3V0b3IiOm51bGwsIm1ldGFkYXRhIjp7fSwicHJldl9oYXNoIjoic2hhMjU2OjZhMDk5MmFhZDcyMjgwNzg2MzYxYTczZGNmMTA0MDdiOWU1ZTI0YjQ3YjgwZWE0M2QxZWUxMjczMWFmZjg0MTYiLCJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIiwicmVkYWN0ZWRfaW5wdXRzX2hhc2giOiJzaGEyNTY6MjlkZTk0MGQ4ZTViNzY4ODAzOTU2ZDJjNDc1MGE4ODY1MTA5NDI0NWRlZjc3ZDJlMTI2ZDYxNDg5Yzc2Mjk3MCIsInNlcXVlbmNlIjoyLCJzdGFydGVkX2F0IjoiMjAyNi0xMC0yMFQxODo1NzowMC4wMDBaIiwidG9vbF9uYW1lIjoiZnJhbnRpYy1ib2FyZC1yZXJlYWQifSwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInN0YXR1cyI6ImxvZ2dlZCIsInZlcmlmeV91cmwiOiJodHRwczovL3phbWJvLmRldi9hcGkvam91cm5hbC9bcHJpdmF0ZV0vdmVyaWZ5In0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJqb3VybmFsX2xvZyIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-10-20T18:58:22.268Z

Bound call context

Receipt schema

0.4

Tool name

journal_log

Tool version

4.0.0

Permission scope

public

Caller type

anonymous

Caller ID

sha256:f310d9ca3f5beae87cd85710b6b060030db5dc6758e6eef81fcdf808bfe75dfd

Caller basis

ip_ua_30d

Caller rotates at

2026-11-03T00:00:00.000Z

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

f11c6c262b74f1732433618152c0d199f0a7ef894f1268cb83412c5d6133da5c

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-20T18:58:22.268Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:3c03fd6f346bb1aa2541a7b2d8280110305b3173817539826b5c2fecd767e018","receipt_uuid":"ae2c069d-bfb8-4cb8-914b-6ace413855c6","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.