Agreements

The four agentic commerce protocols all solve the same problem: how does an AI agent buy something on behalf of a human? This is the right first problem to solve. It is also the smallest one.

A purchase transaction is one point on a spectrum of agreements. The infrastructure that handles "buy this widget" cannot handle "provide this service under these terms for three years with quarterly SLA reviews and structured dispute resolution." These are not extensions of the same problem. They are structurally different.

The Agreement Spectrum

Agreements range from simple to complex, and the requirements change in ways that commerce protocols cannot accommodate.

Simple ────────────────────────────────────────────────── Complex

Purchase          Service         Supply Chain        Joint Venture
Transaction       Contract        Agreement           / Partnership

"Buy this"        "Do this        "Supply these       "Build this
                   over time"      materials under     together over
                                   these terms for     5 years with
                                   2 years"            shared IP"

As you move from left to right across this spectrum:

The commerce protocols are optimized for the left column. Integra provides the infrastructure for the right column. For the simplest case — a purchase that completes without dispute — only the left column is needed. For everything else, the right column is where the value lives.

The Structural Gap

The differences between commerce protocols and agreement infrastructure are not features that can be added via extensions. They are architectural.

Temporal Architecture

Party Architecture

Obligation Architecture

Identity Architecture

Dispute Architecture

Jurisdictional Architecture

Confidentiality Architecture

Eight Agreement Domains

The purchase transaction is the on-ramp. These eight domains are the destination.

1. Service Contracts

Agents negotiate SaaS subscriptions, consulting engagements, managed service agreements. What is needed beyond commerce protocols: performance obligation tracking with SLA uptime monitored over months, acceptance criteria for deliverables, auto-renewal and termination window management, and entity authority verification for who can commit to a $500K/year contract.

2. Supply Chain Agreements

Agents source materials and manage procurement across international vendors. What is needed: multi-party coordination across manufacturer, supplier, logistics, insurer, and financier. Recurring deliveries with quality standards. Cross-jurisdictional compliance (export controls, sanctions, environmental regulations). Force majeure procedures. Trade finance instruments.

3. IP Licensing

Agents negotiate software licenses, content rights, patent cross-licenses. What is needed: usage scope tracking (the license permits X but not Y, in territories A and B but not C), royalty calculations that accrue over time, sublicensing chains with consent tracking, and audit rights. Some license terms survive termination indefinitely.

4. Employment and Contracting

Agents engage freelancers, negotiate contractor terms, manage staffing. What is needed: human identity at high assurance (government-issued ID, not just a passkey), jurisdictional labor law compliance (independent contractor vs. employee classification), IP assignment for work product, and post-termination obligations (non-compete, confidentiality).

5. Real Estate

Agents execute commercial leases and manage property transactions. What is needed: long temporal scope (5-20 year leases with options and escalation clauses), regulatory compliance (zoning, environmental, building codes), verifiable title chain, amendment tracking over a decade-long term, and escrow mechanics for deposits and earnest money.

6. Regulatory Filings

Agents prepare and submit compliance documents. What is needed: authorized signatory verification (specific individuals with verified authority), temporal integrity (provable and immutable filing timestamps), complete amendment chains, permanent record retention for years or decades, and multi-jurisdictional filing coordination.

7. Insurance

Agents procure coverage, file claims, negotiate settlements. What is needed: policy term tracking (coverage periods, exclusions, deductibles, limits), claims lifecycle management (filing through adjustment through settlement), subrogation rights, multi-party claims coordination (insured, insurer, reinsurer, adjuster), and actuarial history tracking.

8. Financial Instruments

Agents enter derivatives, execute loan agreements, manage portfolios. What is needed: complex obligation structures (interest payments, margin calls, collateral requirements, default triggers), mark-to-market valuation, regulatory compliance across jurisdictions (securities law, margin requirements), multi-party structures (borrower, lender, guarantor, collateral agent), and default cascading.

Each of these domains maps to the same Integra infrastructure — records, tokenizers, resolvers, attestations, dispute resolution — with domain-specific configuration rather than domain-specific contracts.

The Three Phases

The agentic era unfolds in three phases, and the commerce protocols cover only the first.

Phase 1: Agentic Shopping (2025-2026)

AI agents buy things on behalf of humans. The commerce protocols handle this. The constraint is authorization proof (VI), checkout lifecycle (UCP and ACP), and payment execution (all four protocols). This phase is well-served by existing infrastructure.

Phase 2: Agentic Contracting (2026-2028)

AI agents negotiate and enter into service contracts, supply agreements, and professional engagements on behalf of organizations. The constraint shifts from "was the payment authorized?" to "was the commitment authorized, by whom, with what scope, under what law?"

This is not hypothetical. Legal AI companies — Harvey, Thomson Reuters CoCounsel, Luminance, Ironclad — are already building contract analysis, negotiation, and management capabilities. These agents analyze terms, identify risks, suggest modifications, and track obligations. What they lack is infrastructure for anchoring what they negotiate, verifying identity of the parties they negotiate with, and resolving disputes when agreements fail.

The commerce protocols have no answer for Phase 2. Not because they are poorly designed — they are well-designed for their scope — but because transactions and agreements are structurally different things.

Phase 3: Agentic Operations (2028+)

AI agents manage ongoing contractual relationships: monitoring performance obligations, detecting breaches, exercising options, negotiating amendments, filing claims, and initiating dispute resolution. The constraint is not a single transaction but an ongoing relationship with evolving obligations.

Commerce protocols handle Phase 1. Integra handles Phases 2 and 3.

Integra's Agreement Infrastructure

Every claim about agreement domains must be grounded in what actually exists. This is not a roadmap.

IntegraRecordV1 provides the permanent, content-addressed agreement anchor with ownership, executor delegation, up to 10 resolver slots, policy resolver, identity extension, and reference hash for amendment chains.

Multi-party tokenizers support N-party agreements with distinct roles. AgreementTokenizerV1 handles 3-party agreements (Party A, Party B, Provider). MultiPartyTokenizerV1 handles arbitrary party counts. GovernanceTokenizerV1 handles governance with voting. ITokenParty.isTokenHolder() provides universal party detection across all token standards.

Resolvers encode obligation logic. StateMachine provides two-tier transition rules. DeadlineTracker manages absolute and relative deadlines. Counter tracks per-record keyed counts. PeriodicSchedule handles recurring obligations. MultiPartyConfirmation provides quorum-based confirmation with cooldowns. The AAAResolverV1 provides the 11-state dispute lifecycle.

EAS attestations provide persistent, composable, independently verifiable identity at every tier — human, entity, agreement, agent — tied to a 9-field schema with capability bitmask.

These are deployed, tested contracts with 464 tests passing across the system. The agreement infrastructure exists. The purchase transaction is the on-ramp. The agreement lifecycle is the destination.