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

fix: add DEATH-FORWARD RULE to PASS 3 — prevents deceased chars getting living state

Browse Source
This commit is contained in:
Nova_2761
2026-03-25 17:14:27 +00:00
parent 7eb23b6ea0
commit 2efc2ab787
1 changed files with 502 additions and 493 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
templates/book_chapter.yml
View File

@@ -366,9 +366,18 @@ steps:
→ Prefix it: "CARRIED (Ch[N]—unresolved): [secret]" → Prefix it: "CARRIED (Ch[N]—unresolved): [secret]"
This ensures multi-chapter secrets are NOT silently dropped between chapters. This ensures multi-chapter secrets are NOT silently dropped between chapters.
FINAL SELF-CHECK before submitting: Scan your output for Kaelen's name. ══ DEATH-FORWARD RULE ══
If he has a Location, Physical, or Emotional field — delete them. He is dead. Before submitting, scan the PASS 1 prose for any character death events.
If any other character is noted as DECEASED in PASS 0 — apply the same rule. For EACH character who DIES in this chapter's prose OR who was already marked
DECEASED in the previous character-state:
→ Set their Status field to: DECEASED (Ch[N] — [cause])
→ Set Location to: [place of death or burial], not a living location
→ Remove Active obligations and Open loops (replace with Legacy:)
→ Legacy field: one sentence on how their death affects surviving characters
→ Set Permanent: YES (deceased)
NEVER give a deceased character a living Location, Physical, or Emotional field.
NEVER assign a deceased character future obligations or arcs.
If a character was DECEASED in the previous state, copy their entry forward unchanged.
CRITICAL: Keep total output under 3500 characters. NO prose — structured data only. CRITICAL: Keep total output under 3500 characters. NO prose — structured data only.