Pick up where you left off · 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-10-24T22:09:19.911Z; 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

c3665fc3-ec9a-486d-b83a-689f7fe58872

SHA-256 output hash

sha256:147b96b0057115dc1669c7d366b30be632f5e8407b9e134dd932614ca58f180a

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YWY3NjBlMjJhNDlhMGU4YjMyMjEwMWNiOGFiZTc4MmU2ZmJkMjAwMDBkNjk1NTU1YTM4ZjU1YjIyZTY3MWY5YiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJjcmVhdGVkXCIsXCJuYW1lXCI6XCJhaWJ0Yy1uZXdzLXNpZ25hbC1kcmFmdFwiLFwiaW5zdHJ1Y3Rpb25zXCI6XCJVc2UgdGhpcyB0aHJlYWRfaWQgYXMgX3Nlc3Npb25faWQgb24gY2FsbHMgZnJvbSBhbnkgQUkgY2xpZW50LiBLZWVwIHRoZSBwYXJlbnQgam9iIElEIHRvIGxpc3Qgb3IgbWFuYWdlIGl0cyBuYW1lZCB0aHJlYWRzLlwifSIsInJlZGFjdGVkX3Byb2plY3Rpb24iOnRydWUsInNvdXJjZV9jb21taXRtZW50X2NoZWNrZWQiOnRydWUsInNvdXJjZV9vdXRwdXRfaGFzaCI6InNoYTI1Njo0ODM3ZjMxODZlYWM0MzM1ZjYzOTdiMDI4YWMyYzBmN2JjZWI1MmIxNzcyYTdkNjNlZWFhZmFlNzA5YTI0NTQ1Iiwic291cmNlX3JlY2VpcHRfaWQiOiI5ZGEzYzI4YS0xMTY2LTQwYmQtOGFkZi1jNTg3ZjUxMDFhOTEifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImNvbnRpbnVpdHlfc3RhcnRfdGhyZWFkIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-10-24T22:09:19.911Z

Bound call context

Receipt schema

0.4

Tool name

continuity_start_thread

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:af760e22a49a0e8b322101cb8abe782e6fbd20000d695555a38f55b22e671f9b

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

c8e51874076243b235cab9370808a2b51cae18158c7b1ca1bd0c352d8b3179d2

Anchor status

published

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-24T22:09:19.911Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:147b96b0057115dc1669c7d366b30be632f5e8407b9e134dd932614ca58f180a","receipt_uuid":"c3665fc3-ec9a-486d-b83a-689f7fe58872","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

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.