Problem
When get_media_buy_delivery disagrees with the buyer's own measurement, there is no normative path to resolve the disagreement. A hostile reviewer correctly flags this as a real gap: for a transaction protocol, the reconciliation story is load-bearing. Without it, buyers and sellers are left to work disputes through out-of-band channels, which undermines the "auditable agentic commerce" framing.
Context
Surfaced during pre-GA attack-surface review of critical-path spec gaps (3.0 readiness assessment, 2026-04-19). Documented as a known limitation in the GA spec-completeness manifest; targeted for normative treatment in 3.1.
Related:
get_media_buy_delivery currently returns delivery numbers as best-effort metrics- Account model covers credit limits and payment terms (
docs/media-buy/advanced-topics/accounts-and-security.mdx) but not dispute
report_usage reconciles between buyer and seller for signals/creative, but not for media-buy delivery discrepancies
Proposed output
A normative section + task covering:
- Are delivery numbers billing-grade or best-effort? Spec MUST answer this per response.
- Dispute task: a mutating request a buyer sends to open a delivery dispute, with fields for claimed delivery, source of claim, and dispute reason.
- Resolution states:
under_review, seller_adjusted, buyer_accepted, unresolved_arbitration.
- Audit semantics: the dispute and its resolution MUST be captured in the audit log for the media buy.
- SLA: recommended (SHOULD) response window.
Disposition
Known limitation at 3.0 GA. Target: 3.1.0.
Problem
When
get_media_buy_deliverydisagrees with the buyer's own measurement, there is no normative path to resolve the disagreement. A hostile reviewer correctly flags this as a real gap: for a transaction protocol, the reconciliation story is load-bearing. Without it, buyers and sellers are left to work disputes through out-of-band channels, which undermines the "auditable agentic commerce" framing.Context
Surfaced during pre-GA attack-surface review of critical-path spec gaps (3.0 readiness assessment, 2026-04-19). Documented as a known limitation in the GA spec-completeness manifest; targeted for normative treatment in 3.1.
Related:
get_media_buy_deliverycurrently returns delivery numbers as best-effort metricsdocs/media-buy/advanced-topics/accounts-and-security.mdx) but not disputereport_usagereconciles between buyer and seller for signals/creative, but not for media-buy delivery discrepanciesProposed output
A normative section + task covering:
under_review,seller_adjusted,buyer_accepted,unresolved_arbitration.Disposition
Known limitation at 3.0 GA. Target: 3.1.0.