Keyword search with source provenance. Source matches do not establish canon or character knowledge. No AI provider is required.
KEYWORD ? 7229 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
## 0A. NON-BYPASSABLE CHAPTER PREFLIGHT AND DELIVERY GATES (OWNER-DIRECTED) **Mandatory applicability:** These are blocking operational gates for ANY Apocalypse chapter writing, chapter repair, QA, packaging, or chapter handoff, including requests for one named chapter. A user-supplied chapter number is not evidence t
### G0. Story intent and entry-point gate Resolve requested reading intent and the live arc/Part/chapter map, including framing chapter, chronological flashbacks, opening chapter, existing accepted chapters and handoff order. If Git asks for a whole couple/character arc but names a later chapter, stop and correct the s
### G1. Live Fanfic OS and binding gate Read the Project operating guide, live `01_active_workfiles_index.md`, THIS file, applicable active canon/Part sources and `18_pre_writing_phase_handoff_2026-07-03.md` when planning/handoffs apply. Use explicit immutable Apocalypse project UUID on every Fanfic OS request. Fanfic
### G2. Skill reality gate Resolve requested named ChatGPT chapter writing, chapter QA, and Zero Day skills using the actual installed skill registry and read their real instructions. If a requested skill is unavailable, state `SKILL_UNAVAILABLE` and block the claim of activation and normal final chapter delivery. Read
### G3. Readiness and contract gate Call `planning_readiness_get`, `chapter_get`, `chapter_context_get`, and retrieve the actual current chapter contract and adjacent relevant chapter and Part boundaries. Verify physical opening/exit, POV, time, cast, knowledge/forbidden knowledge, body/logistics, objects/vehicles, chi
### G4. Real predecessor prose gate Before writing a continuation, fetch every relevant earlier **actual accepted prose revision** with `chapter_prose_get` / manuscript text tools, follow all offsets, record acceptance status/revision/hash, and cross-check adjacent handoff. Do not replace this step with plans, summarie
### G5. Full-scene and voice gate Create a private, concrete scene map for required beats, character body/location/POV/knowledge, events, causality and transitions before drafting. Use live `08_characters_voices.md` and `09_characters_and_couples_research.md` to calibrate individuals and relationship voice. Render comp
### G6. Evidence-based final-text QA gate QA the **exact complete final candidate**, including scene causality, arc position, canon, timeline/age, cast, knowledge, props/vehicles, baby/body/logistics, injuries, distinct dialogue, intimacy/grief, Zero Day rules where relevant and adjacent handoff. Every required check h
### G7. Local file and exact-version gate Only build readable TXT/EPUB from the exact final QA-passed candidate; verify actual word count, SHA-256 provenance, headings, navigation/spine, chapter order, text equality, on-disk existence and opening integrity. Never link a nonexistent artifact or claim a false word count.