### `wai.video.audience` and `wai.delivery.territory`: blackout decisions from an aggregated location, and where a publisher may be shown - [audience-decision](extensions/audience-decision.md) registers the record `wai.video.audience` (`wai-audience-decision`): a decider's signed decision of whether the sessions in one region may be shown a programme over a span, under the blackouts in force. Each blackout is named by the id a session class carries (http-delivery Appendix H `blackouts`) and lists its regions in rung-price §2's region codes, with the programme shown in its place, if any. - **A session's location is aggregated before it leaves the session** (§4.3): to the one listed code that holds it (its subdivision when listed, else its country when listed), to outside, or to unresolved when it holds none or only a country of which subdivisions are listed. The aggregation decides what the location would, and says no more of it. A decision whose evidence holds anything else, or a region finer than the aggregation gives, is refused `audience_location_not_aggregated`; one whose region the blackouts neither list nor hold is refused `audience_region_not_in_set`. - The blackouts that apply (every one in force, for an unresolved session), the verdict (`show`, `withhold`, or `alternate` when every blackout that applies names one programme in its place) and that programme follow from the blackouts and the region; a verifier recomputes them (`audience_decision_inconsistent`). A session class of the programme carries the blackouts that apply as its `blackouts`, and its `geo` is the region's country; a verifier given both states the class's hash, by which a playlist receipt names it. - It registers the record `wai.delivery.territory` (`wai-territory`): a publisher's signed statement of where its content may be shown, everywhere, only in some regions or everywhere but some, in the same codes. The publisher's latest statement stands alone, and one that lapses or is contradicted at its instant revives none. A verifier reports the territory (`within`, `outside`, `undetermined`, or `unstated` with its reason) beside a server key's placement, which cache-authority §4.4 computes from its own inputs alone and which no statement changes; a statement that names a server, an origin or a role is refused `territory_scopes_serving`. cache-authority §4.3 and §4.4 are unchanged. - Both are route-record documents signed in their canonical form under their own domains (`wai:audience-decision`, `wai:territory`); a signature over any other bytes is refused. - The reference is the `audience_decision` module of wai-rs (feature `audience_decision`); the corpus is `live-conformance/audience/`, and `audience_decision_verify.py` is its second implementation.