Spark Long Form Narrative

---
name: spark-long-form-narrative
description: "The user has a module map or chapter list and the question is now *how does this read.* Load whenever you hear \"what's the throughline,\" \"how should chapters flow,\" \"this feels disconnected,\" or \"I have the pieces but it's not a book yet.\""
metadata:
  author: wayland
  version: "1.0.0"
  category: "spark"
---

# Long-form narrative

## When to load this mode

The user has a module map or chapter list and the question is now *how does this read.* Load whenever you hear "what's the throughline," "how should chapters flow," "this feels disconnected," or "I have the pieces but it's not a book yet."

## Procedure

A course or book is not a list of lessons. It is one argument made over many chapters. Without a throughline, the learner gets a folder of files and stops opening them. Four steps.

**1. State the throughline as a single argument.** One sentence: "This book argues that [claim], because [reason], and the reader should now [action]." A throughline of "freelancers should niche down" reads tighter than "here is everything I know about freelancing." Every chapter must move it forward. If not, it's a blog post in the wrong drawer.

For a course, the throughline is the transformation statement in argument form.

**2. Pick the arc shape.** Three default shapes carry most long-form work:

- **Problem-to-resolution.** Open in the learner's current pain. Each chapter removes one obstacle. End in the new state. Default for transformation-led courses and how-to books.
- **Question-to-answer.** Open with a question the reader is already asking. Each chapter sharpens it. End by answering it differently than expected. Default for idea-led books and frameworks.
- **Journey-with-stakes.** Open inside a case. Each chapter advances it and lifts out one principle. End with the case resolved and principles named. Default for narrative non-fiction.

Pick one. Mixing shapes muddies the throughline. Subplots are fine; arc shapes are one per asset.

**3. Sequence chapters by tension, not topic.** Each chapter answers a question the prior raised, and raises the next. A chapter that resolves everything kills the pull; one that resolves nothing frustrates. Shape: open a loop, close part of it, open a bigger one.

Test: at each chapter's end, write one sentence — "what does the reader now want to know that they didn't before this chapter?" If you can't, cut, reorder, or rewrite the close.

For courses, same test at module boundaries. The end of module two should make module three feel necessary.

**4. Open with the strongest scene; close with the recommitment.** First line and page: open inside a moment the reader recognizes, not a definition. Definitions live in chapter two.

Last page: don't end with summary. End with one thing the reader is now equipped to do, and one sentence giving permission to start small. "Thanks for reading" earns no behavior change.

For courses, the last lesson is the recommitment moment — one final artifact, told exactly what to do tomorrow. Vague endings produce shelved courses.

## Decision rules

- **One throughline per asset.** If you can't write it in one sentence, the asset has two books inside. Split or pick one.
- **Every chapter earns its place against the throughline.** Interesting but off-throughline goes in the appendix or gets cut.
- **Chapter length follows tension, not symmetry.** A 3,000-word chapter next to an 8,000-word chapter is fine if both close their loop.
- **First chapter is a contract; last is a handoff.** First promises the transformation in the reader's terms. Last sends them across with the smallest next step named.
- **One framework per book.** Two named frameworks compete; the reader remembers neither. Sub-models nest under one parent.

## Anti-patterns

- **Comprehensive front matter.** Long history of the field, three definitions before the first scene. The reader leaves before the argument starts.
- **Each chapter as an island.** Self-contained, no callback or forward pull. Reads like a magazine — searchable but not readable.
- **The everything-summary chapter.** Re-states the entire book. If the throughline holds, the reader already has it.
- **Ending with a manifesto.** Stirring on the page, inert on Monday morning. Name the next concrete action.
- **Frameworks announced before earned.** Naming the model in chapter one before the reader has felt the problem. The reader nods politely and forgets.

## Before / after

**Before:** *"Chapter one: what is consulting. Chapter two: the consulting industry. Chapter three: how to pick a niche. Chapter four: how to find clients..."*

**After:** *"Throughline: a generalist consultant earns less than a specialist with worse skills, because pricing follows positioning, and the reader should rewrite their headline by Friday. Arc: problem-to-resolution. Ch 1: a generalist loses a deal to a worse specialist. Ch 2: positioning beats skill in buyer perception. Ch 3: the niche the reader is already standing in but hasn't named. Ch 4: writing the headline. Ch 5: the first three messages from the new position. Close: the reader rewrites the headline and sends one message before closing the book."*