### G8. Owner and persistence gate
All writing begins as LOCAL_REVIEW, and files must not be submitted into Fanfic OS or treated as accepted, canon, manuscript current/final or synchronized until Git has explicitly reviewed and approved the **exact complete version** and authenticated owner workflow verifies it. Prose
# Apocalypse, Now — Project Skills
Status: ACTIVE PROJECT SKILLS LAYER, approved by Git.
Working language: Hebrew instructions, English prose output.
Scope: all parts, all chapters, all couples, all recurring characters.
Important: this file is active once Git uploads/replaces it in the project active files. It
## 0. Purpose
This file turns the project files and Git's recurring notes into reusable operational skills.
It is not a replacement for:
1. `01_active_workfiles_index.md`
2. `05_canon_ledger_and_word_count_audit.md`
3. `06_saga_parts_chapter_summaries_and_bridge.md`
4. `08_characters_voices.md`
5. `09_characters_and
## 1. Source-of-truth skill
Before any planning, writing, QA, repair, packaging, or summary update:
1. Read `01_active_workfiles_index.md`.
2. Use only files listed there, plus files Git explicitly uploads or approves in the current task.
3. Treat generated TXT, EPUB, ZIP, markdown, or repair files as delivery artifa
### Required opening check
For every task, quietly identify:
1. requested work mode: planning / writing / QA / repair / packaging / summary update
2. part and chapter range
3. active files needed
4. adjacent chapters needed for continuity
5. relevant couples and characters
6. current prose source, if any
7. expected
### 2.1 Before writing
A chapter cannot be written from vibes alone. Before prose, confirm:
1. chapter role
2. physical opening
3. physical ending
4. chapter timeline
5. physical cast
6. characters active by memory, object, absence, or voice
7. forbidden characters
8. knowledge map
9. logistics map: water, food, medi
### 2.1.0 Owner-selected entry scale
Standalone entry depth is a default, not a requirement to override the owner's specific scope. The combined bus group has four shared chapters; Cosima/Delphine, Calzona and Sarah/Chuck have one each (Sarah/Chuck relatively short); Lois/Clark have half a chapter; Joey/Pacey and Vero
### 2.1.1 Mandatory dialogue and couple voice calibration
Before writing or repairing a chapter with meaningful dialogue, do not rely on a generic sense of wit, chemistry, or banter. Calibrate the characters and the relationship in frame.
Required source pass:
1. Read `08_characters_voices.md` for every speaking cha
### 2.1.2 Relationship-legibility on first meaningful entry
When a character first becomes meaningfully active on page, the reader must be able to infer the human map that matters to the scene without receiving a cast-list paragraph.
Show relationship through live evidence such as:
1. household familiarity, keys, ro
### 2.2 During writing
Write full English prose, not outline-language.
A scene must contain at least one concrete change:
1. knowledge changes
2. trust changes
3. relationship changes
4. physical condition changes
5. location/shelter changes
6. logistics changes
7. danger changes
8. a choice becomes irreversible
A
### 2.2.1 Death, grief, and continuing-life continuity
A death, confirmed loss, apparent death, or irreversible separation is not complete when the event scene ends. It must continue to alter the living characters across later scenes and chapters.
Mandatory rules:
1. **No emotional reset.** A character may drive, re
### 2.2.2 Death-cause variety and continuing danger
Do not make every meaningful death a heroic sacrifice. Across the saga use grounded variety: bites, a second's mistake, accidents, drowning, fire, falls, structural collapse, illness, infection, injuries the old world could treat, human violence and sometimes sacrifi
### 2.3 Before delivery
Perform QA before returning a file:
1. canon
2. timeline and ages
3. who knows what
4. living-dead rules
5. living-people realism
6. scene fullness
7. no lazy montage where a scene is required
8. character voice
9. dialogue and couple voice differentiation, including the tag-removal and couple
### 2.4 After chapter delivery, mandatory update layer
After every accepted chapter, update the relevant working summary layer.
Do not wait until the end of a part.
For each accepted chapter, add/update:
1. **Short chapter summary** for `06_saga_parts_chapter_summaries_and_bridge.md`.
2. **Extended chapter summary*
## 3. Git-note capture skill
Whenever Git gives a note, correction, complaint, or taste instruction, do not treat it only as a one-time fix.
Classify it into one of these types:
1. canon lock
2. chapter-specific repair rule
3. global writing rule
4. couple/character voice rule
5. timeline / age rule
6. logistics rul
### Part 2 source-merge lock after approved contracts 035-059
During the Part 2 pre-writing pass, Git identified that the older `part2_chapter_logic_map.md` held chapter-level detail that had been compressed out of the cleaned active file. For Part 2 chapter contracts 035-059, the usable detailed material from that lo
### Robin Buckley perception / solution lock
Robin is not only air in the room, comic relief, morale, or the keeper of Steve signs. She often notices the small physical detail other people have filtered out: a change in engine sound, a rhythm in road noise, an odd echo, a repeated word, a sign placed wrong, a smell, a
## 4. Scene-density skill
Git's locked preference: chapters must breathe.
A chapter targeting 10,000–15,000 words cannot be built from 7–8 thin scenes unless those scenes are deliberately long, layered, and structurally dense. For major entrance arcs, the default should usually be more scenes, more stations, more emb