presentation-story-architecturelisted

# Build the story architecture Use when `story-architecture` is the current gate. - Read repo instructions, `PRESENTATION-BRIEF.md`, `EVIDENCE-LEDGER.md`, and the cited source files before structuring the talk. - Require one memorable thesis. - Require an explicit audience change from where the talk starts to where it should end. - Write `STORY.md` from `templates/STORY.md`. - Write `STORYBOARD.md` from `templates/STORYBOARD.md`. - Build the story from the approved brief and supported evidence claims only. - If a chapter needs unsupported evidence, return the work to evidence instead of letting the chapter enter the story. - Assign each chapter a role such as context, tension, proof, decision, action, or closing commitment. - Write spoken transitions that explain why the next chapter or slide must exist. - Separate the main-talk range from backup or Q&A material. - **One Dominant Message per Slide**: Require one necessary job per slide. Split the slide rather than shrink text or pack distinct messages onto one page. Remove ornamental, duplicate, or “nice to have” pages. - **Meaningful Brevity (Anti-Over-Pruning)**: Text pruning must eliminate fluff and secondary clutter while preserving clear, grammatically sound, and intellectually substantive core takeaways. Do not reduce statements to cryptic 2-word fragments. ## Instructional design & 4MAT learning cycle Incorporate adult learning dynamics (ATD / 4MAT / Kirkpatrick Level 2 & 3 behavior transfer): 1. **Why (Relevance &