Afterglow Golden Story Fixture: map all 24 Blocks / 96 Mini-Blocks to source evidence

[BryanHarrisScripts]

Parent

#2165 Writer-to-Screen Convergence

Related

• Story Cards Foundation Board: draggable Post-it planning for 24 Blocks / 96 Mini-Blocks #2166 Story Cards Foundation Board — merged foundation
• Block-native Writing: unify Learn, Write and Outline around named Blocks and Mini-Blocks #2167 Block-native Writing / contextual Learn bridge
• Afterglow Character Truth & Arc Map: preserve profile sources and trace motivation across 24 Blocks #2178 Afterglow Character Truth & Arc Map
• Afterglow Story-to-Screen CI/UAT: verify Post-it → Writing → Outline → Storyboard → Previs → Scene Workspace → Production #2174 Story-to-Screen CI/UAT
• PageFlow PPF Migration: preserve diagnostics as read-only Refine over Block-native Write #2180 PageFlow PPF migration / screenplay diagnostics
• Historical version reconciliation: Reconcile the legacy Afterglow folder and convert the 2023 draft poster to WebP #60, Reconcile complete Afterglow v9 with the unfinished v10 Blocks 1–8 rewrite #61

Objective

Turn Afterglow: Reflections of Sentience into the canonical end-to-end reference story for PlotPickle's writer-to-screen architecture by mapping real source evidence from v8, v9, v10 and current approved work onto the canonical 4 Acts → 12 Sequences → 24 Blocks → 96 Mini-Blocks structure.

The screenplay versions are evidence. The 24 Blocks are the canonical planning/evaluation structure.

Governing structural rule

A screenplay version does not need to contain 24 explicitly authored headings in order to be evaluated against the 24-Block framework.

PlotPickle must distinguish:

• source topology — how a particular screenplay/version is actually organized;
• canonical PlotPickle topology — the stable 24 Blocks / 96 Mini-Blocks used for planning, learning, diagnosis and downstream production;
• mapping evidence — why a source passage is associated with a canonical Block/Mini-Block.

Do not infer that page-progress normalization proves authored Block boundaries.

Current Afterglow version evidence

v8 — historical complete comparison

• earlier complete rewrite;
• approximately 86 pages in the recovered FDX;
• useful for structural comparison and gap recovery;
• its FDX does not itself prove 24 explicit authored Block markers.

Use: historical comparison when later versions appear compressed, omit earlier material or leave a structural responsibility weak.

v9 — most complete baseline

• current preferred complete story baseline;
• approximately 80 pages;
• FDX contains 20 explicit titled source sections;
• the supplied historical 20-section summary records those movements and page ranges;
• PlotPickle may map those passages across 24 canonical Blocks, but must not label the 20 source sections as 24 authored Blocks.

Use: baseline story evidence for the whole movie.

v10 — later partial rewrite

• later rewrite direction;
• current recovered PlotPickle source covers Blocks 1–8 / 38 scenes;
• Blocks 9–24 were not attempted in that source;
• v10 may propose/replace material only where evidence actually exists.

Use: later-authority proposal within its real frontier. It never erases v9 coverage outside that frontier.

current PlotPickle working story

May combine Human-approved material from v9, v10, v8 recovery and new writing while retaining provenance and decision history.

Source-use order

For an early canonical Block where v10 contains material:

v9 baseline -> compare v10 later rewrite -> inspect v8 when a gap/compression question remains -> Human decision

For a later Block outside v10:

v9 baseline -> inspect v8 when a gap/compression question remains -> Human decision

This is evidence priority, not automatic canon precedence.

24-Block evidence matrix

For every canonical Block and Mini-Block, record where available:

• stable PPF Block/Mini-Block address;
• Human-readable current title/subtitle;
• expected structural/narrative responsibility;
• source version;
• source section ID/title;
• page/line/passage range;
• source passage IDs/hashes;
• Scene associations;
• mapped characters and locations;
• source-density metrics;
• character-arc evidence from Afterglow Character Truth & Arc Map: preserve profile sources and trace motivation across 24 Blocks #2178;
• mapping method;
• review/confidence state;
• downstream visual/storyboard/previs references where already approved.

Mapping-method vocabulary

A mapping must explain how it was established. Support at least:

• authored-label — explicit source heading/marker;
• historical-crosswalk — known mapping between versions/legacy material;
• semantic-reviewed — Human-reviewed narrative-function mapping;
• page-progress-fallback — deterministic fallback only when better evidence does not exist.

A fallback projection must never be presented as an authored source boundary.

Structural finding vocabulary

Each canonical Block should be able to report one of these descriptive states:

Covered

The mapped screenplay evidence performs the Block's intended narrative responsibility sufficiently for the current review purpose.

Condensed / Shared

The responsibility exists, but one source section/sequence is carrying the work of multiple canonical Block positions, or multiple responsibilities are compressed into one movement.

Gap / Underdeveloped

The expected responsibility is missing or not sufficiently supported by observed screenplay evidence.

Unresolved

Evidence exists but version conflicts, source ambiguity or Human judgment prevents a reliable classification yet.

These are diagnostic evidence states, not quality scores and not automatic rewrite instructions.

Critical distinction: evidence density is not structural completeness

The current Story Card foundation can report passages, scenes, words, source share and Mini-Block evidence density.

Those metrics help locate sparse/overloaded areas, but they cannot by themselves determine whether the correct dramatic work is happening.

A Block can contain many pages and still have a structural or character-arc gap.

Narrative responsibility

The fixture should eventually make each Block's intended job inspectable in plain language.

Examples of responsibilities may include:

• setup/expectation;
• pressure/escalation;
• reveal/withhold;
• decision or commitment;
• consequence;
• relationship movement;
• reversal/turn;
• midpoint reinterpretation;
• crisis pressure;
• climax proof;
• resolution/ending state.

Do not turn these examples into one mandatory beat formula. The curriculum/24-Blocks method explains the craft; the active story provides its own expression.

Runtime / page-length rule

A feature may be shorter or longer than two hours and still use the same 24-Block framework.

Do not require exactly five pages/minutes per Block.

Page/time distribution is pacing evidence, not a completeness definition.

Character integration

Consume #2178 Character Truth/Arc evidence so the fixture can distinguish:

• plot responsibility covered but character transition weak;
• profile/backstory supports motivation but audience-facing evidence is insufficient;
• an arc transition is compressed;
• a later decision assumes an earlier emotional change that has not been dramatized.

Character Truth is not screenplay evidence by itself and must never be converted into exposition automatically.

Human decision boundary

When a gap or compression is found, PlotPickle may present evidence and alternatives such as:

• retain v9;
• prefer reviewed v10 material where available;
• recover/reconsider v8 material;
• combine selected source material;
• write new material;
• intentionally keep the compression;
• defer.

No option is applied automatically.

Education integration

The same Block/Mini-Block addresses should link to #2167 contextual learning:

• why this structural position exists;
• relevant 24 Blocks concepts;
• midpoint/turning-point teaching where applicable;
• character-arc checkpoint teaching;
• setup/payoff, pressure, consequence and other relevant craft;
• active-story exercise/evidence.

Learning explains the principle. It does not dictate the creative answer.

Deterministic fixture / CI boundary

CI may verify:

• address identity;
• source/version provenance;
• passage/page/hash mapping;
• mapping-method validity;
• explicit missing/unresolved states;
• stable source-section markers;
• no manufactured evidence;
• no silent canon promotion.

CI must not judge whether a story is creatively good.

Non-goals

• no claim that v8 is explicitly authored as 24 Blocks without source proof;
• no claim that v9's 20 titled sections are 24 authored source Blocks;
• no blind concatenation of v10 and v9;
• no page-progress mapping presented as semantic truth;
• no automatic story repair;
• no rigid page quota;
• no second story store;
• no subjective structural score replacing Human review.

Exit criteria

1. All 24 canonical Block addresses resolve deterministically.
2. All 96 Mini-Block addresses are represented, including explicit missing-source states.
3. v8, v9 and v10 source/version roles are machine-checkable and preserve immutable provenance.
4. v9's 20 explicit titled source sections are preserved as source topology rather than rewritten into 24 authored headings.
5. v10's real frontier remains bounded to its recovered source; later Blocks fall back to v9 baseline rather than being marked missing from the story.
6. Every non-trivial mapping records its method and source evidence.
7. Coverage, Condensed/Shared, Gap/Underdeveloped and Unresolved states can be reported without manufacturing story content.
8. Source-density metrics remain separate from narrative-responsibility diagnosis.
9. Afterglow Character Truth & Arc Map: preserve profile sources and trace motivation across 24 Blocks #2178 character-arc evidence can contribute to gap diagnosis without making profile claims screenplay proof.
10. Page/runtime distribution remains a heuristic/evidence signal, not a 24-Block validity requirement.
11. Human review controls restore/combine/rewrite decisions.
12. Fixture loading never mutates Afterglow or auto-promotes historical material.
13. The same fixture can be consumed by Block-native Writing: unify Learn, Write and Outline around named Blocks and Mini-Blocks #2167, Storyboard, Previs, Scene Workspace, Production and Afterglow Story-to-Screen CI/UAT: verify Post-it → Writing → Outline → Storyboard → Previs → Scene Workspace → Production #2174 CI/UAT.