Showrunner · YouTube production for GoUltra AI · Stage B

The whole app, page by page — in the locked Family style

You picked Direction A · Family; it's now distilled into one shared stylesheet (see the locked style guide). Every screen below tells one continuous story: the same episodes, the same team — Deven directing, Priya and Arjun producing — on Jul 13, 2026. Click through in order, or wander.

Start here — the Director's board
1Pipeline boardAll 9 stages

Every video as a card moving across Idea → Published: 4 ideas in the inbox, EP-016 in research, EP-014 mid-production, EP-013 waiting on your final-cut approval, EP-012 publishing Thursday. Gate chips mark what needs the Director.

Open the board
The Director flow — follow the pipeline left to righteach page shows a different episode at that stage · Brief isn’t a separate page — it’s edited on the video page (EP-014 shows its locked output)
2ResearchEP-016

The AI research workspace: web-research runs and pasted material become a cited digest, three candidate angles, open questions — refined by chatting with it.

Open
3Script workbenchEP-015

Prose drafting with an AI conversation beside it: versioned drafts, pace estimate, inline verify-flags — ending at "Lock script & break down".

Open
4Direction — segment editorEP-014

The locked script broken into 13 segments grouped into 7 clip tasks — narration, visual type, direction notes — and Gate 1: "Approve & hand off to production".

Open
5Video detailEP-014 · Production

The spine page you saw in Stage A, now on the shared stylesheet: full pipeline rail with both gates, locked brief, the 7 clip tasks, activity, team.

Open
6Assembly reviewEP-013

Cut v1 in the player, version rail, the review thread — and Gate 2: "Approve final cut", with its checklist (captions still pending).

Open
7Publish packageEP-012

Title options, description & chapters derived from segments, tags, thumbnail candidates, and the publish checklist — manual publish in v1, API later.

Open
The Producer seatsthe same app from the team's side
8Clip task sheetPriya · Clip 4

A producer's task: what the clip needs, the copy-ready Seedance generation package, upload dropzone, comments — plus what Avatar/Screen-rec/Motion-graphic sheets carry instead.

Open
9My tasksArjun's queue

A producer's whole plate across videos: the needs-changes re-record first, then in-progress, delivered, and the unassigned "up for grabs" pool with Claim.

Open
10Channel strategyGoUltra AI

The standing profile that feeds idea generation and script tone: audience, four pillars, cadence slots, the AI idea inbox — and where YouTube reporting will land later.

Open
What to judge in this click-through
  1. The pipeline model. Nine stages, two director gates (approve script+direction before handoff · approve the final cut before packaging). Is this how you want to run production?
  2. The handoff. Script locks → AI proposes segments → you set direction → approval creates the 7 producer tasks. Does that boundary sit in the right place?
  3. The task sheets. Per-type packages (HeyGen script lines, Seedance prompt package, capture scripts). Would Priya and Arjun know exactly what to do?
  4. The two seats. Director pages vs the producer queue/task pages — right split of power and visibility? (Static mockups: leaving a producer page flips the seat back to Deven — in the app, gate and idea controls are director-only.)
  5. Names. "Showrunner" is still a placeholder — as are stage names, chip words, and anything else that reads wrong.
The locked style

Direction A distilled into showrunner.css — gua tokens, YouTube-orange identity, navy diamond gates, warm gradient reserved for primary CTAs.

Open the style guide
Stage A archive

The exploration that got us here: A · Family (winner) · B · Control Room · C · Editorial