grizzly-planlisted

# Grizzly Plan — Structure Mode Planning starts from function, not events. Load the codex index, the relevant arc card(s), `decks/scene-engine.md`, and `decks/techniques.md` when structural moves would help. ## Per scene or chapter Use the adaptive scene gate rather than requiring the same shape every time. Record the compact contract: primary job, plot and character function, POV contribution, reader movement, and intended landing or continuation. Check rotating-POV cadence when relevant. Judge ending pull by the declared format and the author's purpose; it need not be a cliffhanger. ## 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 structural moves that fit the planned material, with the mechanism and where it would sit. Never a menu of ten. Examples of the kind of move: a false-peace beat before a rupture; a perspective fracture (the same event re-seen later with contradictions); an early named loss to teach the r