You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Proposal: a 4.0 compatibility check in the compliance suite, so 3.x agents learn what 4.0 breaks before it ships #8332
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
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:
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".
The suite runs every declared check and reports passed, failing (with the fix), or not observable for each.
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).
Implemented. The AdCP 4.0 compatibility check is in the compliance suite and advisory throughout 3.x.
What shipped
Registrystatic/compliance/source/universal/v4-compatibility.yaml (feat(compliance): advisory AdCP 4.0 compatibility checks for 3.x agents #8335). Each 4.0 check has a stable id, its tracking issue, a one-line detection rule, the fix, and where the suite observes it. A report joins one run's output against the registry and shows each check as passed, failing (with the fix), or not observable. Checks ride on steps that already run, as advisory validations (permanent_advisory) or existing 3.2 requirements, so none can fail a 3.x run.
New check kindall_fields_present (absent or empty arrays grade not observable, never a vacuous pass). It's implemented in @adcp/sdk 16.0.0 together with per-step validation verdicts on ComplianceResult and the canonical 4.0 notice codes.
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.
Activity
feat(compliance): advisory AdCP 4.0 compatibility checks for 3.x agen…
feat(schema): mark every 4.0 removal and tie it to the compatibility …
fix(compliance): backport advisory AdCP 4.0 compatibility checks to 3…
feat(registry): show advisory AdCP 4.0 readiness on the agent page (#…
feat(schema): mark every 4.0 removal and tie it to the compatibility …
feat(compliance): give every 4.0 schema removal a tracking issue (#8387)
bokelley commentedon Oct 22, 2026
Implemented. The AdCP 4.0 compatibility check is in the compliance suite and advisory throughout 3.x.
What shipped
Registry
static/compliance/source/universal/v4-compatibility.yaml(feat(compliance): advisory AdCP 4.0 compatibility checks for 3.x agents #8335). Each 4.0 check has a stable id, its tracking issue, a one-line detection rule, the fix, and where the suite observes it. A report joins one run's output against the registry and shows each check as passed, failing (with the fix), or not observable. Checks ride on steps that already run, as advisory validations (permanent_advisory) or existing 3.2 requirements, so none can fail a 3.x run.First checks:
format_ids_removed_in_4_0(4.0: remove deprecated exact format_ids fields and compatibility projections #7629)major_versions_removed_in_4_0andadcp_version_echo_required_in_4_0(Epic: Tier 3 — close the loop on version-negotiation at 4.0 #3572)request_signing_required_in_4_0(Mandatory request signing for mutating calls (RFC 9421 HTTP Signatures or JWS) #2307)legacy_hmac_fallback_removed_in_4_0([meta] Coordinate RFC 9421 webhook signing migration — adoption telemetry + threshold + ownership #4205)signed_requests_specialism_deprecated(4.0: remove deprecated signed-requests value from specialism enum #3078)Require
channelson Product in AdCP 4.0 #7869, 4.0: require duration_ms on hosted video assets #5668, RFC (4.0): the account_id returned by sync_accounts is the only account reference after provisioning #7850 and spec(media-buy): 4.0 cascade — rename nestedstatustomedia_buy_statuson get_media_buys / get_media_buy_delivery / core/media-buy #4905 are held until their 4.0 decisions are made.New check kind
all_fields_present(absent or empty arrays grade not observable, never a vacuous pass). It's implemented in@adcp/sdk16.0.0 together with per-step validation verdicts onComplianceResultand the canonical 4.0 notice codes.Completeness: every schema node removed in 4.0 is marked
"x-removed-in": "4.0.0"(46 today), and the registry lists each one exactly once, under its check or as not checked with a reason and a tracking issue (feat(schema): mark every 4.0 removal and tie it to the compatibility registry #8341, feat(compliance): give every 4.0 schema removal a tracking issue #8387). The ten removals that had no issue are now 4.0: remove the format-level build and pricing surface (input/output_format_ids, pricing_options, canonical_parameters, list_creative_formats pricing) #8377–4.0: remove the 3.1 compatibility projections (legacy terms ref, purchase_continuation) #8386. The build lint fails when the registry, storyboards, notice codes, schema markers and migration guide disagree.Migration guide
docs/reference/migration/v4-compatibility.mdx, with one anchor per check id.3.2 line: the checks are backported to
3.2.x(fix(compliance): backport advisory AdCP 4.0 compatibility checks to 3.2.x #8340) and ship from 3.2.6.Registry agent page: shows the advisory 4.0 readiness report per agent (feat(registry): show advisory AdCP 4.0 readiness on the agent page #8342), and this repo is on
@adcp/sdk16.1.0 (chore(deps): update @adcp/sdk to 16.1.0 and drop the creative build probe bridge #8355).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.
feat(schema): mark every 4.0 removal and give it a tracking issue on …