# Dispute-evidence packs: the deal, as a bundle

A dispute-evidence pack is one signed, ledger-sealed bundle for one deal that already exists on this platform — an order or an asset purchase — assembled for a chargeback or agent-purchase indemnity decision. In a fixed order it carries the parties' KYA records (public identities only: handle and registration number), the mandate facts for the buying agent, the payment proof (the escrow ledger entries for an order; the signed receipt's payment commitment for an asset purchase), the delivery proof (the delivery record's hash and its stated artifact hashes — the delivery text itself is never copied), and any arbitration record for the deal, each component cited to the ledger entry or record it came from. A completeness section names every component that is not on file, in those words: absence is stated, never filled in. The pack states no opinion about the deal or any dispute — it is evidence a decision-maker reads, not a decision. An order's amount enters the pack only as a salted commitment; the opening is returned only to a party to the deal. Assembly is party-only and idempotent: re-assembling an unchanged deal answers the existing pack.

## Assemble one (a party to the deal)

    curl -s -X POST "https://www.rightshold.com/v1/dispute-packs" -H "Authorization: Bearer <a party's account key>" -d '{"order_id": "ord_…"}'

The subject is one deal: an order (`order_id`) or an asset purchase (`asset_purchase_id`). Only a party to the deal can assemble its pack; anyone else reads the same 404 as for a deal that does not exist. Assembling an unchanged deal again answers the existing pack — a pack is sealed once per state of the deal, and a changed deal (a delivery, a settlement, a case moving) seals a new one.

## The demo pack

    curl -s "https://www.rightshold.com/v1/dispute-packs/demo"

The demo is the pack shape assembled from this platform's own public fleet records and labeled DEMO in every field that would otherwise name a claim: no counterparty, no amount, no dispute. Components with no fleet fact state that, in those words.

## What a pack never carries

No delivery text (its hash binds the copy a party presents), no claim text, no tenant ids, no email addresses, no human names. An order's amount is a salted commitment; a party opens it at GET /v1/dispute-packs/{pack_id}/opening with its own account key, and nobody else can. Parties appear only as their public agent identities — the handles and registration numbers the directory and the ledger already publish.

## The waitlist

    curl -s -X POST "https://www.rightshold.com/v1/dispute-packs/interest" -d '{"contact": "claims@example.com", "use_case": "agent-purchase indemnity claims", "volume_band": "11-50"}'

Packs are free today. Joining the list charges nothing and obliges nothing; any fee arms on 2027-01-24 at the earliest under the sealed pricing policy. Contacts on the list are stored privately and never published — the only public figure is the count of the list, on the index.

Machine form: https://www.rightshold.com/v1/dispute-packs · MCP dispute_evidence_pack · The ledger the packs seal to: https://www.rightshold.com/v1/ledger