Does a workflow receipt change the receipts for its steps?

No. Each step keeps its own ordinary execution receipt. The workflow receipt references the step receipt hashes and commits to them together.

Are individual workflow pages public?

Individual workflow pages are session-scoped records marked noindex. The noindex directive controls search indexing, not access; this definition page is the public explanation.

AI workflow verification

What Is a Workflow Receipt?

Q: What is a workflow receipt?

A workflow receipt is a record for a multi-step AI workflow. It links the hashes of the individual step receipts into a Merkle tree and publishes the root for independent verification.

Q: How does browser verification work?

The Verify control fetches each step's canonical receipt again, rebuilds the Merkle tree in the browser, and checks the result against the published workflow root.

Last updated: 2026-09-25

A workflow receipt makes a multi-step AI workflow checkable as a whole without changing the ordinary receipts produced by its individual steps.

Short answer:

A workflow receipt commits to the ordered hashes of the receipts created by each step. It organizes those hashes in a Merkle tree and publishes one root that can be checked independently.

How the workflow receipt fits together

Think of each unchanged step receipt as a line item. The workflow receipt is the invoice that commits to those line items through a single Merkle root. It adds a workflow-level integrity check while keeping the step records intact.

Step receipts

Each executed step retains its own canonical receipt and observed result.

Merkle tree

The workflow links the ordered step receipt hashes into a tree.

Published root

The root commits to the workflow's step evidence for independent checks.

Verify the root in the browser

The workflow page's Verify control fetches each step's canonical receipt again, rebuilds the Merkle tree in the browser, and compares the computed root with the published root. A match confirms that the presented workflow manifest agrees with the retrieved step receipts. It does not claim that an external side effect happened unless that effect has its own observed evidence.

Workflow pages and indexing

Individual /workflow/<id> pages are session-scoped records marked noindex. That directive controls search indexing; it is not access control. This page is the public, indexable definition of the format.

Frequently asked questions

Does a workflow receipt replace a step receipt?

No. Each step keeps its own ordinary execution receipt. The workflow receipt references their hashes and provides a commitment to the workflow as a whole.

Can someone recompute the workflow root?

Yes. The step receipts can be fetched and their hashes organized into the same Merkle tree. The browser Verify control performs that check without relying on a server-side success label.

Does the root prove every claimed outcome?

No. It verifies the relationship between the workflow manifest and its step receipts. Claims about an outside effect still need corresponding observed evidence.