diff --git a/.agents/wg/slack-context.md b/.agents/wg/slack-context.md index 116ca37c1a8..5b86c90c182 100644 --- a/.agents/wg/slack-context.md +++ b/.agents/wg/slack-context.md @@ -7,66 +7,41 @@ channels per `.agents/wg/constitution.md` §Information sources and the record: never quote or attribute this content in public output; Slack informs, GitHub decides. -- Generated: 2026-09-07 +- Generated: 2026-11-13 - Window: last 14 days - Channels: 22 public WG channels swept (4 private excluded) --- -### 3.2 Release Readiness and Remaining Open Issues - -- **Status:** active -- **Summary:** The 3.2 milestone is described as feature-complete apart from a few stragglers, including DOOH audio support and a last open issue in the broadcast/syndication track. Experimental tooling for buyer agents as stateful principals is being introduced as a first for the protocol, alongside merged reporting pipeline work marked experimental. A release-candidate build cycle across the spec and SDKs is underway, with cross-version/cross-language checks causing delays; once ready, the training agent and the Interchange environment will be bumped to 3.2 to enable live traffic testing. -- **Related:** #5878 -- **Thread:** https://agenticads.slack.com/archives/C0ACHCU5210/p1788081427834219, https://agenticads.slack.com/archives/C09BK148CLU/p1788120684328569, https://agenticads.slack.com/archives/C09BK148CLU/p1788268365763459, https://agenticads.slack.com/archives/C09BK148CLU/p1788630892701959 - -### DOOH Schema Support (Broadcast/Syndication and Campaign Lifecycle) - -- **Status:** active -- **Summary:** A pull request adding DOOH-related schema changes is seeking additional review, with outreach underway to bring in more DOOH-focused participants, including contacts at a major DOOH sell-side vendor, to weigh in before the current cycle closes. Separate feedback on DOOH from a working group member has spawned follow-up PRs, one of which is still awaiting review. -- **Related:** #5623, #7177 -- **Thread:** https://agenticads.slack.com/archives/C0ACHCU5210/p1787582147291599, https://agenticads.slack.com/archives/C0ACHCU5210/p1787687143020649, https://agenticads.slack.com/archives/C09BK148CLU/p1788398512662769 - -### Delta Sharing / RFC 6540 and Reporting Pipelines - -- **Status:** active -- **Summary:** A contributor followed up on the delta-sharing component of RFC 6540, asking whether it remains a 3.2 milestone item and flagging that an associated PR appears unblocked with changes aligned to their recommended solution. Related work on reliable reporting pipelines, including support for delivery via Databricks, Snowflake, and cloud buckets, has an RFC and implementation PR open. A further PR proposes moving property reporting from the 3.3 milestone into 3.2, which is considered necessary and is awaiting working-group review. -- **Related:** #6857, #6911, #6953, #6915 -- **Thread:** https://agenticads.slack.com/archives/C09BK148CLU/p1787750898081669, https://agenticads.slack.com/archives/C09BK148CLU/p1787886708854929, https://agenticads.slack.com/archives/C09BK148CLU/p1787828881454989 - -### FAST Channel Modeling in adagents.json / Property Schema - -- **Status:** active -- **Summary:** A detailed governance-channel proposal distinguishes "property" (the host CTV app), "collection" (the independently owned FAST channel), and "placement" (the ad position), suggesting FAST channel owners declare canonical collection identity (including Gracenote IDs and platform distributions) in their own adagents.json, while hosts attest sales rights by authorizing the owner's agent without declaring placements. A separate detailed question raises gaps in the current schema (3.1.15): there is no property_type value for channels carried inside third-party CTV apps, no way to express industry-standard channel identifiers (e.g., Gracenote/TMS IDs, platform EPG channel IDs), and no concept of carriage to represent this distribution model. -- **Thread:** https://agenticads.slack.com/archives/C09NUQS93DF/p1787692753462379, https://agenticads.slack.com/archives/C09NUQS93DF/p1787665044852579 - -### Seller Policy, Change-Right Contracts, and Governance Decision Ratification - +### Campaign-governance doc/spec coherence sweep - **Status:** active -- **Summary:** A governance working group PR adding seller policy and change-right contracts requires that decision memos tied to several linked issues be formally ratified and committed to the governance decisions directory per the RFC process, noting ratification is a human act on the WG memo. Whether linked issues should be marked "Closes" versus "Refs" is left to author discretion pending confirmation that the PR's scope fully resolves each issue. A related issue and implementation PR address giving full visibility into account changes across seller-managed state. -- **Related:** #6794, #6749, #6750, #6757, #6758, #6810, #6811 -- **Thread:** https://agenticads.slack.com/archives/C09NUQS93DF/p1787582062993769 - -### Contextual Embeddings in segment.ext.aa RTB Field +- **Summary:** A read-through of the campaign-governance documentation found that the task, audit-trail and safety-model pages contradict the specification in several places, the spec contradicts its own schemas in a couple, and a number of behaviours every governance agent must implement remain undefined. Examples include inconsistent handling of a budget cut below committed spend, audit mode versus mandatory escalation for plans requiring human review, and a schema that rejects an omitted case the prose says agents should accept. Issues were filed on the spec repo and the Python SDK repo following a working-group conversation. The thread drew a substantial number of replies. +- **Related:** #8733 +- **Thread:** https://agenticads.slack.com/archives/C09NUQS93DF/p1793805096456139 +### 3.3 GA decisions and versioning rules - **Status:** active -- **Summary:** A member raised a question about which models are used or recommended when sending contextual embeddings over the `segment.ext.aa` RTB field, noting prior groundwork but asking whether any consensus or broader interest has formed as they plan to build platform support for buying partners. -- **Thread:** https://agenticads.slack.com/archives/C09BF378H8A/p1788725186616889 +- **Summary:** The upcoming working-group agenda is mostly devoted to 3.3 GA decisions: status against the GA criteria (SDKs on beta.4, storyboards green, closed-schema triage PRs under review with a consent window closing mid-November). A key decision item is whether to adopt a three-rule versioning policy for the rest of 3.x and all of 4.x, including that a minor release only adds and only to open schemas. A concession was posted in response to an on-record objection to making cross-release translation in SDKs normative. The final portion of the session opens discussion of 4.0. +- **Related:** #8600, #8501, #8519, #8704 +- **Thread:** https://agenticads.slack.com/archives/C09BK148CLU/p1793989289197729 -### AdCP SDK (adcp-go) CI and Review Backlog +### 3.3.0-beta.3 release contents +- **Status:** resolved +- **Summary:** The 3.3.0-beta.3 release was announced with experimental additions across accounts (account identity simplified, a new approval-flow request, invoice lines), buys (seller-offered changes to live buys, price adjustment tables, installments, execution readiness), creative (live updates under a stable ID with staged review), signals, reporting and inventory. Interoperability changes include a protocol envelope on every response, closed schemas staying closed within 3.x with CI enforcement, and bounded capabilities. Several items (definition pins, purchase rights, installments) were withdrawn and planned for 4.0. +- **Thread:** https://agenticads.slack.com/archives/C09BK148CLU/p1793456118493969 +### Averaged daily spend target acceptance matrix - **Status:** active -- **Summary:** A contributor reported a failing GitHub Action affecting all adcp-go pull requests and requested help diagnosing it, along with reviews on a backlog of pending SDK PRs. -- **Thread:** https://agenticads.slack.com/archives/C09J28K9K29/p1788480742718759 - -### llms.txt Documentation Structure Change +- **Summary:** A contributor proposed drafting a small acceptance matrix covering discovery through authorization and readback for replacing a hard daily cap with an averaged target. The proposal suggests preserving the existing constraint-relaxation rules and making the accepted averaging window and timezone explicit on readback. The contributor asked whether this slice would be useful. +- **Related:** #8685 +- **Thread:** https://agenticads.slack.com/archives/C09BK148CLU/p1793645362619399 +### Beta SDK capability-discovery version pinning - **Status:** active -- **Summary:** A structural change to docs.adcontextprotocol.org/llms.txt was flagged as likely to break tooling that assumes a flat, single-version index. The file is now a multi-version hub whose flat entries are archived 2.5.x docs, with current-release content behind per-version sub-indexes (3-1, 3-2-beta, 3-0) and no "latest" alias; the reliable way to find current docs is via stable paths that redirect to the active build. The message also notes the hub includes OpenAPI YAML links and cross-origin GitHub raw links that consumers should be aware of. -- **Thread:** https://agenticads.slack.com/archives/C09J28K9K29/p1788451422017619 - -### Docs Site Availability Issue +- **Summary:** A beta-based reader pinned its capabilities call to a prerelease version and, when the seller correctly returned a version-unsupported error listing only stable versions, failed outright instead of retrying unpinned. The 3.3 beta guidance says prerelease pins should only be sent to peers advertising that exact value and never negotiate down, with the buyer expected to retry unpinned on that error; the stable SDK reportedly does this. The thread also notes that capability discovery is expected to be readable without credentials, which matters for sellers who lock down authentication. +- **Thread:** https://agenticads.slack.com/archives/C09J28K9K29/p1794418915773829 +### Synthetic population-model alternative to ID-based audience matching - **Status:** parked -- **Summary:** A member reported that the docs site (docs.adcontextprotocol.org) appeared to be down, redirecting to an unrelated auto-redirect landing page, though no resolution was recorded in the thread. -- **Thread:** https://agenticads.slack.com/archives/C09J28K9K29/p1788159845297419 +- **Summary:** A member proposed exploring a fully synthetic approach in which the buy side plans on a large population model and passes virtual IDs to the sell side, which maps its audiences to them, avoiding match-rate and consent-state problems. A neutral third party could supply the model, with others enriching attributes. A follow-up supported the idea of planning cross-media reach and frequency on such a model independent of media currency and suggested it as a working-group topic. +- **Thread:** https://agenticads.slack.com/archives/C09BF378H8A/p1793902771260599, https://agenticads.slack.com/archives/C09BF378H8A/p1793913489046689