@adcp/sdk 15.8.0 → 15.9.0

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/outcome_target_list_products_inert.yaml

@@ -4,6 +4,9 @@ title: "list_products ignores criteria.outcome_target for every seller"
 category: media_buy_seller
 summary: "Verifies that a list_products request carrying criteria.outcome_target is answered with a product page rather than rejected, whether or not the seller declares media_buy.outcome_target."
 track: media_buy
+requires:
+  - controller
+
 introduced_in: "3.2"
 
 required_tools:

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/owner_sold_channel_carriage.yaml

@@ -5,6 +5,8 @@ title: "Seller declares owner-sold channel carriage and enforces collection sele
 category: media_buy_seller
 summary: "Verifies an owner-sold channel product combines host property scope with the owner's canonical collection selector, that buyer collection selection requires explicit collection_ids, and that unknown or mismatched collection selectors are rejected rather than silently substituted."
 track: media_buy
+requires:
+  - controller
 
 required_tools:
   - get_products

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/package_automatic_bidding.yaml

@@ -4,6 +4,8 @@ title: "Seller preserves explicit package automatic bidding"
 category: media_buy_seller
 summary: "Verifies package-scoped automatic bidding independently of media-buy bidding support."
 track: media_buy
+requires:
+  - controller
 
 requires_capability:
   path: media_buy.features.bidding_policy.package.fixed.modes

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/package_correlation_legacy_fallback.yaml

@@ -4,6 +4,9 @@ title: "Legacy package correlation fallback without product_id"
 category: media_buy_seller
 summary: "Models the mixed-seller compatibility path where a legacy package response omits product_id and buyers correlate by package context.buyer_ref."
 track: media_buy
+requires:
+  - controller
+
 required_tools:
   - get_media_buys
 

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/pending_creatives_to_start.yaml

@@ -4,6 +4,8 @@ title: "Creative sync unblocks pending_creatives → pending_start"
 category: media_buy_seller
 summary: "Verifies that a media buy created without creatives sits in pending_creatives until sync_creatives completes, then transitions to pending_start."
 track: media_buy
+requires:
+  - controller
 
 # This scenario requires both a creative library and an explicit auto-approval
 # declaration. Sellers that lack either capability grade not_applicable rather

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/per_creative_conversion_attribution.yaml

@@ -4,6 +4,8 @@ title: "Seller surfaces per-creative conversion attribution in delivery reportin
 category: media_buy_seller
 summary: "Verifies that a seller advertising conversion_tracking.per_creative_attribution can register two creatives on a single package, accept a media buy with a CPA event-kind goal, ingest conversion events, and surface a populated by_package[].by_creative[] breakdown carrying conversions per creative in get_media_buy_delivery. Sibling to media_buy_seller/performance_buy_flow gated on the per_creative_attribution sub-capability: sellers that report attribution only at the line / package / placement / campaign granularity (retail-media, MMP-mediated mobile, CTV performance) grade not_applicable, not failing."
 track: media_buy
+requires:
+  - controller
 
 # Gate: scenario runs only when the seller declares
 # conversion_tracking.per_creative_attribution equals true. Sellers that

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/performance_buy_flow.yaml

@@ -4,6 +4,8 @@ title: "Seller fulfills a performance (event-kind goal) media buy with a CPA tar
 category: media_buy_seller
 summary: "Verifies that a seller advertising conversion_tracking can bind an event source, accept a media buy with an event-kind optimization_goal targeting CPA, reject malformed performance briefs, ingest conversion events, and report conversion-attributed delivery including per-creative breakdown. ROAS / maximize_value goals are out of scope — see media_buy_seller/performance_buy_flow_roas (separate scenario, gated on the supported_target_kinds capability bit from #4639)."
 track: media_buy
+requires:
+  - controller
 
 # Gate: scenario runs only when the seller declares conversion_tracking.
 # Sellers without it (pure brand/audience sellers — broadcast TV, signal-only)

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/performance_buy_flow_roas.yaml

@@ -4,6 +4,8 @@ title: "Seller fulfills a performance (event-kind goal) media buy with a ROAS ta
 category: media_buy_seller
 summary: "Verifies that a seller advertising conversion_tracking with per_ad_spend in supported_targets can accept a media buy whose event-kind optimization_goal carries a ROAS (per_ad_spend) target bound to an event source with value_field, reject ROAS goals that omit value_field on every event-source entry, ingest valued purchase events, and report conversion_value + roas alongside conversions and cost_per_acquisition. Sibling to media_buy_seller/performance_buy_flow gated on the supported_targets sub-capability: sellers that don't advertise per_ad_spend (most broadcast TV, upper-funnel video, signal-only) grade not_applicable."
 track: media_buy
+requires:
+  - controller
 
 # Gate: scenario runs only when the seller declares per_ad_spend in
 # conversion_tracking.supported_targets. Sellers that compute conversions

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/portfolio_routing_scope.yaml

@@ -4,6 +4,9 @@ title: "Seller declares brief-routing portfolio scope"
 category: media_buy_seller
 summary: "Advises when a media-buy seller omits its complete country or channel routing allowlist."
 track: media_buy
+requires:
+  - controller
+
 introduced_in: "3.2"
 
 required_tools:

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/pricing_currency_filter.yaml

@@ -4,6 +4,9 @@ title: "Seller filters products by accepted pricing currencies"
 category: media_buy_seller
 summary: "Verifies that get_products filters.pricing_currencies returns only products buyable in the requested media pricing currency and prunes returned product pricing_options."
 track: media_buy
+requires:
+  - controller
+
 required_tools:
   - get_products
   - comply_test_controller

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/product_coverage_filters.yaml

@@ -4,6 +4,9 @@ title: "Product coverage is preserved across discovery surfaces"
 category: media_buy_seller
 summary: "Checks legacy and compact coverage predicates against independent negative controls without configuring delivery targeting."
 track: media_buy
+requires:
+  - controller
+
 introduced_in: "3.2"
 required_tools: [get_products, list_products, comply_test_controller]
 

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/product_filter_behavior.yaml

@@ -4,6 +4,8 @@ title: "Seller applies deterministic product filters in every buying mode"
 category: media_buy_seller
 summary: "Verifies schema-valid get_products filters affect brief curation, wholesale feeds, and refinement instead of silently no-oping."
 track: media_buy
+requires:
+  - controller
 
 required_tools:
   - get_products

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/product_signal_targeting.yaml

@@ -4,6 +4,8 @@ title: "Seller exposes wholesale signal options and honors package-level signal_
 category: media_buy_seller
 summary: "Verifies that a seller with wholesale products and wholesale get_signals can expose signal targeting eligibility, accept package-level signal_targeting_groups with pricing, reject unknown signals, and echo the applied grouped expression on readback."
 track: media_buy
+requires:
+  - controller
 
 # Gate: this scenario is for sellers that expose the selectable signal menu
 # through the wholesale signals feed. Product-specific inline menus are covered

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/provenance_audit_observation.yaml

@@ -4,6 +4,9 @@ title: "Seller accepts a provenance carve-out claim surfaced as an audit observa
 category: media_buy_seller
 summary: "Buyer submits AI-assisted creatives with human_oversight directed/edited and disclosure.required false. Seller invokes an on-list verifier, records OVERSIGHT_DISCLOSURE_CARVEOUT_CLAIMED audit observations, and accepts the creatives rather than treating the observations as rejections."
 track: creative
+requires:
+  - controller
+
 required_tools:
   - get_products
   - sync_creatives

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/provenance_enforcement.yaml

@@ -4,6 +4,9 @@ title: "Seller enforces provenance_requirements on sync_creatives"
 category: media_buy_seller
 summary: "Seller publishes provenance_requirements + accepted_verifiers on a product. Four structural rejections (no provenance, missing digital_source_type, off-list verifier, missing disclosure), then a corrected resubmission with on-list verifier is accepted."
 track: creative
+requires:
+  - controller
+
 required_tools:
   - get_products
   - sync_creatives

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/provenance_truth_of_claim.yaml

@@ -4,6 +4,9 @@ title: "Seller refutes a buyer's provenance claim via on-list verifier"
 category: media_buy_seller
 summary: "Buyer attaches a digital_source_type claim. Seller invokes get_creative_features against an on-list verifier (creative_policy.accepted_verifiers); when the verifier contradicts the claim, seller rejects with PROVENANCE_CLAIM_CONTRADICTED carrying audit-safe error.details."
 track: creative
+requires:
+  - controller
+
 required_tools:
   - get_products
   - sync_creatives

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/reach_buy_flow.yaml

@@ -4,6 +4,8 @@ title: "Seller fulfills a media buy with a reach optimization goal"
 category: media_buy_seller
 summary: "Verifies that a seller advertising reach in supported_optimization_metrics can accept a media buy whose metric-kind optimization_goal targets unique reach with a buyer-supplied reach_unit, reject reach_unit values not in the product's metric_optimization.supported_reach_units, and report reach + frequency on delivery. Sibling to the performance buy scenarios on the brand-reach side: sellers that don't advertise reach as an optimization metric (most pure performance DSPs, retail-media networks) grade not_applicable."
 track: media_buy
+requires:
+  - controller
 
 # Gate: scenario runs only when the seller declares reach in
 # media_buy.supported_optimization_metrics (proposed in #4669). Sellers

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/read_filter_behavior.yaml

@@ -5,6 +5,8 @@ title: "Seller applies deterministic media-buy read filters"
 category: media_buy_seller
 summary: "Verifies get_media_buys membership filters and half-open get_media_buy_delivery date bounds instead of accepting them as no-ops."
 track: reporting
+requires:
+  - controller
 
 required_tools:
   - get_media_buys

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/revenue_share_pricing.yaml

@@ -4,6 +4,9 @@ title: "Revenue-share pricing and settlement"
 category: media_buy_seller
 summary: "Verifies contingent revenue-share discovery, commitment without a bid, commissionable-value delivery, and formula-checked usage reconciliation."
 track: media_buy
+requires:
+  - controller
+
 introduced_in: "3.1"
 required_tools:
   - sync_accounts

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/seller_optimized_budget.yaml

@@ -1,9 +1,11 @@
 id: media_buy_seller/seller_optimized_budget
-version: "1.1.0"
+version: "1.1.1"
 title: "Seller accepts and persists a seller-optimized budget across packages"
 category: media_buy_seller
 summary: "Verifies that a seller advertising seller_optimized_budget accepts and persists the core shared-budget contract (shared total, cross-package goals, media-buy pacing, allocation echo). Package caps, minimum-spend targets, and package pacing are graded only when their own sub-capability is advertised, and must be rejected with UNSUPPORTED_FEATURE before any over-subscription validation when it is not."
 track: media_buy
+requires:
+  - controller
 
 requires_capability:
   path: media_buy.features.seller_optimized_budget
@@ -576,7 +578,7 @@ phases:
       equals: true
     steps:
       - id: create_shared_buy_with_min_spend_targets
-        title: "Set a soft minimum on the prospecting package"
+        title: "Set a soft minimum on the retargeting package"
         task: create_media_buy
         schema_ref: "media-buy/create-media-buy-request.json"
         response_schema_ref: "media-buy/create-media-buy-response.json"
@@ -584,7 +586,11 @@ phases:
         stateful: true
         expected: |
           Accept a soft minimum-spend target (20000) on an uncapped
-          prospecting package and echo it unchanged.
+          retargeting package and echo it unchanged. The target sits on the
+          second package because a conformance runner may author a package
+          cap on the first package of every create request; a target on that
+          package could then exceed its own cap, which is graded by
+          media_buy_seller/seller_optimized_min_spend_target_exceeds_package_cap.
         sample_request:
           account:
             brand:
@@ -605,9 +611,9 @@ phases:
           packages:
             - product_id: "shared_budget_prospecting"
               pricing_option_id: "prospecting_cpm"
-              min_spend_target: 20000
             - product_id: "shared_budget_retargeting"
               pricing_option_id: "retargeting_cpm"
+              min_spend_target: 20000
           start_time: "asap"
           end_time: "2099-06-30T23:59:59Z"
           idempotency_key: "$generate:uuid_v4#seller_optimized_budget_min_spend_targets"
@@ -624,7 +630,7 @@ phases:
           - check: field_contains
             path: "packages[*]"
             value:
-              product_id: "shared_budget_prospecting"
+              product_id: "shared_budget_retargeting"
               min_spend_target: 20000
             description: "Response preserves the soft package minimum-spend target"
 
@@ -649,7 +655,7 @@ phases:
           - check: field_contains
             path: "media_buys[0].packages[*]"
             value:
-              product_id: "shared_budget_prospecting"
+              product_id: "shared_budget_retargeting"
               min_spend_target: 20000
             description: "Readback preserves the package minimum-spend target"
 

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/seller_optimized_min_spend_target_exceeds_package_cap.yaml

@@ -4,6 +4,9 @@ title: "Seller rejects a minimum-spend target above its own package cap"
 category: media_buy_seller
 summary: "Verifies that a seller advertising seller-optimized budgets, package budget caps, and minimum-spend targets rejects a package min_spend_target above that package's budget with INVALID_REQUEST before mutation."
 track: media_buy
+requires:
+  - controller
+
 introduced_in: "3.2"
 
 # The cap-versus-minimum check is over-subscription validation across two

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/seller_optimized_proposal_package_pacing.yaml

@@ -4,6 +4,9 @@ title: "Seller-optimized proposal carries subordinate package pacing into the bu
 category: media_buy_seller
 summary: "Verifies that a seller advertising seller-optimized budgets, package pacing, and proposals can express subordinate allocation pacing on a seller-optimized proposal and translate it into package pacing on execution and readback."
 track: media_buy
+requires:
+  - controller
+
 introduced_in: "3.2"
 
 # Proposal-derived package pacing needs three independent declarations: the

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/targeting_aware_discovery.yaml

@@ -4,6 +4,9 @@ title: "Seller resolves targeting during discovery and persists inventory select
 category: media_buy_seller
 summary: "Verifies targeting-scoped discovery forecasts, future overlay support, sparse configured-product modifications, opaque product acceptance, and inventory targeting across create/update/readback."
 track: media_buy
+requires:
+  - controller
+
 introduced_in: "3.2"
 
 required_tools:

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/total_budget_redistribution.yaml

@@ -4,6 +4,8 @@ title: "Atomic media-buy total budget redistribution"
 category: media_buy_seller
 summary: "Verifies that a fixed media-buy total_budget update proportionally rescales active packages, returns auditable package state, and rejects competing package patches atomically."
 track: media_buy
+requires:
+  - controller
 
 required_tools:
   - sync_accounts

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/typed_proposal_negotiation.yaml

@@ -5,12 +5,20 @@ category: media_buy_seller
 summary: "Verifies the AdCP 3.2 typed negotiation lifecycle: capability-gated constraint satisfaction, product changes, digest-verified alternatives, partial invariant, immutable lineage, finalize atomicity, and idempotent replay through refine_proposals."
 track: media_buy
 required_tools:
+  - request_proposals
   - refine_proposals
   - accept_proposal
 
-requires_capability:
-  path: media_buy.proposal_refinement.supported_dimensions
-  contains: "alternatives"
+requires:
+  - controller
+
+# Proposals are seeded through request_proposals (the 3.2 lifecycle tool), so a
+# seller that declares typed refinement without it is not applicable here.
+requires_all_capabilities:
+  - path: media_buy.proposal_refinement.supported_dimensions
+    contains: "alternatives"
+  - path: media_buy.lifecycle_tools
+    contains: "request_proposals"
 
 narrative: |
   AdCP 3.2 introduces typed proposal negotiation through refine_proposals.
@@ -39,7 +47,17 @@ narrative: |
 
   Legacy sellers that do not declare proposal_refinement are not tested by
   this storyboard; their unstructured proposal path is covered by
-  proposal_finalize.yaml.
+  proposal_finalize.yaml. Proposals are seeded with request_proposals, so
+  sellers that declare proposal_refinement but expose proposals only through
+  the legacy get_products facade are not applicable either: that facade cannot
+  represent typed constraints losslessly. The fixture products are seeded
+  through comply_test_controller.
+
+  Each phase after seeding names its upstream phases with depends_on. A
+  capability-gated phase the seller does not support (for example the
+  unsupported-dimension rejection when the seller declares flight) is skipped
+  alone and does not cascade-skip the finalize, accept, amendment, cancellation,
+  or batch phases.
 
 agent:
   interaction_model: media_buy_seller
@@ -60,6 +78,7 @@ prerequisites:
     The caller needs a brand identity and operator credentials. The seller
     must declare proposal_refinement.supported_dimensions in capabilities.
   test_kit: "test-kits/acme-outdoor.yaml"
+  controller_seeding: true
 
 fixtures:
   products:
@@ -175,21 +194,22 @@ phases:
       The buyer needs at least one proposal_id to target with refine_proposals.
 
     steps:
-      - id: get_products_brief
-        title: "Send a brief and receive proposals"
-        task: 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: full_sales_flow
-        stateful: false
+      - id: request_seed_proposals
+        title: "Request seed proposals for the fixture products"
+        task: request_proposals
+        schema_ref: "media-buy/request-proposals-request.json"
+        response_schema_ref: "media-buy/request-proposals-response.json"
+        doc_ref: "/media-buy/task-reference/request_proposals"
+        stateful: true
         expected: |
-          Return products and proposals matching the brief. At least one
-          proposal with proposal_id is required for the typed revision phases.
+          Return outcome proposed with at least one draft proposal covering
+          the seeded fixture products. The proposal_id is required for the
+          typed revision phases.
         sample_request:
-          idempotency_key: "$generate:uuid_v4#typed_negotiation_seed_get_products_brief"
-          buying_mode: "brief"
+          idempotency_key: "$generate:uuid_v4#typed_negotiation_seed_request_proposals"
           brief: "Premium video and display across sports and outdoor lifestyle. Q4 flight, $75K budget. Adults 25-54, US."
+          criteria:
+            product_ids: ["premium_video_q4", "display_standard_q4", "native_feed_q4"]
           account:
             brand:
               domain: "acmeoutdoor.example"
@@ -203,7 +223,7 @@ phases:
 
         validations:
           - check: response_schema
-            description: "Response matches get-products-response.json schema"
+            description: "Response matches request-proposals-response.json schema"
           - check: field_present
             path: "proposals"
             description: "Response contains proposals"
@@ -329,7 +349,7 @@ phases:
             value: "constraint_unsatisfiable"
             description: "reason_code is constraint_unsatisfiable for a typed failure"
           - check: field_contains
-            path: "results[0].unsatisfied_constraints"
+            path: "results[0].unsatisfied_constraints[*]"
             value: "total_budget"
             description: "unsatisfied_constraints echoes the failing constraint key"
 
@@ -485,6 +505,7 @@ phases:
 
   - id: finalize_proposal
     title: "Finalize draft into committed snapshot"
+    depends_on: [account_setup, seed_proposals]
     narrative: |
       Finalize the initial seed draft. The seller creates a committed
       successor with firm pricing and an inventory hold. The committed
@@ -542,6 +563,7 @@ phases:
 
   - id: finalize_idempotent_replay
     title: "Idempotent finalize replay"
+    depends_on: [finalize_proposal]
     narrative: |
       Replay the exact finalize request with the same idempotency_key. The
       seller must return the cached committed proposal with replayed: true.
@@ -579,6 +601,7 @@ phases:
 
   - id: accept_committed
     title: "Accept committed proposal to create MediaBuy"
+    depends_on: [finalize_proposal]
     narrative: |
       The buyer accepts the committed proposal by passing the proposal_id
       and proposal_terms_digest. The seller atomically verifies both before
@@ -618,6 +641,7 @@ phases:
 
   - id: amendment_from_accepted
     title: "Amendment proposal from accepted source"
+    depends_on: [accept_committed]
     narrative: |
       The buyer creates an amendment proposal against the accepted source.
       This exercises the change_kind: amendment path. The source remains
@@ -659,6 +683,7 @@ phases:
 
   - id: cancellation_from_accepted
     title: "Cancellation proposal from accepted source"
+    depends_on: [accept_committed]
     narrative: |
       The buyer creates a cancellation proposal against the accepted source.
       The source remains accepted and unchanged; the result is a new draft
@@ -698,6 +723,7 @@ phases:
 
   - id: double_finalize_rejected
     title: "Double-finalize of committed proposal"
+    depends_on: [finalize_proposal]
     narrative: |
       Attempt to finalize a proposal that is already committed (not a draft).
       The seller must reject with INVALID_STATE at task level because
@@ -729,6 +755,7 @@ phases:
 
   - id: multi_source_batch
     title: "Multi-source batch with mixed outcomes"
+    depends_on: [seed_proposals, amendment_from_accepted]
     narrative: |
       Send a batch revise request targeting two sources in one call. Each
       entry gets its own outcome — one may be revised while another is

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/vendor_metric_accountability.yaml

@@ -4,6 +4,8 @@ title: "End-to-end vendor-metric accountability: declaration → commitment →
 category: media_buy_seller
 summary: "Buyer commits vendor metrics on two packages, then verifies one clean package, one overdue gap, and one not-yet-measurable omission."
 track: reporting
+requires:
+  - controller
 
 requires_capability:
   path: media_buy.features.committed_metrics_supported

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/scenarios/vendor_metric_catalog_precondition.yaml

@@ -4,6 +4,9 @@ title: "Vendor-metric external catalog precondition"
 category: media_buy_seller
 summary: "Exercises the 3.1 SHOULD-window behavior for vendor_metric goals whose metric_id is absent from a seeded measurement.metrics[] catalog."
 track: media_buy
+requires:
+  - controller
+
 introduced_in: "3.1"
 
 # Gate: scenario runs only when the seller declares vendor-metric

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/media-buy/scenarios/vendor_metric_optimization_flow.yaml

@@ -4,6 +4,9 @@ title: "Vendor-metric optimization-goal: acceptance and rejection"
 category: media_buy_seller
 summary: "Verifies that a seller supporting vendor_metric_optimization accepts a media buy whose optimization_goal has kind 'vendor_metric' when all preconditions are met, and rejects goals that fail either the capability check or the reporting-coherence check."
 track: media_buy
+requires:
+  - controller
+
 introduced_in: "3.1"
 
 # Gate: scenario runs only when the seller declares vendor-metric

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/media-buy/state-machine.yaml

@@ -4,6 +4,8 @@ title: "Media buy state machine lifecycle"
 category: media_buy_state_machine
 summary: "Validates media buy state transitions: create, pause, resume, cancel, and terminal state enforcement."
 track: media_buy
+requires:
+  - controller
 
 # This storyboard drives pause/resume immediately after create_media_buy. That
 # only works for sellers that explicitly declare auto-approval; manual-review

package/compliance/cache/{3.2.3/domains → 3.2.4/protocols}/signals/index.yaml

@@ -5,6 +5,9 @@ protocol: signals
 category: signals_baseline
 summary: "Baseline domain storyboard — every signals agent must declare signals support and return discoverable signals."
 track: signals
+requires:
+  - controller
+
 required_tools:
   - get_signals
 

package/compliance/cache/{3.2.3 → 3.2.4}/protocols/signals/scenarios/get_signals_async.yaml

@@ -5,6 +5,9 @@ title: "Signals agent returns and completes async get_signals discovery tasks"
 category: signals_baseline
 summary: "Forces semantic get_signals discovery into the submitted arm, verifies task visibility, completes it deterministically, and observes the terminal webhook result."
 track: signals
+requires:
+  - controller
+
 required_tools:
   - get_signals
   - get_task_status

package/compliance/cache/{3.2.3 → 3.2.4}/specialisms/audience-sync/index.yaml

@@ -5,6 +5,9 @@ protocol: media-buy
 category: audience_sync
 summary: "Full audience lifecycle: account discovery, audience creation with hashed identifiers, and audience deletion."
 track: audiences
+requires:
+  - controller
+
 required_tools:
   - list_accounts
   - sync_audiences

package/compliance/cache/{3.2.3 → 3.2.4}/specialisms/brand-rights/index.yaml

@@ -5,6 +5,9 @@ protocol: brand
 category: brand_rights
 summary: "Brand agent that serves identity assets and licenses rights for AI-generated content."
 track: core
+requires:
+  - controller
+
 required_tools:
   - get_brand_identity
 requires_scenarios:

package/compliance/cache/{3.2.3 → 3.2.4}/specialisms/brand-rights/scenarios/update_rights_lifecycle.yaml

@@ -4,6 +4,8 @@ title: "Update a seeded rights grant and reject unknown references"
 category: brand_rights
 summary: "Verifies that update_rights atomically updates an acquired grant and rejects an unknown rights_id with REFERENCE_NOT_FOUND."
 track: brand
+requires:
+  - controller
 
 narrative: |
   `update_rights` operates on a grant, not on a catalog offering. The controller

package/compliance/cache/{3.2.3 → 3.2.4}/specialisms/collection-lists/index.yaml

@@ -5,6 +5,9 @@ protocol: governance
 category: collection_lists
 summary: "Curated collection lists for program-level brand safety and content targeting — create, query, update, and delete lists of content programs (shows, series, podcasts)."
 track: governance
+requires:
+  - controller
+
 required_tools:
   - create_collection_list
 

package/compliance/cache/{3.2.3 → 3.2.4}/specialisms/content-standards/index.yaml

@@ -5,6 +5,9 @@ protocol: governance
 category: content_standards
 summary: "Define creative quality rules, calibrate content against them, and validate that delivered ads met the standards."
 track: governance
+requires:
+  - controller
+
 required_tools:
   - list_content_standards
 

package/compliance/cache/{3.2.3 → 3.2.4}/specialisms/creative-ad-server/index.yaml

@@ -5,6 +5,9 @@ protocol: creative
 category: creative_ad_server
 summary: "Stateful ad server with pre-loaded creatives. Generates serving tags per media buy. Optionally bills through AdCP."
 track: creative
+requires:
+  - controller
+
 required_tools:
   - build_creative
 

package/compliance/cache/{3.2.3 → 3.2.4}/specialisms/creative-generative/generative-seller.yaml

@@ -4,6 +4,9 @@ title: "Generative seller agent"
 category: creative_generative
 summary: "Seller agent that generates creatives from briefs at buy time — no pre-built assets required."
 track: media_buy
+requires:
+  - controller
+
 required_tools:
   - get_products
   - create_media_buy

package/compliance/cache/{3.2.3 → 3.2.4}/specialisms/creative-generative/index.yaml

@@ -4,6 +4,9 @@ title: "Generative creative agent"
 protocol: creative
 category: creative_generative
 summary: "Agent that takes a brief and generates finished creatives from scratch — no input assets required."
+requires:
+  - controller
+
 required_tools:
   - build_creative
 # Note: sync_catalogs is NOT in required_tools. The catalog_augmented_generation

package/compliance/cache/{3.2.3 → 3.2.4}/specialisms/creative-template/index.yaml

@@ -5,6 +5,9 @@ protocol: creative
 category: creative_template
 summary: "Stateless creative agent that takes assets in, applies templates, and produces tags or rendered output."
 track: creative
+requires:
+  - controller
+
 required_tools:
   - build_creative
 

package/compliance/cache/{3.2.3 → 3.2.4}/specialisms/creative-transformers/index.yaml

@@ -4,6 +4,9 @@ title: "Account-scoped creative transformer agent"
 protocol: creative
 category: creative_transformers
 summary: "Agent that exposes account-scoped transformers (voices, models, render configs) via list_transformers, then builds and refines creatives by transformer_id + typed config — with variant fan-out and strict config validation."
+requires:
+  - controller
+
 required_tools:
   - list_transformers
   - build_creative