## 11.5 Part 5 — The Road to the Base
Engine: lake camp succeeds enough to stop being enough.
Must track:
1. birth of Kurt
2. emergency leadership
3. scouting and relocation realism
4. camp attack
5. Gideon/Legends return through battle
6. Nate death
7. Seth/Summer still alive at end
8. base not clean at ending
## 11.6 Part 6 — The City Opens Its Gates
Engine: captured base becomes city.
Must track:
1. founding council
2. gates/clinic/storage/docks/school/farm/faith space
3. rescue convoys and intake arcs
4. returning families
5. Avalance children
6. science/ethics
7. Seth/Summer deaths in opening
8. city still imperfect
## 11.7 Part 7 — The City Chooses Life
Engine: strong city chooses whether to stay open.
Must track:
1. values crisis, not another real-estate war
2. returning families
3. wedding
4. later arrivals as values tests
5. rescue roads with living people
6. final civic meaning: civilization chosen despite risk
---
# 12. Chapter summary update template
After an accepted chapter, update the relevant work files using this structure.
```markdown
## Chapter XXX, [Locked English Title]
### Short summary
[2-5 sentence summary for chapter index.]
### Extended summary
[Full paragraph or bullet summary of actual events, emotional move
## Accepted clean prose formula — learned from Chapter 030 QA
This is a global saga-writing rule, not a Vauseman-only rule. Use it before writing or repairing any chapter.
1. **Write the correction as scene, not as explanation.** If a logic/structure note was fixed, the prose must not announce the fix. The reader sho
# 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
## 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.
## 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
# 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.
---
# 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 -->
## מצב עבודה חובה
לפני כל עבודה, חובה לזהות בשקט מה מצב העבודה המבוקש. אם המצב אינו ברור מתוך ההודעה, שאלי שאלה קצרה לפני פעולה.
מצבי העבודה האפשריים:
1. **אבחון בלבד**: קוראים, ממפים ומחזירים דוח. אסור לתקן פרוזה או להחזיר קבצי החלפה.
2. **תיקון נקודתי בלבד**: מתקנים רק שורות שסותרות קאנון, ידע, זמן, חפצים, בלוקינג
## Living-world realism check
If the requested chapter or block includes roads, vehicles, stores, houses, supply runs, scouting, rescue, intake, camp perimeter, gates, depots, farms, bridges, or travel, check the active canon rule that the world is not empty of living people.
Do not plan clean empty roads by default.
## Standalone entry arc check
If the requested chapter or block is an entrance arc for a couple, major character, family, or group, plan it as a standalone fanfic arc that could be read up to the meeting point with the main group.
The plan must include:
1. old-world life and relationship texture,
2. Day Zero through
## מקור קריאה חובה
את כל המסמכים אתה לוקח מהשיתופיות בפרויקט או מהקבצים שהועלו בשיחה הנוכחית, לא מהזיכרון שלך, לא מקבצים לוקאליים ישנים, ולא מהנחות.
קודם קרא את הקבצים הפעילים:
1. `active_workfiles_index.md`, אם קיים.
2. `canon_ledger.md`.
3. `worklist.md`.
4. `parts_summaries.md`.
5. `chapters_summaries.md`.
6. `ch