Problem
The tiered reporting staging (#6911) makes reporting.core the required tier, deliberately implementable by a webhook/polling seller with no warehouse, hashing, or receipt code. That promise needs a public implementation guide — otherwise the 5,000-line PR is the only map, and the tier boundary lives in schema conditionals implementers have to reverse-engineer.
Proposal
An implementation guide page shipping with the 3.2 documentation (landing with PR #6953 or immediately after):
- What Core is: obligations before reports, zero-row ≠ missing, the five health states,
get_reporting_status — over get_media_buy_delivery and reporting_webhook transports you already have.
- What Core is not: destinations, manifests, canonical digests, receipts, push (the doorbell is optional; polling is authoritative).
- Build order for a seller: obligation ledger from delivery configs + campaign lifecycle → revision records → status projections → the automated-recovery window and
action_required escalation.
- How to verify: the
reporting-core universal storyboard plus the reporting-core fixture test as the executable definition of the tier boundary.
- Tier ladder: what advertising
managed_delivery and reconciled_billing adds later, so Core adopters see the path without being obligated to it.
The buyer-side pilot one-pager derives from this guide. This is release documentation, not marketing — it becomes the canonical "how to implement AdCP reporting" page going forward.
🤖 Generated with Claude Code
Problem
The tiered reporting staging (#6911) makes
reporting.corethe required tier, deliberately implementable by a webhook/polling seller with no warehouse, hashing, or receipt code. That promise needs a public implementation guide — otherwise the 5,000-line PR is the only map, and the tier boundary lives in schema conditionals implementers have to reverse-engineer.Proposal
An implementation guide page shipping with the 3.2 documentation (landing with PR #6953 or immediately after):
get_reporting_status— overget_media_buy_deliveryandreporting_webhooktransports you already have.action_requiredescalation.reporting-coreuniversal storyboard plus the reporting-core fixture test as the executable definition of the tier boundary.managed_deliveryandreconciled_billingadds later, so Core adopters see the path without being obligated to it.The buyer-side pilot one-pager derives from this guide. This is release documentation, not marketing — it becomes the canonical "how to implement AdCP reporting" page going forward.
🤖 Generated with Claude Code