decisions/SPINE_LIVING_REVISION_LOG.md
This file is the declared repo-native continuation of the Living Revision Log defined at [SRC: T99_Story_Spine_Build_Logic # 7.5 Living Revision Log]. The SSBL is frozen under _source/ and its in-doc §7.5 log block can no longer accumulate entries; without a live continuation, Protocol 9 log alignment [SRC: T99_Story_Spine_Build_Logic # 9.9 Protocol 9] would deadlock against a read-only file. Every Phase 6 chapter session reads this file at Step 6 and applies its latest naming and alignment at Step 9 structured-field scatter, exactly as §7.5 specifies for the in-doc log [SRC: T99_Story_Spine_Build_Logic # Step 6 — Load Continuity Anchor].
This log starts empty, matching the v3.0 lock state of the in-doc §7.5 log [SRC: T99_Story_Spine_Build_Logic # 7.5 Living Revision Log]. Predecessor entries do not carry forward: v2.3 Entries 1-17 were absorbed into canonical T1 and T0 docs at Phase 5, and Entries 18-21 route to canonical docs per Appendix B [SRC: T99_Story_Spine_Build_Logic # Appendix B — Phase 5M Migration Queue]. Verification that Entries 18-21 actually landed in their target docs is a separate work item (ROADMAP 0.B.7) [SRC: ROADMAP # 0.B Cascade runbook]; until verified, the Appendix B fallback binds — an unmigrated entry surfaces at an ad-hoc Stage 2 canonical question review at the chapter where its content first applies, regardless of that chapter's hard-line status, because the SSBL's Migration Execution text itself routes Entries 18-21 to Stage 2 at non-hard-line Ch 11 and thereby authorizes the slot (runbook Step 8 carries the matching exception) [SRC: T99_Story_Spine_Build_Logic # Migration Execution].
At cascade close the accumulated log is read in full by Final Consolidation, its deltas batch-apply to canonical docs, and this file archives per §11.6 [SRC: T99_Story_Spine_Build_Logic # 11.6 Final Consolidation Protocol].
Entries append below this line. Empty at v0.1 creation.
--- LIVING REVISION LOG ---
[Chapter CH_02 session, 2026-07-04] Surface: the v1.0 baseline entries carry flee-by-design or unbeatable bosses (Ch 2: corrupted-dukun chase-escape plus a Cave Bear forced-run), authored before ruling 5 (L1 action-packed and playable every chapter) and the BOSS_PERSONAS bible. Resolution: rebuilt-fresh chapters convert each v1.0 flee-by-design boss into a real playable ruling-5 boss per BOSS_PERSONAS — at Ch 2 the deceptive hunter becomes the playable main boss Rangku Wera (win breaks the corruption and frees the man), and the corrupting dukun becomes a materialized refuse-the-bargain sub-encounter; the Cave Bear tutorial disposition is flagged to Josh. The v1.0 flee-by-design framing is inspiration only and does not carry forward. Reason: Josh's 2026-07-04 rebuild-fresh ruling and ruling 5 supersede the v1.0 boss model, and BOSS_PERSONAS is the ruled boss canon [SRC: BOSS_PERSONAS] [SRC: CANON_AUDIT]. Applies to every rebuilt chapter Ch 2-11 carrying a v1.0 flee-by-design boss; read at Step 6 and honored at the Boss-grid scatter.
[Chapter CH_09 session, 2026-07-07] Surface: the ACTIVE registry name for the Ch 9 boss (NW_0008 and CHAR_0063, Abuna Giyorgis) carried a CVD §17.1 hard-line problem, the Ethiopian Orthodox patriarchal Abuna title plus a collision with the revered saint Abba Giyorgis of Sägla, both on a villain, and the linked scribe row CHAR_0066 re-surfaced the same abuna-giyorgis reference. Resolution: Josh ruled to adopt the §17.1-safe reframe Liqä-Mäzämmir Gäbrä-Ṣəḥuf, a real non-patriarchal Ge'ez master-cantor and scriptorium office plus a constructed Servant-of-the-Writing name that is neither the patriarchal title nor a saint's name; the registry was swept registry-wide, NW_0008 operative_name and CHAR_0063 name, role, and faction and CHAR_0066 faction and extensions, with the high-priesthood descriptors aligned to the master-cantor register, all in the Ch 9 commit. A parallel out-of-scope §17.1 flag was recorded for the future Ch 15 build and refined by a separate read-only review: CHAR_0109 rows the real historical figure Meryre, High Priest of the Aten (Amarna Tomb 4), as a Velheim antagonist boss and needs a §17.1-safe reframe when Ch 15 is built, and BOSS_PERSONAS already pre-supplies the title-only fallback The High Priest of the Erasure; the real adjacent antagonist to co-review is CHAR_0110 (Khabash, a Velheim secondary-boss), while CHAR_0111 (Hapuseneb) is a teacher and counterpoint with alignment none and is not an antagonist. Resolution on the Ch 15 rows is PENDING AUTHOR DECISION at the Ch 15 build. Reason: CVD §17.1 forbids placing a sacred patriarchal title or a saint's name on a villain and wins over a registry name, and supersession must sweep every cross-reference in the same commit per the wiring doctrine [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Character_Index @ CHAR_0063].
[Range Review Ch 2-11, 2026-07-07] Grid: Continuity — familiars_present carry-forward. Drift: the familiars_present end-state field inconsistently carries bonded rotational familiars — Kira (F1, Ch 4), Khan (G1, Ch 5), and Bodhi (G2, Ch 6) are named as bonding in their chapters' mechanical anchors but dropped from the carry-forward chain from Ch 8 on, while Kasa (W5), Msafiri (F3), and Desta (G3) are carried, with no stated rule for the asymmetry. Resolution: the canonical rule is that Shell (W1) is the sustained-bond familiar always present, and every other familiar is ROTATIONAL — once bonded it accumulates into the available roster and rotates through the active slots per T3_Familiars_Named, so the familiars_present carry-forward normalizes to Shell plus the full accumulating set of bonded rotational familiars (Octopus/Kira Ch 4, Khan Ch 5, Bodhi Ch 6, Murugan Ch 7, Kasa/Msafiri Ch 8, Desta Ch 9-10), the exact per-slot mechanics still deferred to the T0_Familiar_Registry population. The mechanical-anchor familiar rows in every chapter are already correct; this normalizes the prose carry-forward summary and applies at the next scatter and at Final Consolidation. Reason: the rotational-bond accumulation is T3_Familiars_Named canon, so the carry-forward must reflect the accumulating bonded set rather than an unexplained subset [SRC: T3_Familiars_Named # Shell] [SRC: T3_Familiars_Named # Kira]. PENDING AUTHOR CONFIRMATION at RR-12 sign-off.
[Range Review Ch 2-11, 2026-07-07] Grid: Cultural / Quality / Thread-Coverage — RR-12 decision batch. Drift: the RR-12 judgment grids surfaced a batch of cross-chapter items for author decision (none a blocker; all four judgment grids PASS_WITH_NOTES and the five machine grids PASS). Resolution: the full ratification report and the enumerated decision batch are filed at docs/spine/range_reviews/RR_12.md, which routes each item to fix-now, flag-for-Josh, or accept; the OPEN cardinal flags (Ch 10 /Kaggen §17.1 naming plus the /Xam//Gwi/!Kung multi-people reconciliation, the Ch 11 Kenge/Moko real-person naming and the Bwiti reproduce-vs-reference pin, the Ch 8 Sayyid-honorific consistency with the ruled Ch 9 Abuna precedent, the SSBL Appendix-B Entry-18 recognition-register reconciliation, the Ch 10/11 sub-boss population against the 2-4 build-target, and the Ch 11 Thread-17 and Ch 3 Thread-11 RCM-vs-Grid divergences) are held for Josh at the RR-12 sign-off. Reason: a Range Review ratifies the window's drafted entries and batches the open decisions for the author rather than resolving cardinal canon unilaterally [SRC: T99_Story_Spine_Build_Logic # 7.4 Grid Revision Trigger Protocol]. PENDING AUTHOR DECISION at RR-12 sign-off.
[Range Review Ch 2-11 RR-12 apply, 2026-07-07] Grid: Cultural §17.1 — Ch 10 shaman-elder name supersession (Kaggen to Kxao). Drift: CHAR_0071 carried the /Xam creator-deity name /Kaggen on a mortal Ju|'hoansi NPC, the same §17.1 deity-name-on-a-mortal class as the Ch 9 Abuna problem, and the _source T3_Supporting_Characters §3.10 and §5.6 had encoded that migration-era name plus an un-sourced spiritual-name-inheritance basis that failed HL_0002. Resolution: the live layer is reframed to Kxao, an attested Ju|'hoan (!Kung) personal name borne by n/um master-healers in the primary ethnographic record (Katz, Boiling Energy 1982), matching the chapter's !Kung kia and n/um register; the live Character_Index CHAR_0071, docs/spine/CH_10.md, and BOSS_PERSONAS BE_0010 are swept, and /Kaggen reverts to a /Xam deity referenced only as cited folklore. The _source T3 §3.10 and §5.6 are updated in place to Kxao with the attested Katz (Boiling Energy 1982) grounding, so the name is now aligned across the live and source layers. Reason: CVD §17.1 and HL_0002 forbid a sacred deity-name on a mortal and require primary-source grounding, and the living-source doctrine carries the correction in place across both the live and source layers, exactly as the Ch 9 Abuna reframe was handled [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Character_Index @ CHAR_0071]. Applied in the RR-12 commit.
[Range Review Ch 2-11 RR-12 apply, 2026-07-07] Grid: Cultural §17.1 — Ch 10 San de-flattening and the bushman exonym. Drift: docs/spine/CH_10.md flattened three distinct self-naming San peoples under one San label, and the Xu (CHAR_0074) framing used the contested colonial exonym bushman, which the frozen _source T3 Xu row also carries. Resolution: each depicted practice is reattributed to the people canon already attests for it — /Xam (rock-art entoptic panels per Bleek-Lloyd, the /Kaggen deity folklore, Blombos ochre), //Gwi (the healing-dance n/um oracle), and Ju|'hoansi/!Kung (the shaman-elder's kia trance, N!ae's arrow-poison, Xu's tracking) — and the CHAR_0074 exonym is replaced with the Kung (Ju|'hoansi) namesake naming tradition across the live Character_Index and CH_10.md; the four frozen Bushman Folklore and Bushman Dictionary bibliographic titles are retained as real published citations, and the frozen _source T3 Xu row is superseded in the live layer, not edited. Reason: CVD §17.1 and HL_0006 require each culture's own self-naming and prohibit stereotyped descriptors, and every reattribution is registry-attested rather than invented [SRC: T0_Hard_Lines @ HL_0006] [SRC: T0_Character_Index @ CHAR_0074]. Applied in the RR-12 commit.
[Range Review Ch 2-11 RR-12 apply, 2026-07-07] Grid: Cultural §6.2/§17.1 — Ch 11 Kenge/Moko real-individual name reframe supersession. Drift: CHAR_0081 (Kenge) is named for a real individual in Turnbull's Mbuti ethnography and CHAR_0078 (Moko) sits one letter from Turnbull's real Mbuti elder Moke yet is tagged Baka; both were given fully invented teaching-NPC personas in the _source T3_Supporting_Characters §3.11, the barred treatment for a living-memory private individual from a protected community at an elevated-care chapter. Resolution: both are reframed to constructed in-register working names — CHAR_0081 to a Bila-Bantu-register form (illustrative first form Apenda) and CHAR_0078 to a Baka-register form (illustrative first form Ndumu); final orthography is set by the standard NAMING_METHOD deep-research pass, the decision to reframe made now. The live Character_Index CHAR_0078 and CHAR_0081, docs/spine/CH_11.md, BOSS_PERSONAS BE_0011, RR_12.md, and the RR-12 in-flight doc are swept; the _source T3 §3.11 is updated in place to Apenda and Ndumu (each carrying the working-name and attested-register note), so the names are now aligned across the live and source layers. Only Kenge and Moko require reframe; Ekila, Bongo, Bokumbo, Iyenge, and Mbomio are swept-checked and read as plausible constructed forms (Ekila is a common-noun Baka cosmological concept, not an individual). If Josh wants the Turnbull homage retained he can veto — a confirm, not a story fork. Reason: the repo naming discipline (a real named person is lawful only documentary-only or as a constructed name) and CVD §6.2 elevated care bind, and the reframe changes no story content [SRC: T0_Character_Index @ CHAR_0081] [SRC: T0_Hard_Lines @ HL_0002]. Applied in the RR-12 commit.
[Range Review Ch 2-11 RR-12 apply, 2026-07-07] Grid: Continuity / SSBL Appendix-B — recognition-register ruling (Entry 18). Drift: the SSBL §9.6 Ch-8 block attributes the family's knowledge of the protagonist to a Ch 2 pirate-captain reveal plus a Ch 5 Madan Singh broker description-circulation, a v2.3-draft artifact the rebuilt-fresh Ch 2-11 window does not carry. Resolution: the rebuilt CONCEALMENT_WITH_HOSTILE_RECOGNITION escalation is the canonical recognition-register — origin Ch 5 Datu Siahaan FAMILY_BRIEFED (NW_0003), first hostile recognition Ch 8 Sayyid FULLY_AWARE (NW_0007), recognition-via-land first-instance Ch 11 Mbuti (Apenda, CHAR_0081) — with Ch 2 as FIRST_CONCEALMENT (NW_0001 UNAWARE, VRIL_STANDALONE), not a recognizer beat and no pirate-captain retrofit. The stale SSBL phrase is reconciled in the live layer (Madan Singh is the Ch 5 counter-intelligence mid-boss, not the briefing vector); the SSBL 9.6 text is a T99 operational doc outside this T1/T3/RCM in-place pass and is left for a separate living-source update, its Entry-18 no-prior-chapter-rewrite clause already satisfied. Reason: the ACTIVE Antagonist_Network awareness tiers, the three rebuilt spine entries, and Entry 18's no-rewrite clause converge, so canon determines the answer [SRC: T0_Antagonist_Network_Registry @ NW_0003] [SRC: T99_Story_Spine_Build_Logic # Migration Execution]. Applied in the RR-12 commit.
[Range Review Ch 2-11 RR-12 apply, 2026-07-07] Grid: Thread-coverage — Ch 3 Thread-11 RCM-versus-Grid reconcile. Drift: the _source RCM Ch 3 Verified-canon clause had implied a distinct scored Ch-3 Thread-11 corrupted-trickster anchor, but the threads-domain owner T1_Threads_22 scores the Flores dukun-trickster at Ch 2 only (next Ch 12) and the T0_Thread_Grid matches the owner. Resolution: no Thread_Grid row is added; the Dukun's-Twisted-Proverb is the Ch-2-anchored Flores corrupted-trickster continuing, and docs/spine/CH_03.md's RR-12 flag is marked RESOLVED. The RCM clause is updated in place to read as the Ch-2-anchored Flores corrupted-trickster expressing in the Ch-3 proverb scene, with no separate Ch-3 grid cell scored, so the RCM and the Thread_Grid are now aligned across the live and source layers. Reason: the authority hierarchy places the threads-domain owner over RCM substrate on a thread-scoring question, so adding a grid row would over-score against the owner and invent canon [SRC: T1_Threads_22_Master_References] [SRC: T1_Research_Corpus_Master # Ch 3]. Applied in the RR-12 commit.
[Range Review Ch 2-11 RR-12 apply, 2026-07-07] Grid: Continuity — familiar-rotation rule application (confirms the 2026-07-07 pending entry above). Drift: the familiar-rotation rule filed 2026-07-07 (Shell sustained; all other familiars rotational and accumulating into the available bonded roster) was PENDING AUTHOR CONFIRMATION and the Ch 11 familiars_present carry-forward still carried a partial subset. Resolution: the rule is applied to docs/spine/CH_11.md's End-state carry-forward, which now carries the full accumulating bonded roster verified against the Ch 4-11 mechanical anchors — Shell (W1, sustained) plus rotational Kira (F1, Ch 4), Khan (G1, Ch 5), Bodhi (G2, Ch 6), Kasa (W5, Ch 8), Msafiri (F3, Ch 8), and Desta (G3, Ch 9-10); the Sanur Octopus (W4) and the Murugan peacock (F2) remain deferred and gated, per-slot mechanics deferred to the Familiar_Registry. The remaining chapters' carry-forward summaries normalize by the same rule at the next scatter and at Final Consolidation. Reason: rotational-bond accumulation is T3_Familiars_Named canon, so the carry-forward must reflect the accumulating bonded set [SRC: T3_Familiars_Named # Shell]. Confirmed and applied in the RR-12 commit.
[Chapter CH_12 session, 2026-07-08] Grid: Cultural §17.1 — Ch 12 West Africa two-NPC /Kaggen-class name reframe. Drift: the Ch 12 build carried two names that place a sacred or real proper name on a mortal NPC at an elevated-care chapter. CHAR_0089 was rowed Priestess Dahndah, a near-doubling of Dan (Dangbe), the Ouidah serpent-Vodun deity the priestess herself serves and the source of the Ch 42 Damballa payoff — the same §17.1 deity-name-on-a-mortal class as the Ch 10 /Kaggen and Ch 9 Abuna problems, and the _source T3 §3.12 itself flagged the name as framework-level pending Phase 6 specific-name pinning. CHAR_0088 was rowed Nanisca, a name both attested for a real Dahomey ahosi in Jean Bayol's 1889 account and carried by the fictional general of the 2022 film The Woman King, so it dressed a thinly-attested real individual (and a pop-culture character) in an invented court-captain persona — the barred treatment for a real named person, per the Ch 11 Kenge/Moko precedent. Resolution: both are reframed to constructed Fon-register working names — CHAR_0089 to Priestess Senami (a personal name carrying no serpent-deity element) and CHAR_0088 to Gbetosi (built on the Agojie's own huntress self-designation, gbeto) — with final orthography set by the standard NAMING_METHOD deep-research pass, the decision to reframe made now. No story content changes: the Dan and Ayida-Weddo tradition, the python-colony communion, the cross-species Animal Communication home base, and the Burton/Forbes/Skertchly primary-source Agojie framing all stand. The live Character_Index CHAR_0088 and CHAR_0089, docs/spine/CH_12.md, docs/proposals/BOSS_PERSONAS.md BE_0012, and the _source T3_Supporting_Characters §3.12, §6.1, and Drift-A note are swept in place so the names are aligned across the live and source layers. If Josh prefers to retain either name he can veto — a confirm, not a story fork. Reason: CVD §17.1 and HL_0002 forbid a sacred deity-name or a real named individual on a mortal NPC persona and require primary-source grounding, and the living-source doctrine carries the correction in place across both layers, exactly as the Ch 9 Abuna and Ch 10 /Kaggen reframes were handled [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Character_Index @ CHAR_0089]. Applied in the CH_12 build (tree left dirty for the lead to gate and commit; Josh confirms at RR-22).
[Chapter CH_12 session, 2026-07-08] Grid: Thread-coverage — Ch 12 Ifa multi-thread alignment and a Thread-14 Threads_22-versus-Grid reconciliation. Drift: the CH_12 draft internally contradicted itself on the Ifa 256 Odu threading (the Threads-advancing block routed Ifa to Threads 12 and 17 and excluded Thread 7, while the Decisions block claimed Ifa at Threads 7 and 12), and T1_Threads_22 scores a Ch 12 Thread-14 Blood-and-Sacrifice anchor (Yoruba and Dahomean animal-sacrifice, sensitivity-flagged) plus the live Character_Index rows the Agojie captain at thread_involvement 14, yet the T0_Thread_Grid and the Chapter_Index thread_anchors_complete score seventeen threads without a Ch 12 Thread-14 cell. Resolution: the Ifa 256 Odu is stated consistently as a multi-thread anchor — Thread 7 numerology (the two-to-the-eighth binary mathematics, grounded in CHAR_0086 thread_involvement 7), Thread 12 divination, and Thread 17 encoding — in the spine and in the _source T3 §3.12 parenthetical, killing the internal contradiction; the Thread-14 anchor gap is documented as a reconciliation, keeping the scored seventeen-thread set consistent across the spine, Chapter_Index, and Thread_Grid to avoid an unaudited mid-build canon-graph change, with the THREAD_14/CH_12 cell recommended for the RR-22 grid pass where thread-scoring changes belong; the animal-sacrifice substrate is present as respectfully-referenced L2 lore and never a combat target. Reason: the threads-domain owner T1_Threads_22 and the registry ground the Ifa multi-thread routing, and a Range Review is the proper venue for adding a scored grid cell rather than a mid-build scatter [SRC: T1_Threads_22_Master_References # Thread 14] [SRC: T0_Character_Index @ CHAR_0086]. Applied in the CH_12 build.
[Chapters CH_34 / CH_35 / CH_36 pointer, 2026-07-08 wiring-audit] Surface: docs/proposals/L3_SEEDS.md holds paste-ready HL_0047 Layer-3-surfacing appends for Ch 34 (Canary Islands / Guanche), Ch 35 (Cape Verde / Kriolu), and Ch 36 (Mid-Atlantic / Trade-10 navigation) — RCM Verified-canon prose, a proposed T0_Vril_Site_Registry row VS_CH34_001 (Risco Caído / Cuatro Puertas), and Chapter_Index time_fluctuation_range cells — but it was orphaned from the build loop, with no consumer referencing it and the cascade only at Ch 12. Resolution: at each of these chapter builds, read L3_SEEDS.md at Step 6 and apply its appends only after Josh resolves the five [DECISION NEEDED - JOSH] flags in that doc (the storage-target convention, the VS_CH34_001 row specifics, the three time_fluctuation_range windows, and the Ch 35/36 Component assignments) and after the standing fresh-context critic gate passes; the seeds are Josh-decision-gated and are not applied pre-cascade. Reason: HL_0047 requires a per-chapter Layer-3 mechanical or environmental surfacing, the L3_SEEDS grounding traces each seed to resolvable [SRC:] canon at substrate-perception intensity without promoting any chapter to a vril-amplification anchor, and the wiring doctrine requires every built artifact to be referenced by its consumer [SRC: T0_Hard_Lines @ HL_0047] [SRC: T1_Research_Corpus_Master # Ch 34]. Scheduled in docs/MASTER_ENHANCEMENT_PLAN.md tracked apply-items. PENDING AUTHOR DECISION at the Ch 34/35/36 builds.
[Chapters CH_10 / CH_57 pointer, 2026-07-08 wiring-audit] Surface: docs/proposals/CH10_57_SIGNIFICANCE.md designs the relief-as-revelation significance and per-layer value for the two antagonist-family-absent chapters (Ch 10 East African Rift Valley, Ch 57 Aboriginal Australia) per Josh's 2026-07-08 ruling that neither is a dead chapter, but it was orphaned from the build loop — CH_10 was built without it, and nothing pointed the future Ch 57 build at it. Resolution: the Ch 57 spine build consumes the proposal's significance framing and three-layer beats, and Ch 10 takes the retrofit at its next Range-Review uplift; the proposal is design-layer only and invents no canon, so it applies as framing on Josh's sign-off, not as a canon edit. Reason: the ruling makes both chapters load-bearing on all three layers and weave into the 79-node progression, and the wiring doctrine requires the design to be consumed by its build rather than stranded in the proposals directory [SRC: T1_CVD_Creative_Vision_Document # 3] [SRC: T99_Story_Spine_Build_Logic # 7.5 Living Revision Log]. Scheduled in docs/MASTER_ENHANCEMENT_PLAN.md tracked apply-items. PENDING AUTHOR SIGN-OFF at the Ch 57 build and the Ch 10 uplift.
[Chapter CH_13 session, 2026-07-08] Grid: Cultural §17.1 — Ch 13 South Africa naming reframes and orthography deferrals. Drift: the Ch 13 build (elevated care) carried names needing the §17.1 real-person and click-orthography passes. CHAR_0096 was rowed Dawid Kruiper-Archetype, and Dawid Kruiper was a real, revered ‡Khomani San leader who died in 2012 — the barred treatment for a real named individual per the Ch 11 Kenge/Moko and Ch 12 precedents. The San /Gwi autonym appeared inconsistently as both single-click /Gwi and double-click //Gwi (different phonemes) inherited from an inconsistent RCM source. CHAR_0097 Maria Stuurman pairs a constructed given name with Stuurman, the surname of the real early-1800s Khoi resistance leaders Klaas and David Stuurman. Resolution: CHAR_0096 is rendered as an explicitly-constructed ‡Khomani-tracker archetype-echo with the constructed working name ‡Nabe (the real leader honored as himself and not recast, carrying no real-person identity); the /Gwi orthography is normalized in docs/spine/CH_13.md to the single-click Gǀwikwe autonym; and Maria Stuurman is retained with a flag. All three — the ‡Nabe final orthography, the /Gwi click form, and the confirmation that Maria Stuurman does not read as dressing the real Stuurman resistance family — are carried to the standard NAMING_METHOD deep-research pass; /Xoana, /Una, Mthembu, and Susanna September are swept-clean constructed in-register forms. No story content changes. Reason: CVD §17.1 and HL_0002 forbid a real named individual or a sacred name on a mortal NPC persona and require each culture's own self-naming, and the repo naming discipline reframes now with final orthography set at the NAMING_METHOD pass, exactly as the Ch 9-12 reframes were handled [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Character_Index @ CHAR_0096]. Applied in the CH_13 build (Josh confirms at RR-22).
[Chapter CH_13 session, 2026-07-08] Grid: Thread-coverage / Cross-cultural — Ch 13 Shona Thread-1 term deferral and the Ch 8-to-Ch 13 gold-trade edge. Drift: the Great Zimbabwe SPREAD raises the Shona mhondoro (lion-spirit medium) and mudzimu (ancestral spirit) tradition as a candidate Thread-1 vril-parallel catalog term, but it is not among the five Thread-1 terms Josh confirmed 2026-07-08 (kami/mana/mu/orenda/wakȟáŋ); and the Ch 8-to-Ch 13 Indian-Ocean gold-trade knowledge-transmission link (closing the Ch 8 gold-trade loop) is genuine RCM substrate added by the coverage rescope but carries no T0_Cross_Cultural_Link_Graph row yet (LINK_0142 is the distinct South-Africa-to-Egypt unity weaving toward Ch 15, not this edge). Resolution: the Shona mhondoro/mudzimu term is carried as substrate in the spine and NOT coined as a Thread-1 catalog term (do-not-invent; pending Josh naming confirmation per T1_Threads_22), the 22-thread count untouched; and the gold-trade edge is authored under the CROSS_CULTURAL_WEAVE Class-2 knowledge-transmission + CIVMARK:CH_13 convention as a [POPULATE→T0_Cross_Cultural_Link_Graph] edge, to be rowed at the next Cross_Cultural_Link_Graph population pass. Reason: Thread naming and count are cardinal canon (Josh's call) and a mid-build link-graph row addition belongs to a deliberate population pass, not an ad-hoc scatter, so both are carried grounded rather than invented [SRC: T1_Threads_22_Master_References # Thread 1] [SRC: CROSS_CULTURAL_WEAVE]. Applied in the CH_13 build; PENDING AUTHOR CONFIRMATION (Shona term) at RR-22 and link-row population at the next link-graph pass.
[Chapter CH_14 session, 2026-07-08] Grid: Cultural §17.1 — Ch 14 Nubia attested-royal-name reframe sweep and the Kxao-rule theophoric nuance. Drift: the Ch 14 (Meroitic Kush) build carried a roster dense with attested Kushite royal names on invented NPC personas, the barred treatment per the Ch 9 Abuna / Ch 11 Kenge-Moko / Ch 12 Nanisca / Ch 13 Dawid-Kruiper precedents, and the pack itself flagged CHAR_0101 Arikankharor (an attested king) cast as the family-aligned antagonist — the strongest form of the Liqä-rule concern. Resolution: the boss is reframed to the title-forward player-facing handle The Priest-King of the Absorbed Script (the pack's named safe fallback; a constructed throne-name deferred to NAMING_METHOD), and the real Arikankharor is honored as documented history in the civilizational-marks (L2) layer. The ally-queen CHAR_0102 Amani'sakheto (echoing the real Amanishakheto / the Amanirenas-archetype) is reframed to the attested queen-title handle the Kandake (audit-only ally, never a boss); CHAR_0104 Netekamani (≈ the real king Natakamani) → the constructed overseer Pisakar; CHAR_0107 Seqnetepibre (an Egyptian prenomen form) → the constructed Amun high-priest Nebkematef; CHAR_0103 Makouria (a medieval Nubian KINGDOM-name mis-carried as a person) → a constructed iron-master personal name; CHAR_0106 Amunnanhi (Shebitqo-descendant archetype) → a constructed memory-keeper name. TWO NAMED COLLISIONS the reframe itself introduced and flagged for the NAMING_METHOD pass to REPLACE: the working name Nasakhma (CHAR_0106) is itself an attested Napatan king (c. 468-463 BCE), and Talakhi (CHAR_0103) echoes the attested king Talakhamani (c. 435-431 BCE) — carried as explicitly-provisional working names under a STANDING INSTRUCTION that no constructed Kushite or Nubian working name may resolve onto an attested Napatan or Meroitic royal name (each checked against the full king-list before finalizing). The real Amanirenas, Amanishakheto, Natakamani, and the 25th-Dynasty pharaohs (Piye, Shabaka, Shebitqo, Taharqa, Tanutamani) are honored as documented history in L2; CHAR_0105 Peqereslo (built on the attested peqer/pqr office-title register, not an individual) and CHAR_0108 Julius Cornelius (generic Roman veteran) are retained clean. Separately, the Kxao-rule wording in the protected-combat block was nuanced to distinguish a bare deity proper-name standing alone as a mortal's whole name (prohibited) from an attested-pattern theophoric compound (a devotional lord/servant-of-the-god form such as the constructed high-priest handle Nebkematef, structurally identical to the historical Amenhotep or the Meroitic Amani-compounds, permitted — the NAMING_METHOD pass confirms it reads as devotional, not as the deity itself). No story content changes; the Meroitic Inscription Limit is authored with ZERO invented Meroitic semantics (the script is genuinely undeciphered). Reason: CVD §17.1 and HL_0002 forbid a real named individual on an invented NPC persona and a real revered figure recast as a villain, and require primary-source grounding; the living-source doctrine carries the reframes in place with final orthography and the royal-collision check set at the NAMING_METHOD pass, exactly as Ch 9-13 were handled [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Character_Index @ CHAR_0101]. Applied in the CH_14 build (Josh confirms at RR-22).
[Chapter CH_15 session, 2026-07-08] Grid: Cultural §17.1 — Ch 15 Egypt attested-name and deity-name sweep (the densest yet). Drift: Ancient Egypt's onomasticon is extremely dense, and the Ch 15 (ancient-arc philosophical climax) roster carried real attested pharaohs, priests, and a DEITY name on invented NPC personas, plus the boss on a real documented priest — the barred treatment per the Ch 9 Abuna / Ch 12 / Ch 13 ‡Nabe / Ch 14 precedents, and the pack explicitly flagged CHAR_0109 Meryre (Akhenaten's actual High Priest of the Aten) as the family-aligned antagonist. Resolution (title- and role-forward reframes, learning the Ch 14 collision trap where reframed names landed back on real Kushite kings): the boss is held to the pack's named title the High Priest of the Erasure (real Meryre honored as documented Amarna history per Aldred in the L2 civ-marks layer); every other real-individual name is reframed to a title- or role-forward working handle carrying no attested identity, with final personal names DEFERRED to the NAMING_METHOD pass rather than freely constructed — CHAR_0111 Hapuseneb (a real Hatshepsut-era Amun High Priest, and mis-tagged post-Akhenaten in the pack) → the restoration High Priest of Amun (chronology corrected to a post-Amarna figure); CHAR_0112 Petosiris (a real Thoth priest/astrologer) → the Hermetic scribe-teacher; CHAR_0113 Hetepheres (Khufu's attested mother) → the Per-Nefer embalming priestess; CHAR_0114 Amenemhat (an attested pharaoh name, Ineni-architect archetype) → the Valley tomb-architect; CHAR_0116 Khenemet (an attested royal element) → the Isis mystery-cult priestess; CHAR_0110 Khabash (echoing the rebel-pharaoh Khababash, carried from Ch 14) → a constructed Napatan-Meroitic emissary handle; and CHAR_0115 Nehemet-Awai — a GODDESS name (the consort of Thoth) placed on a mortal Sobek-priestess, a direct Kxao-rule violation — → the Sobek priestess of Kom Ombo with the deity element stripped. The STANDING no-royal-and-no-deity-collision instruction (established at Ch 14) binds the NAMING_METHOD pass: every constructed Egyptian name is checked against the attested king-lists, priesthood, and deity roster before finalizing. The Kxao-rule wording is honored (a bare deity proper-name never stands alone as a mortal's name; the gods Osiris/Isis/Ra/Anubis/Thoth/Ammit/the 42 Judges appear as the tradition understands them, honored, never trap-monsters — the Duat guardian is the manifested weighing-of-the-heart TEST, not the gods as enemies). No story content changes. Reason: CVD §17.1 and HL_0002 forbid a real named individual on an invented persona, a real revered figure recast as a villain, and a deity-name on a mortal, and require primary-source grounding; the living-source doctrine carries the reframes in place with final orthography + the collision-check set at NAMING_METHOD, exactly as Ch 9-14 were handled [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Character_Index @ CHAR_0109]. Applied in the CH_15 build (Josh confirms at RR-22).
[Chapter CH_15 session, 2026-07-08] Grid: Continuity / Cardinal-canon — Ch 15 Adeptus-Minor onset and two cardinal flags surfaced for Josh. Surface: Ch 15 is the canonical ADEPTUS MINOR (Tier 6) ONSET — substrate perception begins, Vril Sight + Astral Projection unlock, and the HL_0028 restriction that held every earlier chapter to inscription/reverence/lore perception OPENS here (the earned payoff of the long restriction). Two cardinal-canon items are FLAGGED for Josh (not decided): (1) AGE-VS-MASTERY — the protagonist carries age 10 from Ch 14 while reaching Tier 6 here; the per-chapter age step is unpinned so nothing is invented, but whether the arc intends an age advance across Ch 2-15 or a canonical mastery-outpaces-years note for the elven-royal protagonist is age/numerical canon reserved to Josh. (2) COMPONENT-11 CROSS-REFERENCE — the RCM substrate anchors CVD §3 Component 11 as a DUAL anchor spanning Ch 15 (Giza/Serapeum megalithic precision) and Ch 52 (Puma Punku), and the entry carries that dual-anchor framing per the RCM; because CLAUDE.md known-issue 1 records CVD §3 Component 11 at Ch 52 and Component assignment is cardinal canon, the Ch 15↔Ch 52 dual-anchor cross-reference is surfaced for Josh rather than asserted as settled. Both are staged in docs/spine/DECISIONS_PENDING_JOSH.md and carried in the CH_15 Decisions block. Reason: HL_0028 makes Ch 15 the tier-6 threshold (the entry frames it as the payoff, not a violation), and age/numerical + Component assignment are cardinal (Josh's) — do-not-invent requires flagging, not deciding [SRC: T0_Hard_Lines @ HL_0028] [SRC: T1_Research_Corpus_Master # Ch 15]. Applied/flagged in the CH_15 build; PENDING JOSH at RR-22.
[Chapter CH_16 session, 2026-07-08] Grid: Cultural §17.1 — Ch 16 Indus canonically-nameless boss and the role-forward Harappan cast (the INVERSE of the Ch 9-15 attested-name sweeps). Surface: the Harappan (Indus) script is genuinely undeciphered at canonical scope (HL_0094 / T1_Languages §7.4), so — unlike Ch 9-15, where the drift was attested royal/priest/deity names dressed on invented personas — Ch 16 has NO attested Harappan personal onomasticon to collide with, and the correct §17.1 answer is that no Harappan personal name can be canonically supported at all. Resolution: the main boss is held to the title The Priest-Administrator of the Standard, canonically NAMELESS by hard limit and NOT a Phase-6 deferral (the pack's decisive call — the title echoes the one thing the civilization provably did, the 1:2:4 brick-ratio standardization of a subcontinent, without inventing a phoneme the research cannot read), and every Harappan NPC carries a role-forward working handle (the granary-scribe of the standard, the Great Bath water-keeper) rather than a constructed personal name; the later Indo-Aryan textual figures (Manu, the Rig-Vedic tradition) are referenced as documented lore, never cast on a persona. No attested-name reframe sweep was needed because there is nothing to reframe — the illegibility that protects the Harappan community is the same hard limit that makes the whole cast role-forward. Reason: CVD §17.1 and HL_0002/HL_0094 forbid inventing a culture's proper names against its own record, and the naming-method cardinal rule (if the canon does not support the lore a name needs, discard the name) makes title-only the canon-correct answer, not a deferral flag [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Hard_Lines @ HL_0094]. Applied in the CH_16 build.
[Chapter CH_16 session, 2026-07-08] Grid: Cross-cultural / Thread-coverage / Scatter-completeness — Ch 16 inherited link flags, Thread 1 NOT_PRESENT, and the Chapter_Index trailing-cell completeness. Surface: (1) the T0_Cross_Cultural_Link_Graph rows LINK_0166 (the Manu-and-the-Matsya flood-survivor parallel to Utnapishtim, Ch 17) and LINK_0172 (the place-value-and-zero numerical-tradition transmission to Arabic mathematics, Ch 19) each carry a live [DECISION NEEDED - JOSH] source-placement flag over whether their Indian node anchors at Ch 16 (Indus / North-Indian Vedic) or Ch 7 (South India), with the registry's working primary at Ch 16 and a Frame-A convergence-not-diffusion framing; (2) Thread 1 Vril Parallels has no Ch 16 anchor in canon (ruled batch-1 #10 NOT_PRESENT — the chapter's substrate routes to Threads 17/5/13/10/20, and the Great Bath purification and the proto-yogi posture are not Thread-1-labeled anywhere); (3) the CH_16 scatter fully populated the Chapter_Index trailing personal-state cells (spine_entry_drive_anchor, body_prose_word_count, spine_status, canonical_hard_line_flag, protagonist_age, identity fields, cultural/dual-track compliance, prev/next links), which the Ch 13/14/15 scatters left empty. Resolution: both link edges are used at Ch 16 per the registry's working primary and its Frame-A framing, surfaced in the CH_16 Decisions block as an inherited flag pending Josh's RR-22 confirmation (not decided, not re-invented); Thread 1 is carried NOT_PRESENT per the ruling with a Josh-authorable-opening note, the 22-thread count untouched; and the Ch 13/14/15 trailing-cell backfill is logged as a standing minor completeness item in MASTER_ENHANCEMENT_PLAN (non-blocking, gates green either way — Ch 16 sets the complete-scatter example). Reason: the source-placement is a pre-existing foundation flag and Thread naming/assignment is cardinal (Josh's), and the resolve-don't-silently-assert discipline requires surfacing an inherited rowed value rather than presenting it as settled [SRC: T0_Cross_Cultural_Link_Graph @ LINK_0166] [SRC: T0_Thread_Grid @ THREAD_01]. Applied/surfaced in the CH_16 build; PENDING JOSH at RR-22 (link placement) + the trailing-cell backfill scheduled.
[Chapter CH_17 session, 2026-07-08] Grid: Reveal-discipline / Continuity — Ch 17 Mesopotamia is the antagonist-engine ignition (the FIRST DIRECT ARCHITECT CONTACT and the House-of-Velheim foundational-origin event, ~3000 BCE ziggurat rift-discharge), the most reveal-sensitive node so far. Surface: the chapter canonically MEETS the Architect (T3_Core §4 / HL_0101), which risks leaking the antagonist pattern the reveal-timing rule holds to ~Ch 38 (§17.9 / HL_0043 / the ruled Ch 8 Q1). Resolution: built so the PLAYER meets only a single uncanny priest-official who greets the protagonist fluently in the fairy realm's spoken tongue — dread and a mystery — while the House-of-Velheim NAME, the family PATTERN, the awareness-tier taxonomy, the name Maatherion (reserved Ch 69), and the Grand Sage (dark until Ch 76) are ALL held to the design and Layer-3 layer; the role-name "the Architect" and the word "family" are design-layer only; the fairy-tongue echo (FAIRY_REALM_CH17_MESOPOTAMIAN_ECHO) ties forward to the Ch 38 reveal without decode here. The lint gate raised 7 grand_sage/thesis_language WARNs on the banner/reveal/boss/Decisions blocks — a 4-lens fresh-context critic (reveal-discipline lens leading) verified each is a design-layer statement DOCUMENTING what is held from the player, never player-facing narration, and EXPLICITLY confirmed ZERO player-facing leak; the WARNs are the lint doing its job, cleared by the critic. Reason: §17.9/HL_0043 forbid declaring the thesis and HL_0101 fixes the Architect's first-contact behavior, while the reveal-timing rule (Ch 8 Q1 + the antagonist-pattern-reveal-timing memory) holds the name/pattern to ~Ch 38 — the encounter is canonical, the pattern is not surfaced [SRC: T0_Hard_Lines @ HL_0101] [SRC: T0_Hard_Lines @ HL_0043]. Applied in the CH_17 build.
[Chapter CH_17 session, 2026-07-08] Grid: Cultural §17.1 / Grounding — Ch 17 real-person, living-culture, and cross-reference fixes from the critic gate. Drift/fixes applied (GO-WITH-FIXES, 0 blockers / 2 majors / 6 minors): (1) Enheduanna (CHAR_0117), the real first named author in human history, is honored at audit-care as a documentary ally present through her attested hymns and documented role, never fictionalized into invented persona-dialogue and never the boss or villain — the L1 Ur-temple beat pinned explicitly documentary so the persona system cannot later generate first-person dialogue for a real person (a positive inversion of the Ch 9-15 real-person-reframe discipline). (2) MAJOR care fix — the Ma'dan (Marsh Arabs, a LIVING culture) marsh scene originally said "a way of living unchanged for five thousand years," the frozen-in-time trope the Care Doctrine guards against and a contradiction of the RCM (continuous but drained in the 1990s and only partially rehydrated); reframed to "a continuous way of living carried across five thousand years, resilient and enduring rather than frozen." (3) MAJOR grounding fix — CHAR_0056 Binti Hassan's Ch-17 appearance is grounded on her canonical Ch 9-38 sea-crossing-if-ally RANGE rule (Ch 17 in range) rather than an explicit registry row; the citation reworded to the range rule + a [POPULATE→T0_Character_Index] to pin the explicit per-chapter sea-crossing appearances (Ch 16/17) at the next population, not an overclaim of an explicit row. (4) Minor grounding polish: the Enuma Elish creation-combat splitter reframed from "the sky-god" to "the young storm-god" (Marduk's role, unnamed in POV per HL_0002); the HL_0114→HL_0101 re-cite on the Architect's refusal-grace clause; the Thread-2 incoming Apophis edge given its own LINK_0153 anchor; the Adapa wisdom-for-loss myth linked as the ancient mythic mirror of the Architect's offer (L2 substrate, never a player-facing thesis); the identity_hiding_pressure header clarified to LOW arc-level with a MODERATE boss-spike (scatter carries the LOW steady-state, matching the CH_16 convention). The gods (Inanna/Ereshkigal/Enki/Marduk/Anu/Enlil) honored and never fought; Tiamat/Lamashtu folklore-combat as the cosmology frames them; the House of Velheim composite-fictional per HL_0109, never conflated with real dynasties, no real-modern content at ancient Ch 17. Reason: §17.1 Care Doctrine (represent-with-care, never omission or romanticization), HL_0002 primary-source fidelity, and the do-not-overclaim-a-registry-row discipline [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Character_Index @ CHAR_0117]. Applied in the CH_17 build (Josh confirms at RR-22).
[Chapter CH_18 session, 2026-07-08] Grid: Cultural §17.1 (the arc's most sensitive node) — Ch 18 Levant record-editing antagonist rendered SAFE against the antisemitism trope. Surface: the canonical Ch-18 antagonist is a "Theological Editor" (NW_0016, Sector-5 Media/Information) who edits the record that is the Hebrew Bible — a premise adjacent to a real, painful antisemitic conspiracy trope. Resolution (elevated care): built to the strictest §17.1/HL_0109 discipline — the editor is COMPOSITE-FICTIONAL and cross-cultural (the same method at Mesopotamia and elsewhere), never a real Jewish scribe, the Israelite priesthood, a real person, or a stand-in for any people; the documented editorial history (monotheizing trajectory, Documentary Hypothesis, Josianic reform, the Kuntillet Ajrud "Yahweh and his Asherah" pluralism) is presented as MAINSTREAM SCHOLARSHIP crediting Israelite agency, never a debunking of the faith; the Jewish community + the honest scribes + the honorable reform-archivist (the Warden) are the antagonist's VICTIMS and OPPONENTS on the protagonist's side; the negative-consciousness overlay is the game's interpretation per CVD §3, held distinct and never conflated on any player surface; the crime is against MEMORY (the erase-to-control pattern), not the faith. A 4-lens fresh-context critic (the antisemitism-trope lens paramount) returned GO-WITH-FIXES and EXPLICITLY confirmed the guardrail holds on all player surfaces + zero reveal leak; two MAJOR fixes were applied NOW rather than deferred: (1) the L1 body prose now credits the monotheizing reform as the Israelites' OWN authentic development (the Warden its honest champion) and frames the villain's specific crime as the secret erasure of memory, so an L1-only player never reads monotheism as the villain's imposition; (2) the editor's deferred proper name is constrained NON-Hebrew/Aramaic (the enrich pack's Hebrew-derived "Sofér-Mahpék" barred by name) so it never codes him as a Jewish scribe. Minor fixes: SCH_003 grounded as Western-esoteric RECEPTION (Hermetic Qabalah / Solomonic grimoire) not living Jewish Kabbalah as combat-magic; a Solomon-Hiram cooperation civ-mark added (community-as-partner); the Ch18-68/Ch69 materialized-argument window phrasing harmonized; the mischaracterized CLAUDE.md known-issue-1 cross-ref dropped; the Ittobaal working-name reframed role-forward (collides with the attested Tyrian king Ithobaal) and the Miriam element deferred, per the standing no-royal-collision rule. TWO CARDINAL FLAGS → DECISIONS_PENDING_JOSH D-08 (Josh confirms the §17.1 record-editing handling given the living-religion + trope-adjacency) + D-09 (Component 5/10/11 assignment per the RCM). Reason: §17.1 Care Doctrine (represent-with-care) + HL_0109 (composite-fictional, never conflated) make the canonical premise safe only through this discipline; the crime-against-memory framing is the arc's erase-to-control throughline across Egypt/Indus/Levant [SRC: T0_Hard_Lines @ HL_0109] [SRC: T1_CVD_Creative_Vision_Document # 17.1]. Applied in the CH_18 build (Josh confirms at RR-22).
[Chapter CH_18 session, 2026-07-08] Grid: Living-source — BOSS_PERSONAS.md Ch 18 persona id-convention aligned. Surface: the Ch 18 boss persona in docs/proposals/BOSS_PERSONAS.md used a Ch18-M / Ch18-S1/S2/S3 id convention, inconsistent with the BE_00NN convention BE_0013..BE_0017 use in both the persona doc and the T0_Boss_Encounter_Registry, so the spine's [SRC: BOSS_PERSONAS # BE_0018] anchor initially failed to resolve. Resolution: the persona headings were living-source-aligned to carry the canonical BE_0018 / BE_0018_S1/S2/S3 ids (preserving the Ch18-M/S ids alongside), so the anchor resolves and the persona doc, the registry scatter (BE_0018 ×4), and the spine entry all agree. Reason: the anti-orphan / no-deprecated-reference discipline requires the persona doc to carry the canonical boss id the registry and spine use [SRC: T0_Boss_Encounter_Registry @ BE_0018]. Applied in the CH_18 build.
[Chapter CH_19 session, 2026-07-08] Grid: Cultural §17.1 (living-Zoroastrian) + Living-source — Ch 19 Arabia/Persia corrupted-apostate-Magus framing, and the RCM source-hygiene rewrite that kills the risky priesthood-as-apparatus phrasing. Surface: the canonical Ch-19 antagonist is a Magus weaponizing the Achaemenid surveillance network (RCM + boss roster), and Zoroastrianism is a living religion, so the framing is scrupulous: the boss (NW_0017, the Magus Observer / Duruj-Nemah) is a CORRUPTED, APOSTATE Magus — a composite-fictional Velheim surveillance-node vessel who serves druj against asha — NEVER the honest priesthood, the faith, the Magi-as-a-class, or a real Magus; his evil is named in the tradition's OWN emic asha/druj categories (per the D-05 emic-grounding ruling), the honest fire-priests are honored allies, and the apparatus is the family's cooption of a network through corrupted nodes; Ahura Mazda and Anahita are honored and unfought, Azhi Dahaka is faced only as a folklore manifestation from its Damavand binding, and the sacred fire, haoma, and fire-temple (plus Islam/Sufism in the forward-window) are referenced-not-reproduced (HL_0110). A 4-lens fresh-context critic (living-Zoroastrian lens paramount; 5/5 agents, no errors after relaxing the StructuredOutput minLength that had tripped a Ch 18 lens) returned GO-WITH-FIXES (0 blockers / 2 majors / 9 minors) and confirmed the living-Zoroastrian care HOLDS on every player surface with ZERO reveal leak, and that the apostate framing SUFFICES under the Care Doctrine (no blocking Josh fork — RR-22 note only). Fixes applied: the two majors — Thread-13 co-anchored the canonical Thread_Grid "Islamic Persia" content (chahar-bagh / four-iwan / muqarnas) alongside the Achaemenid Persepolis geometry (HL_0053 grid authority), and the false "first double-trade-home of the arc" claim corrected (Ch 7 South India rooted Trade 3 + Trade 4 first); minors — Thread-2 LINK_0030/0157 anchors added, identity-pressure clarified LOW→MODERATE, the Simurgh si-morgh resonance softened to stay ambient Layer-3 and never a protagonist self-realization (HL_0043, ahead of the Ch 76 Grand-Sage reveal), the Atossa archetype + Queen-of-Sheba anchors restored, the S2 sub-boss re-threaded from a duplicate Thread-2 to the Thread-3 economic sub-lane, and the Yezidi/Druze deferral + the mine-forced-extraction-Frame-A watch-note (Achaemenid workforce documented as substantially wage-paid — no "Persia enslaved its miners" reading) + the constructed-name deferrals (Duruj-Nemah, Xšaça-Kāra, the confusing "of the Wadi" epithet) recorded in the Decisions block. LIVING-SOURCE: the RCM Ch-19 verified-canon sentence was reworded in place from "The Magi as Zoroastrian priestly class ... operating as Velheim family continental intelligence apparatus" to the corrupted-apostate-nodes framing, so the source no longer seeds the priesthood-as-apparatus reading a later agent could regenerate; and the BOSS_PERSONAS Ch-19 persona was aligned to the canonical BE_0019 / BE_0019_S1-S3 ids (it had used a Ch19-M/S convention). Reason: §17.1 Care Doctrine + the emic-grounding ruling make the canonical premise safe only through the apostate framing, and the living-source doctrine requires killing the deprecated framing at the source [SRC: T0_Hard_Lines @ HL_0005] [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Antagonist_Network_Registry @ NW_0017]. Applied in the CH_19 build (Josh confirms at RR-22).
[D-06 cross-chapter application, 2026-07-08] Grid: Continuity / Age-and-Mastery — the "Reclaiming the Birthright" model applied across Ch 2-19 (Josh-ruled). Surface: the built spine froze a flat protagonist_age plateauing at 10 through Ch 8-19 and framed the ancient-world arc as childhood ("a child of ten"), which contradicted existing T3 §85 canon (Adolescence = the ancient-world journey) and left the Ch 15 age-vs-mastery flag (D-06) open. Resolution (Josh-confirmed 2026-07-08 via AskUserQuestion — Option C mastery, Childhood→Adolescence at the Ch 13/14 boundary, Variant B early jumps per his "larger jump in Ch 1 and Ch 2" direction): TWO CLOCKS — (1) an externally-legible chapter-anchored age_STAGE (Childhood ≤ Ch 13 / Adolescence Ch 14-38 / Adulthood Ch 39+) driving appearance/voice/dialogue per CVD §9.5, added as a new T0_Chapter_Index age_stage column populated for all 79 rows (baseline refreshed, declared added column); (2) a DESIGNER-ONLY internal age integer, never surfaced, advanced by the already-canonical time-fluctuation (large jumps at the Ch 1 rift-fall and Ch 2 arrival, placed jumps on the era-seams, crystallizing at the Ch 38 stabilization) — internal curve ~5 pre-rift → 7 Ch2 → ~14 Ch15 → ~18 Ch38 → young-adult plateau as elven long-life re-engages. MASTERY (the "why tier 6 already?" answer, touching no hard line): PER-CAPABILITY (HL_0026) — "tier 6 at Ch 15" is the INSCRIPTION capability reaching Adeptus Minor (the HL_0017/HL_0028 substrate-perception binding), with combat/trades/weapons/familiar-bond on their own lagging ladders; and the whole climb is the RECLAMATION of a dormant innate elven birthright (T3 §59/§61/§565), gated by quest/proficiency (HL_0027) and depleted atmospheric vril (full power capped until Ch 70), not learning from zero. The graded ladder Neophyte→Zelator→Theoricus→Practicus (Ch 13)→Philosophus+Portal-Grade (Ch 14, already built at CH_14 line 81)→Adeptus Minor (Ch 15) is now explicit. Applied: the internal-age + age_stage sweep across Ch 2-19; the CH_15 flag closed and its "child of ten" beat recast to adolescent-reclamation; the per-capability + reclamation framing woven through CH_02/13/14/15/16/17; T3 §85 transition wording updated to the Ch 13/14 + Ch 38/39 boundaries; the T3 §9.7→§9.5 citation fixed; and the per-capability/age-stage guidance wired into the /spine-chapter skill (mastery_tier note + the end-state carry-forward block). Gates exit 0. This SUPERSEDES the two CH_15-session flags filed 2026-07-08 (age-vs-mastery is now RESOLVED via D-06; the Component-11 flag via D-07). Reason: resolves a live spine-vs-T3 contradiction toward the canon Josh confirmed; every hard line is preserved (HL_0017/0026/0027/0028, the Ch 15 onset kept in place) and every internal number is designer-only and adjustable [SRC: T0_Hard_Lines @ HL_0026] [SRC: T0_Hard_Lines @ HL_0017] [SRC: T1_CVD_Creative_Vision_Document # 9.5]. Applied in the D-06 ruling commit; cascade UNBLOCKED at Ch 20.
[Chapter CH_20 session, 2026-07-08] Grid: Build + Care + Living-source — Ch 20 Silk Road, the arc's first trans-continental HUB chapter. Surface: the network-mapping Thread-3 pivot (Ch 19 proved the surveillance apparatus exists; Ch 20 maps its full extent), an environmental main boss (the Starved-Oasis-Echo, HL_0080) behind the non-Velheim UNAWARE monopolist Karashan (NW_0018), with living Tibetan-Buddhist dream-yoga/Bardo + the Buddhist naga transmission (standard care, elevated in practice) and the Tarim-Tocharian anti-fringe risk. Resolution: authored to the v2.5 twenty-block schema (all pack material used — the 3 thread-diverse sub-bosses, the five-script window Tocharian/Khotanese-Saka/Sogdian/Old-Uyghur/Middle-Chinese, LINK_0176 paper→Latin-West at Ch 31, INSC_77H_CH20_FRAGMENT, the Mogao Cave-17 polyglot trove as the anti-monopoly counter-archive, the Murugan-associated peacock reappearance); reveal discipline held (Karashan a local monopolist, the pattern a shape she cannot yet name, the House name/family/Architect all design-layer only per §17.9); the D-06 age model applied (age_stage Adolescence, internal 15→16 via the Han-Mongol time-fluctuation; per-capability inscription at Adeptus Minor reading the Silk-Road scripts at their Practicus decode-register, not a tier regression). A 5-lens fresh-context critic (wf_67c4e0b0; grounding / care-anti-fringe / reveal / schema-mechanical / completeness → synthesis) returned GO_WITH_FIXES (0 blockers / 1 major / minors, ALL applied): the MAJOR — the five scripts single-homed as a Mechanical-anchors scripts: FK line mirroring CH_19; MINORS — the inscription_spine FK line added to Mechanical anchors, Key-sites vril_density zone-seeds added, the dream-adept reframed as the exploited/wronged party (not a "conflicted rogue") with the living tradition never villainized and the sacred term "bardo" dropped from the in-entry handle, the Murugan peacock rendered as "the Murugan-associated peacock" (a Murugan-vahana descriptor, not the deity name as the animal's own name) with the underlying familiar naming flagged for a §17.1 review at T3_Familiars_Named and the Ch 7 golden re-enrichment, and the Bardo source swapped from the Theosophist-inflected Evans-Wentz to a tradition-grounded Fremantle-Trungpa / Gyurme-Dorje translation; the reveal lens EXPLICITLY confirmed ZERO player-facing leak (both lint grand_sage/thesis WARNs are design-layer documentation). LIVING-SOURCE: docs/proposals/BOSS_PERSONAS.md Ch 20 aligned to the canonical BE_0020 / BE_0020_S1-S3 id convention (it had used a Ch20-M/S convention). The stale R4/CH_20 topography waiver was removed — CH_20 now carries all five Pillar-1.12 beats (combat/puzzle/learning/character/transformation), so the missing-beats waiver is retired and the topography baseline shrank 62→61. Reason: §17.1 Care Doctrine (living traditions as they understand themselves; the dream-yoga practitioner the wronged party, never occult exotica), Frame-A anti-fringe (the Tarim/Tocharian credited to its own peoples per Mallory & Mair, never a lost-race narrative), HL_0080 (the environmental boss is a non-damageable substrate-presence), and §17.9 reveal discipline (the monopoly pattern a travelling method, never a named family) [SRC: T0_Hard_Lines @ HL_0080] [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Antagonist_Network_Registry @ NW_0018]. Applied in the CH_20 build.
[Chapter CH_21 session, 2026-07-08] Grid: Build + Care/Real-person + Reveal + Living-source — Ch 21 China (with the ratified Korea excursion), the knowledge-destruction-vs-preservation node. Surface: the Qin book-burning (213 BCE) and burying-of-scholars (212 BCE) as the arc's sharpest Thread-3 knowledge-suppression beat (a thematic application of CVD §3 Component 5), against Korea's preservation counterweight (the Tripitaka Koreana, the Jikji movable-metal-type); a moral-triage main boss (the Burning Archive — save texts, win=pacify, no kill) whose documented burn-order is Li Si's, a REAL historical Qin chancellor; the concealed hand is the fictional long-arc vessel Cui Mian (NW_0019, FAMILY_BRIEFED). Resolution: authored to the v2.5 twenty-block schema; Li Si held AUDIT-ONLY (documented role only, no invented interiority/persona/dialogue, the Meryre/Enheduanna real-person discipline) with the playable antagonist the fire+order and the concealed vessel; the burying-of-scholars authored as the documented atrocity (Sima Qian) with the conscript-levy as its combat-eligible apparatus and the scholars as victims/allies (never targets); reveal discipline held (no direct Velheim presence rendered, the family/name/pattern dark, Cui Mian felt as a lulling quiet not named, the trans-era placement read at L3 as the family METHOD via the time-fluctuation window); the D-06 age model applied (age_stage Adolescence, internal 16 held, per-capability inscription reading oracle-bone at its Practicus decode-register). Trade-6 Tailoring ancient home ROOTS here (sericulture/kesi/brocade); SCH_004 Chinese Taoist alchemy debuts (wu-wei Flow-Redirect); the Koi (W3) bonds at the Yellow-River Dragon Gate (the arc's only Koi→Dragon evolution); A_E3_003 Temporal Echo unlocks. A 5-lens fresh-context critic (wf_d2792e71; grounding / care-real-person / reveal / schema-mechanical / completeness → synthesis) returned GO_WITH_FIXES (0 blockers / 0 majors), with the Li-Si real-person handling and the reveal discipline both EXPLICITLY confirmed to hold (zero player-facing leak). Fixes applied: the historical-honesty burying-of-scholars fix (the 212 BCE killing named, the levy the apparatus of the atrocity not a sanitizing forced-labor substitute); SQ12's pattern-intel marked held-to-the-long-arc (no pre-Ch-38 pattern assembly); the body "before Europe managed it" → "generations before Europe's own" (Frame-A softening); the Koi rendered "(W3)" to match sibling slot-ids; a Cui-Mian trans-era L3 clarifier (the family method, not one operative across eight centuries); the dominant_combat_mode aligned to the Chapter_Index's canonical puzzle_routed (the moral-triage/decode frame) rather than the drafted "direct"; the critic's BE_0021 "citation error" was a false-positive (the ids were aligned to BOSS_PERSONAS and the anchors gate resolves them). LIVING-SOURCE: BOSS_PERSONAS Ch 21 aligned to the canonical BE_0021 / BE_0021_S1-S3 id convention. The stale R4/CH_21 topography waiver was removed — CH_21 now carries all five Pillar-1.12 beats (the moral-triage supplies the character beat) — shrinking the baseline 61→60. Frame-A: movable type authored as parallel-independent invention (Bi Sheng, the Jikji, Gutenberg — each its own, LINK_0177), never a diffusion or superiority claim; I Ching/Lo Shu never fringe super-science; the Great Flood as flood-memory not flood-proof. Reason: §17.1 Care Doctrine + the real-person audit-only rule + Principle-3 historical honesty (the atrocity never softened), HL_0003 (combat via the apparatus, never the scholars), §17.9 reveal discipline (the concealed hand felt, never named), and Frame-A anti-hyperdiffusion [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Hard_Lines @ HL_0003] [SRC: T0_Antagonist_Network_Registry @ NW_0019]. Applied in the CH_21 build.
[Chapter CH_02 GOLDEN re-enrichment, 2026-07-08] Grid: Golden re-enrichment (Phase 3, the first of Ch 2-12) — Ch 2 Flores rebuilt to the v2.5 golden bar + the malevolent-being restoration. Surface: the v2.4 CH_02 lacked the v2.5 golden blocks and sanitized the corruptor into "a passing dukun" (mis-assigning malevolence to a real benevolent folk-healer role); the region's own named evil being, the polo (the Nage/Lio soul-eater witch, LINK_0146 polo→leyak), was omitted, Tiwu Ata Polo reduced to a "colour-shift phenomenon," and the Ebu Gogo flattened to a benign coexistence-memory. Resolution (ENRICHMENT_PROPOSAL STRONG + OPTIONAL, §17.1-IMPROVING): added the eight missing golden blocks (Civilizational marks, Key sites, Main quest beats, Side-questlines, Dialogue anchors, Anti-fringe, Asset anchors; the Key-ally block pre-existed); re-grounded the corruption from the dukun to the polo — the dukun DE-VILLAINIZED and restored to its benevolent healer role, bound to CHAR_0014 Healer Maria (a genuine §17.1 improvement, not just an addition); restored Tiwu Ata Polo (the lake of the wicked dead, now tied to the climax stakes) and the Ebu Gogo edge (an ambivalent deep-cave ambient threat, NEVER replaying the villagers' cave-burning, mindful of the real Homo floresiensis overlap, held as a mythic cross-Flores type-site resonance not a Manggarai ethnographic claim); wove the vital-force-eater cross-cultural links (LINK_0146/0152) plus the full ten originating links and the water-buffalo / Weaving-11 first instance (LINK_0117); carried the D-06 framing (internal age 7→9, age_stage Childhood, Neophyte-only perception per HL_0028). A 5-lens fresh-context critic (wf_39c01ede; care-malevolent-being / grounding / reveal / schema-mechanical / completeness → synthesis) returned GO_WITH_FIXES (0 blockers), EXPLICITLY confirming the dukun de-villainization "complete and explicit," the malevolent-being restoration "faithful to the proposal," the Ebu Gogo handled without the extermination, and reveal discipline clean; the 3 MAJORs (the wholly-omitted Weaving-11/LINK_0117 anchor, the omitted CHAR_0013/0014/0015 + the healer-binding, the incomplete 10-link FK home) and the MINOR cluster (source split polo→Forth Beneath the Volcano / Ebu-Gogo→Images of the Wildman; the boss axis 50/30/20→60/20/20 to match the persona; the lingko re-anchored to RCM Ch 3 + the ungrounded Ngada-megalith mark replaced with the Austronesian-settlement mark; the garbled Thread-3 clarifier; the HL_0078-vs-failure-states cite split; the CR_0010 Ebu-Gogo and CR_0011 Orang-Pendek anchors) were ALL applied. LIVING-SOURCE: BOSS_PERSONAS boss_02_main re-grounded dukun→polo across its Substrate / Persona / Combat / NAME-derivation / self-review, with an Ebu-Gogo ambient sub-threat added; the Thread_Grid THREAD_03 and THREAD_11 Ch-2 content_summary cells scrubbed dukun→polo (living-source, so the deprecated framing cannot re-diverge). scatter (Chapter_Index CH_02 folklore_entities / seed_npc_ids / body_prose_word_count) → baseline refresh → gates exit 0 (anchors 23 files / 2952 / 0 unresolved). This sets the Phase-3 pattern (v2.5-golden rebuild + malevolent-being restoration + dukun-de-villainization + exhaustive pack cross-check), and it confirmed the dukun-as-villain pattern recurs (Ch 3 "Ratu Balik-Kata" needs the same treatment). Reason: §17.1 Care Doctrine (the golden-standard mandate — represent each culture's REAL malevolent beings AND de-villainize the benevolent healer role), the ENRICHMENT_PROPOSAL Josh-directed restoration, and the v2.5 golden bar [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Cross_Cultural_Link_Graph @ LINK_0146]. Applied in the CH_02 golden re-enrichment; retag spine/ch-02.
[Chapter CH_03 GOLDEN re-enrichment, 2026-07-08] Grid: Golden re-enrichment (Phase 3) — Ch 3 Manggarai Village rebuilt to the v2.5 golden bar + the potent-landscape restoration. Surface: the v2.4 CH_03 lacked the v2.5 golden blocks, de-fanged the sole supernatural being to a "protective python," and cast Ratu Balik-Kata as a "corrupted dukun." Resolution (ENRICHMENT_PROPOSAL STRONG): added the seven missing golden blocks (Civilizational marks, Key sites, Main quest beats, Side-questlines, Dialogue anchors, Anti-fringe, Asset anchors); RESTORED the Manggarai potent-landscape agency — the amoral darat and the roused naga tana (the soil-guardian, dangerous BECAUSE the ritual-less lingko-edge clearing violated its contract, appeased not slain by restoring the ngoéng-de-tana sacrificial contract), fusing the land-grab's political and spiritual resolutions, grounded in Allerton's Potent Landscapes; REFRAMED Ratu Balik-Kata off the benevolent-dukun label to a twisted-word sorcerer / materialized-argument manifestation (the RR-12-ratified name kept, only the role-label moved off the healer, per the Ch 2 dukun-de-villainization) and FLAGGED it for Josh since it touches an RR-12 ratification; carried the D-06 framing (internal age 9, age_stage Childhood). A 5-lens fresh-context critic (wf_8108f575) returned care GO / reveal GO / GO_WITH_FIXES overall (0 blockers), EXPLICITLY confirming the darat/naga-tana restoration "faithful" to the proposal, the dukun de-villainization applied with an appropriate Josh-flag, the naga tana appeased-not-slain, and reveal discipline clean; the MAJOR (the pack-anchored WPN_033 Shield dropped as "chapter_anchored_weapon_add none" — the caci whip-and-shield seating the player's first off-hand Shield, grounding the boss's parry verb) and the MINORs (the Ratu-Balik-Kata manifestation-not-community-figure disambiguation; the Ch-2 Teresa CHAR_0012 peer-thread reconciled into the community reception; the mastery-tier HL_0028/HL_0017 substrate-perception cite; the CR_0012 water-buffalo re-labelled Weaving-11 / Thread-14 off the registry's ambiguous Thread-11 tag; the Weaving-11 originating label) were ALL applied. LIVING-SOURCE: BOSS_PERSONAS boss_03_main re-grounded (the Naga-of-the-Wae → the roused naga tana; the "corrupted dukun" → the twisted-word sorcerer). scatter (Chapter_Index CH_03 folklore_entities / body_prose_word_count / mode_variety / WPN_033) → baseline refresh → gates exit 0 (anchors 23 files / 2997 / 0 unresolved). Ch 2-3 golden re-enrichment now done; the exhaustive-pack-cross-check lesson from Ch 2 held (all seven originating links, the full CHAR roster, creatures CR_0012-0016 all present) so Ch 3 had no grounding-completeness MAJORs beyond the one dropped weapon. Reason: §17.1 Care Doctrine (the golden-standard malevolent-being + potent-land restoration; the benevolent dukun/healer never the villain), the ENRICHMENT_PROPOSAL, and the v2.5 golden bar [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T1_Research_Corpus_Master # Ch 3]. Applied in the CH_03 golden re-enrichment; retag spine/ch-03.
[Chapter CH_04 GOLDEN re-enrichment, 2026-07-08] Grid: Golden re-enrichment (Phase 3) — Ch 4 Bali (the arc's densest 17-thread convergence node) rebuilt to the v2.5 golden bar + the real-leyak / bhuta-kala restoration + the Rangda-LEAVE guardrail. Surface: the v2.4 CH_04 lacked the v2.5 golden blocks and rendered the leyak a "manufactured fear" hoax (implying the villagers' belief a baseless swindle). Resolution (ENRICHMENT_PROPOSAL STRONG / OPTIONAL / LEAVE): added the seven golden blocks (Civilizational marks, Key sites, Main quest beats, Side-questlines, Dialogue anchors, Anti-fringe, Asset anchors); RESTORED a REAL leyak (a pengiwa night-witch, a community pillar by day / the tradition's own condemned adharma monster by night, fought in its night-form while DEFENDING the villagers and siding with Balian Made Sari's right-hand penengen warding — the certification apparatus exploits, not fabricates, the real terror; LINK_0147 leyak↔begu-ganjang, LINK_0168 pengiwa/penengen); SKINNED the abstract shadow-constructs as bhuta-kala (the Ogoh-ogoh register, the caru/mecaru appeasement respected); deliberately LEFT Rangda (the revered-and-feared ambivalent-maternal queen with a sacred consecrated mask, kept as the Barong-Rangda balance-trial, never a slain boss — the guardrail explicitly held); homed all ELEVEN originating cross-cultural links (the old entry claimed nine but named four); carried the D-06 framing (internal age 9, Childhood). A 5-lens fresh-context critic (wf_3e50fca0) returned GO_WITH_FIXES with NO blockers and NO majors (the cleanest re-enrichment yet — the exhaustive-pack-cross-check discipline held), EXPLICITLY confirming the leyak restoration §17.1-clean (a real being, the community defended, combat strictly on the night-form and off the community), Rangda correctly LEFT (never villainized), and reveal discipline clean; the MINOR cluster was ALL applied (Ana CHAR_0017 carried forward in found_family + the companions FK; the pengiwa "exploits-not-colludes" harmonization; LINK_0138 reworded "unity/syncretism" not "music-and-unity"; LINK_0147/0168 marked parallel-independent echoes not directional transmission per Frame-A; the Sanur-Octopus W4 bond-status harmonized to encounterable-bond-deferred; CR_0022/CR_0023 added to the creatures manifest; the Gate-Naga counter made Neophyte-safe off "attune vril-polarity"; Lansing added to substrate_sources; the main encounter's three phases slotted into the quest beats). LIVING-SOURCE: the live Chapter_Index CH_04.combat_framing and the Thread_Grid THREAD_03 Ch-4 content_summary cell were scrubbed of the retired "manufactured leyak / leyak certification system + Corrupt Market Enforcer" framing to the restored "a real leyak the apparatus exploits" (no deprecated reference survives to re-seed the debunking framing). scatter (Chapter_Index CH_04 combat_framing / folklore_entities / body_prose_word_count) → baseline refresh → gates exit 0 (anchors 23 files / 3044 / 0 unresolved). Ch 2-4 golden re-enrichment now done. Reason: §17.1 Care Doctrine (represent each culture's REAL malevolent beings and honor the belief as true rather than debunk it; LEAVE the revered), the ENRICHMENT_PROPOSAL, and the v2.5 golden bar [SRC: T1_CVD_Creative_Vision_Document # 17.1] [SRC: T0_Cross_Cultural_Link_Graph @ LINK_0147]. Applied in the CH_04 golden re-enrichment; retag spine/ch-04.
--- END LIVING REVISION LOG ---
[Chapter CH_05 GOLDEN re-enrichment + Angkor/Khmer SPREAD, 2026-07-08] Grid: Golden re-enrichment (Phase 3) + RATIFIED-SPREAD RESTORATION + Living-source HL_0028 fix — Ch 5 Sumatra and Java rebuilt to the v2.5 golden bar with the begu-ganjang + Naga-Padoha restorations, AND the dropped Angkor/Khmer + Champa mainland-SE-Asia SPREAD re-authored. Surface (golden): the v2.4 CH_05 rendered the boss Datu Siahaan a purely mundane broker and the Toba encounter an abstract "Deep-Memory." Resolution: RESTORED the begu ganjang as his datu-commanded phase-2 killing-spirit (LINK_0147, Loeb; warded with the legitimate Samosir healer Boru Simanjuntak, held distinct from the revered sombaon/sumangot), re-grounded the Toba-Memory to NAGA PADOHA the bound earth-shaker (LINK_0156, Tobing; endured/re-settled not slain, Mula Jadi Na Bolon and Sideak Parujar honored, moved to Thread 2/18), and LEFT Mahakala protective. Surface (the MAJOR catch): the golden first draft DROPPED the ratified 2026-07-08 coverage-rearch Ch-5 SPREAD (T0_Chapter_Index extensions coverage_rearch_20260708; EXPANDED_COVERAGE_MAP A1/C2) and positively MISCITED its own sources as supporting "no separate SPREAD" — a dropped-ratified-canon + false-citation MAJOR the first 5-lens critic (wf_cb4bd6df) caught as NO_GO. Resolution: authored the Angkor/Khmer + Champa excursion as L1/L2/L3 subordinate beats under the Sumatra/Java anchor (the Malacca-Kra-Tonle-Sap traverse; Angkor Wat/Bayon/Ta Prohm/baray/My Son key sites; a fictional un-named devaraja-court official + materialized temple-guardian constructs as BE_0005_S4 on the existing Tier-3 rung, NO new operative; the 1177 Khmer-Cham war two honored peers; Meru->Threads 5/13/18), grounded on a 4-agent deep-research brief (Coedes/Chandler/Higham/Groslier/Vickery/Maspero) with §17.1 held (living Khmer/Cham faithful protected, devaraja carried as Kulke/Vickery-contested not "the king is a god," Khmer Rouge OUT of era as a witness-depth flag, Champa care-tier flagged for RR-22) and Frame-A typed (Meru transmission-with-authorship / Khmer-naga catalog-convergence vs Naga-Padoha parallel-independent / leyak->krasue parallel-independent with the LEYAK the true cognate not the begu ganjang / baray<->Sri-Lanka parallel-independent, Sri Lanka PREDATING). Living-source: reconciled the CHAR_0031 Character_Index row in place (it asserted a tier-6 "detects vril signature from first encounter" read HL_0028/HL_0017 forbid at Neophyte Ch 5) to briefing-plus-trained-unease recognition. Enacted 3 new links (LINK_0185 Meru knowledge-transmission Ch5->Ch7; LINK_0186 leyak->krasue parallel-independent Ch4->Ch5; LINK_0187 baray->Sri-Lanka parallel-independent Ch5->Ch6), appended BE_0005_S4, updated BE_0005/S2/S3, bumped Thread-2 A->C, added SQ1_ADVANCE, removed the now-stale R4/CH_05 transformation-beat waiver (the beat is grounded in the Naga-Padoha deep-time trial), refreshed docs/fidelity_baseline.json in the same commit; SEA2 (Angkor/baray/Bayon Vril_Site catalog) DEFERRED + logged. Verification: the adversarial re-critic (wf_573adf18) returned GO_WITH_FIXES with both MAJORs confirmed resolved and only two one-line MINORs (link count ten->eleven; "Cham script"->"early Cham Brahmi-derived writing"), both applied. All 9 gates exit 0. LESSON (durable): a golden re-enrichment MUST run the /spine-chapter Step-0 coverage-scope check (EXPANDED_COVERAGE_MAP SPREAD/LENGTHEN/RESCOPE) against the LIVE Chapter_Index, because the 2026-07-08 coverage re-architecture ratified SPREADs the older v2.4 builds predate — modeling a re-enrichment off the stale v2.4 region scope silently drops ratified canon. Retagged spine/ch-05.
[Ch 6-8 GOLDEN re-enrichment + Paravani §17.1 fix, 2026-07-08 (autonomous night run)] Grid: Golden re-enrichment (Phase 3, continuing the Ch 2-12 pass) + Layer-1 traversal + living-source fixes. Ch 6 (Sri Lanka, 9b843bf): the Tovil/Sanni-Yakuma yakku restoration (Mahasona/Riri-Yaka/Daha-ata-Sanniya expelled with the edura, distinct from the revered Vedda nae-yaku), the deceiver-yaka main-boss reframe (Mara-vijaya L3), CHAR_0043 reconciled (kept the L3 pre-Architect design-tie in extensions), CHAR_0039 real-person un-named + FLAGGED D-10 (the Dambana Vedda leader). Ch 7 (South India, dc6bd4a + fix-forward ac37f80): the Surapadman-asura Soorasamharam restoration, first-home-base civ marks; critic fix-forward -- the F2 peacock familiar renamed Murugan->PARAVANI across Ch 7/20/21 + T3_Familiars_Named + Creature_Roster + Chapter_Index (a deities-are-real §17.1 fix: a deity-name on a controllable familiar is the /Kaggen violation; Paravani is the canonical peacock-mount name; every deity reference preserved), the dropped ratified region_secondary site Golconda woven in (the Deccan diamond/wootz node grounding LINK_0184), Palani->Soorasamharam-remnant (Tiruchendur is the Soorasamharam locus), LINK_0066 Frame-A clarifier, BE_0007_S2 counter vril->bearing. Ch 8 (Swahili Coast, HARD-LINE, 41c7a6a): the malevolent sea-shetani/jini restoration (a reef-wrecker bound by a Pemba mchawi's uchawi, faced with the waganga's ngoma; real within Swahili-Islamic cosmology, never Islam=superstition, grounded in the older sea-jini not Popobawa; receiving LINK_0149/0168), with the ratified Stage-2 Q1-Q6 handling PRESERVED unchanged (House name/pattern held from the player; Sayyid personal-bargain care; Sealed-Letter reveal; FULLY_AWARE via briefed-intel not a vril read; slave-trade elevated-care via Rasheed). Each: v2.4->v2.5 (7 golden blocks added), Layer-1 traversal woven, exhaustive link cross-check, D-06 age-bug fixes (Ch 6 'turning eight'->10; Ch 7 'eight/nine'->10). All committed gates-green (9/9 exit 0); Ch 6/7 critic-verified with fixes applied, Ch 8 critic in-flight. Also landed: docs/TRANSITION_TREATMENT.md (Layer-1 traversal in the golden bar wired into /spine-chapter + DOC_MAP; Layer-2 arrival/departure reserved for the Range Review) + the confirmed go-forward cadence (Ch 22+ ranges; endgame split 69-73/74-77; Epilogue then Prologue+Ch1). LESSON reinforced: the /spine-chapter Step-0 coverage-check must verify the LIVE Chapter_Index region_secondary too (Golconda was a dropped ratified site, the Ch-5-SPREAD class of miss).
[Ch 9-12 GOLDEN re-enrichment, 2026-07-08/09 (autonomous night run — golden Ch 6-12 batch COMPLETE)] Grid: Golden re-enrichment (Phase 3) + Layer-1 traversal + malevolent-being restoration + living-source fixes + link homing. Ch 9 (Ethiopia, ELEVATED, 7537c51 + fix-forward 59a3fbb): Werzelya (the Kebra-Nagast child-devouring witch) defeated by inscribing the debtera's Ge'ez protective scroll (grounds LINK_0158/0169, receives the abiku LINK_0160 from Ch 12); the Abuna->Liqä-Mäzämmir reframe + luminous-faith care PRESERVED; the "Mahram Bilqis" region_secondary is actually the Awwam Temple at Marib, YEMEN -> D-11; Ge'ez-as-abugida-not-first-alphabet + Thread-19 1-Enoch + Nehushtan-not-first-serpent fixes. Ch 10 (East African Rift Valley, HIGH, c55f81e): the //gauwasi grounding (the Ju|'hoansi sickness-arrow death-spirits sent by //Gauwa, warded by Kxao's n/um !kia dance per Marshall/Katz/Biesele; the v2.4 "negative-consciousness manifestation" sanitized-construct fixed); the RR-12 San de-flattening PRESERVED (/Xam, //Gwi, Ju|'hoansi distinct; the Ju|'hoan-specific lexicon attributed to the Ju|'hoansi only; //Gwi oracle via LINK_0075); the 70ky rock-ART overstatement fixed (~77ky Blombos engraving distinguished from ~25-30ky /Xam painting); BE_0010 re-skinned off "environmental_manifestation"; eight CH_10 links homed; D-12 FLAGGED (the San staged ~9,000km from home — the Rift's own peoples are the Hadza/Sandawe — + the CHAR_0072 Lebogang Maasai name-culture mismatch). Ch 11 (Congo Basin, ELEVATED, 076197e): v2.4->v2.5 (7 golden blocks) + Layer-1 (arrival->net-hunt/molimo camp->Bwiti ceremony->river-python->Free State station->recognized-by-the-land departure); the benevolent-forest cosmology surfaced (Turnbull: the forest sleeps and is sung awake by the molimo, misfortune never an evil agent); the ENRICHMENT_PROPOSAL [LEAVE] honored and made legible — NO folklore malevolent-being imported (the biloko are Mongo-Nkundo, not Baka/Mbuti; the deliberate absence is the ethnographic point), the sole antagonist the historical Free State machine; 4 links homed (received LINK_0114 bodhi->iboga + LINK_0126 Marma->Bwiti Wounded-Healer; originating LINK_0116/0127). Critic MAJOR (fixed): "Belgian Congo Free State"/"Belgian Free State" is a historical conflation — the 1885-1908 Etat Independant du Congo was Leopold II's PRIVATE domain, NOT a Belgian state (Belgian Congo only post-1908 annexation); corrected across the spine + BE_0011 persona + propagated to the living-source RCM (7 instances) -> "Congo Free State" (mis-attributing it to Belgium mis-assigns the accountability the chapter keeps intact). Plus MINORs: Thread-5 Iroko reframed as the West-African-Yoruba axis-mundi lineage the thread bridges TOWARD (not a Baka/Mbuti tradition); Thread-4 flood-memory restored to the RCM contact-context hedge; sub-boss S-labels corrected. Ch 12 (West Africa, ELEVATED, 0ce4ba3): v2.4->v2.5 + Layer-1 (Ile-Ife bronze city->Ifa diviner + Ajogun/abiku warding->Ouidah python temple + slaving factory->Abomey court + the Dahomey Decision->Bandiagara Dogon escarpment->departure); the STRONG_ENRICH malevolent-being restoration — the tradition's OWN condemned forces warded by Ifa (never worshipped, opposite of the revered orisha): the Ajogun led by Iku/Death as the new materialized-affliction sub-boss BE_0012_S4 (divine-then-ward via the 256-Odu, making Ifa load-bearing and fitting puzzle_routed), the abiku spirit-children as the SQ1 family-haunting (homes LINK_0160 -> Ch 9 Werzelya), the Ewe-Fon adze as folklore (receives LINK_0150 from Ch 10); Esu held as the honored crossroads-messenger (homes LINK_0162 -> Ch 23 Hermes), never an antagonist; all 22 CH_12 links homed (was 10); D-02/D-03 + the Reis/Vaz/Senami/Gbetosi naming reframes + the Dahomey honest-history §5.5 assimilation test PRESERVED; the Amadigne/Amma deity-name-echo flag carried. Each: registry scattered (BE_0010 re-skin, BE_0011 persona, BE_0012_S4 added, Chapter_Index folklore_entities/compliance/word-count/combat_framing), fidelity baseline refreshed in-commit, gates 9/9 exit 0, 4-lens fresh-context critic (Ch 9/10/11 GO_WITH_FIXES applied; Ch 12 critic in-flight wf_b2337661-78c). The systemic Murugan->PARAVANI §17.1 familiar fix swept every remaining spine (Ch 10/11/12). LESSON (durable): the golden pass must home ALL links (received + originating) — the v2.4 builds homed only originating links, dropping the received cross-chapter payoffs; and a real historical polity's exact name matters for §17.1 accountability (Congo Free State != Belgian Congo).
[RR-22 Range Review — Ch 2-21 post-golden-enrichment, 2026-07-09 (autonomous night run)] Grid: Range Review (the mandatory RR-every-10 gate, brief broadened to the full Ch 2-21 range per Josh's confirmed plan, because the golden re-enrichment (Ch 2-12) + the Layer-1 traversal treatment both landed across the range). Ran as FOUR chained Workflows. (1) AUDIT (wf_7b6067d0): 20 per-chapter grids (care/grounding/reveal/continuity/schema + Layer-1 presence) + 4 cross-cutting invariants (link symmetry, recurring-element consistency, reveal continuity, the continuity chain) + synthesis. Verdict BLOCKER — 1 CRITICAL reveal-discipline leak at Ch 19 (the body surfaced the antagonist PATTERN to the PLAYER as a certainty: "the same hand that edited the Levant's record and spoke the fairy tongue at the ziggurat has learned to watch", resolving the Ch 17/18/19 antagonists into one connected agent while the same chapter asserts the pattern is "still entirely unseen by the player") + ~13 MAJOR + ~20 MINOR + 11 chapters PARTIAL on Layer-1. (2) FIX APPLICATION (wf_6900fb31, one agent per chapter editing its own file): the CRITICAL recast to unresolved unnamed unease; the Ch 13 "seventy-thousand-year" rock-art overstatement de-conflated (painting ~25-30k vs Blombos ochre ~77-100k) + n/um re-scoped to the Ju|'hoan strand (un-flattening the /Xam per Ch 10); Ch 15 F2 Murugan->Paravani (the rename straggler) + Osiris->Eleusis/Ra->Apollo relabeled comparative-parallel (off Herodotean diffusionism) + 7 received links enumerated; Ch 16 F2 restored across the Ch15->16 seam + the Sanur Octopus (W4) continuity restored Ch 15-21; Ch 11 the molimo re-attributed to the Mbuti (Apenda) not the Baka elder (two distinct peoples); Ch 6 Sri Maha Bodhi 236->288 BCE; Ch 18 Baalbek Trilithon attributed to Roman-period engineering (off the alt-archaeology premise); the Layer-1 traversal retrofit of 11 PARTIAL chapters (Ch 6/9/10/12/14/15/16/17/18/19/20/21 — the protagonist now physically walks every key site in traveled order, incl. the Akan — a Ch 12 title people previously absent from L1); + ~20 MINOR grounding/continuity fixes. (3) ADVERSARIAL VERIFICATION (wf_5adac7dc): verdict FIXES_NEEDED — caught 2 NEW reveal leaks the parallel Layer-1 body-rewrites had INTRODUCED (Ch 17 "the thing that has been reaching for her all along... It has always known"; Ch 18 "the same hand that spoke the fairy tongue" personalizing toward a single agent), a geographically-backwards Ch 20 reorder (Pamir/Wakhan passes placed AFTER the eastern Tarim), 2 mechanical-anchor stragglers (Ch 11 Iyenge okapi, Ch 13 /Una n|um), and the LINK_0059/0062 registry rows still carrying reception-transmission (diffusion) framing despite the prose relabel — all 10 fixed (the Ch 17/18 leaks recast to method-level / her-uncertain-dread; the Ch 20 order corrected to Sogdiana->passes->Tarim->Gansu->Dunhuang; LINK_0059/0062 reclassified parallel-independent). (4) REVEAL RE-VERIFY (wf_1bd63807): all four antagonist-engine chapters (Ch 17/18/19/20) SAFE; two cost-free precautionary hardenings applied on the calibrated edges (Ch 18 "watched twice"->"whose signature she half-recognizes"; Ch 19 "the same wrongness... a recurrence"->"a wrongness that rhymes with... something"). Gates 9/9 exit 0 at every step; fidelity baseline refreshed in each fix commit; body word counts synced. Commits 0c5178b (fix), 8a7581c (verify fix-forward), 06d28d2 (reveal hardening), 4d90fa7 (report). Tag spine/rr-22; report docs/spine/range_reviews/RR_22.md. Josh flags filed: D-13 (Ch 4 Majapahit 1200 CE era anachronism). Verdict: Ch 2-21 RATIFIABLE (v2.5 schema throughout, malevolent-being restorations grounded, Layer-1 in every body, cross-chapter link symmetry + recurring-element consistency + reveal continuity + the continuity chain all verified), pending Josh's decision-batch sign-off. LESSON (durable): a parallel fan-out fix pass MUST be adversarially verified before commit-as-final — the verify pass caught 2 fresh reveal leaks the Layer-1 body-rewrites introduced (an agent rewriting prose to add traversal re-narrated the antagonist as a single connected agent); verify-don't-trust was load-bearing. Cardinal reveal discipline (no player-facing House-of-Velheim name/family/pattern before ~Ch 38) is the single most fragile invariant under prose rewrites.
[Task #13A — WS8 Design Fix #1: the Ch-76/77 presence funding + the diction de-collision (the arc's single CRITICAL prose fix), 2026-07-13 (autonomous)] Grid: WS8 DESIGN FIX #1 (FINDINGS §5 + §13.1), per docs/proposals/AAA_REARCHITECTURE_PROPOSAL.md. THE PROBLEM: Ch 77's payoff asserts a lifetime of visitation by the Grand-Sage presence — the recognition "assembles itself out of... the light that had no source in the driest year... the direction of attention that was never an instruction... the quality of light she could never quite hold on to when she woke" — but the prior 74 chapters deposited NONE of it (the "always" told at payoff, not funded); AND the presence was narrated as "the FAMILIAR luminous shape/presence" while the actual Child Familiar (the 22nd-slot) stands at her shoulder in the same waterfall scene (Ch 77 L19), an adjective/noun pun that let a close reader fuse the two and mis-aim the game's biggest reveal. NB: the endgame re-cascade had already scrubbed the OLD Ch-76 collision (Ch 76 L33 now clean Register-A "the visions have shown across the whole arc") and had MOVED the pun into Ch 77 when the approach folded there — so the deposits were needed MORE, not less. THE FIX (two parts, both reveal-disciplined at the strictest tier). Part A — FIVE never-explained Register-A luminous deposits, each a single dismissed impression with a mundane in-the-moment cause, each funding its exact Ch-77 collection phrase, each in its host chapter's own pronoun register: Ch 2 Flores (the child/they) a sourceless lightening of the air in the depleted dark laid to hungry eyes -> "the light that had no source in the driest year" (placed OFF the Child-Familiar loss beat); Ch 14 Kush (she) a bodiless warmth at her BACK taken for the day's heat -> "a warmth" (firewalled from the familiar's EMBODIED, heartbeat-bearing, at-her-SIDE warmth); Ch 21 China (she) an attention-lean at a road-fork called "a traveler's hunch" -> "the direction of attention that was never an instruction"; Ch 36 Mid-Atlantic (she) a forgotten water-DREAM of a high fall and a still pool -> "the quality of light she could never quite hold on to when she woke" + "seen this place a hundred times and never once with her feet" (the ONLY site pre-image); Ch 50 Amazon (she) a river-brightness taken for glare -> the "always" up to the approach (placed AWAY from the family forced-construct/vril-forensics beat so it cannot read as a Velheim asset tell). Part B — the diction de-collision: Ch 77 L25 "the familiar luminous shape" -> "the long-known luminous shape"; L80 "the familiar luminous presence" -> "the long-known luminous presence" (the adjective "familiar" banned for the Grand-Sage presence entirely; grep confirms zero "familiar luminous" remain; every surviving "familiar" is the NOUN Child-Familiar / schema field). The two registers now share NO word: Register A (light/sourceless/warmth-no-body/lean-of-attention/falling-water-shown) is the Grand Sage's alone; Register B (a presence/edge-of-her-hearing/at-her-side/heartbeat/following/the-one-who-came-back) is the Child Familiar's alone (Ch 57 L32 tease, Ch 58 L30/34 resolution — untouched). VERIFY: mandatory reveal-discipline re-verify Workflow (wf_5c317e07-2e3, 6 fresh-context adversarial critics — 5 deposit nodes + the Ch-77 scrub/firewall) returned ALL GO — every deposit register_A_clean, whoframe_leak=false, familiar_register_B_leak=false, thesis/Grand-Sage/House leak=false, pronoun_register_ok, funds_ch77_phrase; the scrub critic confirmed the two beings can stand in one frame with no reader able to fuse them and the "always" is now funded not asserted. FIX-FORWARD (belt-and-suspenders on the CRITICAL firewall): the Ch-50 deposit's "at the edge of her sight" -> "in the corner of her eye" to remove even the STRUCTURAL rhyme with the familiar's exclusive "at the edge of her hearing" frame (critic-flagged non-blocking, cleared, hardened anyway). Gates 10/10 exit 0 (deposits clear the §17.14 lint gate); no registry CSV touched (prose-only), so no baseline refresh. The deposits STRENGTHEN the preserved reveal ladder — they carry no thesis, no Grand-Sage identity, no House pattern, no agent-noun; they reframe only in hindsight after Ch 76-77, paying from real seeds what Ch 77 previously only asserted. LESSON (durable): a payoff that says "always" MUST be funded from earlier dismissed deposits, and when two entities (the Grand Sage / the Child Familiar) share a scene, their vocabularies must share NO word (not even a phrase-FRAME like "at the edge of her ___") — a single shared scaffold re-arms the collision the fix exists to kill.
[Task #13B P2 — the membrane scrub (FINDINGS Top-10 #3: purge designer-vocabulary from body prose), 2026-07-13 (autonomous)] Grid: WS8 pass P2. Scanned every "## Body prose" section arc-wide for the build layer speaking in the story's mouth and re-rendered each in the fiction's own register (16 chapters). Removed: "the player" (CH_34 "lie to the player"->"pretend to herself"; CH_42 "The player will meet her later"->"Their paths will cross later"; CH_43 "puts them in the player's own hands"->"here she takes them up in her own hands"; CH_44 "the player will meet later"->"she will meet later"); "the game" as the work (CH_44 "the game refuses it"->"is refused here" — §17.1 antisemitism guardrail CONTENT fully preserved, only the meta word changed; CH_47 "the game slows and lowers its voice"->"here she goes carefully and quiet"; CH_48 "The game does not tell her"->"Nothing tells her"; CH_03 "the shape of the game to come"->"the shape of what is coming"); "playable" (CH_42 "a real playable thing"->"a real thing to be faced"); the medium-naming thesis statement (CH_15 "this is the chapter's signature: the three-layer thesis of the whole game made playable at a single boss"->"and all three are real and lead to the same end" — removing a thesis-STRUCTURE statement from body prose IMPROVES reveal discipline); the designer chapter-counts (CH_18 "for sixteen chapters"->"since the beginning"; CH_37 "for two chapters" x2->"since the last landfall"; CH_48 "run for ten chapters"->"run for the rest of the journey"; CH_38 "For thirty-six chapters the child has been the keeper"->"For the whole road behind her"); the self-referential narrator moves (CH_02 "the story will not say aloud"-> dropped; CH_15 "a debt the story was keeping"->"a debt long kept", "the threshold the arc has been withholding"->"the long climb has been withholding"); and "the arc" as a build/narrative-craft term scrubbed to "the journey/road/world" (CH_06/20/23/40 + CH_37/38 flood-memory motif "thirty forms across the arc"->"across the world"; CH_38 body "records the arc forward"->"records what comes after", anchor-block occurrences left as design metadata). ALSO folds TWO named fixes: CH_02's Ch-2 narrator hedge ("watches it die, or watches something close enough to dying that the belief will hold for the rest of the arc")->("watches it die") — the wink that SPENT Ch-58's Child-Familiar-return surprise is removed, the loss now the child's genuine POV-limited belief (glimpsed from a crack, in the dark, so the canonical Ch-58 escape is not a cheat); and P3(a) reveal-safe — CH_03's healer's-child over-promise ("a watching that will not resolve for ten chapters", which FINDINGS #4 flags as a narrator IOU inviting a resolution not yet authored) UNSEEDED to "a watching the protagonist feels and does not yet understand" (mystery stays live, no narrator promise; the genuine origin-mystery + name remain P3 CARDINAL, flagged to Josh at Ch-65 Q4). LEFT (out of P2's medium-naming scope): the corpus-wide "the chapter is about X" authorial-thematic voice (a softer register tic, not a build-seam) and the anchor/schema-block design vocabulary (legitimate there — never player-facing). VERIFY: fresh-context adversarial reveal + meaning-preservation critic — GO on the primary gate (reveal-status + meaning fully preserved across all edits, no new leak; §17.1 guardrail intact; Ch-58 surprise preserved; Ch-3 mystery live), one completeness miss (CH_38 line-34 residual count+arc) FIXED. Not-in-fiction false-positives correctly left: "the game" = hunted quarry (CH_11) / the Maya ballgame (CH_71) / the game-mother Caipora (CH_50); "the story" = the family's in-world cover-story (CH_46/53); CH_01/PROLOGUE "the player" = the intentional character-creation/prologue framing conceit. Gates 10/10 exit 0. LESSON (durable): scrub the build layer's medium-naming vocabulary (player/game/playable/thesis/N-chapters) from body prose but PRESERVE it in schema/anchor blocks (design metadata the player never sees) and distinguish it from legitimate in-fiction homographs ("the game" = quarry; "the story" = a cover-story) — a blind grep-and-replace would corrupt the fiction.
[Task #13B P3 — the healer's-child debts (FINDINGS Top-10 #4), 2026-07-13 (autonomous)] Grid: WS8 pass P3, three sub-items, all now closed. (a) The Ch-3 "watching that will not resolve for ten chapters" narrator over-promise — UNSEEDED in P2 to "a watching the protagonist feels and does not yet understand" (mystery live, no IOU). (b) The Ch-65 stay-or-go choice — CONFIRMED already in her own beat in body prose (CH_65 "stands with her at the threshold and faces the threshold's own question — whether to go on with her into what waits past the ice, or to stay in the wounded world") and already Josh-ruled NON-GATING (D-23, both Continuation and Departure offered on every path); no work needed. (c) The name — NOT a CARDINAL fork after all: Josh already RATIFIED "Ntala" (Manggarai "star", gender-neutral) in the naming slate; the gap was that the ratified name had never been propagated into the prose (CH_75 Q7 flag: deferred to a single cross-corpus pass). APPLIED that pass (WS8 FINDINGS #4c "name her AND make it mean something"): the name is INTRODUCED at CH_13 at her active-join, tied to the end of her unsigned-notes anonymity ("she signs the next note — the first she does not leave unsigned — Ntala, and begins to write"), and USED at the peak healer's-child beats — CH_38 the journal handoff ("Ntala gives the book into her hands"), CH_57 the record made public ("She lets Ntala make the record public at last"), CH_65 the threshold ("Ntala, the one who has walked beside her the whole way... stands with her at the threshold") — plus the endgame folds (CH_66-77 anchors already carry Ntala). The epithet "the healer's child (CHAR_0002)" is RETAINED by design as the meaningful recurring descriptor (carries her origin as Mama Klara's child); a flattening find-replace was deliberately NOT done. CH_75 Q7 flag updated FLAGGED->APPLIED. Gates 10/10 exit 0. The origin-mystery (WHY she followed) is left un-promised (unseeded) rather than authored — a genuine character-canon deepening Josh may add later, no longer a dangling debt. LESSON (durable): before treating a FINDINGS "CARDINAL fork" as open, CHECK the decision batch — the name + the stay/go model were both already Josh-ratified (Ntala; D-23 non-gating); the only real work was propagating a decision already made.
[Task #13B P7 — the coda rationing (FINDINGS Top-10 #2 tail / §11), 2026-07-13 (autonomous)] Grid: WS8 pass P7. The "the scale is nearly full / she goes on" countdown coda-chain was landing as a near-identical chapter-CLOSER ~11 times (scale-nearly-full at CH_60/61/62/63/64; bare "she goes on." at CH_60/61/62/63/67/68/69), dulling the two anchors that must detonate. THINNED to its anchors by cutting the redundant closers in five chapters (mostly deletion, ethic preserved): CH_60 (cut "and the scale... is nearly full. A few more crossings... She goes on." -> ends on the sword + the promise); CH_61 (cut "The scale... nearly full... One more crossing... She goes on" -> keeps the stakes-realization reworded + ends on the intimate "She does not let go of Ana's hand for a long while"); CH_62 (cut scale + next-crossing + goes-on -> "what remains now is not another front but the reckoning itself"); CH_63 (cut "and the scale... nearly full. One crossing remains... She goes on." -> ends on "The fifth front is broken, the sites left in the hands that always kept them."); CH_68 (cut "— and she goes on" -> ends on "came the right way"). KEPT as the anchored uses: CH_59 (the scale-reading-coming setup), CH_64 ("The scale is nearly full. One crossing remains" — the last before the lock-in), CH_65 ("The scale is full. The path is locked." — the lock-in payoff), CH_67 + CH_69 ("she goes on" — the Realm-Road connective, kept sparingly and once directional). NET ~11 -> ~5 anchored, distinct uses; each remaining closer now stands out. NOTE (proposal-vs-build drift, resolved): P7 references "Ch-70's 'She stays.'" as the detonation to protect, but the endgame RE-CASCADE (post-proposal) rebuilt CH_70 as Hades/Elysium with a stronger myth-grounded climax — "the descent is easy, the return is the labor" + the Lethe/Mnemosyne memory-choice at the two springs (drink memory, do the labor of the return) — which SUPERSEDES the old bare "She stays." beat; the coda-thinning protects THAT distinct closer instead (no "She stays" beat was added — inventing one would contradict the re-cascade's return-not-stay design). All edits are coda DELETIONS + one post-Ch-38 stakes reword (family already named by Ch 61), reveal-neutral by construction (no thesis/Grand-Sage content added). Gates 10/10 exit 0. LESSON (durable): a repeated chapter-CLOSER formula ("she goes on") reads as a tic and steals the punch from the one place the restraint should break; ration it to 2-3 anchored uses and let the distinct climaxes (the lock-in, the underworld return, "one door left") carry their own weight — and when a FINDINGS fix names a specific beat ("Ch-70 'She stays'"), verify the beat still exists after later re-cascades before "protecting" it.
[Task #13B P4+P6 — the lost-familiar grief thread + the register-warmth seams (FINDINGS Top-10 #6 + #5), 2026-07-13 (autonomous)] Grid: two WS8 additive passes, verified together. P4 (grief thread): three one-line Register-B aches for the LOST CHILD FAMILIAR (the being that "bites once, hard, and bolts" at Ch 2, believed dead, reunited alive Ch 58) so the Ch-58 reunion lands as an ANSWERED WOUND, not a recovered asset — CH_08 (they/child register: the first warm thing bit them and bolted into the dark of the cave and did not come back; some part of them has not let a living thing that close since — placed on the "bench/door" first-rootedness beat), CH_33 (she/her: she presses the old scar from the bite she took the first morning of her life, the only mark it left — on the faceless-net vulnerability beat), CH_56 (she/her: every bond since the cave taken with a part held back, braced for the morning it bolts and does not come back — placed right before the Ch-57/58 setup, the ice that "holds both its dead and its living"). FIREWALLED from the DF1 Register-A deposits (Ch 2/14/21/36/50): NO chapter overlap, embodied-companion register ONLY (bite/scar/cave/held-back bond), never the Grand-Sage's sourceless-light/warmth-with-no-body/falling-water-shown; NO hope-of-return telegraph (pure grief — she believes it dead); never the reserved Ch-57 tease phrase "a presence at the edge of her hearing". P6 (warmth seams): two companion-borne light beats to break the monotone (every nearby grief note taller by contrast) — CH_27 Ntala's dry teasing ("for someone who can read the oldest writing in the world, her own hand is a fright... the journal has lasted this long mostly because she is not allowed to touch a page of it" — sets up the Ch-38 handoff irony) and CH_41 Ana's dryness at her costly return ("the company has not improved and the cooking has got worse", then picks up a blade). VERIFY: fresh-context adversarial reveal + two-register-firewall critic — GO (all three aches pure Register B with the firewall holding — the shared lexeme "warm thing" is the deliberate EMBODIED INVERSE of Register A's disembodied "warmth with no body", not a bleed; no hope-of-return; no House/thesis/Grand-Sage leak; pronoun registers matched; both warmth beats in-voice with correct companions). FIX-FORWARD (belt-and-suspenders, the project's known invoke-and-negate leak-pattern): CH_56 "she has never once let herself believe it might not have" (a verbalized survival-counterfactual) -> "she has never once let herself hope otherwise" (grief kept, counterfactual removed). Gates 10/10 exit 0. LESSON (durable): the grief-thread (Register B) and the presence deposits (Register A) are the same one-line technique in opposite registers across the same middle arc — keep them on DIFFERENT chapters and let the ONE shared word ("warm") be a deliberate inverse, and scrub any invoke-and-negate counterfactual even on the familiar thread (the pattern leaks wherever it appears).
[Task #13B P5 — the scene-time pilot (FINDINGS Top-10 #10, the ceiling-raiser; D-PROSE.c a PILOT for Josh), 2026-07-13 (autonomous)] Grid: WS8 pass P5 — the corpus is written entirely in summary voice (no direct speech); this PILOTS the drop into close scene at two chapters, incl. the arc's FIRST line of actual speech, to be measured and (Josh's call) extended to 8-10 peaks or reverted. CH_16 (the grammar-night): a close-scene beat at the moment Ntala cracks the unread Indus script by pure pattern-counting, carrying the arc's one spoken line — "You feel them; I count them. Between us we might get the whole of it." — framed so it lands because the voice never speaks ("the plain words land in the dark of the dead city heavier than any wall of unread signs, because the habit of both of them is to say nothing at all"); the name "Ntala" emerges at the instant she speaks (person-out-of-function). CH_58 (the reunion): a close SENSORY beat (wordless — the Child Familiar does not speak) grounding the abstract return in the body and PAYING the P4 grief-thread — "the warm living weight of it is against her... a heartbeat where for the whole long road there was none... and she goes down onto the ice and holds it and does not, for once, hold any of it back" (closes CH_56's "every bond taken with a part of herself held back"). VERIFY: fresh-context adversarial reveal + register + CRAFT critic — GO (reveal-safe; the CH-58 embodiment markers heartbeat+weight are the exact ANTI-Grand-Sage firewall, un-fusable with the disembodied luminous presence, and are in fact the mechanism that resolves the "sensed presence" into a body; the speech reads earned and disciplined; the grief-callback coheres; straight quotes, no §17.14 emphasis). FIX-FORWARD (both critic-flagged): 3a CH_16 relieved a "The child puts it plainly —" sentence that re-explained the spoken line (-> "What the two of them are doing is this:", elaboration not restatement); 3b CH_58 made SPECIES-AGNOSTIC — the 22nd-slot child familiar is player-selected across 12 elven species (Ground/Flying/Water, T3_Familiars_Named §5.1), so "small ... in her arms" over-committed; changed to "warm living weight ... against her" (keeps the firewall markers, drops the small-scoopable commitment; consistent with the corpus "write the default, vary in production" convention and §5.6 per-player reunion rendering). Gates 10/10 exit 0. STATUS: the pilot is APPLIED at the two nodes; whether to EXTEND scene-time/speech to 8-10 arc peaks is a genuine style-direction call left to Josh (D-PROSE.c — "approve the pilot, not a blanket rewrite"). LESSON (durable): introducing the first direct speech into a summary-voice corpus works ONLY if the prose earns the silence-breaking (name the rarity in the text) and the dose is one line then back to summary; and a player-VARIABLE entity (the 22nd-slot familiar) must be rendered species-agnostic in the single spine line, keeping only the load-bearing invariant (here the anti-Grand-Sage heartbeat/weight).
[Task #13B P8 (bounded subset) — transition-asserted allies rendered in body prose (FINDINGS honorable-mentions), 2026-07-13 (autonomous)] Grid: WS8 pass P8, the two NAMED bounded items done; the diffuse items deferred to final verification. DONE: the two allies who existed only in the ally-NPC anchor blocks now appear in BODY PROSE — CH_44 the Haudenosaunee Faithkeeper Kanenhí:io (the Great-Law teaching now delivered IN SCENE through her — "She sits at the edge of a longhouse where a Faithkeeper named Kanenhí:io teaches her — as a guest, never a participant — the shape of a constitution older than the United States"; this also discharges P2's honorable-mention "Ch-44 historiography via the faithkeeper, delivered in scene not from the lectern") and CH_52 the living Aymara heritage-keeper Nayra Condori ("an Aymara heritage-keeper named Nayra Condori walks her through the stones as what they are — her people's work, not a riddle for anyone else to solve — and is patient about the century of visitors who could believe anyone raised them but the Aymara"; renders a living Indigenous keeper with agency, countering the ancient-aliens credit-theft, care-clean). Both care-appropriate (living Indigenous persons, guest-framing preserved), reveal-neutral. Gates 10/10 exit 0. DEFERRED to the final whole-arc verification (Task #15) with reasoning: (1) the they->she pronoun-crystallization marker at ~Ch 12 — the protagonist's gender presentation is PLAYER-CHOSEN (the spine uses "she" as the default-render, like the 22nd-slot familiar species), so a "crystallization clause" touches a Josh-owned rendering decision, not a free authorial call; flag, do not invent; (2) "for the first time" rationing (heaviest at CH_38 x6, several x5) — a diffuse per-instance judgment thin best done in one focused final pass; (3) the ~60 arrival-sentence opening-variety sweep — diffuse, lowest-leverage; (4) the Ch 36-37 merge/differentiate (FINDINGS #7) — a structural call partly discharged already (DF1 Deposit 4's water-dream now textures Ch 36, differentiating it from Ch 37). LESSON (durable): an ally asserted only in a transition/anchor block is invisible to the player — the body prose is the only player-facing surface, so every load-bearing ally needs at least one in-scene sentence there.
[Task #13C-1 — the Games & Contests spine (WS1 flagship; Josh's gladiator->Olympics mandate), 2026-07-13 (autonomous)] Grid: the FIRST 13C chunk. The built ancient arc mined its contests as LORE; the Games-&-Contests pillar (Josh's single explicit example) had NO playable debut anywhere in Ch 2-38. Wove ONE playable/scored/staked contest beat into five nodes (authored + adversarially verified per chapter via wf_09df1b95-bf5, each editing its own file). CH_03 caci — the arc's FIRST fought contest: earned entry on the Todo royal ground, a scored/timed whip-and-shield parry-duel vouched for by the age-peer Ana (recurs Ch 27/28), seeding the arena->stadium era-rhyme vocabulary. CH_07 Kalaripayattu — a graded martial SCHOOL (Meithari->Kolthari->Ankathari) with scored sparring bouts and the secret Marmakkalai mastery gate, the marma knowledge honored (heals-and-kills held in one hand), the guru relationship intact. CH_22 Naadam — the three-games tournament (bokh / horse-race / archery) as a real competed festival, kept CLEANLY SEPARATE from the sacred coerced-drum boo beat, a joy/festival counterweight. CH_23 Olympia — the pankration contest (the two-prohibition empty-hand fight) under the sacred truce, the gladiator->Olympics ORIGIN-anchor seeded as a taste (not over-signaled). CH_28 THE CAPTURE FLAGSHIP (WS6, Josh's named pair; the arc's first vulnerability beat) — INVERTED the built free-the-ludus-from-outside into: she is genuinely CAPTURED into the Senator's ludus, cut off from familiars + the healer's child, wins the way the enslaved win (never the kill the editor wants), organizes the fighters, and rises with them (Spartacus-echo) — HL_0003 intact (the enslaved are the oppressed she frees; the institution faced as history, never spectacle), the proof "she can be caught" carried out like a coal. VERIFY verdicts: CH_07/22/23 GO; CH_03/28 GO_WITH_FIXES applied — CH_03 (care) the child peer-bout now won on the clean turn + kept count, first-blood re-attributed to the elders' ceremonial FRAME not drawn on the 9-year-old Ana, + shield material de-conflicted (rattan/hide->shield); CH_28 (coherence) the uprising's front is now "the fighters she has won over" not the cut-off Ana (keeps "caught alone" true + strengthens HL_0003). Also hardened a PRE-EXISTING CH_22 reveal edge (the closing "the powers that have learned to steal what men hold holy" — a plural agent-noun + developed method) -> "the old theft she has met in every land so far, the holy taken from the people who keep it" (a recurring wrong-TYPE, no agent-noun). Gates 10/10 exit 0. The new MG_/School registry rows are HELD for the WS7 system sign-off (Josh). Full 13C chunk plan: docs/spine/TASK_13C_BUILD_PLAN.md. LESSON (durable): a mutating author fan-out (one agent per chapter, one file each, NO gates/git) + a per-chapter adversarial care/reveal/coherence verify is the right shape for enrichment beats — the verify caught a real care off-note (child first-blood) and a real coherence break (caught-alone vs Ana-at-the-front) that a gate cannot see; and the verify usefully surfaces PRE-EXISTING reveal edges in the touched files worth hardening in the same commit.
[Task #13C-2 — the Thread-2 dragon/serpent through-line (WS1 #5; the matrix's highest-leverage span fix), 2026-07-13 (autonomous)] Grid: the second 13C chunk. Five chapters each carried a dragon-combat hero-cycle played as read-lore; staged each as a real fought/contended marquee encounter with a shared serpent archetype (the self-assembling L3 "similar-monsters" resonance, felt-never-declared, and the pre-population of the Realm-Road dragon lineage). Authored + adversarially verified per chapter (wf_b7f893c0-f76, one file each). CH_19 Azhi Dahaka at Damavand (GO) — the three-headed bound serpent contended head-by-head with the benevolent Simurgh calling the tells, care-clean (the apostate Magus is the antagonist, the honest fire-priests on her side, HL_0109 held). CH_21 the longwang (GO) — the auspicious rain-sovereign WOKEN not slain ("no one of that land would lift a blade to it, and neither does she... not to slay but to wake it"), the koi-to-dragon resonance, the benevolent pole of the archetype. CH_24 Jormungandr (GO_WITH_FIXES) — the world-serpent's coil deepened at the skerry; FIX: renamed "vril-manifestation" -> "real cosmic world-serpent" (it collided with the chapter's dedicated term for the jarl's FALSE GOD, the ond/vril-manifestation — the two must stay distinct). CH_25 Illuyanka (GO_WITH_FIXES) — the oldest-attested Hittite dragon-fight staged (purulli-festival myth); FIXES: added Illuyanka to the Combat facet (the body staged it but the combat anchor omitted it -> contradiction); softened the "oldest dragon anyone thought to write down" overclaim (Anzu/Labbu are older) -> "one of the oldest dragons anyone ever set in writing"; dropped "seven-turned shape" (seven is Lotan's Ugaritic motif, not Illuyanka's) -> "vast coiling shape". CH_18 Litan (GO_WITH_FIXES, node_locked=FALSE) — the agent OVER-REACHED, staging the ACTUAL Ugaritic cosmic serpent as a fought boss, which CONTRADICTED the chapter's DELIBERATE §17.1 elevated-care design (Litan restricted to a mimic-construct, deities + Nehushtan never fought, combat via the antagonist — CH_18 is elevated-care for the living Abrahamic traditions + the defamatory-trope adjacency). Overriding that elevated-care design is a JOSH-level §17.1 call, so I did NOT fix-forward; instead SOFTENED the body to fit the existing design (the cosmic Litan + Baal-Hadad's binding staged as a REAL awe-ful Frame-A event, no longer read-lore, but what she ANSWERS is the mimic per line 92, the true binding the storm-god's own work not her kill) — body and anchors coherent AND the elevated-care design respected. FLAGGED the fork to Josh: docs/spine/DECISIONS_PENDING_JOSH.md # D-DRAGON-18 (mimic-only soften [RECOMMENDED, applied] vs promote the full Litan boss). Gates 10/10 exit 0. Boss_Encounter / seven-head-archetype link-graph rows are HELD for the registry follow-on + the WS7 sign-off. LESSON (durable): "stage the real dragon" is right by default, but where a chapter carries a DELIBERATE §17.1 elevated-care combat design (mimic-only, deities-never-fought), a fan-out MUST NOT override it — soften the body to fit the care design and FLAG the maximal option to Josh; a care design is not a fan-out's to overrule.
[v3 batch-2 verify — the RR-22 reveal-sweep queue + adjudications, 2026-07-14 (autonomous)] The batch-2 adversarial verify surfaced four pre-existing body-prose/L3 reveal borderlines (all verbatim from v2.5, none conversion-introduced). Applied now with critic wording: CH_09 body prose ("whether he serves something larger" organized-power invocation → "What that recognition means"), CH_17 body prose ("She does not have a name for the hunter" agent-noun → "The hunt has no shape she can name"). Adjudicated PERMITTED and kept: CH_18 L3 three-layer "the same subtle hand" (the design/L3 layer may state the truth per the antagonist-pattern-reveal ruling; player-facing surfaces may not — this is a designer-facing block). QUEUED for the RR-22 reveal sweep (adjudication requested, no wording supplied): CH_11 line ~135 objective echo of preserved body prose. Also fixed at this pass: the CH_18 Grand-Sage window labels Ch 76 → Ch 77 (the ratified REVEAL_WINDOW_REALIGNMENT convention; three stale design-layer labels).
[v3 batch-4 verify — RR reveal-sweep queue additions, 2026-07-15 (autonomous)] The batch-4 adversarial verify adjudicated CH_30's KEEP-verbatim design-layer who-frame phrases ("never assembles it into a single hand" / "the watcher" — preamble + a pre-existing Decisions entry, byte-identical to v2.5) as KEEP (design-layer latitude; every player-facing beat/reveal line uses the safe unassembled register) and QUEUED them for the standing RR reveal sweep alongside the batch-2 CH_11 item. All new-text reveal surfaces across CH_29-38 verified clean; the CH_37+CH_38 group (the reveal hinge) returned zero findings.
[v3 batch-6 verify — fix-forward + RR-62 queue, 2026-07-15 (autonomous)] All findings applied: the CH_49/CH_51 ws.vimana_5th_mode_access conflation deleted (the endgame fifth-MODE enum is NOT the coordinate hunt — runbook gotcha 20 added); CH_56 Ana brand-conditioned per FORK_CH55_A on three surfaces (the companion-conditionality MAJOR); CH_50 trimmed to the v2.5 publish-vs-hold binary (matching CH_49) with coverage notes; the pre-76 patriarch hold-note convention normalized (13 conversion-added "Cassius held" annotations re-worded across CH_50/51/54/55/58; v2.5-inherited design-layer tokens untouched per the KEEP rule); band-vocabulary and enum hygiene sweeps; CH_53's FORK re-anchoring confirmed-intended (Josh-override-able at RR-62); CH_55's consumer-less andean_ties mark dropped to faction standing. QUEUED to RR-62: the CH_53 fork re-anchoring confirmation.
[Josh rulings batch — D-TG-45 + the L3 tie-break + the book sign-off, 2026-07-15] D-TG-45 RATIFIED per the recommendation (the Ch-45 Thread-3 cell = a CH_36-class no-operation dark-cell that still counts as in-era presence; the singular total absence stays Ch 57) — grid cells applied + baseline re-emitted; THREAD_13/CH_45 mis-home corrected to NOT_PRESENT in the same pass. The L3 score-0 tie-break RULED: EVIL wins at perfect equidistance — applied to T1_Integrity §3.5 + the v3 schema flag. The 7-book BUY list purchased + the 34 care-downgrades ratified (BOOK_ACQUISITION_MINIMIZED §8 status updated). BOSS_PERSONAS de-Corr: ruled unnecessary — the design-layer truth doc stands as-is; the enforced grep-zero surfaces (spine files + registry cells) are clean and the per-batch verify greps hold the line.
[Batch-7 v3 landing (CH_59-68), 2026-07-15] Surface: the batch-7 conversion fan-out queued registry corrections + flags needing orchestrator adjudication before serial application. Resolutions applied: (1) BE_0063_S2/S3 (taniwha, aku-aku) — the b27da74 "Refuses the Leash / self-willed" row cells were RESTORED to the forced-then-freed victim frame + the F5 riders (S3: never-spectacle / never a 1862-63 re-run / Rapa Nui's own tradition never Heyerdahl / folk-category-never-named-supreme-ancestor): the F5 Option-C ruling (ecf2caa, Josh-ruled 2026-07-14, ~11h AFTER b27da74) ratified the CVD 17.1 sacredness-tier class rule — aku-aku/taniwha class = FORCEABLE-THEN-FREED, freed-victim the stronger care posture — and updated CVD + CH_63.md + BOSS_PERSONAS but never the Boss rows; the rows were the stale layer. (2) BE_0064_S1 — verbs strike/sever → evade/perceive + never-engages engagement text: the dragon-beats authoring 77b34ed (07-14 00:24) POSTDATES the J10 apply e00051d (07-13 19:50) and deliberately reasserts the watcher's dread-by-restraint ("cannot be fought and must not become the point") while answering J10's combat-emptiness with the drowned-deep dragon marquee (BE_0064_S2) as the node's real L1 fight; the Boss row's fought-route cells lag that final design. Riding to RR-62 for confirmation (a J10-item supersession by later authoring). (3) BE_0064_S2 secondary evade→contend per the same 77b34ed landed text. (4) Thread_Grid THREAD_02/CH_61 NOT_PRESENT→ANCHOR dark-cell (the aždaja marquee): the grid cell lagged the landed entry's own explicit supersession of the batch-1 #10 no-anchor ruling (BE_0061_S3 already carries T02); D-TG-45 pattern; flagged RR-62 per the entry itself. (5) WS_025 domain extension (RECOGNIZED_AS_KIN) DECLINED: CH_66/67/68 all already carry the dual-register texture convention (RECOGNIZED-AS-KIN within-thresholds gloss OVER the unchanged enum value CONCEALMENT_WITH_HOSTILE_RECOGNITION, per CH_66's own typed resolution); extending the closed enum would put two simultaneous values on one scalar — the CH_69/batch-8 build follows the same texture convention. (6) FR-06 qeqchi base-reads WIRED at CH62_B04 + CH65_B03 (in: machine-visible; the route-differentiated ally-return stays the EXISTS_UNPAID enhancement, not authored). (7) L-OP-KILL-65 (the five modern champions' kill-vs-spare differential) surfaced by multiple authors as a NEW proposal contradicting the ratified T4 2.4 canon-forced escapes — NOT typed anywhere; queued as an RR-62 agenda item for Josh. (8) BE_0065 target_type auto-slug "held_ch74" (canonical fields all say Ch 76) — non-load-bearing derived-slug artifact, rides to the D-1 registry re-key audit. (9) gates_config spine_graph gap REPAIRED: CH_39-48 (batch 5) were missing from the gate targets since their landing (the append was lost around the batch-5-era disconnect); re-added alongside CH_59-68 and all ten re-certified checker=0 at this landing. Reason: trust the latest ratified layer over any single row's label; care-frame direction follows the recorded Josh ruling (F5 Option C); grounded alignment applied, genuine proposals deferred [SRC: T0_Boss_Encounter_Registry @ BE_0063_S2] [SRC: T0_Boss_Encounter_Registry @ BE_0064_S1] [SRC: T0_Thread_Grid @ THREAD_02].
[Batch-7 verify fix-forward (CH_59-68), 2026-07-15] Surface: the batch-7 Opus verify returned 0 blockers / 5 MAJORs / ~12 minors; all adjudicated and applied same-session. MAJORS: (1) BE_0064_S1 completion — the landing's 3-cell correction left the row self-contradictory (five sibling cells still carried the J10-era fought-route frame); all five rewritten to never-engages/non-combat-mercy; the verify adversarially CONFIRMED the direction (deliberate dread-by-restraint, R-17 satisfied via the BE_0064_S2 dragon marquee — not a defang). (2) BE_0065_S1 — the CH_65 agent's "VERIFIED CLEAN" cert was materially false: the row carried a stale b27da74-era "self-willed / absent from the menagerie" parenthetical misattributing Option C (which ruled forced-then-freed) and citing the unruled J11; replaced with the F5 enumeration (taniwha/aku-aku IN the menagerie as forced victims) + care riders; target_type re-cut. (3) BE_0068 main row reconciled to J10 (host phase struck-and-purged via S1, listening layered, "nothing slain" narrowed to the sea-mother alone) — it had contradicted its own S1 sibling; residual stale narrative blocks enumerated for the future prose pass. (4+5) CH_67/CH_68 ws.identity_hiding_status machine lines led with the off-enum RECOGNIZED-AS-KIN gloss — normalized to CH_66's enum-first form (bare CONCEALMENT_WITH_HOSTILE_RECOGNITION, kinship demoted to texture note) across both §18s and all seam asserts, closing the CH_66→CH_67 seam mismatch (gate-invisible class: the checker validates keys not values — a post-pass ERROR-upgrade candidate). MINORS applied: CH_59 HL_0048 misreading corrected (the rule constrains only consecutive peaks/valleys — three standards break nothing; wording now matches CH_61); ws.familiar_bond_state threaded through the CH_59→60→61 seams to its Ch-65/75 consumers; CH_61 fork tables normalized to the §3c 8-column form + explicit ws.integrity_score writes; Thread_Grid THREAD_03/CH_61 ANCHOR→ESCALATION (the cell's own content already read escalation); CH_63 FORK_CH63_A care_band open→elevated; CH_65 connective-web mislabel ECV-11→IR-4; CH_68 S1 win-key renamed to the beat out-key + phases collapsed to P1→B06; Decisions records updated in CH_61/63/64/65/68. DECLARED (recorded in CH_68 Decisions, binding for batch 8): the post-lock convention — path_dispatch only where a band-varying surface genuinely exists; path_bucket ALL where nothing varies; the CH_67-vs-CH_68 difference is content-driven. Accepted-as-intentional: entry seams do not mirror carried-but-non-consumed exit keys (the seam sweep's optional symmetry note). CH_69 (batch 8) must apply the same enum-first WS_025 normalization to its v2.5 line 19 on conversion.
[Batch-8 v3 landing (CH_69-77 + CH_EPILOGUE), 2026-07-15] Surface: the final conversion batch (10/10 authors green) queued 8 registry corrections; all adjudicated whole-row and applied serially. (1) BE_0069.boss_name — the CVD 19.8 Maatherion→Duat rename left "taking the name of the realm" scaffolding claiming the Architect takes the real Egyptian sacred realm-name (the forbidden deity/realm-name-on-a-mortal move); both clauses rewritten: the Architect ECHOES the PRINCIPLE of Ma'at, takes NO realm-name and NO deity-name (the constructed persona-name Maatherion stays a BOSS_PERSONAS design-layer persona-name only). (2) BE_0070.primary_verb strike→pass (Cerberus is a passage-contest won, never a slaying — the row's own engagement/win cells and the spine agree). (3) BE_0072 strike/release→release/ascend (the winning verb is RELEASE per the row's own engagement text + the spine; the offered STRIKE death-blow is the F1-ruled FORK option, not the win verb). (4) BE_0074 strike→re-root + axis 45/30/25→40/40/20 (the row's own engagement cell says RE-ROOT/KEEP-WHOLE primary; the corpus never slays Nidhoggr; the spine's boss-structure + win-condition both carry 40/40/20 — the lower-confidence axis call applied as one coherent direction with the verb, personas NOT_FOUND so no tiebreak against). (5) THREAD_03/CH_75 NOT_PRESENT→ESCALATION + content_summary rewritten (the old cell carried the RETIRED antagonist-absent rationale; the WS5 Realm-at-War re-architecture makes the family's reach the faceless corrupting CONDITION — the spine Threads block + BE_0075.threads both carry T03; RR-FINAL history preserved in the new summary). (6) CHAR_0017.chapters_present Ch_41-71→Ch_41-74 (Ana carried through Ch 74 by three spine files independently; the cap predates the Realm-Road extension). (7) CH_71.mode_variety_check puzzle=N→Y (the source's own gameplay_function language types the six-Houses trial-gauntlet and manikin-and-names deception as wit-solve content). Accepted-not-corrected: BE_0069.threads retains T05 (defensible as the structural-serpent echo of the sub-encounter; the chapter-level Thread-5 anchor is genuinely NOT_PRESENT, re-homed Ch 74) — rides to D-1. CH_69 normalized its WS_025 machine lines to the enum-first form on conversion per the b7 lesson; the post-lock convention held corpus-wide (CH_69's negotiation outcome = the band-varying surface; Apep path-invariant). gates_config spine_graph targets now carry all 79 nodes + 3 exemplars (82).
[Batch-8 landing addendum, 2026-07-15] Gate-surfaced extras beyond the queued corrections: (1) topography — the stale R4/CH_71 waiver removed (its puzzle mode restored by the CH_71 fix); the R4/CH_EPILOGUE waiver reason updated (puzzle-only structural absence; a pre-existing waiver already covered the epilogue — an orchestrator mis-read briefly added a duplicate + flipped combat=N, tripping never-waivable R6; reverted same session: combat=Y rides the endgame-sandbox playable layer per Ruling 1, learning=Y kept per the typed fold, and the epilogue's fold line reconciled with its own "combat present but off-frame" clause). (2) anchors — seven fragment re-homes: CH_75's "BE_0075 Ch 75 Movement 2" ×9 → the real "## BE_0075 | Ch 75 |" heading; CH_75's CF-2 ×2 → WHOLE_ARC_CONNECTIVE_WEB (the id lives there, not the INVENTORY); CH_70's supersession-note cite → BOSS_PERSONAS # Ch 70; CH_71's cite of a nonexistent T1_Story_Spine CHAPTER 71 (the v1.0 doc ends at the early arc) → the chapter's own # Body prose; CH_74's "9.2-9.4" range fragment → 9.2 (the real heading).
[Batch-8 verify fix-forward (CH_69-77 + CH_EPILOGUE), 2026-07-15] Surface: the batch-8 Opus verify returned 0 blockers / 12 MAJORs / ~12 minors — eight of the twelve majors were ONE systemic issue: the realm-road conversions each enum-mapped ws.identity_hiding_status differently (ACTIVE_CONCEALMENT at 71/72, free-text "TRAVELER IN THE OTHERWORLD" at 73, CONCEALMENT_WITH_RECOGNIZED_ALLY at 72-exit/74/77, free-text recognized-as-kin variants at 76, REVEAL_RECOVERY at 75). ORCHESTRATOR RECONCILIATION (least-invention, extending the ratified CH_66-70 form + matching the CH_77+Epilogue critic's own fix): the bare enum CONCEALMENT_WITH_HOSTILE_RECOGNITION held INERT across the whole Ch 66→Epilogue span (the world's stance does not change while she is off-world; the sources stage no explicit world-facing transition), all kinship/traveler/father-recognition content demoted to texture notes; ZERO invented state transitions; whether the arc deserves a formal post-reveal terminal WS_025 value rides to Josh/D-1 with the CH_68 domain-gap item. All 8 seam boundaries 70→EPI now assert the identical bare enum on both faces (CH_76's seam lines never carried the key at all — added both faces at the fix-forward). Other majors: CH_76's ws.father_encounter_variant writes re-keyed from free-text to the WS_017 domain (REUNION_TGP / NEGOTIATION_GE / COMBAT_EVIL) that CH_77's father-gloss reads — the TG and GE rows had written the IDENTICAL free-text token (a real dispatch bug, now distinguished); FORK_CH74_A magnitude SIGNATURE→SUBSTANTIAL (the CH_73/75 precedent); CH_EPILOGUE stale refs re-homed ('Cassius resolved Ch 74'→Ch 76; three father-encounter 'Ch 75' refs→Ch 76 per the ratified reveal re-home + Two-Courts fold). Minors: CH_69 preamble care-cite fixed (Louhi is the HL_0122 honored-adversary, never a care-clean monster — Iku-Turso is the Ch-67 HL_0121 class); CH_70 Ntala label normalized + BE_0070 phase-map to single-beat form excluding the boss-none nekyia beat; CH_74 otherworld sites protected→false (the pilot convention) + scene rows to ALL/per_chapter_cutscene; CH_75 THREAD_03 staleness notes updated to LANDED + familiar_bond_state path-qualified (present-varying TG/GE, absent Evil). Deferred correctly: the Ch-67 dominant-mode label reconcile → RR-72. VERIFY CONFIRMATIONS (adversarial): all four batch-8 registry landing calls held (BE_0074 "NOT a defang — Níðhöggr stays a visceral fought dragon-boss"; BE_0072/0070 verb re-keys confirmed against the base→HEAD diff; BE_0069 Architect-takes-no-name verified vs CVD 19.8 + HL_0003); the reveal ladder end-to-end clean (Cassius NAMED only at CH76_B01 literal token; thesis/Grand-Sage only Ch 77; CH_74 dark, Ariosophy/Vril-Society firewalls intact); the decision-web, WS_014/WS_017 chains, and every mark→reader pair line up. WATCH (post-pass value-check candidate): CH_76's seam carries ws.cassius_velheim_state: RESOLVED — pre-existing, critic-passed, but "RESOLVED" should be verified against the WS_013 domain when the WARN→ERROR value-form upgrade lands.
[Whole-arc verify fix-forward (the final v3 round), 2026-07-15] Surface: the 5-dimension whole-arc verification (reveal ladder / connective-web / care / state-machine / machine-consumability) returned 1 BLOCKER + 9 majors + minors; all adjudicated and landed. THE BLOCKER (machine-consumability): check_spine_graph's tag() routed every live §9 "Boss structure (…the narrative lives in the beat graph)" header into the beats bucket via substring-matching — the §9 boss-index checks were VACUOUS corpus-wide (and §9.3/§9.5 citations leaked entry-header/civ-marks content into the boss bucket). Rewritten to leading-marker routing (boss before beats, §10b before §10) + a NEW sites bucket with a beat.site→§3b closure ERROR; the newly-live checks ran clean over all 79 (the authoring was disciplined even where the gate was blind) and were teeth-verified (bad phase ref + dangling site ref each exit 1). STATE-MACHINE majors landed: CH_73's path_dispatch wrote per-bucket integrity deltas (the sole post-lock violator — deltas deleted, the Arawn relationship/mark writes kept); WS_013 cassius_velheim_state re-keyed to its registry domain (FORK_CH76_A now writes RESOLVED_TGP_PURGE | RETREATED_GE | VICTORY_EVIL per bucket, patriarch_named demoted to local.*, the CH_76→77 seam + CH_77 asserts re-keyed off the bare off-domain RESOLVED); the CH_68/69/70 ws.path_bucket:LOCKED guards re-keyed to ws.path_lock_in_state (LOCKED is WS_005's value, never WS_004's); WS_018 six_option_cumulative_record made real (CH_17's fixed token replaced by per-option slot-enum appends in the fork's ws_writes; CH_28/CH_39's collapsed six-option forks re-kinded to exploration_interaction with the slot→outcome map recorded as an unauthored dialogue-build artifact — D-1); '+small'→'+Accumulative' normalized corpus-wide (~17 files, the T1 §5.1 sanctioned class); CH_57/58 symbolic guards re-keyed to derived integrity_level reads; WS_014 recorded write-only-by-design (runtime dispatcher consumers; D-1). CONNECTIVE-WEB major: IR-1's forward-track lived in a prose COLUMN invisible to the mark gate — embedded in the mark braces (live + exemplar), the column folded to opportunity_effects. CARE majors: the five J10-reverted rows adjudicated (strike restored on Jǫrmungandr's Coil / the Soorasamharam asura within its devotional frame / Olgoi-Khorkhoi / the Barrow-Wight; Naga Padoha KEPT soft as the honored/cosmic call with the supersession recorded in-chapter + in the J10 doc); CH_68's kept-verbatim prose narrowed to the ratified J10 state (the nothing-slain clause now the sea-mother's alone — Josh may re-voice). GRAMMAR: the three closed fork-table shapes ruled + normalized corpus-wide (CHOICE-8 / DISPATCH-7 with variant column and structurally-absent delta / SIX-OPTION-7; 22 files normalized by a verified Sonnet pass, 64 tables already canonical; FORK_CH76_A re-kinded combat_resolution→path_dispatch — the dispatch semantic is the fork's, the combat rides the beat/boss binding); the gate now validates headers against the closed sets (teeth-verified); schema §3c/§3d reconciled (the shapes + the ratified 7-column scene row, audio trio Cinematic-downstream). REVEAL minors: the two pre-55 de-Corr audit notes re-worded to de-attribution + design-layer-marked; the CH_28/33 D-14 constructions CONFIRMED-ONLY (RR-32's licensed organized-power-exists register governs). Deferred: the elevated-in-practice fork care_notes (D-1); the exemplar lint emphasis findings (D-1, exemplars are not lint targets). Gates 14/14 exit 0 with every upgrade live.
[The nothing-slain register scrub (Josh-RULED), 2026-07-15] Josh's ruling: the "nothing slain" register goes EVERYWHERE — not narrowed, not kept for the sea-mother. Applied corpus-wide (spine + Boss_Encounter registry + the CH_68 preamble/facets/scenes/anchors/Decisions): every assurance-of-non-killing phrase ("nothing slain / nothing is slain / heard not slain / nothing is killed / never a slaying / non-lethal by design / do not slay / listen-not-slay") retired and re-framed action-forward. Ch 68 now reads as a fight: the Mušḫuššu-class monster-host is FOUGHT AND BROKEN, its swarm destroyed where it presses, the mother drawing back only what remains — and the listening reframes as TARGETING (you listen to know where to strike and when to move while the deep tries to kill you), not mercy. The two survivals that remain are stated as facts, never as promises: the real abyssal megafauna are survived-and-calmed because they are real animals (the science register), and the sea-mother is never bodied at all (audit-only §17.1, stated as absence). The honored-adversary win-shapes stay as POSITIVE facts with the assurance phrasing gone: Louhi "repelled sovereign, dignity intact"; Cerberus "passage over the guardian, taken by strength, song, or cunning"; Níðhöggr "beaten off the root and driven back into the dark (the corpus's own shape — the serpent outlasts Völuspá itself)". KEPT as NOT-this-register: §17.1 community protections (people are never combat-routed), the F5 forced-then-freed victim mechanics ("freed not slain" is the victim's win-shape, not a fight assurance), and the CH_07 "never a slaying of anything sacred" scope clause (the asura IS slain in the festival's own demon-slaying spirit; the clause protects the temple and Murugan). Historical Decisions records that quoted the old register carry RETIRED markers rather than silent rewrites. The RCM Ch-68 block still carries the old framing — its scrub rides the Opus-handback endgame re-key. Gates 14/14.
[Translation-Doc critic pass — corpus-grounded fix-forward, 2026-07-15 (autonomous)] Three fresh-context Opus critics reviewed the five Translation Docs (UE5_Build/Terrain PASS/PASS-WITH-FIXES · AssetGen/Audio PASS-WITH-FIXES/PASS · Cinematic PASS-WITH-FIXES + seam audit COHERENT; ~100 citation spot-checks held, zero invented APIs, zero blockers). The pass surfaced that the Cinematic doc's worked cases were Contract-derived and contradicted the executed spine at CH_76/CH_77 — fixed forward against the real structures (BE_0076 Two Courts two-phase + FORK_CH76_A/B dual dispatch; the CH_77 path-INVARIANT ALL reveal + FORK_CH77_A gloss coda; no SCENE_CH77_ENDING_* triplet exists). SPINE-SIDE corrections in the same pass, all mechanical enum/key alignments (no prose, no reveal surface): (1) anchor_type stragglers normalized to the uniform trigger vocabulary — CH_15 ×2 + CH_57 "branch_decision"→"branch_decision_point", CH_17 "decision_point"→"branch_decision_point" (corpus census: scene_entry/beat_transition/dialogue_initiation/branch_decision_point + reveal ×4 at the arc-reveal moments CH_66/76/77/EPI). (2) CH_76 §10b FORK_CH76_A lock line disambiguated: "committed at Ch 65, WS_005" → names both keys (the bucket WS_004; the lock WS_005 path_lock_in_state) — registry-verified; the compound shorthand had just misled a fresh critic. (3) SPINE_SCHEMA_v3 §3d scene-row line corrected to the EXECUTED shape (7th column = hard_line_relevance, uniform 79/79; the intent trio thematic_anchor/audio_priority_layer/scene_audio_intent defers to Scene_Spec per each node's own §13 preamble — the schema sentence had swapped the fields) + the anchor_type enum and the post-lock LOCKED path_bucket row value documented as executed. Translation-doc fixes: the anchor_type→MapName mis-model corrected in Cinematic Step 3/Step 6 + UE5_Build Step 9 (maps resolve via beat→§3a site→region; anchor_type is trigger-class); WS_004/WS_005 named in Cinematic Step 5; PCG Biome Core reconciled to Experimental v0.2 in Terrain §8; Terrain §1 region-count rationale matched to §14.8 (69 cardinal; four elevations → 71 rows); Marble price re-attributed; AssetGen relabeled DRAFT v0.1 (the ACTIVE self-label predated this gate) + the four-part authority header + the Tripo shipped-rig license tail + the FBX→UE import seam ownership (unreal.AssetImportTask, brief-documented); Audio roster arithmetic + the Cinematic Step-4 population reference. DRAFT→ACTIVE flips ride the contracts-correction pass. [SRC: docs/spine/CH_76.md #9 #10b] [SRC: docs/spine/CH_77.md #10b #13] [SRC: T0_Worldstate_Variables @ WS_004 @ WS_005]
[WS_009 journal_status enum adjudication (Opus handback O-5), 2026-07-16] Surface: the spine's ratified
ws.journal_status usage was audited against the WS_009 registry domain under enum-domain discipline
(gotcha 20). Resolution: NO EXTENSION — no new enum value. All 66 ws.journal_status assignments across
docs/spine/CH_*.md resolve to a declared value, a free-text token, or prose; not one demands a value the
nine-value domain lacks, and the pressure runs the other way — after this order's two re-keys only three
declared values still have no writer at all (PUBLIC_TRULY_GOOD, SUPPRESSED, NEVER_COMPLETED, all downstream
of the Ch-57 ruling and the Ch-58 gap). The nine values cover the five WRITE-anchors of §8.4 (Ch 13, Ch 38,
Ch 56, Ch 57, Ch 58 — the same five the WS_009 note names) and the outcome registers of §8.2; §8.4's
remaining two bullets (Ch 59-65 continental revisits, Ch 77 Epilogue) are state-machine READ nodes,
matching WS_009's own Ch59_65_continental_revisit_dispatcher and Ch77_epilogue_renderer consumers — noting
that a read node still carries journal content, as CH_62:108 writes a Class-D +americas_case_filed token
inside that window. The full malformed class is 34 +token writes, machine-derived this run and enumerated
in the O-5 artifact; they are journal content and phase texture, not state: WS_009 is enum-typed and has no
accumulator, while WS_010 journal_entries_unlocked already owns per-entry accumulation and the spine writes
it correctly at CH_15, CH_47 and CH_70. Per the WS_025 precedent the texture rides WS_010 or a beat note,
never the enum. Applied here: the tokenized Ch-13 and Ch-38 anchors re-key in-domain (ACTIVE_HEALERS_CHILD;
TRANSFERRED_TO_PROTAGONIST, which had no writer in the corpus before this), and the premature Ch-48/49
DECISION_TO_PUBLISH seams re-key to TRANSFERRED_TO_PROTAGONIST, since §8.4 fixes Ch 56 as the commit-point
exactly as those seams' own texture already says. Reason: every re-key target is a value the domain already
declares at an anchor §8.4 already fixes, so this is join-and-type, not new canon; it follows the WS_017
re-key precedent at CH_76. The whole class is gate-invisible — check_spine_graph.py validates the ws NAME,
never the value against its domain [SRC: T0_Worldstate_Variables @ WS_009]
[SRC: T1_Integrity_Paths_Worldstates_Master # 8.4] [SRC: CH_76 # Decisions surfaced].
[WS_009 open gaps recorded, not resolved (O-5), 2026-07-16] Surface: three gaps that are not domain gaps.
Resolution: all left open. (a) The Ch-58 WRITE-anchor of §8.4 has no writer anywhere — CH_58 carries no
ws.journal_status write, beat-out or seam assert at all, only the prose that the record is public since
Ch 57, while the Epilogue reads SHARED_POST_CH58 as a live terminal value; the value is declared, so this is
not an extension question, and authoring the Ch-58 write is a new beat-out rather than a mechanical re-key.
(b) The Ch-57 register is a spine-internal contradiction and the re-key there is BLOCKED pending Josh:
CH_56's fork footnote and Decisions record both state that Ch 57 resolves a
PUBLIC_TRULY_GOOD / PUBLIC_HEDGED_GOOD_ENOUGH / SUPPRESSED branch on the accumulated integrity band, while
CH57_B08 is fork none and releases the record unconditionally, FORK_CH57_A guarantees the release lands on
every path with only its register varying and writes no journal_status at all, and CH_58 carries the record
public on every path; §8.1 and §8.2 side with CH_56. Writing either the three-value or the two-value set
would rule on that fork, so neither is written. (c) The 34 +token sites still need per-token routing off the
enum; two of them predate or fall outside the §8.4 state-machine anchors and are called out for that pass —
CH_03:161 +healers_child_unsigned_record_begun writes ten chapters before §8.4's Ch-13 journal-begins anchor
(an unsigned precursor record, Class-D texture, so the NOT_BEGUN Ch 1-12 window is not in fact untouched),
and CH_62:108 +americas_case_filed writes inside the Ch 59-65 state-machine read window; both route with the
follow-on rather than re-keying here, and whether a precursor record should predate the Ch-13 anchor is
itself a texture question for that pass. Reason: the cardinal rule — a value at Ch 57 is consumed as truth
by four runtime dispatchers, so a wrong value is worse than the inert type error left in place, which the
follow-on enum-domain gate will surface loudly [SRC: CH_56 # FORK_CH56_A] [SRC: CH_57 # FORK_CH57_A]
[SRC: T1_Integrity_Paths_Worldstates_Master # 8.2].
[Josh's rulings applied — O-5 Ch-57 register (R1), SIXOPT Option D (R3), D-8.0 zero-delta (R4), 2026-07-17]
Four rulings landed via AskUserQuestion on the accepted-recommendations default, with a mid-flight Josh
cardinal on Ntala folded in. R1, the Ch-57 journal register: the record's RELEASE is universal — written at
CH57_B08 before the CH57_B09 sovereign fork, it lands on every path that reaches Ch 57 — and only its
REGISTER path-varies at FORK_CH57_A, riding ws.reputation_biography_propagation, so Ch 57 does not resolve a
ws.journal_status band branch. CH_56's FORK_CH56_A footnote and its Decisions record were the stale side and
were superseded in place; the SUPPRESSED and NEVER_COMPLETED terminals are produced upstream per §8.4's
Evil-refuses-the-transition line, so the Epilogue's NEVER_COMPLETED read stays a live terminal on the Evil
path reached upstream and nothing is stranded. The CH_57 O-5 flag flipped from FLAGGED and BLOCKED to RULED.
The token re-key was left as a follow-on in honesty over completion: CH57_B08's ws.journal_status stays the
free-text token +record_released_public because the ruling requires a single register-neutral universal-
release value and the WS_009 enum domain carries none — its four release states (PUBLIC_TRULY_GOOD,
PUBLIC_HEDGED_GOOD_ENOUGH, SUPPRESSED, NEVER_COMPLETED) are all band-conditional, the CH_56 model R1
overrides — and adding a register-neutral value is an IPW §8.4-owned WS_009 domain extension reserved to the
§8.4 and WS_027 wiring commit. R3, the SIXOPT modeling question: Option D — the per-slot slot-to-durable-
outcome routing rides to the dialogue build and the spine does not model it at FORK_CH28_A or FORK_CH39_B;
CH_17 is the anomaly, not the pattern. Applied: CH_39 L297's kind self-contradiction fixed
(dialogue_six_option to exploration_interaction, matching L201); the CH_28 L176 and CH_39 L203 framing lines
re-worded per Option E, keeping the HL_0039/HL_0040 citation and the canonical-six roster while no longer
reading as a promise of an unwritten per-slot map. R4, D-8.0 option (i) CVD-literal zero-delta ratified:
six-option biography-slot choices move no integrity per CVD §10.1/§10.3; CH_17 §9.1's two CVD-illegal cells
were re-keyed — DEFIANT was generative and +Substantial, CURIOUS was generative and +Accumulative, both to
neutral and ~0, matching the already-zero SYMPATHETIC and DETACHED rows, with the TRULY_GOOD and TRULY_BAD
direction rows unchanged and the coverage still resolving — and the sibling IPW §6.4 L276 wording tightened
in place from "do not add substantial new integrity shift" to "do not shift integrity when chosen", the scan
baseline re-emitted in the same commit. A mid-flight Josh cardinal folded into the record corrections:
for_life inverts and never breaks — on the Evil path Ntala does not depart the story but becomes an
additional endgame opposition encounter, the arc's moral anchor standing against what the player has become,
so CH_65's Evil-path staging is the inversion beginning and the "only for_life is exempt" departure-rule
clause is now consistent; the encounter's seating, mechanics, and spare-kill semantics are follow-on design,
not staged here. Two published-record corrections rode the same pass: the refuted claim that the spine
travels with four characters (CHAR_0140/0144/0145/0146) carrying no loyalty_model was struck in
DECISIONS_PENDING_JOSH and RATE_MISMATCH_ANALYSIS (each of the four appears in exactly one node, single-region
heritage-keepers, a filter artifact), and the Ruling-3 departure defect re-worded to CH_65 staging the
departure only on the Evil path (path-differentiated, continuing on TG/GE). No registry CSV was touched in
this commit [SRC: CH_57 # Decisions surfaced] [SRC: CH_56 # FORK_CH56_A] [SRC: T0_Worldstate_Variables @ WS_009]
[SRC: T1_Integrity_Paths_Worldstates_Master # 8.4] [SRC: T1_CVD_Creative_Vision_Document # 10.3].
[Roster ratified — Option B applied (R2), 2026-07-17]
Josh ruled the companion roster Option B via AskUserQuestion. registries/T0_Character_Index now rows only the
two spine-proven long-haul travellers with real loyalty values: Ntala (CHAR_0002) as for_life /
truth_witness_mercy / departure never / join invest_Ch03_active_join_Ch13, and Ana (CHAR_0017) as come_and_go
/ caci_honor_community / departure circumstance_only (corrected from the major_opposition seed, since she
leaves by plot and route rather than by integrity opposition) / join invest_Ch03. Tunde's illustrative seed
loyalty row (CHAR_0127) was cleared to parity with his unrowed light-ally cohort — all six loyalty columns
emptied — because he carries zero CHAR_id actor-beats and was a seed read as a cast. The light-ally candidate
tier is named but not rowed (Tunde, Amboko CHAR_0126, Gert CHAR_0125, Binti Hassan CHAR_0056), and the two
not_companion markers CHAR_0003 and CHAR_0109 are unchanged. The ~30 roster-size target stays explicitly open
as Josh's question — it is an author's estimate single-sourced to WS7 L158, not measured and not canon, and
the familiar menagerie is a separate 22-slot axis that must not be folded into the human-companion count. The
Ntala for_life-versus-Evil-path-departure reconciliation is now ruled, not open: for_life inverts and never
breaks, so on the Evil path she becomes an endgame opposition encounter rather than departing, CH_65's
Evil-path staging is the inversion beginning, and the encounter design is follow-on. The fidelity baseline
was re-emitted to record the loyalty-cell divergence and the canon index rebuilt; gates 16/16 pass unpiped
[SRC: T0_Character_Index @ CHAR_0002] [SRC: T0_Character_Index @ CHAR_0017] [SRC: T0_Character_Index @ CHAR_0127].
[Prologue + CH_01 amendment — the amulet integration wave, 2026-07-27] Grid: Continuity / Reveal-discipline /
Cross-registry. Surface: Josh authored the Prologue/Ch-1 emotional spine in conversation across four sittings,
and the two origin nodes had to be amended in place to carry it. The authorizing blocks, in the order they
bind: the THIRD sitting authored the shape — the concealment ward was the MOTHER'S and passed to the newborn
at the birth, leaving her unprotected; a catastrophic rift-spawn event days-to-weeks later came toward the
modest castle while the King was OUT among the people; the playable arc runs adventure-and-service, then the
catastrophe, then a playable RUN BACK to the scene of the mother dying; the King never held resentment against
the child; the time jump into a childhood some of the realm's grieving people blame the child for, the best
friend's constancy, and the dumb fight the child ran from. The SIXTH sitting authored the Ch-1 ending
sequence — the chapter's quests and story and familiar bonding COMPLETE first, then one last morning: the
amulet taken off the neck in the sun, the familiar's playful keep-away, the chase into the woods, and the rift
that swallows child, familiar and amulet together (which settles that the object CROSSES, closing the old
CH_02 no-inventory question). The SEVENTH sitting ruled the physics and the payoff — VIBRATIONAL GRAVITY as
canon (high-vibrational beings attract rifts, the ward counters the attraction, the newborn a stronger magnet
than the mother, the Ch-1 fall lawful physics rather than accident or authored consequence) and THE GIFT AT
THE CH-13 DEPARTURE, the gift and the goodbye as one beat. The FIFTH sitting set the scope these nodes serve
(the Prologue→Ch 13 slice, Prologue and Ch 1 built last). Resolution: the integration landed as a six-cluster
wave against the re-pointed plan at docs/proposals/AMULET_PROVENANCE_BRIEF.md, touching eighteen files.
CH_PROLOGUE grows from a ceiling tutorial into a fuller playable arc with a cost at its end (title re-scoped to
carry the realm served and the first taking; the existing sealing set-piece SEQUENCES BEFORE the catastrophe
and becomes the chapter's PROOF rather than its climax, so the ceiling is never beaten and never lost and
BE_PROLOGUE's death-none no-fail-wall clause survives in substance; the realm-service arc, the catastrophe,
the unfailable run-back and the arrival are new; the close is re-scoped, not deleted). CH_01 gains the time
jump, the grain the grieving realm lays on the child, the friend's constancy, the argument staged on a prior
day, and the last morning — the fall relocating from the veil_seam to the realm_woods at the end of the
keep-away chase. CH_02's start state gains the one clause reconciling a worn, uninscribed, unidentified and
unrechargeable realm object with a no-inventory seam. CH_13's exit beat becomes the gift and the goodbye in a
single beat with a new scene anchor and the ward's ally-side terms. Both transitions files were re-authored for
a Prologue that now ends in loss and a Ch-1 fall that now happens somewhere else. Four living-source tier docs
carry the canon home: T1_Vril §1 takes vibrational gravity as an EXTENSION of the existing rift-formation
paragraph with the spontaneity clause and the no-author reading restated inside the amendment so no later
reading drifts them, magnitudes held ordinal, the ward held out of the selectable bonus pools per the balance
doctrine, and the whole law scoped authorial-L3 and shown in staging rather than narrated; T3_Core gains the
mother at §2.1, the never-resentment at §6, an attribution LOCK keeping the grief geography single-sourced to
the child's loss, and the Ch-76 restraint that the mother goes unspoken at the father encounter;
T3_Familiars_Named §5 takes the keep-away sequence and names the familiar as the canonical mechanism by which
a realm object reaches the human world (and corrects in place a stale line that had placed the fall in the
Prologue rather than at the Ch-1 climax); T1_Threads_22 gains the first taking as Thread 6's origin anchor and
the amulet as Thread 20's third sacred-object chain beside the Sealed Letter and the Tomb Artifact. Reason:
this is Josh-authored chapter canon for two nodes that were already built, so the work is amendment rather
than authoring, and the ruling's own integration order required the reconciliation pass before anything
entered the spine [SRC: docs/spine/DECISIONS_PENDING_JOSH.md # RULED 2026-07-27 (third sitting)]
[SRC: docs/spine/DECISIONS_PENDING_JOSH.md # RULED 2026-07-27 (sixth sitting)]
[SRC: docs/spine/DECISIONS_PENDING_JOSH.md # RULED 2026-07-27 (seventh sitting)]
[SRC: docs/proposals/AMULET_PROVENANCE_BRIEF.md # 10].
BEAT-ID STABILITY, measured rather than asserted, because a renumber at an origin node would break every
downstream join. The Prologue is clean: CHPRO_B01 through CHPRO_B09 keep both their ids and their seq 1-9 and
their meaning; the six new beats append as CHPRO_B11 through CHPRO_B16 at seq 10-15; and CHPRO_B10 keeps its
id and its EXIT role, moving only to seq 16 so the chapter still closes where it always closed. Every
pre-existing Prologue id therefore still means what it meant, which is what the twelve CHPRO_B01-B10 cells in
T0_Quest_Definition_Registry and the CHPRO_B01/B07/B08/B09 references in T0_Scene_Spec_Registry depend on.
CH_01 is the case that needs stating honestly: ids CH01_B01 through CH01_B10 all survive and CH01_B11 through
CH01_B14 append, so nothing dangles — but the tail was RE-PURPOSED rather than merely extended, and the fall
moved from CH01_B08 to CH01_B12, the landing from CH01_B09 to CH01_B13, and the taking from CH01_B10 to
CH01_B14, with CH01_B01-B06 semantically stable. That is safe in the registries because no registry references
a CH01_B id at all (measured: zero such cells in both T0_Scene_Spec_Registry and T0_Quest_Definition_Registry),
and the entry's own §13 scene table and side-questline beat lists were re-bound to the new ids inside the same
pass. Two published prose artifacts still describe the OLD CH_01 semantics and are named here so a later reader
is not misled: docs/proposals/AMULET_PROVENANCE_BRIEF.md §6 (which predicted CH01_B07 and CH01_B08 would keep
their content, a prediction the landed sequence overtook) and
docs/pipeline_review/STORYDEPTH_WHOLE_ARC_INSTRUMENT_2026-07-27.md at its CH01_B09 reference. Two machine
checks back the guarantee: a corpus-wide sweep of every tracked .md, .csv and .json file, taken on the landed
wave, found twenty-three carrying CHPRO_B or CH01_B references and ZERO dangling ids — thirty distinct ids are
referenced corpus-wide and every one of the thirty is defined in the two entries, against a positive control of
four hundred and fifty-seven reference occurrences across those files, so the sweep could match; the same sweep
taken at HEAD returns eighteen carriers, and the five the wave adds are this log, T0_Ally_Behavior_Policy,
T0_Equipment_Registry, T0_Thread_Grid and T0_Chapter_Index, which reconciles the two counts exactly. A scan for
the parser-invisible letter-suffixed form returned zero in both entries against a positive control of forty-nine
and sixty-one numeric matches in the same files, so the search could match and the zero is real. The
build/spine_rows CSVs regenerate from the entries and are the director's, not
a hand-edit surface [SRC: docs/SPINE_SCHEMA_v3.md] [SRC: T0_Quest_Definition_Registry] [SRC: T0_Scene_Spec_Registry].
REGISTRY CELLS TOUCHED, enumerated so the same-commit baseline refresh can be checked against them. Seven CSVs
moved. T0_Character_Index gains ONE new row, CHAR_0164, the mother — named by relation only with the name cell
marked provisional in its own extensions text, chapter_first_appearance and chapters_present Prologue,
thread_involvement 6;20, attackability_tier protected-collective, is_load_bearing true — and amends CHAR_0005's
voice_signature_notes and extensions to carry the never-resentment characterization. T0_Equipment_Registry
takes its FIRST row ever, EQ_0001, the ward: string_status placeholder with no proper name minted, item_class
wearable, region_native fairy_realm, canonical_chapter_acquisition CH_PROLOGUE, and the provenance chain in its
notes. T0_Ally_Behavior_Policy gains six rows, AP_0009 through AP_0014, all on CHAR_0002, encoding the ward as
a rule the encounter layer honours rather than a pool it resolves. T0_Boss_Encounter_Registry amends
BE_PROLOGUE's boss_name and phase_breakdown_object, and BE_01's boss_name, phase_breakdown_object,
engagement_modes_object, win_reward and target_type, all in place, and mints NO new row, because whether the
catastrophe is fought is unruled and minting a boss would have decided it. T0_Thread_Grid goes 664 to 666 rows:
THREAD_06 × CH_PROLOGUE and THREAD_06 × CH_01 amended at content_summary, THREAD_20 × CH_PROLOGUE and
THREAD_20 × CH_01 added. T0_Scene_Spec_Registry amends SCENE_PROLOGUE_OPENING's participant_entity_refs and
scene_beat_structure. T0_Chapter_Index moves CH_PROLOGUE's combat_framing and seed_npc_ids and
body_prose_word_count (691 to 1378) and CH_01's combat_framing and body_prose_word_count (668 to 1565), and
DELIBERATELY leaves the Prologue intensity and mode_variety_check cells unflipped (see the open-items entry
below). Reveal discipline was re-verified after the fact rather than assumed: a scan of the player-facing Body
prose block of both entries found ZERO occurrences of Velheim, Grand Sage, Maatherion, Architect or thesis,
against a positive control of forty-one and thirty-three word-bounded occurrences of those same five tokens
elsewhere in the same two files, of which nineteen and twelve are Grand Sage alone — every one of them a
design-layer statement DOCUMENTING what is held from the player, which is the already-adjudicated CH_17
lint-WARN class and not a leak. Gender discipline holds: every gendered pronoun added by the wave attaches to
the mother or to the King, and no line fixes the protagonist's or the healer's child's gender. Any registry
edit requires the director's --emit-baseline refresh on harness/registry_fidelity.py in the SAME COMMIT or
the gates go red; that command, run_gates.py unpiped, extract_spine_rows.py and the canon index rebuild are the
director's alone and were not run by this wave [SRC: T0_Character_Index @ CHAR_0164]
[SRC: T0_Character_Index @ CHAR_0005] [SRC: T0_Equipment_Registry @ EQ_0001]
[SRC: T0_Boss_Encounter_Registry @ BE_PROLOGUE] [SRC: docs/fidelity_baseline.json].
[Prologue + CH_01 amendment — the sub-points the rulings did NOT settle, carried PROPOSAL-TIER, 2026-07-27]
Grid: Open-decision carry. Surface: the sittings ruled the shape, the ending sequence, the physics and the gift
staging, and they left a bounded set of staging and naming sub-points open. Every one below is drafted or
recorded PROPOSAL-TIER and marked inline at its site, never applied as ruled, per the cardinal do-not-invent
rule. The CH-2 AMULET-RECOVERY STAGING: the sixth sitting names its own remaining sub-point — where the object
is once the child is on this side. Three stagings are presented in the CH_02 Decisions block and none is
chosen: on the cave floor beside the child at waking; a find-beat at or near the place the familiar is believed
to have died; or a later find-beat across Ch 3-12. One DERIVED hard constraint is stated as derivation and not
as invention — the gift is ruled at the Ch-13 departure, so recovery must complete at or before Ch 13, which
excludes by construction any staging that waits for the Ch-58 familiar reunion. THE PROLOGUE CATASTROPHE'S
STAGING: a fought realm-side spawn, or an arrive-too-late catastrophe whose spawn is gone by the time the King
reaches the castle. This is the sub-point that decides whether a second Boss_Encounter row exists at all, and
because it is unruled NO second row was minted; either way the spawn carries no author, no intent, no target
and no recurrence framing, since the moment it reads as aimed at the royal house the arc leaks an antagonist
pattern roughly thirty-eight chapters early. THE PROLOGUE INTENSITY CELL stays standard. The recommendation
to move it to peak is recorded with its derivation shown — the ruled shape adds the chapter's true climax by
intensity, and HL_0048's no-three-consecutive clause permits it because this node's only neighbour, CH_01, is
valley — but it is a registry canon value that moves the arc's topography string, so the flip belongs to the
director inside the gate ritual and never to a silent scatter; the craft caution that the Prologue must not
become a tragedy chapter cuts the other way and is recorded beside it. THE PROLOGUE MODE-VARIETY CELL likewise
does not move: its five letters stand, though the combat letter's BASIS changes, because the realm-service arc
now earns at beat scale what the pre-v3 encounter-present convention had carried; the puzzle letter remains the
live vocabulary seam the entry's Decisions block already records and is settled against the final beat graph,
not here. ALL NAMING stays Josh's: the mother is written by relation and never by name under the HL_0099
parallel that withholds the King's, the ward's equip_name_text lands string_status placeholder with no minted
proper name and no minted in-world term, and the Prologue's new settlement site takes a descriptive handle.
THE OPTIONAL MAKER ENRICHMENT — the mother as the ward's maker — remains explicitly NON-RULED and DECLINED by
default; it is assumed nowhere in the landed wave. Two SUPERSESSIONS of the integration brief are recorded so
no later author re-imports them: §7's gift-staging option set and its recommendation are RETIRED by the
seventh sitting's ruled Ch-13 departure, and §9's "the two ruptures must stay distinct in kind" is SUPERSEDED
IN PART, because Josh's own words make both ruptures instances of one law; the surviving core of that bullet is
that neither rupture has an AUTHOR, and the rhyme between them is now lawful and intended. Reason: staging,
registry canon values and naming are the classes the do-not-invent rule reserves, so the wave presents them
with derivations shown rather than deciding them, and the two supersessions are recorded because a retired
recommendation left unmarked is exactly how a superseded option walks back into canon
[SRC: docs/spine/DECISIONS_PENDING_JOSH.md # RULED 2026-07-27 (sixth sitting)]
[SRC: docs/spine/DECISIONS_PENDING_JOSH.md # RULED 2026-07-27 (seventh sitting)]
[SRC: docs/proposals/AMULET_PROVENANCE_BRIEF.md # 11] [SRC: T0_Hard_Lines @ HL_0048]
[SRC: T0_Hard_Lines @ HL_0099]. PENDING AUTHOR DECISION on the recovery staging, the catastrophe staging, the
intensity flip, and all naming.