Compliance storyboard: measurement_terms negotiation fails on unsupported measurement_window

[annamedvedieva-teqblaze]

Protocol: media-buy
Storyboard: Media buy seller agent (17 storyboards, partial 48/77 steps passing)
Failing step: propose_seller_compatible_measurement_terms (task: create_media_buy)

Error:

TERMS_REJECTED: Proposed measurement_terms are outside the supported envelope.
packages[0]: measurement_window 'c7' is not a window this seller guarantees
(supported: delivery, givt_filtered, mrc_2s, post_givt, post_sivt, sivt_filtered)

Observed vs expected:
The storyboard proposes measurement_window: c7 and expects the seller to accept/negotiate it, but the seller agent under test only guarantees a fixed enum of windows (delivery, givt_filtered, mrc_2s, post_givt, post_sivt, sivt_filtered) and rejects the request outright.

Unclear whether this is:

1. A gap in the storyboard's negotiation flow (it should retry with a seller-supported window rather than treating outright rejection as terminal failure), or
2. A gap in spec guidance for how buyer/seller agents should negotiate measurement_terms when the initially-proposed window isn't supported.

6 additional failures remain in this run (7 total failures, 22 skipped of 77 steps) — filing this as the first representative failure; happy to file the others separately if they're distinct root causes.

Repro context: seller agent storyboard run — "Seller agent that receives briefs, returns products, accepts media buys, and reports delivery."

[bokelley]

Triage

Thanks for filing!

Classification: Conformance failure + Spec question
Bucket(s): compliance-suite, media-buy
Status: ready-for-human
Milestone: Spec Backlog

What the experts said:

• ad-tech-protocol-expert: Storyboard logic is correct — the replay-what-you-advertise contract is the intended design. The spec has no normative MUST preventing a seller from advertising a measurement_window it will reject at runtime. That gap needs closing with a bidirectional MUST (advertise-only-what-you-accept, accept-what-you-advertise), mirroring the attribution_windows cross-constraint pattern in optimization-goal.json.
• code-reviewer: The storyboard should not add a cross-validation step — that would be scaffolding around a seller bug. The right anchor is a spec MUST. Storyboard fix is a narrative addition to prerequisites, not a new step.

My take: The storyboard (measurement_terms_accepted.yaml) correctly reads products[0].measurement_terms and replays it in create_media_buy. A seller that returns measurement_window: "c7" on a product and then rejects c7 with TERMS_REJECTED is exhibiting a product-catalog/runtime inconsistency — not a storyboard defect. Two fixes are needed; one can ship immediately.

---

Decision memo (WG ratification needed)

Ruling: Sellers MUST NOT include a measurement_window value in a product's measurement_terms.billing_measurement that the seller would reject in create_media_buy with TERMS_REJECTED.

Class: Normative MUST addition — new seller conformance obligation; no wire-format change; additive to existing TERMS_REJECTED semantics.

Synthesis: The measurement_window field already says it "references a window_id from the product's reporting_capabilities.measurement_windows." This is descriptive, not normative. The proposed MUST closes the bidirectional gap: sellers advertise only windows they honor; storyboards that replay advertised terms are safe to trust. Prior art: optimization-goal.json attribution_windows cross-constraint.

Recommendation: Add a normative MUST to the create_media_buy and/or get_products task-reference docs, route to Spec Backlog. Storyboard narrative fix can ship as an independent patch (see below).

Dissent: None.

---

Ready to implement — storyboard narrative fix (patch-eligible)

• File: static/compliance/source/protocols/media-buy/scenarios/measurement_terms_accepted.yaml
• Change: Extend prerequisites.description to state explicitly that the seller's product MUST declare in measurement_terms only windows it will accept in create_media_buy. The storyboard replays these terms verbatim; a seller that returns a window it later rejects is exhibiting a conformance bug that this storyboard is designed to surface.
• Non-breaking: docs-only, no schema change, no new storyboard step.
• Release: patch-eligible; no changeset needed (non-normative).

---

Triaged by Claude Code. Session: https://claude.ai/code/session_01FpQLHNhUGtVD8H1xNwoYtd

---

Generated by Claude Code