@hybridlabor-api/aos 4.13.2 → 4.14.0

package/skills/global_config/plan-canvas/scripts/lib/plan-builder/templates/research/plan.mdx

@@ -0,0 +1,91 @@
+---
+title: Queue choice for Lanternfish exports
+status: draft
+---
+
+# Queue choice for Lanternfish exports
+
+<Callout tone="note" title="How to use this template">
+
+Replace the Lanternfish example with your own question: rewrite the question and constraints, edit the options in Compare and Decision, replace the evidence rows with what you actually measured or read (keep a source per row), and state your own recommendation. Delete sections you do not need. All names and numbers here are invented.
+
+</Callout>
+
+## Question
+
+Lanternfish is a fictional reporting service. Exports of large reports currently run inside the web request and time out for about 4 percent of customers. Which mechanism should run exports in the background?
+
+**Constraints**
+
+- Ship within one quarter with a team of three.
+- No new managed service that needs an on-call rotation.
+- Failed exports must be retried and visible to the customer.
+
+## Options
+
+<Compare beforeLabel="Option A: database-backed queue" afterLabel="Option B: managed message broker">
+<Before>
+
+Jobs live in a table in the existing Postgres database; workers poll with row locks.
+
+- Zero new infrastructure.
+- Throughput tops out around a few hundred jobs per minute.
+- Retries and dead jobs are plain SQL.
+
+</Before>
+<After>
+
+Jobs are published to a hosted broker; workers subscribe.
+
+- Scales far beyond current need.
+- Adds a service, credentials and a monthly bill.
+- Retries and dead letters come from the broker.
+
+</After>
+</Compare>
+
+## Evidence
+
+<Table title="What we found" columns={["Claim", "Source", "Confidence", "Effect on the decision"]} rows={[
+  ["Peak load is 40 exports per minute", "Request log sample, last 30 days", "High", "Both options are fast enough"],
+  ["A table queue handled 300 jobs per minute in a spike test", "Local benchmark, 10 minute run", "Medium", "Option A has 7x headroom"],
+  ["Broker setup needs about 6 engineer days", "Team estimate", "Low", "Option B costs a sprint of the quarter"],
+  ["Managed broker costs about 90 EUR per month", "Vendor price page, invented", "Medium", "Small, but adds a vendor to review"],
+  ["Customers care about progress, not speed", "Five support tickets", "Low", "A status page matters more than the queue"],
+]} />
+
+## Recommendation
+
+<Decision title="Which queue" question="Which mechanism should run Lanternfish exports?" options={[
+  { id: "table", label: "Database-backed queue", detail: "Fits current load with 7x headroom and needs no new service.", recommended: true },
+  { id: "broker", label: "Managed message broker", detail: "Better long-term ceiling, but costs a sprint and a vendor today." },
+]}>
+
+Start with the table queue behind a small interface (`enqueue`, `claim`, `complete`, `fail`). If sustained load passes 150 jobs per minute, swap the implementation for a broker without touching callers.
+
+</Decision>
+
+<Callout tone="warn" title="Risks">
+
+Polling workers can hold row locks too long if a job hangs; set a claim timeout of 10 minutes. The benchmark ran on a laptop, so repeat it on staging before relying on the headroom figure.
+
+</Callout>
+
+## Open questions
+
+<QuestionForm title="Open questions" questions={[
+  { title: "Should failed exports email the customer or only show in the app?", mode: "single", options: [
+    { label: "Show in the app only", recommended: true },
+    { label: "Also send an email" },
+  ] },
+  { title: "How long are finished export files kept?", mode: "single", options: [
+    { label: "7 days", recommended: true },
+    { label: "30 days" },
+  ] },
+]} />
+
+<Checklist title="Before deciding">
+- [ ] Repeat the benchmark on staging
+- [ ] Confirm the 40 per minute peak with last month's logs
+- [ ] Agree the interface for enqueue, claim, complete and fail
+</Checklist>

package/skills/global_config/plan-canvas/scripts/lib/plan-builder/templates/research/standard.md

@@ -0,0 +1,54 @@
+# Queue choice for Lanternfish exports
+
+> Invented example. Replace the question, options, evidence and recommendation with your own.
+
+**Status:** draft
+
+## Question
+
+Lanternfish is a fictional reporting service. Exports of large reports run inside the web request and time out for about 4 percent of customers. Which mechanism should run exports in the background?
+
+**Constraints**
+
+- Ship within one quarter with a team of three.
+- No new managed service that needs an on-call rotation.
+- Failed exports must be retried and visible to the customer.
+
+## Options
+
+| Option | Summary | Upside | Downside |
+|--------|---------|--------|----------|
+| A: database-backed queue | Jobs in a Postgres table, workers poll with row locks | No new infrastructure, retries are plain SQL | Tops out around a few hundred jobs per minute |
+| B: managed message broker | Jobs published to a hosted broker | Scales far beyond current need | New service, credentials and monthly bill |
+
+```mermaid
+flowchart LR
+  Q[Export request] --> A[Option A: table queue]
+  Q --> B[Option B: managed broker]
+  A --> W[Worker]
+  B --> W
+  W --> F[Export file]
+```
+
+## Evidence
+
+| Claim | Source | Confidence | Effect on the decision |
+|-------|--------|------------|------------------------|
+| Peak load is 40 exports per minute | Request log sample, last 30 days | High | Both options are fast enough |
+| A table queue handled 300 jobs per minute in a spike test | Local benchmark, 10 minute run | Medium | Option A has 7x headroom |
+| Broker setup needs about 6 engineer days | Team estimate | Low | Option B costs a sprint of the quarter |
+| Managed broker costs about 90 EUR per month | Vendor price page, invented | Medium | Small, but adds a vendor to review |
+| Customers care about progress, not speed | Five support tickets | Low | A status page matters more than the queue |
+
+## Recommendation
+
+**Option A, the database-backed queue.** It fits current load with 7x headroom and needs no new service. Put it behind a small interface (`enqueue`, `claim`, `complete`, `fail`) and swap in a broker if sustained load passes 150 jobs per minute.
+
+**Risks:** polling workers can hold row locks too long if a job hangs (use a 10 minute claim timeout); the benchmark ran on a laptop and must be repeated on staging.
+
+## Open questions
+
+- [ ] Should failed exports email the customer or only show in the app? (recommended: app only)
+- [ ] How long are finished export files kept? (recommended: 7 days)
+- [ ] Repeat the benchmark on staging
+- [ ] Confirm the 40 per minute peak with last month's logs

package/skills/global_config/plan-canvas/scripts/lib/plan-builder/templates/show-control/canvas.mdx

@@ -0,0 +1,53 @@
+<DesignBoard title="Tidewater Night - stage and rack layout" version={1} transitions={[
+  { from: "foh", to: "rack", label: "fibre, 2 x 1G" },
+  { from: "rack", to: "stage", label: "DMX / sACN, video" },
+  { from: "foh", to: "video", label: "NDI and SDI" },
+  { from: "video", to: "stage", label: "LED wall feed" },
+]}>
+<Section title="1 Layout" subtitle="Low-fidelity plan view. Positions are indicative, not a rigging drawing.">
+<Artboard id="foh" label="FOH position" surface="web" x={60} y={120} width={360} height={260} order={1}>
+<Screen surface="web" caption="Audio desk, lighting console and show laptop.">
+  <FrameScreen>
+    <Title text="Front of house" />
+    <Row>
+      <Box><Text value="Lighting console" weight="bold" /><Lines n={2} widths={[80,50]} /></Box>
+      <Box><Text value="Audio desk" weight="bold" /><Lines n={2} widths={[70,45]} /></Box>
+    </Row>
+    <Box dashed><Text value="Show laptop: timecode master, backup on UPS" tone="muted" /></Box>
+  </FrameScreen>
+</Screen>
+</Artboard>
+<Artboard id="rack" label="Stage-left rack" surface="web" x={520} y={120} width={360} height={260} order={2}>
+<Screen surface="web" caption="Network, DMX and power distribution.">
+  <FrameScreen>
+    <Title text="Rack A (12U)" />
+    <Box><Text value="Switch, VLAN 10 control, VLAN 20 video" /></Box>
+    <Box><Text value="Node 1 universes 1-4, Node 2 universes 5-8" /></Box>
+    <Chips items={[{"label":"UPS 1500 VA","active":true},{"label":"Spare node"}]} />
+  </FrameScreen>
+</Screen>
+</Artboard>
+<Artboard id="video" label="Video position" surface="web" x={60} y={460} width={360} height={240} order={3}>
+<Screen surface="web" caption="Media server and signal conversion.">
+  <FrameScreen>
+    <Title text="Video booth" />
+    <Box><Text value="Media server A (live)" weight="bold" /><Lines n={1} widths={[60]} /></Box>
+    <Box dashed><Text value="Media server B (hot standby, mirrored)" tone="muted" /></Box>
+  </FrameScreen>
+</Screen>
+</Artboard>
+<Artboard id="stage" label="Stage" surface="web" x={520} y={460} width={360} height={240} order={4}>
+<Screen surface="web" caption="Truss, LED wall and floor fixtures.">
+  <FrameScreen>
+    <Title text="Stage" />
+    <Row>
+      <Box><Text value="Truss 1: 12 spots, 8 washes" /></Box>
+      <Box><Text value="LED wall 6 x 3.5 m" /></Box>
+    </Row>
+    <Box dashed><Text value="Floor: 6 strobes, 4 haze units" tone="muted" /></Box>
+  </FrameScreen>
+</Screen>
+</Artboard>
+</Section>
+<Annotation targetId="rack" placement="right" title="Keep DMX runs under 100 m per line, use the spare node if a line fails." />
+</DesignBoard>

package/skills/global_config/plan-canvas/scripts/lib/plan-builder/templates/show-control/meta.json

@@ -0,0 +1 @@
+{"id":"show-control","label":"Show control","description":"Live show technical plan with signal flow, cue list, patch and universe tables, failure plan and load-in checklist, plus a stage and rack layout board.","useWhen":"You plan the lighting, video, audio and network of a live show or event and need one reviewable technical document.","hasBoard":true}

package/skills/global_config/plan-canvas/scripts/lib/plan-builder/templates/show-control/plan.mdx

@@ -0,0 +1,225 @@
+---
+title: Tidewater Night - Show Control Plan
+status: draft
+needs-network: load-in
+needs-lighting: network
+needs-video: network
+needs-audio: network
+needs-programming: lighting, video, audio
+needs-rehearsal: programming
+---
+
+# Tidewater Night: Technical Plan for the Live Show
+
+<Callout tone="note" title="How to use this template">
+
+Replace the show, venue, fixture counts, universes and cues with your own. Keep the signal flow, the patch table, the cue list and the failure plan: crew reads these first. The board in the Canvas section is a rough plan view; redraw it for your stage. All names and numbers below are invented.
+
+</Callout>
+
+## Goal
+
+Run a 75 minute festival headline set with synchronised lighting, LED wall video and a two-person audio team, driven by one timecode source and with a defined fallback for every critical link.
+
+- Show opens on timecode 01:00:00:00 and every cue is repeatable from any song start.
+- A single failure in network, media or console never causes a full blackout.
+- Load-in is done by 14:00, line check by 16:00, doors at 19:00.
+
+## Decision
+
+<Decision title="Who is the timecode master?" question="Which device drives lighting and video cues?" options={[
+  { id: "audio", label: "Audio playback laptop, LTC out", detail: "Band tracks and cues share one clock, musicians can stop the show.", recommended: true },
+  { id: "lighting", label: "Lighting console internal clock", detail: "Simple, but video drifts if the console restarts." },
+  { id: "manual", label: "Manual GO from each operator", detail: "No single point of failure, but cues drift between departments." },
+]}>
+
+LTC from the audio playback laptop is distributed to the console and the media server. Both fall back to their internal clocks if LTC drops, which is on the failure plan.
+
+</Decision>
+
+## Signal flow
+
+<Mermaid label="Control, video and audio signal flow" source={"flowchart LR\n  PB[Audio playback laptop] -- LTC --> CON[Lighting console]\n  PB -- LTC --> MSA[Media server A]\n  PB -- LTC --> MSB[Media server B standby]\n  PB -- audio --> DESK[Audio desk]\n  CON -- sACN u1-8 --> SW[Network switch]\n  SW --> N1[DMX node 1]\n  SW --> N2[DMX node 2]\n  N1 --> TR[Truss fixtures]\n  N2 --> FL[Floor fixtures]\n  MSA -- SDI --> PROC[LED processor]\n  MSB -. SDI standby .-> PROC\n  PROC --> WALL[LED wall]\n  DESK --> PA[PA system]"} />
+
+<Diagram label="Network layout" data={{
+  nodes: [
+    { id: "switch", label: "Core switch, 24 port", description: "Managed 24 port switch, 4 SFP+ uplinks, IGMP snooping on for sACN" },
+    { id: "console", label: "Lighting console, VLAN 10", description: "2.0.10.10 /24, one 1G port to the switch, sACN universes 1-8" },
+    { id: "nodes", label: "DMX nodes 1 and 2, VLAN 10", description: "2.0.10.21 and 2.0.10.22 /24, 4 DMX ports each, ports 3-4 on the switch" },
+    { id: "media", label: "Media servers A and B, VLAN 20", description: "2.0.20.11 and 2.0.20.12 /24, 10G fibre on SFP+ ports 23-24" },
+  ],
+  edges: [
+    { from: "console", to: "switch", label: "1G copper" },
+    { from: "switch", to: "nodes", label: "1G copper" },
+    { from: "media", to: "switch", label: "10G fibre" },
+  ],
+}} />
+
+## Patch and universes
+
+<Table title="Universe map (sACN)" columns={["Universe", "Node / port", "Fixtures", "Channels used", "Position"]} rows={[
+  ["1", "Node 1 / A", "12 moving spots", "384 of 512", "Truss 1"],
+  ["2", "Node 1 / B", "8 LED washes", "280 of 512", "Truss 1"],
+  ["3", "Node 1 / C", "6 strobes", "48 of 512", "Floor"],
+  ["4", "Node 1 / D", "Spare", "0", "Reserve"],
+  ["5", "Node 2 / A", "16 LED battens", "256 of 512", "Back truss"],
+  ["6", "Node 2 / B", "4 haze units, 2 fans", "24 of 512", "Floor"],
+  ["7-8", "Node 2 / C-D", "Pixel tape, 300 pixels", "900 of 1024", "Wall surround"],
+]} />
+
+<DataModel entities={[
+  { name: "Fixture", fields: [
+    { name: "fixtureId", type: "int", note: "Console fixture number, unique" },
+    { name: "type", type: "string", note: "Spot, wash, strobe, batten, pixel" },
+    { name: "universe", type: "int", note: "sACN universe 1 to 8" },
+    { name: "address", type: "int", note: "DMX start address 1 to 512" },
+    { name: "mode", type: "string", note: "Personality, for example 24 channel" },
+  ] },
+  { name: "Cue", fields: [
+    { name: "cueNumber", type: "decimal", note: "Console cue, for example 12.5" },
+    { name: "timecode", type: "string", note: "HH:MM:SS:FF" },
+    { name: "department", type: "enum", note: "light, video, audio, fx" },
+  ] },
+]} />
+
+## Cue list
+
+<Table title="Show cues (excerpt)" columns={["Cue", "Timecode", "Song / moment", "Lighting", "Video", "FX"]} rows={[
+  ["1", "01:00:00:00", "Intro tape", "Blackout then slow blue fade", "Wall: opening loop", "Haze on"],
+  ["10", "01:03:20:00", "Song 1 downbeat", "Full wash, spot chase", "Wall: live camera mix", "None"],
+  ["24", "01:18:45:12", "Song 4 drop", "Strobe burst 3 s", "Wall: white flash, then pattern", "CO2 jets"],
+  ["38", "01:41:10:00", "Ballad", "Warm amber, two followspots", "Wall: slow footage", "None"],
+  ["52", "02:02:00:00", "Encore break", "House half, wash low", "Wall: countdown", "Haze off"],
+  ["60", "02:15:00:00", "Closing", "Slow fade to black", "Wall: logo, then black", "None"],
+]} />
+
+## Build map
+
+### Load-in and rigging {#load-in}
+
+<Checklist title="Load-in checklist" items={[
+  { label: "Truss hung, motors tested, safety signed off" },
+  { label: "Power distribution tested, earth and RCD checked" },
+  { label: "Rack A powered, UPS holding for 10 minutes" },
+  { label: "LED wall built, tiles counted and addressed" },
+  { label: "FOH cabling labelled and strain relieved" },
+]} />
+
+<ImplementationMap files={[
+  { path: "venue/power-plan.pdf", change: "added", note: "Distribution and phase balance" },
+  { path: "venue/rigging-plan.pdf", change: "added", note: "Truss and motor loads" },
+]} />
+
+### Network {#network}
+
+<Checklist title="Network tasks" items={[
+  { label: "VLAN 10 control and VLAN 20 video configured" },
+  { label: "Static addresses assigned and labelled on every device" },
+  { label: "sACN multicast limited to VLAN 10" },
+  { label: "Ping and bandwidth test between FOH and Rack A" },
+]} />
+
+<ImplementationMap files={[
+  { path: "network/address-plan.csv", change: "added", note: "Device, address, VLAN, port" },
+  { path: "network/switch-config.txt", change: "added", note: "VLAN and multicast settings" },
+]} />
+
+### Lighting {#lighting}
+
+<Checklist title="Lighting tasks" items={[
+  { label: "Patch fixtures to universes 1 to 8" },
+  { label: "Focus and colour check on every truss position" },
+  { label: "Program looks for all songs" },
+]} />
+
+<ImplementationMap files={[
+  { path: "lighting/show-file-v3.show", change: "modified", note: "Patch, groups, palettes and cues" },
+]} />
+
+### Video {#video}
+
+<Checklist title="Video tasks" items={[
+  { label: "Map LED wall to the media server canvas" },
+  { label: "Load content and verify frame rate at 50 fps" },
+  { label: "Mirror media server A to B and test the switch" },
+]} />
+
+<ImplementationMap files={[
+  { path: "video/wall-map.json", change: "added", note: "Tile layout and processor settings" },
+  { path: "video/content/", change: "added", note: "Loops and song visuals, ProRes" },
+]} />
+
+### Audio and timecode {#audio}
+
+<Checklist title="Audio tasks" items={[
+  { label: "Playback laptop outputs LTC on channel 8" },
+  { label: "Line check every input and monitor mix" },
+  { label: "Verify LTC arrives at console and both media servers" },
+]} />
+
+<ImplementationMap files={[
+  { path: "audio/stage-plot.pdf", change: "added", note: "Inputs, monitors and stage layout" },
+  { path: "audio/playback-session.als", change: "added", note: "Tracks and LTC lane" },
+]} />
+
+### Programming and sync {#programming}
+
+<Checklist title="Programming tasks" items={[
+  { label: "Import the cue list and attach timecode events" },
+  { label: "Run each song from the middle and from the start" },
+  { label: "Write the operator cheat sheet" },
+]} />
+
+<ImplementationMap files={[
+  { path: "show/cue-list.csv", change: "added", note: "Single source for all departments" },
+  { path: "show/operator-notes.md", change: "added", note: "GO buttons, hold points and fallbacks" },
+]} />
+
+### Rehearsal and doors {#rehearsal}
+
+<Checklist title="Rehearsal tasks" items={[
+  { label: "Full run with the band at 16:00" },
+  { label: "Failure drills: pull LTC, pull media server A, pull a DMX node" },
+  { label: "Final go from the production manager at 18:30" },
+]} />
+
+## Agent trail
+
+<AgentTrail />
+
+## Failure and blackout plan
+
+<Table title="Failure modes and responses" columns={["Failure", "Detected by", "Immediate response", "Recovery"]} rows={[
+  ["LTC lost", "Console timecode lamp, media server clock", "Both switch to internal clock, operators GO manually", "Re-sync at the next song start"],
+  ["Media server A fails", "Wall black or frozen", "Video operator flips to server B on the processor", "Reboot A, keep B live for the set"],
+  ["DMX node 1 fails", "Truss fixtures freeze", "Console outputs to spare node on universe 4 port", "Replace node during the next break"],
+  ["Network switch fails", "All sACN lost, fixtures hold last look", "Swap to the spare switch, config is on USB", "Verify addresses, resume"],
+  ["Power loss on stage", "Lights and wall dark", "Audio on UPS keeps playback, house lights on emergency circuit", "Hold the show until power is confirmed"],
+  ["Emergency stop", "Production manager call", "Console blackout, haze and CO2 off, house lights up", "No restart without a safety sign-off"],
+]} />
+
+<Callout tone="warning" title="Blackout rule">
+
+A deliberate blackout is a console cue (cue 1 and cue 60) and never a power switch. If any department calls "stop", all effects (strobe, CO2, haze) go off first, then lights fade to house. Only the production manager restarts the show.
+
+</Callout>
+
+## Risks
+
+<Table title="Risk register" columns={["Risk", "Likelihood", "Impact", "Mitigation"]} rows={[
+  ["Wireless interference from the neighbouring stage", "Medium", "High", "Frequency coordination, wired backups for key mics"],
+  ["Strobe bursts exceed the venue photosensitivity limit", "Low", "High", "Cap at 3 Hz, warning signs, approval in the safety plan"],
+  ["Rain reaches the front of house", "Medium", "Medium", "Covered FOH tent, cable ramps, tarp for the rack"],
+  ["Content delivered late", "Medium", "Medium", "Delivery deadline two days before, placeholder loops loaded"],
+]} />
+
+## Open questions
+
+<QuestionForm title="Open Questions" questions={[
+  { title: "Do we run followspots from FOH or a side tower?", mode: "single", options: [
+    { label: "Side tower", recommended: true }, { label: "FOH" } ] },
+  { title: "Is a second haze unit allowed by the venue?", mode: "single", options: [
+    { label: "Yes, with smoke detector isolation", recommended: true }, { label: "No, one unit only" } ] },
+  { title: "Which extras do we want?", mode: "multi", options: [
+    { label: "Audience-facing blinders" }, { label: "Live camera on the wall" }, { label: "Wireless DMX backup" } ] },
+]} />

package/skills/global_config/plan-canvas/scripts/lib/plan-builder/templates/show-control/standard.md

@@ -0,0 +1,111 @@
+# Tidewater Night: Technical Plan for the Live Show
+
+> Template guidance: replace the invented show, venue, fixture counts, universes and cues. Keep the signal flow, patch table, cue list and failure plan. All names and numbers are invented.
+
+**Status:** draft
+
+## Goal
+
+Run a 75 minute festival headline set with synchronised lighting, LED wall video and a two-person audio team, driven by one timecode source and with a defined fallback for every critical link.
+
+- Show opens on timecode 01:00:00:00 and every cue is repeatable from any song start.
+- A single failure in network, media or console never causes a full blackout.
+- Load-in is done by 14:00, line check by 16:00, doors at 19:00.
+
+## Decision
+
+| Question | Options | Recommendation | Why |
+|---|---|---|---|
+| Who is the timecode master? | Audio playback laptop (LTC) / console clock / manual GO | **Audio playback laptop, LTC out** | One clock for band tracks and cues; console and media server fall back to internal clocks if LTC drops |
+
+## Signal flow
+
+```mermaid
+flowchart LR
+  PB[Audio playback laptop] -- LTC --> CON[Lighting console]
+  PB -- LTC --> MSA[Media server A]
+  PB -- LTC --> MSB[Media server B standby]
+  PB -- audio --> DESK[Audio desk]
+  CON -- sACN u1-8 --> SW[Network switch]
+  SW --> N1[DMX node 1]
+  SW --> N2[DMX node 2]
+  N1 --> TR[Truss fixtures]
+  N2 --> FL[Floor fixtures]
+  MSA -- SDI --> PROC[LED processor]
+  MSB -. SDI standby .-> PROC
+  PROC --> WALL[LED wall]
+  DESK --> PA[PA system]
+```
+
+## Patch and universes
+
+| Universe | Node / port | Fixtures | Channels used | Position |
+|---|---|---|---|---|
+| 1 | Node 1 / A | 12 moving spots | 384 of 512 | Truss 1 |
+| 2 | Node 1 / B | 8 LED washes | 280 of 512 | Truss 1 |
+| 3 | Node 1 / C | 6 strobes | 48 of 512 | Floor |
+| 4 | Node 1 / D | Spare | 0 | Reserve |
+| 5 | Node 2 / A | 16 LED battens | 256 of 512 | Back truss |
+| 6 | Node 2 / B | 4 haze units, 2 fans | 24 of 512 | Floor |
+| 7-8 | Node 2 / C-D | Pixel tape, 300 pixels | 900 of 1024 | Wall surround |
+
+## Cue list (excerpt)
+
+| Cue | Timecode | Song / moment | Lighting | Video | FX |
+|---|---|---|---|---|---|
+| 1 | 01:00:00:00 | Intro tape | Blackout then slow blue fade | Wall: opening loop | Haze on |
+| 10 | 01:03:20:00 | Song 1 downbeat | Full wash, spot chase | Wall: live camera mix | None |
+| 24 | 01:18:45:12 | Song 4 drop | Strobe burst 3 s | Wall: white flash, then pattern | CO2 jets |
+| 38 | 01:41:10:00 | Ballad | Warm amber, two followspots | Wall: slow footage | None |
+| 52 | 02:02:00:00 | Encore break | House half, wash low | Wall: countdown | Haze off |
+| 60 | 02:15:00:00 | Closing | Slow fade to black | Wall: logo, then black | None |
+
+## Stage and rack layout
+
+- **FOH:** lighting console, audio desk, show laptop (timecode master) on UPS.
+- **Rack A, stage left:** switch (VLAN 10 control, VLAN 20 video), DMX nodes 1 and 2, spare node, UPS.
+- **Video booth:** media server A live, media server B hot standby.
+- **Stage:** Truss 1 with 12 spots and 8 washes, LED wall 6 x 3.5 m, floor strobes and haze.
+- Keep DMX runs under 100 m per line; use the spare node if a line fails.
+
+## Load-in checklist
+
+- [ ] Truss hung, motors tested, safety signed off
+- [ ] Power distribution tested, earth and RCD checked
+- [ ] Rack A powered, UPS holding for 10 minutes
+- [ ] LED wall built, tiles counted and addressed
+- [ ] FOH cabling labelled and strain relieved
+- [ ] VLANs configured, static addresses labelled, sACN multicast limited to VLAN 10
+- [ ] Fixtures patched to universes 1 to 8, focus and colour check done
+- [ ] LED wall mapped, content at 50 fps, media server A mirrored to B
+- [ ] LTC verified at console and both media servers
+- [ ] Failure drills run: pull LTC, media server A, DMX node
+- [ ] Final go from the production manager at 18:30
+
+## Failure and blackout plan
+
+| Failure | Detected by | Immediate response | Recovery |
+|---|---|---|---|
+| LTC lost | Console timecode lamp, media server clock | Both switch to internal clock, operators GO manually | Re-sync at the next song start |
+| Media server A fails | Wall black or frozen | Video operator flips to server B on the processor | Reboot A, keep B live for the set |
+| DMX node 1 fails | Truss fixtures freeze | Console outputs to spare node | Replace node during the next break |
+| Network switch fails | All sACN lost, fixtures hold last look | Swap to the spare switch, config on USB | Verify addresses, resume |
+| Power loss on stage | Lights and wall dark | Audio on UPS keeps playback, house lights on emergency circuit | Hold the show until power is confirmed |
+| Emergency stop | Production manager call | Console blackout, haze and CO2 off, house lights up | No restart without a safety sign-off |
+
+**Blackout rule:** a deliberate blackout is a console cue (cue 1 and cue 60), never a power switch. On "stop", effects go off first, then lights fade to house. Only the production manager restarts the show.
+
+## Risks
+
+| Risk | Likelihood | Impact | Mitigation |
+|---|---|---|---|
+| Wireless interference from the neighbouring stage | Medium | High | Frequency coordination, wired backups for key mics |
+| Strobe bursts exceed the venue photosensitivity limit | Low | High | Cap at 3 Hz, warning signs, approval in the safety plan |
+| Rain reaches the front of house | Medium | Medium | Covered FOH tent, cable ramps, tarp for the rack |
+| Content delivered late | Medium | Medium | Delivery deadline two days before, placeholder loops loaded |
+
+## Open questions
+
+- Followspots from FOH or a side tower? Side tower (recommended) / FOH
+- Second haze unit allowed by the venue? Yes with smoke detector isolation (recommended) / no
+- Extras? Audience blinders / live camera on the wall / wireless DMX backup