Dispute Bundle

Simulated. No real agent, store, bank, or standard takes part. The hashes are real SHA-256 in your browser. The signatures are fake.

Press Play or Step.

1. The purchase

2. The dispute desk

Four records link into one bundle that a dispute desk reads Four boxes in a row: the user's mandate, the agent's cart, the merchant's order, and the payment. Arrows join them in order. Lines from each box lead down to one signed bundle bar. An arrow leads from the bar to the dispute desk. The steps light up one at a time. User mandateNike, 120 USD max Agent cartAdidas, 119 USD Merchant order128.99 USD total Payment128.99 USD paid One signed bundle: each block holds the hash of the block before itDispute desk: one view, one verdict
The diagram follows the story. Each step adds one link to the bundle.

What exists today, per public reports

FormatWhat it coversWhat it leaves out

The bundle is a proposal. It does not replace these. It links records from them.

Try this

  1. Press Play. Watch the chat until the user opens a dispute.
  2. Read the desk with Without bundle. Count the formats and shared ids.
  3. Press With bundle. Tick the box that edits the merchant record. See the chain break.

Pain point

Five parties cannot agree on what an agent was allowed to buy when something goes wrong.

Problem statement

Each of five parties keeps its own record in its own format. A dispute team must collect and compare them all.

What sparked it

Per public reports on 2026-10-22, US banks detect and delete third-party AI agents in customer accounts. A PNC executive asked for authentication and liability law.

Why this approach

The mandate, cart, order, and payment link into one signed bundle. A dispute desk reads it in one view.

Hypothesis tested

We believed that one linked bundle lets a dispute desk read a case in one view. If it holds, card networks could ask for a bundle on the lighter dispute path.

How to try it

  1. Open the Prototype tab. Press Play, or Step.
  2. Read the desk under Without bundle.
  3. Press With bundle and read the verdict table.
  4. Edit the merchant record. Find the block that breaks.

What this does not do

Sources

Notes

Traces

Prompts used to make this prototype
StepPromptModelToolDate

Cost

Cost to make this prototype
StepModelInput tokensOutput tokensCost (USD)
Total

Measured: the author runs used 120,733 tokens in total. Estimated: the split into input and output tokens (90 percent input, 10 percent output) and the dollar cost, at $2 input and $10 output per million tokens for Sonnet 5.5 (about $0.34). The run reported one total only. The lead session's planning, research, and publishing are not included. The prompts in the Traces section are listed in the order they were given.