Story Cards Foundation Board: draggable Post-it planning for 24 Blocks / 96 Mini-Blocks

[BryanHarrisScripts]

Parent

#2165 Writer-to-Screen Convergence

Objective

Create the earliest writer-facing planning surface: a digital Post-it / Story Card board that introduces the canonical 24 Blocks before any screenplay pages are required.

Product contract

• 24 Block positions remain deterministic structural addresses.
• Each Block card can expose its four Mini-Block positions/cards.
• Cards may be dragged/reordered while exploratory.
• Dragging moves planned creative content between stable structural positions; it must not invent a second address system.
• A writer can lock/accept the current arrangement when ready.
• Locked does not mean forever immutable: later Human-authorized change is allowed, but affected downstream evidence must be marked stale through existing dependency / Creative Transaction machinery.
• The same Block/Mini-Block vocabulary must carry into Learn, Write and Outline.
• No prose, Scene, Beat, Shot or visual material is fabricated merely because a card exists.

UX direction

The experience should feel like a wall of Post-it notes rather than a technical schema editor:

• quick card title/subtitle;
• short story intent/note;
• obvious Block number/address;
• expandable Mini-Blocks;
• drag/drop + keyboard equivalent;
• lock/unlock state;
• one horizontal row per Act where practical, matching the agreed Outline orientation.

Afterglow acceptance

Afterglow should be able to load into this board with its known Block identities/titles so a Human can start at the planning cards and later traverse to the written and visual forms of the same story.

Reuse boundaries

Reuse PPF/24-96 identity, #2035 Creative Transactions, #2159 Surface Grammar/Registry and existing story structure. Do not create another story store or revision engine.

Exit criteria

1. A new/blank story can be planned as 24 draggable Block cards with four Mini-Block positions each.
2. Address identity remains deterministic after reorder.
3. Human lock/unlock state is explicit.
4. Existing downstream work can detect staleness after a locked upstream card changes.
5. Afterglow can project its known structure into the same board.
6. Keyboard and pointer movement are both supported.
7. Focused tests prove reorder/lock/provenance behavior without manufacturing story data.