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
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
11 changes: 0 additions & 11 deletions .changeset/catalog-reporting-collection-applicability-3-2.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/gate-image-creative-on-format-kind.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/product-signal-targeting-wholesale-gate.md

This file was deleted.

14 changes: 14 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,19 @@
# Changelog

## 3.2.10

### Patch Changes

- bdc61ec: Stop the 3.2 collection and reporting storyboards from failing sellers on features they do not offer. Backports the applicability part of #8336 and narrows #8428 for the 3.2 runner (#8744).

`advanced_delivery_reporting` no longer seeds a video product. It discovers a native wholesale sandbox product that advertises format breakdown, with a fixed-price CPM option, and grades metric narrowing, the `by_format` array, truncation disclosure and the applied-sort echo on that product. When no product qualifies, the storyboard reports `fixture_unsatisfied`: the feature was not tested, which is neither a pass nor proof of nonsupport. It no longer grades `time_based_views`, because the controller cannot inject view observations and the old checks expected an invented 2-second threshold.

`collection_selection` and `owner_sold_channel_carriage` keep their existing checks. They now run only when wholesale discovery finds a native product that allows collection targeting and declares at least one domain-qualified collection. Otherwise they report `fixture_unsatisfied`. Discovery failures still fail. Sellers that do not advertise the wholesale buying mode grade all three storyboards not applicable.

Full independent collection grading needs the 3.3 fixture contract and runner, and ships in 3.3. No schema changes.
- 5541479: Stop the `dependency_impairment` and `dependency_impairment_cardinality` storyboards from failing sellers whose selected format option is not an image format (adcp#8770). Both storyboards send a fixed 300x250 image creative against the first product's first format option. When that option is a `display_tag`, `video_vast` or other non-image kind, the creative phases are now skipped instead of failing a seller that correctly refuses an image it does not accept. Image sellers run the storyboards unchanged.
- 8f159e4: Gate `product_signal_targeting` and `cross_path_targeting_provenance` on wholesale support in both `media_buy.buying_modes` and `signals.discovery_modes`. A seller that advertises only brief discovery no longer runs them. Their negative probes now cascade-skip when product discovery fails, instead of sending an unresolved `$context.product_id`.

## 3.2.9

### Patch Changes
Expand Down
196 changes: 196 additions & 0 deletions dist/compliance/3.2.10/domains/brand/index.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,196 @@
id: brand_baseline
version: "1.0.0"
title: "Brand baseline"
protocol: brand
category: brand_baseline
summary: "Baseline protocol storyboard — every brand agent must declare the brand protocol in capabilities and return a schema-valid brand identity."
track: brand
required_tools:
- get_brand_identity

narrative: |
Brand protocol agents are the identity layer of AdCP. Their job is to hold
brand identity data (names, logos, colors, fonts, tone) and expose it to
other agents — buyer agents, creative agents, DSPs — that need to render
on-brand creative or verify who a campaign is for.

The baseline tests the minimum contract that every brand agent honors,
regardless of what additional capabilities (rights licensing, creative
approval) it layers on top:

1. Declare `brand` in `supported_protocols` on `get_adcp_capabilities`.
2. Respond to `get_brand_identity` with a schema-valid identity manifest.
3. Reject unknown `brand_id` values with a structured error.

Rights licensing (`get_rights`, `acquire_rights`, `update_rights`,
`creative_approval`) ships experimentally in 3.0 and is covered by the
`brand-rights` specialism storyboard, not this baseline.

agent:
interaction_model: brand_agent
capabilities: []
examples:
- "Any brand agent (simple identity host or full rights platform)"
- "Brand-owned agents (Acme Outdoor)"
- "Third-party brand identity platforms"
- "Agency-hosted brand agents"

caller:
role: buyer_agent
example: "Any buyer, creative agent, or DSP needing brand identity"

prerequisites:
description: |
The test kit provides a sample brand (Nova Motors) that any brand agent
can serve identity for.
test_kit: "test-kits/nova-motors.yaml"

phases:
- id: capability_discovery
title: "Capability discovery"
narrative: |
The buyer calls `get_adcp_capabilities` to confirm the agent declares
the brand protocol before issuing any brand-identity call.

steps:
- id: get_capabilities
title: "Check agent capabilities"
narrative: |
Verify that the agent declares `brand` in `supported_protocols`.
Without this claim the buyer MUST NOT send `get_brand_identity`.
task: get_adcp_capabilities
schema_ref: "protocol/get-adcp-capabilities-request.json"
response_schema_ref: "protocol/get-adcp-capabilities-response.json"
doc_ref: "/protocol/get_adcp_capabilities"
comply_scenario: capability_discovery
stateful: false
expected: |
Return capabilities declaring `brand` in `supported_protocols`.

sample_request:
context:
correlation_id: "brand_baseline--get_capabilities"
validations:
- check: response_schema
description: "Response matches get-adcp-capabilities-response.json schema"
- check: field_present
path: "supported_protocols"
description: "Response declares supported_protocols"

- id: brand_identity_retrieval
title: "Brand identity retrieval"
narrative: |
The buyer calls `get_brand_identity` to retrieve the brand's identity
manifest. The minimum contract is a schema-valid response that echoes
the requested `brand_id` and carries at least one name.

steps:
- id: get_brand_identity
title: "Retrieve brand identity"
narrative: |
The buyer calls `get_brand_identity` with a known `brand_id`. The
response MUST match the brand-identity schema and echo the
requested `brand_id`. Rich fields (logos, colors, fonts, tone,
visual_guidelines) are optional at the baseline level — the
minimum bar is that identity resolution works and is schema-valid.
task: get_brand_identity
schema_ref: "brand/get-brand-identity-request.json"
response_schema_ref: "brand/get-brand-identity-response.json"
doc_ref: "/brand-protocol/tasks/get_brand_identity"
stateful: false
expected: |
Return a schema-valid brand identity that echoes the requested
brand_id and includes at least one name.

sample_request:
brand_id: "nova_motors"
context:
correlation_id: "brand_baseline--get_brand_identity"
context_outputs:
- path: "brand_id"
key: "brand_id"

validations:
- check: response_schema
description: "Response matches get-brand-identity-response.json schema"
- check: field_present
path: "brand_id"
description: "Response includes brand_id"
- check: field_value
path: "brand_id"
value: "nova_motors"
description: "Returned brand_id echoes the requested brand"
- check: field_present
path: "names"
description: "Response includes brand names"

- id: unknown_brand_rejection
title: "Unknown brand rejection"
narrative: |
Agents MUST reject unknown `brand_id` values with a structured
AdCP error rather than returning an empty or fabricated manifest.

steps:
- id: get_brand_identity_unknown
title: "Reject unknown brand ID"
narrative: |
The buyer calls `get_brand_identity` with a `brand_id` the agent
does not serve. The response MUST be a structured error with a
recovery classification — not a success response with empty
fields.
task: get_brand_identity
schema_ref: "brand/get-brand-identity-request.json"
response_schema_ref: "brand/get-brand-identity-response.json"
doc_ref: "/brand-protocol/tasks/get_brand_identity"
stateful: false
expected: |
Return an AdCP error response indicating the brand is not known
to this agent.

sample_request:
brand_id: "brand_that_does_not_exist_12345"
context:
correlation_id: "brand_baseline--get_brand_identity_unknown"

expect_error: true
negative_path: payload_well_formed
validations:
- check: error_code
value: "REFERENCE_NOT_FOUND"
description: "Error code indicates brand-not-found. REFERENCE_NOT_FOUND is the canonical fallback per error-handling.mdx (brands lack a dedicated *_NOT_FOUND code)."

- id: brand_discovery
title: "Optional brand discovery"
narrative: |
Agents that implement the experimental `search_brands` task expose a
schema-valid discovery surface without making that task part of the
baseline brand protocol requirement.

steps:
- id: search_brands
title: "Search the agent's brand roster"
task: search_brands
schema_ref: "brand/search-brands-request.json"
response_schema_ref: "brand/search-brands-response.json"
doc_ref: "/brand-protocol/tasks/search_brands"
comply_scenario: brand_discovery
requires_tool: search_brands
stateful: false
expected: |
Return a schema-valid ranked array of brand stubs. An empty array is
valid when the agent has no matching roster entry.
sample_request:
query: "automotive brands with electric vehicles"
countries: ["US"]
context:
correlation_id: "brand_baseline--search_brands"
validations:
- check: response_schema
description: "Response matches search-brands-response.json schema"
- check: field_present
path: "brands"
description: "Discovery response includes the brands array"
- check: field_value
path: "context.correlation_id"
value: "brand_baseline--search_brands"
description: "Context correlation_id returned unchanged"
Loading
Loading