pae/crimson_leaf_publishing
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix PASS 3: MANDATORY CHECK and DEATH-FORWARD RULE respect author_intent retcon

Browse Source 
The MANDATORY CHECK was rigidly applying DECEASED status from previous
character-state deliverables even when author_intent explicitly retconned
the character as alive. Similarly, the DEATH-FORWARD RULE had no exception
for author-directed resurrection/retcon.

Fixes:
- MANDATORY CHECK: add STEP 2 resurrection check -- if AUTHOR'S INTENT
  explicitly states character is ALIVE, skip DECEASED format entirely
- DEATH-FORWARD RULE: add EXCEPTION clause -- author_intent overrides
  previous state DECEASED status; prose is authoritative source of truth

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Baity
2026-03-25 17:02:48 -04:00
parent baefaa7e6d
commit 92311e9904
1 changed files with 14 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
templates/book_chapter.yml
View File

@@ -320,9 +320,14 @@ steps:
══ MANDATORY CHECK — DECEASED CHARACTERS ══ ══ MANDATORY CHECK — DECEASED CHARACTERS ══
STEP 1: Check PASS 0 above. Find every character listed as "(DECEASED)" or "†" or "DEAD". STEP 1: Check PASS 0 above. Find every character listed as "(DECEASED)" or "†" or "DEAD".
STEP 2: For each such character, use ONLY the short DECEASED format below. STEP 2: RESURRECTION OVERRIDE CHECK — Before marking anyone DECEASED, re-read the
EDITORIAL OVERRIDES (AUTHOR'S INTENT) in PASS 0.
If the author's intent EXPLICITLY states the character is ALIVE, the editor has
retconned the death. Treat that character as ALIVE and use the LIVING FORMAT.
The author's intent is BINDING and overrides all prior state files.
STEP 3: For characters confirmed dead (no resurrection override in author intent), and
who were NOT shown alive in PASS 1 prose, use ONLY the short DECEASED format.
You MAY NOT give them a Location, Physical, Emotional, or Arc field. You MAY NOT give them a Location, Physical, Emotional, or Arc field.
They are DEAD. Dead characters do not have locations. They do not have arcs.
══ DECEASED FORMAT(two lines only) ══ ══ DECEASED FORMAT(two lines only) ══
## [Name] — DECEASED (Ch[N]) ## [Name] — DECEASED (Ch[N])
Established: [one sentence: how they died] Established: [one sentence: how they died]
@@ -374,7 +379,13 @@ steps:
→ Set Permanent: YES (deceased) → Set Permanent: YES (deceased)
NEVER give a deceased character a living Location, Physical, or Emotional field. NEVER give a deceased character a living Location, Physical, or Emotional field.
NEVER assign a deceased character future obligations or arcs. NEVER assign a deceased character future obligations or arcs.
If a character was DECEASED in the previous state, copy their entry forward unchanged. EXCEPTION — AUTHOR RETCON: If the EDITORIAL OVERRIDES (AUTHOR'S INTENT in PASS 0)
explicitly state the character IS ALIVE, this OVERRIDES the previous state.
The editor has retconned the death. Use LIVING FORMAT for that character.
The prose you wrote for this chapter is the authoritative source of truth.
If a character was DECEASED in the previous state, copy their entry forward UNCHANGED
unless (a) they die in THIS chapter's prose (update the cause), or
(b) the author's intent explicitly retcons them as alive.
IMPORTANT: If a relative, sibling, or successor of a deceased character appears in the IMPORTANT: If a relative, sibling, or successor of a deceased character appears in the
prose, they are a NEW character — do NOT create or update the deceased character's entry prose, they are a NEW character — do NOT create or update the deceased character's entry
based on this relative's traits. Keep the deceased entry exactly as it was. based on this relative's traits. Keep the deceased entry exactly as it was.