Foreshadowing, Events & Continuity

Steps

1. Foreshadowing lives on "plotlines": open a plotline for a thread, then record its entries chapter by chapter — touch, plant, advance, twist, resolve, reopen — keeping the whole arc of that thread.
2. The "Foreshadowing" view in the Asset Library shows each thread’s state at a glance: planted, developing, resolved, or overdue — "overdue" means its planned payoff has arrived but the thread isn’t resolved yet.
3. Capture key plot points as "Events" with an "in-story time" (e.g. "the 17th of the Fog Moon") or a story era; the "Event Timeline" supports two orderings: world chronology and narrative reveal.
4. After finishing a chapter, click "Sync this chapter’s story"; the AI reads the chapter and proposes structured updates — create/update assets, add relations, state changes, character knowledge, plotline entries — each with supporting "evidence" and a "rationale".
5. The review card summarizes this batch of changes by category — events, states, knowledge, plotlines — each with evidence and rationale; approve once to write the whole batch in, or reject to discard it all. If you edit the prose after syncing, the chapter is marked "drifted" so you know to re-sync.
6. Want a second net? Turn on "Write-after consistency review" (Beta) under Settings → Writing: after each story sync commits, it rereads the whole chapter looking for knowledge contradictions, character drift, timeline clashes, and leaked foreshadowing; findings appear in the editor as an "N open" overlay, where you can fix with one click, hand them to the assistant, mark them intentional, or dismiss.