//Production Plan

POI Podcast — Production Plan (v1)

Drafted: 2026-05-29 (s373) from Ryan B's questionnaire answers + the 9-dimension research brief. This is the working plan — decisions that are locked, my recommendations on the open ones, and the end-to-end workflow.

1. The Show's Angle (the part that makes it yours)

The strongest thing in your answers is the host dynamic, so the whole show is built on it:

Ryan C is the AI doomer. Ryan B is the grounded builder. You watch a 2011–2016 show that dramatized — years early — the exact fight you two are having about 2026 AI: a benevolent, constrained machine vs. an unconstrained one that "optimizes" humanity by controlling it.

That gives a double-guide dynamic that powers every episode:

  • Ryan C guides Ryan B through the show (he's the veteran; Ryan B has never seen it).
  • Ryan B guides Ryan C through the reality (Ryan B works with AI daily; Ryan C fears it).

Each episode the fiction tees up a fear → Ryan B grounds it in how AI actually works in 2026 → and sometimes the show turns out to be more right than comfortable. That tension is the engine, the running gag, and the reason a general audience (not just POI fans) tunes in.

Host roles / angles to try (you asked)

  • The Sherpa & The Skeptic-of-the-Skeptic — Ryan C leads on lore; Ryan B leads on "here's what's real."
  • Doomer vs. Builder — explicit framing; the show is the referee.
  • "He's seen the future, I've built it" — Ryan C knows where the plot goes; Ryan B knows where the tech actually went.
  • Recurring bit: a lighthearted "P(doom) check" at the end — Ryan C states how scared this episode made him (0–100%); Ryan B adjusts it with facts. Ties the running gag to a repeatable, clip-able segment without forcing a rigid format.

2. Naming (no "POI" in the title — about the two of you, inspired by the show)

Mined from the show's concepts (the Machine, surveillance, "relevant vs. irrelevant numbers," being watched, prediction) and your doomer/builder dynamic. Top picks first:

Name Why it works
P(doom) AI-insider term for "probability of doom." Is your dynamic (Ryan C's fear vs. Ryan B's grounding), insider-cool, short, brandable, zero IP risk. My #1.
Threat Model Double meaning: AI-safety term and the show's premise. Sounds like a real show.
Relevant / The Irrelevant Straight from the show's core idea (who the Machine deems worth saving). Brandable, no IP name.
The Machine Room Evokes the show + "two guys in a room." Warm, ownable.
Acceptable Use AI policy term, wry, on-theme.
Garbage In "Garbage in, garbage out" — funny, about AI + about two guys riffing.
Can You Hear Me? The Machine's line to Root. Cryptic, memorable (slightly inside-baseball).

Recommendation: P(doom) or Threat Model as the brand, with a tagline that names the show, e.g. "P(doom): two friends, one afraid of AI, one building it — re-watching the show that called it." (SEO comes from the description/tags, not the title.) Pick one and the domain + channel + tracker all key off it.

3. Locked Decisions (from your answers)

Area Decision
Episode scope Pending Ryan C — you lean curated (~50). Hedge below.
Cadence Start bi-weekly, move to weekly if the workflow holds.
Length 30–90 min, target 60.
Prep budget ~3–4 hrs/host/episode.
Recording Start in-person at the studio (build the vibe); ~50/50 long-term.
Live? Record-then-publish; occasional live once established.
Editor Ryan B owns final cut.
Post ceiling 2–3 hrs/ep now → 1–2 hrs as it tightens.
Automation Maximize.
Clips Several short-form/episode, soundbite-targeted (primary growth lever).
Show clips Fair-use show-and-keep (OK with Content ID claims).
Money No ads if avoidable; open to Patreon/sponsorship; not the motive.
Channels YouTube + Apple + Spotify + Shorts/Reels. No TikTok.
Transcripts Full, auto only (no human edit).
Tracker Custom, both edit, simple auth, must survive the home server being down.
Quality 1080p–2K, no 4K.
Budgets Software ~$50 (up to $100); gear solid→pro.

The 103-vs-50 hedge (your idea — it's a good one)

Start at S1E1, but cover multiple episodes per podcast when the AI narrative is thin (the early procedural run) and slow to one-episode-per-show when it gets rich (S3–S5). This naturally compresses the ~2-year commitment toward ~10–12 months and front-loads the AI-discussion density that your audience is here for. Final call waits on Ryan C's input.

4. The Production Pipeline (record → publish, low-touch)

Designed around your constraints: fast/easy/max-quality, ≤2–3 hr post (→1–2), automate the handoffs, several clips, full auto transcripts.

RECORD                 EDIT (Descript)            DISTRIBUTE
─────────              ─────────────────          ──────────
In-person:             • Studio Sound (denoise)   • YouTube (video, w/ clips)
 each host own track   • filler-word removal      • Apple + Spotify (audio,
 + a camera each       • Auto multicam            •   via Transistor RSS)
 (1080p–2K)            • Eye-contact (remote)      • Spotify video (separate)
                       • auto transcript →         • Shorts/Reels from clips
Remote (later):          chapters + captions
 Riverside/Descript    • OpusClip → several        AUTOMATE THE HANDOFFS:
 Rooms (local tracks)    soundbite shorts          script export → host/YT

Editor = Descript (Creator plan, ~$24/mo). It is the single best fit for "fast + easy + max quality without burning time," and your A/V background means you'll fly in it. It does denoise, filler removal, automatic multicam (so you do not need a hardware switcher — just record each camera separately and let Descript cut between them), captions, and full auto transcripts. Optional DaVinci finishing later if you want more polish, but default to Descript-only to protect the time budget.

Clips = OpusClip (~$15–29/mo) or Descript's own clip feature — feed the episode, get several auto-captioned, soundbite-targeted verticals. This is the growth engine, so we lean in.

Automation (your "automate as much as possible"): a watch-folder script on your infra that, on a finished export, (1) pushes the audio to the podcast host's API, (2) kicks OpusClip via API, (3) drops the YouTube upload via the YouTube Data API with title/description/chapters from the transcript. This is squarely in your wheelhouse and is the difference between 2–3 hr and 1–2 hr post.

Software budget check (~$50/mo target): Descript Creator $24 + OpusClip ~$15 + Transistor $19 ≈ $58/mo. Trim by using Descript's built-in clips instead of OpusClip to land ~$43/mo. Comfortably under your $100 ceiling.

5. Show Clips — capture, and the tradeoffs (you asked about both)

How do we capture clips?

The clean answer: own the source and rip it. - The Person of Interest complete-series Blu-ray/DVD box set is cheap (~$30–60). Rip with MakeMKV (free), pull the exact clip in Descript/DaVinci. No DRM fights, broadcast-quality source, and you legally own a copy. - Streaming capture (Prime, etc.) is unreliable — DRM/HDCP usually yields black frames on screen recordings, and a capture card needs an HDCP stripper. Don't fight it; the discs are easier and better. (You can still watch on Prime; just pull clips from the discs.) - You'll also want to watch the same way so you're discussing the same cut — decide Prime vs. discs with Ryan C, but capture from discs either way.

Tradeoffs of show-and-keep (so you go in eyes-open)

  • Content ID is automated and does not evaluate fair use. Warner/CBS will likely auto-claim clip-containing videos. A claim ≠ a strike:
  • Claim → typically the video stays up; ad revenue (if any) routes to the owner. You're fine with that.
  • Risk to watch: in rare cases a claim can block the video in some regions; and 3 copyright strikes in 90 days deletes the channel. Claims are common and benign; strikes are the real danger.
  • Keep the risk low even while showing clips: short clips (seconds, not whole scenes), always talk over/around them (transformative commentary), cluster discussion tightly around each clip, don't replay full sequences. Fair use is a defense, strongest when the use is clearly commentary — so the format should make the commentary obviously load-bearing.
  • Two-track output: put clips in the YouTube cut; keep the audio RSS (Apple/Spotify) clip-free (describe instead). The automated pipeline will produce both from one Descript project. This minimizes exposure on the audio platforms and is cleaner for listeners anyway.
  • Licensing: worth a low-priority inquiry to WB for a fixed-fee clip license, but don't block launch on it. Only becomes urgent if a channel actually gets struck down.

6. Equipment Plan (solid→pro, 1080p–2K, using what you have)

You already have: Rode music vocal mics, Focusrite Scarlett + PreSonus 32R + portable mixers (plenty of A/D), a somewhat-deadened room, a Logitech webcam, workable lighting.

Recommended buys: - Mics: music vocal mics pick up room; for spoken-word in a lightly-treated room use dynamic broadcast mics — 2× Shure SM7dB (pro) or 2× Rode PodMic (solid, ~$99 ea). Run into your PreSonus/Scarlett, or consider a RODECaster Pro II (~$700) as an all-in-one that records separate tracks, adds sound pads, and cuts recording friction — strong fit for in-person + your music background. Biggest single quality upgrade for spoken word. - Cameras (1080p–2K, 2 angles for auto-multicam): - Solid: 2× Logitech Brio / Opal webcams — simplest, no capture cards. - Pro: 2× mirrorless (Sony ZV-E10 ~$700) + Elgato Cam Link each — better image, more setup. Optionally a phone as a free third wide shot. - No switcher needed — Descript auto-multicam handles cutting in post. - Lighting: add 2× Elgato Key Light (or softboxes) to your existing kit. - Storage: none yet — 1080p–2K multicam ≈ 10–30 GB/hr. Start with a 2–4 TB external SSD; graduate to a NAS on your infra for the archive.

7. Publishing & Distribution

  • YouTube: brand-new channel (video home, where clips live).
  • Audio host: Transistor (recommended — clean, great analytics, multi-show, video-podcast support maturing) or Buzzsprout if you want the simplest UX. This generates the RSS that feeds Apple Podcasts + Spotify.
  • Spotify video: upload separately (or via host once their push is live).
  • Short-form: YouTube Shorts + Instagram Reels from the OpusClip outputs.
  • No TikTok (your call; also dodges the US regulatory uncertainty).
  • Cadence: bank a small buffer (2–3 episodes) before launch — the algorithms reward consistency and it protects you on busy weeks.
  • Transcripts: Descript auto-transcript → chapters in the YouTube description
  • full transcript published on the show page (no human edit, per your call).

8. Shareable Project Tracker (survives the home server being down)

Your requirement — "Mason offline is a must" — means the tracker cannot live on the spine. Architecture:

  • Cloudflare Pages (static PWA frontend) + Cloudflare Workers + D1 (data)
  • a simple shared-auth layer (password or Cloudflare Access). Fully independent of the home server — it's up even when the home box is down. Both you and Ryan C can edit. iPhone-installable (add-to-home-screen PWA).
  • True offline editing isn't required (you confirmed) — so we skip the complex sync layer; online-to-save is fine.
  • Groundwork reuse: the Discord/connector patterns from the an internal app and the questionnaire page give us reusable UI + data-shape patterns, but the hosting is Cloudflare, not the spine (that's what buys the "works when the home server is down" guarantee).
  • Cost: Cloudflare free tier covers this; domain ~$10–12/yr (Cloudflare Registrar, at-cost). Your $20/yr budget is plenty.
  • Domain: brainstorm alongside the show name (keep them aligned; nothing that reveals your surname/business/existing domains). e.g. if the show is P(doom) → pdoom.fm / pdoompod.com; if Threat Model → threatmodel.fm.

Note: this questionnaire page (/poi) was the fast intake tool and does rely on the spine. The Cloudflare tracker above is the durable, self-host-independent home — a Phase-3 build.

9. Community

Discord server seeded from r/PersonOfInterest, with automated moderation (Discord AutoMod + a bot, reusing our Discord patterns) plus organic host presence. Doubles as a source of listener questions for a recurring segment.

10. Phase Plan & Todos

Phase 1 — Decisions (now) - [ ] Ryan C's input on scope (full 103 vs curated ~50 + multi-ep hedge) - [ ] Pick the show name (→ drives domain, channel, tracker branding) - [ ] Confirm watch source + buy the Blu-ray/DVD box set for clip capture

Phase 2 — Production design / buy - [ ] Mics (PodMic ×2 or SM7dB ×2; consider RODECaster Pro II) - [ ] Cameras ×2 (Brio solid / ZV-E10 pro) + lighting + storage SSD - [ ] Stand up Descript Creator + OpusClip; build the record→export template - [ ] Script the export→host/YouTube/clip automation

Phase 3 — Shareable tracker - [ ] Register domain; Cloudflare Pages + Workers/D1 + simple auth; PWA; both edit

Phase 4 — Pilot - [ ] Record S1E1 in-person; run the full automated pipeline once end-to-end; measure real post-production time vs. the 2–3 hr target

Phase 5 — Launch - [ ] Channel art/branding; bank 2–3 episode buffer; Discord; go live; clips engine

Open items needing Ryan B/Ryan C

  1. Scope — waiting on Ryan C.
  2. Show name — pick from §2 (my rec: P(doom) or Threat Model).
  3. Watch/capture source — confirm; buy the box set regardless for clips.
  4. Gear tier within solid→pro — confirm the RODECaster + camera choice.