Microsoft Azure · France Central · Paris
Sovereign Manifest · Agentic Marketplace Protocol for Consumer Packaged Goods

# SM-AMP-CPG

*The machine-resolution protocol for agentic marketplaces.*

## Canonical Definition

The Agentic Marketplace Protocol for Consumer Packaged Goods (AMP-CPG)
is a deterministic, machine-readable protocol that enables an AI Agent
to resolve the authoritative commercial endpoints for an identified
product in a defined market.

It answers one question:

Given this product and this market, where can an Agent transact for it?

One product. One market. One resolution set.

## Purpose

AI Agents must not have to infer commerce from webpages, search
results, advertising copy, or model memory.

AMP-CPG provides a direct machine path from:

Product identity → market → authoritative seller / marketplace endpoints

The protocol does not require the Agent to know which marketplace
exists in advance. The Agent resolves first. Commerce happens
downstream.

## Core Operation

RESOLVE

GTIN + MARKET → AMP-CPG → ENDPOINT SET

Example:

GET /resolve?gtin=990832300082&market=FR

Resolution is live on this node and all 49 jurisdiction nodes;
publication is not open.

Canonical response:

```json
{
  "amp": "1.0",
  "gtin": "990832300082",
  "market": "FR",
  "endpoints": [
    {
      "uri": "https://commerce.example/990832300082",
      "seller": "gsc-demo:seller/verdemar-eu",
      "type": "marketplace",
      "protocol": "https"
    }
  ],
  "issued": "2026-08-24T00:00:00Z",
  "expires": "2026-08-24T00:05:00Z",
  "signature": "..."
}
```

## Authority

An AMP-CPG resolution is not search. Published records must have a
verifiable authority chain.

Product authority → delegated commercial authority → signed AMP record
→ jurisdiction node

Records may be signed using standard public-key cryptography. Public
keys are independently discoverable. Key rotation does not change
product identity. Compromised or expired authority can be revoked.
Unsigned, invalid, expired, and unreachable authority states are
distinguishable from verified records.

## Sovereign Resolution

SM-AMP-CPG is the global Sovereign Manifest. It resolves the
applicable jurisdiction node.

SM-AMP-CPG → FR-AMP-CPG → GTIN → authoritative commercial endpoints

The estate consists of: 1 Sovereign Manifest apex + 49 jurisdiction
nodes = 50 nodes.

Each node has exactly one canonical surface: its .org. The 50 .org
zones are the protocol's canonical URLs. Each .org carries a .com
twin that answers only with a 308 permanent redirect to its .org —
a forwarding address, never a second live surface. 50 canonical .org
nodes; 50 .com twins that 308.

## Scale Architecture

AMP-CPG is designed so a resolution does not require a centralized
transaction. Resolvers are: stateless · deterministic · cacheable ·
independently verifiable. Records carry expiry information. Responses
support normal HTTP caching and content validation. Identical verified
inputs produce identical resolution results. Jurisdiction nodes can be
independently replicated globally. No session is required to resolve a
public record. No central database must sit in the request path. No AI
model is required to interpret the result.

## Security Model

Public resolution is read-only. Publication and delegation require
authenticated authority. Transport uses HTTPS. Records are
cryptographically signed. Consumers verify the record, not merely the
server that delivered it. Replay is constrained through issue time,
expiry, version, and record identity. Updates are append-only.
Revocation is explicit. Secrets never appear in public records. A
compromised jurisdiction node cannot silently manufacture product
authority without a valid authority signature.

## What AMP-CPG Does Not Own

AMP-CPG does not own: price · inventory · checkout · payment ·
fulfillment · recommendation · negotiation.

Those remain authoritative at the commercial endpoint. AMP resolves
where those systems live. This prevents AMP from becoming a global
catalog synchronization system.

## Protocol Independence

An AMP endpoint may expose any downstream commerce interface. Today
that may include: HTTP APIs · MCP · A2A · UCP · ACP. Tomorrow it may
be something that does not yet exist. AMP does not depend on any of
them. The resolver returns the endpoint and declared protocol. The
purchasing Agent chooses what it supports.

## Design Law

No inference. No ranking. No checkout. No payment. No central hot path.

Identify. Resolve. Verify. Route.

## Deterministic Architecture

Product ↓ GTIN / Product Identity ↓ Market ↓ SM-AMP-CPG ↓ Sovereign
AMP Node ↓ Signed Resolution ↓ Authorized Commercial Endpoint(s) ↓
Agent / ERP / Marketplace / Commerce Protocol

## Canonical Statement

AMP-CPG is the machine-resolution layer for agentic marketplaces. It
enables an AI Agent to take a known product identity and market and
deterministically discover the authoritative commercial endpoints
through which commerce can continue. It does not require an LLM. It
does not require a marketplace monopoly. It does not require a
particular payment system. It does not require a particular Agent
framework. It requires only the web, a product identity, an authority
chain, and a resolver.

Built for billions of Agents. Deployable today.

## Open Rulings

The following are CEO-gated. They are named here so the protocol text
is honest about what it does not yet decide. Nothing in this section
is designed, implied, or scheduled by this document.

- **Lodging authority mechanism** — how a product authority or its
  delegate lodges a record with a jurisdiction node: the credential,
  the channel, and the acceptance rule. Third-party lodging is CLOSED
  and CEO-gated. Open. (Scope ruling, 2026-08-24: GSC lodges GSC's
  records only — GSC is the product authority for its own GTIN and
  the operator of its own endpoints; no lodging-authority ruling is
  consumed. Publication endpoints: none public.)
- **Free / verified differential** — whether and how an unverified
  lodging differs from a verified one in what the resolver returns.
  Open.