docs(academy): Track B publisher/SSP on-ramp — B0 module and landing section

.changeset/academy-track-b-publisher-onramp.md

@@ -0,0 +1,6 @@
+---
+---
+
+Add B0 pre-module ("Is Track B right for you?") to the publisher/SSP track with sell-side value prop and role → module mapping table. Add "For Publishers & SSPs" landing section to the Academy overview page. Cross-link from the intro homepage's "Where do you want to start?" section. Closes #2572.
+
+Docs/academy-only change — no protocol schema changes.

.changeset/billing-did-you-mean-lookup-key.md

@@ -0,0 +1,6 @@
+---
+---
+
+Surface `did_you_mean` in Addie billing tool responses when the LLM passes a non-canonical `lookup_key` alias (e.g. `explorer_annual` instead of `aao_membership_explorer_50`). Tighten tool descriptions on `create_payment_link`, `send_invoice`, and `confirm_send_invoice` to explicitly forbid constructing the key from tier name and billing interval. Closes #2550.
+
+Server-side Addie change only — no protocol schema changes.

.changeset/docs-media-buy-lifecycle-page.md

@@ -0,0 +1,6 @@
+---
+---
+
+Add new canonical Media Buy Lifecycle Flow page (`docs/media-buy/media-buys/lifecycle.mdx`) covering the sequenced task flow, full state machine diagram, guaranteed/PG deal IO acceptance path, and creative sync timing. Adds nav entries in both navigation tabs, a link in the quickstart What's next section, and a link from `sales-agent-creative-capabilities.mdx`. Closes #2570.
+
+Docs-only change — no protocol schema changes.

docs.json

@@ -190,6 +190,7 @@
                           "docs/media-buy/product-discovery/collections-and-installments",
                           "docs/media-buy/product-discovery/refinement",
                           "docs/media-buy/media-buys/index",
+                          "docs/media-buy/media-buys/lifecycle",
                           "docs/media-buy/media-buys/optimization-reporting",
                           "docs/media-buy/media-buys/policy-compliance",
                           "docs/media-buy/creatives/index",
@@ -696,6 +697,7 @@
                       "docs/media-buy/product-discovery/collections-and-installments",
                       "docs/media-buy/product-discovery/refinement",
                       "docs/media-buy/media-buys/index",
+                      "docs/media-buy/media-buys/lifecycle",
                       "docs/media-buy/media-buys/optimization-reporting",
                       "docs/media-buy/media-buys/policy-compliance",
                       "docs/media-buy/creatives/index",

docs/creative/sales-agent-creative-capabilities.mdx

@@ -311,3 +311,4 @@ if (managesCreatives) {
 - [Generative Creative](/docs/creative/generative-creative) — Using `build_creative` for AI-powered generation
 - [get_creative_delivery](/docs/creative/task-reference/get_creative_delivery) — Variant-level delivery reporting
 - [get_media_buy_delivery](/docs/media-buy/task-reference/get_media_buy_delivery) — Media buy delivery reporting
+- [Media Buy Lifecycle](/docs/media-buy/media-buys/lifecycle) — State machine, sequenced flow, guaranteed deal IO path, creative sync timing

docs/intro.mdx

@@ -607,6 +607,9 @@ Governance isn't a gate that slows things down. It's the safety net that lets yo
   <Card title="I want to build with AdCP" icon="code" href="/docs/building">
     For platforms, publishers, and developers implementing the protocol
   </Card>
+  <Card title="I'm a publisher or SSP" icon="server" href="/docs/learning/tracks/publisher">
+    Track B: expose your inventory to AI buyer agents. Start with B0 to see if it's the right fit.
+  </Card>
 </CardGroup>
 
 ## Get started

docs/learning/overview.mdx

@@ -84,6 +84,18 @@ Everyone starts here. All three modules are free — no membership required.
 | [A2](/docs/learning/foundations/a2-protocol-architecture) | Your first media buy | 20 min | Yes |
 | [A3](/docs/learning/foundations/a3-ecosystem-governance) | The AdCP landscape | 15 min | Yes |
 
+### For publishers & SSPs
+
+AdCP gives publishers a single endpoint that exposes your product catalog, handles media buy creation, and delivers reporting to AI buyer agents — 24/7, without per-platform API integrations or inbound sales calls. Reach buyers who operate autonomously at programmatic scale while keeping direct deal quality and margins.
+
+If you work on the sell side, Track B is your path. A quick role map: ad ops and yield teams start with B1 (catalog design) and B3 (delivery reporting and signals); revenue and sales teams focus on B1 and B2 (creative specs); engineers should do the full B1–B4 track, which ends with building and validating a real sales agent.
+
+[Publisher / seller track](/docs/learning/tracks/publisher) — or start now:
+
+<Card title="Start B0 with Addie" icon="play" href="https://agenticadvertising.org/chat">
+  "I'd like to start certification module B0."
+</Card>
+
 ### Role tracks (choose your path)
 
 After Basics, choose the track that matches your role. Each track is four modules culminating in a build project.

docs/learning/tracks/publisher.mdx

@@ -17,6 +17,35 @@ Completing this track (plus A1–A3) earns the **AdCP practitioner** credential.
 
 ---
 
+## B0: Is Track B right for you?
+
+**~10 min** | No prerequisite — can be done before A1
+
+AdCP gives publishers a single endpoint that AI buyer agents can use to discover your inventory, negotiate and create media buys, and pull delivery data — without a sales call, a custom API integration, or giving up your direct deal terms. One implementation; always-on access for buyers that operate autonomously.
+
+### Who Track B is for
+
+| Your role | Where to start | Modules that matter most |
+|-----------|---------------|--------------------------|
+| Ad operations / yield manager | B1, then B3 | B1 (catalog design), B3 (delivery reporting, signals) |
+| Sales / revenue | B1, then B2 | B1 (what buyers see), B2 (creative specs) |
+| Engineer / developer | B1 through B4 | Full track — ends with building and validating a real sales agent |
+| Executive / strategist | B0 orientation, then A1–A3 | Track A for protocol and ecosystem context |
+
+If you're not sure whether you need the full track: engineers and ad tech builders should do B1–B4. Anyone else can take B0 with Addie now, then decide.
+
+### What you'll build toward
+
+- B4 is a build project: you create a working sales agent that handles real buyer queries — product discovery, media buy creation, creative specs, and delivery reporting
+- The agent is validated against AdCP storyboards, not just reviewed manually
+- Completing B1–B4 (plus A1–A3) earns the **AdCP practitioner** credential
+
+<Card title="Start B0 with Addie" icon="play" href="https://agenticadvertising.org/chat">
+  "I'd like to start certification module B0."
+</Card>
+
+---
+
 ## B1: Designing your product catalog
 
 **~20 min** | Prerequisite: A3

docs/media-buy/media-buys/lifecycle.mdx

@@ -0,0 +1,170 @@
+---
+title: Media Buy Lifecycle Flow
+description: "Step-by-step sequence from product discovery through delivery, including the guaranteed-deal IO acceptance path and creative sync timing."
+"og:title": "AdCP — Media Buy Lifecycle Flow"
+---
+
+This page is the canonical sequence reference for media buy lifecycle. For conceptual background on the full lifecycle — campaign structure, package model, property targeting, and async operations — see [Media Buy Lifecycle](/docs/media-buy/media-buys/).
+
+## Standard flow
+
+Every media buy follows four steps:
+
+```mermaid
+flowchart TD
+    A[get_products] --> B[create_media_buy]
+    B --> C{initial state}
+    C -->|creatives missing| D[pending_creatives]
+    C -->|creatives present,\nflight not yet started| E[pending_start]
+    C -->|creatives present,\nflight started| F[active]
+    D --> G[sync_creatives]
+    G --> E
+    E --> F
+    F --> H{delivery}
+    H -->|budget exhausted /\ngoal met / flight ended| I[completed]
+    H -->|buyer or seller action| J[paused]
+    J --> F
+```
+
+1. **`get_products`** — discover available inventory matching your brief.
+2. **`create_media_buy`** — submit packages; the seller validates and confirms.
+3. **`sync_creatives`** — assign creative assets to packages that need them.
+4. **Delivery** — the buy enters `active`, accrues impressions, and eventually reaches a terminal state.
+
+## State machine
+
+### Media buy states
+
+| State | Meaning | Terminal? |
+|-------|---------|-----------|
+| `pending_creatives` | Approved; no creatives assigned yet | No |
+| `pending_start` | Creatives assigned; waiting for flight date | No |
+| `active` | Delivering impressions | No |
+| `paused` | Temporarily halted | No |
+| `completed` | Flight ended, goal met, or budget exhausted | Yes |
+| `rejected` | Seller declined the buy | Yes |
+| `canceled` | Buyer or seller terminated before completion | Yes |
+
+<Note>
+`pending_manual` and `pending_permission` are **task-level** statuses — they describe whether the *operation* (e.g., `create_media_buy`) is queued for human review, not the media buy's own state. The media buy enters `pending_creatives`, `pending_start`, or `active` once the operation completes. See [Asynchronous Operations](/docs/media-buy/media-buys/#asynchronous-operations-and-human-in-the-loop).
+</Note>
+
+### Transitions
+
+```mermaid
+stateDiagram-v2
+    [*] --> pending_creatives : create_media_buy\n(no creatives)
+    [*] --> pending_start : create_media_buy\n(creatives present,\nflight future)
+    [*] --> active : create_media_buy\n(creatives present,\nflight started)
+
+    pending_creatives --> pending_start : sync_creatives
+    pending_start --> active : flight date reached
+
+    active --> paused : update_media_buy\n(paused: true)
+    paused --> active : update_media_buy\n(paused: false)
+
+    active --> completed : flight ended /\ngoal met / budget exhausted
+    paused --> completed : flight ended /\ngoal met / budget exhausted
+
+    pending_creatives --> rejected : seller declines
+    pending_start --> rejected : seller declines
+
+    pending_creatives --> canceled : update_media_buy\n(canceled: true)
+    pending_start --> canceled : update_media_buy\n(canceled: true)
+    active --> canceled : update_media_buy\n(canceled: true)
+    paused --> canceled : update_media_buy\n(canceled: true)
+
+    completed --> [*]
+    rejected --> [*]
+    canceled --> [*]
+```
+
+### Discovering valid actions at runtime
+
+Rather than hardcoding the state machine, read `valid_actions` from `get_media_buys`. The seller returns exactly what the buyer can do in the current state:
+
+```json
+{
+  "media_buy_id": "mb_12345",
+  "status": "active",
+  "revision": 3,
+  "valid_actions": ["pause", "cancel", "update_budget", "update_dates", "update_packages", "add_packages", "sync_creatives"]
+}
+```
+
+Always pass `revision` in `update_media_buy` calls. The seller rejects with `CONFLICT` if the revision has changed since your last read.
+
+## Guaranteed / PG deal variation
+
+Products with `delivery_type: "guaranteed"` require contractual commitment before delivery begins. The flow diverges after `create_media_buy`:
+
+```mermaid
+flowchart TD
+    A[get_products\ndelivery_type: guaranteed] --> B[create_media_buy\nwith accountability_terms]
+    B --> C{task status}
+    C -->|IO signing needed| D[submitted\ntask_id returned]
+    C -->|IO pre-signed| E[pending_creatives\nor pending_start]
+    D --> F[IO signed\nout-of-band]
+    F --> E
+    E --> G[sync_creatives\nif needed]
+    G --> H[active — guaranteed delivery]
+    H --> I{performance}
+    I -->|standards met| J[completed]
+    I -->|under-delivery| K[makegood / remediation]
+    K --> J
+```
+
+### What makes a guaranteed buy different
+
+**`accountability_terms` are required** on each package with a guaranteed product. Three fields are required:
+
+- `performance_standards` — viewability, IVT, completion rate, and other thresholds with measurement vendor
+- `measurement_terms` — who counts the billing metric, acceptable variance, and makegood remedies
+- `cancellation_policy` — notice period and cancellation fee for early termination
+
+Omitting any of these on a guaranteed package causes the seller to return `TERMS_REJECTED`.
+
+**IO signing** — `create_media_buy` for a guaranteed product may return task status `submitted` with a `task_id` rather than completing synchronously. This means the seller's system is awaiting insertion order (IO) acceptance. Poll with `tasks/get` or configure a webhook. Once the IO is signed, the completion artifact carries the `media_buy_id` and the media buy enters `pending_creatives` or `pending_start`.
+
+**Makegoods** — if the seller under-delivers against agreed `performance_standards`, they propose a remedy from the `makegood_policy`: `additional_delivery`, `credit`, or `invoice_adjustment`. The buyer accepts or disputes.
+
+<Note>
+A seller who accepts without under-delivering earns a favorable accountability signal. See [Accountability](/docs/media-buy/advanced-topics/accountability) for the full negotiation flow including how buyers can propose non-default terms at `create_media_buy` time.
+</Note>
+
+## Creative sync timing
+
+### When creatives are required
+
+`create_media_buy` accepts inline `creative_assignments` or `creatives` per package. If you supply them at creation time and the flight date has passed, the buy enters `active` directly. If the flight date is in the future, it enters `pending_start`.
+
+If no creatives are assigned at creation, the buy enters `pending_creatives`. Delivery cannot begin until `sync_creatives` is called to assign at least one creative per package.
+
+### The `creative_deadline`
+
+`create_media_buy` returns a `creative_deadline` timestamp on the media buy response. Individual packages may carry their own `creative_deadline`. **Package-level deadlines take precedence over the media buy deadline.** This matters for mixed-channel orders — a print package may have a material deadline days before the digital packages in the same buy.
+
+After the deadline, `sync_creatives` calls for that package return `CREATIVE_REJECTED`. Creative changes are blocked; delivery continues with whatever creatives are currently assigned (or the package remains in `pending_creatives` if none were ever assigned).
+
+```
+Deadline hierarchy:
+  package.creative_deadline  (if present — wins)
+    ↓ else
+  media_buy.creative_deadline
+```
+
+### Effect on creatives when a buy ends
+
+When a media buy reaches `rejected`, `canceled`, or `completed`, creative assignments are released. The creatives themselves are not deleted — they remain in the library with their existing review status and are available for assignment to other media buys.
+
+<Tip>
+Creative library state and creative assignment state are tracked independently. A creative that was assigned to a canceled buy still has whatever review status it earned and can be immediately assigned to a new buy. See [creative state and assignment state](/docs/creative/creative-libraries#creative-state-and-assignment-state-are-separate).
+</Tip>
+
+## See also
+
+- [Media Buy Lifecycle](/docs/media-buy/media-buys/) — full lifecycle reference: campaign structure, package model, async operations
+- [`create_media_buy`](/docs/media-buy/task-reference/create_media_buy) — task reference with request parameters, response shapes, and examples
+- [`sync_creatives`](/docs/creative/task-reference/sync_creatives) — assign and update creative assets on active packages
+- [Accountability](/docs/media-buy/advanced-topics/accountability) — performance standards, measurement terms, makegood resolution
+- [Optimization & Reporting](/docs/media-buy/media-buys/optimization-reporting) — delivery monitoring, dimensional reporting, campaign updates

docs/quickstart.mdx

@@ -299,6 +299,7 @@ console.log(result.data.products);
 - **[Compliance Catalog](/docs/building/compliance-catalog)** — the domains and specialisms an agent can claim, and the storyboards that verify each claim
 - **[MCP integration guide](/docs/building/integration/mcp-guide)** — transport, sessions, auth details
 - **[A2A integration guide](/docs/building/integration/a2a-guide)** — streaming, artifacts, push notifications
+- **[Media Buy Lifecycle](/docs/media-buy/media-buys/lifecycle)** — state machine, sequenced flow, guaranteed deal IO path, creative sync timing
 - **[Task reference](/docs/media-buy/task-reference)** — all available tasks with testable examples
 - **[Error handling](/docs/building/implementation/transport-errors)** — error codes, recovery strategies
 - **[Authentication](/docs/building/integration/authentication)** — production credential setup

server/src/addie/config-version.ts

@@ -28,7 +28,7 @@ import { loadRules } from './rules/index.js';
  * Format: YYYY.MM.N where N is incremented for multiple changes in a month
  * Example: 2025.01.1, 2025.01.2, 2025.02.1
  */
-export const CODE_VERSION = '2026.04.5';
+export const CODE_VERSION = '2026.04.6';
 
 // Types
 export interface ConfigVersion {