Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/add-principal-registration-walkthrough.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Add the "Set up your buyer agent with a seller" walkthrough for the experimental principal layer: seller-issued credentials, `get_adcp_capabilities` discovery, `sync_principal` declarations, webhooks, and a reusable destination through the `action_required` to `ready` proof flow, account feed binding, `get_principal` readback, the kill switch, and the `principal.changed` webhook. Cross-linked from `sync_principal`, `get_principal`, and the 3.2 guide.
5 changes: 5 additions & 0 deletions .changeset/canonicalization-step5-empty-path-no-query.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Add four URL-canonicalization conformance vectors covering step 5 when the path is empty and no query is present. No normative change: step 5 already reads "If the path is empty AND an authority is present, substitute `/`", and `docs/reference/url-canonicalization.mdx` is untouched. The vectors close a detection gap. Of the 37 cases in `test-vectors/request-signing/canonicalization.json` exactly one had an empty path, and that one carried `?x=1` — the query in step 5's illustrative example. An implementation that read the example as the condition and gated the substitution on the query therefore scored 37 of 37 while emitting `https://host` for `https://host`, where RFC 3986 §6.2.3 and step 5 both require `https://host/`. The new cases are the bare authority, a non-default port that must keep the slash after the port rather than before it, an IPv6 literal whose brackets stay inside the slash, and the empty-query spelling `https://host?` where steps 5 and 7 compose to `https://host/?`. That last one is where a query-gated reading fails on its own terms: the raw URL carries a `?` but the parsed query is the empty string. The gap is not hypothetical — the Python SDK had exactly this gating, and the four cases fail against it before its fix and pass after, with the original 37 green throughout. Canonicalization divergence is silent until it surfaces as a signature mismatch or an agent-URL authorization failure, and the same algorithm governs every URL-identifier surface in the "Where it applies" table, not only `@target-uri`.
5 changes: 5 additions & 0 deletions .changeset/compose-version-envelope-compact.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Compose `core/version-envelope.json` via root `allOf` in the nine 3.2 compact/experimental request schemas (`accept_proposal`, `buy_products`, `control_media_buy`, `decline_proposals`, `list_products`, `refine_proposals`, `request_proposals`, `list_account_changes`, `sync_reporting_status`) and `core/compact-task-submitted.json` (version and protocol envelopes), so generated SDK types share envelope ancestry with the rest of the spec. The local `adcp_version` / `adcp_major_version` property declarations are retained on strict (`additionalProperties: false`) requests because draft-07 does not evaluate properties across `allOf`; request validation is unchanged. Response validation of `compact-task-submitted.json` is tightened: it now enforces the version-envelope grammar and the protocol envelope's field constraints (including the `task_status`/`response_status` ban); conformant sellers already satisfy both. `tests/composed-schema-validation.test.cjs` now fails when any non-MCP `*-request.json` stops composing the envelope, and `core/version-envelope.json` states its actual coverage.
5 changes: 5 additions & 0 deletions .changeset/controller-seeding-requires-controller.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Compliance storyboards that seed fixtures through `comply_test_controller` (`prerequisites.controller_seeding: true`) now declare `requires: [controller]`. A seller without a test controller receives one storyboard-level `requirement_unmet` skip naming `controller`, not a `missing_test_controller` grade on every seeded step; a controller that disappears mid-run still grades per step. The maintenance sweep adds the gate to existing 3.2 storyboards (excluding main-only outcome-target additions) without changing step logic (a seller with no controller now skips each such storyboard as a whole, including steps that did not need seeding, instead of running those steps and grading the seeded ones per step), and a new lint (`lint-storyboard-controller-requires`, wired into the compliance build) fails if a storyboard seeds through the controller without the gate. The conformance docs now state the policy: reference sellers SHOULD implement `comply_test_controller`; translator and adapter sellers that front platforms which cannot seed state are not expected to.
5 changes: 5 additions & 0 deletions .changeset/dedupe-bundled-provenance-defs.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Bundled schemas (`/schemas/{version}/bundled/`) now carry `core/provenance.json` once in root `$defs.Provenance` and reference it from each call-site as `{"$ref": "#/$defs/Provenance", "description": "..."}`, instead of inlining the full body 40-80 times per bundle. Bundle output shrinks by roughly 20%. Source schemas and validation behavior are unchanged, and per-call-site descriptions are preserved. In bundles with repeated provenance, enclosing inlined schemas now lose their deep `$id` (existing behavior for subtrees containing hoisted `$defs` refs), and two `required_disclosures` description strings may differ because the enum hoist fingerprints enums without their description.
16 changes: 16 additions & 0 deletions .changeset/fix-advanced-delivery-reporting-join-key.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
"adcontextprotocol": patch
---

fix(compliance): add operator_unit join key to advanced_delivery_reporting storyboard

The `advanced_delivery_reporting` storyboard was missing the `account.operator_unit.id`
join key on all graded steps (`sync_account`, `discover_product`, `create_buy`,
`get_narrowed_format_delivery`). Without this key, the controller-seeded product
(`advanced_reporting_video`) could not be resolved by any seller because nothing on
the wire linked the harness-identity seed to the acme-account reads. The storyboard
graded `partial` on fully-conformant sellers.

Adds `operator_unit.id: compliance-media_buy_seller_advanced_delivery_r-a37f01cb`
to all four steps, matching the isolation pattern used by every other
controller-seeded storyboard in the bundle. Bumps version to 1.0.3.
5 changes: 5 additions & 0 deletions .changeset/fix-billing-gate-required-discovery.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Make billing_gate_dispatch 1.1.2 capability discovery required while preserving its account capability gate. Agents with account capabilities can receive a passing overall verdict after valid billing checks; agents without account capabilities remain not applicable.
5 changes: 5 additions & 0 deletions .changeset/fix-non-guaranteed-lifecycle-status.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Accept active as well as pending_creatives in the non-guaranteed sales storyboard so sellers without a creative library can complete the buying flow. Clarify the capability-dependent lifecycle expectations while retaining context, package-state, and upstream-traffic checks.
5 changes: 5 additions & 0 deletions .changeset/fix-typed-proposal-negotiation-seed.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Repair the `typed_proposal_negotiation` compliance storyboard so it can pass against a conformant 3.2 seller. The seed step now calls `request_proposals` (the 3.2 proposal-lifecycle tool, as `declined_proposal_refinement` does) instead of legacy `get_products`, so the proposal it targets is one `refine_proposals` can resolve; the storyboard is gated on the seller advertising `request_proposals` in `media_buy.lifecycle_tools` and on `comply_test_controller`, and declares `controller_seeding: true` so its fixture products are seeded. The `unsatisfied_constraints` `field_contains` check addresses array elements with `[*]`, and each post-seed phase now names its upstream phases with `depends_on`, so a capability-gated phase the seller does not support (for example the unsupported-dimension rejection when the seller declares `flight`) skips alone instead of cascade-skipping finalize, accept, amendment, cancellation, and batch coverage.
5 changes: 5 additions & 0 deletions .changeset/product-channel-declaration-guidance.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Recommend an explicit nonempty `channels` declaration on every product in AdCP 3.x while preserving existing property-based inheritance and validation constraints. Buyers request channel details before classifying sparse responses; omission from an unrequested projection does not establish an absent seller declaration. Explain format-option narrowing and distinguish declared buying contexts from independent evidence of actual delivery or per-channel totals. Document the proposed 4.0 required-channel migration, with removal of reliance on omission-based inheritance and the projection policy left to that future breaking change. Schemas remain unchanged.
5 changes: 5 additions & 0 deletions .changeset/profile-3-2-step-0-1-mirrors.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Compliance corpus: `profile-3.2/` now mirrors every remaining root request-signing vector except `negative/018`, so a `covers_content_digest: "required"` verifier, which is every 3.2+ verifier, can grade them. The new negatives are `001`, `011`, `019`, `021`, `022`, `023`, `024`, `026`, `027`, `028`, `029`, `030` and `031`, and the new positive guards are `013`, `014` and `015`. Each mirror keeps its root number, slug and expected code, covers `content-digest` wherever a `Signature-Input` exists, and carries a correct `Content-Digest`, so the step-0/1 fault is the vector's only fault. `negative/018` stays unmirrored because `forbidden` is illegal in 3.2. The vector README now requires every vector to carry exactly one fault (adcp#7577). No normative change.
7 changes: 7 additions & 0 deletions .changeset/reporting-revision-unreadable-issue.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
"adcontextprotocol": patch
---

Add the `REVISION_UNREADABLE` reporting status issue code for a published revision that the seller still owes within `status_retention_days` but cannot currently serve or verify, for example because its stored rows are missing or fail the revision binding. The issue always belongs to the seller and carries the affected `reporting_obligation_id` plus a new `reporting_revision_id` field. It is `delayed` with `wait_for_retry` while automatic repair runs, and `action_required` with `contact_seller` once that repair can't restore the content. While the issue is open, the obligation is neither `healthy` nor `complete`, and an authorized exact read through `get_media_buy_delivery` returns `SERVICE_UNAVAILABLE` rather than `REFERENCE_NOT_FOUND`. The issue is retired when the committed content is readable again or the revision's retention window ends. An obligation whose official revision is lost never becomes `complete`. Readers that strictly validate the closed issue-code enum must accept the new value. Closes #8082.

Release classification: this is an additive change confined to the experimental Reliable Reporting surface (`media_buy.reporting_delivery`). It introduces no new transport error code or stable envelope field: authorized exact reads use the existing `SERVICE_UNAVAILABLE` code. Strict reporting-schema consumers must update their definitions before accepting the new issue. This patch classification does not advance the consumer-status requirement or superseded-snapshot compaction notices.
7 changes: 7 additions & 0 deletions .changeset/request-signing-step1-grading-vectors.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
"adcontextprotocol": patch
---

Add request-signing conformance vectors for three step-1 rules the corpus did not grade (adcp#7905). `negative/029` rejects a duplicate `sig1` label on the `Signature` header (RFC 9421 §4.2, RFC 8941 §3.2). `negative/030` rejects `Content-Digest: SHA-256=…, sha-256=…`: `SHA-256` is a parse-invalid dictionary key under RFC 8941 §3.1.2, and verifiers must not fold case. `negative/031` rejects an unbracketed IPv6 `Host` header (`::1`) with `request_target_uri_malformed` at step 10; it carries a real signature over the URL authority so the header is the only fault. Adds three false-positive guards, `positive/013` (distinct `sig1`/`sig2` labels), `014` (`sha-256` + `sha-512`) and `015` (`Host: [2001:db8::1]:8443`). No new requirement; the profile-3.2 mirrors follow in adcp#7733.

Correction to `negative/026-non-ascii-host`: its expected outcome changes from `request_signature_header_malformed` (step 1) to `request_target_uri_malformed` (step 10), aligning the vector with the `security.mdx` error table and `canonicalization.json`, which map a raw non-ASCII host to `request_target_uri_malformed`. The vector now also carries a real Ed25519 signature over the A-label base so the host is its only fault. Verifiers that matched the old code to pass 026 must update.
5 changes: 5 additions & 0 deletions .changeset/seller-optimized-min-spend-fixture-package.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Compliance: in the `seller_optimized_budget` storyboard, place the positive minimum-spend target on the second (retargeting) package instead of the first. The `@adcp/sdk` storyboard request builder authors a package budget on the first package of every `create_media_buy` step, which made a minimum-spend target on that package exceed its own injected cap for a seller that declares both package caps and minimum-spend targets. The target-versus-cap contradiction stays graded by `seller_optimized_min_spend_target_exceeds_package_cap`.
2 changes: 1 addition & 1 deletion docs/accounts/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ When `require_operator_auth` is `true` (**account-id namespaces**), operators au

When `require_operator_auth` is `false` (**buyer-declared accounts**), the agent is trusted and account-scoped calls use the natural key (`brand` + `operator`). Most sellers provision these relationships through [`sync_accounts`](/docs/accounts/tasks/sync_accounts). A seller MAY instead lazily provision on the first account-scoped request when billing and every other required setting are unambiguous from capabilities or the authenticated agent's onboarding defaults. A lazy-provisioning seller MUST keep accepting the natural key and MUST expose [`list_accounts`](/docs/accounts/tasks/list_accounts) for recovery. If buyer input is required before use, the seller MUST expose `sync_accounts`.

Follow [Provision a seller-mediated account](/docs/accounts/provisioning-walkthrough) for a complete buyer-declared workflow from discovery through human setup, activation, and first spend.
Follow [Provision a seller-mediated account](/docs/accounts/provisioning-walkthrough) for a complete buyer-declared workflow from discovery through human setup, activation, and first spend. Follow [Set up your buyer agent with a seller](/docs/accounts/principal-registration-walkthrough) for the standing, caller-scoped setup that comes before accounts: webhooks, reusable reporting destinations, and declarations.

An **ad network** may use both models simultaneously — buyer-declared accounts on the buyer-facing side (the network is agent-trusted) and an account-id namespace with each underlying platform (the network authenticates as an operator). See the [Sponsored Intelligence guide — account model for networks](/docs/sponsored-intelligence/networks#account-model-for-networks) for the full account chain: `buyer agent → network (buyer-declared) → AI platform (account-id namespace)`.

Expand Down
Loading
Loading