Skip to content

Proposal: a 4.0 compatibility check in the compliance suite, so 3.x agents learn what 4.0 breaks before it ships #8332

Closed

Description

@bokelley

Problem

AdCP 4.0 removes or tightens a lot of what 3.x agents depend on today. Each change has its own tracking issue, but nothing tells a 3.x agent which of them it relies on. A seller finds out when a 4.0 buyer stops working with it.

Some of the changes already tracked:

4.0 change Issue What breaks for a 3.x agent
Exact plural format_ids removed; canonical format_options only #7629 Products described only with legacy format ids
adcp.major_versions and adcp_major_version removed #3572 Agents that declare a release only through major_versions
signed-requests specialism value removed #3078 Agents that still declare it
channels required on Product #7869 Products without channels
account_id from sync_accounts is the only account reference #7850 Agents that accept other account references after provisioning
Nested status renamed to media_buy_status #4905 Clients and agents reading the old name
duration_ms required on hosted video assets #5668 Video assets without it

Proposal

Add a 4.0 compatibility check to the compliance suite. It runs against a 3.x agent and reports, for each 4.0 removal or new requirement, whether the agent depends on what 4.0 takes away. It is advisory throughout 3.x: it never fails a 3.x conformance run, it just tells the agent what to fix before 4.0.

To keep it complete without a separate list to maintain:

  1. Every 4.0 issue that removes or tightens something declares a stable check id and a one-line detection rule, for example "products declare format_ids without format_options".
  2. The suite runs every declared check and reports passed, failing (with the fix), or not observable for each.
  3. The 4.0 migration guide links each check id to its replacement.

Why now

Sellers need lead time. We operate a marketplace of AdCP sales agents, and from 1 February 2027 we require the 4.0-critical capabilities: canonical creative formats, Reliable Reporting and the compact lifecycle. Today we flag missing ones on each agent's page, with the date. Without a shared check, every buyer platform writes its own version of this list, and they will drift. One check in the compliance suite gives sellers one answer and gives the working group a measure of how ready the ecosystem is before 4.0 ships.

We can contribute the first checks, starting with canonical creative formats (#7629) and the version declaration (#3572).

Activity

  1. bokelley commented on Oct 22, 2026

    @bokelley
    ContributorAuthor

    Implemented. The AdCP 4.0 compatibility check is in the compliance suite and advisory throughout 3.x.

    What shipped

    Still to happen: live passed/failing results appear once a released compliance bundle (3.2.6 or the next 3.3 beta) carries the check ids. Until then hosted runs show those checks as not observable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions