AdCP 3.0 rc2 prep: release notes, cleanup, and doc updates#1488
Merged
Conversation
…s, everyone builds (#1482 #1483 #1484 #1485 #1487) - FAQ: add buy-side and certification sections with CTAs (closes #1482) - Intro: early audience fork (buy vs build) after narrative (closes #1483) - Learning overview: urgency-driven opening, Addie description, "everyone builds" section, duration fixes (closes #1485) - AI media: extract ad network section to standalone page (closes #1487) - Surface "everyone builds" across buyer's guide, FAQ, agentic advertising explainer, intro, and A1 module (closes #1484) - Expert review fixes: correct Basics to 3 modules/~50 min, membership caveat on cert pricing, accurate vibe coding framing, "discovers pricing" not "negotiates" Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
All top-level protocol, guide, reference, and certification groups now start collapsed to reduce visual noise in the doc sidebar. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Images adcp-04-workflow.png and adcp-05-governance.png don't exist yet. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Schema Link Check ResultsCommit:
|
This concept belongs on the AAO site (about.html already covers it), not in protocol docs. Intro.mdx and FAQ handle protocol-level context. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…eatures schema delete_content_standards had a doc page but no JSON schema — content standards should be archived via update, not deleted. get_property_features schema was orphaned after property governance moved to the stateful property list model. Also fixes broken certification-tools link to removed agentic-advertising page. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add Version 3.0.0-rc.2 section to release notes with 8 features and 5 breaking changes - Update intro.mdx banner, homepage banner, and JSON-LD metadata to rc.2 - Update roadmap status to rc.2 released - Fix schema version references (2.6.0 → 2.5.3, schema registry v2 → v3) - Fix OpenRTB comparison table version reference - Fix S3 signals specialist description to match module scope - Fix role track durations to match database (103/92/89 min) - Fix FAQ "buyer agent" → "advertising agent" for build project - Fix geo-content-planner reference to removed agentic-advertising page - Consolidate duplicate A1 module resource for intro page Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Addie, website, admin UI, member features, docs-only fixes, and internal tooling changes should not bump the protocol version. Converted from patch/minor to empty changesets. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Brand rights lifecycle (get_rights, acquire_rights, update_rights) - Visual guidelines on brand.json for generative creative - Shows and episodes content dimension - AI media channel (20th channel) - Creative governance (get_creative_features) - Brand tone structured format (breaking change) - Account resolution removal (breaking change) - Updated at-a-glance table, migration checklists, and removed-in-v3 table Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…anup - Simplify intro.mdx banner (stability caveat, not feature list) - Rewrite homepage banner as outcome-oriented copy with "New:" prefix - Update FAQ maturity to rc.2 and "suitable for pilot implementations" - Add rc1→rc2 trajectory sentence to roadmap - Move certification/docs to "Other Updates" in release notes - Remove brand logo fields from breaking changes (additive, not breaking) - Fix channel count 19→20 in 5 files (ai_media added in rc2) - Add AI media to A1 channel list - Fix FAQ Practitioner duration range (~90–105 min) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
bokelley
changed the title
bokelley
added a commit
that referenced
this pull request
May 3, 2026
Phase 1 BuyerAgentRegistry adoption per adcp-client#1269. Unblocked by SDK 6.8.0's extra-forwarding fix (issue #1484 / PR #1488 — both filed and reviewed in this session). - SDK pin bumped to ^6.8.0. - Bearer authenticator stamps extra: { demo_token: token } on the AuthPrincipal returned for demo-* test bearers. The token doesn't survive AdcpCredential normalization (api_key carries key_id: SHA-256(token)); extra is the documented escape hatch for prefix-based test conventions. - New buyer-agent-registry.ts — BuyerAgentRegistry.bearerOnly resolver that reads extra.demo_token, delegates to commercial-relationships.ts for the principal → relationship lookup (single source of truth), and returns a BuyerAgent record with the appropriate billing_capabilities Set. Unrecognized credentials return null (uniform-response rule). Signed credentials are refused per the bearerOnly factory's posture. - All six v6 tenant platforms wire agentRegistry: trainingBuyerAgentRegistry — sales, signals (v6-platform.ts), governance, creative, creative-builder, brand. Framework calls agentRegistry.resolve(authInfo) once per request before accounts.resolve and threads the resolved record through ctx.agent to platform handlers. No gate-logic changes. commercial-relationships.ts remains the source of truth and the legacy /mcp path keeps consuming it via handleSyncAccounts. The v6 platforms now ALSO have ctx.agent.billing_capabilities populated — forward-compat for SDK Phase 2 (adcp-client#1292) framework-level enforcement of BILLING_NOT_PERMITTED_FOR_AGENT. Tests: 6 new unit tests on the registry resolver covering all branches (prefix matching, missing extra, defensive type-checks, http_sig refusal). Existing sync-accounts-gates integration test (11 tests) and account-handlers unit test (22 tests) all pass — proves the gate logic still fires correctly under the new wiring. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bokelley
added a commit
that referenced
this pull request
May 3, 2026
Phase 1 BuyerAgentRegistry adoption per adcp-client#1269. Unblocked by SDK 6.8.0's extra-forwarding fix (issue #1484 / PR #1488 — both filed and reviewed in this session). - SDK pin bumped to ^6.8.0. - Bearer authenticator stamps extra: { demo_token: token } on the AuthPrincipal returned for demo-* test bearers. The token doesn't survive AdcpCredential normalization (api_key carries key_id: SHA-256(token)); extra is the documented escape hatch for prefix-based test conventions. - New buyer-agent-registry.ts — BuyerAgentRegistry.bearerOnly resolver that reads extra.demo_token, delegates to commercial-relationships.ts for the principal → relationship lookup (single source of truth), and returns a BuyerAgent record with the appropriate billing_capabilities Set. Unrecognized credentials return null (uniform-response rule). Signed credentials are refused per the bearerOnly factory's posture. - All six v6 tenant platforms wire agentRegistry: trainingBuyerAgentRegistry — sales, signals (v6-platform.ts), governance, creative, creative-builder, brand. Framework calls agentRegistry.resolve(authInfo) once per request before accounts.resolve and threads the resolved record through ctx.agent to platform handlers. No gate-logic changes. commercial-relationships.ts remains the source of truth and the legacy /mcp path keeps consuming it via handleSyncAccounts. The v6 platforms now ALSO have ctx.agent.billing_capabilities populated — forward-compat for SDK Phase 2 (adcp-client#1292) framework-level enforcement of BILLING_NOT_PERMITTED_FOR_AGENT. Tests: 6 new unit tests on the registry resolver covering all branches (prefix matching, missing extra, defensive type-checks, http_sig refusal). Existing sync-accounts-gates integration test (11 tests) and account-handlers unit test (22 tests) all pass — proves the gate logic still fires correctly under the new wiring. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
delete_content_standardstask andget_property_featuresschema (never shipped)What happens on merge
The release workflow automatically:
changeset version→ bumps to3.0.0-rc.2build:schemas --release→ createsdist/schemas/3.0.0-rc.2/Test plan
🤖 Generated with Claude Code