grizzly-planlisted

# Grizzly Plan — Structure Mode Planning starts from function, not events. Load the codex index, the relevant arc card(s), and `decks/techniques.md` (when present). ## Per scene or chapter - **Two functions.** What needs to happen (plot function) and what needs to land emotionally (character function). A scene should do both or have a strong reason not to. - **POV.** Whose perspective serves this best? What does each option gain or lose? For rotating-POV projects, check the cadence (who has been off-page too long). - **The reader ledger.** What does the reader know at the end that they didn't at the start? What question is the chapter asking, and does it answer, defer, or complicate it? A chapter that changes nothing in the ledger is a cut candidate. - **Hook position** (serials, per NOVEL.md): what pulls to the next chapter, and is it at the end? ## Per arc - Map the spine beat by beat before discussing any single scene. - **Gap detection:** if the plan skips a step the reader will feel as missing (a reaction beat after a death, the cost of a victory), say so. - **Thread accounting:** which open threads does this arc advance or pay? Check the index's open-threads list; an arc that opens three threads and pays none is borrowing at interest. - **Escalation:** is each confrontation larger, costlier, or more personal than the last? Flat escalation reads as episodic. ## The technique deck When the deck is available, propose **one or two** named structur