Fanfic OS / Apocalypse, Now

Source passage search

Keyword search with source provenance. Source matches do not establish canon or character knowledge. No AI provider is required.

KEYWORD ? 6093 results

2.3 Before delivery

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### 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

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### 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

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

## 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

Git-note placement rules

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### Git-note placement rules 1. Chapter-specific note → chapter logic entry and extended chapter summary. 2. Couple/dynamic note → couple skill card and relevant voice/research reference. 3. Character behavior note → character skill card. 4. Global craft note → writing/QA skill. 5. Canon/time/age/death note → canon le

Part 2 source-merge lock after approved contracts 035-059

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### 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

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### 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

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

## 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

Red flags

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### Red flags 1. One-line time jumps: “By the third day...”, “Weeks passed...”, “Over the next months...”, unless followed by or embedded inside real scene work. 2. Montage replacing the first moment of fear. 3. A travel arc summarized as locations instead of lived episodes. 4. A character learning a survival rule off

Required fix

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### Required fix When a red flag appears: 1. stop the shortcut 2. return to body and location 3. identify whose POV owns the moment 4. write the immediate sensory chain 5. show the choice, argument, touch, mistake, or consequence 6. only then move time forward Working sentence: > If the reader can ask “where did th

4.1 Repair-without-lampshading skill

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### 4.1 Repair-without-lampshading skill When Git points out a structural, logic, pacing, or realism problem, do not explain the correction inside the prose. A repair is successful only when the corrected logic disappears into the live scene. The reader should experience the moment through the POV character, not thro

4.2 Category-wide repair skill

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### 4.2 Category-wide repair skill When Git gives two or three examples of a prose problem, treat them as samples of a category, not as an exhaustive checklist. Do not repair only the quoted lines. Run a full pass across the relevant chapter or block for the same failure pattern. For example, if Git points out over-

5. Knowledge-logic skill

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

## 5. Knowledge-logic skill Every scene must pass a knowledge audit. A character may only report what she: 1. physically saw 2. physically heard 3. touched 4. smelled 5. inferred from available evidence 6. learned from another character on-page 7. previously experienced on-page A character may not know: 1. floor n

Required check before finalizing each scene

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### Required check before finalizing each scene Ask: 1. Whose head is this? 2. What does she know at the start? 3. What does she learn in this scene? 4. How exactly does she learn it? 5. What must she still not know? 6. Is the prose accidentally giving narrator knowledge to the POV?

5.1 Human-before-protocol and knowledge-acquisition ladder

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### 5.1 Human-before-protocol and knowledge-acquisition ladder When characters enter a reality that violates ordinary life, begin with the human mind they had before the event. A character does not jump from seeing one impossible thing to using mature survival protocol. For every new danger rule, track four separate

5.2 Geography, travel time, and arrival-order gate

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### 5.2 Geography, travel time, and arrival-order gate Before any call, meeting, rescue, return, or discovery that depends on movement, build a simple route check: 1. starting location, 2. destination, 3. approximate distance, 4. departure order, 5. vehicle or walking speed, 6. known obstacles, 7. elapsed time, 8. wh

5.3 Group-composition continuity

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### 5.3 Group-composition continuity When people leave, travel, shelter, or evacuate as a family group or convoy, later chapters must preserve the composition until an on-page event separates them. 1. Do not rewrite children traveling with parents or guardians as isolated missing children. 2. Track the adults, childr

5.4 Physical continuity gate learned from Chapters 002-003

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

### 5.4 Physical continuity gate learned from Chapters 002-003 Before planning, writing, repairing, or packaging any chapter that carries forward a road, house, vehicle, weapon, map, letter, phone, bag, injury, or relationship fact, build one explicit physical-state ledger. This is not optional bookkeeping. It is the

5.4.1 Vehicle identity and state

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

#### 5.4.1 Vehicle identity and state For every active vehicle, lock: 1. make/type and distinguishing identity, 2. original owner and where it was acquired, 3. who has the keys, 4. current driver and seat placement, 5. fuel level / fuel source, 6. damage and repairs, 7. cargo and what is reachable from each door, 8.

5.4.2 Object custody and transfer

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

#### 5.4.2 Object custody and transfer Every important object needs a visible chain of custody: 1. where it came from, 2. who picked it up, 3. where it is stored, 4. who can reach it during danger, 5. when it changes hands, 6. whether it is left, lost, damaged, emptied, or carried forward. Letters, maps, phones, wea

5.4.3 Environmental resource audit

02_project_skills_and_operational_rules.md ? OPERATIONAL_RULES ? revision 5a88bb6a-ff38-4398-bf8d-2e150d1df79a

#### 5.4.3 Environmental resource audit Before adding a scavenging problem or declaring a shortage, audit the physical place already on-page: * vehicles and keys, * fuel and siphonable fuel, * weapons and ammunition, * clothes, coats and shoes, * food and water containers, * tools, maps and paper records, * medicine

Previous Next