@adcp/client 4.22.0 → 4.23.0

package/storyboards/schema_validation.yaml

@@ -1,10 +1,9 @@
 id: schema_validation
 version: "1.0.0"
 title: "Schema compliance and temporal validation"
-category: media_buy_seller
-track: core
+category: schema_validation
 summary: "Validates that agent responses conform to AdCP schemas and that temporal constraints are enforced."
-
+track: core
 required_tools:
   - get_products
 
@@ -29,13 +28,18 @@ caller:
   role: buyer_agent
   example: "Compliance test harness"
 
+prerequisites:
+  description: |
+    The caller needs a brand identity for product discovery requests.
+  test_kit: "test-kits/acme-outdoor.yaml"
+
 phases:
   - id: schema_compliance
     title: "Response schema compliance"
     narrative: |
       The buyer sends a standard get_products request and validates that the response
       matches the published schema. Each product must have the required fields defined
-      in the AdCP spec: product_id, delivery_type, and pricing information.
+      in the AdCP spec.
 
     steps:
       - id: get_products_schema
@@ -45,7 +49,10 @@ phases:
           must conform to the get-products-response.json schema, with required v3 fields
           present.
         task: get_products
-        requires_tool: get_products
+        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: schema_compliance
         stateful: false
         expected: |
           Return products matching the brief. Each product must have:
@@ -53,11 +60,13 @@ phases:
           - name: human-readable name
           - delivery_type: guaranteed or non_guaranteed
           - pricing_options: at least one pricing option
+
         sample_request:
           buying_mode: "brief"
           brief: "Show all available advertising products"
           brand:
             domain: "acmeoutdoor.com"
+
         validations:
           - check: response_schema
             description: "Response matches get-products-response.json schema"
@@ -70,32 +79,31 @@ phases:
           - check: field_present
             path: "products[0].delivery_type"
             description: "Each product declares guaranteed or non_guaranteed delivery"
-          - check: field_present
-            path: "products[0].name"
-            description: "Each product has a name"
 
       - id: pricing_options_present
         title: "Validate pricing options structure"
         narrative: |
-          Check that products include pricing_options with the required fields:
-          pricing_option_id and pricing_model. These are essential for buyers to
+          Verify that products include pricing_options with the required fields:
+          pricing_option_id and pricing_model. These are required for buyers to
           construct valid create_media_buy requests.
         task: get_products
-        requires_tool: get_products
+        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: schema_compliance
         stateful: false
         expected: |
           Products include pricing_options with:
           - pricing_option_id: unique identifier for the pricing option
-          - pricing_model: CPM, CPC, flat_fee, etc.
+          - pricing_model: CPM, CPC, flat_rate, etc.
+
         sample_request:
           buying_mode: "brief"
-          brief: "Products with detailed pricing information"
+          brief: "Premium display inventory with pricing details"
           brand:
             domain: "acmeoutdoor.com"
+
         validations:
-          - check: field_present
-            path: "products[0].pricing_options"
-            description: "Products include pricing_options array"
           - check: field_present
             path: "products[0].pricing_options[0].pricing_option_id"
             description: "Pricing options have a pricing_option_id"
@@ -106,61 +114,60 @@ phases:
   - id: temporal_validation
     title: "Temporal constraint enforcement"
     narrative: |
-      Flight dates are a fundamental constraint in media buying. The start date must come
-      before the end date, and agents should validate this before accepting a media buy.
-      Some agents also reject start dates in the past, though this is platform-dependent.
+      The buyer sends media buy requests with invalid temporal constraints. The agent
+      must reject reversed dates (end before start) and handle past start dates
+      appropriately.
 
     steps:
       - id: reversed_dates
-        title: "Reject reversed date range"
+        title: "Reject reversed flight dates"
         narrative: |
-          Send a create_media_buy with end_time before start_time. The agent must reject
-          this — a campaign cannot end before it starts.
+          Send a create_media_buy request where end_time is before start_time. The agent
+          must reject this with an INVALID_REQUEST error.
         task: create_media_buy
-        requires_tool: create_media_buy
-        expect_error: true
+        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: temporal_validation
         stateful: false
         expected: |
-          Reject with an error containing:
-          - code: INVALID_REQUEST
-          - recovery: correctable
-          The agent must not accept a media buy where end_time precedes start_time.
+          Reject the request with:
+          - Error code: INVALID_REQUEST
+          - Message indicating the date constraint violation
+
         sample_request:
-          idempotency_key: "temporal-test-reversed"
-          start_time: "2026-05-31T23:59:59Z"
-          end_time: "2026-05-01T00:00:00Z"
+          start_time: "2026-12-31T00:00:00Z"
+          end_time: "2026-01-01T00:00:00Z"
           packages:
             - product_id: "test-product"
-              budget: 1000
+              budget: 10000
               pricing_option_id: "test-pricing"
+
         validations:
-          - check: error_code
-            value: "INVALID_REQUEST"
-            description: "Error code is INVALID_REQUEST for reversed date range"
+          - check: field_present
+            path: "errors"
+            description: "Response contains an error for reversed dates"
 
       - id: past_start_date
-        title: "Handle start date in the past"
+        title: "Handle past start date"
         narrative: |
-          Send a create_media_buy with a start_time in the past. Some agents reject this
-          outright, others accept it and auto-adjust the start date. Both behaviors are
-          acceptable — what matters is that the response is structured and intentional.
+          Send a create_media_buy request with a start_time in the past. The agent
+          should either reject the request or auto-adjust the start date forward.
         task: create_media_buy
-        requires_tool: create_media_buy
+        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: temporal_validation
         stateful: false
         expected: |
-          Either:
-          - Reject with INVALID_REQUEST (strict validation)
-          - Accept and auto-adjust the start date (permissive)
-          Both are acceptable. The agent should not silently accept a past date without
-          adjusting it or warning the buyer.
+          Either reject with INVALID_REQUEST or accept with adjusted dates.
+          Both behaviors are valid — the key is that the agent does not silently
+          accept a past start date without acknowledgment.
+
         sample_request:
-          idempotency_key: "temporal-test-past-start"
-          start_time: "2025-01-01T00:00:00Z"
+          start_time: "2020-01-01T00:00:00Z"
           end_time: "2026-12-31T23:59:59Z"
           packages:
             - product_id: "test-product"
-              budget: 1000
+              budget: 10000
               pricing_option_id: "test-pricing"
-        validations:
-          - check: response_schema
-            description: "Response is a valid create-media-buy-response or structured error"