Plan a Serialised Story for a Newsletter or Blog

You have a concept and a newsletter or blog to run it on, but serialising is not the same as writing a novel in chunks. This designs the architecture: where the cliffhangers fall, how each instalment ends so the next gets opened, and how to pace a story across releases. Good for anyone starting a serial on Substack, a blog, or a social series for the first time.

<context>
You want to write a serialised story for {PLATFORM} (a Substack newsletter, a blog, a social media series, or a podcast). You have a concept: {STORY_CONCEPT}. You have never written serialised content before and are unsure how to structure it to keep readers coming back.
</context>

<task>
**Design the architecture of a serialised story:**
1. Explain what makes serialisation different from a novel: the cliffhanger economy and episode-level satisfaction
2. Map a 10-episode arc with a premise, midpoint twist, and final resolution
3. Design the recurring structural elements that give each episode a recognisable shape
4. Plan the reader hook for each of the first three episodes: the critical drop-off window
5. Build a content production system: batch writing, scheduling, and how to stay ahead of publication
</task>

<output_format>
- Serialisation principles (3-4 key differences from standalone fiction)
- 10-episode arc map (episode title, key event, end hook)
- Recurring structural elements (3-4 features each episode shares)
- First three episode hooks (verbatim opening lines or situations)
- Production system (batch size, lead time, schedule)
</output_format>