Keyword search with source provenance. Source matches do not establish canon or character knowledge. No AI provider is required.
KEYWORD ? 6093 results
# 01_active_workfiles_index Status: ACTIVE SOURCE-TRUTH INDEX for the cleaned Apocalypse, Now package. Approved structure: 17 active story/source markdown workfiles, plus one active pre-writing stage handoff file. Working language: Hebrew instructions and planning, English prose output.
## Absolute source-of-truth rule 1. The only active source files are the files listed in this index, plus any file Git explicitly marks active in the current conversation. 2. Generated TXT, EPUB, ZIP, QA reports, repair files, chapter drafts, skeleton drafts, or any file with suffixes like `_v1`, `_v2`, `_repair`, `_p
## Active file list, 18-file package | # | Active file | Role | |---:|---|---| | 01 | `01_active_workfiles_index.md` | Active workfiles index. | | 02 | `02_project_skills_and_operational_rules.md` | Project skills and operational rules. | | 03 | `03_prompts_planning_writing_repair_package.md` | Prompts planning writin
## Required reading order by task
### Every Apocalypse, Now project response 1. `01_active_workfiles_index.md` 2. `02_project_skills_and_operational_rules.md` 3. Any specific active file directly relevant to Git's current question. 4. During the pre-writing phase, also check `18_pre_writing_phase_handoff_2026-07-03.md` when the task concerns planning
### Chapter planning / skeleton 1. `01_active_workfiles_index.md` 2. `02_project_skills_and_operational_rules.md` 3. `03_prompts_planning_writing_repair_package.md` 4. `04_global_worklist_methodology_and_handoff.md` 5. `05_canon_ledger_and_word_count_audit.md` 6. `06_saga_parts_chapter_summaries_and_bridge.md` 7. `07_
### Chapter writing Same as planning, plus any accepted locked skeleton or accepted prose file Git explicitly marks active.
### QA / repair Same as writing, plus the chapter draft Git asks to check or repair.
### Packaging / EPUB / summaries 1. `01_active_workfiles_index.md` 2. `02_project_skills_and_operational_rules.md` 3. `03_prompts_planning_writing_repair_package.md` 4. `05_canon_ledger_and_word_count_audit.md` 5. `06_saga_parts_chapter_summaries_and_bridge.md` 6. the relevant part file 7. accepted prose files Git exp
## Post-chapter update rule After Git accepts a chapter as usable, update the relevant active sources or prepare replacement patches for them, according to Git's instruction: 1. short chapter summary, 2. extended chapter summary, 3. what the chapter gave the saga, 4. what future chapters must carry forward, 5. knowle
# 02_project_skills_and_operational_rules Status: ACTIVE PROJECT SKILLS LAYER, approved by Git for insertion into the Apocalypse, Now active workfiles package. Purpose: reusable operational skills for all Apocalypse, Now project responses, writing, QA, repair, packaging, character/couple consistency, and post-chapter
# 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. Chapter lifecycle skill Every chapter moves through this lifecycle.
### 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.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.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