Story Architecture
Controlling question, episode spine, act turns, resets, and viewer-load discipline.
Read chapterA field manual for long-form YouTube that wants the rhythm of John Oliver and the spine of Frontline.
Scope
This is not another screenwriting syllabus. It is a workbench for The Blindspot: long-form geopolitical, historical, and investigative episodes made by a small team or one stubborn adult in Los Angeles.
The manual is built to be entered at random. A reader can start with the cold open, a research problem, a sound problem, a packaging problem, or a case file.
The structure is still ordered. Shape the story, build the proof, cut the argument, finish the episode, then learn from the upload.
Reuters Institute's 2025 Digital News Report says 30% of the global sample uses YouTube for news weekly, and social video news consumption rose from 52% in 2020 to 65% in 2025. The audience is already in the room. The work is to arrive with standards intact.
Main Menu
The Blindspot Workflow Map
Find the controlling question, source the claims, and choose the line.
Make the click feel earned and the host useful.
Turn evidence into a watchable argument.
Finish clean, publish honestly, and read the upload calmly.
Use this as the subpage's main menu: production order for planning, chapter cards for problem-solving, case files for pattern theft.
The route is simple: shape the question, prove the promise, build the edit, ship the lesson.
Chapter Deck
Controlling question, episode spine, act turns, resets, and viewer-load discipline.
Read chapterSeed, beat map, source stack, fact pass, legal language, and research stop rules.
Read chapterFirst 30 seconds. Promise the argument, prove the tone, and remove every ceremonial throat-clear.
Read chapterWriting for the ear, pause discipline, teleprompter defaults, and dry lines that do not beg.
Read chapterArchival logic, data cards, maps, lower thirds, document zooms, and graphics that argue.
Read chapterCut on argument first, rhythm second. Slow down when the proof needs air.
Read chapterDialogue clarity, natural sound, silence, captions, export specs, and source-integrity QC.
Read chapterSolo shooting, folder shape, file naming, review handoff, and the local 70% ship rule.
Read chapterCTR, AVD, intro retention, title/thumb tests, postmortems, and honest promise mechanics.
Read chapterCase Files
Follow one line through a large subject. Cut the impressive material that leaves the line.
Turn civic tedium into a usable action without pretending correlation proves causation.
Make maps answer to local sources before they become beautiful.
Steal production logic, not surface mannerisms. No tribute-band editing.
Use the workflow map as the subpage menu during production reviews. Start with the stage that is failing, then jump to the matching checklist.
Source Rule
Books supplied craft. YouTube supplied current platform mechanics. Operator interviews supplied case patterns. Forum notes supplied friction and are marked anecdotal in-page.
Distribution claims were checked against current official YouTube Help and YouTube's recommendation-system blog before this pass shipped. The source ledger tracks every live source and why it was allowed into the manual.