CANDIDATE_RESOLUTIONS.md

decisions/spine/CANDIDATE_RESOLUTIONS.md

Candidate Resolutions — the whole-arc flagged items (deep-dive + adversarial)

Every non-blocking item flagged in docs/spine/WHOLE_ARC_REVIEW.md ("Flagged items"), each run through a fresh-context deep-dive of the real canon, an adversarial stress of the best option, and a paste-ready recommendation. Method: a two-stage-per-item Workflow (deep-dive -> adversarial finalize) plus a CVD ground-truth agent, 23 subagents, ~2.17M tokens, 0 errors. This doc is the decision-of-record; the two documentation-only conventions (integrity-band vocabulary, reunion vocabulary) live here as their authoritative home.

The cardinal rule bound every agent: a labeling / register CLARIFICATION that reorganizes existing canon is in-scope, but a change to any chapter / Component / numerical / naming / hard-line ASSIGNMENT is Josh's. Reveal discipline and the locked cosmic-thesis phrasing were held throughout.

Disposition at a glance

Why several are held rather than auto-applied: the Ch-66 recast edits a hard-line origin-recognition BODY-PROSE beat, and the two enrichments ADD body prose — all three change the source, which means the Fable review reel must be rebuilt and a reveal re-verify run before the next review. The whole-arc review already declared the arc delivery-ready for the Fable pass, so the clean sequencing is: run Fable on the current arc, then fold these (plus whatever Fable surfaces) into one revision pass. Each is paste-ready below the moment you want it.

Standing Josh-owned items (unchanged — NOT resolved here; cardinal)

These are carried in docs/spine/DECISIONS_PENDING_JOSH.md; the deep-dive method does not touch them.

---

1. Thread 1 (Vril Parallels) dual RESOLUTION_FINAL — Ch 70 culmination vs Ch 76-77 framework resolution

Options considered:

Recommendation: B — Keep the RESOLUTION_FINAL cells; scope the Ch-70 cell as the experiential/testimonial-register resolution and make the two-register (experiential Ch 70 / framework-cosmological Ch 76-77) distinction explicit in the grid cell and both spine nodes. No assignment changes, no new stage token, no Josh ruling required.

Reasoning:

The finding's own premise is slightly off, and correcting it dissolves most of the apparent conflict. There is no contradiction INSIDE T1_Threads: §8 (line 1360) calls Ch 70 a 'FRAMEWORK-LEVEL CULMINATION anchor' and §6 (line 1184-1188) reserves 'resolution' for the Ch 76-77 waterfall. The token 'RESOLUTION_FINAL' appears nowhere in T1_Threads — it is a Thread_Grid (DRAFT v1.1) stage-label, one of seven schema tokens (none of which is 'CULMINATION'). The grid author mapped §8's 'culmination' to the closest available token, RESOLUTION_FINAL, producing three FINAL cells for Thread 1 (Ch 70/76/77) where the Ch-70 one is really a culmination of a distinct sub-question. That is a label-overload in an operational draft registry, not a canon conflict and not a Josh-authored assignment (the cell's flags column is empty; the batch-1 #2 confirmation Josh gave was about the Ch-70 payoff's EXISTENCE and the RCM source reconciliation, not the grid token). B represents the true state — Thread 1 uniquely resolves twice in two registers: the experiential/testimonial payoff at Ch 70 (the cross-cultural vril traditions were accurate memory, felt by direct contrast when the full ceiling reopens) and the cosmological unification at Ch 76-77 (every name refers to one phenomenon). These are genuinely different propositions; Ch 76-77 never re-opens the Ch-70 answer. The decisive tie-breaker over C is precedent: the repo already faced this exact shape — Thread-3 carries RESOLUTION_FINAL at the intermediate Ch 35, scoped by a form note, distinct from its Ch 69/74 endgame resolution — and CH_35 line 194 ruled it 'registry-label hygiene / RESOLVED-WITHIN-VISION', explicitly a non-Josh clarification. Applying C (demote-to-partial) would contradict that ruling; applying B is consistent with it. A is the only option that actually needs Josh (it invents a stage token and fights §6); B deliberately does not do that.

Adversarial findings:

Stress-tested B on four axes. (1) Canon invention: B changes no chapter/Component/numerical/naming/hard-line assignment, keeps the grid token, and only names a distinction the doc ALREADY draws (§8 'culmination' vs §6 'resolution') — no invention. PASS. (2) Reveal leak (the sharpest check, since Ch 70 is pre-reveal and Ch 76-77 carries the locked cosmic thesis): the proposed notes stay strictly framework-bounded and never state revelation content. 'Framework/cosmological register' and 'the resolution deferred to the endgame' are vocabulary §6 itself uses publicly (Thread 5, line 1196 're-contextualizes at the cosmological level') and that CH_70 line 38 ALREADY carries ('the cosmological-register resolution still deferred to the endgame') — vocabulary that already passed the per-node reveal re-verify, RR-72, and the whole-arc review. I deliberately keep the Ch-70 (pre-reveal) note away from any unification phrasing ('one substrate'/'every name for the one') and confine unification language to the Ch-77 note (post-reveal, arc terminus — no forward leak possible). No NEW leak vector is introduced. PASS, but because it touches endgame-register language at a pre-reveal node, the apply stage should still run a reveal re-verify on the Ch-70 note before commit. (3) §17.1 care: no cultural representation touched. N/A. (4) The residual token-vs-§6 mismatch (the honest weak point): B leaves 'RESOLUTION_FINAL' literally on the Ch-70 cell while §6 says resolution is at 76-77. This is real but is exactly the Ch-35 Thread-3 situation already ruled acceptable label hygiene, and the scope note + the accepted multi-FINAL convention + the grid's DRAFT status contain it; C would 'fix' the token at the cost of mislabeling a culmination as partial and breaking consistency with the Ch-35 ruling. One process caveat carried into the exact change: editing the grid CSV requires refreshing docs/fidelity_baseline.json via registry_fidelity.py --emit-baseline in the same commit, or the fidelity gate goes red.

Exact change (paste-ready):

Three core edits (paste-ready), plus one optional conservative source-doc parenthetical. All keep every assignment and the RESOLUTION_FINAL token unchanged.

EDIT 1 — Grid cell, registries/T0_Thread_Grid [DRAFT v1.1]/T0_Thread_Grid DRAFT v1.1.csv, row 67 (THREAD_01,CH_70). Stage token stays RESOLUTION_FINAL; append a scope clause to the cell's content text. Replace the cell content:

"- Ch 70 framework-level culmination — fairy-realm return as canonical direct-experience confirmation that the fifteen human-world cultural-tradition parallels preserved accurate testimonial memory of pre-decline atmospheric reality, not metaphor."

with:

"- Ch 70 framework-level culmination — fairy-realm return as canonical direct-experience confirmation that the fifteen human-world cultural-tradition parallels preserved accurate testimonial memory of pre-decline atmospheric reality, not metaphor. Experiential/testimonial-register resolution (the Beautiful-Lie sub-question answered by direct experience); scoped per the Ch-35 Thread-3 registry-label-hygiene precedent, distinct from and complementary to the Thread-1 framework/cosmological resolution at Ch 76-77 (§6). Not the whole-thread close."

Then in the SAME commit run: python harness/registry_fidelity.py --emit-baseline (refresh docs/fidelity_baseline.json), and verify harness/run_gates.py exits 0 UNPIPED.

EDIT 2 — docs/spine/CH_70.md, line 39 (the stale 'permitted and flagged for RR-72' note). Replace:

"- Major-thread coverage note — Ch 70 advances Major Thread 1 (its RESOLUTION_FINAL), 3, and 5 (grid-rowed) and carries Weaving 9 forward; Thread 2 and Thread 6 carry no Ch-70 direct anchor (per T1_Threads §8, which anchors Thread 1 at Ch 70 and states no other direct anchors; RCM governs the Ch-70 source reconciliation per batch-1 #2), permitted and flagged for RR-72 [SRC: T1_Threads_22_Master_References # Thread 1]."

with:

"- Major-thread coverage note — Ch 70 advances Major Thread 1 (its framework-level CULMINATION per T1_Threads §8, grid-tokened RESOLUTION_FINAL in the experiential/testimonial register), 3, and 5 (grid-rowed) and carries Weaving 9 forward; Thread 2 and Thread 6 carry no Ch-70 direct anchor (per §8, which anchors Thread 1's culmination at Ch 70 and states no other direct anchors; RCM governs the Ch-70 source reconciliation per batch-1 #2). Register note — Ch 70 is Thread 1's experiential-register resolution (the vril-tradition testimony confirmed by direct experience); the framework/cosmological-register resolution stays deferred to the Ch 76-77 waterfall (§6), the two complementary and neither redundant [SRC: T1_Threads_22_Master_References # Thread 1]."

EDIT 3 — docs/spine/CH_77.md, line 43. Replace:

"- Thread 1 (Vril Parallels), RESOLUTION_FINAL (consummated, build-derived) — the vril-parallel terms resolve: every name for the one substrate unified at the recharge-source the game opened and closed with, the ring shut [SRC: T1_Threads_22_Master_References # Thread 1]."

with:

"- Thread 1 (Vril Parallels), RESOLUTION_FINAL (consummated, build-derived) — the framework/cosmological register: every name for the one substrate unified at the recharge-source the game opened and closed with, the ring shut; the experiential-register culmination (the traditions confirmed as accurate memory) landed earlier at Ch 70, this the cosmological unification that completes it [SRC: T1_Threads_22_Master_References # Thread 1]."

OPTIONAL EDIT 4 (conservative, living-source, gate-safe; restates the existing §8/§6 relationship only) — _source/01_Tier_1_Foundation/T1_Threads_22_Master_References [ACTIVE v2.2].md, §8 line 1360. After 'Thread 1 Vril Parallels FRAMEWORK-LEVEL CULMINATION anchor' add the parenthetical: '(the experiential/testimonial-register Thread-1 resolution; the framework/cosmological-register resolution lands at Ch 76-77 per §6)'. This changes no assignment and only makes the already-encoded §8-vs-§6 distinction self-explicit; omit it if a minimal footprint is preferred.

Reveal re-verify required on EDIT 2 (a pre-reveal node) before commit — confirm no thesis/unification content leaks; the wording above stays within the §6/Thread-5 framework-bounded register already present at Ch 70.

---

2. Ch 66 recognition beat: recast "she is of this place / the source is here" so Atlantis reads her as KIN of the shared origin-lineage, not as her literal birthplace

Options considered:

Recommendation: Option A — the minimal surgical recast. It fixes the contradiction with the smallest footprint, stays strictly inside canon already present in the chapter (resonance-source + origin-script + 'kin of the origin' anchors), preserves the emotional force of the origin-recognition beat, honors the D-06 fairy-realm birthplace (making line 28 consistent with the already-correct line 32), and avoids both the anti-fringe root-race firewall and the mild thesis-adjacency that Option B's 'the source they both rose from' would introduce.

Reasoning:

The defect is real and dual: line 28 has an INTERNAL contradiction with line 32 of the same chapter. Line 32 correctly says 'the realm she was born to' is three thresholds BEYOND Atlantis (the fairy realm — Prologue T3_Core §2.1: born in the fairy realm, child of the Elven King; D-06). But line 28's 'the source is here … she is of this place, and the realm knows her the way a house knows a child of the house returned after a lifetime away' reads literally as Atlantis being her birthplace/home. Atlantis is the FIRST threshold realm / 'pre-deluvian origin civilization' (line 7), not where she began. The fix is a labeling/register clarification, not a canon change, because the connective tissue is already canon: the resonance she has followed is 'gathered here at its source' (L26), Atlantis is 'the origin of the inscription lineage every drowned site fragmented' (L39), the Warden recognizes her as 'KIN of that origin' (L66/L74), and her Sealed Letter — which names her elven/fairy origin — is written in the Atlantean origin-script (L120). So the kinship Atlantis extends is lineage/substrate kinship (she carries and half-knows the origin-resonance and origin-script Atlantis is the source of), NOT native birth. Recasting to that frame moves no canonical assignment: Atlantis stays Ch 66; her birthplace stays the fairy realm. The finding's own QUESTION sanctions exactly this frame ('recognizing her as KIN of the shared precursor/origin-lineage, not her literal birthplace'), so this implements a sanctioned clarification rather than inventing cosmology. Option A is preferred over B because it grounds the kinship in the script/resonance the chapter already establishes and refuses to assert a shared cosmogonic parent-source (which would be uncanonized AND thesis-adjacent).

Adversarial findings:

Stress-testing the recommended wording surfaced and headed off six failure modes: (1) SHARED-COSMOGONY OVERREACH — Option B's 'the source they both rose from' would assert the fairy realm and Atlantis both sprang from one prior source; that is uncanonized genealogy AND edges into the HELD 'presence built downstream of a source' material (line 30's felt seed, which §17.9 keeps FELT not declared). Rejected; Option A frames kinship as the origin-resonance/lineage she CARRIES and Atlantis SOURCES, never a shared parent. (2) SPECIES-GENESIS INVENTION — any phrasing like 'source of her kind' would imply Atlantis birthed the elven species (canon invention; her origin is the fairy realm). Avoided; the wording ties kinship to the inscription/resonance lineage, not her species. (3) ANTI-FRINGE FIREWALL — the Atlantis firewall's core reason is documented hyperdiffusionist racism (§19.1 / lines 100-102); the recast uses only substrate/source/lineage/'first language' register, never 'blood/bloodline/root-race,' clearing the firewall. (4) REVEAL LEAK — 'a source older than the daylight world' / 'older than the daylight world ever let her know' is the licensed elven-origin register (her fairy origin is older than / outside the human world); it adds nothing of the Grand Sage, the ultimate thesis, or Cassius, and the retained clause 'whose she is and where she began' points to the elsewhere (fairy-realm) origin without naming the King (HL_0099 intact). Line 30's stronger felt seed already exists and is untouched. (5) INTERNAL CONSISTENCY — the new sentence B explicitly says 'though she was not born here,' directly reconciling line 28 with the correct line 32; line 30's bare 'recognized as kin' needs no change. (6) The one residual assumption — that the fairy-realm/elven origin is OF the same vril-inscription origin-lineage Atlantis sources (rather than a fully separate origin) — is exactly the frame the finding's QUESTION sanctions and is evidenced by the Sealed Letter being written in the Atlantean origin-script; if Josh intends a stricter reading (kinship ONLY via the letter's shared language, no lineage claim), the wording can dial back to pure script-kinship without restructuring. REQUIRED: because this sits on the Ch-66 origin-recognition reveal surface (D-06 / HL_0043 / §17.9), any applied edit must be followed by a whole-window reveal-discipline re-verify confirming (a) the licensed elven-origin reveal still lands, (b) the fairy-realm birthplace reads as elsewhere and consistent with line 32, (c) the 'downstream-of-source' seed stays felt-not-declared, (d) no Grand-Sage/thesis/Cassius leak was introduced.

Exact change (paste-ready):

Three edits in C:\dev\humanity-forgotten\docs\spine\CH_66.md. Edits 1 and 2 are two sentences inside the single body paragraph at line 28 (the surrounding sentences of that paragraph are UNCHANGED); edit 3 is the line-94 anchor.

EDIT 1 — line 28, sentence A.

OLD: "She is not what she was told she was, nor what the ones who hunted her decided she was; she is something with a source, and the source is here, and it has been waiting."

NEW: "She is not what she was told she was, nor what the ones who hunted her decided she was; she is something with a source, and the resonance she has carried since the beginning has its source here, and this place has been waiting for one who carries it to come so far."

EDIT 2 — line 28, sentence B (the last sentence of the paragraph).

OLD: "She is older than the daylight world ever let her know, and she is of this place, and the realm knows her the way a house knows a child of the house returned after a lifetime away."

NEW: "She is older than the daylight world ever let her know, and though she was not born here, she is kin to this place — of the origin it holds, the lineage it is the source of — and the realm knows her the way an ancient house knows one of its own line come home from very far away: not a child returning to the room she was born in, but kin arrived at the source of what she has carried all along."

EDIT 3 — line 94 anchor.

OLD: "- Recognized as kin, not hunted — after a whole road of being recognized as a threat, being seen, for one threshold, as kin of the house returned [SRC: T1_Research_Corpus_Master # Ch 66]."

NEW: "- Recognized as kin, not hunted — after a whole road of being recognized as a threat, being seen, for one threshold, as kin of the origin, not as a threat [SRC: T1_Research_Corpus_Master # Ch 66]."

No other spot in CH_66 requires change: line 32 ('the realm she was born to') is already correct and must be kept; line 30 ('recognized as kin'), line 66 and line 74 ('kin of that origin' / 'kin of the origin') are already safe/correct.

---

3. Add designer-only best-friend→healer's-child gender-resonance note to Ch 13 Continuity anchor

Options considered:

Recommendation: A — append a single tightened designer-only sentence to the end of the Ch 13 Continuity anchor paragraph.

Reasoning:

The task explicitly scopes the fix to Ch 13's Continuity anchor, and that is also the adversarially-best location: it is the one block that already narrates the healer's-child join, so the gender-provenance fact sits with the event it qualifies, and it mirrors how CH_01 records the same fact in its own continuity/selection layer. Options B-D scatter the fact away from the join event or into a section with the wrong semantics; E leaves the flagged gap. The change is a pure designer-note addition that restates existing canon (T3_Core §3.2 verbatim in substance), touches no player-facing prose (Body prose lines 24-35 untouched), changes no canonical assignment, and carries zero reveal or §17.1 exposure. I tightened the first-pass draft: it was verbose and said the resonance is 'meant to feel only in hindsight,' which imports an intended-recognition register the silent gender echo does not have — canon says only 'Designed narrative resonance' (§3.2) / 'invisible on first play' (CH_01). The finalized note uses the canonical phrasing and explicitly flags zero forward reveal-valence.

Adversarial findings:

No reveal leak: the note contains no thesis, Grand Sage, House-of-Velheim, or Elven-King-name content; the best-friend↔healer's-child 'echo' is already canonical designer framing (CH_01 lines 89/102; T3_Core §2.2), so restating it in a Ch-13 designer-only note is symmetric and safe. No invented canon: the note restates T3_Core §3.2 (line 173) and §2.2 (line 69) in substance and alters no chapter/naming/numerical/hard-line assignment. No §17.1 exposure: the note concerns a gender-resonance mechanic, not cultural representation. One defect corrected in the first-pass draft: it was over-long and asserted the resonance is 'meant to feel only in hindsight,' overstating a silent structural fact as a staged hindsight beat — replaced with canon phrasing ('invisible on first play' / 'designed resonance'). Mis-classification-as-player-prose risk is neutralized by the leading 'Designer-only' marker, matching the doc's existing 'internal, designer-only' asides (lines 13, 180). Placement verified against the doc: line 21 ends the Continuity anchor paragraph with '...not a first-time arrival [SRC: T3_Core_Characters # The Healer's Child] [SRC: T0_Hard_Lines @ HL_0070].' — the append target.

Exact change (paste-ready):

In C:\dev\humanity-forgotten\docs\spine\CH_13.md, append the following sentence to the END of the Continuity anchor paragraph (immediately after the existing line 21 text '...not a first-time arrival [SRC: T3_Core_Characters # The Healer's Child] [SRC: T0_Hard_Lines @ HL_0070].'), as a new trailing sentence in the same paragraph:

Designer-only, never surfaced to the player and invisible on first play: the healer's child's gender is not independently set at Ch 13 — it inherits from the player's Ch-1 best-friend selection, carrying the same gender as the fairy-realm best friend the protagonist chose, so the ancient-world companion who joins here echoes the fairy-realm companion left behind at the fall (pinned at the Ch-1 end-state biography_set; a designed narrative resonance carrying zero forward reveal-valence) [SRC: T3_Core_Characters # 3.2] [SRC: T3_Core_Characters # 2.2].

---

4. Ch 70 two-clock (fairy-time) designer note — pinning the D-06 boundary the Prologue defers

Options considered:

Recommendation: Option A (single corrected designer-note at Ch 70's Continuity anchor, after line 17). Reject the provisional draft's specific mechanism as an invention that contradicts applied D-06; keep its placement and its Josh-reservation.

Reasoning:

The finding is real: the Prologue explicitly defers the fairy-time distortion to Ch 70 (CH_PROLOGUE lines 106, 159 — "planted only as ambient timelessness, a Ch-70 payoff"), Ch 70 pays it off NARRATIVELY (the changed-realm-on-return, the Oisín motif at line 43), but the two-clock designer relationship (D-06) is never pinned at the boundary. Ch 70/71 line 17 state only "eighteen, the young-adult plateau holding." Meanwhile Ch 1 (line 162) DOES state the symmetric outbound event at designer level ("the fairy-time polarity flip, the single irreversible instant"). So the note restores an absent symmetry and closes a genuine misread-risk (a builder could read the King's aging + the Oisín "three years that were three hundred" as a literal chronological dilation that contradicts elven agelessness and the plateau). Placement at the Continuity anchor is correct because the crossing is a start-state event. The note is pure designer-only, touches nothing player-facing, and reserves the sole genuine fork (elapsed-realm-time magnitude) to Josh — the line between a permitted clarification and a prohibited assignment.

Adversarial findings:

Stress-testing the provisional draft surfaced a substantive canon error that I corrected. (1) INVENTED MECHANISM contradicting applied D-06: the draft says re-entry "REVERSES the Ch-1 polarity flip — the internal clock STOPS at the return" and the plateau "is now NATIVE ... no longer the vril-starved temporary cap it read as." This is wrong. Per D-06 (RESOLVED-APPLIED), the internal integer reaches ~18 and PLATEAUS at the Adolescence→Adulthood transition (~Ch 38/39, at vril stabilization / end of the involuntary time-fluctuation), and that plateau operates for the entire modern arc (~Ch 38-69) while she is still in the DEPLETED HUMAN WORLD — it is emphatically NOT caused by, and does not begin at, the Ch-70 realm re-entry. Saying the clock stops / the plateau becomes native at Ch 70 injects a new transition D-06 does not have and mischaracterizes the Ch 38-69 plateau. CORRECTION: the crossing is AGE-NEUTRAL — neither clock changes on return; the plateau simply continues. (2) CONFLATION RISK the draft actually enables rather than closes: Ch 70 loudly restores the full vril-POWER ceiling (stated ~6 times), so a builder could infer "vril ceiling back → elven long-life kicks in → plateau starts now." The corrected note's core payload explicitly SEPARATES the vril-POWER ceiling (an ability state, restored at Ch 70) from the age plateau (native since ~Ch 38) so they are not collapsed. (3) NUMBER-HEDGING: D-06's internal ages/transition chapters are "EVERY NUMBER A PROPOSAL, Josh's cardinal call" and still listed under OPEN CALLS RESERVED TO JOSH; the corrected note frames "~Ch 38/39" and "~18" as the applied-curve values, designer-adjustable, not fixed canon — avoiding inventing a hard number. (4) REVEAL/§17.1: clean — the note is designer-only, the internal integer is explicitly never surfaced, and it touches nothing of the thesis / Grand Sage / patriarch / Elven-King name; the Oisín echo is already an existing L2 civilizational mark. (5) The elapsed-realm-time magnitude (any literal Oisín ratio) IS a genuine Josh fork; the note forecloses only the MISREADING that a ratio was applied and reserves the magnitude to Josh — it does not set it.

Exact change (paste-ready):

Add ONE designer-only bullet to docs/spine/CH_70.md in the "Continuity anchor" block, immediately AFTER line 17 (the line ending "...age_stage Adulthood [SRC: T0_Chapter_Index @ CH_70].") and BEFORE the "- Companions:" line. No Ch 71 edit (Ch 71 inherits the unchanged clocks). Insert verbatim:

---

5. Integrity-band terminology drift before the Ch-65 path lock

Options considered:

Recommendation: A, executed with the cheap documentation step of C: capture the canonical vocabulary + accepted-synonym note NOW (apply-now-safe), and DEFER any node sweep. The single genuine fix ('L3 Neutral band' → 'L3 Drifting band') is folded into C's opportunistic approach, applied only when a node is next edited for another reason — never as a dedicated pass over ratified nodes.

Reasoning:

This is a NIT the reviewer already graded 'optional' on a BUILT, RR-ratified, tagged, delivery-ready arc. The master doc (T1_Integrity_Paths §3.2/§3.3/§4.1) establishes an unambiguous three-level architecture where the five bands map 1:1 to the five world states and to the three path buckets — so every spine phrasing, including 'L3 Neutral band', resolves to the SAME band/state/bucket and no downstream author is ever misled about a mechanic. That removes the normal justification for a normalization sweep (terminology drift is dangerous when it misassigns meaning; here it cannot). The one thing worth doing now is documentation, not editing: recording the master's §3-§4 vocabulary as the canonical standard and blessing the spine's synonyms closes the item as 'standard captured, sweep deferred' rather than leaving an open defect — and that is a pure labeling/register clarification pointing at already-existing Josh-owned canon, touching no chapter/numerical/naming/hard-line assignment. A 60+-file cosmetic sweep, by contrast, would reopen ratified windows and hard-line nodes and (per the standing lesson that parallel prose edits can inject reveal leaks a gate can't catch) force a reveal re-verify over each — cost grossly disproportionate to the gain.

Adversarial findings:

Stressed the recommended option on five axes. (1) Reveal leak: the doc-capture note authors only band/world-state/bucket labels — none of which is reveal-held content (the cosmic thesis, Grand Sage identity, and House-of-Velheim name are untouched; no who-frame, no locked thesis phrasing). Safe. The reveal risk lives in the SWEEP, not the capture — which is precisely why the sweep is deferred. (2) Invent-canon: the note changes NO assignment; it mirrors §3.2/§3.3/§4.1 verbatim and cites them. Blessing 'three finales'/'Evil-bucket' as synonyms is not invention — 'three ending architectures/three Finales' and 'the Evil path bucket' are both already the master's own concepts (§1, §3.3); the note only declares the spine's shorthand equivalent, a labeling clarification. (3) §17.1 Care: no cultural, living-tradition, or human-subject content in scope. N/A. (4) 'Resolve-don't-defer' objection: satisfied — the DECISION (what the canonical vocabulary is) is resolved and recorded now; only the mechanical churn over ratified nodes is deferred, which is the correct disposition for an optional NIT, not an unresolved fork. (5) Is even the 'L3 Neutral band' fix truly a defect? Arguably it is a deliberate reader-friendly fusion of band-index (L3) with world-state (Neutral); the canonical form 'L3 Drifting band / World State 3 Neutral' is a clarification, not a correction of an error — which is exactly why it is opportunistic-only and never forced. No axis produces a break, leak, invention, or care failure.

Exact change (paste-ready):

Apply-now-safe (documentation only; no node edits). Add the following resolution note to the finding's entry in docs/spine/WHOLE_ARC_REVIEW.md (and, if desired, mirror one line into docs/spine/SPINE_LIVING_REVISION_LOG.md):

---

RESOLUTION (integrity-band terminology NIT): Canonical vocabulary captured; node sweep DEFERRED (optional, out of proportion to a NIT on a ratified arc). No prose edits applied.

Canonical target — per T1_Integrity_Paths_Worldstates_Master [ACTIVE v2.1] §3.2/§3.3/§4.1:

Accepted spine synonyms (not defects — leave as-is): 'three finales' = the three ending architectures / three path buckets; 'Evil-bucket' = the Evil path bucket; hyphenated adjectival forms ('Truly-Good path', 'Good-Enough Finale') are correct English adjectival hyphenation and are preferred in-prose over the master's unhyphenated noun form.

Only genuine (optional) correction: the pre-lock path_states phrasing 'near the L3 Neutral band' fuses the band name (L3 = Drifting) with its paired world state (WS3 = Neutral). Canonical form is 'L3 Drifting band (World State 3 Neutral)'. Apply OPPORTUNISTICALLY only when a node is next edited for another reason — do NOT run a dedicated sweep over the tagged/ratified nodes for this. If a uniform sweep is ever wanted, fold it into the Fable grading pass or a scoped RR mechanical pass, gated with a reveal re-verify.

---

If nothing else touches the review doc, the change is exactly this note; otherwise 'none' to the chapter prose.

---

6. "reunion" overloaded across the familiar/finale through-line (Ch 58 vs 70 vs father)

Options considered:

Recommendation: Option 1 — Document-only. Record the vocabulary convention in WHOLE_ARC_REVIEW/handoff and apply no finale prose edits now. The optional Option-2 tidy is apply-now-safe but must be the complete SIX-line version, taken opportunistically only when those nodes are next edited for another reason — not worth a dedicated edit pass of hard-line finale nodes on its own.

Reasoning:

Verified against the files: 'reunion' carries THREE relational senses, not the finding's two — (A) protagonist↔childhood familiar (Ch 58 'Child-Familiar reunion'); (B) familiar↔realm/King (Ch 70/75 'return-to-realm reunion' / 'Familiars-thread reunion beat'); (C) protagonist↔father/the King (the DOMINANT finale use — CH_75 is titled 'The Father Encounter — the reunion met', carried by CH_76:13 and CH_77:19). The finding's frame ('reserve reunion for Ch 58') is untenable because it would force an invasive rename of the finale's emotional climax where sense C is correctly lexicalized. The overload is already carried by qualifiers in essentially every instance, and the lone co-occurrence (Ch 70) is between two already-distinct qualified phrases in separate bullets — genuine NIT severity. Given the targets are hard-line (Ch 74/75) and §17.9-reveal-held (Ch 70/76/77) finale nodes, cost/benefit favors documenting a convention over editing sensitive prose.

Adversarial findings:

1) The deep-dive's Option-2 edit list is INCOMPLETE: it lists CH_70:20/85/113/143 and CH_75:131 but misses CH_75:67 ('the childhood-familiar reunion beat (the generative path, the Familiars thread)'), which independently labels the same Sense-B familiar beat 'reunion'. Renaming line 131 without line 67 leaves Ch 75 internally contradictory. The tidy, if taken, is a SIX-line change, not five. 2) The finding's proposed alternative 'homecoming' is DISQUALIFIED — verified CH_70:8/71 lexicalize 'reckoning-not-homecoming' and CH_70:60/65/80/136 attach 'homecoming-recognition' to the father; assigning 'homecoming' to the familiar return fights both. 3) Reveal/§17.1/canon safety of the tidy CONFIRMED CLEAN: target phrases are meta-anchor/asset-block prose (not reveal surfaces); the §17.9 hold block CH_70:156 is untouched; 'the Familiar's Choice' and 'return-to-realm' already exist verbatim, so nothing is coined and no chapter/Component/thread/hard-line assignment moves. 4) The Elven-King name-forbid (HL_0099) is not implicated — no instance names him. Net: these findings push the disposition toward document-only (Option 1); a half-applied Option 2 would create new inconsistency on sensitive nodes.

Exact change (paste-ready):

APPLY NOW: none (document-only). Paste-ready convention to add to docs/spine/WHOLE_ARC_REVIEW.md (and the session handoff):

"Familiar/finale 'reunion' vocabulary convention. 'reunion' denotes two beings rejoining and is ALWAYS qualified by who: 'the (Child-)Familiar reunion' (Ch 58, familiar-with-protagonist, Truly-Good path) and 'the father-reunion' / 'the reunion met' (Ch 70/75/76/77, protagonist-with-the-King). The familiar-with-realm/King beat (Ch 70/75, generative path) is 'the childhood familiar's return-to-realm' / 'the Familiar's Choice arc' — NOT called 'reunion' or 'homecoming' ('homecoming' is reserved-against by Ch 70's 'reckoning-not-homecoming' framing and already attaches to the father as 'homecoming-recognition'). Both 'reunion' senses keep the word because the parties differ; the shared verb reads naturally."

OPTIONAL TIDY (only when these nodes are next touched; apply ALL SIX or none, to avoid internal inconsistency):

All Sense-A (Ch 58) and Sense-C (father, Ch 70/75/76/77) instances stay verbatim.

---

7. Ch-1 best friend (Selection 2) — SEEDS the main companion + endgame reunion (SUPERSEDED 2026-07-14)

Superseded note: the old "Option B — accept the gender-resonance as the sole payoff" is retired; the best-friend choosing is now a flagship early-choice → whole-journey → endgame link (the strongest in the connective-web map).

Recommendation: Option B — accept the gender-resonance as the sole payoff; make no player-facing change. (If a builder wants the intentionality marked at the design layer, the optional designer-only annotation under Option A-designer-note is the only safe additive form; it is not required.)

Reasoning:

The friend's non-return is not an unpaid thread — it is intentional by construction. CH_01 authors a deliberate familiar/friend asymmetry (line 88: the familiar is 'the thing the fall will not be able to fully sever,' recovered across Ch 58/70/75; the friend is the contrast — part of what the fall took) and states the friend's sole designed discharge is the gender-link (line 89, T3_Core 3.2). CH_01's own civilizational mark (line 49) already frames it: 'the deepest wound is the one that takes what was simply had.' The friend being among the simply-unrecoverable IS the fall's cost made real, and restoring it would cheapen both the cost and the familiar's meaningful return. On first play the friend has zero forward valence, so there is no expectation to pay off; the only lens that notices the friend is the re-play audit lens — which is exactly where the gender-resonance is the intended discovered payoff. Every player-facing acknowledgment (the finding's Option a) intrinsically authors a fate — either present (embodied reunion, a cardinal fork) or absent (a loss canon never set) — and the only tonally-available placement, Ch 70, is where CHAR_0002 is on-screen (resonance-leak risk) and where the father-grief monopoly is the load-bearing design. So the resolve-don't-defer answer is: do nothing player-facing. This is within vision, invents nothing, and touches no locked canon.

Adversarial findings:

Stress of the provisional best (A@70) breaks it on four points: (1) it is not fate-neutral — 'not here to be recovered' asserts the friend's absence, authoring a loss-outcome canon never set, and does so on top of an inference (CH_01 line 33 states only the familiar fell; the friend's whereabouts are unstated), which is do-not-invent tension. (2) The gender-resonance leak is real, not hypothetical: CHAR_0002 is present in the Ch-70 scene (line 18/85), so a 'friend beside me then' interiority beat can make the 'invisible on first play' resonance legible, cheapening the very payoff the finding protects. (3) It introduces a second personal grief-channel that smudges Ch-70's father-grief monopoly ('blighted by how much he has missed her') and its grief-vs-corruption discernment mechanic. (4) The felt-gap is smaller than the finding claims — the non-return is already carried as intentional by the asymmetry + civ-mark, and only surfaces to the same re-play audit lens that finds the gender-resonance. Also confirmed: A@74 (antisemitism-guardrail confrontation) and A@75 ('only a father and a child') are tonally sealed and disqualified, leaving Ch 70 as the sole candidate — and it is not free. No §17.9/House-of-Velheim/Grand-Sage reveal content is involved either way (the friend is reveal-inert); the risk is design-integrity, not a reveal leak. The Realm-War window (Ch 71-73) was not read; any heavier friend material (a survivor/loss role) would live there and is a Josh fork, not something to apply.

Exact change (paste-ready):

none (player-facing). Recommend no edit to CH_01, CH_70, CH_74, or CH_75. — Optional, only if a builder wants the intentionality marked at the design layer (not required and not recommended as necessary): append to CH_01's 'Key ally NPCs' best-friend bullet (line 89), inside the existing designer-facing sentence, the clause: "; the friend remains in the realm at the fall (only the familiar falls with the child, line 33) and is deliberately NOT recovered on the return — the authored familiar/friend asymmetry (the familiar is what the fall could not sever; the friend is part of what the fall took), so the friend's non-return is intentional grief-geography, never an unpaid thread, and carries no player-facing acknowledgment beat (which would author a fate and risk surfacing the Ch-13 gender-resonance)." This is a designer-only annotation; it adds no player-facing prose and authors no fate.

---

8. Epilogue→Prologue ring: journal-as-vehicle is fine; no change needed

Options considered:

Recommendation: Option A — no change. The Epilogue→Prologue ring is already well-formed through the 'road' inclusio, the 'first page again' re-begin gesture, and the memory↔record rhyme; the healer's-child journal (a Ch-13 object) is the correct vehicle and the fact that it is not a Prologue object is immaterial to ring composition, which needs a rhyming close, not a shared artifact.

Reasoning:

I read both spine entries in full. The finding's premise is verified: the ring vehicle is the journal begun Ch 13 (CH_EPILOGUE line 40), not a Prologue object, and 'began with a fall' correctly denotes the Ch-1 rift-fall (Prologue Q1, line 154, explicitly reserves the fall for Ch 1; the Prologue's own rift is sealed successfully — there is no fall in 'The Birth'). Ring composition is delivered by a rhyming close, and three devices already deliver it (road inclusio, first-page-again, memory↔record), so the absence of a shared diegetic object is a non-issue. The 'first page again' ambiguity (journal's first page / the whole story's first page = the read-first Prologue) is a deliberate meta-ring, not a defect. No strengthening is warranted; the two candidate strengthenings both degrade the node's essential restraint, and Option B additionally carries a subtle reveal-adjacency (echoing the Prologue's return-motif keynote nudges the close toward the held return-thesis). Likely-classification confirmed: no-change-needed.

Adversarial findings:

Stressing the no-change recommendation for reveal leaks / §17.1 / invented canon: (1) Reveal — no-change touches nothing, so there is no exposure; the 'hand, unseen' is the already-authored held/uncaptioned unseen reader (Q3, lines 33/88/106), not a leak. Notably, the adversarial pass surfaced that the OPPOSITE action (Option B) would be the reveal risk: the Prologue's 'to get back to' keynote is the return-to-fullness motif that is the felt shape of the held thesis, so amplifying its Epilogue echo edges toward restating the return-thesis (HL_0043/§18.1) — a reason to reject B beyond mere redundancy, and a reason the current restrained wording is actively correct. (2) §17.1 — the seam depicts no living Earth community; framed-narrative/testament traditions are craft-reference echoed never lifted (line 100); no-change preserves this. (3) Invent canon — no chapter/numerical/naming/hard-line assignment is touched; the Elven King is not named at the seam; the journal is established Ch-13 canon (T3_Core §3.13). (4) The one apparent nit ('began with a fall' seems to point at Ch 1, not the Prologue) is not a defect — 'the road' = the protagonist's journey, launched by the Ch-1 fall; the Prologue+childhood are the pre-road home, so the phrasing is precisely accurate and still rhymes on 'road' with the Prologue's 'the whole long road ahead.' Conclusion: no-change survives adversarial stress; the current wording is not just adequate but the safest option.

Exact change (paste-ready):

none

---

9. Distinctness-guarded Norse Álfheim (LIGHT axis) enrichment for the fairy-realm return, Ch 70 + Ch 75

Options considered:

Recommendation: Option 2 (refined): make the already-anchored Norse Álfheim a FELT, distinct presence on the LIGHT axis in Ch 70 (sharpened civ-mark + both firewalls extended + one asset line), and add a single asset-level Álfheim light echo to Ch 75 — the one axis that cannot blur into the Celtic return/sovereignty material, grounded (Snorri's 'fairer than the sun'), and entirely felt-not-lectured. Option 1 is a defensible low-cost decline, but the Ch 75 gap is real and the enrichment is cheap and on-vision.

Reasoning:

The finding's premise is half-accurate and I corrected scope against the page: Ch 66-69 are NOT Celtic/fairy (verified CH_66 = Plato/orichalcum; the four thresholds are Plato / Kalevala+Pythagoras / Enuma Elish / Ma'at). The fairy/fair-folk substrate lives in exactly two nodes — Ch 70 (the return) and Ch 75 (the father's court). 'Changeling-inversion' does not appear in any of the six files; the Celtic material actually present is Otherworld-return (Oisín/Niamh), Sídhe sovereignty, and the Grail/Fisher-King wound. Ch 70 already anchors Álfheim at civ-mark depth (line 44, with Ljósálfar/Dökkálfar) but it is an attributed name-check, not felt; Ch 75 has zero Norse register (grep-confirmed). The distinctness key is that Ch 70's body prose ALREADY runs on light imagery that is currently un-attributed (reads as generic vril-glow), and Ch 75's court is literally 'bright vril... frozen mid-fall' — so attributing that existing, load-bearing light-register to the authentically-Norse Ljósálfheim 'fairer than the sun' glory deepens what is on the page rather than importing a competing element, while the Celtic axis (timeless youth, return-as-bereavement, sovereignty-wedded-to-land) stays untouched. Elf = álfr and Álfheim is her birth-realm, so Norse is the aptest tradition, not an imported one. It changes no assignment and touches nothing reveal-bearing, so it is applicable within the deep-dive+adversarial method without a Josh fork.</parameter>

<parameter name="reasoning">The finding's premise is half-accurate and I corrected scope against the page: Ch 66-69 are NOT Celtic/fairy (verified CH_66 = Plato/orichalcum; the four thresholds are Plato / Kalevala+Pythagoras / Enuma Elish / Ma'at). The fairy/fair-folk substrate lives in exactly two nodes — Ch 70 (the return) and Ch 75 (the father's court). 'Changeling-inversion' does not appear in any of the six files; the Celtic material actually present is Otherworld-return (Oisín/Niamh), Sídhe sovereignty, and the Grail/Fisher-King wound. Ch 70 already anchors Álfheim at civ-mark depth (line 44, with Ljósálfar/Dökkálfar) but it is an attributed name-check, not felt; Ch 75 has zero Norse register (grep-confirmed). The distinctness key is that Ch 70's body prose ALREADY runs on light imagery that is currently un-attributed (reads as generic vril-glow), and Ch 75's court is literally 'bright vril... frozen mid-fall' — so attributing that existing, load-bearing light-register to the authentically-Norse Ljósálfheim 'fairer than the sun' glory deepens what is on the page rather than importing a competing element, while the Celtic axis (timeless youth, return-as-bereavement, sovereignty-wedded-to-land) stays untouched. Elf = álfr and Álfheim is her birth-realm, so Norse is the aptest tradition, not an imported one. It changes no assignment and touches nothing reveal-bearing, so it is applicable within the deep-dive+adversarial method without a Josh fork.

Adversarial findings:

Stressed the recommended option and it holds, with four refinements folded in: (1) Reveal leak (Ch 75) — the only real danger, since Ch 75's held-silence (HL_0116) is the arc's most delicate restraint. Mitigated by confining the Ch 75 edit to the ASSET/material_palette layer (design register, about the crystallized court's visual palette), attaching 'fairer than the sun' to environmental grief-crystallization already established, with NO King-identity, protagonist-identity, or cosmic content, no future-tense/agent-noun, and explicitly no proper noun in body prose. The King's silence is untouched. (2) Racialization care trap — the Ljósálfar/Dökkálfar light/dark ordering: the recommended edit adds an explicit anti-moral-binary firewall (held as Snorri's own schematization, Dökkálfar plausibly a dwarf-conflation, corruption authored so it can never be read off a light/dark axis, never a 'dark-elf' people) — mirroring the Ch 68 'Tiamat-as-dragon held scholarly-contested' precedent. (3) Self-created risk — attributing the light to Álfheim could invite a Nordic-race-mystical-radiance reading that fights the vril-ecology Frame-A firewall; closed by extending Ch 70's existing Vril-Society firewall (line 102) explicitly to the light register. On Ch 75 this is ALREADY covered — line 104 says 'never a race-resonance'/'substrate-mathematics' — so NO new Ch 75 firewall is needed (keeps the delicate chapter's touch to one asset line). (4) Placement/lecture-iness — I split the two firewalls to their natural homes (light-mystical → line 102 Vril-Society; moral-binary → line 103 fairy-tradition-care) instead of stacking both into the civ-mark, keeping the felt civ-mark short. Do-not-invent check: no chapter/Component/numerical/naming/hard-line change; Álfheim already canonically anchored; the 'fairer than the sun' and dwarf-conflation notes are real attributed L2 scholarship, not invented game-canon. HL_0099 (King name-forbidden) and HL_0116 (held silence) untouched.

Exact change (paste-ready):

FIVE edits (four in docs/spine/CH_70.md, one in docs/spine/CH_75.md), each an insertion placed immediately BEFORE the [SRC] brackets that end the target line. Anchor strings are verbatim from the current files.

--- EDIT A — CH_70.md, civilizational-marks line 44 (make the LIGHT axis felt + distinct) ---

FIND: a distinct mythological cosmology, not a lesser order of spirits [SRC: T1_Research_Corpus_Master # Ch 70] [SRC: SIGNIFICANCE_LENSES].

REPLACE WITH: a distinct mythological cosmology, not a lesser order of spirits; the game reads this Álfheim strand on its own distinct axis — LIGHT, the realm whose defining glory is a radiance fairer than the sun, so that the dimming the player perceives registers as that luminous quality going out — held complementary to and never merged with the Celtic axis of timeless youth, return-as-bereavement, and sovereignty-wedded-to-the-land (the two traditions echoed side by side, never blurred into one fairyland) [SRC: T1_Research_Corpus_Master # Ch 70] [SRC: SIGNIFICANCE_LENSES].

--- EDIT B — CH_70.md, Anti-fringe / Frame-A flags, Vril-Society firewall line 102 (extend to the light register) ---

FIND: the Bulwer-Lytton and Vril-Society lineage held as the excluded association [SRC: ESOTERIC_GROUNDING].

REPLACE WITH: the Bulwer-Lytton and Vril-Society lineage held as the excluded association; the Álfheim fairer-than-the-sun luminosity in particular reads as vril-ecology and craft-radiance, never a race-mystical "Nordic light" or the birthright of a light-race — the firewall extended explicitly to the light register, where the Álfheim-plus-Nordic-plus-radiance combination is exactly where a race-mystical reading could creep [SRC: ESOTERIC_GROUNDING].

--- EDIT C — CH_70.md, Anti-fringe / Frame-A flags, fairy-tradition care discipline line 103 (add the anti-moral-binary firewall) ---

FIND: and Tolkien, Dunsany, and Morris echoed as tradition never lifted; the game's fairy realm its own invention [SRC: T0_Hard_Lines @ HL_0001].

REPLACE WITH: and Tolkien, Dunsany, and Morris echoed as tradition never lifted; the game's fairy realm its own invention; and the Ljósálfar/Dökkálfar light-elf-and-dark-elf ordering is held as Snorri's own schematization (scholarly-contested, the Dökkálfar plausibly a conflation with the dwarves) and is NEVER rendered as a moral light-good/dark-evil racial binary — the realm's corruption is the family's reach made geographic, authored so it can never be read off a light/dark axis, and never a "dark-elf" people [SRC: T0_Hard_Lines @ HL_0001].

--- EDIT D — CH_70.md, Asset anchors, material_palette line 115 (the felt light stratum) ---

FIND: awe-and-loss, never a whimsical flower-fairy or an occult-elemental rendering [SRC: T1_World_Geography_Master # 9].

REPLACE WITH: awe-and-loss, never a whimsical flower-fairy or an occult-elemental rendering; the light-design carries a distinct Álfheim luminous stratum — the fairer-than-the-sun radiance and its going-out — readable as a third layer separate from the King's grief and from the corruption's rot (re-registering the existing vril-decline, not a new mechanic) [SRC: T1_World_Geography_Master # 9].

--- EDIT E — CH_75.md, Asset anchors, material_palette line 117 (the Norse light echo; the only Ch 75 touch) ---

FIND: mythologically-stylized (the game's own dimensional court) [SRC: T1_World_Geography_Master # 9].

REPLACE WITH: mythologically-stylized (the game's own dimensional court); the frozen bright vril carries a distinct Norse Álfheim light echo — the luminous glory fairer than the sun stilled by grief, the radiance frozen mid-fall — held complementary to the Celtic wounded-king and aos-sí sovereignty register that governs the wound-as-wasteland, the two traditions distinct and attributed, echoed never lifted, and no proper noun entering the body prose [SRC: T1_World_Geography_Master # 9].

NOTE: No body-prose edits (Ch 75's reveal-restraint is load-bearing). No new firewall on Ch 75 — line 104 already carries the race-mystical/'never a race-resonance' guard that covers Edit E. HL_0099 and HL_0116 untouched.

---

10. Otherworld-abundance felt-motif: curate a light "scarcity briefly lifts" through-line across 3-4 traversal nodes (Ch 2 root untouched, Ch 57 excluded)

Options considered:

Recommendation: Placement B with the M1 carrier (rendered as the scarcity/lack briefly lifting — NOT light-from-nowhere), M3 permitted as a single water-node variation, M2 dropped. Concretely: Ch 2 stays untouched as the existing ratified origin instance; add ONE light felt-clause at Ch 21 (the Wudang neidan beat) and ONE at Ch 39 (the ase substrate-recognition beat); select a fourth clean, non-protected, vril-dense hand-off node in the Ch 48-54 band (candidate Ch 52 Uyuni altiplano) and author its clause only after a reveal re-verify of that node. Ch 57 is excluded. Every touch is applied at the node's next re-enrichment/RR pass WITH a mandatory reveal re-verify and a golden Step-0 coverage check, never as a blind inline edit.

Reasoning:

The load-bearing chain (Prologue ceiling -> Ch 2 depleted floor -> Ch 70 reclaim) already exists; Ch 70 ASSERTS at the payoff that she carried the intuition 'through all of it' ('The oldest thing she carried... the sense that the human world was somehow a beautiful lie, was true'), but the traversal only thinly seeds it. A minor felt-motif lets the player feel it WITH her a few times so the Ch 70 line lands as recognition, not exposition. The motif must be the payoff's own logic — FULLNESS (the human world was 'lying about' fullness), so M1 is correct and M2 (capacity/identity) is wrong. Rendering it as the LACK lifting (not sourceless light) keeps it clear of the Prologue's read-first signature while staying native to Ch 2's own 'emptied... falling water gathers it' frame. Ch 21 (cultivated breath 'schools her hands in the wu-wei flow') and Ch 39 (ase as 'the same substrate she has touched under a dozen names... mechanically real') are the two aptest existing beats — the fullness rides HER phenomenology/recognition, not the sacred practice, so no appropriation. Ch 39 is thematically ideal: her honest felt-recognition of ase stands against Selby-Marchant's commodification of it, putting the touch on the right side of the chapter's own anti-extraction line. Ch 2 is left alone because its ratified line is already the root and re-authoring it courts a Step-0 SPREAD drop for no gain.

Adversarial findings:

1) The deep-dive's Ch 57 pick is the biggest flaw: it is MAXIMUM-care, hard-line, author-in-loop with Stage-2 questions batched for Josh; it already carries the Grand-Sage presence-hint and the 'felt something beneath the surface everywhere' through-line; a touch there blurs the reveal, is redundant, and instrumentalizes sovereign Aboriginal country against the node's own guest/'does-not-own-the-healing' discipline. DROPPED. 2) M1 as 'the air brightens from nowhere' would reproduce the Prologue's distinctive sourceless-light signature (Prologue is read FIRST) — re-registered as the LACK lifting to avoid the premature back-link. 3) M2 ('every faculty could open all the way') collides with Ch 70's held payoff ('every skill opens all at once') and the §17.9 'no vast-identity gesture' hold — DROPPED as the identity-magnitude leak vector. 4) 'Sharpening' the ratified Ch 2 line is a needless re-author with a golden Step-0 SPREAD-drop risk — Ch 2 left untouched. 5) The realm-origin is NOT a held reveal (player knows she is an elf from the Prologue), so the motif is origin-safe; what is held is the cosmic thesis/Grand Sage — the clauses stay substrate-phenomenology with zero forward valence, no agent-noun/who-frame, and no birthright surfaced (anti-fringe vril firewall: fullness = atmospheric saturation, never race-mystical polar-energy/birthright). 6) Every candidate node is committed/ratified, so any touch is a prose re-author requiring a reveal re-verify + Step-0 check at application — not a silent inline edit; the 4th late node's clause is withheld until that node is read for reveal-state.

Exact change (paste-ready):

Apply at each node's next re-enrichment/RR pass, WITH a reveal re-verify + golden Step-0 coverage check; do NOT blind-edit now.

CH_02 — NO CHANGE. The existing ratified line ('...become one continuous distance the child was never told existed. None of this is spoken. It is felt, through the hands, at the water.') is the motif's origin instance and stays verbatim.

CH_21 — append one clause to the existing Wudang/Shaolin sentence in Body prose. Current sentence ends: '...school her hands in the wu-wei flow the archive keeps demanding of her.' Change the terminal period to a dash and append:

'— and once, as the cultivated breath settles all the way, the ordinary want of the world drops out for a single beat, the air briefly full in a way the human world never quite is, gone before she can turn to look at it.'

CH_39 — insert one sentence in Body prose immediately AFTER the existing sentence that ends '...the same substrate she has touched under a dozen names across the world, here in Yoruba, mechanically real.' New sentence:

'And for a breath, standing in the current of it, the world stops feeling drained — the background scarcity she has lived inside her whole human life simply lifts, the air gone briefly full, and settles back before she can name what left.'

FOURTH (late hand-off) NODE — NOT paste-ready. Select one clean, non-protected, vril-dense traversal node in the Ch 48-54 band (candidate: Ch 52, Bolivia/Uyuni altiplano) that is neither maximum-care nor reveal-critical; read it first for reveal-state, then author a single M1 (or one-off M3 water) clause in the same register. Ch 57 is explicitly excluded.

Register rules binding all clauses: carry FULLNESS as the depletion/scarcity briefly lifting (never 'light from nowhere' — that is the Prologue signature); keep it present-tense bodily sensation, un-nameable to her, quickly gone; NO capacity/identity-magnitude ('faculties open'), NO agent-noun/who-frame, NO forward/prophetic valence, NO birthright surfaced; one clause per node only.

---

11. Supplement the §8.8 five-parallel finale set with a non-Old-World tradition

Options considered:

Recommendation: Option A, routed as Option D: recommend no change (no supplement), surfaced to Josh as a closed fork with reasoning rather than left open. Concrete change to CH_77.md: none.

Reasoning:

Three independent reasons converge on no-change, ranked. (1) The finding itself states the Fable handoff LOCKS the §8.8 five as load-bearing, and Ch 77 is a hard-line node (line 12). The count is not decorative: 'five' is woven into the body prose (line 29), the SQ3/SQ7 side-quest mapping (line 85), and the Weaving-20 cross-tradition synthesis (line 45). Altering the set is a re-author of a locked, hard-line element — outside my do-not-invent authority; it is Josh's call. (2) The proposal's own non-Old-World guard cannot be met without a §17.1 care failure. The reveal's specific shape is self-as-source (the guide was never separate; the council one keeps is oneself; the circle's far end is its near one — lines 35/51). The traditions that attest that shape cleanly are all Old-World mystical philosophy; the non-Old-World candidates that resonate require distortion: Tezcatlipoca's smoking mirror was scrying/fate/rulership, not a self-is-source recognition; the Plains sacred hoop is a living high-care tradition that conscripting into a 'same recognition' set is exactly the flattening §17.1 forbids. The genuinely precise fits — Advaita's Tat Tvam Asi and Yoruba Ori — are themselves Old-World (India; West Africa) and so fail the non-Old-World guard, and Advaita additionally collapses toward the existing Sufi register, reducing distinctness. That every clean fit is Old-World and every non-Old-World candidate needs distortion is itself evidence the set is Old-World by fit, not oversight. (3) Piling a sixth 'same recognition' tradition onto the terminal node raises the perennialist/hyperdiffusion load the chapter already actively guards (lines 104/110: 'a convergence of symbolic structure across cultures, never a shared historical source... never hyperdiffusion or ancient-aliens'). If Josh's real concern is breadth, the better levers are not at the locked node: tighten the internal redundancy of the existing five (2 Plato + 2 Sufi into a sharper three-to-four distinct roads — Option C, his call), or distribute cultural breadth across the arc's earlier L2 substrate (Ch 2-75, 69 regions) where the finale's convergence is earned rather than tokenized.

Adversarial findings:

Stress-testing the no-change recommendation for where it could break: (a) Reveal-leak — the recommendation is analysis-only, no edit, so no §17.9 surface changes; and I mirror the file's own discretion (the locked thesis phrasing is owned upstream, T3_Core §8.7/§18.1, and is neither reproduced nor authored here) — I describe the reveal's shape only via the proxy-glosses the file itself already surfaces openly (lines 35/51), never the locked sentence. No leak. (b) Invent-canon — the candidate tradition names (Advaita/Tat Tvam Asi, Yoruba Ori, Tezcatlipoca, sacred hoop) are decision-support handed to Josh, not written into any canon file; nothing is added to CH_77.md or a registry. No invention. (c) §17.1 — the recommendation actively avoids the care landmines rather than committing them. (d) The one over-reach in the first-pass deep-dive: it offers Josh a 'best candidate' (Advaita). That is acceptable as analysis ONLY because it is paired with the finding that even the best candidate argues against the change (Old-World + Sufi-redundant); if handed to Josh it must be framed as 'why even the strongest candidate fails,' not as an endorsement to add — otherwise it risks reading as a soft recommendation for Option B. Framed correctly, no-change stands. (e) Could a truly clean, care-safe, non-Old-World fit exist that both passes were missing? Adversarial sweep of Indigenous-American / Oceanic / non-Old-World options finds none that attests self-as-source without distortion — which strengthens, not weakens, Option A. (f) Does recommending against the proposal overstep by pre-empting Josh? No — the disposition is explicitly to route it to him as a fork with a recommended disposition, not to close it unilaterally.

Exact change (paste-ready):

none — no edit to docs/spine/CH_77.md. Route to docs/spine/DECISIONS_PENDING_JOSH.md as a closed fork with recommended disposition NO CHANGE. Suggested pending-decision entry (paste-ready, decision-support only — not a canon edit): "§8.8 finale parallels — supplement with a non-Old-World tradition? RECOMMENDATION: no change. The five (Plato's Cave, Plato's Charioteer, Laozi's Tao, al-Hallaj's Ana l-Haqq, Attar's Conference of the Birds) are Fable-locked and load-bearing — the count 'five' is woven into body prose (CH_77 line 29), the SQ3/SQ7 mapping (line 85), and the Weaving-20 synthesis (line 45), on a hard-line node. Every clean thematic fit for the reveal's self-as-source shape is Old-World mystical philosophy; every non-Old-World candidate that resonates (Tezcatlipoca's mirror, the Plains sacred hoop) requires distorting a living/historical tradition to fit — a §17.1 care failure and an increase in the perennialist load the chapter already guards (lines 104/110). The strongest precise fits (Advaita's Tat Tvam Asi; Yoruba Ori) are themselves Old-World and/or collapse toward the existing Sufi register, so even they argue against the change. If breadth is the goal, the better non-locked levers are: (i) tighten internal redundancy of the existing five (2 Plato + 2 Sufi to a sharper 3-4 distinct roads), or (ii) distribute cultural breadth across the arc's earlier L2 substrate (Ch 2-75), where the convergence is earned. Josh's call — touches the Fable-locked, hard-line set."

---

Generated by harness/site/structure_site.py — the URL path is the repo path. review root