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-14T22:59:49.388Z; 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

691752ed-73ed-4d30-bcbe-ae4fcc68921d

SHA-256 output hash

sha256:bfd694df61ee89101565b0f7c27bfa641137fbd4d6186b642c753b52f7c873db

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NzM0MGE4MjExMTc2NTgxYmM1MGM0MDhiMzkzYjU3NDk0OGNmZWNiMzczYjRlM2RhN2Q3N2QwOGFlMDZiM2YyMyIsImxhYmVsIjoibW9ybmluZy1sb29wLWRlbW8iLCJsYWJlbF9zb3VyY2UiOiJjYWxsZXJfcmVwb3J0ZWQiLCJ0eXBlIjoic2Vzc2lvbiJ9LCJpc3N1ZXJfY2xhaW1zIjp7InByb3ZlbmFuY2VfY2xhc3MiOiJMT0dHRUQgQlkgQUdFTlQifSwib3V0cHV0Ijp7ImF0dGVzdHMiOiJaYW1ibyBhdHRlc3RzIHRoYXQgdGhpcyByZWNvcmQgd2FzIHJlY2VpdmVkLCByZWRhY3RlZCwgdGltZXN0YW1wZWQsIGFuZCBjaGFpbmVkLiIsImRvZXNfbm90X2F0dGVzdCI6IlphbWJvIGRpZCBub3QgcnVuIG9yIG9ic2VydmUgdGhlIHJlcG9ydGVkIGFjdGlvbi4iLCJlbnRyeSI6eyJjb21wbGV0ZWRfYXQiOiIyMDI2LTExLTE0VDIyOjU5OjQ5LjE4NloiLCJkZWxldGVkIjpmYWxzZSwiZHVyYXRpb25fbXMiOjAsImVudHJ5X2hhc2giOiJzaGEyNTY6MGEzY2QzNTNiYjQxNjk3OTUzNDc2NjIwMTAxYzg0MjJiNmFmNDAxMDFlYTk0YjQ3MDE2OGMxZjQyYTgzNDcyOSIsImVudHJ5X2lkIjoiYzY5OTRlMDAtZjQwYi00ZTA4LWFiZmEtYjM3NzIxZWM5Y2U4IiwiZXhlY3V0b3JfaWRlbnRpdHkiOiJyYW1ibyAobGFuZS1oMSBsb29wLXZvbHVtZSBkZW1vKSIsImV4dGVybmFsX2V4ZWN1dG9yIjpudWxsLCJtZXRhZGF0YSI6e30sInByZXZfaGFzaCI6bnVsbCwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInJlZGFjdGVkX2lucHV0c19oYXNoIjoic2hhMjU2OmNjMGMwZWJiMTNjYmEzY2M0MmRiNTdjODEyODBlOTg3ZTYzMjY5YjVkMzU2OGVkMmVlM2U2NjZlMGVjMmEzNjgiLCJzZXF1ZW5jZSI6MSwic3RhcnRlZF9hdCI6IjIwMjYtMTEtMTRUMjI6NTk6NDkuMTg2WiIsInRvb2xfbmFtZSI6Im1vcm5pbmdfbG9vcF9jaGVja19ydW4ifSwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInN0YXR1cyI6ImxvZ2dlZCIsInZlcmlmeV91cmwiOiJodHRwczovL3phbWJvLmRldi9hcGkvam91cm5hbC9bcHJpdmF0ZV0vdmVyaWZ5In0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJqb3VybmFsX2xvZyIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS40In19

Timestamp

2026-11-14T22:59:49.388Z

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:7340a8211176581bc50c408b393b574948cfecb373b4e3da7d77d08ae06b3f23

Caller-reported label

morning-loop-demo (caller_reported, not authenticated team ownership)

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

b825234743af98bc4377956fec71c1e834bbfc5ddf35fd9195314b43d4c4ce71

Anchor status

published

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-14T22:59:49.388Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:bfd694df61ee89101565b0f7c27bfa641137fbd4d6186b642c753b52f7c873db","receipt_uuid":"691752ed-73ed-4d30-bcbe-ae4fcc68921d","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.