Keyword search with source provenance. Source matches do not establish canon or character knowledge. No AI provider is required.
KEYWORD ? 6093 results
## One-paragraph reminders for when the writing drifts ----- **On voice:** Every chapter, ask: cover the speaker tag , can the reader still tell who's talking? Cover the POV marker , can the reader still tell whose head we're in? If yes, the voice is doing its job. If no, the prose has drifted into authorial register
# PART TEN , SESSION FEEDBACK LOG
## Notes from live revision sessions , update this doc as feedback comes in -----
### LEGACY CHAPTER 4 SESSION , Feedback preserved as craft lessons The diagnostic patterns that surfaced repeatedly during the chapter 4 revision: **1. The "explaining outside" reflex.** When a feeling is happening, the writer's first impulse was to name it from outside (*"she felt sad"*; *"there was tension"*). Almo
# carry_forward_chapter Working language: English. Purpose: temporary handoff file for the next chapter or next block only. This file is not a canon ledger, not a part worklist, not a chapter logic map, and not a storage place for broad project rules.
## Current status No active carry-forward notes are open. The project is currently in skeleton-first planning mode. This file stays empty until a specific chapter skeleton or prose session creates concrete handoff material for the next chapter or next block.
## Source-of-truth rule 1. `active_workfiles_index.md` controls which files are active. 2. `canon_ledger.md` controls canon locks. 3. `worklist.md` controls global working laws. 4. `parts_summaries.md` controls the seven-part saga architecture. 5. `worklist_by_parts_partX.md` controls part-level planning. 6. `partX_ch
## When to update this file Update this file only after one of these actions: 1. A full chapter skeleton has been built. 2. A chapter has been written. 3. A chapter has been repaired. 4. A block has been planned in enough detail that the next chapter or block must inherit concrete information. Do not update this fil
## What belongs here Only concrete material that the immediate next chapter or next block must inherit. Examples: 1. Physical location at the end of the previous chapter. 2. Time of day or time gap. 3. Who is physically present. 4. Who is absent but active through object, memory, injury, message, or unresolved dange
## What does not belong here Do not store broad project rules here. The following belong in other active files: 1. World rules belong in `canon_ledger.md`, `worklist.md`, and relevant part files. 2. Living people, dirty roads, and moving vehicles rules belong in canon, worklist, methodology, prompts, and part files.
## Template for next use When a specific chapter or block creates carry-forward material, replace the empty status above with the following structure.
### Source session Chapter or block: Part: Work mode: Date: Status:
### Immediate next target Next chapter or block: Next chapter title, if locked: Purpose of next chapter or block:
### Physical handoff Location: Time: Weather or season: Vehicles: Supplies: Weapons and tools: Shelter: Road or route state:
### Character handoff Physically present at ending: Absent but active: Characters who must not appear yet: Children: Animals: Injuries: Pregnancy, birth, or medical state: Hygiene, exhaustion, hunger, or body state:
### Knowledge handoff What the group knows: What specific characters know: What the reader knows: What must remain unknown: Forbidden future knowledge:
### Relationship handoff Core couple state: Sub-main or side couple state: Friendship or family state: Conflict still open: Trust movement: Intimacy movement:
### Objects and signals Active objects: Notes or signs: Radio or communication state: Maps or route marks: Promises, symbols, clothing, jewelry, letters, photographs, or private objects:
### Immediate risks Living dead: Living people: Road or vehicle risk: Weather risk: Medical risk: Emotional risk: Camp, station, base, city, or gate risk:
### Required next-file updates After the next skeleton or prose session, check whether these files need updates: 1. `chapters_summaries.md` 2. `worklist_by_parts_partX.md` 3. `partX_chapter_logic_map.md` 4. `canon_ledger.md`, only if canon changes. 5. `chapter_word_count_audit.txt`, only if prose exists. 6. `carry_fo