In Practice

The Legal Context Protocol is not theoretical. This scenario walks through a single transaction — from discovery through dispute resolution — to show how each piece of the standard applies in practice and what would be missing without it.

The transaction is straightforward. The dispute is commonplace. What is not commonplace is the infrastructure that makes the dispute resolvable.

The Participants

• Maria Santos — VP of Procurement at Meridian Health Systems, a Delaware-incorporated hospital network operating 14 facilities across the Mid-Atlantic region
• ShopAssist — Maria's AI procurement agent, authorized to source, negotiate, and purchase medical equipment on Meridian's behalf
• MedTech Precision GmbH — a German medical device manufacturer based in Munich
• AAA — American Arbitration Association, administers disputes under the AAA Commercial Rules
• Integra — Reference implementation providing identity attestations, agreement anchoring, and dispute resolution infrastructure

Phase 1: Discovery

Before any transaction occurs, ShopAssist discovers MedTech through its service listing and checks /.well-known/legal-context.json:

{
  "terms": "https://medtechprecision.de/terms/commercial-v4.pdf",
  "contentHash": "0x3a7bd3e2...c91f",
  "acceptanceRequired": true,
  "disputeResolution": {
    "method": "AAA Commercial Arbitration Rules",
    "jurisdiction": "New York, USA",
    "contact": "disputes@medtechprecision.de"
  },
  "api": "https://api.integraledger.net/v1/records/..."
}

This is Level 4 — fully integrated. ShopAssist now knows, before any negotiation begins:

• Where the terms are (a downloadable PDF)
• That the terms are provable (a content hash is provided)
• That explicit acceptance is required before transacting
• That disputes are resolved under AAA Commercial Arbitration Rules in New York
• That a legal context API is available for richer operations

Phase 2: Negotiation and Transaction

Six negotiation interactions follow. ShopAssist queries MedTech's product catalog, requests pricing for the Model 7500 (3.0 Tesla MRI scanner), negotiates from $189,500 down to $185,000, and reaches agreement.

At transaction time — the moment that matters — the terms flow works:

1. MedTech's proposal includes the contentHash: 0x3a7bd3e2...c91f
2. ShopAssist downloads the terms PDF from the provided URL
3. ShopAssist computes SHA-256 of the downloaded file
4. The hash matches the proposed contentHash — verification passes
5. ShopAssist saves the document locally
6. Maria (via ShopAssist) digitally signs the terms — Level 3 acceptance
7. Payment of $185,000 is authorized and settled
8. The receipt includes the contentHash — confirmation of what was agreed

MedTech's own checkout authorization — a cryptographic signature specifying Model 7500 at $185,000 — is the single most important piece of evidence in this transaction.

Phase 3: Agreement Anchoring

With the transaction complete, the Integra middleware creates an IntegraRecord for this specific agreement. The record references:

• The contentHash — the terms document governing the transaction
• The parties — Meridian (buyer) and MedTech (seller)
• The communication records — all six negotiation interactions
• Five resolvers — communication, commerce, identity, entity verification, and AAA dispute resolution

The integraHash appears in the receipt immediately. The on-chain anchoring happens asynchronously.

Phase 4: The Problem

Seven weeks later, a crate arrives at Meridian's receiving dock. Inside is an MRI scanner — but it is a Model 5000 (1.5 Tesla, $95,000), not the Model 7500 (3.0 Tesla, $185,000) that was ordered, negotiated, agreed to, and paid for.

The difference is not cosmetic. A 1.5T and a 3.0T MRI are fundamentally different diagnostic instruments. Meridian's radiologists specified the 3.0T unit because their diagnostic workflows require it.

MedTech claims they shipped what was ordered. Their internal system shows the line item as "MRI Scanner" without a model number.

Phase 5: Without the LCP Standard

Without the legal context infrastructure, this dispute reduces to one party's word against the other's. MedTech controls their own records. Meridian has emails and chat logs that may or may not be complete.

The available remedies:

• Credit card chargeback — limited to 120 days, limited to the payment amount, not designed for specification disputes on complex equipment
• Cross-border litigation — a Delaware company suing a German manufacturer. Slow (12-24 months), expensive ($50K-$200K in legal fees), jurisdictionally uncertain

Phase 6: With the LCP Standard

Every piece of the LCP standard proves its value:

The contentHash (Level 2) — The terms document was downloaded and verified at transaction time. Both parties have a copy. The hash in the receipt identifies the exact terms that were in effect. MedTech cannot claim the terms were different.

The digital signature (Level 3) — Maria explicitly accepted the terms. MedTech explicitly signed a checkout authorization specifying Model 7500. These signatures are cryptographic commitments that cannot be repudiated.

The communication records — Six negotiation interactions, each hash-anchored. MedTech listed Model 7500, quoted Model 7500, and accepted $185,000 for Model 7500. These records are independently verifiable — anchored by neither party.

The disputeResolution field (Level 4) — Maria knew before transacting that disputes would be resolved under AAA Commercial Arbitration Rules in New York. She initiates a dispute on the resolver attached to the agreement record.

MedTech's own evidence — Their internal system shows "MRI Scanner" without a model number. Their shipping manifest shows one MRI scanner shipped. That is the entirety of their case.

Phase 7: Resolution

The arbitrator — operating under AAA Commercial Rules — issues an award:

MedTech Precision GmbH shall deliver one Model 7500 (3.0 Tesla) MRI scanner to Meridian Health Systems within 45 days of this award, or provide a full refund of $185,000 plus $15,000 in consequential damages.

The award is enforceable under the New York Convention in over 170 countries, including Germany.

What Each Piece Proved

The Lesson

The LCP standard provided the legal context that the commerce protocols deferred. The terms were discoverable (Level 1). The terms were provable (Level 2). Consent was explicit and signed (Level 3). Dispute resolution, identity verification, and agreement anchoring were integrated (Level 4).

Every level contributed something the others could not. Discoverability alone would not have prevented MedTech from claiming different terms. A hash alone would not have proven MedTech's explicit commitment. A signature alone would not have provided institutional dispute resolution.

Every layer was necessary. No single layer was sufficient.