decisions/spine/CARDINAL_FORKS_BRIEF_2026-07-14.md
For Josh. Five genuinely cardinal forks surfaced by the Section-3 re-cascade, each run through the standing decision-analysis protocol (fan-out steelmanned alternatives → deep-dive grounded in CVD + tier docs + RCM + vision → adversarial review vs canon/vision/AAA/care-reveal → options/pros-cons/reasoning/recommendation/strongest-objection). Workflow wf_49b30a0e-c30 (10 agents: one analyst + one adversary per fork). Nothing here is applied — every affected node stays as-built and reversible until you rule. The creative-within-vision halves I have already applied or can apply the moment you rule (listed per fork); only the cardinal cores below need you.
How to read this: each fork gives you the question, the options, my recommendation, the single strongest objection, and exactly what I need from you. Where the adversary changed the recommendation, I say so.
---
| # | Fork | My recommendation | The one call |
|---|---|---|---|
| F1 | Ch 72 Vritra: kill or release? | Two co-primaries — either kill-at-72 (max-faithful, priced optics) OR relocate the clean kill to the care-free Ch-75 dragon and keep Vritra honored-release | kill-at-72 vs kill-at-75; + accept/decline the out-of-context-clip optics |
| F2 | Ch 75 terminal dragon + coalition | Land both; fuse the terminal dragon into the ratified Cinder-Advance closer (or seat it as the Mv2→3 hinge) rather than adding a 5th marquee | seating (fuse / hinge / 5th) + its name |
| F3 | ER-1/ER-2 gladiator ladder | Self-apply 5 real-history rungs; reserve the tangata-manu depth call | tangata-manu witness vs participation (rule with F5) |
| F4 | Trade mastery-numbering | Ratify Option D (10 grades / 12 gates), conditioned on fixing HL_0084 + binding the name-primary rule | confirm Option D + the HL_0084 hard-line numeral fix |
| F5 | aku-aku forceable-bucket | Option C — state the sacredness line; keep aku-aku + duppy forceable-then-freed with riders; rule the class | where the sacredness line sits (binds Ch 59/62/63 together) |
Cross-fork: F3's tangata-manu (Ch 63) and F5's aku-aku (Ch 63) are both Rapa Nui §17.1 calls on the same sacred envelope — rule them together as one Rapa Nui care decision.
Suggested order (most-gating first): F4 (numbering gates two questlines and the F3 Epilogue loop) → F5 + F3-tangata-manu (one Rapa Nui ruling) → F2 → F1.
---
Question. At Ch 72 the protagonist, echoing the Indra-archetype, breaks the last coil of Vritra the Enclosing Dragon and looses the pent cosmic waters. Does Vritra die by that blow — the waters running *because* the serpent is slain, exactly as the tradition's own oldest hymn RV 1.32 frames it (Indra *Vritrahan*, "the Vritra-slayer") — or is the built release-not-kill preserved ("un-enclosed, returned to his bounds, never a corpse to gloat over")?
Provenance note (important): the built release-not-kill was an autonomous build-time resolution, not a prior Josh ruling — there is no "JOSH RULED" banner for Ch 72. So choosing the kill *revisits a Claude decision*, it does not overturn yours. The punch-list phrase "a ratified §17.1-MAXIMUM decision" overstates its weight.
Options.
Strongest objection (adversary) — and the co-primary it produces. The firewall governs the *design's* grounding, not the *audience's* associations: the devotionally-dominant Vritra today is the Puranic Brahmin-sage who attains liberation *through* his death at Indra's hand, so the optics exposure is real and directional and not neutralized in-fiction. Crucially: §17.16 is *already satisfied* by the built node (release-by-breaking-coils is a real fought marquee boss, never a routed-around puzzle) — so the hard line mandates the fight, not the corpse. And the flagship's "one clean fair-game kill" is fully satisfiable one door later at Ch 75 (the care-free realm-native Fáfnir/Muspell dragon), since Thread-2 convergence lands at Ch 72 whether or not Vritra dies. → This makes "keep Vritra honored-release at 72, put the clean kill on the Ch-75 realm-dragon" a genuine co-primary, not an also-ran: it gives the flagship its kill at zero living-religion cost.
What I recommend you weigh: two clean paths — (B) kill-at-72 (max-faithful; you accept a priced, directional optics exposure at the top care tier) vs (relocate) kill-at-75 (Vritra honored-release stays; the unambiguous corpse rides the care-free dragon). Either way: reject C (keep care_tier MAXIMUM), and if any integrity texture rides, it's on the *manner* (gloat/amrita-grasp), never kill-vs-spare.
What I need from you: (1) kill-at-72 vs kill-at-75; (2) if kill-at-72, your accept/decline of the out-of-context-clip optics (a marketing/QA/comms call, parallel to D-08, not closable in-fiction); (3) confirm care_tier stays MAXIMUM either way.
Self-applies once ruled: dropping the no-corpse clause (if kill), or leaving the node as-built (if release/relocate); the Ch-75 dragon already needs authoring under F2 regardless. Reveal axis is clean either way (beast-lineage beat, no family leak; felt-recurrence stays undeclared).
---
Question. Should the recurring chaos-dragon lineage get its terminal fought stand at Ch 75 (TL-08's "final answered stand"), and should the TL-25 coalition-return be authored (Arawn + honored otherworld guardians stand with her / send aid; the taming-breeding roster mustered as a war-host)?
Status correction: D-EMB-75 (the four Movement-2 champions — Unlidded Eye / Westering Host / Pitch-Court / Cinder-Advance) is already ratified + applied (BOSS_PERSONAS BE_0075). The "blocked by D-EMB-75" notes in the punch-list and DECISIONS_PENDING_JOSH.md are stale pre-ratification snapshots. Both items in this fork are *unbuilt*: Ch 75 records Thread 2 as NOT_PRESENT and lists no coalition.
What self-applies (creative-within-vision, no ruling): the coalition-return itself (Arawn is canonical at Ch 73; the guardians are canonical allies — no new naming); the felt-L3 terminal recognition held undeclared (Ch-69 Apep precedent); the Thread-2 NOT_PRESENT→ANCHOR flip; the war-host muster (fields *existing* familiars — no count touched, the 12 elven-native legendary species stay honored/un-fought). Two gates on the self-apply: (a) the Arawn-crossing execution routes through the care-critic — it must not collapse the load-bearing Ch-73 firewall that Annwn is a distinct honored Welsh Otherworld, *never* conflated with the game's own fairy realm; (b) coalition is Arawn + selective aid where the protagonist parted owing/owed, not a blanket "all guardians march" (Louhi, CH_67, is an honored *adversary* who withdrew sovereign — casting her as a marching ally is a coherence stretch).
The cardinal core — seating the terminal dragon. The analyst first proposed a *fifth* named marquee. The adversary corrected this and I agree: a free-standing fifth marquee collides with the ratified loud-to-silent signature (the Cinder-Advance is canonically THE closing eschaton-wall marquee, then the war goes silent for the wordless solo colossus) and risks back-to-back dragon fatigue (Ch 74 Níðhöggr → Ch 75 dragon). Options:
Strongest objection: the "ratify one name + a four→five re-weight" framing under-ranks what a fifth marquee actually does — it re-opens the D-EMB-75 architecture you ratified only 2026-07-13, whose explicit signature is the loud-to-silent hinge. So the genuinely cardinal question is structural, not nominal.
What I need from you: (1) seating — fuse-into-Cinder-Advance (rec) vs Mv2→3 hinge vs free-standing fifth; (2) the name for the terminal chaos-dragon (a champion title if a fifth, a sub-title under the Cinder-Advance if fused; proposed *the Last Coil*; alts *the Root-Wyrm* / *the Deep-Coil*) — with the D-EMB-75 sub-flag that Fáfnir/Níðhöggr/Jörmungandr stay Layer-2 reference, never lifted as an in-world proper noun; (3) a one-line re-confirm that this dark-mythic boss is boss-roster, distinct from the 33-legendary / 22-familiar counts (identical to the confirm already given for the four).
Also gated: the "dragon's uncleared corruption feeds a limb of the Movement-3 colossus" flourish is gated self-apply — it must read strictly as *her* unfinished leaving (the corruption she didn't fully clear), never the dragon's residue given external form (golem-exclusion / the intrinsic-mirror L3), and routes through the care/reveal critic. Reveal ceiling intact throughout (coalition is ally-side; Cassius Ch 76 / thesis Ch 77 untouched; family's hand stays faceless weather, never a marched army — HL_0109 held).
---
Question. Of the missing set-pieces on your flagship gladiator→Olympics chains, which self-apply (real history / ratified doctrine) and which are cardinal?
Self-apply (creative-within-vision — real history on standard-care nodes, or ratified doctrine on already-open layers):
1. Ch 23 pankration — the body beat already exists (she steps into the pankration, earns up the drawn lots, "the prize that cannot be bought"); wire it into the mechanical/boss layer as a scored consensual contest rung. *Operational rider:* this scatters BE_0023 rows → needs a same-commit --emit-baseline or the fidelity gate goes red.
2. Ch 28 Circus Maximus chariot race — add as a vehicle sub-rung feeding the ER-6 motorsport rhyme (documented Roman institution; the capture + arena above it are ratified, confirm-only).
3. Tinku assimilation contest — draw the protagonist into a Tinku on the community's own terms. Two corrections from the adversary: (a) Tinku is Bolivian (Macha/Potosí = Ch 52's ground), not Ch 51 (Nazca/Cuzco) — the punch-list's "Tinku Ch51" is a geography error; (b) Tinku carries a blood-offering-to-Pachamama religious dimension, so it is care-sensitive — route it through the fresh-context + care-critic lane (participation-vs-witness), and if the critic surfaces a participation problem it escalates to you. (Chapter placement Ch 51 vs Ch 52 is itself a chapter-assignment call — flagged, not self-decided.)
4. Epilogue contest-prestige loop — add as an L2-completionist systems free-play loop, firewalled from the §17.9/HL_0045 shared unseen-reader bookend prose (and the D-23 never-caption-the-departed-child trap) and NOT leaning on / re-labeling the Magister-Templi "Tier-9" prestige framing — because that tier-number is exactly the open F4 numbering fork. Any version that renders in the narrative bookend or leans on the tier-number crosses into two reserved forks.
5. Ch 65 human captive→liberator terminal recognition — a light additive callback so the freed modern concession-*humans* of Ch 59-64 stand among the freed at the existing re-freeing terminus (ER-2's human lineage gets its terminus alongside the spirit menagerie), routed through the broker apparatus, kept clear of the §17.1 Aboriginal land-dispossession beat. The line: *additive beat* self-applies; any change to the verdict-mirror / path-lock / re-bound-menagerie *structural core* is yours.
6. WS6 wiring — populate the Cross-Cultural Link Graph era-rhyme edges + light callback beats; retire the stale "never captured / liberate-from-outside" note in through_line_era_rhyme.md (superseded by the layer-model-v2 capture reversal).
Confirm-only (do not re-open): the Ch-28 capture (protagonist captured → fights for freedom, integrity-gated lethal route, easter-egg sneak-out) stands, per the layer-model-v2 reversal + D-14.
The cardinal core — reserved for you:
What I need from you: the tangata-manu depth (witness vs participation vs reference-only) — ideally in one ruling with F5.
---
Question. Does the ladder run on one index or two? The live Trade_Registry numbers Adeptus Minor = gate 7, Magister Templi = gate 11 (Portal = gate 6, Babe-of-the-Abyss = gate 10 as full gates), while CVD §12.1 + HL_0028/29/30 + CH_15 + CH_EPILOGUE all number Adeptus Minor = tier 6, Magister Templi = tier 9, Magus = tier 10. You ratified Option D in direction (10 named grades you BECOME / 12 gates you CROSS). This asks for the explicit numerical yes.
Status: the mechanical half is already in the tree but unratified — commit b27da74 relabeled the registry prefix tier_N_→gate_N_ (cosmetic; the 12-position ladder was always there). Not done: your explicit yes, and one hard-line row (HL_0084) drifted to the gate index and now contradicts HL_0028/29/30 in the same registry.
Options.
Strongest objection (adversary) — conditions the ratification. Ratifying D as a bare "grade-6/gate-7 both canonical, done" would bless a live hard-line contradiction as intended design: HL_0028 ("Vril Sight at tier 6", grade index) and HL_0084 ("Inner Order Tiers 7-9 … Third Order Tiers 11-12", gate index worded as "Tiers") are both tagged canonical and numerically contradict each other about the same grade, in the same registry. So D must be conditioned on riders or it locks the contradiction.
Recommendation: ratify Option D, conditioned on:
canonical hard-line numeral edit, so it is yours, not a silent living-source edit.twelve_tier_quest_gates field (it says "tier" over gate rows) with a same-commit --emit-baseline; author the crosswalk table; run the Ch-15 / Epilogue / §248 label-*wording* alignment (Portal = gate 6 at Ch 14; Adeptus-Minor grade-6/gate-7 at Ch 15; Abyss = gate 10 before Magister Templi grade-9/gate-11); then land the Gate-6 and Gate-10 playable questlines.What I need from you: confirm Option D (or pick B/C); and rule R1 (HL_0084's numeral — grade-index vs gate-vocabulary). R2/R3 then self-apply. No care/reveal axis is engaged (design-layer systems numbering).
---
Question. May a named living people's general ancestral-spirit folk-category — the Rapa Nui aku-aku (CH_63 BE_0063_S3) and, by the same logic, the Jamaican duppy (CH_62 BE_0062_S1) — be depicted as family-forced-then-freed, or must it join the never-forced set with named deities and specific revered ancestral collectives (Pele, the huaka'i pō Nightmarchers)? This fixes where the sacredness line sits for "the returning dead of a living people."
Factual correction (verified in-repo — the flag was wrong): the flag claims the aku-aku was "dropped from the Ch-65 re-bound menagerie." It was not. What's applied is a *body-prose abstraction* (Ch-65 main narrative names only the least-sensitive members); the aku-aku (and duppy) are still enumerated in the Ch-65 sub-encounter anchor (line 65) and asset anchor (line 116). So "Option-C re-home" was a prose-softening, not a roster removal. Both CH_63 and CH_65 landed GO on care; the flag is advisory, non-blocking.
Options.
Strongest objection (adversary): the CVD's own closest ratified hard line — §17.1 Ch-57 (line 970) keeps the Rainbow Serpent *off the physical board entirely*, honored non-physically, not even present as a victim-to-free. An L1-only player who never reads the witness-depth L2/L3 gets the raw mechanic: "Rapa Nui ancestor-spirits wrenched into weapons; I fight through and free them" — a plausible desecration read of a devastated living people's dead.
Why C still holds (adversary confirms, +3 sharpenings): the same Ch-57 line that raises the objection *also splits the categories* — it protects the supreme/revered being (Rainbow Serpent, honored non-physically) while explicitly mandating a fought monster-boss drawn from "the tradition's own malevolent beings" even in the maximum-care Australia chapter. The aku-aku is a folk spirit-category (family/place spirits, some malevolent), not the supreme creator being — it falls on the CVD's own *playable* side, and the build's villain-forces / hero-frees-with-compassion frame is *gentler* than the fought monster the CVD already permits. Moving it to never-forced triggers the Care Doctrine's explicit ban (line 944: "care never means omission, reverence-gloss") and deletes the beat that dramatizes the 1862-63 atrocity — a care *loss*. The three sharpenings:
1. Rule the CLASS, not one chapter — any principle binds the Ch-59 Shona vadzimu/mhondoro (more explicitly venerated than the aku-aku) and the Ch-62 duppy identically.
2. Add the Ch-57-mirror guardrail — the forced aku-aku (and any Class-3 ancestral turned-guardian) must be rendered as the *folk spirit-category with malevolent/wronged members*, never the venerated/revered ancestral collective or a named supreme ancestor. That's the line that keeps it on the CVD-permitted playable side.
3. The duppy holds independently — its live axis is antisemitism (§11.5), not ancestral-desecration; it's built as the family's *own* foreclosure/displacement victims inside a dedicated firewall, pishtaco kept as the community's diagnostic lens. No change regardless of the aku-aku ruling.
What I need from you: where the sacredness line sits (Option C recommended — state the rule; keep the class forceable-then-freed with the Ch-57-mirror guardrail + the two aku-aku riders). If you instead rule move (B), the edits are larger than the flag states: re-tag CH_63 BE_0063_S3 + CH_62 BE_0062_S1, drop both from the Ch-65 roster (lines 65, 116), and resolve the Ch-59 vadzimu/mhondoro/njuzu consistency (reverse them too, or state the principled distinction that spares them).
Self-applies now (either ruling): the two aku-aku riders (a 1862-63 slave-raid non-re-enactment rider; an authorial Heyerdahl-"Aku-Aku"-appropriation flag — frame via Rapa Nui's own tradition); a one-line duppy emic-grounding note at CH_62; and finishing the Ch-65 factual reconciliation (either complete the roster-level drop or correct the "dropped from the menagerie" claim to "body-prose-abstracted only").
---
These are queued and grounded; I apply them the moment the gating ruling lands (or now where nothing gates them):
--emit-baseline), Circus Maximus chariot sub-rung, the Ch-65 light human-liberation callback, WS6 era-rhyme edges, retire the stale never-captured note; Tinku via the care-critic (and its Ch 51-vs-52 placement flagged); the Epilogue L2 loop after F4 (it must not lean on the tier-number).[POPULATE→] BE_ rows + the CH_19 Kanshah/[SRC:] nits, in one --emit-baseline pass.