@adcp/sdk 6.13.2 → 6.15.0

package/examples/hello_seller_adapter_proposal_mode.ts

@@ -529,6 +529,13 @@ const platform: DecisioningPlatform<unknown, NetworkMeta> = {
     channels: ['olv', 'ctv', 'display'],
     pricingModels: ['cpm'],
     config: undefined,
+    // Declare the comply_test_controller surface so the conformance runner
+    // grades missing scenarios as `not_applicable` rather than `failed`. The
+    // framework auto-derives the `scenarios` list from the `complyTest`
+    // adapter set wired below.
+    compliance_testing: {
+      scenarios: ['force_media_buy_status', 'simulate_delivery'],
+    },
   },
   accounts,
   proposalManager,
@@ -544,6 +551,21 @@ const proposalStore = new InMemoryProposalStore<GAMLikeRecipe>();
 const stateStore = new InMemoryStateStore();
 const mediaBuyStore = createMediaBuyStore({ store: stateStore });
 
+// ─── TEST-ONLY: in-memory state for comply_test_controller adapters ─────
+// DELETE THESE MAPS BEFORE DEPLOYING (or scope per-tenant if you keep the
+// controller wired in a sandbox tenant). Module-scope shared maps leak
+// state across accounts — that's fine for a worked example whose only
+// caller is the conformance harness, but unacceptable in production.
+// SWAP: scope by `account.id` (or your tenant key) and persist via the
+// same data layer your production handlers read from. The controller
+// and production tools should share one source of truth for state.
+const seededMediaBuys = new Map<string, { status: string; revision: number }>();
+const simulatedDelivery = new Map<
+  string,
+  { impressions: number; clicks: number; reported_spend: { amount: number; currency: string } }
+>();
+// ─── /TEST-ONLY ──────────────────────────────────────────────────────────
+
 serve(
   ({ taskStore }) =>
     createAdcpServerFromPlatform(platform, {
@@ -559,6 +581,55 @@ serve(
         const acct = ctx.account as Account<NetworkMeta> | undefined;
         return acct?.id ?? 'anonymous';
       },
+      // ─── TEST-ONLY: comply_test_controller wiring ──────────────────────
+      // DELETE THIS BLOCK BEFORE DEPLOYING. The conformance runner uses
+      // `comply_test_controller` to seed media-buy fixtures and force
+      // state transitions across cascade scenarios in the broader
+      // `sales_proposal_mode` storyboard suite (delivery_reporting,
+      // invalid_transitions, pending_creatives_to_start). The
+      // `proposal_finalize` storyboard itself doesn't invoke the
+      // controller, but the surface is wired here for parity with the
+      // other reference seller adapters.
+      //
+      // No `sandboxGate` here — the framework gate inside
+      // `createAdcpServerFromPlatform` admits via the resolved account's
+      // `mode === 'sandbox'`. Production refs flow through the live path
+      // with the field unset (default `'live'`), so the framework gate
+      // refuses dispatch for them.
+      complyTest: {
+        seed: {
+          media_buy: ({ media_buy_id, fixture }) => {
+            const existing = seededMediaBuys.get(media_buy_id);
+            const status = typeof fixture['status'] === 'string' ? (fixture['status'] as string) : 'pending_creatives';
+            seededMediaBuys.set(media_buy_id, { status, revision: existing?.revision ?? 0 });
+          },
+        },
+        force: {
+          media_buy_status: ({ media_buy_id, status, rejection_reason }) => {
+            const buy = seededMediaBuys.get(media_buy_id);
+            const previous = buy?.status ?? 'pending_creatives';
+            seededMediaBuys.set(media_buy_id, { status, revision: (buy?.revision ?? 0) + 1 });
+            void rejection_reason;
+            return { success: true, previous_state: previous, current_state: status };
+          },
+        },
+        simulate: {
+          delivery: ({ media_buy_id, impressions, clicks, reported_spend }) => {
+            const prev = simulatedDelivery.get(media_buy_id) ?? {
+              impressions: 0,
+              clicks: 0,
+              reported_spend: { amount: 0, currency: 'USD' },
+            };
+            simulatedDelivery.set(media_buy_id, {
+              impressions: prev.impressions + (impressions ?? 0),
+              clicks: prev.clicks + (clicks ?? 0),
+              reported_spend: reported_spend ?? prev.reported_spend,
+            });
+            return { success: true, simulated: { media_buy_id, impressions, clicks, reported_spend } };
+          },
+        },
+      },
+      // ─── /TEST-ONLY ──────────────────────────────────────────────────
     }),
   {
     port: PORT,

package/examples/hello_signals_adapter_marketplace.ts

@@ -36,6 +36,7 @@ import {
   type CachedBuyerAgentRegistry,
 } from '@adcp/sdk/server';
 import type { GetSignalsResponse, ActivateSignalRequest, ActivateSignalSuccess } from '@adcp/sdk/types';
+import { activationKey, signalId } from '@adcp/sdk';
 import { createUpstreamRecorder, toQueryUpstreamTrafficResponse } from '@adcp/sdk/upstream-recorder';
 import { createHash, randomUUID } from 'node:crypto';
 
@@ -292,11 +293,10 @@ function toAdcpSignal(c: UpstreamCohort): GetSignalsResponse['signals'][number]
   const coverage = c.total_universe > 0 ? Math.round((c.member_count / c.total_universe) * 100) : 0;
   return {
     signal_agent_segment_id: c.cohort_id,
-    signal_id: {
-      source: 'catalog',
+    signal_id: signalId.catalog({
       data_provider_domain: c.data_provider_domain,
       id: c.data_provider_id,
-    },
+    }),
     name: c.name,
     description: c.description,
     value_type: c.value_type,
@@ -449,18 +449,16 @@ class SignalMarketplaceAdapter implements DecisioningPlatform<Record<string, nev
               client_request_id: `${idempotency}.${i}`,
             });
             if (dest.type === 'agent') {
-              // ActivationKey oneOf — for `type: 'key_value'`, `key` and `value`
-              // sit at the TOP level (not nested under a `key_value` field).
-              // `value` MUST be string. See skills/SHAPE-GOTCHAS.md §1.
+              // `activationKey.keyValue({...})` injects `type: 'key_value'`
+              // and accepts the flat `{ key, value }` shape. SHAPE-GOTCHAS §1.
               return {
                 type: 'agent' as const,
                 agent_url: dest.agent_url,
                 is_live: true,
-                activation_key: {
-                  type: 'key_value' as const,
+                activation_key: activationKey.keyValue({
                   key: 'agent_segment',
                   value: activation.agent_activation_key?.agent_segment ?? activation.activation_id,
-                },
+                }),
                 deployed_at: new Date().toISOString(),
               };
             }
@@ -468,10 +466,9 @@ class SignalMarketplaceAdapter implements DecisioningPlatform<Record<string, nev
               type: 'platform' as const,
               platform: dest.platform,
               is_live: false,
-              activation_key: {
-                type: 'segment_id' as const,
+              activation_key: activationKey.segment({
                 segment_id: activation.segment_id ?? activation.activation_id,
-              },
+              }),
               estimated_activation_duration_minutes: 30,
             };
           })

package/examples/signals-agent.ts

@@ -18,6 +18,7 @@
 
 import { createAdcpServer, serve } from '@adcp/sdk/server/legacy/v5';
 import { createIdempotencyStore, memoryBackend } from '@adcp/sdk/server';
+import { activationKey, signalId } from '@adcp/sdk';
 import type { GetSignalsResponse, ServeContext } from '@adcp/sdk';
 
 // ---------------------------------------------------------------------------
@@ -28,11 +29,10 @@ type Signal = GetSignalsResponse['signals'][number];
 const SEGMENTS: Signal[] = [
   {
     signal_agent_segment_id: 'high_intent_shoppers',
-    signal_id: {
-      source: 'catalog',
+    signal_id: signalId.catalog({
       data_provider_domain: 'example-signals.com',
       id: 'high_intent_shoppers',
-    },
+    }),
     name: 'High Intent Shoppers',
     description: 'Users who visited product pages 3+ times in the last 7 days without purchasing.',
     value_type: 'binary',
@@ -51,11 +51,10 @@ const SEGMENTS: Signal[] = [
   },
   {
     signal_agent_segment_id: 'lapsed_subscribers',
-    signal_id: {
-      source: 'catalog',
+    signal_id: signalId.catalog({
       data_provider_domain: 'example-signals.com',
       id: 'lapsed_subscribers',
-    },
+    }),
     name: 'Lapsed Subscribers',
     description: 'Email subscribers who have not opened in 90+ days but previously had high engagement.',
     value_type: 'binary',
@@ -74,11 +73,10 @@ const SEGMENTS: Signal[] = [
   },
   {
     signal_agent_segment_id: 'geo_urban_commuters',
-    signal_id: {
-      source: 'catalog',
+    signal_id: signalId.catalog({
       data_provider_domain: 'example-signals.com',
       id: 'geo_urban_commuters',
-    },
+    }),
     name: 'Urban Commuters',
     description: 'Users whose location data indicates daily commute patterns through major metro areas.',
     value_type: 'binary',
@@ -171,21 +169,19 @@ function createSignalsAgent({ taskStore }: ServeContext) {
               platform: dest.platform,
               is_live: false,
               estimated_activation_duration_minutes: 30,
-              activation_key: {
-                type: 'segment_id' as const,
+              activation_key: activationKey.segment({
                 segment_id: `${dest.platform}_${params.signal_agent_segment_id}`,
-              },
+              }),
             };
           }
           return {
             type: 'agent' as const,
             agent_url: dest.agent_url,
             is_live: true,
-            activation_key: {
-              type: 'key_value' as const,
+            activation_key: activationKey.keyValue({
               key: 'audience',
               value: params.signal_agent_segment_id,
-            },
+            }),
             deployed_at: new Date().toISOString(),
           };
         });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adcp/sdk",
-  "version": "6.13.2",
+  "version": "6.15.0",
   "description": "AdCP SDK — client, server, and compliance harnesses for the AdContext Protocol (MCP + A2A)",
   "workspaces": [
     ".",
@@ -361,5 +361,5 @@
     },
     "minimatch": "^10.2.1"
   },
-  "adcp_version": "3.0.6"
+  "adcp_version": "3.0.8"
 }

package/skills/SHAPE-GOTCHAS.md

@@ -10,7 +10,7 @@ Six patterns surfaced repeatedly while building reference adapters (`examples/he
 
 When returning `activate_signal` deployments with `type: 'key_value'` activation keys, `key` and `value` sit at the TOP level of `activation_key`. NOT nested under a `key_value` sub-field.
 
-✗ Wrong (intuitive — the discriminator name *suggests* nesting):
+✗ Wrong (intuitive — the discriminator name _suggests_ nesting):
 
 ```ts
 activation_key: {
@@ -37,6 +37,17 @@ activation_key: { type: 'segment_id', segment_id: 'plat_seg_xyz' }
 
 — same flatness, single string ID under the discriminator.
 
+**Prevent at write time:** import `activationKey` from `@adcp/sdk`. The
+typed factory injects the `type` discriminator and accepts the flat shape:
+
+```ts
+activation_key: activationKey.keyValue({ key: 'segment', value: 'abc123' });
+activation_key: activationKey.segment({ segment_id: 'plat_seg_xyz' });
+```
+
+The nested-`key_value` mistake doesn't typecheck — `activationKey.keyValue`
+takes `{ key, value }`, not `{ key_value: {...} }`.
+
 ---
 
 ## 2. `signal_ids` is `signal_id[]` (provenance objects), not `string[]`
@@ -46,7 +57,9 @@ activation_key: { type: 'segment_id', segment_id: 'plat_seg_xyz' }
 ✗ Wrong:
 
 ```ts
-{ signal_ids: ['cohort_abc', 'cohort_xyz'] }
+{
+  signal_ids: ['cohort_abc', 'cohort_xyz'];
+}
 ```
 
 ✓ Right (matches `/schemas/3.0/core/signal-id.json`):
@@ -62,11 +75,23 @@ activation_key: { type: 'segment_id', segment_id: 'plat_seg_xyz' }
 
 `SignalID` is a discriminated union: `source: 'catalog'` (with `data_provider_domain` + `id`) or `source: 'agent'` (with `agent_url` + `id`). When implementing the filter on the seller side, narrow on `source` before reading `data_provider_domain` — only the catalog variant has it.
 
+**Prevent at write time:** import `signalId` from `@adcp/sdk`. The typed
+factory injects the `source` discriminator and only takes the fields the
+selected variant requires:
+
+```ts
+signalId.catalog({ data_provider_domain: 'tridentauto.example', id: 'likely_ev_buyers' });
+signalId.agent({ agent_url: 'https://liveramp.com/.well-known/adcp/signals', id: 'custom_auto_intenders' });
+```
+
+A bare-string `signal_ids` filter is rejected by the request type as soon
+as you stop typing it as `any`.
+
 ---
 
 ## 3. `VASTAsset` requires an embedded `delivery_type` discriminator
 
-`asset_type: 'vast'` is itself a discriminator at the asset level. A *second* discriminator (`delivery_type`) picks between inline VAST XML and a redirect URL. Both are required; you can't pass `content` or `vast_url` without `delivery_type`.
+`asset_type: 'vast'` is itself a discriminator at the asset level. A _second_ discriminator (`delivery_type`) picks between inline VAST XML and a redirect URL. Both are required; you can't pass `content` or `vast_url` without `delivery_type`.
 
 ✗ Wrong (flat `content` without `delivery_type`):
 
@@ -125,6 +150,28 @@ Same pattern applies to `DAASTAsset` (audio).
 
 Each `PreviewRender` requires `render_id`, `output_format: 'url'` (or `'inline_html'`), `preview_url`, and `role`. Don't omit `role` — the validator requires it.
 
+**Prevent at write time:** import `previewCreative` from
+`@adcp/sdk`. The typed factory injects the `response_type` discriminator
+and pairs naturally with `urlRender({...})` / `htmlRender({...})` /
+`bothRender({...})` for the per-render `output_format`:
+
+```ts
+previewCreative.single({
+  previews: [
+    {
+      preview_id: 'prv_abc',
+      renders: [urlRender({ render_id: 'rnd_1', preview_url: 'https://...', role: 'primary' })],
+      input: { name: 'default' },
+    },
+  ],
+  expires_at: '2026-05-03T00:00:00Z',
+});
+previewCreative.batch({ results: [...] });
+previewCreative.variant({ variant_id, creative_id, previews });
+```
+
+A flat `{ preview: {...} }` shape doesn't typecheck.
+
 ---
 
 ## 5. `BuildCreativeReturn` has 4 valid shapes — framework auto-wraps the bare manifest
@@ -133,13 +180,13 @@ Each `PreviewRender` requires `render_id`, `output_format: 'url'` (or `'inline_h
 
 ```ts
 type BuildCreativeReturn =
-  | CreativeManifest                    // bare single — framework wraps as { creative_manifest: <obj> }
-  | CreativeManifest[]                  // bare multi  — framework wraps as { creative_manifests: <arr> }
-  | BuildCreativeSuccess                // shaped single — passthrough; you set sandbox/expires_at/preview
-  | BuildCreativeMultiSuccess           // shaped multi  — passthrough
+  | CreativeManifest // bare single — framework wraps as { creative_manifest: <obj> }
+  | CreativeManifest[] // bare multi  — framework wraps as { creative_manifests: <arr> }
+  | BuildCreativeSuccess // shaped single — passthrough; you set sandbox/expires_at/preview
+  | BuildCreativeMultiSuccess; // shaped multi  — passthrough
 ```
 
-Easy mistake: return a bare `CreativeManifest` and confirm the response *seems* fine via tests that read `response.format_id` directly. The wire shape after framework wrapping is `response.creative_manifest.format_id` — a level deeper. Storyboards check the wire path; if you didn't go through the framework wrapper in your test, the storyboard will surface "field missing at `creative_manifest.format_id`" while your local test passes.
+Easy mistake: return a bare `CreativeManifest` and confirm the response _seems_ fine via tests that read `response.format_id` directly. The wire shape after framework wrapping is `response.creative_manifest.format_id` — a level deeper. Storyboards check the wire path; if you didn't go through the framework wrapper in your test, the storyboard will surface "field missing at `creative_manifest.format_id`" while your local test passes.
 
 If you need to set `sandbox: true` or attach `preview` previews, return the shaped envelope directly:
 
@@ -151,16 +198,29 @@ return {
 };
 ```
 
+**Prevent at write time:** import `buildCreativeReturn` from `@adcp/sdk`.
+The typed factory pins which arm of the 4-shape union you're emitting and
+handles the singular/plural manifest-field rename for the shaped envelopes:
+
+```ts
+return buildCreativeReturn.single(manifest); // bare — framework wraps as { creative_manifest }
+return buildCreativeReturn.multi(manifests); // bare — framework wraps as { creative_manifests }
+return buildCreativeReturn.singleEnveloped({ manifest, sandbox: true, expires_at });
+return buildCreativeReturn.multiEnveloped({ manifests, sandbox: true });
+```
+
+Mixing `manifest` / `manifests` arms doesn't typecheck.
+
 ---
 
 ## 6. `log_event` projection for walled-garden CAPIs
 
 Sales-social adopters fronting walled-garden conversion APIs translate AdCP's `log_event` wire shape onto the upstream CAPI's. Three projections trip every walled-garden integration on the first pass — the upstream returns `400` and the AdCP wire surface gives no hint that the field name or encoding was the problem.
 
-| AdCP wire (`Event`)                                                            | Walled-garden CAPI                                                                          | Translation                                                                  |
-| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
-| `event_type` (string)                                                          | `event_name` (string)                                                                       | rename on the way out                                                        |
-| `event_time` (ISO 8601 string)                                                 | `event_time` (UNIX seconds, number)                                                         | `Math.floor(new Date(t).getTime() / 1000)`                                   |
+| AdCP wire (`Event`)                                                                                      | Walled-garden CAPI                                                       | Translation                                                                  |
+| -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------- |
+| `event_type` (string)                                                                                    | `event_name` (string)                                                    | rename on the way out                                                        |
+| `event_time` (ISO 8601 string)                                                                           | `event_time` (UNIX seconds, number)                                      | `Math.floor(new Date(t).getTime() / 1000)`                                   |
 | `user_match` (`hashed_email` / `hashed_phone` / `uids[]` / `click_id` / `client_ip`+`client_user_agent`) | `user_data.{email_sha256,phone_sha256,external_id_sha256}` (≥1 required) | map per the upstream's identifier types; drop events with empty `user_match` |
 
 ### 6.1 `event_name`, not `event_type`
@@ -187,13 +247,17 @@ upstream.trackEvents({
 ✗ Wrong:
 
 ```ts
-{ event_time: e.event_time }                 // '2026-04-05T14:30:00Z'
+{
+  event_time: e.event_time;
+} // '2026-04-05T14:30:00Z'
 ```
 
 ✓ Right:
 
 ```ts
-{ event_time: Math.floor(new Date(e.event_time).getTime() / 1000) }
+{
+  event_time: Math.floor(new Date(e.event_time).getTime() / 1000);
+}
 ```
 
 ### 6.3 Hashed-identifier requirement — read `Event.user_match`, drop on empty
@@ -221,11 +285,11 @@ The `examples/hello_seller_adapter_social.ts` reference adapter codifies all thr
 
 The spec definitions:
 
-| Value | Use when | Example adopter |
-| --- | --- | --- |
-| `marketplace` | Resold third-party segments. Provider's authorization is verifiable via their `adagents.json`. | LiveRamp marketplace; Oracle Data Cloud catalog; reseller of third-party panels |
-| `owned` | First-party segments derived from data the signal agent **directly owns**. | Retailer purchase data (Kroger 84.51°, Walmart Connect); publisher behavioral data (NYT subscribers); telco data |
-| `custom` | Agent-native segment built **on demand** from models, composites, or buyer inputs. Not attributable to a standing upstream provider. | Contextual classifier you train per-request; lookalike model output computed from a buyer's seed audience |
+| Value         | Use when                                                                                                                             | Example adopter                                                                                                  |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- |
+| `marketplace` | Resold third-party segments. Provider's authorization is verifiable via their `adagents.json`.                                       | LiveRamp marketplace; Oracle Data Cloud catalog; reseller of third-party panels                                  |
+| `owned`       | First-party segments derived from data the signal agent **directly owns**.                                                           | Retailer purchase data (Kroger 84.51°, Walmart Connect); publisher behavioral data (NYT subscribers); telco data |
+| `custom`      | Agent-native segment built **on demand** from models, composites, or buyer inputs. Not attributable to a standing upstream provider. | Contextual classifier you train per-request; lookalike model output computed from a buyer's seed audience        |
 
 **`owned` is the default for first-party data agents.** Most non-marketplace adopters mis-classify their segments as `custom` because the segment was "built" — but the test is provenance, not lifecycle. If you can point at a stable data-asset you own (a customer table, a pixel, a panel), it's `owned`. `custom` is reserved for segments that don't have a standing data asset behind them — the agent computed them per-call.
 

package/skills/build-creative-agent/SKILL.md

@@ -9,16 +9,18 @@ A creative agent accepts assets from buyers, stores or transforms them, and retu
 
 ## Pick your fork target
 
-Three creative archetypes; two have dedicated worked adapters, the third lives in `build-generative-seller-agent` because it's coupled with selling inventory.
+Three creative archetypes. Two have dedicated worked adapters; the third (`creative-generative`) reuses the template adapter and applies brief-to-creative deltas.
 
-| Specialism | Archetype | Fork this | Mock upstream | Storyboard |
-| --- | --- | --- | --- | --- |
-| `creative-ad-server` | Stateful library, pricing + billing (Innovid, Flashtalking, CM360, GAM-creative) | [`hello_creative_adapter_ad_server.ts`](../../examples/hello_creative_adapter_ad_server.ts) | `npx adcp mock-server creative-ad-server` | `creative_ad_server` |
-| `creative-template` | Stateless transform from inline manifest (Celtra, AudioStack, ElevenLabs, Resemble) | [`hello_creative_adapter_template.ts`](../../examples/hello_creative_adapter_template.ts) | `npx adcp mock-server creative-template` | `creative_template` |
-| `creative-generative` | Brief-to-creative generation (AI ad networks coupled with sales) | → `skills/build-generative-seller-agent/` | — | `creative_generative` |
+| Specialism            | Archetype                                                                               | Fork this                                                                                      | Mock upstream                             | Storyboard            |
+| --------------------- | --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | ----------------------------------------- | --------------------- |
+| `creative-ad-server`  | Stateful library, pricing + billing (Innovid, Flashtalking, CM360, GAM-creative)        | [`hello_creative_adapter_ad_server.ts`](../../examples/hello_creative_adapter_ad_server.ts)    | `npx adcp mock-server creative-ad-server` | `creative_ad_server`  |
+| `creative-template`   | Stateless transform from inline manifest (Celtra, AudioStack, ElevenLabs, Resemble)     | [`hello_creative_adapter_template.ts`](../../examples/hello_creative_adapter_template.ts)      | `npx adcp mock-server creative-template`  | `creative_template`   |
+| `creative-generative` | Brief-to-creative generation (standalone generative platform; not coupled with selling) | Same — fork the template adapter and apply the [generative deltas below](#creative-generative) | Same                                      | `creative_generative` |
 
 The `interaction_model` in each specialism's `index.yaml` is the forcing function: `stateful_ad_server`, `stateless_transform`, `stateless_generate`. Decide which one matches your business, then fork the adapter for that row.
 
+> **Coupling generation with selling inventory?** That's the AI-ad-network shape (e.g., generative DSPs that sell programmatic inventory and generate the creative). See [`skills/build-generative-seller-agent/`](../build-generative-seller-agent/SKILL.md) — combine `sales-non-guaranteed` + `creative-generative`.
+
 For exact response shapes, error codes, and optional fields, `docs/llms.txt` is the canonical reference. The fork target stays in sync with the spec because PR #1394's three-gate contract fails CI when it drifts.
 
 ## When to use this skill
@@ -29,7 +31,7 @@ For exact response shapes, error codes, and optional fields, `docs/llms.txt` is
 **Not this skill:**
 
 - Brief-to-creative generation coupled with selling inventory (AI ad network) → `skills/build-generative-seller-agent/`
-- Publisher creative service that pairs with selling — usually a `build-seller-agent` adopter that omits a creative-* specialism claim
+- Publisher creative service that pairs with selling — usually a `build-seller-agent` adopter that omits a creative-\* specialism claim
 
 ## Cross-cutting rules
 
@@ -90,7 +92,20 @@ curl -H 'Authorization: Bearer mock_creative_template_key_do_not_use_in_prod' \
 # Final: { ..., "status": "complete", "output": { "audio_url": "….mp3", "preview_url": "...", "assets": [{ "kind": "audio_url", "mime_type": "audio/mpeg" }] } }
 ```
 
-**`creative-generative`** — generate from `message` + `brand.domain`; honor `quality: draft|production`; support refinement (re-send manifest in). Goes through `skills/build-generative-seller-agent/` because it's coupled with selling inventory.
+### `creative-generative`
+
+Forking [`hello_creative_adapter_template.ts`](../../examples/hello_creative_adapter_template.ts) for a `creative-generative` agent? Apply these deltas — the template adapter already handles the stateless `build_creative` flow, manifest projection, and async render polling. Generative just changes the **input semantics** (brief, not template inputs) and adds brand resolution.
+
+- **`build_creative` accepts `message` + `brand.domain`** — no `template_id`, no slot inputs. Treat `message` as the creative brief and `brand.domain` as the brand identity.
+- **Honor `quality: draft|production`** — drafts are cheap/fast (lower-quality model, no human review); production goes through full safety + brand checks.
+- **Refinement loop** — buyers re-send the prior `creative_manifest` plus a new `message` to iterate. Detect "iterating on this manifest" by manifest-id presence and route to your refine endpoint instead of generate.
+- **Brand resolution via `sync_accounts`** — buyers sync an account with `brand.domain`; treat that domain as resolvable for subsequent `build_creative` calls. Don't hardcode a brand allowlist; storyboards use fictional `.example` TLD brands.
+- **Response shape stays the same** — `{ creative_manifest: { format_id, assets } }`, **not** `{ creative_id, status, preview_url }` (those are `sync_creatives` fields).
+- **Delete the template-input slot validation** in the template adapter's `build_creative` handler — generative agents accept free-form briefs and can't validate slot presence/types up front.
+
+The `creative_generative` storyboard exercises the same async render contract as `creative_template` — `build_creative` returns a render id, the buyer polls until status flips to complete. The template adapter's polling pattern transfers verbatim.
+
+If your platform also sells inventory (AI ad network), claim both `sales-non-guaranteed` + `creative-generative` and see [`../build-generative-seller-agent/`](../build-generative-seller-agent/SKILL.md) for the combined wiring.
 
 ## Validate locally
 

package/skills/build-decisioning-creative-template/SKILL.md

@@ -1,28 +1,28 @@
 ---
 name: build-decisioning-creative-template
-description: Build an AdCP v6.0 creative-template decisioning platform — a stateless creative transform service (TTS, watermarking, format conversion, template fill). Use when the user wants the v6.0 DecisioningPlatform shape; for the lower-level handler-bag API, use `build-creative-agent` instead.
+description: Build an AdCP creative-template decisioning platform — a stateless creative transform service (TTS, watermarking, format conversion, template fill). Use when the user wants the typed `DecisioningPlatform` shape; for fork-an-adapter starting points, see `build-creative-agent`.
 ---
 
-# Build a Creative-Template Decisioning Platform (v6.0)
+# Build a Creative-Template Decisioning Platform
 
 You're building a **stateless creative transform** service that fits the AdCP `creative-template` specialism: take an input creative manifest + format spec, produce an output creative manifest. No library, no review queue, no persisting state. Examples: TTS audio synthesis, image watermarking, video format conversion, template-based ad generation.
 
 ## When this skill applies
 
-- User wants a creative-template service on the **v6.0 DecisioningPlatform** surface
+- User wants a creative-template service against the typed `DecisioningPlatform` surface
 - Specialism: `creative-template` (stateless transform; not `creative-ad-server` which is stateful, not `creative-generative` which is brief-driven — though `creative-template` and `creative-generative` share the same `CreativeBuilderPlatform` interface; pick the specialism ID that matches your behavior)
-- SDK package: `@adcp/sdk` 6.0+
+- SDK package: `@adcp/sdk`
 
 **Wrong skill if:**
 
-- User wants the lower-level handler-bag API → `skills/build-creative-agent/`
+- User wants to fork a worked adapter → `skills/build-creative-agent/`
 - User wants stateful creative library/ad-server → `skills/build-creative-agent/` § creative-ad-server
 - User wants brief-to-creative generation → same skill as this one (Builder covers both); declare `'creative-generative'` instead of `'creative-template'`
 - User wants to sell media inventory → `skills/build-seller-agent/`
 
 ## The whole shape (read this first)
 
-A v6.0 creative-template platform is a **single class** implementing `DecisioningPlatform` with a `creative` field of type `CreativeBuilderPlatform`. The framework dispatches each tool call to the right method. (`CreativeTemplatePlatform` and `CreativeGenerativePlatform` are deprecated aliases of `CreativeBuilderPlatform` for source compat.)
+A creative-template platform is a **single class** implementing `DecisioningPlatform` with a `creative` field of type `CreativeBuilderPlatform`. The framework dispatches each tool call to the right method. (`CreativeTemplatePlatform` and `CreativeGenerativePlatform` are deprecated aliases of `CreativeBuilderPlatform` for source compat.)
 
 ### Key fact: `CreativeManifest.assets` is a **keyed map**, not an array
 
@@ -406,7 +406,7 @@ serve(() => server, {
 - Wraps each method with `AdcpError`-catch + `submitted`-envelope projection for HITL
 - Returns a `DecisioningAdcpServer` (extends `AdcpServer`) with `getTaskState(taskId)` + `awaitTask(taskId)` for HITL inspection
 
-`serve()` is unchanged from v5.x; it accepts the server and binds HTTP transport for both MCP and A2A.
+`serve()` accepts the server and binds HTTP transport for both MCP and A2A.
 
 ## Capabilities — declare what you support
 
@@ -486,9 +486,7 @@ For HITL platforms, `server.awaitTask(taskId)` settles the background promise; `
 
 ## What NOT to do
 
-❌ **Don't import from `@adcp/sdk/server` for the platform shape.** That's the v5.x handler-style API. Use `@adcp/sdk/server` for v6.0.
-
-❌ **Don't use `ctx.runAsync(...)` or `ctx.startTask(...)`.** Those were in earlier preview drops; they're gone in v2.1. The async story is dual-method (`xxx` vs `xxxTask`), period.
+❌ **Don't use `ctx.runAsync(...)` or `ctx.startTask(...)`.** The async story is dual-method (`xxx` vs `xxxTask`), period.
 
 ❌ **Don't define both `buildCreative` and `buildCreativeTask`.** `validatePlatform()` will throw with a clear diagnostic. Pick one.
 

package/skills/build-decisioning-platform/SKILL.md

@@ -48,7 +48,7 @@ For other agent shapes:
 - **Brand-rights agent:** swap for `BrandRightsPlatform`
 - **Multi-tenant host:** add `createTenantRegistry`
 
-The full export list is in `@adcp/sdk/server`. Many surfaces are marked `@deprecated` (legacy v5 response builders, old MCP task helpers) — your IDE will strikethrough them. Trust the strikethrough.
+The full export list is in `@adcp/sdk/server`. Surfaces marked `@deprecated` will strikethrough in your IDE. Trust the strikethrough — pick from the typed-error catalog above instead.
 
 ## When you need...
 

package/skills/build-decisioning-platform/advanced/REFERENCE.md

@@ -5,13 +5,9 @@ description: Use when building an AdCP seller, creative, or audience agent again
 
 # Build a Decisioning Platform (v6.0)
 
-> **Status: GA.** v6.0 ships under `@adcp/sdk/server` —
-> `createAdcpServerFromPlatform` + `DecisioningPlatform`. The lower-level
-> `createAdcpServer({ mediaBuy: { ... } })` API remains fully supported
-> as the substrate this framework calls into; reach for it when you need
-> fine control over individual handlers or have custom-shaped tools the
-> platform interface doesn't yet model. The handler-bag skill is at
-> `skills/build-seller-agent/`.
+> **Status: GA.** Ships under `@adcp/sdk/server` —
+> `createAdcpServerFromPlatform` + `DecisioningPlatform`. The handler-bag
+> skill (forking a worked adapter) lives at `skills/build-seller-agent/`.
 
 ## Overview
 
@@ -102,7 +98,7 @@ const platform = {
 const server = createAdcpServerFromPlatform(platform, {
   name: 'My Ad Network',
   version: '1.0.0',
-  // Plus standard createAdcpServer options: idempotency, signedRequests,
+  // Plus standard server options: idempotency, signedRequests,
   // webhooks, validation, etc.
 });
 

package/skills/build-decisioning-signal-marketplace/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: build-decisioning-signal-marketplace
-description: Build an AdCP v6.0 (preview) signal-marketplace OR signal-owned decisioning platform — a data provider serving audience signals to buyers. Use ONLY when the user explicitly wants the v6.0 DecisioningPlatform shape; for v5.x handler-style signals agents, use `build-signals-agent` instead.
+description: Build an AdCP signal-marketplace OR signal-owned decisioning platform — a data provider serving audience signals to buyers. Use when the user wants the typed `DecisioningPlatform` shape; for fork-an-adapter starting points, see `build-signals-agent`.
 ---
 
-# Build a Signals Decisioning Platform (v6.0 preview)
+# Build a Signals Decisioning Platform
 
 You're building a **signals data provider** that fits one of two AdCP specialisms:
 
@@ -14,19 +14,19 @@ Both share the same `SignalsPlatform` interface. Pick the specialism that matche
 
 ## When this skill applies
 
-- User wants a signals platform on the **v6.0 DecisioningPlatform** surface (preview, pre-GA)
+- User wants a signals platform on the typed `DecisioningPlatform` surface
 - Specialism: `signal-marketplace` OR `signal-owned`
-- SDK package: `@adcp/sdk` v5.18+ with the `decisioning` preview surface
+- SDK package: `@adcp/sdk`
 
 **Wrong skill if:**
 
-- User wants v5.x handler-style API → `skills/build-signals-agent/`
+- User wants to fork a worked adapter → `skills/build-signals-agent/`
 - User wants creative transforms → `skills/build-decisioning-creative-template/`
 - User wants to sell media inventory → `skills/build-seller-agent/`
 
 ## The whole shape (read this first)
 
-A v6.0 signals platform implements two methods:
+A signals platform implements two methods:
 
 - **`getSignals(req, ctx) → Promise<GetSignalsResponse>`** — sync catalog discovery. Buyer sends filters; you return the matching signals. No async envelope.
 - **`activateSignal(req, ctx) → Promise<ActivateSignalSuccess>`** — sync ack with async lifecycle. Provision the signal onto destination platforms (Snap, Meta, TikTok, etc.); return immediately with `deployments[]` rows in current state (`pending` is valid). Each deployment's eventual `activating` / `deployed` / `failed` flows via `publishStatusChange({ resource_type: 'signal', ... })`.
@@ -229,8 +229,6 @@ console.log(result.structuredContent);
 
 ## What NOT to do
 
-❌ **Don't import from `@adcp/sdk/server` for the platform shape.** Use `@adcp/sdk/server` for v6.0.
-
 ❌ **Don't try to make activateSignal HITL.** The wire response has no `Submitted` arm. Sync ack + `publishStatusChange` is the correct pattern.
 
 ❌ **Don't return error envelopes manually.** Throw `AdcpError`; the framework projects to wire shape.