CRITIC_L-R3-sacred-space-living-tradition.md

pipelines/CRITIC_L-R3-sacred-space-living-tradition.md

CRITIC PASS — L-R3 · sacred-space-and-living-tradition-adaptation

Fresh-context adversarial refutation. Read-only on C:\dev\humanity-forgotten and

C:\dev\Humanity\Humanity — nothing was edited or staged in either repo. Every verdict below was

re-derived by opening the cited file or re-running the enumeration in Python over the live CSVs; the

author's numbers were not trusted.

Draft under review: ...\realm_wave\L-R3-sacred-space-living-tradition_DRAFT.md

Unit mandate: verify the PER-REALM CARE TIERING TABLE both directions (an inflated tier is a defect

exactly as a missing one is), and confirm nine realms + fairy realm coverage.

---

HEADLINE — the findings body is strong; the gating table's care column does not survive

The draft's method is genuinely good and I want that on the record before the kills. **Every registry

enumeration I re-ran reproduced the author's numbers exactly**: 281 boss rows and the 15-value

care_tier vocabulary; 123 hard-line rows and the applies_to_high_care_chapter distribution

{none:107, Ch29|Ch42|Ch57:6, Ch57:5, Ch29|Ch57:4, Ch29|Ch42:1}; the 16/281 defeat_protected

fill confined to CH_02–CH_05; the per-node audit-only counts CH_66:1 / CH_67:4 / CH_68:22 /

CH_69:16 / CH_70:0 / CH_71:1 / CH_72:0 / CH_73:0 / CH_74:0; the region-row fills (fairy_realm 11/25,

the other nine 9/25). Every CVD and charter quotation I spot-checked is verbatim, including the

long §17.1 devil's-advocate sentence, "Care tiers add depth, never subtract content," "Deities are

equally real, portrayable, and usable as characters," the §15.4 consultation-flag deprecation, the

T1_Region_Page_Template L120-121 care_tier declaration, the charter's Panel A definition and its

"a guess with good lighting" clause. The citation discipline is real.

Then: the care_band column is built on a false premise and fails in both directions, the

draft's loudest evidentiary claim (the Duat "live contradiction") is a misreading of a sentence that

says the opposite, and one whole finding (F-17) was overtaken by a commit that landed the same day.

Four KILLS and six AMENDs follow, most of them on the gating output itself.

---

PART A — KILLS (decisive evidence quoted)

K-1 · KILL · care_band is an EXISTING gate-enforced six-value enum. The draft mints a colliding two-value one, and standard — assigned to 3 of its 11 rows — is not a legal value in it.

Draft §1.2: *"care_band ∈ {standard, elevated} — the RATIFIED enum, not widened. No maximum,

no open, no high, no prose."*

care_band is already a live field with a closed, gate-checked, six-value enum:

• docs/SPINE_SCHEMA_v3.md §3c: care_band {open|elevated|maximum|protected-elevated|antisemitism-guardrail|none}
• docs/SPINE_SCHEMA_v3.md §4 (Closed ENUMS): "care_band = §3c."
• harness/check_spine_graph.py L99-100: CARE_BANDS = {"open", "elevated", "maximum", "protected-elevated", "antisemitism-guardrail", "none"}
• harness/check_spine_graph.py L393-396: cb = FF.get("care_band"…); if cb and cb not in CARE_BANDS: E(f"…care_band '{cb}' not in enum …") — ERROR severity, and §6 of the schema records the gate as "BUILT and green," wired into run_gates.py as the spine_graph gate.
• harness/spinelib.py L337-338: care_band is a first-class FORK_FIELDS column.
• 270 occurrences across 199 files (ripgrep count).

standard is not in the enum. The draft assigns standard to rows 5 (Hades), 10 (fairy realm)

and 11 (Personal Dimension). Enumerated over build/spine_rows/*/forks.csv (90 built fork rows):

open 45, protected-elevated 21, elevated 13, maximum 7, antisemitism-guardrail 4 —

standard appears zero times in the built corpus.

Live typed care_band per realm vs the draft's table:

The draft's own §1.1 thesis is that the corpus collapses independent facts into one column. It then

does exactly that, onto a field name that is already taken, already gated, and already carries values

for eight of its own rows. The charter shares the defect — REALM_DESIGN_PROGRAM.md §3.3 writes

*"The CARE BAND — how the living community around a tradition is portrayed. Ratified. Two values,

standard and elevated"* — so the draft inherited the collision rather than inventing it. But L-R3

is the named authority on this output; catching it was the job.

Amended recommendation — and the charter itself supplies the reuse-first answer. The charter's

own board spec (§3.2) already names the field the art board reads: *"TWO badges read off the Zone

Catalog columns rather than re-derived per board — the ratified care_tier badge (standard or

elevated, driving re[view depth]…)"*. So the consuming surface is care_tier, not care_band.

**Rename the draft's column to care_tier, bind it to the ratified two-value enum at

T1_Region_Page_Template L120-121, and leave the gate-enforced six-value care_band untouched.**

The two then coexist without collision — care_band is the per-fork authoring register, care_tier

is the per-zone cultural-representation register. Zero new fields, zero gate churn, and K-2 dissolves

with it. What cannot ship is a second care_band with an incompatible vocabulary; this repo already

carries a recorded scar from exactly this class (CLAUDE.md known-issue 3: thread IDs in two encodings

across two registries).

K-2 · KILL · "OPEN care is not an enum value and is retired" — it is a legal enum value, and the corpus explicitly defends it as a real tier.

Rows 8 and 9 both override the spine with the reason *"The spine's OPEN care is not an enum value

and is retired."* Two independent refutations:

1. open is a first-class member of CARE_BANDS (K-1), gate-enforced, and the **most common value

in the built corpus** (45 of 90 fork rows).

2. T0_Chapter_Index.cultural_depiction_compliance, CH_73: *"OPEN care -- the Welsh Otherworld of

the Mabinogi, a treasured medieval literature of the living Welsh culture/language, honored on its

own terms (open != low care…"* — and CH_74: *"OPEN care with the LOUDEST anti-fringe firewall

of the whole road … (open != low care)."* The corpus anticipated this exact misreading and

wrote the rebuttal into the cell.

OPEN is a deliberate, defended, gate-legal value — not an unrated placeholder and not retired.

Rows 8 and 9 need re-reasoning, not a retirement note. (Their generation_class = living calls are

unaffected and stand — see PART C.)

K-3 · KILL · The Duat "live contradiction" (F-01's tail, and the whole of C-2) is a misquote produced by dropping "standard care," out of the sentence being cited.

Draft F-01: *"Separately BE_0069 (the Duat) reads standard while its spine heading reads

'elevated Egyptian duties' — a live contradiction inside the corpus."* Draft C-2: *"the live corpus

disagrees with itself: spine heading 'elevated Egyptian duties' vs BE_0069.care_tier = standard

… one of the two live cells must change."*

The actual heading, docs/spine/CH_69.md:

## Protected-chapter / living-culture framing (§17.1, standard care, elevated Egyptian + cross-cultural + anti-fringe duties)

Four live cells agree on standard; none disagree:

• spine heading (above);
• CH_69 body, twice: *"a CANONICAL HARD-LINE node … with STANDARD care, carrying an **ELEVATED

§17.1 duty**"*;

• T0_Chapter_Index CH_69: *"STANDARD care (a game-canon L3 realm) w/ ELEVATED Egyptian +

cross-cultural + anti-fringe duties"*;

• BE_0069.care_tier = standard — agrees with all three.

And the corpus states the tier-vs-duty separation explicitly, in docs/spine/CH_70.md:

*"the sibling Realm-Road mythic-underworld chapter CH_69 (the Duat) likewise self-describes as

carrying \"STANDARD care\" with \"an ELEVATED §17.1 duty,\" not protected-elevated."*

So canon already draws the very axis-separation §1.1 says the corpus is missing: the TIER is

standard, the DUTY is elevated. There is a genuine tension worth recording — the charter's §1.1

line reads *"Care: ELEVATED (ancestral with living descendants and active revival)"* and the v3 typed

care_band for CH_69 is elevated — but that is charter-and-v3 vs spine-and-both-registries,

the inverse of the framing the draft filed. C-2 as written would send the director to change the

wrong cell.

K-4 · KILL · F-17 is overtaken by the corpus. The realm aspect rows EXIST, and L-R3 is named in them as a claiming wave.

F-17 asserts: *"no realm aspect row exists, and under the QA program's aspect_id join contract the

realm rubrics report ROSTER-INCOMPLETE indefinitely — including R-A20, which this document is the

producer for. Nothing this lens returns can land in the join until the rows exist."*

docs/DESIGN_GAP_REGISTER.md at HEAD (working tree clean; git status --porcelain empty), §"v1.2 —

the ASPECT×LENS coverage matrix (the WAVE-0 fold, 2026-07-28)", L444-448:

*"THE REALM SET: R-A1 through R-A20 minted by reference — the roster, per-aspect teacher state

(3 taught / 4 partial / 13 teacherless) and definitions live in

docs/pipeline_review/REALM_ANALYSIS_LENS_GAPS_2026-07-27.md; the realm doctrine wave (L-R1 +

L-R2 + L-R3 + register-variety + corruption-as-condition) is the claiming wave for

R-A1/2/3/4/6/7a/9/11/12/13/14/15/18/20."*

Cell 14a in the same matrix reads CLAIMED-RUNNING (realm Wave 1). The commit is cf6e935 —

landed the same day the draft was written. The draft's §0 control row (*"file reads at 28,142

chars; care×2, R-A×1, realm×0"*) is a stale read of v1.1; the file now reads 35,494 chars with

R-A×6, realm×8, aspect×6, ASPECT×2 (I re-counted). Finding is FALSE as of HEAD and its

"zero-token, now" recommendation is already DONE.

Method note worth carrying into the wave. This is a distinct failure mode from the one the

program's search law guards. The draft's control proved the *matcher* could fire; it did not prove

the *read* was current. On a shared tree with concurrent waves landing, a positive control needs a

freshness leg — re-stat the file or check git log -1 -- <path> before minting an absence claim

against a file another lane owns.

---

PART B — AMENDS (finding survives; verdict, scope, count or reasoning is corrected)

A-1 · AMEND · Rows 1-4 are UNDISCLOSED care-tier INFLATIONS against an explicitly stated canon value — the exact defect §1.5 is written to guard against.

§1.5 is a good-faith devil's-advocate pass refusing four inflations. The table then commits four of

its own, silently. Ch 66-69 each state their tier explicitly and identically, and it is

standard:

• CH_66 body: *"a CANONICAL HARD-LINE node … with STANDARD care (a game-canon L3 realm, no living

culture) but carrying an ELEVATED anti-fringe duty"*; registry cell: *"STANDARD care … w/

ELEVATED anti-fringe + reveal duties."*

• CH_67 body: *"with STANDARD care, carrying an ELEVATED §17.1 duty"*
• CH_68 body: *"with STANDARD care, carrying an ELEVATED §17.1 duty (Tiamat, Apsu, Marduk…)"*
• CH_69: as K-3.

Row 1's own citation refutes row 1's value. The draft quotes CH_66's *"a §17.1-adjacent CARE

matter because the pseudo-archaeology it excludes is documented hyperdiffusionist RACISM"* — which I

verified verbatim at CH_66 offset 42975, correctly attributed to the Protected-chapter section. But

the sentence it opens reads: *"Ch 66 depicts no living culture … the chapter carries **no §17.1

living-community obligations in the ordinary sense; its elevated duty** is the anti-fringe

Atlantis firewall."* The node performs the tier/duty split the draft's row then collapses.

The draft nowhere states that it is overriding an explicit spine value on these four rows. Contrast

its handling of Ch 72, where the de-escalation is flagged, reasoned in §1.5, and routed to the

director as C-3. The same disclosure is owed in the inflating direction. Under the ruled

calibration (*"care-tier inflation is itself a defect, because the timid option in a rated-M

action-adventure fantasy RPG is usually the wrong one"* — CVD §17.1, verified verbatim), an

undisclosed four-row inflation in the gating deliverable is the more serious of the two errors: it

silently raises review depth and Panel-A lane restriction on three realms whose own nodes ruled

otherwise. Row 4 (Duat) is defensible on the charter's Care: ELEVATED line and should be carried as

CONTESTED; rows 1-3 return to standard unless the draft argues the override on the record.

Note the shape this produces: **ten of eleven rows read elevated, and the one that does not is

wrong in the other direction** (row 5, A-2). A tiering table where one value covers 10/11 rows has

stopped tiering.

A-2 · AMEND · Row 5 (Hades, standard) reverses a live RESOLVED typing the draft did not surface.

docs/spine/CH_70.md: *"The care_band typing call (elevated, not protected-elevated) — RESOLVED

(v3 conversion, judgment call) … FORK_CH70_A and the §3b site rows are typed care_band elevated,

matching CH_69's own precedent and the absence of a living combat-protected community here

[SRC: T0_Hard_Lines @ HL_0003]."* Confirmed in built data: build/spine_rows/CH_70/forks.csv →

elevated.

The draft's row-5 reason instead says Ch 70 is *"the only road node whose spine heading carries no

tier word at all."* That is TRUE of the heading (re-derived: CH_70's heading reads "§17.1,

deities-real, honored-adversary, and reverence-for-the-ineffable" — no tier lexeme) and of the

registry cell (opens "DEITIES-REAL / S17.1"). But the node HAS a ruled value in a RESOLVED block, and

the table silently reverses it. The charter also reads *"Care: classical Greek, standard"* (§1.1), so

this is a genuine two-source conflict that belongs in PART 4 as a contested item, not a clean row.

A-3 · AMEND · Coverage mandate is MET, but four charter-roster realm surfaces have no row — including the highest-care surface in the whole roster.

**Mandate check: the table carries Ch 66-74 (nine road realms) + the fairy realm (row 10) + the

Personal Dimension (row 11) + an explicit RLM_0000 non-row note. The nine-realms-plus-fairy-realm

requirement is SATISFIED.**

But the draft justifies row 11 as *"included so the schema's provenance tooth has a declared exempt

row rather than a silent skip"* — and that reasoning applies with equal or greater force to the four

surfaces REALM_DESIGN_PROGRAM.md §1.3 lists beside the Personal Dimension, none of which appear:

• THE DREAM TRADITION — charter §1.3: *"The clearest un-taken realm slot in the corpus, and the

one with the sharpest care constraints on its most obvious substrate (the Australian Dreaming sits

under Ch 57's maximum care tier and must not be reached for casually)."* This is the single

highest-care realm surface in the roster, and the care tiering table has no row for it. A fan-out

reaching for it finds no rule — precisely the failure mode source_corpus_state was minted to

prevent, on the surface where it costs most.

• THE ASTRAL PLANE — charter: D as a realm, A as a mechanic; structural spine of Ch 38/44/46/58.
• THE HOLLOW — designed and unratified; Josh expanded it into a content pillar 2026-07-27.
• RIFT INTERIORS — blank BY DOCTRINE; needs a declared n/a row for the same reason RLM_0000 got

its non-row note.

Add four rows; three can be declared-exempt one-liners. The Dream Tradition needs a real call.

A-4 · AMEND · F-01's "five of the nine road bosses carry off-enum values" is arithmetically wrong; the real count is three.

Re-enumerated over all 281 rows. Off-enum among BE_0066–BE_0074: BE_0072 = maximum,

BE_0073 = open, BE_0074 = open — three. The draft's own parenthetical proves it

(*"BE_0071 elevated OK; BE_0072 maximum; BE_0073/BE_0074 open"*) and then adds

BE_0075*/BE_0076/BE_0077, which are not road realms (Ch 75-77 are the fairy realm and

finale). Everything else in F-01 reproduces exactly: 15 distinct values, standard 198 / elevated

51 / high 12 / standard_elevated 5 / maximum 2 / open 2, plus nine distinct prose values —

though "nine one-off" is loose, since standard-with-the-war-register occurs 3× (11 prose rows

across 9 distinct strings). Finding SURVIVES as WEAKER; fix the count.

Consequential rider: with K-1 in hand, maximum and open are not off-enum against the

care_band vocabulary — only against the region-page care_tier. F-01's normalisation fix must name

its target column unambiguously, or a well-meant "normalise to two values" pass destroys valid data

on BE_0072/BE_0073/BE_0074 and the whole Ch 75-77 block.

A-5 · AMEND · F-10 (Annwn acquisition gap) is not a fresh find — the charter already records it, positive-controlled, with its repair wave named.

The gap is REAL. REALM_DESIGN_PROGRAM.md §1.1, Ch 73: *"Annwn is MISSING ENTIRELY from the RCM's

Acquisition Priority Master List — POSITIVE-CONTROLLED AND CONFIRMED, and the control is recorded

because an absence-claim without a search that can match is this repo's most-repeated defect. The

list carries a per-chapter block for Ch 66, 67, 68, 69, 70, 71, 72 and then jumps straight to Ch 74

… which is precisely the layer Wave 3 repairs."* The draft reproduces this independently and

correctly (its Wave-3 owner assignment matches) but presents it as this lens's discovery without

citing the charter. Verdict class should read DESIGNED-UNBUILT (known — charter §1.1, Wave 3),

not MISSING. The source_corpus_state column it motivates is genuinely new and stands.

A-6 · AMEND · F-18 under-reports the missing-section count by one; its own control number caught it.

F-18: *"CH_39 and CH_40 have no protected-chapter section at all (positive-controlled: the same

regex returns headings for 76 of 79 nodes)."* 76 of 79 implies three missing; the draft names

two. Re-derived: the nodes with no ## Protected-chapter… heading are CH_39, CH_40 and CH_41

(all three contain "17.1" in body text, so the section is absent, not the subject — the draft's own

disambiguation, extended). Everything else in F-18 verifies: CH_70 carries no tier word, and CH_29

and CH_42 both read only ## Protected-chapter combat framing (ruling 5) with no tier lexeme, while

CH_50 reads (§17.1, elevated care) and CH_57 (§17.1, maximum tier).

---

PART C — SURVIVING FINDINGS (independently verified, no change)

• F-02 · MISSING · SURVIVES. Re-enumerated: T0_Chapter_Index (79 rows / 52 cols) and

T0_Region_Index (76 rows / 25 cols) carry no column whose name contains "care". The region

pages under _source/02_Tier_2_Region_Pages/ are 12 Earth regions (angkor_khmer, bali,

central_africa_congo, ethiopia, flores_island, rift_valley, south_africa, south_india, sri_lanka,

sumatra_java, swahili_coast, west_africa) — no realm page exists. The care register does live only

in prose. Verdict and HIGH priority correct.

• F-03 · WEAKER · SURVIVES exactly as stated. Distribution reproduces byte-for-byte. Not one row

scopes to a realm chapter. HL_0111's rule_text does enumerate Ch 29/42/57 by name (SFX

cultural-authenticity discipline); HL_0110's is class-scoped (*"living-religion synthetic-voice

DEFAULT"*). The draft's split of which survives the scope test is correct, and the reuse-first fix

(widen HL_0111's scope rather than mint a realm hard line) is the right rail.

• F-04 · WEAKER (mis-citation) · SURVIVES; the HL_0003 quote is exact. HL_0003: *"The faithful

community and its living tradition are never the story antagonist … This is collective,

framing-level protection of the community as a whole; it does not render individual members

mechanically un-attackable."* A community-framing rule that says nothing about deity instantiation

and whose closing clause points the other way. The audit-only → HL_0003 attribution in CH_69 is a

genuine mis-citation of the class this repo has caught before.

• F-05 · MISSING · SURVIVES, and it is the draft's best finding. The anti-timidity call is

correct and I would strengthen it: reading audit-only as "do not render" would put a depopulated

Hall of Two Truths under a panel header the charter defines as *"What the source tradition itself

says the place looks like"* (verified verbatim, §3.2) — a false statement about an ancestral

tradition in the one place the pipeline promises truth. CVD backs the draft verbatim: *"Care tiers

add depth, never subtract content. The maximum-depth chapters (Ch 29 Sámi, Ch 42 Haiti, Ch 57

Australia) and elevated-care chapters carry more weight, deeper grounding, and stricter

authenticity, never avoidance. High-care governs cultural authenticity only; it never lowers the

action, combat, or exploration [ceiling]."* The deity_depiction (art) / instantiation_class

(play) split is reuse-first and lands on the ruleset row the charter already specifies. **Act on

this one first.**

• F-06 · WEAKER · SURVIVES; every count reproduced exactly (CH_66:1, CH_67:4, CH_68:22, CH_69:16,

CH_70:0, CH_71:1, CH_72:0, CH_73:0, CH_74:0). The inverted-gradient observation is sound and the

CVD licenses the permissive direction verbatim: *"Deities are equally real, portrayable, and usable

as characters — a good deity may appear as a disguised human quest-giver or a rescuer

(rescue-and-re-encounter) … the only firewall is that no deity-name sits on a mortal NPC and no

revered or real figure is cast as the villain."*

• F-07 · WEAKER · SURVIVES. My broader regex returns CH_67:8 (draft said 7), CH_77:1, CH_15:2,

and zero on every other node CH_66-CH_76. The substantive claim holds: on a road of nine realms

populated with honored deities, sovereigns and functionaries, not one grants the player anything.

Routing the fix to the charter's existing EXPLOIT slot on the signature-law row, bounded by

D-RR.5, is properly reuse-first.

• F-08 · DESIGNED-UNBUILT · SURVIVES, and is correctly called the cheapest high-value item.

defeat_protected and has_nonkill_path are each non-blank on **exactly 16 of 281 rows, all

CH_02–CH_05**. BE_0005_S3 "Naga Padoha, the bound earth-shaker (Batak…)" reads

defeat_protected = TRUE / has_nonkill_path = TRUE — the semantics exist and have already been

used for a tradition's bound being. Every BE_0066–BE_0074 row reads '' on both. Sharp

instances spot-verified: BE_0067 Louhi REDUCE/strike, both blank (against CVD §17.1

constitutional text that she is never slain); BE_0070 Cerberus PERCEIVE;PACIFY/pass, blank;

BE_0074 Níðhöggr verb re-root, blank; BE_0068_S1 REDUCE/strike, blank; BE_0072

PART_BREAK;FREE/release, blank.

• F-11 · DESIGNED-UNBUILT (known) · SURVIVES. T0_Region_Index mythic_realm rows do carry

pohljar, tiamarath, maatherion as live region_id primary keys. The draft correctly credits

the prior record rather than minting it fresh, and the **care consequence it adds is genuinely

new** — region_id is the region page's path key per T1_Region_Page_Template L25, so the Duat's

board directory, art bible and rights ledger would key on a CVD-retired occult-adjacent coinage.

Re-key before the first Duat board is the right sequencing call.

• F-12 · MISSING · SURVIVES. Verified against _source/02_Tier_2_Region_Pages/flores_island.md:

all seven use_class values are present in the live page (SUBSTRATE, ESOTERIC-PRIMARY,

AUTHORIAL-REBUTTAL, REFERENCE, TONE, DUPLICATE, FRINGE-SKIP) and INSIDER occurs zero times.

No value records authorship standpoint. Adding one value on an existing rail rather than a lane is

the reuse-first shape.

• F-13 · DIVERGENT-BY-DESIGN · SURVIVES and is correctly classed. CVD §15.4 verified verbatim:

*"The cascade-era flag system using bracketed tags such as the verification flag, the cultural

consultation flag, and the bridge flag is deprecated as of CVD lock."* Refusing to recommend a

consultation apparatus on a solo AI-factory build is the recommend-what-can-exist discipline, not

timidity — the translatable half is kept in F-12/F-14.

• F-14 · WEAKER · SURVIVES; the CVD §17.9 quote is exact (*"Per-chapter investigatable substrate

content (journal, Grimoire link, inscription, language fragment, or cultural-tradition content) is

required"*). Ruling that living rows surface a named attributed source in the tradition's own

framing costs an authoring convention, not a system. The Pentiment read — diegetic apparatus rather

than a citation UI, tied to the ruled natural-voice doctrine — is correct and correctly marked

COVERED with a bounded extension.

• F-15 · COVERED (confirming) · SURVIVES. Charter §1.1 Ch 72 matches the Raji shape line for line

(*"deities honored and never villainized; the protagonist echoes the Indra-role, honoring and never

supplanting"*). The "stop re-litigating this timidly" framing is the correct calibration.

• F-16 · WEAKER (charter amendment) · SURVIVES; both quotes verified verbatim. §3.3: *"Lane G is

permitted on Panel A only where the realm is wholly invented. Atlantis and the fairy realm

qualify."* §3.2: *"a CITATION LINE naming the substrate rows behind it, where a citation that

cannot resolve is a defect and an empty one means the option is not an accurate depiction at all

but a guess with good lighting."* The hole is real — lane legality is not sourcing licence — and

the one-clause fix is minimal.

• F-19 · COVERED + bounded extension · SURVIVES. CVD §17.9 verified verbatim: *"The surface track

is self-contained. The action-adventure RPG arc reads complete on the surface track without

engaging the investigatable-depth or canonical-truth tracks."* Naming Ch 66's INSCRIPTION BINDS

MATTER as the road's harmony-doctrine showcase is a real, bounded recommendation.

• F-20 · DESIGNED-UNBUILT (known) · SURVIVES; fills reproduced exactly. fairy_realm 11/25;

atlantis/pohljar/tiamarath/maatherion/hades/xibalba/naraka_meru/annwn/yggdrasil

all 9/25; page_status = dimensional and protected_terrain_ref = '' on all ten. **The care-

specific rider is the important half and it is correct**: because the ratified care_tier is

*"derived from the protected flag"* and protected_terrain_ref is empty on every realm row, the

ratified derivation would emit standard for Xibalba and for Naraka and Meru. Explicit values are

genuinely load-bearing here.

• F-21 · DESIGNED-UNBUILT · SURVIVES, verified by direct existence check. ABSENT:

harness/read_boards.py, docs/art_boards/, docs/art_bibles/, harness/check_realm_ruleset.py,

registries/T0_Realm_Ruleset_Registry. PRESENT: harness/read_captures.py,

harness/check_care_scope.py. Its framing — these outputs are inputs to a mint, not corrections to

a built thing — should be preserved in the landing note.

• The generation_class column · SURVIVES INTACT, and it is the charter's actual named ask.

REALM_DESIGN_PROGRAM.md §1: *"the authority that settles each realm's value is **L-R3's named

output**"*; §3.3 leaves *"The Apsu; Pohjola and Hades pending L-R3"* (historical) and *"Annwn and

Yggdrasil pending L-R3"* (living). The draft settles all of them and **every assignment is

consistent with the charter's own pending placements**: invented (Atlantis, fairy realm, Personal

Dimension); historical (Pohjola, the Apsu, Hades); living (the Duat, Xibalba, Naraka and Meru,

Annwn, Yggdrasil). Zero unsettled remain, so the strict default fires nowhere. **This is the

column that actually unblocks the art wave, and it is sound.** C-3 (Annwn) is correctly closed to

living on Welsh-language-and-culture grounds, and the closure is well-argued.

• §1.4's Mesoamerican scope note · SURVIVES. Verified: T0_Chapter_Index CH_71 reads *"elevated

care -- a LIVING people (the K'iche' Maya of highland Guatemala) and a LIVING sacred text"*, the

CH_71 heading reads *"§17.1 elevated care — a living people and a living sacred text"*, and

BE_0071.care_tier = elevated. Xibalba is genuinely coherent across spine + chapter registry +

boss registry, and it is also the one row where the draft's value matches the live typed

care_band. Correctly recorded as a COVERED positive rather than inflated into a gap.

• Comparator-title claims (outside repo verification, checked against general knowledge). Never

Alone's community co-development with Iñupiat elders and its documentary-video unlocks; AC Origins

*Curse of the Pharaohs* staging the Duat and Aaru with the Egyptian divine beings at monumental

scale, with Discovery Tour shipped as a separate curator-narrated layer; Raji (Nodding Heads, an

Indian studio) with deities narrating and asuras/rakshasas as the fought class; Mulaka (Lienzo,

Rarámuri) with demigods as summonable powers and *sukurúame* as the enemy class; Okami's Celestial

Brush as the tradition's own visual grammar made the core verb; Pentiment's marginalia,

manuscript frame and typeface-by-speaker. All accurate as stated. The AC Origins precedent in

F-05 — separation by LAYER, not by emptying the game — is the correct reading and is the strongest

single argument in the draft.

---

PART D — DEVIL'S-ADVOCATE-AGAINST-TIMIDITY PASS

Run against the R-17+ bar (CLAUDE.md content bar; care = weight/authenticity, never omission; the

timid option is usually the wrong one).

• No defanged recommendation found in the draft's prose. It argues consistently in the bold

direction: it refuses the CULTURAL_PROTECTED promotion for Ch 71/72 on the correct ground that it

would import Ch 57's content floors and *"defang two of the road's best fights"* (and the ground is

right — CULTURAL_PROTECTED is exactly the four chapters CH_29/42/50/57, verified, all of which have

a living community on stage); it refuses the consultation lane; it rules the Duat's iconography

renderable at full spectacle; it holds the Vritra death-blow fork offered; it insists the Lords

of Xibalba render *"at full marquee-antagonist weight — never horror-schlock demon-parade, never

caricatured 'evil Maya gods'"* while keeping HL_0007's no-staged-bloodletting line, which is the

right place to draw it (HL_0007 verified: *"Registered and protected cultural property is

referenced not reproduced"*).

• The one inversion, and it is the thing to fix. The draft's timidity failure is not in its

RECOMMENDATIONS — it is in its DATA (A-1). It de-escalated the single tier it flagged and escalated

four it did not. A tiering table that resolves 10 of 11 rows to elevated has performed care

inflation at the schema level while arguing against it in prose. Under the ruled calibration that

is a defect, and it is the one thing the director should fix before this lands.

• F-06's restraint is correct, not timid. Declining to tighten Hades/Annwn/Yggdrasil and instead

asking whether Ch 68/69 are tighter than doctrine requires is the doctrine-aligned direction.

C-1's decision to HOLD Ch 69's instantiation rule on a structural ground is well-reasoned and

independently supported by charter §1.1: *"Apep carries the fight so the Architect never lifts a

hand."* Not timidity.

• One care-inflation risk the draft creates and should retract. Rows 1-3 at elevated would, via

R1, restrict Panel A on Atlantis — a wholly invented realm the draft itself rules Lane-G-legal.

The row's generation_class saves it, but only because the two columns are read together. If the

care column ships inflated and a downstream tooth reads it alone, the draft's own Rule R1 bites the

one realm it explicitly exempts.

---

PART E — RE-LITIGATION / PRE-REGISTERED-DIVERGENCE CHECK

• No finding re-opens a DIVERGENT-BY-DESIGN entry. F-13 correctly *files* one rather than

re-litigating it. The no-scoreboard and markerless/diegetic-navigation guards are untouched.

• Charter contradiction C-4 (Atlantis: generation-legal AND elevated-duty) is already closed in

REALM_DESIGN_PROGRAM.md §3.3 as a schema fix — *"not a disagreement between two analyses, both of

which are right, but a schema defect in the charter's own keying"* — and the draft's row 1 cites it

as confirmed rather than re-opening it. Correct. The draft's own C-4 (a fifth hard_line_status

value) is a different item, correctly recorded as closed-so-it-is-not-reopened.

• The draft's C-5 (Ch 7 possibly under-scoped) is correctly routed OUT of realm scope. Cell

verified: T0_Chapter_Index CH_07 = *"standard care; Tamil/Malayali/Siddha/Kalaripayattu/

Meenakshi/Murugan per primary-source…"*, hard_line_status = NONE. The inversion against CH_72's

*"MAXIMUM care — Hinduism is a LIVING major world religion (~1.2B adherents)"* is real.

• Rider on C-3/F-09. With K-1 in hand, F-09's premise that Ch 72 *"asserts an enum value that

does not exist"* fails — maximum is a legal care_band value and CH_72's built fork rows carry

it. The de-escalation argument must be re-made on the CVD/HL_0009 leg alone, which does stand on

its own: CVD verbatim names *"the maximum-depth chapters (Ch 29 Sámi, Ch 42 Haiti, Ch 57

Australia)"* and HL_0009 verbatim names the same three. That is a real argument; it is just no

longer the one the draft wrote.

---

CLOSING VERDICT

Killed: 4 · Survived: 16 · Amended: 6 · Contested: 4

• KILLED — K-1 (§1.2's two-value care_band premise and the three standard values built on

it), K-2 (the "OPEN is not an enum value / is retired" reasoning carrying rows 8 and 9), K-3 (the

Duat "live contradiction" — F-01's tail and the whole of C-2 as filed), K-4 (F-17 entire — the

realm aspect rows exist at HEAD and name L-R3 as a claiming wave).

• SURVIVED — F-02, F-03, F-04, F-05, F-06, F-07, F-08, F-11, F-12, F-13, F-14, F-15, F-16, F-19,

F-20, F-21, plus the generation_class column and the §1.4 Mesoamerican positive.

• AMENDED — A-1 (rows 1-4 undisclosed inflation vs an explicit standard care), A-2 (row 5 vs

CH_70's RESOLVED care_band elevated), A-3 (four charter §1.3 surfaces have no row, incl. the

Dream Tradition), A-4 (F-01 count 5 → 3, plus the normalisation-target rider), A-5 (F-10 MISSING →

DESIGNED-UNBUILT/known, charter §1.1, Wave 3), A-6 (F-18 misses CH_41; its own 76-of-79 control

implied three).

• CONTESTED for the director — (i) which vocabulary the realm ruleset's care column adopts:

rename to the ratified care_tier (my recommendation — it is the field the charter's own board

spec already reads) or adopt the six-value care_band; (ii) the Duat's true tier, now a

charter-plus-v3 vs spine-plus-both-registries conflict, the inverse of what C-2 filed; (iii) Ch 70

standard (charter §1.1) vs elevated (CH_70's own RESOLVED v3 typing); (iv) Ch 72's

de-escalation, which must be re-argued on the CVD/HL_0009 leg alone.

LANDING RECOMMENDATION — GO WITH FIXES (blocking on the care column only)

Land PARTS 2, 3 and 4 substantially as written. The findings body is strong, the citations are real,

and every registry enumeration reproduced exactly. Act on F-05 and F-08 first — F-05 is the

highest-value anti-timidity ruling in the wave and directly protects the Duat board from shipping a

depopulated Hall of Two Truths under an "accurate" header; F-08 is a nine-row data fill against an

existing schema with no new systems, and it closes the gap where CVD §17.1 constitutional text (Louhi

never slain) has no data cell backing it.

Do NOT land §1.2's care_band column as the gating instruction for the art fan-out. Ship the

table with generation_class, source_corpus_state and deity_depiction — the three columns that

are sound, new, and actually unblock the wave — and hold the care column for a director pass that

resolves K-1/K-2 and A-1/A-2. Shipping it as filed would push a value that is illegal in a

gate-checked field, silently inflate three realms whose own nodes ruled standard, and silently

deflate two the corpus typed higher — which is the failure this unit was commissioned to prevent, in

both directions at once.

Add the four §1.3 rows (A-3) before the table is called complete; the Dream Tradition in particular

must not reach an art fan-out with no rule attached to it.

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