SLICE-corruption-as-condition_DRAFT.md

pipelines/SLICE-corruption-as-condition_DRAFT.md

SLICE — CORRUPTION-AS-CONDITION (the extracted doctrine slice of L-R7 fading-court-realm)

Wave 1 doctrine lens, read-only audit, 2026-07-28. Unit: how a shipped title frames corruption as a

CONDITION the realm suffers, never an essence the folk ARE — Hollow Knight (Hallownest), The Legend

of Zelda: Twilight Princess (the Twilight Realm and its exiled sovereign), Ori and the Will of the

Wisps (the Decay/renewal loop). Aspects audited: R-A14, R-A12, R-A15, R-A6.

Written for a SCHEMA DESIGNER. Every finding names the field, enum, tooth, rubric or row it becomes,

and the existing system it lands on. Nothing here authors canon; everything is proposal-tier and

mints later under its own fresh-context critic and the full gate ritual.

Register per CVD §17.14. Verdict classes per the wave runbook: COVERED / DESIGNED-UNBUILT / WEAKER /

MISSING / DIVERGENT-BY-DESIGN. Owner = the lane that fixes it. Priority = player-impact × solo+AI

feasibility, honest.

---

0. HEADLINE — the six things that carry the slice

• THE GUARDRAIL IS DECLARED AT EVERY LAYER AND EXPRESSED AT NONE. HL_0109 / HL_0114 /

§17.1 are bound in the Ch-75 header, the hard-line binding, the boss block and six beat

reveal-notes. Not one of them resolves to a quantity, a field, a verb or a win-state a machine or a

critic can read. That is precisely the Law-3 failure the harmony doctrine exists to catch

(REALM_DESIGN_PROGRAM.md §2.2 LAW 3), applied to the single sharpest care line in the game.

• THE TWO BLIGHTS HAVE OPPOSITE TOPOLOGY, AND CANON ALREADY SAYS SO. The Hollow occupies a VACATED

substrate gap and grows a body that was never alive. The fairy-realm corruption creates no body at

all — it saturates an OCCUPIED, living substrate and TURNS what is already standing there. Same

substance (negative vril), inverse topology. Minting that as one enum is the whole

must-not-blur requirement, made checkable. §3.2, finding F-4.

• THE GRIEF GEOGRAPHY IS NOT CORRUPTION AND A SINGLE-FIELD SCHEMA WILL EAT IT. T3_Core §6.5/§6.6

carry an explicit ATTRIBUTION LOCK with a drift warning attached, and CH_75 prose rules

over-purging the grief-country "the worst thing her power could do." Three typed deformation

classes, not one. F-5 — the highest-priority finding in the slice.

• THE PERCEPTION INSTRUMENT SATURATES. The player's vril-sight reads CONCENTRATION against a depleted

baseline; the fairy realm is anchor density on every site row. CH75_B02's core verb is "tell the

two wounds apart" and the chapter names no instrument that still works. The fix is nearly free and

canon nearly states it: in the source realm, perception inverts from concentration to STILLNESS vs

FLOW. F-17.

• THE CHARTER'S OWN PREMISE IS HALF-WRONG. "A fading folk" imports Hallownest's absolute ruin. Our

realm is at the VRIL CEILING and wounded only RELATIVE TO ITS OWN REMEMBERED HEIGHT — which is a

harder art problem, is why the Prologue is built last and read first, and demands a before/after

reference panel on every fairy-realm concept board. F-1.

• ONE BLOCKER IS ALREADY DEAD. HL_0080's ninth-sitting amendment removed the Hollow class from the

non-damage protocol entirely and states the protocol "never applies to a mythological monster,

deity-champion, or malevolent being" — which is exactly the Ch-75 champion class. The Hollow

integration record still carries JB-1 as open and sequences worklist X-9 behind it. F-12.

---

1. WHAT THE THREE TITLES ACTUALLY TEACH ON THIS AXIS

Compressed to the transferable rule. These are analytical readings and carry no citation burden; the

CANON side of every finding below is cited.

1.1 Hollow Knight — the infection is a WEATHER WITH A SOURCE, and the folk are its victims

• The infection has a single named origin (a sealed thing whose containment failed) and a single

unmistakable sensory signature — one orange light — that reads identically in a corpse, a wall, a

boss and a pool. The player learns the signature before learning the story. CORRUPTION IS TAUGHT AS

A SUBSTANCE, NOT AS A FACTION.

• The infected bugs cannot be saved, and the game is HONEST AND MOURNFUL about that rather than

silent. The condition-not-essence reading is carried instead by the un-infected individuals you

meet — the wanderer, the hunter, the sibling — each of whom is a person with a life, met one at a

time, so the player's model of "the folk" is built from persons and only then contrasted with the

turned.

• The kingdom's ruin is EXCAVATED. There is no "before" screen; decline is legible from frame one

because the architecture is a ruin and the folk are absent. This is the analogy's biggest hidden

divergence from ours — see F-1.

• The sovereign is ABSENT and the game withholds judgement on him for dozens of hours. A ruined king

you assemble from evidence.

1.2 Twilight Princess — the FOUR-OBJECT SEPARATION, which is the guardrail's cleanest test

• The realm (the Twilight Realm), the people (the Twili — exiled, not evil, never the antagonist),

the usurper (Zant — one of the people, individually culpable, a chosen direction not a heritage),

and the power behind (Ganondorf — external, and faceless for most of the running time). Four

objects, never collapsed.

• The twilight covering Hyrule is a CONDITION laid over a place. It is lifted, not defeated. The

people under it are restored, not killed. The rightful sovereign is restored to her own throne.

• The one thing TP does that we cannot: it lets the player BE inside the condition (the wolf form,

the twilight vision) so the condition is experienced from within rather than described from

without. That is a legibility technique, not a story move, and it is directly reusable — see F-17.

1.3 Ori and the Will of the Wisps — DECAY AS A NAMED AXIS, and grief with a griever

• The Decay is authored as a degradation ALONG A NAMED AXIS: colour drains toward one hue, growth

forms go brittle and geometric, sound thins. The eye reads "this was lovely" and "this is wrong" in

the same frame. Beauty-in-decay is a rendering rule, not a mood.

• The Decay's cause is a GRIEF WITH A GRIEVER — a specific loss, held by a specific being, that

deformed the land. The resolution is restoration of what was lost, not the killing of a villain,

and the game's last movement is consent-shaped rather than combat-shaped.

• The renewal loop is PLAYABLE and INCREMENTAL: the player restores, the world visibly answers, and

the answering is the reward. Decay and renewal share one visual vocabulary read in two directions.

1.4 The one-line synthesis the doctrine needs

All three titles make the condition READABLE BEFORE IT IS EXPLAINED, give it a SINGLE SENSORY

SIGNATURE independent of biome, and keep the AFFLICTED and the AFFLICTION as separate objects the

player can point at separately. A guardrail that lives only in a doc protects nothing; a guardrail

that lives in a signature, a verb and a win-state protects itself.

---

2. FINDINGS

Each carries verdict · owner · wave · priority, and a reuse-first recommendation naming the existing

system it lands on.

F-1 · The lens charter's own premise imports the wrong kind of decline

**Verdict WEAKER · owner spec-doc (charter) + P5-factory (art bible) · wave 1 (charter) / slice-end

(art) · priority HIGH — slice-relevant**

The L-R7 charter reads "a sovereign non-human court in decline… a fading folk"

(docs/proposals/REALM_DESIGN_PROGRAM.md §4.2 L1156-1162; same wording at

docs/pipeline_review/REALM_ANALYSIS_LENS_GAPS_2026-07-27.md §4 L323-334). Against live canon that

is half true and the false half is the one that drives concept art.

CITED CURRENT STATE. docs/spine/CH_75.md L9 types the biome as "a sovereign, vril-luminous

otherworld now a war-country"; L25 (Body prose) reads "a country lit from inside, the air itself a

substance so rich she feels her whole rebuilt power settle into it and stand at its full height for

the first time since she was a child falling through a rift"; every one of the four typed site rows

(L63, L65, L67, L69) carries vril_density anchor. REALM_DESIGN_PROGRAM §1.2 grades Ch 75 "Vril

CEILING." AND, on the other side: _source/03_Tier_3_Characters/T3_Core_Characters [ACTIVE v1.0].md

§6.6 L605 — "The father has been ruling a wounded realm alone" — and L603 — "the father's specific

grief over the protagonist's absence and the realm's decline."

So the realm's decline is REAL and it is RELATIVE TO ITSELF. Against Earth the realm is still the

ceiling. Hallownest is absolutely fallen and legible as fallen from the first screen, with no "before"

to compare against. Ours is legible ONLY against the Prologue's height — which is exactly the third

fact the whole program rests on (REALM_DESIGN_PROGRAM §0.2: the Prologue is "the only scene that

shows the fairy realm's physics as ORDINARY… that scene cannot be authored until the nine partial

views exist"). An artist handed "fading folk" will render Hallownest and contradict the ceiling.

RECOMMENDATION, reuse-first. (a) Amend the L-R7 charter line before the craft remainder runs: "a

sovereign realm wounded relative to its own remembered height, at undiminished density" — a

one-line edit, zero tokens. (b) The art-concept board at REALM_DESIGN_PROGRAM §3.2 gains a FOURTH

REFERENCE PANEL for fairy-realm units only: the Prologue-height counterpart of the same view,

rendered from the same palette, shown beside the three choice panels. This is an extension of an

existing board format, not a new pipeline. (c) The realm-ruleset row records the comparison as data —

see F-16's two-state row recommendation.

F-2 · The guardrail is declared everywhere and expressed nowhere — no fairy-realm win-state is typed as restoration

Verdict WEAKER · owner spec-doc (doctrine) → schema-data · wave 2 · priority HIGH

CITED CURRENT STATE. CH_75.md binds the guardrail in five places (L3 provenance, L11 operational

type, L12 canonical_hard_line_flag, L14 hard_line_binding, L75 boss block) and in six beat

reveal-notes (B02, B05, B06, B07, B09, B10). Every binding is PROSE. Meanwhile the typed win-states

of the four ratified champions (L78-L82) are: the eye BLINDED, the host GROUNDED, the court

UN-THRONED, the advance BROKEN. Not one typed field distinguishes a being that was ALWAYS dark from a

being that was TURNED — and CH75_B07 L126 states the distinction explicitly in prose: "the

corruption did not invade the aristocracy, it TURNED it."

Why this matters against the teachers: all three ship a restoration the player performs. TP lifts the

twilight and restores the sovereign. Ori reverses the Decay and the land visibly answers. Hollow

Knight is the counter-case and is instructive precisely because it is EXPLICIT that the infected

cannot be saved and mourns it out loud. We currently have neither a restoration nor an authored

mourning-of-the-impossibility. Under HL_0114 (live T0_Hard_Lines: "Negative vril is not

personified evil. It is a vibrational state that reinforces self-loss"), a turned court that can only

ever be driven back reads, at the SURFACE where the guardrail actually has to work, as an essence.

The good news, and it moderates the finding: the restoration register is ALREADY IN THE PROSE.

BE_0075_S2 (L79) wins by "the host GROUNDED and turned back west toward the rest it was denied,

sent back toward its sleep, never exterminated — the honored dead protected, THE WIN IS REST."

BE_0075_S3 (L80) wins by "a sovereignty unseated, never a race destroyed." Those are restoration-

register wins. They are simply not TYPED, so no tooth and no critic rubric can see them.

RECOMMENDATION, reuse-first — a TYPING fix, not a content change. Add two fields to the boss/encounter

row family (they belong on the encounter row, not the realm row, because they vary per champion):

• affliction_state ∈ {native_dark, turned, uncorrupted} — was this being ever clean?
• resolution_register ∈ {driven_back, rested, unseated, restored, ended} — what the win DID to it.

Then one arithmetic tooth on harness/check_realm_ruleset.py: T-RLM-CONDITION — every encounter

whose affliction_state = turned must carry a resolution_register from the restoration set

(rested | unseated | restored), never ended. That converts "the corruption is a condition, not an

essence" from authorial care into a gate. And one critic rubric on the existing RB-RLM-CARE family:

from the fairy-realm frames alone, name which defeated beings were always dark and which were turned —

a critic who cannot tell them apart is a guardrail failure at the surface.

Nothing about the four ratified wins changes. The words already say it; this makes the machine able

to check that a later pass has not quietly dropped it.

F-3 · "Corruption" is already a HOLLOW-locus word AND a fairy-realm-agent word — the mint will harden the collision

**Verdict MISSING (vocabulary discipline) · owner schema-data + spec-doc · wave 2, BEFORE the mint ·

priority HIGH — free now, expensive after**

CITED CURRENT STATE. The Hollow's canonical spawn loci include CORRUPTION_SEAM

(docs/pipeline_review/HOLLOW_EXPANSION_INTEGRATION_2026-07-27.md §4.1 L652: "the procedural spawn

table is chapter-scoped and VELHEIM_EXTRACTION_SCAR and CORRUPTION_SEAM are absent below Ch 39"; the

underlying row is docs/proposals/systems/creature-system.md L244 FU.2). Simultaneously CH_75.md

L29 uses the same word as the fairy realm's own agent: "its corruption seeped into the realm's own

substrate like rot climbing a lattice." The two blights therefore already share their principal noun,

and T0_Realm_Ruleset_Registry is about to mint a field family around exactly this concept.

Canon has ALREADY given the Hollow its own distinct noun and nobody has noticed. Live T0_Hard_Lines

HL_0080 (ninth-sitting amendment) reads: "the full loop is find the cause, enter the rift, clear the

hollow CONTAMINATION and the Hollow itself."

RECOMMENDATION, reuse-first — LOCK THE PAIR, both words already canonical:

• CONTAMINATION = the Hollow's environmental blight. Authority: HL_0080 amended text.
• CORRUPTION = the fairy realm's substrate agent, the House's reach. Authority: CH_75 L29, L14.
• CORRUPTION_SEAM is recorded as THE ONE DELIBERATE OVERLAP, with a schema note, because it is an

existing ratified locus token and renaming it costs more than documenting it.

Arm it on the tooth that already exists: T-RLM-CARE is specified as a FIXED-STRING scan

(REALM_DESIGN_PROGRAM §2.7 — "a FIXED-STRING scan for retired coinages… never an escaped pattern").

Extend its word list two ways: no T0_Hollow_Codex row may use "corruption" as the agent noun, and no

RLM_0010 field may use "contamination." Fixed-string, no regex, per the repo's own

a-search-that-cannot-match rule.

F-4 · The two blights have OPPOSITE TOPOLOGY — this is the harmonization the slice was commissioned to produce

**Verdict DESIGNED-UNBUILT (both halves designed, the distinction unwritten) · owner schema-data ·

wave 2 mint · priority HIGH — the slice's primary deliverable**

CITED CURRENT STATE, both sides.

• HOLLOW. REALM_DESIGN_PROGRAM §1.3: "negative vril congealed into flesh, occupying a VACATED

substrate-gap and wearing the eroded shape of something the depletion took."

HOLLOW_EXPANSION_INTEGRATION §3.2 phase 3: "IT IS NOT DEATH AND THERE IS NO CORPSE — the body was

never alive." §3.5: the worn shape is "the eroded silhouette of what that place LOST."

• FAIRY-REALM CORRUPTION. CH_75.md L29: "its corruption seeped into the realm's own substrate like

rot climbing a lattice, and where it settled it WOKE AND TURNED the realm's OWN dark mythology

against the rest." CH75_B07 L126: it "TURNED" an intact aristocracy. It grows NO body. Every

entity on the Ch-75 front pre-existed the corruption.

So: the Hollow needs an ABSENCE to fill; the fairy corruption needs a PRESENCE to sour. One is

vacancy-fill, the other is occupancy-saturation. Same substance under HL_0114; inverse topology.

This is not an aesthetic distinction — it is the reason the two systems can sit adjacent without

blurring, and it is derivable entirely from cited canon.

RECOMMENDATION — MINT IT AS ONE ENUM, consumed by two registries.

blight_topology ∈ { vacancy_fill , occupancy_saturation , none }

• On T0_Realm_Ruleset_Registry (per realm row): RLM_0000 human-world baseline =

vacancy_fill (Earth is the depleted substrate; the Hollow is its native blight). RLM_0010

fairy realm = occupancy_saturation. Road realms default none until a row asserts otherwise.

• On the T0_Hollow_Codex singular class row: blight_topology = vacancy_fill, non-nullable.
• Tooth T-RLM-TOPOLOGY (rides check_realm_ruleset.py, one more member of an existing family):

no realm row may declare vacancy_fill while its vril_density_class is anchor, because a

saturated substrate has no vacancy to fill. This single arithmetic assertion is what mechanically

keeps a Hollow out of the fairy realm — see F-11 — and it needs no judgement call at authoring time.

• Must-fire fixture: an RLM_0010 copy mutated to vacancy_fill. Must-not-fire: the real row.

F-5 · The GRIEF GEOGRAPHY must be typed as NOT-CORRUPTION, or the schema silently breaks a canonical attribution lock

**Verdict MISSING (schema risk against an explicit drift warning) · owner schema-data · wave 2 mint ·

priority HIGHEST IN THE SLICE**

CITED CURRENT STATE. T3_Core_Characters §6.5 L593: the King's sustained grief produced vril that is

"heavy, crystallized, dense with accumulated emotion rather than flowing freely." §6.5 L595 + §6.6

L609 carry the ATTRIBUTION LOCK with its own drift warning quoted here because the tier doc flags it

as a magnet: "The grief geography has ONE cause: the child taken by the rift, and the decades of that

particular absence… A later authoring pass that reaches for a second source has drifted the canon and

is corrected against this line." And CH_75 L27 rules the player-facing consequence: "that is not a

corruption to purge, it is love in a terrible shape… over-purging here — scouring away the shapes his

missing her built — would be the worst thing her power could do." T3_Core §6.5 L593 adds the gate:

"the father must consent."

THE RISK, stated concretely for the schema designer. The grief-crystal is the VISUALLY DOMINANT

deformation of the fairy realm — it is what the region looks like. Any realm row carrying a single

corruption / blight / affliction field WILL absorb it, because an author populating one field

will populate it with the thing they can see. The moment that happens, the grief-country becomes

purge-eligible in data, and the attribution lock is broken in the one direction the tier doc warned

about.

RECOMMENDATION — THREE TYPED DEFORMATION CLASSES ON RLM_0010, never one. Repeating sub-row group,

mirroring the schema's existing metaphysical_laws and taboo_constraints groups so the parser and

the fidelity harness need no new shape:

realm_deformations[]:
  deformation_id
  deformation_class ∈ { grief_crystallization , substrate_corruption , native_dark_risen }
  cause_ref            (single-valued; FK)
  purge_eligible       (bool)
  consent_gated        (bool)
  meter_eligible       (bool)   -- writes the content completion ledger, see F-11
  physical_expression  (mandatory, Law 3 — resolves to a real quantity)
  care_ref

Populated for the fairy realm:

Tooth T-RLM-GRIEFLOCK: on any row carrying a grief_crystallization deformation, assert

cause_ref is single-valued, purge_eligible = FALSE, and consent_gated = TRUE. Must-fire fixture:

a copy with a second cause appended — which is EXACTLY the drift T3_Core §6.6 L609 predicts, so the

fixture is the canon's own warning turned into a test. This is the cheapest possible protection for

the most explicitly flagged drift risk in the fairy fold.

Note for the doctrine author: native_dark_risen being purge_eligible = FALSE is not timidity. It

is HL_0121 (live T0_Hard_Lines: "a myth's own dragon, chaos-serpent, sea-beast, undead, ogre, or

demon is a boss to be fought, never routed around or reduced to a containment puzzle") stated in

data. The tradition's own monsters are FOUGHT, not cured. Only the TURNED are restoration-eligible.

That split is the whole doctrine in two rows.

F-6 · The mechanism by which the corruption took hold in a saturating realm is UNSTATED, and Law 3 cannot be satisfied without it

**Verdict MISSING (doctrine gap) · owner spec-doc (harmony doctrine) → schema-data · wave 2 ·

priority HIGH · CONTESTED — see §5 C-1**

CITED CURRENT STATE. The fairy realm's own native law is written in the Prologue's body prose

(docs/spine/CH_PROLOGUE.md, Body prose): "within his reach the air brightens to the realm's own

saturation and ANYTHING THAT SHOULD NOT BE THERE SIMPLY THINS AND FAILS, not struck down but unable

to hold against so much fullness." That is a saturation-expels-negation law, and it is the realm's

signature property at its height. Yet at Ch 75 the realm is still at anchor density on every site row

(CH_75 L63-L70) and the corruption is nonetheless established throughout the substrate (L29).

A realm whose native law expels negation, in which negation is established, requires a stated reason.

REALM_DESIGN_PROGRAM §2.2 LAW 3 makes this mandatory, not optional: "Every metaphysical law must

name the physical quantity it writes… If the answer to 'what does this law physically do' is 'it

glows,' the law is an overlay and the row fails." "The corruption seeped in" names no quantity.

Three alternatives are deep-dived at §5 C-1 with a recommendation and its strongest objection. The

finding here is only that the gap is real, that it is load-bearing for the schema (the mechanism IS

the physical_expression value of the substrate_corruption deformation row), and that it must be

settled before RLM_0010 is authored rather than after.

F-7 · The four-object separation — we PASS Twilight Princess's test, and the pass should be recorded so nobody "fixes" it

Verdict COVERED · owner QA loop (rubric) · wave 2 · priority MEDIUM · zero cost

TP's guardrail architecture keeps four objects separate and never collapses them: the realm, the

people, the usurper (one of the people, individually culpable), and the power behind (external,

faceless for most of the running time).

CITED CURRENT STATE — we have all four, and they are already separated in the built chapter. The

REALM: CH_75 L7/L9. The PEOPLE: the King's court and defender-nobles, the childhood best friend

"alive and grown and one of the realm's own" (L27), the honored dead the player is required to

protect (L79). The USURPER-EQUIVALENT: the Pitch-Court under the Sunless Jarl — the realm's OWN

nobility, turned, un-throned rather than destroyed (L80, CH75_B07 L123-126), which is Zant's exact

structural position. The POWER BEHIND: the House of Velheim, explicitly and repeatedly FACELESS —

"the family's hand is in all of it and has no face in any of it… the reach is a condition, not a

marched people" (L29), reinforced at L83's reveal-binding ("no Velheim operative is fought and the

patriarch is not named").

RECOMMENDATION — record it as a passing structure so a later enrichment pass does not helpfully give

the reach a face at Ch 75 (which would break HL_0035 reveal timing AND the guardrail in one move).

Add to RB-RLM-CARE (the existing rubric, REALM_DESIGN_PROGRAM §2.7): "From the fairy-realm frames

alone, name the four objects — the realm, its folk, the turned, the power behind. A critic who

collapses folk-and-turned, or turned-and-power-behind, is reporting a guardrail failure at the

surface." Advisory tier, as all critic rubrics are. Zero new machinery.

F-8 · R-A12 — the fairy realm has THREE character rows for an entire sovereign civilization

**Verdict DESIGNED-UNBUILT · owner schema-data + P5-factory · wave slice-end · priority HIGH —

slice-relevant**

CITED CURRENT STATE, positive-controlled. registries/T0_Character_Index [ACTIVE v1.1] carries 164

rows. A scan of every field for fairy or elven returns four: CHAR_0001

(protagonist_elven_royal_child), CHAR_0005 (protagonist_father_fairy_realm_sovereign),

CHAR_0164 (the King's consort and the protagonist's mother), plus CHAR_0059, an unrelated Kilwa

Sufi row that matched on an incidental token. So: three rows for the realm that opens and closes the

game.

POSITIVE CONTROL for the absence claim: a scan for friend returns exactly 3 rows — CHAR_0002

(primary_human_companion), CHAR_0019 and CHAR_0021 (both Manggarai NPCs) — and a control scan

for healer returns 5, court returns 8. The matcher demonstrably matches. The CHILDHOOD BEST

FRIEND — a Ch-1 player selection (T3_Core §2.2 Selection 2) with a ratified Ch-75 reunion beat

(CH75_B03, docs/spine/CH_75.md L97-101) and a designed downstream consequence at Ch 13 — has NO

character row. Neither does the Sunless Jarl, the Griever-at-the-Head or the Kindler at the Wall;

those exist only as BOSS_PERSONAS material behind BE_0075_S1..S5.

WHY IT MATTERS ON THIS AXIS. Hollow Knight's entire method for making a fading folk land is that you

meet the un-turned ONE AT A TIME, as persons with lives, before and between the turned. That is the

same mechanism our own ratified ENTITY_PERSONA_SYSTEM prescribes (every entity a 13-field persona).

Today the fairy realm's folk are legible only as a court in aggregate and a war. Without persons, the

"condition, not essence" reading has nothing to attach to — because a condition is only visibly a

condition when you have met someone it did NOT take.

RECOMMENDATION, reuse-first. (a) The fairy-realm folk cast is recorded as a NAMED BLANK on the

RLM_0010 row (the schema already has a named-blank convention in the roster axis). (b) A P5-factory

persona batch at slice-end, seeded from the existing 13-field persona schema — no new schema. (c) The

childhood best friend gets a T0_Character_Index row in the SAME pass that wires the Ch-1 selections,

since the selection already writes state the Ch-75 beat reads. (d) Minimum viable count for the

guardrail to work at the surface: at least one un-turned member of the SAME court the Pitch-Court

came from, met before CH75_B07, so the player has a face for "these are the same people."

F-9 · R-A15 — the art hooks carry a CEILING law and no DECAY law, and both freeze together

**Verdict MISSING · owner schema-data (wave 2) + P5-factory · priority HIGH — gated by the DR-2

freeze**

CITED CURRENT STATE. The realm-ruleset's art-direction hook family is palette_law,

silhouette_law, impossible_architecture_budget, signature_phenomenon, plus the three

concept-choice slots (REALM_DESIGN_PROGRAM §2.3). None is a decay law. Separately the presentation

charter amendment has LANDED declaring the realms ceiling-setting art surfaces (§5.1, quoting

COMPARATOR_LENS_PROGRAM WAVE P1-C verbatim). So the ceiling is registered and the degradation is

not.

Ori's transferable rule: decay is BEAUTY DEGRADED ALONG A NAMED AXIS — one hue the colour drains

toward, one geometric transformation the growth-forms undergo, one thinning the sound performs — so

the frame says "this was lovely" and "this is wrong" simultaneously. Hollow Knight's is the same idea

executed as a single unmistakable infection-orange that reads against every biome. Both are RULES,

authored once, applied everywhere. Neither is a mood note.

This is the exact instrument F-1 says our realm needs, because our decline is legible only by

comparison.

RECOMMENDATION, reuse-first — ONE new field in an EXISTING family, not a new art doc:

decay_law  -- the named axis along which THIS realm's own beauty degrades:
              the hue the palette drains toward, the form-transform, the acoustic thinning.
              Written in the environment-grammar micro-grammar, same parser as palette_law.

Plus: the fairy-realm board's fourth reference panel (F-1) is generated from the Prologue-height

palette, so the degradation axis is visible in one glance rather than argued in prose. And

RB-RLM-PROVENANCE's sibling rubric gains one line: shown a fairy-realm frame, the critic states

what the place looked like BEFORE — if it cannot, decay_law has failed on the art side even where

the data passes.

TIMING IS THE FINDING'S TEETH: decay_law is an art-contract input, and the DR-2 tiered-asset request

contract freeze is the same freeze the presentation lens gates. A realm tier sized without a decay

axis buys one palette per realm and then needs two.

F-10 · R-A6 — the fairy fold's grief is a DIFFERENT register from the five death realms', and no register row claims it

**Verdict MISSING · owner spec-doc · wave 1-2 (rides the register-variety slice) · priority

MEDIUM-HIGH · zero new lens**

CITED CURRENT STATE. The register-variety slice riding this same wave is scoped explicitly to the

five DEATH realms — "what makes Hades warm, Xibalba adversarial, Annwn seductive-and-hospitable,

Naraka moral-architectural, the Duat exact and grave" (REALM_DESIGN_PROGRAM §4.2 L1119-1124) — and

its title-set (Spiritfarer · Grim Fandango · Edith Finch · Hades) is a death-realm set. The fairy

fold's grief is not death-grief: it is a LIVING father's decades-long grief for a LIVING child, whose

canonical resolution is neither combat nor purge but CONSENT (T3_Core §6.5 L593: "the father must

consent"; CH_75 L27: over-purging is "the worst thing her power could do").

That register — grief-without-death, consent-gated, restraint-verbed — is the emotional spine of

three of the game's four most important nodes (Ch 75 opener, Ch 76 Phase 2, the Epilogue) and no

register row anywhere claims it.

RECOMMENDATION, reuse-first — extend the register-variety slice's named output table by exactly ONE

row rather than minting anything: the fairy fold's register, named, with its verb (restraint), its

gate (consent), and its forbidden verb (purge). Dual-list ORI into that slice for this row

specifically: Ori's Decay is a grief-condition with a named griever, and its final movement resolves

by restoration-and-consent rather than by a kill, which is the closest shipped analog to the

grief-country and to the Ch-76 father encounter's Truly-Good variant (T3_Core §6.6.1: "This path

requires no combat"). Cost: two lines in a table the slice is already producing.

F-11 · The Hollow's REALM ledger axis reaches the fairy fold by construction, and nobody has scoped it

**Verdict MISSING (scope gap with a live collision) · owner spec-doc → schema-data · wave 2 ·

priority HIGH · CONTESTED — see §5 C-2**

CITED CURRENT STATE. HOLLOW_EXPANSION_INTEGRATION §2.1 mints `ledger_axis ∈ {RIFT | AFFLICTION |

REALM}`. §1.1 (axis 1, REALM-TRAVERSAL CLEANSING) budgets Hollow density per realm node and defines a

DEFERRED YIELD that banks power and releases it "at the ruled climb points (Ch 72-74) and the CEILING

(Ch 75)." §2.4 states "REALM TRAVERSAL: budgeted per realm node against the Pattern A terrace

clauses." The fairy fold is a realm. Nothing in either document says whether Ch 75-77 is inside or

outside Hollow placement — so on the face of the specs, it is inside.

If a Hollow can stand in the fairy realm, the two blights share a frame at the one place the

antisemitism guardrail is sharpest, and every distinction F-3 and F-4 draw has to survive a player

looking at both at once.

RECOMMENDATION — rule the fairy fold OUT of Hollow PLACEMENT on canon grounds, not taste, and rule its

own substrate work IN to the ledger:

• OUT of placement, mechanically enforced by F-4's T-RLM-TOPOLOGY: a Hollow requires a vacated

substrate gap; the fairy realm is vril_density anchor on every site row (CH_75 L63-L70), so

there is no vacancy to occupy. The exclusion falls out of the physics rather than being asserted.

• IN to the ledger: CH75_B08's anchor-site re-attunement ("purge while you restore, defend while

you channel", CH_75 L127-131) writes the REALM ledger axis as SUBSTRATE cleansing — WITHOUT

being typed as Hollow cleansing, and without touching the champions or the grief-country

(F-5's meter_eligible column already encodes exactly this three-way split).

• The deferred-yield arithmetic is unaffected: axis 1 already banks yield and releases at the Ch-75

ceiling, which is where the fairy realm's own re-attunement sits anyway.

F-12 · HL_0080's ninth-sitting amendment has ALREADY closed JB-1, and it clears the fairy-realm champions by its own text

**Verdict COVERED (with a stale-doc flag) · owner spec-doc (supersession pass) · wave 0-1, zero

tokens · priority HIGH — it unblocks a named worklist item**

CITED CURRENT STATE, quoted from the LIVE registry row (registries/T0_Hard_Lines [ACTIVE v0.2],

HL_0080.rule_text): "Scope AMENDED (Josh RULED 2026-07-27, ninth sitting): this non-damage protocol

governs ONLY the sacred-site atmospheric echo class… THE HOLLOW CLASS IS REMOVED from this protocol's

scope entirely -- Hollows are DEFEATED… It never applies to a mythological monster, deity-champion, or

malevolent being, which are fully-fought damage-based staged boss encounters per the §17.1

honored-adversary (Louhi) rule."

Against that live text: HOLLOW_EXPANSION_INTEGRATION §2.6 (the EIGHTH sitting) still runs an

"INTERIM DIRECTOR INTERPRETATION," still carries the scope ambiguity to Josh as JB-1, and still

sequences worklist item X-9 (the BLIGHT / CONTAIN_BLIGHT mint) behind that resolution: "X-9 lands

AFTER JB-1 resolves, or the mint hardens the ambiguity into the registries."

TWO CONSEQUENCES for this slice:

• The fairy-realm champion tier is CLEARED by HL_0080's own text. Every Ch-75 champion is

either the tradition's own malevolent being or a turned noble fought as one (CH_75 L75 types the

faces as "the care-clean malevolent-being class… the exact class as the Ch-74 Níðhöggr and the

Ch-69 Apep"). The non-damage protocol explicitly never applies to them. No cross-dependency remains.

• JB-1 is dead and X-9 is unblocked. The supersession pass should close it against the live row rather

than sending a resolved question to Josh — which is the exact inversion the eighth sitting's own

critique flagged in the other direction.

Method note: this is a live-row read, not a doc read, per the standing "trust content, not labels"

rule. The doc is stale; the registry is current.

F-13 · The one doc that actually holds the fading-folk substrate is on PRE-v3 chapter numbering throughout

**Verdict WEAKER (staleness with a build consequence) · owner spec-doc / Wave 3 world-repair ·

priority MEDIUM · zero tokens**

CITED CURRENT STATE. docs/proposals/FINALE_FAIRY_ENRICHMENT.md §2 headings read "Ch 74 — Cassius

Velheim", "Ch 75 — The Elven King", "Ch 76 — the Approach", "Ch 77 — the Revelation." The live v3 fold

is Ch 74 Yggdrasil / Ch 75 The Realm at War / Ch 76 The Two Courts / Ch 77 The Waterfall

(docs/spine/CH_74.md … CH_77.md headers). T3_Core_Characters §6.6 L599 carries an explicit

displacement note for exactly this and names the re-key as an open follow-up, while §6.5 L593 still

says the grief geography is "what the protagonist encounters at Ch 70" and §6.1 L549 still routes the

Realm War to "Ch 71-73" and the Father Encounter to "Ch 75."

WHY IT MATTERS HERE SPECIFICALLY. FINALE_FAIRY_ENRICHMENT §3 is the ONLY place in the corpus holding

the fading-realm L2 substrate this slice's axis depends on — "The fading/withdrawing realm: 'the good

people are going' (centuries-old folk melancholy); Tolkien's long-defeat/fading/eucatastrophe

(literary, echo-only)" — and it sits under stale headings, in the doc a fairy-realm concept board will

read. This repo's own recorded failure mode is that a stale reference in a source doc makes later

agents hallucinate.

RECOMMENDATION — add the fairy-fold re-key to the Wave-3 world-repair punchlist alongside the four

stale Ch-69 World-Tree artifacts already enumerated (REALM_DESIGN_PROGRAM §5.1). Deterministic,

zero model budget. It should land BEFORE the slice-end fairy build, not after.

F-14 · The Hollow Knight analogy is closer than the charter says in one place and false in another; both bound the art prompts

**Verdict DIVERGENT-BY-DESIGN (record the split; do not close it) · owner spec-doc (art bible) ·

wave slice-end · priority HIGH — a per-prompt bound, cheap now, a regenerated wave later**

CLOSER THAN THE CHARTER SAYS. Hallownest's infection originates in a SOVEREIGN'S containment failing.

Ours has the same shape at one remove: the King's PRIMARY FUNCTION is sealing (T3_Core §6.4: "Rift

Sealing. The King's primary function… He has done this thousands of times"), the Prologue stages the

first seal as PROOF that he always seals it (CH_PROLOGUE entry header: "the first rift sealed (the

PROOF that the King always seals it)"), and the arc's founding wound is the one breach he could not

reach in time. That structural rhyme is a gift and the charter does not name it.

FALSE, AND SHARPLY. Hallownest's king is ABSENT, unaccountable, and judged in retrospect from

evidence. Ours is PRESENT, honored, canonically NOT the villain (T3_Core §6.6 L605: "The father is

not the villain of this chapter. He is a parent who lost their child and ran a civilization through

decades of that loss"), and canonically never resentful (§6.2 L557: "He never held resentment against

the child… no blame in him and none arriving in the years that followed"). The excavated-ruin register

— a kingdom you read as evidence, a sovereign you convict — is available for the LAND and FORBIDDEN

for the KING.

RECOMMENDATION — state it as a two-column rule in the art bible so every concept prompt inherits it

without a critic having to catch it after the image exists:

This costs one table in a document that is being written anyway and it is the cheapest possible

ordering — bounding a prompt is free, regenerating a realm's art costs a wave.

F-15 · The fairy realm's best-looking state is its QUIETEST one, and the asset budget is being sized against its war

Verdict DESIGNED-UNBUILT · owner P5-factory (DR-2 contract input) · priority HIGH — pre-freeze

CITED CURRENT STATE. CH_75's thirteen beats resolve to combat ×6, character ×4, discovery ×1,

vril_management ×1, transformation ×1, intensity PEAK (CH_75 L153). Ch 76 is a hall

(CH_76 entry header: "the King's own hall"). Ch 77 is a compressed approach and a waterfall

(REALM_DESIGN_PROGRAM §1.2). So the fairy realm is, across its three main nodes, experienced almost

entirely under fire.

All three teachers place their fading realm's best art in long UNOPPOSED stretches — that is where

the player actually looks. This is NOT a missing-content finding, because canon already designed the

quiet realm: the Epilogue IS "the post-reveal traversal of the realm (healed or not, per path)"

(FINALE_FAIRY_ENRICHMENT §2, Epilogue L1) and is graded intensity VALLEY

(REALM_DESIGN_PROGRAM §1.2). The Prologue is nine-tenths splendour and service

(CH_PROLOGUE entry header: "its first nine-tenths are splendour, mastery and service, and the cost

arrives at the end").

THE FINDING IS AN ASSET-SIZING ONE. If the fairy realm's art budget is sized against Ch 75's war, the

realm's two most beautiful states — the Prologue at height and the Epilogue restored — inherit a tier

sized for a battlefield. And per F-1 those two states are ALSO the comparison the whole decline

depends on being legible against.

RECOMMENDATION, reuse-first — the DR-2 tiered-asset request contract sizes the fairy realm against its

UNOPPOSED nodes (Prologue height, Epilogue restored) and treats the Ch-75 war as a state overlay on

that base, not as the base. This is an input to a contract already being authored under a lens already

scheduled (presentation-craft-anim-audio, P1-C), and it must land before that freeze.

F-16 · The fairy realm has ONE stub region row for two different environments sharing a name

Verdict DESIGNED-UNBUILT · owner schema-data · wave 3 · priority HIGH

CITED CURRENT STATE, live registry. registries/T0_Region_Index [ACTIVE v1.2], row fairy_realm:

region_name = Fairy Realm, chapters = Prologue, Ch 1, Ch 75-77, Epilogue, `modern_country = N/A

(dimensional), page_status = dimensional, env_profile_status = STUB, node_kind = story_anchor`,

last_updated = 2026-05-02. Eleven populated fields. Compare the sibling yggdrasil row, which at

least carries node_kind = mythic_realm and a 2026-07-12 timestamp. REALM_DESIGN_PROGRAM §1.2

independently records the same blank: "no vril site row exists for the fairy realm at the Prologue;

region row fairy_realm 11 of 25 fields."

One stub row is being asked to carry the realm at its height (Prologue, Ch 1), the realm wounded and

at war (Ch 75-76), and the realm after (Epilogue). Those are not one environment. F-1's before/after

requirement cannot be satisfied by a row that cannot express the difference.

RECOMMENDATION — either TWO region rows (fairy_realm_height / fairy_realm_wounded) or one row

carrying an explicit state axis that the zone catalog can read. The decision is row-count, not

tooling; the apply vector is the already-ruled single sanctioned writer,

harness/apply_zone_catalog_columns.py --populate-empty (REALM_DESIGN_PROGRAM §5.1 / §7), never a

hand edit. Recommend the STATE-AXIS form over two rows, because two rows would fork every FK that

currently resolves to fairy_realm and the arc's own framing is one place seen at three times.

F-17 · The player's perception instrument SATURATES in the fairy realm, so the chapter's own core verb has no instrument

**Verdict MISSING (legibility gap) · owner spec-doc (doctrine) → schema-data (RLM_0010) · wave 2 ·

priority HIGHEST — most load-bearing unbuilt piece in the slice, and nearly free**

CITED CURRENT STATE. The player's vril perception is a CONTRAST instrument calibrated against a

depleted world: T1_Vril §9 grants Outer-Order perception of "vril concentrations, recharge sites,

and atmospheric density variation" (quoted at HOLLOW_EXPANSION_INTEGRATION §1.3, which builds the

Hollow's entire visibility law on exactly this: "A Hollow at a natural deadzone is a vril-density

anomaly standing up, so reading a drained place as wrong is precisely the Outer-Order capability").

Now put that instrument in the fairy realm. Every site row reads vril_density anchor

(CH_75 L63, L65, L67, L69); the prose reads "the air itself a substance so rich" (L25). A

contrast instrument in a uniformly saturated field reads flat everywhere. And CH75_B02 — the

chapter's second beat and the beat the entire guardrail rests on — has as its objective "TELL THE TWO

WOUNDS APART" (CH_75 L93), with the failure state named as over-purging the King's grief. The game

asks the player to make the single most care-critical discrimination in the arc with an instrument

that is pinned at its ceiling.

Both teachers solve this the same way and it is the reusable move: Hollow Knight gives the infection

ONE unmistakable signature that reads against every biome regardless of ambient light; Ori gives the

Decay its own hue-and-form signature independent of the scene's brightness. TP goes further and lets

the player stand INSIDE the condition (the twilight vision) so it is experienced rather than

described.

RECOMMENDATION, reuse-first, and canon nearly writes it already. REALM_DESIGN_PROGRAM §2.5 currently

leaves the fairy realm's signature-law slot deliberately empty — "Ch 75-77 the fairy realm — NOT A

DELTA. The source." That is right about the DELTA and wrong about the SLOT: the source realm still has

a native law, and this is it.

THE FAIRY REALM'S NATIVE LAW — PERCEPTION READS FLOW, NOT CONCENTRATION. In the source realm,

where everything is saturated, the vril-sense inverts: it stops reading HOW MUCH and starts reading

HOW IT MOVES. Grief-crystal reads STILL AND DENSE. Corruption reads FLOWING-WRONG. Healthy realm reads

FLOWING-RIGHT. Native dark risen reads as its own thing entirely — it does not flow, it BURNS.

• It is derived from cited canon, not invented: T3_Core §6.5 L593 already describes the grief-vril

as "dense with accumulated emotion rather than FLOWING FREELY" — the flow axis is the tier doc's own

word, and the Prologue's saturation-expels-negation law is the same physics read from the other side.

• It satisfies LAW 3 with a real quantity (a flow-state field on the vril profile, not "it glows").
• It satisfies LAW 5, the legibility law, without a line of tutorial text: the grief-country IS the

low-threat teaching zone, hosts B01/B02/B03 (CH_75 L64), and B02 is where the law is learned by

using it.

• It makes CH75_B02's ruled verb playable and its ruled failure state (over-purging) a real risk

rather than a prose warning.

• Schema form: a flow_state term added to the physics vocabulary V (which REALM_DESIGN_PROGRAM

§2.3 states honestly is only four terms today — conductivity, mass, structural_integrity,

thermal_state — and is a real Wave-2 authoring task); RLM_0010.metaphysical_laws[] carries it as

the signature law with physical_expression = flow_state, taught_at = grief_country,

scope = all_actors.

• And it is a V-ADEQUACY PROBE CANDIDATE in its own right: flow_state is exactly the kind of real

bend that the four-term seed vocabulary cannot express, so authoring it is also a live demonstration

that the probe at §2.3 is necessary rather than ceremonial.

---

3. THE DOCTRINE DELIVERABLE — corruption-as-condition, restated so a schema designer can consume it

Everything below is the slice's output for Wave 2. Proposal-tier.

3.1 The five rules

1. THE CONDITION HAS A TOPOLOGY. Negative vril is one substance (HL_0114) with two shipping

modes: it FILLS A VACANCY (the Hollow, on a depleted substrate) or it SATURATES AN OCCUPANCY (the

fairy corruption, on a living one). A blight row that does not declare which is not typed.

2. THE AFFLICTED AND THE AFFLICTION ARE SEPARATE OBJECTS, IN DATA. affliction_state says whether

a being was ever clean; resolution_register says what the win did to it. A turned being whose

win register is ended is a guardrail defect, not a tuning choice.

3. NOT EVERY DEFORMATION IS A CORRUPTION. Three classes, three purge-eligibilities, three

consent-gates, three meter-eligibilities. Grief is never purged. Native dark is never cured. Only

the turned are restoration-eligible.

4. THE CONDITION MUST BE PERCEIVABLE BEFORE IT IS EXPLAINED. One signature, independent of ambient

density, taught in a low-threat zone of the same realm with no tutorial text (LAW 5). In the fairy

realm that signature is FLOW.

5. THE POWER BEHIND STAYS FACELESS AND STAYS SEPARATE. Four objects — realm, folk, turned, power

behind — never collapsed, at Ch 75 enforced additionally by the reveal ceiling (HL_0035).

3.2 The field set, consolidated (what Wave 2 mints)

Three new teeth, all members of the ALREADY-SPECIFIED harness/check_realm_ruleset.py family, each

shipping a must-fire and a must-not-fire fixture per the charter's own arming rule:

T-RLM-TOPOLOGY (F-4), T-RLM-GRIEFLOCK (F-5), T-RLM-CONDITION (F-2). Two rubric extensions

on the existing RB-RLM-CARE family (F-7's four-object test, F-9's before-state test). Zero new gate

files, zero new registries beyond the one the charter already proposes.

3.3 The Hollow ⇄ fairy-corruption boundary table (the harmonization the brief asked for)

The last row is the point, and it is why the two systems must be adjacent rather than merged: they are

the SAME reach expressing itself against two different substrates. Keeping them mechanically distinct

is what makes the eventual cassus recognition land as a connection the player MAKES rather than a

label the game applied.

---

4. ASPECT ROLL-UP (for the DESIGN_GAP_REGISTER matrix fold)

---

5. CONTESTED — for the director, each with alternatives, a recommendation and its strongest objection

C-1 · What made the saturating realm vulnerable? (F-6)

The doctrine needs a physical_expression for substrate_corruption and the answer is a real

story call.

• (a) GRIEF-STILLNESS IS THE VACANCY. The grief crystallized the vril "rather than flowing freely"

(T3_Core §6.5); stilled vril cannot expel; stillness is the aperture. PRO: mechanically perfect —

it unifies with F-17's flow law and with the Hollow's vacancy ontology in one stroke, and needs no

new canon. CON, and it is severe: it makes the father's love the enabling cause of the realm's

invasion, which cuts against T3_Core §6.6 L605 ("The father is not the villain of this chapter")

and risks turning a grief the game treats with total tenderness into an accusation.

• (b) THE UNSEALED BREACH IS THE APERTURE. The King's primary function is rift sealing

(T3_Core §6.4); the Prologue's own set-piece is the FIRST RIFT SEALED as proof he always seals it;

a king carrying decades of grief seals slower and reaches fewer, and the corruption "SEEPED" in

(CH_75 L29) — seepage requires an aperture. PRO: routes through grief at one remove — a DUTY

degraded, not a love weaponized; pays the Prologue's proof-beat off as tragedy rather than irony;

gives Law 3 a concrete quantity (unsealed-breach count / seal latency) that is already a canonical

faculty. CON: still routes the wound through the father, and an unsympathetic rendering could still

read as blame.

• (c) NO APERTURE — SLOW SOAK. The realm's fullness expels a SPARK, not a decades-long soak; the

House simply outlasted the expulsion. PRO: zero father-blame, zero canon strain. CON: weakest for

legibility — it names no quantity and no threshold, so it fails Law 3 on its face and gives the art

and QA layers nothing to render or measure.

RECOMMENDATION: (b). It satisfies Law 3 with an existing canonical faculty, it makes the

Prologue's most memorable beat pay off seventy-five chapters later, and it keeps the King honored —

his function was degraded by a loss, which is a tragedy about a role, not a verdict on a feeling. It

also composes cleanly with F-17: what the player SEES in the grief-country is stillness; what actually

let the rot in is a seam the King could not reach. Two different facts, and the game gets to let the

player conflate them and then correct them, which is exactly the "tell the two wounds apart" verb.

STRONGEST OBJECTION: any answer that runs through the father at all hands a hostile reader the

sentence "the King's grief let the enemy in," and the Ch-76 father encounter is the arc's most

important scene. The devil's-advocate-against-timidity check cuts the other way here and should be

recorded: refusing to give the realm a mechanism at all, in order to protect the King from a reading

nobody has yet made, would be exactly the care-inflation the standing calibration forbids — and (c),

the timid option, is also the one that fails the harmony doctrine. The bolder call is to state the

mechanism and author the King's dignity into the rendering, not to leave the physics blank.

C-2 · Is the fairy fold inside Hollow placement scope? (F-11)

• OUT (recommended). Falls out of T-RLM-TOPOLOGY physics — no vacancy at anchor density — so it

needs no special-casing and no authorial judgement per site. Keeps the two blights out of one frame

at the sharpest guardrail point in the game.

• IN. The REALM ledger axis exists partly to give the realm road cleansing content, and

excluding the crown-jewel realm shrinks that axis exactly where the player is most powerful. There

is also a real thematic argument: a Hollow standing in the fairy realm would be the most eloquent

single image of what the House does.

RECOMMENDATION: OUT for placement, IN for the ledger (the anchor-site re-attunement writes the

REALM axis without being typed as Hollow work). The eloquent image is better spent where it is

canonically native — an Earth deadzone the player already walked through clean.

C-3 · Should the Griever-at-the-Head's win be TYPED as a restoration? (F-2)

• YES (recommended). The ratified win is already "the win is REST" (CH_75 L79); typing it

resolution_register = rested makes the guardrail machine-visible and costs nothing narratively.

• NO. Typing a marquee champion's win into a restoration vocabulary that the Hollow's

CLEANSE/ABSORB fork also uses risks importing the Hollow's fork grammar into a realm boss — which is

precisely the blur F-3 and F-4 exist to prevent.

RECOMMENDATION: YES, with the vocabularies kept disjoint. resolution_register is an ENCOUNTER-row

field with realm-side values (rested, unseated, restored); the Hollow's phase-4 fork stays

CLEANSE/ABSORB on its own class row. Two vocabularies, one concept, no shared token — which is the

same discipline F-3 applies to the nouns.

---

6. WIRING OBLIGATIONS (anti-orphan — if any of this is adopted)

• docs/proposals/REALM_DESIGN_PROGRAM.md — §2.3 gains blight_topology, realm_deformations[],

decay_law; §2.5 gains the fairy realm's native signature law (F-17) replacing "NOT A DELTA. The

source." with "not a delta — the SOURCE, whose native law is X"; §2.7 gains T-RLM-TOPOLOGY,

T-RLM-GRIEFLOCK, T-RLM-CONDITION and the two rubric extensions; §4.2's L-R7 charter line is amended

per F-1.

• docs/DESIGN_GAP_REGISTER.md — R-A14 / R-A12 / R-A15 / R-A6 aspect rows minted with the §4

roll-up verdicts and this file as the teacher of record.

• docs/pipeline_review/HOLLOW_EXPANSION_INTEGRATION_2026-07-27.md — supersession pass closes JB-1

against the live HL_0080 row and unblocks X-9 (F-12); §2.4's realm-traversal budget records the

fairy-fold exclusion (F-11).

• docs/proposals/FINALE_FAIRY_ENRICHMENT.md + T3_Core_Characters §6.1/§6.5/§6.6 — the pre-v3

chapter re-key joins the Wave-3 residue punchlist (F-13).

• registries/T0_Region_Index — the fairy_realm state axis (F-16), applied only through

harness/apply_zone_catalog_columns.py.

• registries/T0_Character_Index — the childhood best friend's row, in the Ch-1 selection wiring pass

(F-8).

• docs/proposals/QA_WATCHING_PROGRAM.md — R-A15 gains a watchable rubric row for decay_law per its

§8 contract.

• docs/DOC_MAP.md — a row for whatever lands.

---

7. POSITIVE CONTROLS, PRIOR-ART BOUNDARIES, AND HONEST LIMITS

7.1 Positive controls run before every absence claim

• Comparator-title presence. Hollow Knight | Twilight Princess | Ori and the Will | Hallownest

(fixed alternation, case-insensitive, whole repo) returns 22 lines across 8 files — ALL of them

roster/lens/brief documents naming the titles as proposed teachers, none a design consumer.

CONTROL: Elden Ring | Bloodborne over docs/ returns 16 occurrences across 10 files, including

DESIGN_GAP_REGISTER.md ×7 where an already-run lens deposited findings. So the matcher can find

both a proposed title and a CONSUMED one; the zero on consumption is real.

• Character-index absence (F-8). Scan of all 164 T0_Character_Index rows for friend → 3 rows

(CHAR_0002, CHAR_0019, CHAR_0021), none the fairy-realm childhood friend. CONTROLS on the same

file, same method: healer → 5, court → 8, noble → 1. Matcher works; the zero is real. Controls

that legitimately returned zero and are reported as such: jarl, griever, kindler, courtier.

• Fading/decline vocabulary. fading|dwindl|waning case-insensitive over docs/ → 119

occurrences across 58 files, so the term class is findable. The finding at F-1 is therefore NOT that

"fading" is absent — it is present, at FINALE_FAIRY_ENRICHMENT §3 as an L2 REFERENCE substrate —

but that it is contradicted at the typed layer by vril_density anchor.

• Gap-register pre-registration. DESIGN_GAP_REGISTER.md scanned for `fairy|realm|

DIVERGENT-BY-DESIGN`: the divergence section (L190-236) covers 5 lenses with 19 COVERED and 17

DIVERGENT-BY-DESIGN entries, NONE of them a realm or fairy entry. No finding here re-litigates a

pre-registered divergence.

• Live-row reads over doc reads. HL_0080, HL_0109, HL_0114, HL_0121, HL_0035, HL_0046,

HL_0112, HL_0115 were read from registries/T0_Hard_Lines [ACTIVE v0.2]/Sheet1.csv directly,

not from any summarizing document. That read is what produced F-12.

7.2 Prior-art boundaries pre-registered (so this slice does not double-count)

• docs/pipeline_review/HOLLOW_LENS_SWEEP_2026-07-27.md §2.1 ALREADY ran Hollow Knight — for the

VOID / ABSENCE-ENTITY axis and the NAMING collision (§2.2, §7.2). This slice takes the

CORRUPTION-AS-CONDITION / FADING-COURT axis only, and re-litigates neither the Hollow's player-facing

name nor the void-lineage reading. That sweep's own §8 explicitly reserves L-R7's claim: "Hollow

Knight is claimed at L-R7 for the fading-court structure and should be dual-listed for the

VOID/absence-entity lesson." The dual-listing is therefore already agreed and this slice is the

L-R7 half.

• docs/pipeline_review/HOLLOW_CANON_CONTEXT_2026-07-27.md §3.9 pre-draws the same line: "L-R7

teaches a sovereign realm in decline, which serves the fairy realm, NOT the blight." F-3, F-4 and

F-11 are the first work that makes that line MECHANICAL rather than editorial.

• FORKC_ANALYSIS_DESIGN_PRECEDENT_2026-07-27.md owns the crossing CONVEYANCE (R-A7b). Nothing here

touches how the player physically crosses into the fairy realm.

• The director-ai-emergent-dread lens owns dread register; this slice owns grief and condition. F-10

states the boundary rather than crossing it.

7.3 Limits, stated

• docs/spine/CH_75.md was read to L161 of 343; the fork graph beyond FORK_CH75_A's header, the

scene block, the side-quest block and the state-write block were NOT read. A restoration-typed

win-state could exist in the unread tail; F-2's recommendation is a TYPING fix and survives either

way, but a Wave-2 author should re-read L162-343 before authoring RLM_0010.

• docs/proposals/REALM_DESIGN_PROGRAM.md was read at §0-§5.2 and §4 in full (1060-1260 of 1658);

§6 (the Josh forks), §7 (wiring) and §8 (analyst contradictions) were not read. If §6.2 already

carries a fairy-corruption fork, C-1 may duplicate it and should be reconciled before it is surfaced.

• HOLLOW_EXPANSION_INTEGRATION_2026-07-27.md was read to L667 of 1863. Sections 5-12 — including the

ranked worklist, the naming section and the positive-control appendix — were not read. F-11's scope

claim rests on §1.1/§2.1/§2.4; if a later section already excludes the fairy fold, F-11 downgrades

from MISSING to COVERED and the recommendation stands as a confirmation rather than a mint.

• Ori, Hollow Knight and Twilight Princess readings are analytical and carry no citation burden per

the wave rule; every CANON claim above is cited to file and line.

• No file in either repo was written, edited or staged by this agent.

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