docs(specs): static OOH draft proposal

[bokelley]

Summary

Draft design doc for adding static (printed) out-of-home to the Media Buy protocol — the channel gap raised by AdQuick, who transact static OOH daily and want to help define it in the spec. ooh exists in channels.json and the media channel taxonomy today, but nothing downstream implements it: the DOOH guide requires an impression tracker on every format, and a printed bulletin has no play event to fire.

The draft is grounded in existing standards rather than invented conventions:

• OAAA model contracts (Bulletin/Poster Net Contracts) for proof-of-performance photos, posting leeway, material deadlines, and makegoods — conventions the whole US industry mirrors but nobody has made machine-readable
• OAAA Standard OOH Media Formats + Print Production Specs for format definitions and asset requirements
• IAB Tech Lab OpenDirect 2.1 (Oct 2024, with OAAA/OMA/Outsmart) as prior art that classic OOH belongs in guaranteed order-based trading — vocabulary borrowed, transport not
• Geopath/Route/MOVE/COMMB for delivery as vendor-attested weekly modeled impressions, kept pluggable given the announced Geopath→Ipsos transition

Core architectural claim: static OOH is broadcast-shaped, not DOOH-shaped — no tracker slot + billing_measurement naming the audience currency, reusing the print creative machinery, the installment/material-deadline model for posting periods, and existing billing-authority modes. The genuinely new pieces are posting-period semantics, a structured measurement-methodology reference, a posting_evidence proof-of-performance artifact, and an ooh property type.

Status

Discussion draft — this is the GitHub-first strawman ahead of Media Buy WG review. The Open Questions section lists the decisions that need real transaction data (unit identity across operators, markets without a measurement currency, rotary bulletins, makegood states, materials responsibility, the dooh/ooh boundary). Comments welcome, especially from folks who transact static today.

No schema or docs changes in this PR — design doc only.

🤖 Generated with Claude Code

[aao-secretariat]

Ladon verdict: Approve

Approve — clean first review, no blocking findings.

Checked: single new file specs/static-ooh.md (125 lines), a discussion-draft design memo explicitly marked "Draft — for discussion." It touches no published protocol surface (no static/schemas/source/**, no docs/reference/** normative docs, no dist/**, no release scripts), so no changeset is required and the wire-shape/immutability/oneOf/patch-eligibility gates do not apply. Constitutionally it is Normative-input (a memo), not the change itself — not a Breaking-class change requiring ratification.

Reviewer verified all six load-bearing factual claims about the existing spec as accurate against base (ooh in channels.json but absent from property-type.json, taxonomy exclusion quoted verbatim, reporting-frequency.json lacking weekly, venue_breakdown nesting, impression-multiplier prose with no backing field, Static Billboard Manifest impression_tracker requirement).

No Critical/High/Medium findings. high_risk: false, gated_paths: false (so the REVIEW_REQUIRED status does not trigger row 2), no no-auto-approve team match, no prior decision. Rows 1–8 do not fire; falls through to row 9 → approve.

[aao-secretariat]

Ladon verdict: Approve

Approve — clean prose-only spec draft, no blocking findings.

This PR adds a single new file, specs/static-ooh.md, a Draft design narrative for the Working Group proposing static-OOH support (channel guide, ooh_metrics, posting evidence, installment-based posting periods, property-type/identifier additions). It is prose only — no published protocol surface is touched: no JSON Schema under static/schemas/source/**, no docs/reference/** normative docs, no dist/** artifacts, no wire shape, and no server code. Consequently the changeset, oneOf-discriminator, artifact-immutability, and 3.1.x patch-eligibility gates do not apply.

Gate checks:

• No no-auto-approve team match.
• gated_paths: false, so the deterministic path gate does not fire even though review_decision is REVIEW_REQUIRED (row 2 requires gated_paths: true).
• high_risk: false; no deleted/modified high-risk files.
• No breaking-class protocol change (a draft narrative adds no normative wire requirement).

Reviewer verified every load-bearing factual claim against the repo; all hold. Zero findings at any severity. Prior decision was also approve on an earlier head with no findings. Rows 1–8 do not fire; falls through to row 9.