Keyword search with source provenance. Source matches do not establish canon or character knowledge. No AI provider is required.
KEYWORD ? 7229 results
# 13. QA checklist, final gate Before delivery, answer yes to all: 1. Does every major scene have body? 2. Does every chapter have enough scene density for its target length? 3. Does every character know only what she could know? 4. Are living-dead rules learned on-page? 5. Are living people present as world factor w
## Active Git Note, Prose Tightening and Reader Trust When Git gives two or three examples of over-explained prose, treat them as symptoms of a pattern, not as an exhaustive checklist. Reusable rule: 1. Do a full pass for the category of problem across the entire chapter, not only the quoted lines. 2. Watch especial
## Active QA Rule, Supersession Before Regression Failure A previous correction, historical QA note, change log entry, handoff note, delivery note, or \“do not do this again\” item proves that a problem existed at that time. It does not automatically prove that the old implementation of the fix is still current story
## Added rule — sex and intimacy scenes are not summary bridges When a romantic or sexual scene is a relationship event, do not replace it with a beautiful summary sentence such as `they made love because...`. The scene must be written as a lived scene when the chapter structure calls for it: 1. clear initiation, 2.
# Integrated Update: Part 1 pre-writing contract discipline
## World / Body / Weather / Threat chapter-contract rule For every Apocalypse, Now chapter contract, especially in the Part 1 rebuild, do not leave the surrounding world for later. The contract itself must include the world layer before prose begins: 1. month after Day Zero, 2. season, 3. region/place, 4. weather and
## Raven / Robin Clexa bet rule Do not frame the Part 1 Raven / Robin thread as romantic or as a threat to Ronance. Their running dynamic in the Shell arc is the Clexa bet / intervention: two sharp people noticing Clarke and Lexa's tension before Clarke and Lexa name it. Nancy can tax them. Alex Vause may later join t
## Raven / Clarke / Abby chosen-family rule Raven is like a sister to Clarke before Day Zero. Abby took Raven under her wing, and Raven became part of Clarke's chosen-family structure. Abby's death is not only Clarke losing her mother; it is Raven losing a maternal axis too. Clarke reaches Raven after Abby dies as a s
## Owner-approved long-arc / geography QA additions — 2026-10-03 1. Before any long-distance movement or entrance/backstory prose, consult the Day Zero Geography Ledger: starting location, physical position, companions, first destination, reason for leaving, transport, approximate route and elapsed-time proof. 2. Recov
## Owner lock — three-axis survival, repair QA, and multi-POV entrant handoffs — 2026-10-03
### A. Three-axis survival / life-worth-living rule Apocalypse, Now must keep three realities alive across every sustained survival sequence: 1. **Living dead / unknown apocalypse.** People die and rise. Rules are learned through witnessed events, mistakes, repeated patterns and physical cause/effect. Brain destructi
### B. Mandatory repair QA before delivery No prose correction, rewrite, scene insertion/deletion, continuity fix, restructuring or EPUB revision may be returned to Git before QA passes. After every repair: 1. Re-read the changed span with enough prose before and after it to test flow, causality, voice, pacing and e
### C. Multi-POV entrant handoff rule Before writing the first chapter of any major character/couple/group entrance, plan the complete handoff in advance. Default three-step entrance: 1. **Existing-group POV ending** — decide exactly where the existing cast first sees/hears/contacts the entrant and where that chapte
## Owner-approved physical identity / blocking QA rule — 2026-10-03 Every correction that exposes a reusable failure becomes a QA category for the current chapter and future chapters, not a one-line memory. Before prose delivery, explicitly verify character physical identity and blocking wherever the scene depends on
## Owner-approved cumulative EPUB / Library persistence workflow — 2026-10-03 This workflow keeps chapter review fast while making closed chapters durable. 1. During active chapter review, do not block the reading/correction loop on Fanfic OS relay writes or Library persistence. Work from the latest local cumulative
# 02_prompts_01_04_planning_writing_repair_package Status: PROPOSED MERGED ACTIVE FILE. Combines the former `02_prompts_01_02_planning_and_writing.md` and `03_prompts_03_04_repair_and_package.md` so the active project package can remain at 20 files while keeping `20_apocalypse_now_project_skills.md` active. ---
# PART A — Prompt 01 and Prompt 02
# 02_prompts_01_02_planning_and_writing Consolidated active source-truth file for **Apocalypse, Now**. Original files preserved in this file: * `prompt_01_read_anchor_plan.md` * `prompt_02_write_chapter.md` --- <!-- BEGIN ORIGINAL FILE: prompt_01_read_anchor_plan.md -->
# prompt_01_read_anchor_plan אתה מתחיל עכשיו שלב קריאה, עיגון, אבחון ושלד לפרק או בלוק שאבקש בהודעה שלי. אסור לך לכתוב אפילו שורה אחת של פרוזה.
## מצב עבודה חובה לפני כל עבודה, חובה לזהות בשקט מה מצב העבודה המבוקש. אם המצב אינו ברור מתוך ההודעה, שאלי שאלה קצרה לפני פעולה. מצבי העבודה האפשריים: 1. **אבחון בלבד**: קוראים, ממפים ומחזירים דוח. אסור לתקן פרוזה או להחזיר קבצי החלפה. 2. **תיקון נקודתי בלבד**: מתקנים רק שורות שסותרות קאנון, ידע, זמן, חפצים, בלוקינג