Calendar
Every date carries a day type and inherits that type’s template across all five dayparts — templates are editable from any date’s day view. Give dates friendly names, override any daypart for a specific date, and move between month, week, and day. Edits happen in the day view, in edit mode.
Mood library — the palette
The moods the daily show is assembled from — each one a board: schema, creative intent, and storyboard imagery. The Regular day-type template is one walk through this library — the calendar inherits it; the Creative Advisor's daily-show assembly is exactly this selection. In edit mode every card can be rewritten, and new moods join the palette.
Event day types swap their own moods in from Afternoon onward and inherit this library through Morning. Each recipe strip shows who owns the mood's thirty minutes.
Anatomy of a mood
A mood is a 30:00 looping program. The carrier bed holds the room; interstitial slots hand moments to other buckets; overlays strike from above on event nights and recede. Press play to watch a loop — recipe edits redraw it live.
Creative intent
What Works
What Doesn't
Storyboard & inspiration
— the 30:00 loop
The rundown
Why the minutes matter
Bucket minutes are the inventory. The rundown is the timed order of the mood's thirty minutes: who owns which moments, and how much of the room's attention each governing body is granted. Change the rundown and the mood changes character — the loop structure stays the same.
Sponsor minutes per loop, times loops per night, is Corporate Partnerships' sellable number. Wayfinding minutes are JLL's guarantee that guests are never lost. The carrier bed is Entertainment's — the district's own voice.
Inside a bucket — where slot content comes from
Corporate Partnerships bucket — one owner, one pipeline
- Sponsor spot A — :60, approved 8/12
- Sponsor spot B — :60, approved 8/19
- Sponsor spot C — :60, approved 8/22
- Partner sting D — :30, approved 8/25
- Sponsor spot E — :60, in intake. Not eligible.
A bucket is a pool of intake-approved content with a single responsible governing body accountable for it (SOP 5.8). Each slot in the loop pulls from its bucket per the content's behavior.
Rotational — the slot draws the next item in the pool each loop: spot A, then B, then C. One :60 slot across ten evening loops rotates the whole pool nightly.
Scheduled — an item pins to dates and dayparts: a partner's opening week takes every sponsor slot that week.
Accountability sits with the governing body until technical approval, and with the ROC after. Spot E is in intake — visible to its owner, invisible to the loop.
Mood × Tech
How a mood lands on the hardware — every display, light, and speaker, and the content type that occupies it. The mood defines the tech use; ownership lives upstream in the recipe, so there is no bucket column here. Night Garden ships fully drawn; other moods show generated summaries until you make them editable.
Ownership sits upstream: buckets and their governing bodies live in the mood’s recipe, not this table. Kiosk face display IDs pend spec v0.6; tenant and private zones never appear; interior venues run nested venue moods with the district mood governing thresholds.
Mechanics & registers
The rules underneath the arc, and the reference tables the moods are built on. This layer edits through the SOP suite, not here.
Mood mechanics — six rules
1. The loop. A mood is a 30:00 looping program. Loops start on :00 and :30 — the district heartbeat — so concurrent moods stay phase-locked and the schedule is human-legible.
2. Buckets. A mood is assembled from buckets: containers of media content, each owned by one responsible governing body. Only intake-approved bucket content is eligible.
3. Inventory. Each mood's rundown allocates its thirty minutes across buckets. Sponsor minutes per loop, times loops per day, is Corporate Partnerships' sellable number.
4. Overlays. The base loop is timecode-locked and never stops. Goal Moment composites over it for 45–60 seconds and recedes; the Game-Day Skin is additive from Afternoon on.
5. Protection. Protection is bucket permissions. Candlelight is defined by the buckets barred from it, and runs concurrently beside any event-night mood for its audience.
6. Boundaries. Daypart transitions fire on the astronomical and operational clock at the next content seam inside the loop. Hard cuts are reserved for safety messaging and Goal Moment.
Bucket registry — one owner per bucket (SOP 5.8)
Proposed to double as the SOP 5.8.3 designation table — bucket ownership is the per-program owner mapping that subsection holds a placeholder for.
Audience key
Solar reference — Anaheim, and the loop math
Loops at 30:00 — Dawn 8, Morning 6, Afternoon 3.5–10, Dusk 3, Evening 5–12, the seasonal columns breathing while the sequence holds. Boundaries resolve daily on the CueServer and Q-SYS astronomical clock.
Basis documents & open items
Basis. Burton concept plan overlay (092425 source, sheet dated 9/17/25) — all layers register 1:1. Audio zones revision 8/30/26; displays layer 8/30/26; building areas 8/30/26. Content spec Preliminary v0.5 (v0.6 pending). ROC SOP v1.8, section 5.8 accountability model.
Open. Bucket registry as the 5.8.3 designation table — confirm with OCVIBE. Loop transition rule at daypart boundaries — next-content-seam default proposed. Scent: controlled program or adjacency only. Kiosk-face display IDs ride on spec v0.6; Kiosk 1's facing direction. Zone 1's feed; Spatial zones as one canvas or discrete scenes; the General-zone control surface; the Waterfall's visibility from grade.