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-11-07T19:50:14.916Z; 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

f7a364a8-595f-4fec-8ea7-ec2169ad7a44

SHA-256 output hash

sha256:04e715863026d00c539de6df5ffbf1ae683a64f80549a81217f0c5f1ff1d3318

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MzAyZTg3N2UyNzI2OTJlMDQ2NDk4ZjNkNmUwY2Q0MjIyYTVhODI5MzkwZThiNzk5MzY1MjZjOWEzZGZkZWJiZSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJzYXZlZFwiLFwiZmFjdF9pZFwiOlwiMWJjZTI1NDktZDBlNy00OGFmLWFkZmYtYzU4NWIyZWQzYjRkXCIsXCJmYWN0X2hhc2hcIjpcImFkYTBiOTZkOTUxODg3Mzk3NWY3OTA5NDc0ODYwZDliMjk0NjVhNTkwMzZmOGNiOGM0MTZmNmE4ZWUzNjY2NjNcIn0iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzb3VyY2VfY29tbWl0bWVudF9jaGVja2VkIjp0cnVlLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6ZmIzMmRmZjM3ZTM1YzEzYzI5ZmQ2ZGRlYjBiMDQ1N2M1YjZhMmFhYjc3ZWM3YmFlYzUwNGFlY2RmNjI3NWYxOSIsInNvdXJjZV9yZWNlaXB0X2lkIjoiMjRkMTg5MzAtZjRiYi00N2NlLTk5NzMtZWZmMDhkOGZjNzJlIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJtZW1vcnlfcmVtZW1iZXIiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-11-07T19:50:14.916Z

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:302e877e272692e046498f3d6e0cd4222a5a829390e8b79936526c9a3dfdebbe

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

Neutral Nostr anchor

Event ID

a51d88c7c76e4b12abb35b0f2a189a381c03745b7d81e8e2d5ff90894a9a7782

Anchor status

published

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-07T19:50:14.916Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:04e715863026d00c539de6df5ffbf1ae683a64f80549a81217f0c5f1ff1d3318","receipt_uuid":"f7a364a8-595f-4fec-8ea7-ec2169ad7a44","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.