UTC canonical vs local experience

The unit is UTC, but 'primetime', 'morning', and 'lunch' are LOCAL experiences (8pm local everywhere). Comparing behavior at the same UTC slot is not the same as at the same local hour — the core temporal-interop tension, and the direct analog of geo's requested-vs-executed geography.

Class

Case to account for

Affects

2 conversions

Detection

A cross-zone comparison holds the UTC slot fixed while the intent is a local hour (or vice versa).

Mitigation

Store the canonical UTC slot plus a declared local annotation; compare local experience via local slots, join in UTC.

Affected conversions

Daypart (local band) ⇄ UTC slot-set

OPEN

semantics

OPEN