Memory remember · 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-21T04:39:37.959Z; 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

3d5aa4e5-4a99-4f6c-a94b-0226e32d9e94

SHA-256 output hash

sha256:6a57436bd2b79383f93a3e292dfbe2ece035e3042b67d8105e2f7b79b09c1931

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NzBlMmE2MDU5MTNmMjk0M2I0MjA2YmNhYTdiOTRiMGIyMTNkMmJiMWJlMWFjNmI1YmYwZWZkMjZlOGY2YjQ3YSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJzYXZlZFwiLFwiZmFjdF9pZFwiOlwiM2RkYzU2ZGYtOWRhMy00YTc5LWI0YTEtZTcyNTgxMDc5NjRiXCIsXCJmYWN0X2hhc2hcIjpcImViMzY5MGI2MGMyMTE3OGIyMzAyZDNlZWRjNmNhMTY3MmYzMTlmMmU5MmVlZDEwOWMyODM4NDA4ZGI5ZDE3Y2RcIn0iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzb3VyY2VfY29tbWl0bWVudF9jaGVja2VkIjp0cnVlLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6MjMxYzI3MjY2YTE0MTE3MDEzYzA3MmI0YzJmMzhiNzMwNjU5NTlmN2JmYzg1Y2VjYTM4MjU3YWU4NjJjNTllZiIsInNvdXJjZV9yZWNlaXB0X2lkIjoiYjMzMTQ0MjUtZGI1MC00Mzk1LWE2MGQtZThkMjNlMGIxMGVlIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJtZW1vcnlfcmVtZW1iZXIiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-10-21T04:39:37.959Z

Bound call context

Receipt schema

0.4

Tool name

memory_remember

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:70e2a605913f2943b4206bcaa7b94b0b213d2bb1be1ac6b5bf0efd26e8f6b47a

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

e10f8de3749a64dda7fd5f6b08527f0d289b89d1a2330b276daa87f2566e0d83

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-21T04:39:37.959Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:6a57436bd2b79383f93a3e292dfbe2ece035e3042b67d8105e2f7b79b09c1931","receipt_uuid":"3d5aa4e5-4a99-4f6c-a94b-0226e32d9e94","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.