Verifiable receipt 28a2e92b - sample_job_draft 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-18T15:07:20.501Z; 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

28a2e92b-a1a4-4dbd-9849-4fda7eaaea3d

SHA-256 output hash

sha256:223220d9a031ee57d95ec4ace9de250c2be818817f5df3110a402fdc01510f94

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ODc5ZTEyMGMxZGQ3NGZlNTM0MjUyOGY0Mzk4ZDYyNjRiN2RjYWFhNzRjZTJlMWM3ZWE1NjFlNDAzM2I4NTIzYiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic2FtcGxlXCI6dHJ1ZSxcInRleHRcIjpcIlNhbXBsZSBkcmFmdDogV2VsY29tZSEgSGVyZSBpcyB5b3VyIGdldHRpbmctc3RhcnRlZCBjaGVja2xpc3QuXCIsXCJjbGFpbVwiOlwiU3VwcGxpZWQgc2FtcGxlIHRleHQsIG5vdCBpbmRlcGVuZGVudGx5IGV4ZWN1dGVkIG9yIGNoZWNrZWQuXCJ9IiwicmVkYWN0ZWRfcHJvamVjdGlvbiI6dHJ1ZSwic291cmNlX2NvbW1pdG1lbnRfY2hlY2tlZCI6dHJ1ZSwic291cmNlX291dHB1dF9oYXNoIjoic2hhMjU2OjY4NzhkYTliNWNjM2NmYjJhNTU4M2RhYzVlMjY0MGUxODZkYTJkMGFkMmUyZDkzYjkxZjI0NDBjZTBlZGViNTciLCJzb3VyY2VfcmVjZWlwdF9pZCI6ImYzNTlkNDczLTEzYTctNDk4Yi05YzNkLWE2OTM3MDVkZmQzOCJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJzYW1wbGVfam9iX2RyYWZ0Iiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-10-18T15:07:20.501Z

Bound call context

Receipt schema

0.4

Tool name

sample_job_draft

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:879e120c1dd74fe5342528f4398d6264b7dcaaa74ce2e1c7ea561e4033b8523b

Declared side effects

none

Side-effects schema

zambo-side-effects/1

Declaration hash

sha256:45aad38f3aa982b9aafe92ecb416ebe98791eddbaf8ab6df0bd08605b7c1bfee

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

b55b0bf5d4c8e94236f0918ec3fd4bcf057de90244a92c76a9a6b82902d7e8bd

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-18T15:07:20.501Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:223220d9a031ee57d95ec4ace9de250c2be818817f5df3110a402fdc01510f94","receipt_uuid":"28a2e92b-a1a4-4dbd-9849-4fda7eaaea3d","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.