Writer-to-Screen Convergence: block-native writing, visual production, and Afterglow acceptance harness

[BryanHarrisScripts]

Purpose

Capture the product architecture emerging from the September Human UAT and design discussion before further implementation. The goal is not another disconnected workflow. PlotPickle should let a writer create the story in the same deterministic structure that later drives Outline, Storyboard, Previs, Scene Workspace, and Production.

Core product principle

The written Block is the creative source that progressively attracts the other production components around it.

The same 4 Acts → 12 Sequences → 24 Blocks → 96 Mini-Blocks structure should organize learning, outlining, writing, visual references, storyboard decisions, previs, synchronized scene work, and production evidence. As the work moves downstream, more components are attached to the same story addresses rather than copied into new authorities.

The Human described this as a gravitational/convergent model: the original story idea and written Block remain the center while structure, characters, references, shots, movement, audio, timing and provider instructions are progressively pulled into one final production object.

Writer-first chain

WRITE — What is the story on the page?

• The writer works in named Blocks, using a Block title/subtitle as a human-readable story unit.
• A feature-length screenplay can be shaped in roughly Block-sized writing increments instead of forcing the writer to think in implementation objects.
• Each Block maps to four Mini-Blocks and exposes the relevant real screenplay text.
• Learning/education should use the same Block/Mini-Block language, so the user learns the same structure they later writes in.

OUTLINE — What happens in this Block and why?

• Act / Sequence / Block / Mini-Block structure.
• Dramatic function, purpose, progression and written source material.
• Writer can see the Block as a story unit before any visual production detail is required.

STORYBOARD — What does it look like?

• approved/candidate character references;
• representative poses/expressions;
• locations, props, palette, lighting, tone and composition;
• key visual moments associated with the Block/Mini-Block and real Scene/Beat material.

PREVIS — How does it move and play?

• visual coverage summary first;
• camera intent, blocking, motion, pacing, transitions and rough timing;
• low-cost/rough motion is valid; the purpose is decision-making rather than final rendering.

SCENE WORKSPACE — How do the pieces synchronize over time?

A scene-level workbench should combine screenplay context, playback, inspection and a block/timeline surface for synchronized evidence such as:

• Dialogue;
• Action;
• Shot;
• Audio;
• later lighting / FX / transition / camera motion where useful.

This is the place where Scene → Beat → Shot → Frame becomes visually understandable rather than an architecture phrase.

PRODUCTION — Generate/render the approved result

• compile approved upstream story and visual intent into provider-neutral production instructions;
• use already-selected provider/runtime routing;
• generated output remains candidate material until Human acceptance;
• provider prose is disposable and does not become canon by itself.

Structural relationship

• Block / Mini-Block = stable story address.
• Scene / Beat = variable-density authored material related to that address.
• Shot / Frame = variable-density visual material related to that authored material.
• technical RenderClip addresses remain production plumbing and are not creative shot quotas.
• relationships are not forced 1:1.

Agentic mode

A writer who only wants to write should be able to ask PlotPickle to project the story downstream automatically:

Written Block → Outline interpretation → visual references → Storyboard candidates → Previs candidates → synchronized Scene Workspace → Production candidate

Agents may interpret and propose each downstream layer, but they do not silently rewrite the source story or promote candidates to accepted creative truth. The Human can accept, reject, revise, regenerate or return upstream to rewrite.

Afterglow as the reference acceptance story

Use Afterglow: Reflections of Sentience as a canonical worked example and deterministic acceptance fixture. Its written screenplay should let PlotPickle verify story-to-screen fidelity at a known Block/Mini-Block address.

A CI/UAT fixture should be able to select one known Afterglow Block and verify that the same story address survives through:

1. correct Block title/subtitle and source text;
2. correct Mini-Block projection;
3. Outline purpose/structure;
4. Storyboard visual references/candidates;
5. Previs coverage/movement/timing intent;
6. Scene Workspace Dialogue/Action/Shot/Audio synchronization;
7. provider-neutral production instructions;
8. candidate output provenance back to the original story address.

The test must verify continuity and provenance, not subjective artistic quality. Missing downstream material must remain truthfully missing rather than fabricated just to make CI pass.

Relation to existing PlotPickle architecture

This work must reuse existing authorities and compiler boundaries rather than create parallel systems:

• PPF/canonical project remains creative truth;
• existing 24/96 address model remains canonical;
• existing pre-production provider-instruction compiler remains provider-neutral and cannot select providers or promote output into creative state;
• Human approval remains the promotion boundary;
• Skin V1 Surface Grammar and complete UI continuity governance #2159 Surface Grammar/Registry governs UI consistency;
• Writer UAT: make Outline read like a story before it reads like a production pipeline #2164 remains the current writer-facing clarity pass, not the full implementation of this architecture.

Mathematical implication

The deterministic structure becomes more useful when every stage shares the same addresses. PlotPickle Score and future measurable signals can evaluate continuity, completeness, progression and drift across the same story graph without pretending to judge creative quality. The stronger the shared address/provenance model, the stronger the measurable structural evidence becomes.

Implementation phases

1. Writing Block contract — formalize Block title/subtitle, source-text span/page range, four Mini-Block projections and shared Learn/Write/Outline vocabulary.
2. Afterglow fixture — choose and freeze one or more reference Blocks with expected story addresses and source evidence.
3. Storyboard convergence — attach visual reference/character/location/lighting/tone evidence to the same addresses.
4. Previs convergence — attach motion/camera/timing evidence without new canon authority.
5. Scene Workspace — synchronize Dialogue/Action/Shot/Audio against real Scene/Beat/Shot identities and source story addresses.
6. Production compiler path — compile approved creative state into provider-neutral production instructions and candidate renders.
7. Story-to-screen CI/UAT — deterministic continuity/provenance checks across all stages.
8. Agentic one-click projection — allow a writer to generate candidate downstream layers from the written story, with Human review at every promotion boundary.

Non-goals

• no forced five-page exact Block size;
• no forced one-Scene-per-Mini-Block or fixed creative Shot count;
• no AI authority over the writer's story;
• no automatic acceptance of generated visual or production material;
• no second project/store/compiler authority;
• no subjective CI score for whether a scene is creatively "good";
• no requirement that every writer use visual/production stages.

Acceptance direction

PlotPickle should eventually demonstrate this simple Human story:

I can write my screenplay in understandable named Blocks. PlotPickle can show me what each Block means structurally, visualize it, rough out how it moves, synchronize the scene, and generate a production candidate — while every downstream decision remains traceable to what I actually wrote and nothing becomes my accepted story without my approval.

September 17 convergence clarifications

The Story Card / Afterglow / curriculum review added three governing principles that apply across the child issues.

1. The screenplay is evidence; 24/96 is the shared structural coordinate system

• 24 Blocks / 96 Mini-Blocks remain the canonical PlotPickle planning, learning and diagnostic addresses.
• A source screenplay may be organized differently.
• Source section count, page count and PlotPickle Block count must not be conflated.
• Afterglow v9 is the most complete baseline and contains 20 explicit titled source sections; v8 is a historical complete comparison source; v10 is a later partial rewrite whose recovered source covers the opening frontier only.
• Afterglow Golden Story Fixture: map all 24 Blocks / 96 Mini-Blocks to source evidence #2168 owns the version-aware evidence crosswalk and the distinction between Covered, Condensed/Shared, Gap/Underdeveloped and Unresolved structural responsibilities.
• Source-density metrics support diagnosis but do not prove dramatic completeness.

2. Character Truth is not automatically audience knowledge

Character profiles/backstory can explain motivation, fear, strategy, relationships and intended emotional start/end states even when none of that material is spoken or shown directly.

The system must distinguish:

• Character Truth / writer knowledge;
• Character Arc State at a story address;
• audience-visible Screenplay Evidence.

#2178 owns source-profile preservation, provenance and character-arc mapping across the same 24 Blocks. Backstory may inform diagnosis without becoming automatic exposition or canon.

3. Learn and Story use the same conceptual coordinates

PlotPickle's curriculum should explain the same concepts the writer applies in PLAN/Story Cards, WRITE and OUTLINE.

#2167 owns the contextual bridge:

• the existing Make the original 24 Blocks concepts explicit in Read & Learn #48 24-Blocks teaching;
• PlotPickle the Character archive into a guided character-in-motion learning system #51 Characters in Motion / Arc Matrix teaching;
• PlotPickle the Essentials archive into an integrated story-craft learning path #54/Make the legacy General archive the PlotPickle core curriculum and learning-router spine #55 craft/router material;
• LEARN: 24-course guided journey, open exploration, integrity harness and Agent lenses #1918 24-course journey and LEARN -> APPLY -> CHECK -> CONTINUE rhythm.

This is an almost one-to-one concept-to-use relationship, not one lesson per Block. A writer should be able to move from a lesson into the relevant story position and from a Block/Mini-Block/arc checkpoint back to the teaching that explains it.

Curriculum explains and asks questions; it never dictates the creative answer or manufactures missing material.

Current child-issue ownership

• Story Cards Foundation Board: draggable Post-it planning for 24 Blocks / 96 Mini-Blocks #2166 — Story Card Foundation Board and stable 24/96 planning identities — completed.
• Block-native Writing: unify Learn, Write and Outline around named Blocks and Mini-Blocks #2167 — Block-native writing plus bidirectional contextual Learn bridge.
• Afterglow Golden Story Fixture: map all 24 Blocks / 96 Mini-Blocks to source evidence #2168 — Afterglow v8/v9/v10/current source evidence, 24/96 crosswalk and structural gap diagnosis.
• Afterglow Character Truth & Arc Map: preserve profile sources and trace motivation across 24 Blocks #2178 — Afterglow Character Truth, source profiles and 24-Block arc evidence.
• Storyboard Convergence: visual references and shot intent attached to canonical story addresses #2169 — Storyboard convergence on the same addresses.
• Previs Convergence: motion, camera and timing intent over approved storyboard evidence #2170 — Previs convergence.
• Scene Workspace: synchronize screenplay, playback, Dialogue / Action / Shot / Audio timeline #2171 — Scene Workspace synchronization.
• Creative revision propagation: upstream Block changes invalidate only dependent downstream work #2172 — revision/staleness propagation.
• Production Convergence: compile approved story-to-scene state into renderable production intent #2173 — Production convergence.
• Afterglow Story-to-Screen CI/UAT: verify Post-it → Writing → Outline → Storyboard → Previs → Scene Workspace → Production #2174 — deterministic Story-to-Screen CI/UAT.
• Agentic Story-to-Screen Projection: one-click downstream candidate generation from the written story #2175 — agentic downstream projection.
• PageFlow PPF Migration: preserve diagnostics as read-only Refine over Block-native Write #2180 — PageFlow PPF migration; read-only Refine diagnostics over Block-native Write.

No child issue may create a parallel story store, curriculum store, character authority or address system.

[BryanHarrisScripts]

Quadruple-review architecture checkpoint

The developer brief is now captured at docs/developer-briefs/2165-writer-to-screen-convergence.md on issue-2164-writer-first-outline-flow (commit 0faadb2cd650f8609eb91767e011ad43c9f1abc5).

The review reconciled four sources before freezing the direction:

1. the current Human writer UAT and Scene Workspace reference;
2. prior PlotPickle decisions around one canonical 4 Acts / 12 Sequences / 24 Blocks / 96 Mini-Blocks structure, Afterglow as the worked example, and Human approval of AI proposals;
3. current repository authority boundaries — PPF, PlotPickle CONTRACT / COMPILER / BINDER / LOCKS, provider-neutral Director Specification compilation, and Sequence Evidence separation of creative Shots from technical RenderClip slots;
4. a deterministic CI/UAT model using Afterglow story addresses to verify continuity/provenance from Writing through Production without cloud spend or subjective artistic grading.

The gravitational/convergence analogy is retained only as a product explanation: downstream evidence accumulates around the same canonical story identities. It is not a new store, authority or compiler.

[BryanHarrisScripts]

Final product-model addition — Post-it / Story Card foundation

The writer-to-screen chain begins before prose exists.

A writer commonly starts by moving physical Post-it notes around until the story shape feels right. PlotPickle should model that as the earliest writer-facing projection of the existing 24/96 structure:

STORY CARDS / FOUNDATION BOARD → WRITE → OUTLINE → STORYBOARD → PREVIS → SCENE WORKSPACE → PRODUCTION

Key decisions:

• the board introduces the 24 Block concept before the writer has written pages;
• each Block card can expose its four Mini-Block cards/positions;
• cards can be dragged/reordered while exploratory;
• moving content between positions changes the story plan while the canonical structural addresses remain deterministic;
• cards can be Human-locked/accepted when the writer is ready to treat the arrangement as current creative truth;
• a later unlock/move/rewrite is allowed, but downstream affected evidence must become stale/invalidated through existing dependency / Creative Transaction machinery rather than silently remaining certified;
• the board, Learn, Write and Outline must use the same structural vocabulary;
• Afterglow should ultimately be traversable from its Story Cards through written Blocks, Outline, Storyboard, Previs, Scene Workspace and Production so the Human can move to any stage and still recognize the same story.

This makes the "gravitational" model complete: the first card is not replaced downstream; progressively richer evidence accumulates around the same story identities.

[BryanHarrisScripts]

Locked implementation sequence after final triple-check

This is the execution order. Stop adding parallel architecture; work these in sequence and keep Afterglow as the continuity thread.

0. Writer UAT: make Outline read like a story before it reads like a production pipeline #2164 — Writer-first clarity pass
   Finish/merge the currently implemented Library/Score/Outline/Written Story/Storyboard naming/Previs coverage corrections first.

1. Story Cards Foundation Board: draggable Post-it planning for 24 Blocks / 96 Mini-Blocks #2166 — Story Cards Foundation Board
   Post-it planning surface for 24 Blocks / 96 Mini-Blocks, drag/reorder, keyboard parity, Human lock/unlock, stable structural addresses.

2. Block-native Writing: unify Learn, Write and Outline around named Blocks and Mini-Blocks #2167 — Block-native Writing
   Align Learn → Write → Outline around named Blocks/subtitles, four Mini-Blocks and real screenplay/source material. Five-to-seven pages is a useful Afterglow heuristic, not a hard limit.

3. Afterglow Golden Story Fixture: map all 24 Blocks / 96 Mini-Blocks to source evidence #2168 — Afterglow Golden Story Fixture
   Map the full 24/96 structural/source evidence so every later phase tests against the same real story instead of inventing new demos.

4. Storyboard Convergence: visual references and shot intent attached to canonical story addresses #2169 — Storyboard Convergence
   Visual references, character poses/identity, locations/props, palette/lighting/tone, candidate/accepted images and shot intent attached to canonical story refs. Reuse Pre-production Production Object Layer: Story → Frames progressive authoring architecture #2092 and Shot Information Boundary: preserve audience reveal / withhold timing through Story → Shots → Frames #2107.

5. Previs Convergence: motion, camera and timing intent over approved storyboard evidence #2170 — Previs Convergence
   Visual coverage first, then camera/blocking/motion/timing/pacing over the same accepted Storyboard/story evidence. Reuse Pre-production Production Object Layer: Story → Frames progressive authoring architecture #2092 ProductionShotIntent and Sequence Director boundaries.

6. Scene Workspace: synchronize screenplay, playback, Dialogue / Action / Shot / Audio timeline #2171 — Scene Workspace
   Screenplay + playback + inspector + synchronized Dialogue / Action / Shot / Audio timeline, preserving exact Block/Mini-Block/Scene/Beat/Shot source refs.

7. Creative revision propagation: upstream Block changes invalidate only dependent downstream work #2172 — Creative revision propagation
   Make the chain bidirectional. A moved Story Card, rewritten Block or changed visual decision invalidates only dependent downstream work. Reuse completed Provider-neutral Universal Creative Transaction Contract #2035 Creative Transactions and existing staleness/evidence machinery.

8. Production Convergence: compile approved story-to-scene state into renderable production intent #2173 — Production Convergence
   Feed approved upstream state into completed Provider-neutral Director Spec Compiler #2064 Director Spec Compiler and existing provider routing. No second compiler/router and no provider prompt as canon.

9. Afterglow Story-to-Screen CI/UAT: verify Post-it → Writing → Outline → Storyboard → Previs → Scene Workspace → Production #2174 — Afterglow Story-to-Screen CI/UAT
   Deterministically verify Story Cards → Write → Outline → Storyboard → Previs → Scene Workspace → Production, first for one reviewed Block, then report full 24/96 structural/source coverage. CI remains local/offline; provider-backed generation is an explicitly authorized UAT/Responsibility Run.

10. Agentic Story-to-Screen Projection: one-click downstream candidate generation from the written story #2175 — Agentic Story-to-Screen Projection
    Optional one-click/bounded downstream proposal generation from the writer's accepted story, with Human review/promotion at every authority boundary.

Existing architecture these issues must consume rather than duplicate

• Pre-production Production Object Layer: Story → Frames progressive authoring architecture #2092 Production Object Layer owns the progressive Story → Frames reuse/reconciliation problem.
• Shot Information Boundary: preserve audience reveal / withhold timing through Story → Shots → Frames #2107 Shot Information Boundary owns show/withhold audience-information timing.
• Provider-neutral Universal Creative Transaction Contract #2035 completed Creative Transaction Contract owns staged change/verification/review/commit/recovery.
• Provider-neutral Director Spec Compiler #2064 completed Director Spec Compiler owns provider-neutral production compilation.
• Skin V1 Surface Grammar and complete UI continuity governance #2159 Surface Registry / Grammar governs UI consistency.

Final outcome

The acceptance target is simple: load Afterglow and move to any stage — Story Cards, written Block, Outline, Storyboard, Previs, Scene Workspace or Production — and still recognize the same story, same title/subtitle, same Block/Mini-Block identities and source lineage. The writer can move forward, backward, edit, refine, lock/unlock and visualize without switching conceptual systems.