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
  •  
  •  
  •  
File renamed without changes.
75 changes: 75 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,80 @@
# Changelog

## 3.2.0-rc.4

### Minor Changes

- 121d8b3: Add owner-selectable Legacy and Strict Spec grading profiles for verified agents, with Sandbox preview support. Persist immutable exact-role/version assessments and audited selections, project public badges through durable retries, and expose the selected profile through registry APIs, feeds, dashboard controls, badge metadata, and verification tokens.
- dc69e0b: Publish canonical supply-path verification golden vectors and an explicit evaluator semantics version. Clarify fail-closed owner-sold carriage verification for affirmative collection constraints, dangling property references, unknown or unevaluated authorization constraints, revocation precedence, agent URL identity and independent domain-level paths.

Retain authority-scoped revocations and authoritative-location pins in persistent registry state. Refuse stale or non-authoritative cache provenance and require explicit publisher attribution in cross-origin shared catalogs. Expose cache observation times and resolved URLs.

Add publisher_domain attribution to shared collection declarations and require it for cross-origin owner evidence. Preserve successful-fetch provenance through failed crawls and provide an operator command for independently confirmed authority migrations.
- 3cea56c: Add protocol-specific `anonymous_discovery` declarations for media-buy product discovery and signal discovery. The optional booleans let callers plan anonymous catalog reads without making catalog-completeness claims or weakening authentication requirements for mutations and private state.
- cfc33f6: Require recovery on AdCP 3.2 producer errors while preserving legacy 3.1 decoding and adding compatibility vectors for retry classification and scheduling.
- 33edf91: Add an optional `account` field to `sync_accounts` response rows, echoed for settings-update-mode entries. Previously the response schema required `brand` + `operator` on every row, which made settings-update mode unimplementable for account-id-namespace sellers with no buyer-declared natural key, and made `action: "failed"` rows for such accounts unrepresentable entirely. The new discriminator mirrors the pattern `sync_governance` already uses. Closes #7517.

### Patch Changes

- 70a91fe: Add compliance scenario for frequency-cap negotiation through proposal refinement (refine_frequency_cap_negotiation). Exercises replace-cap, clear-cap, and unable outcomes against the fields introduced in #7449.
- 336546b: 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.
- eb3cbd6: `canonical_format_validate_input` no longer lists `comply_test_controller` in `required_tools`. The storyboard runner's per-storyboard gate admits a storyboard when any listed tool is present, so any agent exposing the (universal) test controller was selected and then failed all 17 steps on the missing `validate_input`. Agents without `validate_input` now receive a coverage-gap skip; agents implementing it run unchanged. Same shape as #6774 (fixes #7404, bug 1).
- 8b9868a: Allow complete reporting summaries to carry the nearest future period start
from active committed configuration schedules while preserving both scope
guards, obligation boundaries, and evaluated coverage. Clarify the seller's
population rule and add portable compliance vectors, a lifecycle storyboard,
and source, generated, and runtime validation regressions.
- 17f0921: Provenance storyboards now mark every creative-library and test-controller step
with its actual tool prerequisite, so hosted grading does not fail sellers for
optional surfaces they do not advertise. Fixes #7586.
- 516c9d2: Skip billing capability discovery when an agent does not advertise the account capability block, preventing unrelated agents from receiving failing billing grades.
- af1ea26: Gate the webhook-emission storyboard's wholesale `get_products` branch set and its aggregate assertion on the advertised wholesale buying mode, so non-media-buy agents grade the branch family as not applicable.
- 7509a53: Keep the universal media-buy lifecycle and non-governance seller specialisms
ungoverned, and isolate their account natural keys so governance bindings from
other compliance scenarios cannot leak into their runs. Refs #7585.
- 4d0b482: Test kits declare the account their storyboards address. `acme-outdoor` and `nova-motors`
now carry an `account:` block naming the operator (and both sandbox spellings) that
account-bearing steps send, so a seller implementing a kit can seed the accounts those
steps reference instead of inferring them from the storyboards' sample requests. Closes the
seeding half of #7588, where one unseeded account produced 19 check failures attributed to
the tools the steps name rather than to the account they could not resolve.
- 8a4aac7: Preserve canonical document identities across bundled schemas and embedded MCP
profile resources so relocated schema packages resolve nested references fully
offline.
- 1fdb7fc: Give 35 request-signing conformance vectors bodies that are schema-valid for the operation their URL names, so a seller that validates the request payload before authenticating the caller still reaches the RFC 9421 verifier checklist. Only `request.body` changes; headers, URLs, `verifier_capability` and `expected_outcome` are untouched, and each vector's intended fault is preserved (#7567).
- 70e8363: Controller-seed canonical test-kit account prerequisites before account-scoped
storyboard steps run, using deterministic per-storyboard operator units to keep
account state isolated. This prevents missing or leaked setup from being
misgraded as failures of the tools those steps exercise. The reference training
agent now accepts those account fixtures on every applicable tenant and lets
framework task settlement emit terminal webhooks before controller completion
returns, with a bounded wait that releases the tenant lock if settlement stalls.
Refs #7588.
- 98fa207: Add the `media_buy_frequency_cap_updates` compliance scenario covering root-cap
replace and clear through `update_media_buy_frequency_cap`, atomic rejection of
`new_packages` whose product cannot join the shared counter, the resulting-state
rule for clearing a cap while adding packages, and the `ACTION_NOT_ALLOWED`
path when the package mix can no longer change the root cap. The reference
training seller now implements package and shared MediaBuy frequency caps so
the four frequency-cap scenarios execute against it, and the specification
states the `ACTION_NOT_ALLOWED` rule for root-cap changes explicitly.
- 1467e46: Training agent implements the rc.3 Reliable Reporting consumer-status hardening and the conformance storyboard grades it.

The public training agent now advertises `consumer_status_task`, serves
`sync_reporting_status`, and projects the full RC.3 contract: `content_mismatch`
with its closed `mismatch_code`, `obligation_counts.consumer_status_pending`,
issue `opened_at` / `issue_state` / `external_ref`, and the
`operations_contact` / `consumer_mismatch_escalation_seconds` capability fields
driving `recommended_action` escalation — with the escalation boundary taking
precedence over the stale-`received` grace deadline.

`comply_test_controller`'s `reporting_core_lifecycle_probe` gains two additive
operations, `advance_past_status_deadline` and `advance_past_escalation`, and
the capability-gated `reporting_consumer_status` storyboard uses them to grade
counted silence, each `mismatch_code`, `opened_at` stability across the
severity change, escalation to a `contact_*` action, and `operations_contact`
presence.

## 3.1.23

### Patch Changes
Expand Down
196 changes: 196 additions & 0 deletions dist/compliance/3.2.0-rc.4/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