@adcp/sdk 15.2.0 → 15.2.1

package/dist/lib/schemas-data/3.2/mcp/2026-07-28/account/sync-governance-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json",
   "title": "Sync Governance Request",
   "description": "Sync the governance agent endpoint against specific accounts. The service persists the governance agent and calls it for approval during governed lifecycle events via check_governance. Uses replace semantics: each call replaces any previously synced agent on the specified accounts. The service MUST verify that the authenticated agent has authority over each referenced account before persisting the governance agent.\n\nThe binding is **account-scoped, not plan-scoped**. Each account binds to exactly one governance agent, and that agent owns the lifecycle for every plan on the account. Initial buyer-side checks address a plan by plan_id; downstream services pass only the opaque governance_context, from which the issuing agent recovers the plan. Governance registration does not vary per plan.\n\nA plan is unitary — budget authority, delivery monitoring, and regulatory compliance are phases of the same evaluation (`purchase` / `modification` / `delivery` on check_governance), not specialisms held by different agents — so a single agent owns the full lifecycle. Buyers that need internal specialist review compose that inside the governance agent, not at the registration layer. `governance_agents` is an array (not a scalar) because that is the shape 3.0 shipped with and existing senders MUST continue to work; the `maxItems: 1` constraint is load-bearing. The single-agent rule is also baked into the singular governance_context carried across tasks.",
   "x-tool-summary": "Bind or replace the governance agent used for approval across specific advertiser accounts.",
@@ -168,7 +168,7 @@
   ],
   "$defs": {
     "external:core/version-envelope.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json",
       "title": "AdCP Version Envelope",
       "description": "Release-precision AdCP protocol version negotiation fields. Composed via `allOf` into every AdCP request and response schema so the version semantics live in exactly one place. Distinct from `core/protocol-envelope.json`, which wraps responses at the transport layer (context_id / task_id / status / payload). This envelope is part of the payload itself.",
       "type": "object",
@@ -194,7 +194,7 @@
       }
     },
     "external:core/account-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/account-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/account-ref.json",
       "title": "Account Reference",
       "description": "Reference to an advertiser account by seller-assigned ID or natural key. account_id is the seller/storefront handle returned by list_accounts. The natural key is brand + operator + optional operator_unit.id + optional fixed currency + optional buyer-selected account timezone + sandbox; it describes the advertiser object the seller resolves or provisions. After a capability-gated identity rekey, the former natural key is tombstoned and returns ACCOUNT_MOVED to authorized callers rather than resolving or provisioning another account. brand.countries qualifies the advertiser's geographic identity. operator_unit identifies the operator-owned buying seat or business unit and is distinct from the seller account. operator_unit.name is display metadata and does not participate in identity. Use account_id when the seller or upstream platform owns the canonical account namespace; use the natural key for buyer-declared accounts (require_operator_auth: false).",
       "type": "object",
@@ -203,7 +203,7 @@
           "properties": {
             "account_id": {
               "type": "string",
-              "description": "Seller-assigned account identifier. For upstream-managed account namespaces, this value comes from list_accounts; for seller-defined namespaces without a list_accounts surface, it is supplied out-of-band. Buyer-declared account sellers MAY echo account_id from sync_accounts as an internal handle, but they MUST continue accepting the account's current natural-key AccountRef on subsequent calls. A former key tombstoned by identity reconciliation returns ACCOUNT_MOVED to authorized callers.",
+              "description": "Seller-assigned account identifier. For upstream-managed account namespaces, this value comes from list_accounts; for seller-defined namespaces without a list_accounts surface, it is supplied out-of-band. Buyer-declared account sellers MAY echo account_id from sync_accounts as an internal handle, but they MUST continue accepting the account's current natural-key AccountRef on subsequent calls. Buyers of buyer-declared accounts send the natural key; a seller MAY also accept its echoed account_id, and buyers MUST NOT assume it does. A former key tombstoned by identity reconciliation returns ACCOUNT_MOVED to authorized callers.",
               "x-entity": "account"
             }
           },
@@ -215,7 +215,7 @@
         {
           "properties": {
             "brand": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1brand-ref.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1brand-ref.json",
               "description": "Brand reference identifying the advertiser"
             },
             "operator": {
@@ -225,7 +225,7 @@
               "x-entity": "operator"
             },
             "operator_unit": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1operator-unit.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1operator-unit.json",
               "description": "Optional operator-owned business unit, agency seat, or platform account. Only id participates in the natural account key; name is mutable display metadata."
             },
             "currency": {
@@ -293,7 +293,7 @@
       ]
     },
     "external:core/brand-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/brand-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/brand-ref.json",
       "title": "Brand Reference",
       "description": "Reference to a brand by domain and optional brand_id. The domain hosts /.well-known/brand.json or is registered in the brand registry. For single-brand domains, brand_id can be omitted. For house-of-brands domains, brand_id identifies the specific brand. For creative production, brand.json is the canonical source of master brand identity (logo, palette, fonts, voice, and visual guidelines), subject only to the supported per-call fields in brand_kit_override. Catalogs supply product or item payload; catalog item asset groups, including property- or franchise-level logos, are item identity and do not override these master brand fields.",
       "type": "object",
@@ -304,7 +304,7 @@
           "pattern": "^[a-z0-9]([a-z0-9-]*[a-z0-9])?(\\.[a-z0-9]([a-z0-9-]*[a-z0-9])?)*$"
         },
         "brand_id": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1brand-id.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1brand-id.json",
           "description": "Brand identifier within the house portfolio. Optional for single-brand domains."
         },
         "countries": {
@@ -363,7 +363,7 @@
           "description": "Inline override for brand-kit fields normally resolved from `/.well-known/brand.json` on `domain` (logo, colors, voice, tagline). Use when brand.json is missing, stale, or inappropriate for this specific call — e.g., a campaign-scoped tagline, a co-branded creative, a freshly-rebranded color palette the brand.json hasn't shipped yet. Same inline-override pattern as `industries` and `data_subject_contestation` above: brand.json is canonical, the override is per-call. Adopters needing to override fields outside this subset (`voice_attributes`, `prohibited_terms`, etc.) MUST publish a different brand.json and reference it via a different `domain` — the inline override is intentionally narrow to a small high-traffic subset.\n\n**Merge semantics (normative).** The merge is **field-level**, not whole-object replacement. Each field within `brand_kit_override` (`logo`, `colors`, `voice`, `tagline`) is evaluated independently — when a field is present on the override the override value applies; when a field is absent the brand.json value applies (or is absent if brand.json doesn't carry one either). For composite fields (`colors.primary`, `colors.secondary`, `colors.accent`), the merge is one level deeper: each color slot is evaluated independently — a producer can override `colors.primary` while still inheriting `colors.secondary` from brand.json. SDKs MUST NOT treat a present `brand_kit_override.colors` as wiping the brand.json `colors` block entirely; only the per-slot fields present in the override take precedence. Without this rule, a partial-override semantics would diverge across SDKs and produce inconsistent rendering for the same payload.",
           "properties": {
             "logo": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1assets~1image-asset.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1assets~1image-asset.json",
               "description": "Override logo asset."
             },
             "colors": {
@@ -422,7 +422,7 @@
       ]
     },
     "external:core/brand-id.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/brand-id.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/brand-id.json",
       "title": "Brand ID",
       "description": "Identifier for a brand within a house portfolio. Must be lowercase alphanumeric with underscores only. The house chooses this identifier.",
       "type": "string",
@@ -437,7 +437,7 @@
       ]
     },
     "external:core/assets/image-asset.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/assets/image-asset.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/assets/image-asset.json",
       "title": "Image Asset",
       "description": "Image asset with URL and dimensions",
       "type": "object",
@@ -501,7 +501,7 @@
           "x-accessibility": true
         },
         "provenance": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1provenance.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1provenance.json",
           "description": "Provenance metadata for this asset, overrides manifest-level provenance"
         }
       },
@@ -514,13 +514,13 @@
       "additionalProperties": true
     },
     "external:core/provenance.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/provenance.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/provenance.json",
       "title": "Provenance",
       "description": "Declares how content was produced, whether AI was involved, and what disclosure obligations apply. Attaches to creative manifests, individual assets, or content-standards artifacts. When present at multiple levels, the most specific provenance object replaces the inherited one entirely (no field-level merging). Provenance is a claim by the declaring party — receiving parties should verify claims independently via their own detection tools.",
       "type": "object",
       "properties": {
         "digital_source_type": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1digital-source-type.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1digital-source-type.json",
           "description": "IPTC-aligned classification of AI involvement in producing this content"
         },
         "synthetic_depiction": {
@@ -630,7 +630,7 @@
             "type": "object",
             "properties": {
               "method": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1embedded-provenance-method.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1embedded-provenance-method.json",
                 "description": "How provenance data is carried within the content"
               },
               "standard": {
@@ -681,7 +681,7 @@
             "type": "object",
             "properties": {
               "media_type": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1watermark-media-type.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1watermark-media-type.json",
                 "description": "Media category of the watermarked content"
               },
               "provider": {
@@ -709,7 +709,7 @@
                 "additionalProperties": false
               },
               "c2pa_action": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1c2pa-watermark-action.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1c2pa-watermark-action.json",
                 "description": "C2PA action classification for this watermark"
               },
               "embedded_at": {
@@ -760,7 +760,7 @@
                     "minProperties": 1,
                     "properties": {
                       "persistence": {
-                        "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1disclosure-persistence.json",
+                        "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1disclosure-persistence.json",
                         "description": "How long the disclosure must persist during content playback or display"
                       },
                       "min_duration_ms": {
@@ -772,13 +772,13 @@
                         "type": "array",
                         "description": "Preferred disclosure positions in priority order. The first position a format supports should be used.",
                         "items": {
-                          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1disclosure-position.json"
+                          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:enums~1disclosure-position.json"
                         },
                         "minItems": 1,
                         "uniqueItems": true
                       },
                       "ext": {
-                        "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1ext.json"
+                        "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1ext.json"
                       }
                     }
                   }
@@ -840,12 +840,12 @@
           }
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/account/sync-governance-request.json#/$defs/external:core~1ext.json"
         }
       }
     },
     "external:enums/digital-source-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/digital-source-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/digital-source-type.json",
       "title": "Digital Source Type",
       "description": "Classification of AI involvement in content creation, aligned with IPTC digitalsourcetype vocabulary. Used in provenance metadata to declare how a creative asset, artifact, or individual asset was produced.",
       "type": "string",
@@ -873,7 +873,7 @@
       }
     },
     "external:enums/embedded-provenance-method.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/embedded-provenance-method.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/embedded-provenance-method.json",
       "title": "Embedded Provenance Method",
       "description": "How provenance data is carried within the content stream. Distinguishes between format-level manifest embedding (where the manifest travels inside the file container) and provenance markers (where invisible markers in the content itself encode or reference a provenance record). Both survive operations that strip sidecar metadata, but provenance markers additionally survive content-level transformations such as copy-paste, reformatting, and CMS re-encoding.",
       "type": "string",
@@ -887,7 +887,7 @@
       }
     },
     "external:enums/watermark-media-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/watermark-media-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/watermark-media-type.json",
       "title": "Watermark Media Type",
       "description": "Media category of a content watermark. Identifies what kind of content the watermark is applied to, which determines the detection and verification methods required.",
       "type": "string",
@@ -905,7 +905,7 @@
       }
     },
     "external:enums/c2pa-watermark-action.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/c2pa-watermark-action.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/c2pa-watermark-action.json",
       "title": "C2PA Watermark Action",
       "description": "C2PA action classification for a content watermark. Distinguishes watermarks that are cryptographically linked to a C2PA manifest (bound) from watermarks that exist independently (unbound). Aligns with the c2pa.watermarked.* action family in the C2PA action taxonomy.",
       "type": "string",
@@ -919,7 +919,7 @@
       }
     },
     "external:enums/disclosure-persistence.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/disclosure-persistence.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/disclosure-persistence.json",
       "title": "Disclosure Persistence",
       "description": "How long a disclosure must persist during content playback or display. Different jurisdictions and regulations require different persistence behaviors for AI-generated content labels. When multiple sources specify persistence for the same jurisdiction (e.g., brief and provenance), the most restrictive mode applies: continuous > initial > flexible.",
       "type": "string",
@@ -935,7 +935,7 @@
       }
     },
     "external:enums/disclosure-position.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/disclosure-position.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/disclosure-position.json",
       "title": "Disclosure Position",
       "description": "Where a required disclosure should appear within a creative. Used by creative briefs to specify disclosure placement and by formats to declare which positions they can render.",
       "type": "string",
@@ -951,14 +951,14 @@
       ]
     },
     "external:core/ext.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json",
       "title": "Extension Object",
       "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
       "type": "object",
       "additionalProperties": true
     },
     "external:core/operator-unit.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/operator-unit.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/operator-unit.json",
       "title": "Operator Unit",
       "description": "Operator-owned buying context used to distinguish business units, agency seats, or platform accounts beneath one operator domain. The id is stable identity in the operator's namespace; name is mutable display metadata and never participates in account identity.",
       "x-entity": "operator_unit",
@@ -994,7 +994,7 @@
       ]
     },
     "external:core/context.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json",
       "title": "Context Object",
       "description": "Opaque correlation data that is echoed unchanged in responses. Used for internal tracking, UI session IDs, trace IDs, and other caller-specific identifiers that don't affect protocol behavior. Context data is never parsed by AdCP agents - it's simply preserved and returned.",
       "type": "object",

package/dist/lib/schemas-data/3.2/mcp/2026-07-28/brand/acquire-rights-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json",
   "title": "Acquire Rights Request",
   "description": "Binding contractual request to acquire rights from a brand agent. Parallels create_media_buy — the buyer selects a pricing_option_id from a get_rights response and provides campaign details. The agent clears against existing contracts and returns terms, generation credentials, and disclosure requirements.",
   "type": "object",
@@ -158,7 +158,7 @@
   "additionalProperties": true,
   "$defs": {
     "external:core/version-envelope.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json",
       "title": "AdCP Version Envelope",
       "description": "Release-precision AdCP protocol version negotiation fields. Composed via `allOf` into every AdCP request and response schema so the version semantics live in exactly one place. Distinct from `core/protocol-envelope.json`, which wraps responses at the transport layer (context_id / task_id / status / payload). This envelope is part of the payload itself.",
       "type": "object",
@@ -184,7 +184,7 @@
       }
     },
     "external:core/brand-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/brand-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/brand-ref.json",
       "title": "Brand Reference",
       "description": "Reference to a brand by domain and optional brand_id. The domain hosts /.well-known/brand.json or is registered in the brand registry. For single-brand domains, brand_id can be omitted. For house-of-brands domains, brand_id identifies the specific brand. For creative production, brand.json is the canonical source of master brand identity (logo, palette, fonts, voice, and visual guidelines), subject only to the supported per-call fields in brand_kit_override. Catalogs supply product or item payload; catalog item asset groups, including property- or franchise-level logos, are item identity and do not override these master brand fields.",
       "type": "object",
@@ -195,7 +195,7 @@
           "pattern": "^[a-z0-9]([a-z0-9-]*[a-z0-9])?(\\.[a-z0-9]([a-z0-9-]*[a-z0-9])?)*$"
         },
         "brand_id": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1brand-id.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1brand-id.json",
           "description": "Brand identifier within the house portfolio. Optional for single-brand domains."
         },
         "countries": {
@@ -254,7 +254,7 @@
           "description": "Inline override for brand-kit fields normally resolved from `/.well-known/brand.json` on `domain` (logo, colors, voice, tagline). Use when brand.json is missing, stale, or inappropriate for this specific call — e.g., a campaign-scoped tagline, a co-branded creative, a freshly-rebranded color palette the brand.json hasn't shipped yet. Same inline-override pattern as `industries` and `data_subject_contestation` above: brand.json is canonical, the override is per-call. Adopters needing to override fields outside this subset (`voice_attributes`, `prohibited_terms`, etc.) MUST publish a different brand.json and reference it via a different `domain` — the inline override is intentionally narrow to a small high-traffic subset.\n\n**Merge semantics (normative).** The merge is **field-level**, not whole-object replacement. Each field within `brand_kit_override` (`logo`, `colors`, `voice`, `tagline`) is evaluated independently — when a field is present on the override the override value applies; when a field is absent the brand.json value applies (or is absent if brand.json doesn't carry one either). For composite fields (`colors.primary`, `colors.secondary`, `colors.accent`), the merge is one level deeper: each color slot is evaluated independently — a producer can override `colors.primary` while still inheriting `colors.secondary` from brand.json. SDKs MUST NOT treat a present `brand_kit_override.colors` as wiping the brand.json `colors` block entirely; only the per-slot fields present in the override take precedence. Without this rule, a partial-override semantics would diverge across SDKs and produce inconsistent rendering for the same payload.",
           "properties": {
             "logo": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1assets~1image-asset.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1assets~1image-asset.json",
               "description": "Override logo asset."
             },
             "colors": {
@@ -313,7 +313,7 @@
       ]
     },
     "external:core/brand-id.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/brand-id.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/brand-id.json",
       "title": "Brand ID",
       "description": "Identifier for a brand within a house portfolio. Must be lowercase alphanumeric with underscores only. The house chooses this identifier.",
       "type": "string",
@@ -328,7 +328,7 @@
       ]
     },
     "external:core/assets/image-asset.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/assets/image-asset.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/assets/image-asset.json",
       "title": "Image Asset",
       "description": "Image asset with URL and dimensions",
       "type": "object",
@@ -392,7 +392,7 @@
           "x-accessibility": true
         },
         "provenance": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1provenance.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1provenance.json",
           "description": "Provenance metadata for this asset, overrides manifest-level provenance"
         }
       },
@@ -405,13 +405,13 @@
       "additionalProperties": true
     },
     "external:core/provenance.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/provenance.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/provenance.json",
       "title": "Provenance",
       "description": "Declares how content was produced, whether AI was involved, and what disclosure obligations apply. Attaches to creative manifests, individual assets, or content-standards artifacts. When present at multiple levels, the most specific provenance object replaces the inherited one entirely (no field-level merging). Provenance is a claim by the declaring party — receiving parties should verify claims independently via their own detection tools.",
       "type": "object",
       "properties": {
         "digital_source_type": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1digital-source-type.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1digital-source-type.json",
           "description": "IPTC-aligned classification of AI involvement in producing this content"
         },
         "synthetic_depiction": {
@@ -521,7 +521,7 @@
             "type": "object",
             "properties": {
               "method": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1embedded-provenance-method.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1embedded-provenance-method.json",
                 "description": "How provenance data is carried within the content"
               },
               "standard": {
@@ -572,7 +572,7 @@
             "type": "object",
             "properties": {
               "media_type": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1watermark-media-type.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1watermark-media-type.json",
                 "description": "Media category of the watermarked content"
               },
               "provider": {
@@ -600,7 +600,7 @@
                 "additionalProperties": false
               },
               "c2pa_action": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1c2pa-watermark-action.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1c2pa-watermark-action.json",
                 "description": "C2PA action classification for this watermark"
               },
               "embedded_at": {
@@ -651,7 +651,7 @@
                     "minProperties": 1,
                     "properties": {
                       "persistence": {
-                        "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1disclosure-persistence.json",
+                        "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1disclosure-persistence.json",
                         "description": "How long the disclosure must persist during content playback or display"
                       },
                       "min_duration_ms": {
@@ -663,13 +663,13 @@
                         "type": "array",
                         "description": "Preferred disclosure positions in priority order. The first position a format supports should be used.",
                         "items": {
-                          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1disclosure-position.json"
+                          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1disclosure-position.json"
                         },
                         "minItems": 1,
                         "uniqueItems": true
                       },
                       "ext": {
-                        "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1ext.json"
+                        "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1ext.json"
                       }
                     }
                   }
@@ -731,12 +731,12 @@
           }
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1ext.json"
         }
       }
     },
     "external:enums/digital-source-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/digital-source-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/digital-source-type.json",
       "title": "Digital Source Type",
       "description": "Classification of AI involvement in content creation, aligned with IPTC digitalsourcetype vocabulary. Used in provenance metadata to declare how a creative asset, artifact, or individual asset was produced.",
       "type": "string",
@@ -764,7 +764,7 @@
       }
     },
     "external:enums/embedded-provenance-method.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/embedded-provenance-method.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/embedded-provenance-method.json",
       "title": "Embedded Provenance Method",
       "description": "How provenance data is carried within the content stream. Distinguishes between format-level manifest embedding (where the manifest travels inside the file container) and provenance markers (where invisible markers in the content itself encode or reference a provenance record). Both survive operations that strip sidecar metadata, but provenance markers additionally survive content-level transformations such as copy-paste, reformatting, and CMS re-encoding.",
       "type": "string",
@@ -778,7 +778,7 @@
       }
     },
     "external:enums/watermark-media-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/watermark-media-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/watermark-media-type.json",
       "title": "Watermark Media Type",
       "description": "Media category of a content watermark. Identifies what kind of content the watermark is applied to, which determines the detection and verification methods required.",
       "type": "string",
@@ -796,7 +796,7 @@
       }
     },
     "external:enums/c2pa-watermark-action.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/c2pa-watermark-action.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/c2pa-watermark-action.json",
       "title": "C2PA Watermark Action",
       "description": "C2PA action classification for a content watermark. Distinguishes watermarks that are cryptographically linked to a C2PA manifest (bound) from watermarks that exist independently (unbound). Aligns with the c2pa.watermarked.* action family in the C2PA action taxonomy.",
       "type": "string",
@@ -810,7 +810,7 @@
       }
     },
     "external:enums/disclosure-persistence.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/disclosure-persistence.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/disclosure-persistence.json",
       "title": "Disclosure Persistence",
       "description": "How long a disclosure must persist during content playback or display. Different jurisdictions and regulations require different persistence behaviors for AI-generated content labels. When multiple sources specify persistence for the same jurisdiction (e.g., brief and provenance), the most restrictive mode applies: continuous > initial > flexible.",
       "type": "string",
@@ -826,7 +826,7 @@
       }
     },
     "external:enums/disclosure-position.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/disclosure-position.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/disclosure-position.json",
       "title": "Disclosure Position",
       "description": "Where a required disclosure should appear within a creative. Used by creative briefs to specify disclosure placement and by formats to declare which positions they can render.",
       "type": "string",
@@ -842,14 +842,14 @@
       ]
     },
     "external:core/ext.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json",
       "title": "Extension Object",
       "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
       "type": "object",
       "additionalProperties": true
     },
     "external:core/account-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/account-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/account-ref.json",
       "title": "Account Reference",
       "description": "Reference to an advertiser account by seller-assigned ID or natural key. account_id is the seller/storefront handle returned by list_accounts. The natural key is brand + operator + optional operator_unit.id + optional fixed currency + optional buyer-selected account timezone + sandbox; it describes the advertiser object the seller resolves or provisions. After a capability-gated identity rekey, the former natural key is tombstoned and returns ACCOUNT_MOVED to authorized callers rather than resolving or provisioning another account. brand.countries qualifies the advertiser's geographic identity. operator_unit identifies the operator-owned buying seat or business unit and is distinct from the seller account. operator_unit.name is display metadata and does not participate in identity. Use account_id when the seller or upstream platform owns the canonical account namespace; use the natural key for buyer-declared accounts (require_operator_auth: false).",
       "type": "object",
@@ -858,7 +858,7 @@
           "properties": {
             "account_id": {
               "type": "string",
-              "description": "Seller-assigned account identifier. For upstream-managed account namespaces, this value comes from list_accounts; for seller-defined namespaces without a list_accounts surface, it is supplied out-of-band. Buyer-declared account sellers MAY echo account_id from sync_accounts as an internal handle, but they MUST continue accepting the account's current natural-key AccountRef on subsequent calls. A former key tombstoned by identity reconciliation returns ACCOUNT_MOVED to authorized callers.",
+              "description": "Seller-assigned account identifier. For upstream-managed account namespaces, this value comes from list_accounts; for seller-defined namespaces without a list_accounts surface, it is supplied out-of-band. Buyer-declared account sellers MAY echo account_id from sync_accounts as an internal handle, but they MUST continue accepting the account's current natural-key AccountRef on subsequent calls. Buyers of buyer-declared accounts send the natural key; a seller MAY also accept its echoed account_id, and buyers MUST NOT assume it does. A former key tombstoned by identity reconciliation returns ACCOUNT_MOVED to authorized callers.",
               "x-entity": "account"
             }
           },
@@ -870,7 +870,7 @@
         {
           "properties": {
             "brand": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1brand-ref.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1brand-ref.json",
               "description": "Brand reference identifying the advertiser"
             },
             "operator": {
@@ -880,7 +880,7 @@
               "x-entity": "operator"
             },
             "operator_unit": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1operator-unit.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:core~1operator-unit.json",
               "description": "Optional operator-owned business unit, agency seat, or platform account. Only id participates in the natural account key; name is mutable display metadata."
             },
             "currency": {
@@ -948,7 +948,7 @@
       ]
     },
     "external:core/operator-unit.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/operator-unit.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/operator-unit.json",
       "title": "Operator Unit",
       "description": "Operator-owned buying context used to distinguish business units, agency seats, or platform accounts beneath one operator domain. The id is stable identity in the operator's namespace; name is mutable display metadata and never participates in account identity.",
       "x-entity": "operator_unit",
@@ -984,7 +984,7 @@
       ]
     },
     "external:enums/right-use.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/right-use.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/right-use.json",
       "title": "Right Use",
       "description": "Types of rights usage that can be licensed through the brand protocol. Aligned with DDEX UseType direction for interoperability with music and media rights systems.",
       "x-status": "experimental",
@@ -1019,7 +1019,7 @@
       }
     },
     "external:core/format-id.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/format-id.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/format-id.json",
       "title": "Format Reference (Structured Object)",
       "deprecated": true,
       "description": "**DEPRECATED in 3.2.** Legacy named-format reference retained for 3.x compatibility. This JSON object — never a plain string — identifies a format by its declaring agent and local slug, and may carry legacy logical dimensions, pixel ratio, or duration parameters. New products and manifests use canonical `format_options`, `format_kind`, and `format_option_ref`; creative-agent build routing uses `creative.supported_formats[].capability_id`.",
@@ -1076,7 +1076,7 @@
       }
     },
     "external:core/canonical-format-kind.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/canonical-format-kind.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/canonical-format-kind.json",
       "title": "Canonical Format Kind",
       "description": "Discriminator naming one of the 15 AdCP 3.2 canonical creative formats, plus `custom` for adopter-defined shapes. AdCP 3.2 adds `audio_vast` for VAST-tag-delivered audio (the standards-conformant profile starts at VAST 4.1, with older versions available only as seller-declared legacy interoperability) and promotes the legacy `multi_state_display` and `multi_placement_takeover` custom shapes to `seller_rendered_stateful_display` and `coordinated_placements`. When `format_kind` is `custom`, the declaration also carries `format_shape` and `format_schema`. The enum mirrors the branches in `product-format-declaration.json` and is closed for producer validation: sellers do not mint ad-hoc values. SDKs may retain unknown future values in tolerant in-memory parsers, but that does not change versioned JSON Schema validation. A seller responding to a 3.1-or-earlier request MUST project away 3.2-only kinds and emit a compatible legacy declaration; a strict older schema correctly rejects an unprojected newer kind. See adcp#3666 and the promotion migration contract in canonical-formats.mdx.",
       "type": "string",
@@ -1100,7 +1100,7 @@
       ]
     },
     "external:core/format-option-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/format-option-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/format-option-ref.json",
       "title": "Format Option Reference",
       "description": "Discriminated reference to a product format option. The global canonical shape is still named by `format_kind`; this reference selects one concrete product `format_options[]` entry. `scope: \"publisher\"` identifies a publisher-declared catalog option by `{ publisher_domain, format_option_id }`. `scope: \"product\"` identifies a product-local option by `format_option_id`; the enclosing package/product context supplies the namespace.",
       "type": "object",
@@ -1161,7 +1161,7 @@
       "additionalProperties": true
     },
     "external:core/push-notification-config.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/push-notification-config.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/push-notification-config.json",
       "title": "Push Notification Config",
       "description": "Webhook configuration for asynchronous task notifications. Uses A2A-compatible PushNotificationConfig structure. By default, webhooks are signed with the AdCP RFC 9421 profile (see docs/building/by-layer/L1/security.mdx#webhook-callbacks) — the seller signs outbound with a key published at the jwks_uri on its own brand.json `agents[]` entry and the buyer verifies against that JWKS, so no shared secret crosses the wire. The optional `authentication` block selects the legacy Bearer or HMAC-SHA256 fallback for compatibility with receivers that have not yet adopted the 9421 profile; this fallback is deprecated and will be removed in AdCP 4.0. Note: the `idempotency_key` that receivers dedup on lives inside the webhook **payload** body (see docs/building/by-layer/L3/webhooks.mdx#reliability and the mcp-webhook-payload schema), not in this configuration object — this schema only describes the receiver-side transport config sent to the seller. This schema is designed for composition via allOf - consuming schemas should define their own additionalProperties constraints.",
       "type": "object",
@@ -1193,7 +1193,7 @@
               "type": "array",
               "description": "Array of authentication schemes. Supported: ['Bearer'] for simple token auth, ['HMAC-SHA256'] for legacy shared-secret signing. Both are deprecated; new integrations SHOULD omit `authentication` and use the RFC 9421 webhook profile.",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1auth-scheme.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/brand/acquire-rights-request.json#/$defs/external:enums~1auth-scheme.json"
               },
               "minItems": 1,
               "maxItems": 1
@@ -1216,7 +1216,7 @@
       ]
     },
     "external:enums/auth-scheme.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/enums/auth-scheme.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/auth-scheme.json",
       "title": "Authentication Scheme",
       "deprecated": true,
       "description": "Legacy authentication schemes for the webhook auth block. Bearer: token sent in Authorization header. HMAC-SHA256: legacy shared-secret signing. Both are deprecated; new integrations SHOULD omit the authentication block and use the RFC 9421 webhook signing profile (applicable on schemas where authentication is optional). Removed in AdCP 4.0.",
@@ -1227,7 +1227,7 @@
       ]
     },
     "external:core/context.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json",
       "title": "Context Object",
       "description": "Opaque correlation data that is echoed unchanged in responses. Used for internal tracking, UI session IDs, trace IDs, and other caller-specific identifiers that don't affect protocol behavior. Context data is never parsed by AdCP agents - it's simply preserved and returned.",
       "type": "object",