diff --git a/.changeset/align-32-docs-rc3.md b/.changeset/align-32-docs-rc3.md new file mode 100644 index 00000000000..f6fdd19786a --- /dev/null +++ b/.changeset/align-32-docs-rc3.md @@ -0,0 +1,5 @@ +--- +"adcontextprotocol": patch +--- + +Align the 3.2 docs, announcement banner, and SDK guidance with the published 3.2.0-rc.3 checkpoint and @adcp/sdk@14.0.0-rc.36. diff --git a/docs.json b/docs.json index 6c1de752d93..d6ad6409055 100644 --- a/docs.json +++ b/docs.json @@ -2,7 +2,7 @@ "$schema": "https://mintlify.com/schema.json", "name": "AdCP - Ad Context Protocol", "banner": { - "content": "AdCP 3.2 release candidate adds Reliable Reporting to the compact lifecycle — [open the current signed release →](https://github.com/adcontextprotocol/adcp/releases/tag/v3.2.0-rc.2)", + "content": "The AdCP 3.2 release candidate now hardens the Reliable Reporting consumer-status loop and adds MediaBuy-level frequency caps — [see what's new →](/3.2)", "dismissible": true }, "description": "AdCP (Ad Context Protocol) is the open standard for agentic advertising. It defines how AI agents buy media, generate creatives, activate audiences, and enforce governance across platforms. Current stable documentation index: https://docs.adcontextprotocol.org/llms-current.md.", diff --git a/docs/building/by-layer/L4/choose-your-sdk.mdx b/docs/building/by-layer/L4/choose-your-sdk.mdx index 47f811f3b29..c72435dda3f 100644 --- a/docs/building/by-layer/L4/choose-your-sdk.mdx +++ b/docs/building/by-layer/L4/choose-your-sdk.mdx @@ -23,7 +23,7 @@ For the layered model behind this — what each layer contains and what an SDK a What "shipped" means at each layer is the [L0–L3 checklist](/docs/building/cross-cutting/sdk-stack#what-an-sdk-at-each-layer-should-provide). -*Last updated: 2026-09-11.* +*Last updated: 2026-09-14.* | SDK | Current package | 3.2 RC support | L0 | L1 | L2 | L3 | |---|---|---|:-:|:-:|:-:|:-:| @@ -33,11 +33,15 @@ What "shipped" means at each layer is the [L0–L3 checklist](/docs/building/cro Legend: ✅ shipped · ⚠️ partial / role-dependent · ❌ not yet covered. The L0–L3 columns describe the current package, not a 3.2 support claim. +The current `rc` npm tag of `@adcp/sdk` is ahead of this checkpoint: it embeds `3.2.0-rc.2` and adds the seller-side reporting modules (`@adcp/sdk/reporting/source` and `@adcp/sdk/reporting/ledger`). The repository checkpoint alignment follows once the Python and Go SDKs publish matching bundles. + -**All three maintained SDKs now embed RC.1.** Pin the exact package and wire -versions shown here for development and staging. This is not a GA signal: -production integrations should remain on 3.1 until 3.2 is released. See the -[3.2 prerelease program](/docs/reference/3-2-beta). +**No SDK embeds RC.3, the current protocol checkpoint.** All three still +embed `3.2.0-rc.1`. Pin the exact package +and wire versions shown here for development and staging, and test RC.3 from +its [signed bundle](/docs/reference/3-2-beta#use-the-rc-3-artifact-directly). +This is not a GA signal: production integrations should remain on 3.1 until +3.2 is released. See the [3.2 prerelease program](/docs/reference/3-2-beta). The TypeScript SDK currently provides the broadest L0–L3 surface. Python is a @@ -205,6 +209,10 @@ npx @adcp/sdk@14.0.0-rc.35 my-agent list_products '{"adcp_version":"3.2-rc.1","a npx @adcp/sdk@14.0.0-rc.35 test-mcp list_products '{"adcp_version":"3.2-rc.1"}' ``` +The `adcp_version` in the payload is a wire pin the CLI passes through, so it +can name a checkpoint other than the one the SDK embeds. Request and response +validation still uses the SDK's embedded bundle. + The CLI also drives storyboards (`adcp storyboard run`), conformance grading (`adcp grade`), and registry diagnostics. See `--help` for the full surface. ### Python CLI diff --git a/docs/intro.mdx b/docs/intro.mdx index 88642632bc3..6d46d32935d 100644 --- a/docs/intro.mdx +++ b/docs/intro.mdx @@ -9,11 +9,13 @@ description: "AdCP is an open agentic advertising standard. Follow Alex's team f Alex stands arms crossed in a war room of mismatched screens and tangled cables, surveying the chaos — her team hunched over laptops in the background -AdCP 3.2 is in release candidate. RC.1 is the current signed protocol bundle; +AdCP 3.2 is in release candidate. RC.3 is the current signed protocol bundle; it combines the proposal-to-operation lifecycle, an experimental -authenticated-principal connection layer, and experimental Reliable Reporting -1.0. The TypeScript, Python, and Go SDKs now publish exact RC.1 pairings for -staging integration tests. Keep production traffic on 3.1 until 3.2 reaches GA. +authenticated-principal connection layer, a hardened experimental Reliable +Reporting consumer-status loop, and shared MediaBuy-level frequency caps. No +SDK embeds RC.3 yet — test it from its signed bundle, or run SDK-backed +staging tests against the checkpoint your SDK embeds. Keep production traffic +on 3.1 until 3.2 reaches GA. See [what's new in 3.2](/docs/reference/whats-new-in-3-2) and the [prerelease program](/docs/reference/3-2-beta) before testing. diff --git a/docs/media-buy/reporting-core-implementation-guide.mdx b/docs/media-buy/reporting-core-implementation-guide.mdx index 9f33f54012a..300a5d7fd9d 100644 --- a/docs/media-buy/reporting-core-implementation-guide.mdx +++ b/docs/media-buy/reporting-core-implementation-guide.mdx @@ -9,10 +9,12 @@ Reliable Reporting is experimental in 3.2. `reporting.core` is its required tier; `managed_delivery` and `reconciled_billing` are separately advertised optional tiers. -The consumer-status loop is additive and opt-in in current source. Sellers -advertise `consumer_status_task` only when implemented. The active notice makes -it required Core in the next eligible minor after October 24, 2026; RC.1 and the -current public training seller remain unchanged. +The consumer-status loop is additive and opt-in. It is published in +`3.2.0-rc.2` and hardened in `3.2.0-rc.3`, and it stays opt-in until the notice +window closes on October 24, 2026. Sellers advertise `consumer_status_task` +only when implemented. The active notice makes it required Core in the next +eligible minor after that date; RC.1 and the current public training seller +remain unchanged. Every buyer eventually asks one question: **"do I have definitive reporting @@ -299,7 +301,8 @@ digest is intentionally retained). received. Reliable Reporting 1.0 is published in the RC wire bundles; the consumer-status -loop lands in `3.2.0-rc.2`. The public training sales agent serves whichever +loop is published in `3.2.0-rc.2` and hardened in `3.2.0-rc.3`. The public +training sales agent serves whichever prerelease contract its deployment advertises, which may trail the newest published bundle. Read the advertised version from `get_adcp_capabilities` and put that exact negotiated value on every diff --git a/docs/media-buy/task-reference/get_reporting_status.mdx b/docs/media-buy/task-reference/get_reporting_status.mdx index 0f32ca507f3..d075265b867 100644 --- a/docs/media-buy/task-reference/get_reporting_status.mdx +++ b/docs/media-buy/task-reference/get_reporting_status.mdx @@ -6,11 +6,12 @@ description: "Check Reliable Reporting health, enumerate expected periods and re **Reliable Reporting 1.0 is published through `3.2.0-rc.3` and remains -experimental.** RC.2 publishes the opt-in consumer-status sync and readback; -RC.3 adds its hardening. Sellers implementing that extension advertise -`consumer_status_task`; it becomes required Core only in the next eligible minor -after the notice window. Sellers declare `media_buy.reporting_delivery` in -`get_adcp_capabilities.experimental_features`. +experimental.** RC.2 publishes the opt-in consumer-status sync and readback and +RC.3 hardens it. Sellers implementing that extension advertise +`consumer_status_task`; it stays opt-in until the notice window closes on +October 24, 2026, and becomes required Core only in the next eligible minor +after that date. Sellers declare +`media_buy.reporting_delivery` in `get_adcp_capabilities.experimental_features`. `get_reporting_status` is the authoritative status surface for AdCP 3.2 diff --git a/docs/media-buy/task-reference/sync_reporting_status.mdx b/docs/media-buy/task-reference/sync_reporting_status.mdx index ca12ae54751..62a064de241 100644 --- a/docs/media-buy/task-reference/sync_reporting_status.mdx +++ b/docs/media-buy/task-reference/sync_reporting_status.mdx @@ -8,8 +8,9 @@ description: "Tell a seller whether expected reporting was received, omitted, mi `sync_reporting_status` is an additive, opt-in Reliable Reporting extension published in `3.2.0-rc.2` and hardened in `3.2.0-rc.3`. RC.1 implementations do not expose it. Sellers that implement it advertise `consumer_status_task`; the -active breaking-change notice makes it required Core only in the next eligible -minor after October 24, 2026. +task stays opt-in until the active breaking-change notice window closes on +October 24, 2026, and becomes required Core only in the next eligible minor +after that date. `sync_reporting_status` closes the operational loop between what a seller says diff --git a/docs/reference/3-2-beta.mdx b/docs/reference/3-2-beta.mdx index 065f1208946..2f357ff79c8 100644 --- a/docs/reference/3-2-beta.mdx +++ b/docs/reference/3-2-beta.mdx @@ -15,15 +15,16 @@ change 3.2 surfaces before GA. The 3.2 prerelease cycle started with a protocol-first beta checkpoint. -RC.1 is the current signed protocol checkpoint. TypeScript SDK -`14.0.0-rc.35`, Python SDK `8.0.0b14`, and Go SDK `adcp/v3@v3.2.1` embed it -exactly: +RC.3 is the current signed protocol checkpoint. No SDK embeds it yet: +TypeScript SDK `14.0.0-rc.35`, Python SDK `8.0.0b14`, and Go SDK +`adcp/v3@v3.2.1` all still embed `3.2.0-rc.1`: -**RC.1 now has matched SDKs.** Use its signed bundle for raw-wire validation -and code generation, or use one of the exact package pairings below for -SDK-backed integration testing. Do not infer compatibility from a floating -package tag or from an SDK generated against an earlier checkpoint. +**RC.3 has no matched SDK yet.** Use its signed bundle for raw-wire validation +and code generation. The exact package pairings below are all still on RC.1, +so an SDK-backed run is RC.1 evidence — not RC.3 evidence. Do not infer +compatibility from a floating package tag or from an SDK generated against an +earlier checkpoint. | Checkpoint | Purpose | Who should test | @@ -41,30 +42,35 @@ package tag or from an SDK generated against an earlier checkpoint. | `3.2.0-beta.10` | Previous protocol checkpoint for managed reporting delivery, authenticated principals, audio VAST and DOOH support, programmed channel collections, committed collection selection, and expanded conformance coverage | Pinned adopters comparing beta.10 and beta.11 behavior | | `3.2.0-beta.11` | Previous protocol checkpoint | Pinned adopters comparing beta.11 and RC.0 behavior | | `3.2.0-rc.0` | Previous protocol checkpoint | SDK-backed integration testing with an exact RC.0 package pairing | -| `3.2.0-rc.1` | Current protocol checkpoint for Reliable Reporting 1.0 and reporting-semantics hardening | Raw-wire, signed-artifact, code-generation, and SDK-backed integration testing | -| Current SDK wave | `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` embed `3.2.0-rc.1` | Exact RC.1 SDK-backed testing; higher-level Python and Go coverage remains role-dependent | +| `3.2.0-rc.1` | Previous protocol checkpoint for Reliable Reporting 1.0 and reporting-semantics hardening | SDK-backed integration testing with an exact RC.1 package pairing: `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, or Go `adcp/v3@v3.2.1` | +| `3.2.0-rc.2` | Previous protocol checkpoint for the opt-in Reliable Reporting `sync_reporting_status` consumer-status loop, buyer and orchestrator storyboards, and truncated-breakdown cursor pagination | Raw-wire, signed-artifact, and code-generation integration testing; no maintained SDK embeds it | +| `3.2.0-rc.3` | Current protocol checkpoint for consumer-status hardening, MediaBuy-level frequency caps, and request-only targeting with `null`-clear semantics | Raw-wire, signed-artifact, and code-generation integration testing | +| Current SDK wave | `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` all embed `3.2.0-rc.1` | Exact RC.1 SDK-backed testing; higher-level Python and Go coverage remains role-dependent. No row names RC.2 or RC.3 | Earlier betas and RC.0 remain useful as pinned implementation checkpoints. TypeScript SDK beta.31 and Python SDK beta.13 are historical RC.0 pairings; -TypeScript SDK beta.29 and Python SDK beta.12 pair with beta.11. Do not combine -a newer wire pin with an SDK generated from an older bundle unless the SDK -maintainer documents forward compatibility. +TypeScript SDK beta.29 and Python SDK beta.12 pair with beta.11. Do not +combine a newer wire pin with an SDK generated from an older bundle unless the +SDK maintainer documents forward compatibility. An SDK's wire-only +`wireAdcpVersion` override can carry a different pin than the bundle it +validates against, but a run under that override is not evidence for the +pinned checkpoint. ## Know which version string to use The artifact version, wire pin, and documentation selector are related but not interchangeable: -| Surface | beta.0 | beta.1 | beta.2 | beta.3 | beta.4 | beta.5 | beta.6 | beta.7 | beta.8 | beta.9 | beta.10 | beta.11 | RC.0 | RC.1 | -|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| -| Protocol artifact | `3.2.0-beta.0` | `3.2.0-beta.1` | `3.2.0-beta.2` | `3.2.0-beta.3` | `3.2.0-beta.4` | `3.2.0-beta.5` | `3.2.0-beta.6` | `3.2.0-beta.7` | `3.2.0-beta.8` | `3.2.0-beta.9` | `3.2.0-beta.10` | `3.2.0-beta.11` | `3.2.0-rc.0` | `3.2.0-rc.1` | -| Git tag | `v3.2.0-beta.0` | `v3.2.0-beta.1` | `v3.2.0-beta.2` | `v3.2.0-beta.3` | `v3.2.0-beta.4` | `v3.2.0-beta.5` | `v3.2.0-beta.6` | `v3.2.0-beta.7` | `v3.2.0-beta.8` | `v3.2.0-beta.9` | `v3.2.0-beta.10` | `v3.2.0-beta.11` | `v3.2.0-rc.0` | `v3.2.0-rc.1` | -| `adcp_version` wire pin | `"3.2-beta.0"` | `"3.2-beta.1"` | `"3.2-beta.2"` | `"3.2-beta.3"` | `"3.2-beta.4"` | `"3.2-beta.5"` | `"3.2-beta.6"` | `"3.2-beta.7"` | `"3.2-beta.8"` | `"3.2-beta.9"` | `"3.2-beta.10"` | `"3.2-beta.11"` | `"3.2-rc.0"` | `"3.2-rc.1"` | -| Documentation selector | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-rc` | `3.2-rc` | +| Surface | beta.0 | beta.1 | beta.2 | beta.3 | beta.4 | beta.5 | beta.6 | beta.7 | beta.8 | beta.9 | beta.10 | beta.11 | RC.0 | RC.1 | RC.2 | RC.3 | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| Protocol artifact | `3.2.0-beta.0` | `3.2.0-beta.1` | `3.2.0-beta.2` | `3.2.0-beta.3` | `3.2.0-beta.4` | `3.2.0-beta.5` | `3.2.0-beta.6` | `3.2.0-beta.7` | `3.2.0-beta.8` | `3.2.0-beta.9` | `3.2.0-beta.10` | `3.2.0-beta.11` | `3.2.0-rc.0` | `3.2.0-rc.1` | `3.2.0-rc.2` | `3.2.0-rc.3` | +| Git tag | `v3.2.0-beta.0` | `v3.2.0-beta.1` | `v3.2.0-beta.2` | `v3.2.0-beta.3` | `v3.2.0-beta.4` | `v3.2.0-beta.5` | `v3.2.0-beta.6` | `v3.2.0-beta.7` | `v3.2.0-beta.8` | `v3.2.0-beta.9` | `v3.2.0-beta.10` | `v3.2.0-beta.11` | `v3.2.0-rc.0` | `v3.2.0-rc.1` | `v3.2.0-rc.2` | `v3.2.0-rc.3` | +| `adcp_version` wire pin | `"3.2-beta.0"` | `"3.2-beta.1"` | `"3.2-beta.2"` | `"3.2-beta.3"` | `"3.2-beta.4"` | `"3.2-beta.5"` | `"3.2-beta.6"` | `"3.2-beta.7"` | `"3.2-beta.8"` | `"3.2-beta.9"` | `"3.2-beta.10"` | `"3.2-beta.11"` | `"3.2-rc.0"` | `"3.2-rc.1"` | `"3.2-rc.2"` | `"3.2-rc.3"` | +| Documentation selector | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-beta` | `3.2-rc` | `3.2-rc` | `3.2-rc` | `3.2-rc` | Only send a prerelease wire pin to a peer that advertises that exact value in `get_adcp_capabilities.adcp.supported_versions`. Prerelease pins are exact: a -buyer pinned to `"3.2-rc.1"` must not silently negotiate to another prerelease, +buyer pinned to `"3.2-rc.3"` must not silently negotiate to another prerelease, and a stable `"3.2"` pin must not silently negotiate to a prerelease. ## Use matched SDK prereleases @@ -80,6 +86,9 @@ SDK 14 includes typed caller and server support for the compact media-buy lifecycle, the RC.1 schemas and compliance assets, version-aware request signing, governance plan-adjustment reporting, and agent notification configuration. It retains 3.0 and 3.1 adaptation for mixed-version testing. + +The current `rc` npm tag of `@adcp/sdk` is ahead of this checkpoint: it embeds `3.2.0-rc.2` and adds the seller-side reporting modules (`@adcp/sdk/reporting/source` and `@adcp/sdk/reporting/ledger`). The repository checkpoint alignment follows once the Python and Go SDKs publish matching bundles. + See [Choose your SDK](/docs/building/by-layer/L4/choose-your-sdk) for the support matrix and install guidance. @@ -92,19 +101,20 @@ registration, response builders, signing, and transport/server building blocks remain role-dependent; consult the SDK matrix before treating schema parity as complete L1–L3 coverage. -## Use the RC.1 artifact directly +## Use the RC.3 artifact directly -Download the signed RC.1 protocol bundle rather -than copying schemas from `main` or from the moving `/schemas/latest/` path: +RC.3 has no matched SDK, so the signed bundle is the only way to test it. +Download it rather than copying schemas from `main` or from the moving +`/schemas/latest/` path: ```bash -curl -fLO https://adcontextprotocol.org/protocol/3.2.0-rc.1.tgz -curl -fLO https://adcontextprotocol.org/protocol/3.2.0-rc.1.tgz.sha256 -shasum -a 256 -c 3.2.0-rc.1.tgz.sha256 -tar -xzf 3.2.0-rc.1.tgz +curl -fLO https://adcontextprotocol.org/protocol/3.2.0-rc.3.tgz +curl -fLO https://adcontextprotocol.org/protocol/3.2.0-rc.3.tgz.sha256 +shasum -a 256 -c 3.2.0-rc.3.tgz.sha256 +tar -xzf 3.2.0-rc.3.tgz ``` -The extracted `adcp-3.2.0-rc.1/` directory contains: +The extracted `adcp-3.2.0-rc.3/` directory contains: - `manifest.json` — release version, bundle contents, skills, and file count; - `schemas/` — source-shaped and bundled request/response schemas, including @@ -122,13 +132,13 @@ Useful direct-artifact tests are: 1. Generate or refresh types from the pinned bundled schemas. 2. Validate representative requests and responses for the roles you implement. 3. Compare your advertised tools with `schemas/manifest.json`. -4. Exercise raw MCP or A2A calls with `adcp_version: "3.2-rc.1"` against a +4. Exercise raw MCP or A2A calls with `adcp_version: "3.2-rc.3"` against a staging peer that advertises the same pin. 5. Run the compliance assets with a source-compatible runner if you maintain one. Do not weaken production authentication to accommodate a prerelease runner. -**No 3.2 verification badge is currently issued for a prerelease.** Treat RC.1 as an +**No 3.2 verification badge is currently issued for a prerelease.** Treat RC.3 as an implementation input, not a certification target. @@ -144,7 +154,7 @@ An SDK support claim must name all of the following: The SDK compatibility matrix lives in [Choose your SDK](/docs/building/by-layer/L4/choose-your-sdk). All three rows name exact RC.1 support with different higher-layer coverage. -None implies support for another checkpoint. Treat generated 3.2 types and +None implies support for another checkpoint, and none names RC.2 or RC.3. Treat generated 3.2 types and validators in every other SDK as unavailable until its row names an exact package and protocol checkpoint. Raw JSON calls may still be possible, but they are not equivalent to SDK support. @@ -155,15 +165,16 @@ SDK implementation bugs in the SDK's own repository. Accepted protocol fixes receive a changeset and ship in a later prerelease; published prereleases are never rebuilt in place. -## Current RC.1 checkpoint +## Current RC.3 checkpoint -Protocol beta.1 through beta.11, RC.0, and RC.1 are published. TypeScript SDK -RC.32, Python SDK beta.14, and Go SDK v3.2.1 embed RC.1. Before -treating a test result as RC.1 protocol evidence, confirm that: +Protocol beta.1 through beta.11 and RC.0 through RC.3 are published. +TypeScript SDK RC.35, Python SDK beta.14, and Go SDK v3.2.1 all embed RC.1. +Before treating a test result as RC.3 protocol evidence, confirm that: -- the test uses the signed RC.1 artifact directly or an exact RC.1 SDK pairing; -- both peers advertise `"3.2-rc.1"` before calls use that pin; -- the integration scenarios below run against RC.1 and retain the exact +- the test uses the signed RC.3 artifact directly, on the raw wire or through + types generated from it — no published SDK pairing is RC.3 evidence; +- both peers advertise `"3.2-rc.3"` before calls use that pin; +- the integration scenarios below run against RC.3 and retain the exact bundle version; - copy/paste installation and validation commands have been executed as published; @@ -250,8 +261,20 @@ release as working groups resolve scope and interoperability risk. training agent implements it. Capability declarations remain authoritative. - Experimental surfaces retain their [experimental-status contract](/docs/reference/experimental-status). A 3.2 prerelease does not graduate them to stable. -- The `3.2-rc` documentation selector moves forward; `3.2-beta` remains frozen - at beta.11. Pinned semver artifacts and documentation snapshots remain immutable. +- The `3.2-rc` documentation selector moves forward with each release-docs + snapshot, so it can trail the newest signed bundle by one checkpoint; + `3.2-beta` remains frozen at beta.11. Pinned semver artifacts and + documentation snapshots remain immutable. +- RC.3 is tagged and published as + [`v3.2.0-rc.3`](https://github.com/adcontextprotocol/adcp/releases/tag/v3.2.0-rc.3), + with signed assets attached. Its documentation snapshot lands separately, so + the `3.2-rc` selector can still show RC.2 for a short window. +- Superseded 3.x beta artifacts were retired from the repository and runtime + image on 2026-09-14. Only the `3.2.0-beta.11` schema bundle stays hosted, to + back the frozen `3.2-beta` documentation selector. Previously published beta + URLs continue to resolve from the artifact CDN on a best-effort basis only; + move pinned beta adopters to `3.2.0-rc.3`. Release-candidate and stable + artifacts are never retired. - Stable schema aliases continue to resolve to stable releases during prerelease. Use pinned prerelease URLs when validating prerelease behavior. @@ -266,7 +289,7 @@ Include this information in a prerelease issue: - schema path or JSON Pointer involved; - expected and actual behavior; - minimal redacted payload and validation error; -- whether the problem blocks RC.1 interoperability or only an older SDK-backed +- whether the problem blocks RC.3 interoperability or only an older SDK-backed checkpoint. Never include credentials, signed URLs, bearer tokens, private keys, or live diff --git a/docs/reference/migration/3-1-to-3-2.mdx b/docs/reference/migration/3-1-to-3-2.mdx index 0ea9ca17896..93f50d21c3a 100644 --- a/docs/reference/migration/3-1-to-3-2.mdx +++ b/docs/reference/migration/3-1-to-3-2.mdx @@ -8,11 +8,11 @@ description: "Role-based migration checklist for adopting the AdCP 3.2 release c # Migrating from 3.1 to 3.2 -**3.2 is in release candidate.** RC.1 is the current signed protocol -checkpoint. TypeScript `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and -Go `adcp/v3@v3.2.1` embed it exactly; Python and Go higher-level coverage -remains role-dependent. Keep production traffic pinned to `"3.1"` -while validating an exact 3.2 checkpoint in staging. +**3.2 is in release candidate.** RC.3 is the current signed protocol +checkpoint, and no SDK embeds it yet: TypeScript `@adcp/sdk@14.0.0-rc.35`, +Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` all still embed +`3.2.0-rc.1`; Python and Go higher-level coverage remains role-dependent. Keep production traffic pinned to `"3.1"` while validating an +exact 3.2 checkpoint in staging. 3.2 is a minor release over 3.1. Existing integrations do not need to adopt the @@ -47,23 +47,23 @@ surfaces by hand. | Step | Who | Action | |---|---|---| | 1 | Everyone | Keep production on `"3.1"`; choose an exact 3.2 prerelease artifact for staging. | -| 2 | SDK and codegen maintainers | Generate from the signed `3.2.0-rc.1` protocol tarball, not `main` or `/schemas/latest/`. | +| 2 | SDK and codegen maintainers | Generate from the signed `3.2.0-rc.3` protocol tarball, not `main` or `/schemas/latest/`. | | 3 | Sellers and agents | Advertise the exact prerelease in `adcp.supported_versions` and echo the release actually served. | -| 4 | Buyers | Send `adcp_version: "3.2-rc.1"` only after exact capability discovery; never silently move between prerelease pins. | +| 4 | Buyers | Send `adcp_version: "3.2-rc.3"` — or whichever exact prerelease the peer advertises — only after exact capability discovery; never silently move between prerelease pins. | | 5 | Media-buy implementations | Move create/update success handling completely to `media_buy_status`. | | 6 | Signing implementations | Require `content-digest` coverage and migrate request `Signature` and `Content-Digest` binary values to RFC 8941 padded Base64. | | 7 | Creative implementations | Adopt canonical format capability/product discovery and isolate legacy projection at compatibility boundaries. | -| 8 | Compliance operators | Test RC.1 from its signed assets or an exact SDK pairing: `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, or Go `adcp/v3@v3.2.1`. Retain the exact package and wire versions. | +| 8 | Compliance operators | Test RC.3 from its signed assets; no SDK pairing covers RC.3 yet. `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` all test RC.1. Retain the exact package and wire versions. | | 9 | Delivery-reporting implementations | Emit and consume currency at media-buy or package grain, move qualified outcomes to `by_package[].metric_values`, and stop producing new `aggregated_totals`. | ## Required to claim 3.2 behavior ### Serve and echo the exact release -During prerelease, version matching is exact. A seller serving RC.1 advertises -`"3.2-rc.1"`. Do not advertise stable `"3.2"` before GA, silently negotiate -between prerelease pins, or treat a major-only declaration as evidence of 3.2 -support. +During prerelease, version matching is exact. A seller serving RC.3 advertises +`"3.2-rc.3"`; a seller still on RC.1 advertises `"3.2-rc.1"`. Do not advertise +stable `"3.2"` before GA, silently negotiate between prerelease pins, or treat +a major-only declaration as evidence of 3.2 support. The 3.2 compliance posture makes missing `supported_versions` or a missing response echo a blocking failure for a 3.2 claim, even though the fields remain @@ -244,7 +244,7 @@ See [Cross-role governance enforcement](/docs/reference/migration/cross-role-gov | Creative agent | Canonical supported-format capabilities, operation selection, and explicit compatibility handling for legacy named formats. | | Signals or measurement agent | Exact prerelease pin and only the attestation, targeting, or feedback capabilities actually implemented. | | Governance provider/service | Exact prerelease pin, `governance.campaign` experimental declaration, and the complete cross-role authorization migration. | -| SDK maintainer | Signed RC.1 bundle ingestion, generated-type/validator tests, exact support matrix entry, and protocol feedback destined for the next prerelease. | +| SDK maintainer | Signed RC.3 bundle ingestion, generated-type/validator tests, exact support matrix entry, and protocol feedback destined for the next prerelease. | | Compliance operator | Matching assets, SDK package, and wire pin end to end; no 3.2 badge from a prerelease checkpoint. | ## Rollback diff --git a/docs/reference/migration/index.mdx b/docs/reference/migration/index.mdx index 28e484b987d..c977f8809a1 100644 --- a/docs/reference/migration/index.mdx +++ b/docs/reference/migration/index.mdx @@ -14,7 +14,7 @@ This page covers every breaking change when upgrading from AdCP 2.x to 3.0, with -**Preparing for 3.2?** Start with the [3.1 to 3.2 migration guide](/docs/reference/migration/3-1-to-3-2). For the signed RC.1 artifact, exact wire pins, matched SDKs, and feedback guidance, read the [3.2 prerelease program](/docs/reference/3-2-beta). +**Preparing for 3.2?** Start with the [3.1 to 3.2 migration guide](/docs/reference/migration/3-1-to-3-2). For the signed RC.3 artifact, exact wire pins, the SDK checkpoint pairings, and feedback guidance, read the [3.2 prerelease program](/docs/reference/3-2-beta). diff --git a/docs/reference/migration/reliable-reporting-status-loop.mdx b/docs/reference/migration/reliable-reporting-status-loop.mdx index 19ef867067d..549b5d769ef 100644 --- a/docs/reference/migration/reliable-reporting-status-loop.mdx +++ b/docs/reference/migration/reliable-reporting-status-loop.mdx @@ -8,8 +8,9 @@ description: "Breaking-change notice and migration guide for sync_reporting_stat **Experimental breaking-change notice published September 12, 2026.** Under AdCP's six-week experimental-surface notice policy, the Core requirement described here must not appear in an immutable release before October 24, -2026. `3.2.0-rc.2` publishes the task as opt-in; making it *required* is what -the notice window governs. Published `3.2.0-rc.1` remains unchanged. +2026. `3.2.0-rc.2` publishes the task as opt-in and `3.2.0-rc.3` hardens it; +making it *required* is what the notice window governs. Published +`3.2.0-rc.1` remains unchanged. Reliable Reporting RC.1 lets a seller publish its obligation/revision state and @@ -19,9 +20,9 @@ or unreadable. A seller can therefore project `healthy` while the buyer's webhook, exact revision read, or destination access is failing. `3.2.0-rc.2` closes that loop additively with opt-in -[`sync_reporting_status`](/docs/media-buy/task-reference/sync_reporting_status). -A seller advertises `consumer_status_task` only when the task and readback are -implemented. The requirement itself lands only in the next eligible minor +[`sync_reporting_status`](/docs/media-buy/task-reference/sync_reporting_status), +and `3.2.0-rc.3` hardens it. A seller advertises `consumer_status_task` only +when the task and readback are implemented. The requirement itself lands only in the next eligible minor after the notice window. Both changes remain inside the experimental `media_buy.reporting_delivery` surface. @@ -43,8 +44,8 @@ Before (`3.2.0-rc.1`): } ``` -Current opt-in form, and required form in the next eligible minor after the -notice window: +Current opt-in form (`3.2.0-rc.3`), and required form in the next eligible +minor after the notice window: ```json { @@ -183,8 +184,9 @@ billing-feed constraints. Tracked in `reporting_status_id` are now required on that issue code. The code itself shipped in RC.1's `reporting-status-issue.json` enum, so an RC.1 seller that already emits it must add `opened_at` — fixed at first emission, never advanced -on re-emission — before validating against current source. No other issue code -is affected. +on re-emission — before validating against +[`3.2.0-rc.3`](https://adcontextprotocol.org/schemas/3.2.0-rc.3/core/reporting-status-issue.json). +No other issue code is affected. ## Verifying the loop diff --git a/docs/reference/release-notes.mdx b/docs/reference/release-notes.mdx index 760a9752118..617947544f2 100644 --- a/docs/reference/release-notes.mdx +++ b/docs/reference/release-notes.mdx @@ -11,21 +11,21 @@ Authoritative version-by-version release record for AdCP, with cumulative change ## Version 3.2.0 -**Status:** Release-candidate cycle — minor release targeting the 3.2.0 milestone. RC.1 is the current signed protocol checkpoint. It completes the experimental Reliable Reporting 1.0 contract and hardens delivery, reach, and vendor-metric semantics. TypeScript `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` embed RC.1 exactly; Python and Go higher-level coverage remains role-dependent. Stable wire shapes remain backward compatible except for the ratified `media_buy_status` cleanup and request-signature encoding migration described below; explicitly experimental surfaces may carry noticed changes under the [experimental-status contract](/docs/reference/experimental-status). +**Status:** Release-candidate cycle — minor release targeting the 3.2.0 milestone. RC.3 is the current signed protocol checkpoint. It hardens the experimental Reliable Reporting consumer-status loop, adds a shared MediaBuy-level frequency cap with structured product frequency-cap constraints, and adds request-only targeting inputs with `null`-clear semantics. No SDK embeds RC.3 yet: TypeScript `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` all still embed RC.1; Python and Go higher-level coverage remains role-dependent. Stable wire shapes remain backward compatible except for the ratified `media_buy_status` cleanup and request-signature encoding migration described below; explicitly experimental surfaces may carry noticed changes under the [experimental-status contract](/docs/reference/experimental-status). **Reliable Reporting breaking-change notice — published September 12, 2026.** -Current source adds opt-in `sync_reporting_status` so a buyer can report missing, +RC.2 publishes opt-in `sync_reporting_status` so a buyer can report missing, unreadable, contradictory, or exactly received reporting back to the seller; the seller can then detect when a received revision becomes stale after restatement. -The loop is hardened for RC.2: a stale `received` gets a bounded re-read grace +RC.3 hardens the loop: a stale `received` gets a bounded re-read grace window before it escalates, buyers owe a status by `expected_at + automated_recovery_window_seconds` (counted in `obligation_counts.consumer_status_pending`, never in health), issues carry `opened_at` / `issue_state` / `external_ref` with an optional `consumer_mismatch_escalation_seconds` and `operations_contact`, and `content_mismatch` names contract-fact disagreements through a closed -`mismatch_code`. `reporting-delivery-config.json` also reserves +`mismatch_code`. RC.3's `reporting-delivery-config.json` also reserves `authoritative_party`; sellers MUST reject `consumer` with `UNSUPPORTED_FEATURE` until a later minor defines the buyer-deposited revision task ([#7440](https://github.com/adcontextprotocol/adcp/issues/7440)). Sellers advertise @@ -51,7 +51,9 @@ See the [migration guide](/docs/reference/migration/reliable-reporting-status-lo | `3.2.0-beta.10` | Add managed reporting delivery, authenticated principals, audio VAST and DOOH support, programmed channel collections, committed collection selection, and expanded conformance coverage | Previous protocol checkpoint with exact TypeScript support in `@adcp/sdk@14.0.0-beta.28` and exact Python schema/type support in `adcp==8.0.0b11` | | `3.2.0-beta.11` | Add `get_principal` to the MCP media-buy role profile and align the public training agent with the latest beta bundle | Previous protocol checkpoint with exact TypeScript support in `@adcp/sdk@14.0.0-beta.29` and exact Python schema/type support in `adcp==8.0.0b12` | | `3.2.0-rc.0` | Publish the first 3.2 release candidate after beta integration fixes and expand reporting lifecycle conformance | Previous checkpoint with exact TypeScript support in `@adcp/sdk@14.0.0-beta.31` and exact Python schema/type support in `adcp==8.0.0b13` | -| `3.2.0-rc.1` | Complete the experimental Reliable Reporting 1.0 contract and harden delivery currency, aggregate reach, vendor-metric identity, and integration behavior | Current signed protocol checkpoint with exact TypeScript, Python, and Go SDK pairings | +| `3.2.0-rc.1` | Complete the experimental Reliable Reporting 1.0 contract and harden delivery currency, aggregate reach, vendor-metric identity, and integration behavior | Previous checkpoint with exact Python support in `adcp==8.0.0b14` and exact Go support in `adcp/v3@v3.2.1` | +| `3.2.0-rc.2` | Add the opt-in experimental Reliable Reporting `sync_reporting_status` consumer-status loop, buyer and orchestrator storyboards with a buyer-orchestrator compliance track, cursor pagination for truncated `get_media_buy_delivery` breakdowns, sub-country product coverage filters, and restored `canonical-forecast-point` constraints | Previous checkpoint. No maintained SDK embeds it; test it from the signed bundle | +| `3.2.0-rc.3` | Harden the consumer-status loop (`content_mismatch` and `mismatch_code`, a bounded grace window for a stale `received`, the buyer posting deadline and `obligation_counts.consumer_status_pending`, issue lifecycle fields, `operations_contact`, and the reserved `authoritative_party`), add a shared MediaBuy-level `frequency_cap` with structured product frequency-cap constraints, add request-only targeting with `null`-clear semantics, and retire superseded beta artifacts | Current signed protocol checkpoint. No SDK embeds it yet; test it from the signed bundle | Each prerelease is immutable. The `3.2-rc` documentation selector advances to the latest release candidate; the `3.2-beta` selector remains frozen at beta.11. Pinned protocol, schema, compliance, and documentation artifacts remain available. See the [3.2 prerelease program](/docs/reference/3-2-beta). @@ -59,12 +61,13 @@ Each prerelease is immutable. The `3.2-rc` documentation selector advances to th - **Media buying:** compact listing, immutable proposal negotiation, direct purchase, proposal acceptance, operational control, seller-optimized budgets and bidding, atomic total-budget changes, revenue-share pricing, creative rotation, warnings, and durable indicators. - **Identity and connections:** an experimental authenticated-principal layer for caller-scoped webhooks, reusable reporting destinations, asynchronous capability declarations, optimistic replacement, and `principal.changed` repair. -- **Targeting and audiences:** targeting-aware discovery, portable demographic predicates, named places, value-aware regions, browser families, property exclusions, audience evidence, and exact package readback. +- **Targeting and audiences:** targeting-aware discovery, portable demographic predicates, named places, value-aware regions, browser families, property exclusions, audience evidence, exact package readback, and request-only targeting inputs where each dimension distinguishes omission, a non-null replacement, and an explicit `null` that clears it. +- **Frequency management:** a shared MediaBuy-level `frequency_cap` counted once across every package, advertised through `media_buy.aggregate_frequency_capping` and product `media_buy_support`, plus structured product frequency-cap constraints on `overlay_support.frequency_cap_support` and the `update_media_buy_frequency_cap` action. - **Inventory identity:** first-class programmed channel collections, including FAST and virtual linear streams, with host-property carriage mapping and collection-scoped host attestation for owner-sold avails. - **Creative:** canonical capability discovery, image pixel density and rendition sets, localization, async preview opt-in, audio loudness, VAST 4.3 and validation levels, accessibility detail, and synthetic depiction provenance. - **Security and evidence:** required body binding for 3.2 request-signing profiles, OAuth discovery grading, portable attestations, rights and signal evidence, signed brand-response verification, and safer secured asset access. - **Operations and measurement:** capability/account change notifications, snapshot-and-log repair, demographic and spot delivery, metric accountability, deterministic filters, fixture resolution, and capability-selected runtime projections. -- **Reliable Reporting:** a separately discovered, versioned experimental three-tier contract for expected-period obligations, immutable official revisions, managed materializations, authenticated receipts, correction ledgers, and repairable status. RC.1 completes Reliable Reporting 1.0. +- **Reliable Reporting:** a separately discovered, versioned experimental three-tier contract for expected-period obligations, immutable official revisions, managed materializations, authenticated receipts, correction ledgers, and repairable status. RC.1 completes Reliable Reporting 1.0; RC.2 adds the opt-in two-sided `sync_reporting_status` consumer-status loop; RC.3 hardens that loop and reserves `authoritative_party` for a later minor. - **Experimental surfaces:** cross-role campaign governance revisions and Trusted Match authentication, routing, attribution, and creative-data cleanup under their existing experimental declarations. ### Adopter action @@ -75,8 +78,8 @@ Each prerelease is immutable. The `3.2-rc` documentation selector advances to th | A seller or service | Advertise and echo the exact prerelease served, emit canonical status/retry shapes, and declare only capabilities actually implemented. | | A signing implementation | Require `content-digest` coverage for every signed request body on a 3.2 signing endpoint. | | A creative implementation | Prefer canonical capability and product format discovery; isolate named-format conversion at compatibility boundaries. | -| An SDK maintainer | Generate from the current signed RC.1 tarball, publish an exact support statement, and route accepted protocol corrections into a later prerelease. | -| A compliance operator | Test RC.1 from its signed assets or an exact SDK pairing: `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, or Go `adcp/v3@v3.2.1`. Retain exact package and wire versions and do not issue a 3.2 badge from a prerelease checkpoint. | +| An SDK maintainer | Generate from the current signed RC.3 tarball, publish an exact support statement, and route accepted protocol corrections into a later prerelease. | +| A compliance operator | Test RC.3 from its signed assets; no SDK pairing covers RC.3 yet. `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` all test RC.1. Retain exact package and wire versions and do not issue a 3.2 badge from a prerelease checkpoint. | ### Required 3.2 migrations diff --git a/docs/reference/versioning.mdx b/docs/reference/versioning.mdx index e5e5c8dbc50..a8a1316fcd8 100644 --- a/docs/reference/versioning.mdx +++ b/docs/reference/versioning.mdx @@ -250,12 +250,13 @@ The v2 sunset is the documented exception to this commitment: v2 predates this p |---------|--------| | **3.0** | April 2026 — GA release | | **3.1** | Late June 2026 | -| **3.2** | RC.1 published September 2026; GA targeted for late September 2026 | +| **3.2** | RC.3 published September 2026; GA targeted for late September 2026 | | **4.0** | Early 2027 — next major, accumulated breaking changes | -The 3.2 cycle began with a protocol-first beta before SDK convergence. RC.1 is -now the current signed protocol checkpoint. TypeScript SDK RC.32, Python SDK -beta.14, and Go SDK `adcp/v3@v3.2.1` embed it exactly. See the +The 3.2 cycle began with a protocol-first beta before SDK convergence. RC.3 is +now the current signed protocol checkpoint, and no SDK embeds it yet: +TypeScript SDK RC.35, Python SDK beta.14, and Go SDK `adcp/v3@v3.2.1` all +still embed `3.2.0-rc.1`. See the [3.2 prerelease program](/docs/reference/3-2-beta). Further 3.x releases are scheduled based on implementation feedback and working group priorities, with at least 8 weeks between stable releases. Planned scope for each release is tracked on the [GitHub milestones page](https://github.com/adcontextprotocol/adcp/milestones) — open issues on the `3.1.0` and `3.2.0` milestones reflect current candidate work, not fixed commitments. diff --git a/docs/reference/versions.mdx b/docs/reference/versions.mdx index f7ab1bbafa1..ec2329125d5 100644 --- a/docs/reference/versions.mdx +++ b/docs/reference/versions.mdx @@ -13,7 +13,7 @@ description: "Every published AdCP version, its status, and its end-of-life date | Status | Versions | Wire pin | What it means | |---|---|---|---| -| **Release candidate** | 3.2 (current prerelease: `rc.1`) | `"3.2-rc.1"` | Development and staging only. RC.1 is the current signed protocol checkpoint. TypeScript SDK RC.32, Python SDK beta.14, and Go SDK 3.2.1 embed it exactly. Follow the [3.2 prerelease program](/docs/reference/3-2-beta). | +| **Release candidate** | 3.2 (current prerelease: `rc.3`) | `"3.2-rc.3"` | Development and staging only. RC.3 is the current signed protocol checkpoint, tagged and published as [`v3.2.0-rc.3`](https://github.com/adcontextprotocol/adcp/releases/tag/v3.2.0-rc.3). No SDK embeds RC.3 yet — TypeScript SDK RC.35, Python SDK beta.14, and Go SDK 3.2.1 all still embed `3.2.0-rc.1`. Test RC.3 from its signed artifacts with raw-wire or code-generation workflows. Follow the [3.2 prerelease program](/docs/reference/3-2-beta). | | **Active** | 3.1 (current stable: 3.1.20) | `"3.1"` | Current production minor release. See [What's New in AdCP 3.1](/docs/reference/whats-new-in-3-1) for the feature set. | | **Maintained** | 3.0 (current stable: 3.0.26) | `"3.0"` | Supported previous minor for existing production integrations. Receives compatibility and security patches. | | **End of life** | 2.0.0, 2.1.0, 2.5.0–2.5.3 | — | No patches. Migrate to 3.0. See [v2 sunset](/docs/reference/v2-sunset). | @@ -21,7 +21,7 @@ description: "Every published AdCP version, its status, and its end-of-life date **Wire values are release-precision only.** Send `"3.1"` for the stable 3.1 line or `"3.0"` for the maintained 3.0 line. Do not send patch components like `"3.0.19"` or full semver pre-release values like `"3.1.0-rc.15"`. Historical prerelease pins such as `"3.1-rc.15"` remain valid only for agents that explicitly advertise those prerelease values. See [patches are not negotiated](/docs/reference/versioning#patches-are-not-negotiated). -*Status legend: Pending beta = announced but not yet published. Release candidate = immutable prerelease checkpoint for development and staging. Beta = superseded checkpoint; beta bundles are retired from the repository and runtime image once a release candidate exists, and previously published beta URLs are served from the artifact CDN on a best-effort basis only. Active = current stable generation. Maintained = supported previous minor. Security-only = patches for security issues only, no features. End of life = no patches. Planned = not yet released.* +*Status legend: Pending beta = announced but not yet published. Beta and release candidate = immutable prerelease checkpoints for development and staging. A one-time cleanup on 2026-09-14 retired some historical 3.x beta bundles from the repository and runtime image; remaining and future published prerelease artifacts stay immutable, and retired beta URLs are served from the artifact CDN on a best-effort basis only. Active = current stable generation. Maintained = supported previous minor. Security-only = patches for security issues only, no features. End of life = no patches. Planned = not yet released.* ## All published versions @@ -45,7 +45,9 @@ Supported patches don't change the wire contract. Upgrading within 3.0.x is alwa | Version | Released | Notes | |---|---|---| -| **3.2.0-rc.1** | 2026-09-05 | Current protocol checkpoint. Completes the experimental Reliable Reporting 1.0 contract and hardens delivery, reach, and vendor-metric semantics. TypeScript SDK RC.32, Python SDK beta.14, and Go SDK 3.2.1 embed it exactly; use `"3.2-rc.1"` only with peers that explicitly advertise it. | +| **3.2.0-rc.3** | 2026-09-14 | Current protocol checkpoint, published as [`v3.2.0-rc.3`](https://github.com/adcontextprotocol/adcp/releases/tag/v3.2.0-rc.3). Hardens the experimental Reliable Reporting consumer-status loop (`content_mismatch` with a closed `mismatch_code`, a bounded grace window for a stale `received`, the buyer posting deadline and `obligation_counts.consumer_status_pending`, issue lifecycle fields, and the reserved `authoritative_party` value), adds a shared MediaBuy-level `frequency_cap` with structured product frequency-cap constraints, and adds request-only targeting inputs with `null`-clear semantics. No SDK embeds it yet; use `"3.2-rc.3"` only with peers that explicitly advertise it. | +| 3.2.0-rc.2 | 2026-09-13 | Previous protocol checkpoint. Adds the opt-in experimental Reliable Reporting `sync_reporting_status` consumer-status loop, buyer and orchestrator storyboards with a buyer-orchestrator compliance track, cursor pagination for truncated `get_media_buy_delivery` breakdowns, sub-country product coverage filters, and restored `canonical-forecast-point` constraints. No maintained SDK embeds it. | +| 3.2.0-rc.1 | 2026-09-05 | Previous protocol checkpoint. Completes the experimental Reliable Reporting 1.0 contract and hardens delivery, reach, and vendor-metric semantics. TypeScript `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` embed it exactly. | | 3.2.0-rc.0 | 2026-09-03 | First 3.2 release candidate. TypeScript SDK beta.31 and Python SDK beta.13 embed it exactly; Go SDK 3.2.0 remains generated from beta.9. | | 3.2.0-beta.11 | 2026-09-03 | Previous protocol checkpoint. Adds `get_principal` to the MCP media-buy role profile alongside `sync_principal`, and aligns training-agent and compliance guidance with the beta.10 bundle. TypeScript SDK beta.29 and Python SDK beta.12 embed it exactly. | | 3.2.0-beta.10 | 2026-09-01 | Previous protocol checkpoint. Adds managed reporting delivery, authenticated principals, audio VAST and DOOH support, programmed channel collections, and committed collection selection. TypeScript SDK beta.28 and Python SDK beta.11 embed it. | @@ -58,7 +60,7 @@ Supported patches don't change the wire contract. Upgrading within 3.0.x is alwa | 3.2.0-beta.3 | 2026-08-19 | Integration checkpoint, superseded by beta.4 for new beta testing. | | 3.2.0-beta.2 | 2026-08-19 | Integration checkpoint, superseded by beta.3 for new beta testing. | | 3.2.0-beta.1 | 2026-08-19 | Integration-correction checkpoint, superseded by beta.2 for new beta testing. | -| 3.2.0-beta.0 | 2026-08-17 | Protocol-first beta input for SDK work. Retired from the repository and runtime image on 2026-09-14 together with the other 3.x betas except `3.2.0-beta.11` (frozen `3.2-beta` documentation selector), `3.2.0-beta.6` (training-agent retained checkpoint), and `3.1.0-beta.7` (TypeScript SDK side bundle); pinned adopters should move to `3.2.0-rc.2`. | +| 3.2.0-beta.0 | 2026-08-17 | Protocol-first beta input for SDK work. Retired from the repository and runtime image on 2026-09-14 together with the other 3.x betas except `3.2.0-beta.11` (frozen `3.2-beta` documentation selector), `3.2.0-beta.6` (training-agent retained checkpoint), and `3.1.0-beta.7` (TypeScript SDK side bundle); pinned adopters should move to `3.2.0-rc.3`. | | 3.1.0-rc.1 through 3.1.0-rc.15 | 2026-05-29 to 2026-06-16 | Superseded by 3.1.0 GA. These artifacts remain available for pinned prerelease adopters and release forensics. | | 3.0.0-beta.1 through rc.2 | 2026-01-26 to 2026-03-15 | Superseded. | | 3.0.0-rc.3 | 2026-04-01 | Superseded by GA. See [prerelease upgrade notes](/docs/reference/migration/prerelease-upgrades) if you adopted rc.3. | @@ -98,8 +100,8 @@ Targeted for early 2027. 3.x is mid-cycle — see the [planned releases table](/ | If you are… | Use | |---|---| | Building a new production integration today | **3.1**. Pin `"3.1"` on the wire. | -| Implementing or testing 3.2 without an SDK | Use the signed **3.2 RC.1** artifacts with raw-wire or code-generation workflows. Follow the [prerelease program](/docs/reference/3-2-beta). | -| Running an SDK-backed 3.2 integration test | Pair exact RC.1 wire pin `"3.2-rc.1"` with `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, or Go `adcp/v3@v3.2.1`. | +| Implementing or testing 3.2 without an SDK | Use the signed **3.2 RC.3** artifacts with raw-wire or code-generation workflows. Follow the [prerelease program](/docs/reference/3-2-beta). | +| Running an SDK-backed 3.2 integration test | Pair the exact RC.1 wire pin `"3.2-rc.1"` with `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, or Go `adcp/v3@v3.2.1`. No SDK embeds RC.2 or RC.3 schemas or types yet — test those against their signed artifacts on the raw wire, or from types generated from them, until the next SDK wave ships. | | Running an existing 3.0 integration | Stay on **3.0** while you migrate, or move to **3.1** when your SDK and validation are ready. | | Running a 2.5.x integration | Upgrade now — out of support. Start with the [migration guide](/docs/reference/migration). | | Running a 2.0 or 2.1 integration | Upgrade now — out of support. | diff --git a/docs/reference/whats-new-in-3-2.mdx b/docs/reference/whats-new-in-3-2.mdx index ac18dfb0422..e39133004c7 100644 --- a/docs/reference/whats-new-in-3-2.mdx +++ b/docs/reference/whats-new-in-3-2.mdx @@ -8,18 +8,24 @@ description: "AdCP 3.2 turns a media-buy conversation into an explicit lifecycle # What's new in AdCP 3.2 -**3.2 is in release candidate.** RC.1 is the current signed protocol -checkpoint. TypeScript `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and -Go `adcp/v3@v3.2.1` embed it exactly; Python and Go higher-level coverage -remains role-dependent. Use these exact packages for RC.1 staging tests. See the +**3.2 is in release candidate.** RC.3 is the current signed protocol +checkpoint, and no SDK embeds it yet: TypeScript `@adcp/sdk@14.0.0-rc.35`, +Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` all still embed RC.1; Python +and Go higher-level coverage remains role-dependent. Test RC.3 +from its signed bundle, and use these exact packages for staging tests against +the checkpoints they embed. See the [3.2 prerelease program](/docs/reference/3-2-beta). -**New in RC.1:** Reliable Reporting 1.0 becomes a named, version-discovered -experimental capability, with stronger delivery, reach, vendor-metric, and -reconciliation semantics. The public training seller and all three maintained -SDKs now expose the exact RC.1 checkpoint. +**New in RC.3:** the opt-in Reliable Reporting consumer-status loop published +in RC.2 is hardened — `content_mismatch` with a closed `mismatch_code`, a +bounded grace window for a `received` overtaken by a seller restatement, a +buyer posting deadline surfaced through +`obligation_counts.consumer_status_pending`, issue lifecycle fields, and a +reserved `authoritative_party`. RC.3 also adds a shared MediaBuy-level +`frequency_cap`, structured product frequency-cap constraints, and +request-only targeting inputs with `null`-clear semantics. AdCP 3.2 turns a media-buy conversation into a commercial lifecycle that @@ -49,7 +55,8 @@ tools after capability discovery. confirmation gates. No membership or setup is required. - Choose an SDK-backed RC.1 path or use the signed RC.1 bundle directly. + Use the signed RC.3 bundle directly, or take an SDK-backed path on the + checkpoint your SDK embeds. Add compact lifecycle tools incrementally while keeping 3.1 integrations @@ -196,8 +203,23 @@ RC.0 introduced the reporting-status baseline. RC.1 makes Reliable Reporting a named, version-discovered experimental capability and adds source-timezone schedules, checkpointed repair for missed or out-of-order events, immutable billing-purpose evidence, adjustment and receipt reconciliation, and -evidence-scoped reliability statistics. RC.1 has matched TypeScript, Python, -and Go SDK pairings. See +evidence-scoped reliability statistics. + +RC.2 publishes the opt-in `sync_reporting_status` consumer-status loop, so a +buyer's report of what it actually received sits beside the seller's +obligations in `get_reporting_status` as immutable, buyer-attributed history. +RC.3 hardens that loop: `content_mismatch` with a closed `mismatch_code` +names contract-fact disagreements — explicitly not measurement disputes — a +`received` overtaken by a seller restatement gets a bounded grace window +before it escalates, an unmet buyer posting deadline is counted in +`obligation_counts.consumer_status_pending` without ever changing seller +health, issues carry `opened_at` / `issue_state` / `external_ref` alongside +optional `consumer_mismatch_escalation_seconds` and `operations_contact`, and +`authoritative_party: "consumer"` is reserved for a later minor and MUST be +rejected with `UNSUPPORTED_FEATURE` today. The loop stays opt-in until the +notice window closes on October 24, 2026, and becomes required Core only in +the next eligible minor after that date. No maintained SDK embeds RC.2 or +RC.3 yet, so both are raw-wire or code-generation targets today. See [Implementing Reliable Reporting Core](/docs/media-buy/reporting-core-implementation-guide). ### A durable connection for authenticated principals @@ -260,7 +282,12 @@ exact package readback — including committed inventory selection: collections, the latter materializing concrete selectors even when the selection came from collection-list references. Products can also disclose per-package cardinality for country inclusion, country exclusion, and proximity targeting before a buyer -creates or updates a package. Daypart windows now default explicitly to each +creates or updates a package. On the request-only targeting and +product-purchase inputs for the compact and established create/update +surfaces, each targeting dimension distinguishes three cases: omission +(inherit or preserve), a non-null replacement, and an explicit `null` that +clears the dimension. Discovery, capability, accepted-commercial-term, and +readback schemas stay strict and non-null. Daypart windows now default explicitly to each inventory unit's seller-assigned local clock and can instead name one IANA timezone for a synchronized schedule; products declare the supported modes through `overlay_support.daypart_targets`. Products whose package frequency-cap support @@ -434,14 +461,14 @@ for the remaining runner and coverage gaps. | If you are… | Review before advertising 3.2 | |---|---| -| Any seller or service | Advertise `"3.2-rc.1"` only when serving that exact prerelease, echo it on responses, and keep 3.1 traffic on its negotiated contract. | +| Any seller or service | Advertise `"3.2-rc.3"` — or whichever exact prerelease you serve — only when serving that exact prerelease, echo it on responses, and keep 3.1 traffic on its negotiated contract. | | A buyer | Gate compact tools and optional targeting on capabilities; do not infer 3.2 support from a major-only declaration. | | A media-buy implementer | Use `media_buy_status` on create/update success payloads; root `status` is the task-envelope state. | -| A reporting implementer | Treat Reliable Reporting as a separately discovered, versioned experimental capability. Do not infer RC.1 fields from RC.0 or from legacy delivery reporting. | +| A reporting implementer | Treat Reliable Reporting as a separately discovered, versioned experimental capability. Do not infer RC.3 fields from an earlier checkpoint or from legacy delivery reporting, and advertise `consumer_status_task` only when the loop is implemented. | | A signing implementation | Require `content-digest` coverage for every signed body on a 3.2 signing endpoint. | | A creative implementation | Prefer canonical capability and product format discovery; retain legacy conversion only at a proven compatibility boundary. | -| An SDK maintainer | Generate from the signed RC.1 tarball, name the exact supported bundle, and feed accepted protocol corrections into the next prerelease. | -| A compliance operator | Test RC.1 from its signed assets or an exact SDK pairing: `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, or Go `adcp/v3@v3.2.1`. Retain exact package and wire versions end to end, and do not issue a 3.2 badge from a prerelease. | +| An SDK maintainer | Generate from the signed RC.3 tarball, name the exact supported bundle, and feed accepted protocol corrections into the next prerelease. | +| A compliance operator | Test RC.3 from its signed assets; no SDK pairing covers RC.3 yet. `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` all test RC.1. Retain exact package and wire versions end to end, and do not issue a 3.2 badge from a prerelease. | ## Start here diff --git a/server/public/index.html b/server/public/index.html index 5b868dd6bc5..60694d60a68 100644 --- a/server/public/index.html +++ b/server/public/index.html @@ -34,11 +34,11 @@