@adcp/client 4.22.1 → 4.24.0

package/storyboards/media_buy_guaranteed_approval.yaml

@@ -3,15 +3,11 @@ version: "1.0.0"
 title: "Guaranteed media buy with human IO approval"
 category: media_buy_guaranteed_approval
 summary: "Seller agent that requires human-in-the-loop IO signing before guaranteed media buys go live."
-platform_types:
-  - display_ad_server
-  - video_ad_server
-  - audio_platform
-  - linear_tv_platform
-
 track: media_buy
 required_tools:
+  - get_products
   - create_media_buy
+
 narrative: |
   You run a sell-side platform that requires human approval before guaranteed media buys go
   live. When a buyer creates a guaranteed buy, your platform returns a submitted status with
@@ -20,7 +16,7 @@ narrative: |
 
   The buyer either polls get_media_buys or configures a push_notification_config webhook to
   receive a callback when the IO is signed. Once approved, the media buy transitions from
-  pending_approval to confirmed/active and the buyer can sync creatives and monitor delivery.
+  pending_approval to active and the buyer can sync creatives and monitor delivery.
 
   This storyboard isolates the guaranteed approval path — the async handshake between agent
   automation and human decision-making that makes guaranteed buys work in practice.
@@ -114,6 +110,7 @@ phases:
         schema_ref: "media-buy/get-products-request.json"
         response_schema_ref: "media-buy/get-products-response.json"
         doc_ref: "/media-buy/task-reference/get_products"
+        comply_scenario: full_sales_flow
         stateful: false
         expected: |
           Return guaranteed products matching the brief. Each product should include:
@@ -172,6 +169,7 @@ phases:
         schema_ref: "media-buy/create-media-buy-request.json"
         response_schema_ref: "media-buy/create-media-buy-response.json"
         doc_ref: "/media-buy/task-reference/create_media_buy"
+        comply_scenario: create_media_buy
         stateful: true
         expected: |
           Return the media buy in submitted status:
@@ -229,6 +227,7 @@ phases:
         schema_ref: "media-buy/get-media-buys-request.json"
         response_schema_ref: "media-buy/get-media-buys-response.json"
         doc_ref: "/media-buy/task-reference/get_media_buys"
+        comply_scenario: media_buy_lifecycle
         stateful: true
         expected: |
           Return the media buy in pending_approval status:
@@ -265,28 +264,29 @@ phases:
     narrative: |
       The human has reviewed the IO and signed it through the setup URL. The buyer
       polls get_media_buys again (or received a webhook notification) and sees that the
-      media buy has transitioned from pending_approval to confirmed or active. The buy
+      media buy has transitioned from pending_approval to active. The buy
       is now live.
 
     steps:
-      - id: get_media_buys_confirmed
-        title: "Check media buy status (confirmed/active)"
+      - id: get_media_buys_active
+        title: "Check media buy status (active)"
         narrative: |
           After the human signs the IO, the buyer checks the media buy status again.
-          Your platform returns confirmed or active, indicating the buy is approved
+          Your platform returns active, indicating the buy is approved
           and inventory is reserved.
         task: get_media_buys
         schema_ref: "media-buy/get-media-buys-request.json"
         response_schema_ref: "media-buy/get-media-buys-response.json"
         doc_ref: "/media-buy/task-reference/get_media_buys"
+        comply_scenario: media_buy_lifecycle
         stateful: true
         expected: |
-          Return the media buy in confirmed or active status:
+          Return the media buy in active status:
           - media_buy_id: matches the buy created earlier
-          - status: confirmed or active (IO has been signed)
+          - status: active (IO has been signed)
           - confirmed_at: timestamp when the IO was signed
-          - packages: line items now confirmed with reserved inventory
-          - valid_actions: updated for confirmed state (creative sync, pause, etc.)
+          - packages: line items with reserved inventory
+          - valid_actions: updated for active state (creative sync, pause, etc.)
 
         sample_request:
           account:
@@ -301,15 +301,15 @@ phases:
             description: "Response matches get-media-buys-response.json schema"
           - check: field_present
             path: "media_buys[0].status"
-            description: "Media buy status is confirmed or active"
+            description: "Media buy status is active"
           - check: field_present
             path: "media_buys[0].confirmed_at"
-            description: "Confirmed buy includes a confirmed_at timestamp"
+            description: "Active buy includes a confirmed_at timestamp"
 
   - id: creative_sync
     title: "Creative sync"
     narrative: |
-      With the IO signed and the media buy confirmed, the buyer syncs creative assets
+      With the IO signed and the media buy active, the buyer syncs creative assets
       to your platform. Each package has creative format requirements that the buyer
       discovered during product discovery.
 
@@ -323,6 +323,7 @@ phases:
         schema_ref: "creative/sync-creatives-request.json"
         response_schema_ref: "creative/sync-creatives-response.json"
         doc_ref: "/creative/task-reference/sync_creatives"
+        comply_scenario: creative_sync
         stateful: true
         expected: |
           Accept and validate creatives:
@@ -371,6 +372,7 @@ phases:
         schema_ref: "media-buy/get-media-buy-delivery-request.json"
         response_schema_ref: "media-buy/get-media-buy-delivery-response.json"
         doc_ref: "/media-buy/task-reference/get_media_buy_delivery"
+        comply_scenario: reporting_flow
         stateful: true
         expected: |
           Return delivery metrics for the guaranteed media buy:
@@ -392,5 +394,5 @@ phases:
           - check: response_schema
             description: "Response matches get-media-buy-delivery-response.json schema"
           - check: field_present
-            path: "media_buys"
+            path: "media_buy_deliveries"
             description: "Response contains media buy delivery data"

package/storyboards/media_buy_non_guaranteed.yaml

@@ -3,15 +3,11 @@ version: "1.0.0"
 title: "Non-guaranteed auction-based media buy"
 category: media_buy_non_guaranteed
 summary: "Seller agent for auction-based, non-guaranteed buying where the buyer sets bid prices and budgets."
-platform_types:
-  - social_platform
-  - dsp
-  - pmax_platform
-  - generative_dsp
-
 track: media_buy
 required_tools:
+  - get_products
   - create_media_buy
+
 narrative: |
   You run a sell-side platform with auction-based inventory. Non-guaranteed buys don't
   require IOs or human approval — the buyer sets a bid price and budget, and your platform
@@ -66,6 +62,7 @@ phases:
         schema_ref: "media-buy/get-products-request.json"
         response_schema_ref: "media-buy/get-products-response.json"
         doc_ref: "/media-buy/task-reference/get_products"
+        comply_scenario: full_sales_flow
         stateful: false
         expected: |
           Return non-guaranteed products matching the brief. Each product should include:
@@ -122,11 +119,12 @@ phases:
         schema_ref: "media-buy/create-media-buy-request.json"
         response_schema_ref: "media-buy/create-media-buy-response.json"
         doc_ref: "/media-buy/task-reference/create_media_buy"
+        comply_scenario: create_media_buy
         stateful: true
         expected: |
           Return the media buy in completed status:
           - media_buy_id: your platform's identifier
-          - status: confirmed or active (no async approval needed)
+          - status: active (no async approval needed)
           - confirmed_at: timestamp
           - packages: confirmed line items with bid prices acknowledged
           - valid_actions: pause, update_bid, get_delivery
@@ -178,6 +176,7 @@ phases:
         schema_ref: "media-buy/get-media-buys-request.json"
         response_schema_ref: "media-buy/get-media-buys-response.json"
         doc_ref: "/media-buy/task-reference/get_media_buys"
+        comply_scenario: media_buy_lifecycle
         stateful: true
         expected: |
           Return the media buy with pacing data:
@@ -219,6 +218,7 @@ phases:
         schema_ref: "media-buy/update-media-buy-request.json"
         response_schema_ref: "media-buy/update-media-buy-response.json"
         doc_ref: "/media-buy/task-reference/update_media_buy"
+        comply_scenario: media_buy_lifecycle
         stateful: true
         expected: |
           Apply the updates and return the modified media buy:
@@ -262,6 +262,7 @@ phases:
         schema_ref: "media-buy/get-media-buy-delivery-request.json"
         response_schema_ref: "media-buy/get-media-buy-delivery-response.json"
         doc_ref: "/media-buy/task-reference/get_media_buy_delivery"
+        comply_scenario: reporting_flow
         stateful: true
         expected: |
           Return delivery metrics for the non-guaranteed media buy:
@@ -284,5 +285,5 @@ phases:
           - check: response_schema
             description: "Response matches get-media-buy-delivery-response.json schema"
           - check: field_present
-            path: "media_buys"
+            path: "media_buy_deliveries"
             description: "Response contains media buy delivery data"

package/storyboards/media_buy_proposal_mode.yaml

@@ -3,16 +3,11 @@ version: "1.0.0"
 title: "Media buy via proposal acceptance"
 category: media_buy_proposal_mode
 summary: "Seller agent that generates curated media plan proposals the buyer can review, refine, and accept."
-platform_types:
-  - dsp
-  - retail_media
-  - pmax_platform
-  - generative_dsp
-
 track: media_buy
 required_tools:
-  - create_media_buy
   - get_products
+  - create_media_buy
+
 narrative: |
   Your seller generates curated media plan proposals. The buyer sends a brief, your platform
   returns products alongside proposals — curated bundles with budget allocations and rationale
@@ -110,6 +105,7 @@ phases:
         schema_ref: "media-buy/get-products-request.json"
         response_schema_ref: "media-buy/get-products-response.json"
         doc_ref: "/media-buy/task-reference/get_products"
+        comply_scenario: full_sales_flow
         stateful: false
         expected: |
           Return products and proposals matching the brief:
@@ -164,6 +160,7 @@ phases:
         schema_ref: "media-buy/get-products-request.json"
         response_schema_ref: "media-buy/get-products-response.json"
         doc_ref: "/media-buy/task-reference/get_products"
+        comply_scenario: full_sales_flow
         stateful: true
         expected: |
           Return the refined proposal:
@@ -200,7 +197,7 @@ phases:
       The buyer is satisfied with the refined proposal and accepts it by creating a
       media buy with the proposal_id. Instead of specifying individual packages, the
       buyer passes the proposal_id and total_budget. Your platform converts the proposal
-      into a confirmed media buy with the exact product selections and budget allocations
+      into an active media buy with the exact product selections and budget allocations
       from the proposal.
 
     steps:
@@ -217,11 +214,12 @@ phases:
         schema_ref: "media-buy/create-media-buy-request.json"
         response_schema_ref: "media-buy/create-media-buy-response.json"
         doc_ref: "/media-buy/task-reference/create_media_buy"
+        comply_scenario: create_media_buy
         stateful: true
         expected: |
-          Convert the proposal into a confirmed media buy:
+          Convert the proposal into an active media buy:
           - media_buy_id: your platform's identifier
-          - status: confirmed or active
+          - status: active
           - confirmed_at: timestamp
           - packages: line items derived from the proposal's budget allocations
           - proposal_id: echoed back to confirm which proposal was accepted
@@ -260,6 +258,7 @@ phases:
         schema_ref: "creative/list-creative-formats-request.json"
         response_schema_ref: "creative/list-creative-formats-response.json"
         doc_ref: "/creative/task-reference/list_creative_formats"
+        comply_scenario: creative_lifecycle
         stateful: false
         expected: |
           Return creative formats your platform accepts. Each format should define:
@@ -286,6 +285,7 @@ phases:
         schema_ref: "creative/sync-creatives-request.json"
         response_schema_ref: "creative/sync-creatives-response.json"
         doc_ref: "/creative/task-reference/sync_creatives"
+        comply_scenario: creative_sync
         stateful: true
         expected: |
           Accept and validate creatives:
@@ -344,6 +344,7 @@ phases:
         schema_ref: "media-buy/get-media-buy-delivery-request.json"
         response_schema_ref: "media-buy/get-media-buy-delivery-response.json"
         doc_ref: "/media-buy/task-reference/get_media_buy_delivery"
+        comply_scenario: reporting_flow
         stateful: true
         expected: |
           Return delivery metrics for the media buy:
@@ -365,5 +366,5 @@ phases:
           - check: response_schema
             description: "Response matches get-media-buy-delivery-response.json schema"
           - check: field_present
-            path: "media_buys"
+            path: "media_buy_deliveries"
             description: "Response contains media buy delivery data"