RECASCADE_PUNCHLIST.md

pipelines/RECASCADE_PUNCHLIST.md

Re-cascade Punch-List (Section 3 tracker) — verified 2026-07-13

CANON SUBORDINATION — this document is PROPOSAL-TIER: it serves canon and never outranks it.
The canon: the CVD · the T1 foundation docs · the T0 registries (registries/) · the spine
(docs/spine/CH_*.md) · the region pages (_source/02_Tier_2_Region_Pages/). Authority order: docs/DOC_MAP.md § 0.
Canon served (scanned from this document's own citations — widen it by hand where it is thin):
CVD §12 · T1_Combat · T1_Vril · T0_Boss_Encounter_Registry · T0_Trade_Registry
READ THAT CANON FIRST — open it and derive from it before you build anything from this document.
If this document disagrees with canon, CANON WINS and this document is the defect — fix the
document, never the canon. Nothing here is applied until it is ratified into canon.

From the recascade_gap_audit workflow (wf_07cff43b-28d, 6 agents, every status file-read-grounded). This is the authoritative Section-3 execution tracker — the connections-pass §5 work × the built spine. Execute PENDING/PARTIAL items via /spine-chapter + reveal/care re-verify, landing each; mark DONE here. Canon-forks (canon_fork=true) are routed to DECISIONS_PENDING_JOSH — never invented.

environment-overfence

_Audited all 9 stream items against the built docs/spine/CH files, the Trade_Registry CSV, and T1_Vril. Verdict: the over-fence fixes are almost entirely UNBUILT. Ch 5, Ch 28, and Ch 29 all still carry the exact fenced framing the pass flags (Ch 5 "never an assassination"; Ch 28 "without ever taking the kill"; Ch 29 routes ALL combat through the environmental protocol + audit-trail with NO Stallu and NO honest L1 direct action — the flagship "defanged pure-witness"). Ch 65 is the one over-fence t_

Section-3 re-cascade

_Audited the six named items against the built spine (file-read per item). One is DONE-by-canon (TL-06: the 22nd familiar slot is NOT an orphan — it is the Child Familiar, homed at CH_58 Truly-Good + a path-variable finale resolution; CH_68 explicitly authors no bond under the D-EMB-68 re-cascade, so the proposal's Ch-68 landing is stale and would fork canon — canon_fork flagged). Two high-priority gaps drive the re-cascade: TL-08 (the Ch-18 Litan promise is fully PLANTED at CH_18 and mid-arc rec_

CLEAN-RUNGS BOUNDARY (2026-07-14 overnight checkpoint)

The clean, low-care-risk, non-fork content is LANDED (8 nodes: dragons Ch 15/23/31/61/64 + the Ch-69 TL-08 CULMINATION; over-fence Ch 5/28). The REMAINING re-cascade content is triaged for the handling it needs — do NOT batch-author it at depth:

dragon-lineage

_The flagship dragon-lineage is landed in its ancient middle and its ratified hear-rung, but ORPHANED at both ends and at its two designated payoffs. DONE (6): Ch 17 Tiamat (BE_0017, echoes to Ch 68), Ch 18 Litan (D-DRAGON-18 anchor, recurrence-seed planted), Ch 24 Jörmungandr, Ch 25 Illuyanka (both staged + recognition present), and Ch 68 Mušḫuššu (ratified D-EMB-68 hear/restraint rung with the recognition wired). PARTIAL (4): Ch 19 (fought + recognition present but still a perceive-forward sub-_

Section-3 era-rhymes

_The connective era-rhyme LAYER is essentially unbuilt: no CH_*.md file contains any explicit rhyme/ladder wiring (grep for era_rhyme / contest ladder / prestige ladder / combat-contest across docs/spine = 0 hits inside CH_* files; only TASK_13C_BUILD_PLAN.md carries it, marked PENDING) — matching the doc's own note that the Cross-Cultural Link Graph has ZERO era-rhyme edges. What DOES exist is the local set-pieces at most nodes. Per chain: ER-1 PARTIAL (caci Ch3 / kalari Ch7 / holmgang Ch24 / Ro_

Section-3 monster-class-lines

_Audited all four fair-game monster class-lines against the built docs/spine/CH_*.md via direct grep+read. Every item is PARTIAL: each has its anchor/debut or apex node built, but the RECURRING chain beats the pass names are frequently absent or present only as an L2 cross-link. Cross-cutting pattern: ancient base-build nodes carry the debut but not the pass's specific entity (Nho Lobo, Coyote, nittaewo, Enkidu, Basajaun, Stallu, Stone Giants, Zipacna/Cabracan all absent), and the -rc endgame nod_

deity-patron

_Audited the §194-201 DEITY_PATRON section, which lists exactly SIX chains (D1-D6) — there is no D7/D8 in the doc (the task's "D1-D8" over-counts). Split D2 into three actionable items for the re-cascade (8 items total). Verdict: the ancient-arc and endgame-authored beats are largely DONE — D2's existing storm-god nodes (Ch 7/18/25/26/72), D1's Ch 19 bond + Ch 31 Sufi home + Ch 77 parable, D4's Ch 55 apu/mallku + Ch 65 re-freed menagerie, D6's Ch 73 Arawn, D5's Ch 39 Mami Wata, and D3's Ch 12/23/_

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