Skip to content

[P0] Backup video — script + recording for booth network failures #8

@ausbru87

Description

@ausbru87

Wi-Fi at booth events is famously unreliable. We need a 3–5 minute pre-recorded video of the full demo to fall back on if Coder is unreachable mid-presentation.

Depends on: end-to-end validation pass (issue for that one).

Two parts

Part A — author the recording script (`docs/backup-video-script.md`)

A literal script — what's said on screen, what's clicked, what should be visible:

  • 0:00–0:30 — Hook: "This is a Coder workspace running on a Coder + Red Hat OpenShift cluster. Everything you'll see is governed end-to-end — every model call, every workspace egress."
  • 0:30–1:30 — Act 1: open issue with sprint-ticket label → workspace appears (warm-pool claim) → presenter narrates while Coder UI loads
  • 1:30–3:30 — Act 2: paste TASK.md prompt into Coder Tasks → agent reads, runs make test, fails, edits verifier.go, retries, passes → diff visible
  • 3:30–4:30 — Show governance: Grafana Agent Boundaries dashboard with every egress logged, AI Gateway audit line per model call
  • 4:30–5:00 — Outro: "Two-tier audit, on-prem-portable, RH-supported — the whole stack lands on any OpenShift cluster."

Part B — record + store

  • Record using QuickTime (macOS) or OBS — full screen, 1080p, 30fps
  • Mic on, ambient noise low
  • Save as `booth-backup-2026-MM-DD.mp4` (date the recording)
  • Store in Google Drive at `Shared drives/Marketing Material Masters/Events/26Q2EV_Red_Hat_Summit_MAY11/booth-backup-video/` — NOT in this repo (file too big, plus video isn't source-controlled material)
  • Also copy to a USB stick the booth presenter carries

Acceptance criteria

  • `docs/backup-video-script.md` committed with the literal script
  • Video recorded against a real cluster + sample-repo flow (not a mock)
  • Video uploaded to Drive + USB
  • `docs/booth-runbook.md` recovery playbook references the Drive path + USB drawer location

Style notes

  • Don't narrate the architecture in the video — the audience can read those docs. Narrate what's happening on screen and what each governance event means in plain English.
  • Mention specific things visitors at the booth ask about: "this fixed test was a deliberate bug", "the agent's egress was firewalled", "every model call hit AI Gateway with the user's identity".

Production niceties (P1, optional)

  • Add subtitles (Otter, descript, or YouTube auto-captions)
  • Add a "Coder + Red Hat" lower-third overlay

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-docsDocumentation workdemoBooth demo contentp0Booth-blocking — must ship before May 11 2026pre-boothTracked for the May 11 booth windowrhsummit-2026Red Hat Summit 2026 demo asset

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions