HOLLOW_CANON_CONTEXT_2026-07-27.md

supernatural/HOLLOW_CANON_CONTEXT_2026-07-27.md

THE HOLLOW — THE CANON CONTEXT

Wave axis: everything the corpus holds on the Hollow. Read-only sweep, 2026-07-27 (fourth sitting).

Written beneath the realm charter's opening position (docs/proposals/REALM_DESIGN_PROGRAM.md §6.2):

admit as OBSERVE/CONTAIN class outside the 33 and the 22, "the Hollow" common with "substrate-echo"

as the class term, pure atmosphere pre-Ch-76.

**Headline of this axis: two of those three opening positions are contradicted by the corpus itself,

and the third is closer to already-ratified than the charter's framing implies.** Detail below.

Sweep method: Hollow / hollow / hollowed / substrate-echo / substrate echo / depleted dark /

deadzone / vril-null / negative vril across _source/, docs/, registries/, build/,

harness/. 189 Hollow occurrences across 69 files, all triaged. Positive controls run on every

zero (§8).

---

1. WHAT THE HOLLOW IS IN CURRENT CANON

1.1 Provenance — Josh-seeded twice, never agent-invented

This matters for how the admission fork should be read. The class is not a proposal looking for

permission; it is Josh's own idea, sharpened by Josh, awaiting his formal admission.

• Seed. docs/proposals/systems/creature-system.md §2.7: "This is the one genuinely new idea, and

the one Josh named directly: an intentional, cleanly-authored rare-encounter easter-egg that

evokes the MissingNo glitch-rare vibe without being a bug and without breaking canon."

• Refinement (2026-07-13). The FU section opens: "Josh raised two coupled points: (1) the

Hollow glitch-rare should read as a negative-vril BLIGHT — the negative-vril made flesh, a mature

R-rated horror-collect, not a cute pet; and (2) across the arc the player fights many folklore,

supernatural, and fairy-lore monsters as bosses — which of them are collectible, and how?"

• Design-of-record doc: docs/proposals/systems/creature-system.md (§2.7 the original spec; §5

FORKS 1-5; §FU.1-FU.7 the blight refinement, the CONTAIN verb, the collectibility map, FORKS 6-9).

Workflow provenance: the 5 AAA fun-mandate systems (wf_c3e19697 + wf_4934f395, per

docs/spine/NEW_SESSION_HANDOFF.md L93).

1.2 The physics reading (current — post-FU.1, supersedes §2.7's pure-echo read)

Negative vril congealed into flesh. Where negative vril has pooled and hardened — in a vril-null

deadzone, at a Velheim extraction scar, along a corruption seam — it occupies a vacated substrate-gap

and takes on a half-formed body. It wears the eroded shape of something the depletion took (the wound

note: a stolen face), but what animates that shape is negative vril, not life (the blight note:

self-losing, disconnected, consciousness-hardening flesh).

The parent physics is ACTIVE T1 canon, not proposal-tier —

_source/01_Tier_1_Foundation/T1_Vril_and_Magic_System_Master [ACTIVE v2.2].md L23:

"Negative vril is the substrate the antagonist family has accumulated across the canonical

5,000-year chronology... Negative vril is not personified evil. It is a vibrational state that

reinforces self-loss, disconnection, and consciousness-hardening. **Cassius Velheim's name (Latin

cassus, hollow, empty) carries the etymological signature.**"

Three binding riders from the same doc:

• §12.7 framing hard line — "Negative vril is not personified evil." The Hollow may never be

staged as a demon, a will, or a personified antagonist. It is a remainder in the world's arithmetic.

• §11.8 — Cassius's Ch-76 Phase-3 purge is the *single canonical negative-vril purge event in the

77-chapter arc*. A per-Hollow "purify" beat is a local gap-seal, not a purge; the wording must

never collide with the §11.8 singular.

• The Vril-Society firewall — reads mathematical/physical, never race-mystical polar energy

(memory: vril-vs-nazi-occult-vril-society-firewall). The landed registry row carries this as its

sole firewall_anchor value (see §4.1 — that is itself a defect).

1.3 The canon PARENT pattern — the Ch-6 False Naga

The single most load-bearing canon-nativity claim in the design (FU.1): the Hollow is "the wild,

ambient cousin of the False Naga (Ch 6): the same mechanic — negative-consciousness occupying a

being's vacated space and rising as a false substitute that must be identified and the genuine

restored — but spontaneous and environmental rather than a targeted vessel-substitution."

Verified present: False Naga = 67 occurrences across 30 files, including

T4_House_of_Velheim_Canonical [ACTIVE v1.0], T3_Supporting_Characters [ACTIVE v1.0],

T1_Story_Spine [ACTIVE v1.0] (9), T0_Character_Index, T0_Boss_Encounter_Registry,

build/spine_rows/CH_06/boss.csv. The parent is real, authored, and ratified.

This anchoring is what removes the "is this a fourth-wall rendering glitch" risk: the Hollow is the

game's own corruption substrate doing at ambient scale what the player already watches it do to the

naga at Ch 6.

1.4 Appearances by chapter — the substrate chain, staged end to end

From docs/proposals/whole_arc/through_line_system_throughline.md (THROUGH-LINE 3, "the Hollow

CONTAIN sub-line") and docs/proposals/whole_arc/through_line_recurring_antagonist.md §6:

through_line_recurring_antagonist.md §6 names this chain explicitly as **"the antagonist

SUBSTRATE... the deepest recurring pattern"**, and files it *out* of the fair-game-beast scope so the

beast chains stay distinct from it.

Critical placement fact for the reveal wave: the whole-arc pass certifies "the Hollow surface" as

one of the pre-Ch-38 seeds that introduce no agent-noun and no who-frame

(through_line_system_throughline.md L348-351). This is why extraction-scar spawn loci are listed

starting at Ch 39 — a blight visibly clustering at family sites before Ch 38 would leak the

pattern. The deadzone locus is family-neutral and carries no such constraint.

1.5 Relationship to rifts and the depleted dark

Four distinct things, one chain — worth stating precisely because the corpus keeps them separate:

• Rifts — spontaneous quantum events neither side creates intentionally. Every authored rift beat

is at the MEMBRANE; there is no inside-the-rift canon at all (REALM_DESIGN_PROGRAM.md: "blank

BY DOCTRINE rather than by neglect"). The Hollow is not a rift interior and must not be conflated

with one — they are two of the four un-authored otherworld surfaces on the same charter list.

• The depleted dark — what presses through a rift. The Prologue/Ch-1 phenomenon. Deliberately

UNAUTHORED, faceless, never a foe (WHOLE_ARC_CONNECTIONS_PASS.md L47: "the intrusion held

unauthored and unnamed"; AMULET_PROVENANCE_BRIEF.md L400: "A rift-spawn is the depleted dark

pressing through, ambient" — the mother's death must have NO author).

• Negative vril — the substrate itself. Accumulated by the family since ~3000 BCE. Not personified.
• The Hollow — that substrate *standing up as a body* in a vacated gap. The only member of the

chain with anatomy.

1.6 The collect-verb, the reward, the tone

• CONTAIN — a hazmat/exorcism grammar, never a pokeball grammar. STABILIZE the negative-vril

charge → SEAL the substrate-gap → LIFT a containment-record into a sealed sub-codex of the Bestiary

(an "unlisted" slot). *The collectible is the record, never a living entry.*

• The purify/harvest integrity fork. Good register: PURIFY — the blight unmade, the gap sealed,

a measure of positive substrate returns to the deadzone (a small world-healing beat, a mercy for the

stolen shape). Evil register: HARVEST — draining the negative charge into your own signature, a

hardening act with an integrity cost. Both log the same record. Never a power gate, never a dead end

(the non-gating invariant).

• Reward, firewall-safe: documentation, lore, a prestige/cosmetic containment-halo, and a thread

toward the Forgotten One prestige content. No combat power.

• SUPERSEDED ON THE ABSORB PATH (Josh, eighth and ninth sittings 2026-07-27; ruling record

docs/spine/DECISIONS_PENDING_JOSH.md; integration record

docs/pipeline_review/HOLLOW_EXPANSION_INTEGRATION_2026-07-27.md §4.5). "No combat power" is

superseded on the ABSORB branch, where the evil-integrity path grants hollow-type abilities toward

endgame. The documentation payout above holds for the whisper tier and for the cleanse branch. Read

the purify and harvest terms in the bullet above as the retired synonyms of CLEANSE and ABSORB, and

note that the hardening-pull in the tone bullet is promoted to the class's signature phase-2

mechanic, still never an unleavable debuff, because the class is now fought and defeated.

• Tone: R-rated body horror — unrendered flickering flesh, wrong anatomy, silence, vril-static,

and a light *hardening-pull* on approach (a felt integrity-pressure moment, never a mechanical

debuff you cannot leave). "You never keep a Hollow alive, never bond it, never garden it. The horror

is precisely that it looks like a lost thing and is filled with the wrong substrate."

• Trigger: sigma-governed (§17.13 — no 1/8192 misery; anti-streak ceiling guarantees it appears

for a player who does the arcane thing, floor stops it trivializing). The arcane thing is a

discoverable ritual — observing at a vril-null deadzone at a liminal time, *after* the bestiary is

deep enough that Vril Sight can perceive the gaps.

---

2. THE THREE SUB-FORKS — THE PRIOR RECORD

2.1 Where the original fork text lives

docs/proposals/systems/creature-system.md §5 "Forks for Josh — options and recommendation"

(FORKS 1-5), extended by §FU.6 "New forks for Josh" (FORKS 6-9). Mirrored as open flags in

docs/proposals/systems/WS7_WIRING_BUILD_PLAN.md §creature-breeding (8 flags), summarized in

docs/proposals/systems/RULINGS.md L19, and tracked as outstanding in

docs/FOUNDATION_COMPLETION_PLAN.md L39, docs/spine/FABLE5_HANDOFF.md L106,

docs/spine/NEW_SESSION_HANDOFF.md L96 ("STILL WANTING JOSH'S FINAL EXPLICIT YES... the Hollow

OBSERVE-class"), and docs/PRE_5090_BUILD_PLAN.md L122.

Verbatim, the three:

FORK 1 — Does the substrate-echo glitch-rare enter canon at all, and as what class? Options:

(a) it does not exist (drop the novel hook); (b) it exists as an OBSERVE-class documentation

phenomenon OUTSIDE the 33/22 numerology, not tameable/breedable/slot/legendary (the clean-firewall

design in §2.7); (c) it exists but as a tameable oddity (rejected on my side — it endangers the

firewall). Recommendation: (b).

FORK 2 — The substrate-echo's name and in-world register. Naming is Josh's. Options, all reading

mathematical/substrate per the vril-register firewall and evoking MissingNo's "missing number":

the Unnumbered (closest MissingNo resonance, eerie, mathematical), the Remainder (what the

arithmetic left over), the Hollow / Hollows (the wound register, most atmospheric), **σ-echo /

the Sigma-ghost (ties to the §17.13 sigma boundary). Recommendation: "the Hollow"** as the

in-world common name (what people whisper), with "substrate-echo" as the design/registry class

term.

FORK 3 — Reveal-tie of the substrate-echo (§17.9). Options: (a) pure atmosphere pre-Ch-76, zero

explanation, its meaning strictly Layer-3/post-reveal (the safe design in §2.7); (b) it carries

breadcrumb lore that partially explains the depletion earlier. Recommendation: (a).

The coupled FU.6 set — FORK 6 (adopt the blight refinement + CONTAIN verb + purify/harvest fork),

FORK 7 (ratify the ontology-driven collectibility map onto Creature_Roster + Boss_Encounter),

FORK 8 (the EARN lane's count/curation, rec ~6-12 hand-authored), FORK 9 (formalize the

sacred-set invariant as a §17.1 coupling, likely a new HL_ id).

2.2 ⚠ FORK 3 WAS ALREADY SUPERSEDED BY ITS OWN FOLLOW-UP — the charter carries the stale wording

This is the sharpest single finding of the sweep. creature-system.md FU.1 contains a sub-heading

that says so in the text:

"Reveal, refined (updates FORK 3). Because negative-vril corruption is on stage from Ch 6 onward

(the False Naga, the strigoi-as-vril-parasite at Ch 26, the negative-consciousness manifestations),

the Hollow's SURFACE reading — a negative-vril blight, a corruption-organism — is **reveal-SAFE and

can be legible from its first appearance.** What stays Layer-3 and post-Ch-76 is the deeper meaning:

that the shape it wears is what the depletion erased, and that the depletion and the substrate point

ultimately at the Grand Sage truth. So the Hollow is now safER than the old framing, which

leaned its whole meaning on the reveal-locked depletion-substrate. Surface: corruption made flesh

(say it). Depth: a wound wearing a lost face, pointing at the pre-depletion truth (never say it

pre-reveal)."

Four independent artifacts carry the REFINED split, not the §5 wording:

1. The landed registry cell — T0_Hollow_Codex designs reveal_tier as a const:

'SURFACE_blight_legible; DEPTH_L3_post_Ch76' (WS7_WIRING_BUILD_PLAN.md L371).

2. through_line_system_throughline.md L159-160 — "Reveal: surface = negative-vril blight (SAFE

from Ch 6); depth (the erased shape → the Grand-Sage substrate) = Layer-3 / post-Ch-76 only."

3. through_line_system_throughline.md L350-351 — "The Hollow's surface (negative-vril blight) is

Ch-6-legible; its depth... stays Layer-3 / post-Ch-76."

4. through_line_recurring_antagonist.md L366-368 — "its SURFACE — a starved self-losing dark — is

reveal-safe from first appearance... its meaning is Layer-3 locked to Ch 74-77."

5. phase1_A1_prologue_ch1.md L36 — the same split applied back to the Prologue.

The charter's §6.2 opening position — "pure atmosphere pre-Ch-76" — is the **superseded §5 FORK-3

(a)** wording. REALM_ANALYSIS_CANON_INVENTORY_2026-07-27.md inherited it the same way (its bullet

correctly *describes* the refined split in the Status para, then lists the stale recommendation in the

Blank para). The reveal wave should rule the FU.1 split, not the §5 sentence — and should note

that "pure atmosphere pre-Ch-76" and "surface legible from Ch 6" are materially different builds:

the former forbids an NPC from ever saying what the thing is; the latter lets the world name it a

blight and only forbids the *why*.

2.3 What "the reveal window" is actually bounded by

• CVD §17.9 (T1_CVD_Creative_Vision_Document [ACTIVE v1.4] L1093-1105): "The thesis is never

declared explicitly anywhere"; "Pre-Ch 76 Grand Sage identity hints are forbidden"; the surface

track is self-contained and reads complete without the investigatable-depth or canonical-truth

tracks.

• The standing silences: Cassius held to Ch 76; the thesis and the Grand Sage held to Ch 77;

no House-of-Velheim pattern before ~Ch 38 (memory: antagonist-pattern-reveal-timing — even

invoked-and-negated agent-nouns leak).

• Therefore the Hollow's reveal constraint set is three-layered, not two:

1. Surface (what it is) — a negative-vril blight. Safe from Ch 6 per FU.1.

2. Pattern (whose footprint it clusters on) — extraction-scar loci must not read as a *who*

before Ch 38. Deadzone loci carry no such constraint.

3. Depth (what the worn shape means) — the erased pre-depletion thing → the Grand Sage

substrate. Layer-3, post-Ch-76, never earlier.

---

3. WHAT ALREADY CONSUMES IT

The class is not greenfield. Ranked by how much a NO would cost.

3.1 ⚠ HL_0080 — an ACTIVE canonical hard line already names the Hollow class

registries/T0_Hard_Lines [ACTIVE v0.2]/Sheet1.csv, row HL_0080 (source_section T1_Combat §9.2,

status canonical, consumers UE5,Quest,Spine,SFX, related HL_0008,HL_0021). Its scoping clause:

"**Scope: this non-damage protocol governs ONLY the negative-vril / sacred-site atmospheric echo

(the Hollow-adjacent CONTAIN-verb class).** 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..."

Provenance: docs/proposals/canon_correction/cc1_hardlines.md §A3, VERDICT REWRITE, CLASS APPLY.

Consequence for the admission fork. A NO (option a, drop the class) does not simply un-build a

proposal — it orphans a term inside a live canonical hard-line row and forces an HL_0080 rewrite. A

YES ratifies wording that is already in the registry. The charter's framing of this as an open

greenfield admission understates how far the class has already propagated.

3.2 T0_Hollow_Codex — LANDED, gate-declared, and DIVERGENT from its own design

registries/T0_Hollow_Codex [DRAFT v0.1]/Sheet1.csv exists on disk: 14 columns, 1 row. Created in

WS7 Increment A (FOUNDATION_COMPLETION_PLAN.md L19: 7 new registries anchored, gates 13/13).

Named in the registry census at OPEN_DECISIONS_BRIEF_2026-07-22.md L173/L187 as one of the three

empty-but-schemad registries ("Hollow_Codex (1/14)... can already receive rows and need population").

The row on disk:

HW_0001, The Hollow (negative-vril blight), drain-deadzone, central_africa_congo,
CH_39-CH_65, CONTAIN, purify|harvest, , tier-gated vril-sight, design-layer,
vril-restore; lore, vril-vs-nazi-occult firewall, standard,
creature-system.md §the-Hollow

Five divergences from the designed seed (WS7_WIRING_BUILD_PLAN.md L376-377):

Plus: HW_0002 (the extraction-scar locus) is missing entirely — the designed second seed row was

never written. And WS7_WIRING_BUILD_PLAN.md marks the whole creature-breeding increment

STATUS: TODO, so this row predates or partially anticipates the design and was never reconciled.

Net: the registry is real and gate-enrolled, but its single row asserts two cardinal facts (a chapter

window and a region) that no ruling supports, and drops the two columns (reveal_tier, firewall_anchor)

that carry the discipline. This needs fixing regardless of which way the admission fork goes —

it is a live do-not-invent breach, not a design question.

3.3 T0_Creature_Roster — the ontology columns ARE landed

Header verified on disk. Alongside the husbandry set (husbandry_breedable, offspring_tier_lock,

husbandry_venue, trait_halo_pool, temperament_prior) it carries the FORK-7 map's columns:

ontology_class, collect_verb, dex_completion_class. collect_verb's declared vocabulary

includes CONTAIN_BLIGHT, and dex_completion_class includes CONTAINMENT — i.e. the Hollow's lane

is already a value in a landed controlled vocabulary. Per-row assignment is the open part (FORK 7).

3.4 T0_Boss_Encounter_Registry — designed extension + the adjacent cast

Designed columns (ontology_class / collect_verb / restore_target, via stub refresh). The

registry already carries the Hollow-*adjacent* cast that the name analysis turns on — BE_0002, BE_0053,

BE_0058 (The Unmade Rift), BE_0060_S1. See §5.

3.5 The two whole-arc through-lines

• docs/proposals/whole_arc/through_line_system_throughline.md — THROUGH-LINE 3 is titled "The

Taming / Breeding creature line (+ the 22nd slot and the Hollow CONTAIN sub-line)". The Hollow

is one of the three strata of the creature population and has its own staged sub-line paragraph

(L153-160), with Verdict FAIR_GAME/blight.

• docs/proposals/whole_arc/through_line_recurring_antagonist.md §6 — "the negative-vril / Hollow

substrate (the phenomenon under everything)... the antagonist SUBSTRATE... the deepest recurring

pattern."

3.6 The Personal Dimension dependency (a sequencing fact)

Named twice as one of four systems the Tier-6 Personal Dimension venue hosts:

"the Personal Dimension is the shared endgame VENUE for breeding, the Hollow sub-codex, the

arcade room, and the Games-Master trophy aggregator — the Tier-6 unlock is load-bearing for four

systems' completion loops." (through_line_system_throughline.md L332-333; echoed

WHOLE_ARC_CONNECTIONS_PASS.md L250.)

But the Personal Dimension is itself maturity D with an empty spec ("a private astral sub-space,

ability-canon only, spec stub empty" — REALM_ANALYSIS_CANON_INVENTORY_2026-07-27.md). Admitting the

Hollow adds a fourth consumer to an unwritten spec. Not a blocker; a sequencing note for whoever

schedules the Personal Dimension work.

3.7 WS_039 — the worldstate variable

Designed (WS7 Increment C): hollow_containment_fork_last, enum(NONE|PURIFY|HARVEST), default

NONE, consumers integrity_score_resolver, world_state_resolver, authority creature-system.md FU.2.

KEY CORRECTION (2026-07-27 — integration record X-3). This section was written as WS_029,

the id the WS7 seed carried. The row landed at WS_039

(registries/T0_Worldstate_Variables [ACTIVE v0.1]/Sheet1.csv, row 40); live WS_029 is

trade_sovereignty_valence, an unrelated base-building row.

3.8 The realm program (this session's own consumer)

• REALM_DESIGN_PROGRAM.md roster: the Hollow is one of "four further otherworld surfaces that exist

as MECHANIC or PHENOMENON and never as authored places: the astral plane, the dream tradition, the

Hollow, and rift interiors." Graded D — designed and UNRATIFIED. Described as "**not a realm but

an ANTI-realm**... the negative-space counterpart to the realms and the most direct visual

expression of the vril-altered-physics doctrine available outside the realms themselves."

• REALM_ANALYSIS_CANON_INVENTORY_2026-07-27.md Part 4 (§"The Hollow") is the fullest standing

inventory entry; Part 6 lists the admission fork as open; Part 7 grades it D.

• REALM_DESIGN_PROGRAM.md §6.2 carries it as one of three genuine Josh forks.

3.9 The dread-register / comparator gap

docs/proposals/COMPARATOR_LENS_PROGRAM.md L54: "**nothing teaches horror-tension pacing for the

Hollow**, rift spawns, the realm road, the R-17..." — a named, still-open lens gap. The realm

program's L-R7 fading-court-realm lens (Hollow Knight · Ori · Twilight Realm · Nokron) is *adjacent

but not it* — L-R7 teaches a sovereign realm in decline, which serves the fairy realm, not the blight.

If the Hollow is admitted, the horror-tension lens is an unfilled dependency.

3.10 What does NOT consume it — the honest negative

Zero playable content. No spine chapter stages a Hollow encounter; no quest row, no beat row, no

scene row, no dialogue line. Positive-controlled: every one of the 21 Hollow hits in

docs/spine/CH_60.md is the *Hollow Retainer* construct; all 4 in CH_02.md are *Rangku Wera the

Hollow Hunter*; both in CH_53.md are the *hollowed-vessel* inversion. The class is designed,

schema'd, hard-line-referenced, and through-line-staged — and has never been built.

No DOC_MAP row for T0_Hollow_Codex. Positive control: Rune_Registry 0, Dwelling_Registry 0,

Vehicle_Registry 0, Environment_Grammar 0, Minigame_Registry 1 — so this is a **WS7

Increment-A-wide DOC_MAP gap**, not Hollow-specific neglect. The anti-orphan rule (every artifact needs

a consumer AND a DOC_MAP row) is breached for most of the batch. Worth a separate cleanup, not a

finding against the Hollow.

---

4. THE CONSTRAINT SET — WHAT ADMISSION TOUCHES

4.1 The 33 and the 22 — NOT touched, and provably so by construction

The locks, verbatim from T0_Hard_Lines [ACTIVE v0.2]:

• HL_0057 (CVD §17.12, canonical) — "33 legendary-tier species: 21 mortal (7 Ground, 7 Flight, 7

Water, all earned via bonding-quest vril development) plus 12 elven (realm-elevated vril,

power-on-par with mortal legendary)."

• HL_0058 (CVD §17.12, canonical) — "Player familiar slots: 22 total — 21 base plus one

path-variable 22nd... The 22nd path-variable slot is reserved for the protagonist's childhood

familiar from the fairy realm."

The Hollow's exclusions are structural, not promissory — four independent gates:

1. Never TAME-status → outside the 22nd-slot binding-stone pool, which T3_Creatures_Tameable

§2.4 gates to TAME-status species *only*. So a Hollow can never be the elevated 22nd. This is the

strongest of the four: it is a consequence of an existing rule, not a new promise.

2. No CR_ id — it lives in its own HW_ registry, not T0_Creature_Roster. It cannot be

counted into the legendary roster because it is not in that table.

3. Not breedable → HL_0057/HL_0058's offspring firewall (bred offspring ALWAYS ordinary-tier) is

untouched; the Hollow never enters the husbandry pool at all.

4. Not a combat slot, no combat power → the three sacred slots stay legendary-only.

SUPERSEDED IN HALF, WITH PRECISION (integration record §4.5). The NOT-A-COMBAT-SLOT half SURVIVES:

the three sacred familiar slots stay legendary-only and the absorb lane never touches a slot. The

no-combat-power half is superseded only for the ABSORB lane, which is catalog access on the ability

tree rather than a slot, a species, or an entry in the 33 or the 22 — so the guarantee this gate

protects is unaffected.

Precedent for the additive move: CVD §17.12's new-systems reconciliation already ratified

(2026-07-12) that additive live-layer registries' *existence* is canonical and their *counts* are

authorial — the exact basis on which MG_ (Minigame) and VH_ (Vehicle) were admitted. Admitting HW_

adds a registry, not a count.

The one number that does move, and should be declared: the bestiary/dex total. That figure is

*already* drifting — T3_Creatures_Tameable says "200+" in §0.1, "400-plus / 420-plus" in §1.1/§2,

and "222 entries" in §3 (creature-system.md §4; OPEN_DECISIONS_BRIEF_2026-07-22.md L183).

Recommendation: declare the containment records a separate sealed sub-codex, explicitly NOT an

addition to the bestiary count — which is what §2.7/FU.2 already describe ("a sealed sub-codex... an

'unlisted' slot"). Saying so at ratification prevents the drift getting worse.

4.2 The entity taxonomy — FORK 1 is coupled to FORKS 7 and 9

The FU.3 collectibility map sorts every supernatural being to exactly one of seven lanes by

ontology (what the tradition says the being IS), not by "is it supernatural":

LEGENDARY (BOND, quest only) · ORDINARY_FAUNA TAME-status (TAME+BREED) · ORDINARY_FAUNA

OBSERVE/DANGEROUS/CRYPTID (DOCUMENT) · A SACRED (DOCUMENT / FREE / ALLY — *never* captured) ·

B CONDEMNED (FIGHT; CONTAIN-PURGE where it is an affliction on a person) · C AMBIVALENT

(EARN — a small hand-curated set) · D CONSTRUCT (FIGHT + FREE) · E BLIGHT = the Hollow

(CONTAIN-blight).

Coupling: the BLIGHT lane exists only if the Hollow is admitted. A YES on FORK 1 makes FORK 7

(ratify the map) and FORK 9 (the sacred-set invariant as a §17.1 hard line) nearly forced — they are

the same instrument. A NO leaves the map intact minus one lane; FU.6 states the degradation is clean

(same as lane C: "the map degrades cleanly — lane C empties and every supernatural being routes to

DOCUMENT / FIGHT / FREE / CONTAIN / BOND with no other change").

The care value runs through this coupling. Lane A exists *so that* the aku-aku, Pele, the

Nightmarchers, taniwha, moʻo, the revered Rangda, the conscious Naga, and the Ouidah sacred python are

structurally uncapturable by design — routed to DOCUMENT/FREE/ALLY, never owned. The Hollow is

what absorbs the "collect the horror" impulse onto a thing that is *nobody's tradition*: zero

real-culture attribution surface, zero §17.1 exposure. That is the strongest care argument for

admission, and it is an argument that care ADDS content rather than subtracting it.

4.3 The boss rosters — the anti-defang firewall must ride forward verbatim

HL_0080's scope clause exists *precisely* to stop the non-damage CONTAIN protocol from spreading onto

mythological monsters: "It never applies to a mythological monster, deity-champion, or malevolent

being... 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."

Two riders in the same row that any admission must carry:

• "The 4-step non-damage protocol is ONE encounter class within a chapter, **never the chapter's sole

combat layer**: every listed instance also stages a real fought encounter."

• "the containment beat itself is staged as an action-forward, vril-taxing set-piece — dodge,

parry, and manage the pool under real pressure — not a static perceive-and-wait puzzle."

The devil's-advocate note the care doctrine requires. The repo's documented failure direction is

DEFANGING, and it has repeatedly had to be REVERSED (OPEN_DECISIONS_BRIEF_2026-07-22.md L903: "the

project has repeatedly had to REVERSE defanging — D-DRAGON-18 reversed; the 'never captured' rule

killed; §17.16 written specifically to stop this"). So the calibrated-bolder pass should ask the

opposite question to the one the design keeps asking: is the Hollow too safe? No combat power, no

fight, a documentation-only reward, and a "light hardening-pull... never a mechanical debuff you

cannot leave" — for a hook Josh explicitly asked to be *mature R-rated horror, not a cute pet*. The

HL_0080 riders (action-forward, vril-taxing, real pressure) are the corrective already in canon; a

ratification that does not carry them forward risks shipping the timid version of Josh's own steer.

ANSWERED IN THE AFFIRMATIVE DIRECTION (Josh, eighth and ninth sittings 2026-07-27; integration record

§4.5). The devil's-advocate question was the right one and the ruling agreed with it. The class is

FOUGHT: Josh removed the Hollow from HL_0080's non-damage protocol, wrote "defeat it to heal or absorb

it instead," and set the encounter-design mandate — puzzle-forward encounters still carrying real

combat, action-forward encounters carrying a per-encounter trick such as a damage window, a combo or

parry requirement, or environmental-damage-only, with the palette open. So "no combat power, no fight,

a documentation-only reward" no longer describes the class. The two riders quoted above SURVIVE and

now govern the sacred-site atmospheric echo, which keeps its non-damage protocol and its six built

instances, while their language is also the correct register for phase 2 of the Hollow's own

four-phase grammar.

4.4 The realm roster the charter just built — untouched

Admission adds no realm. The 9 road realms + the fairy fold + the Personal Dimension structure is

unchanged; the Hollow is admitted as a *phenomenon-class* and stays on the "exists as MECHANIC or

PHENOMENON, never as an authored place" list alongside the astral plane, the dream tradition, and rift

interiors. What admission *does* give the realm program is a design target: the Hollow is the named

"most direct visual expression of the vril-altered-physics doctrine outside the realms" — i.e. an

art-bible/board deliverable, not a spine node. That is the sense in which the realm program is the

correct forcing function for this fork.

4.5 Chapter assignment — deliberately unset, currently violated

The design and the wiring plan both hold chapter assignment as Josh's (do-not-invent). The landed

HW_0001 row asserts CH_39-CH_65 + central_africa_congo anyway (§3.2). Either Josh sets a window,

or the row reverts to deadzone-availability. The through-line's own staging supplies the natural

answer if he wants one: deadzone loci available broadly; extraction-scar loci from Ch 39 (the

pre-Ch-38 pattern-silence boundary, §2.3).

4.6 Care doctrine at bolder calibration — the surfaces

• Zero cultural-attribution surface. The Hollow is nobody's tradition, nobody's sacred being,

nobody's condemned monster. It is the only lane in the map with no §17.1 living-culture exposure.

• The §17 hard-line floor — untouched. No genocide-as-goal, no real-world targeted hate, no sexual

violence, no child harm. Body horror against a non-person blight is squarely inside the rated-M bar.

• The one genuine care surface is HARVEST — draining a stolen shape into your own signature. This

is an evil-path act carrying an integrity cost, non-gating, with the purify branch always available.

That is the mature-consequence register the content bar asks for, not a care problem. The register

to hold: the harvested thing wears *a lost face*, and the game should let that land.

• The vril-register firewall is the live care constraint: the Hollow must read mathematical and

physical (a remainder in the world's arithmetic), never race-mystical. This intersects the

hollow-earth naming problem in §5.

---

5. THE NAME — THE CANON CONTEXT THE NAMING METHOD NEEDS

This is where the sweep most directly contradicts the charter's opening position. Both halves of

"'the Hollow' common with 'substrate-echo' as the class term" have checkable collisions.

5.1 ⚠ "substrate-echo" collides with a LIVE, WIRED, DIFFERENT term

Substrate-Echo is already the name of the canonical NAMING METHOD — docs/NAMING_METHOD.md,

the deep-dive-canon → adversarial-filter → player-vibe-test loop Josh ruled on 2026-07-04. It is not

a doc reference; it is wired into the authoring pipeline:

• harness/enrich.py:59 — a load-bearing instruction line in every chapter's enrich pack:

("docs/NAMING_METHOD.md", "Substrate-Echo naming for any NPC/boss/site introduced")

• harness/enrich.py:674 — the not-found fallback: `"NOT_FOUND — author fresh per the Substrate-Echo

method + the boss-as-system rules."`

• docs/proposals/BOSS_PERSONAS.md — 7+ uses ("Substrate-Echo names", "Substrate-Echo confirms:",

"Derived autonomously via the Substrate-Echo method"), including Section C's "six refined

Substrate-Echo rules".

• docs/spine/CH_57_BUILD_BRIEF.md L130/L233 — "goes through the Substrate-Echo naming method at

build time"; "pending the Substrate-Echo naming pass".

• docs/DECISION_DOSSIER.md §17 — the ratified boss-naming methodology is literally *"A.

Substrate-Echo methodology (the §17.7 realm-name discipline generalized)"*.

Adopting "substrate-echo" as the Hollow's class term makes **"the Substrate-Echo method" and "a

substrate-echo"** two unrelated things in one corpus, with one of them read by every chapter build

through enrich.py. Every future authoring agent reading an enrich pack would see both.

And it is independently stale. FU.1 retired the echo framing on its own terms: the class is no

longer "an echo of a lost thing" but "negative vril congealed into flesh *wearing* a lost shape." The

§2.7 substrate-*echo* read is the superseded one. So the class term is doubly wrong — semantically

superseded AND lexically colliding with a wired pipeline term.

*Note for the naming wave:* docs/spine/CH_66.md L225 also uses "substrate-echoes" in a third,

unrelated sense (Atlantis's non-lethal realm phenomena). Three senses, one hyphenate.

5.2 "the Hollow" — the resonance is real, and so is the crowding

Already a proper-noun role-title on two ratified bosses:

• BE_0002 "Rangku Wera, the Hollow Hunter" (Ch 2) — the game's first main boss. CHAR_0008.

The name is not incidental: quest QS_CH_02_04 is titled "The Hollow Hunter", with

quest_anchor_id: CH02_HOLLOW_HUNTER and dialogue namespace DLG_CH02_HOLLOW_HUNTER; speaker

attributions read "Rangku Wera (the hollow answering)"; harness/check_build_readiness.py's

derived boss index prints "BE_0002 the Hollow Hunter · morphology: hollowed-humanoid gaunt".

STATUS.md L181 names him too.

• BE_0060_S1 "the Hollow Retainer" (Ch 60) — a family-forced bound tool-spirit

(tsukumogami/onryō), Construct-Kit CLASS 1, freed-not-slain. Carried across T0_Chapter_Index,

T0_Antagonist_Network_Registry, aaa_ws3_modern_reflesh.md, modern_scope_59_65.md,

through_line_recurring_antagonist.md, REVEAL_WINDOW_REALIGNMENT.md, CH_60.md (21 hits),

build/spine_rows/CH_60/boss.csv.

• BE_0053 (Ch 53) — the WS4 HOLLOWED-VESSEL inversion; win-condition register literally

"EXPOSURE-OF-THE-HOLLOW", pity-edged.

• Plus the RULED shared boss grammar: "inscription-made-flesh as the class grammar + the per-boss

regional condemned-register skin + the shared hollow-core tell" (D-MATARG-LOOK, Josh-ruled).

And the anti-fringe collision. "Hollow Earth" is a *named excluded lineage* in the

authorial-only anti-fringe firewall — and it is co-located with the Vril-Society firewall the Hollow

class must itself hold:

• aaa_ws1_opportunity_matrix.md L535 — "Antarctica owns no indigenous tradition — its 'mythology' is

the heroic-era survival epic plus the polar-fringe mythos (**Hollow Earth / Symmes / Thule-vril,

which is exactly where the Vril-Society firewall must operate**)."

• T0_Chapter_Index Ch 54 / Ch 67 / Ch 71 — "no Nazi-base/Base-211, no hollow-earth, no

ancient-aliens-under-the-ice (authorial-only)"; Ch 71: "**hollow-earth ONLY honored

history-of-science (Halley 1692 concentric-shells; Symmes 1818) never the modern conspiracy**".

• modern_scope_53_58.md L254 — the same firewall.
• Legitimate unrelated use: Ch 30 "Glastonbury Tor = the hollow-hill gateway to Annwn" (Celtic,

fine).

The case FOR the name is genuinely strong and should not be dismissed: *cassus = hollow* is

ACTIVE T1 canon (T1_Vril L23), not a proposal. Rangku Wera hollowed by the polo's bargain, the

Hollow Retainer's hollowed oath, Salmuera's exposed hollow, the shared hollow-core boss tell, Cassius's

hollow name, and the ambient blight all being *hollow* is arguably the arc's deepest single through-line

made lexically legible. FU.1 says exactly this: "The name was always pointing here."

The case AGAINST is a naming-method failure mode, verbatim. docs/NAMING_METHOD.md lists under

"Failure modes to design against": "Endpoint collision. A middle name must not be a near-synonym

of a fixed endpoint." And the natural-voice doctrine asks the player-vibe question directly: does a

player who meets "the Hollow Hunter" at Ch 2, contains "a Hollow" at Ch 20, and frees "the Hollow

Retainer" at Ch 60 parse three things or one?

The synthesis this axis supports: keep the *hollow root* (it is canon, and the resonance is the

design's own argument), but do not ship the bare capital-H common noun into a corpus that already

spends it on two boss role-titles — run the full method on a distinguishing form so the player

parses the class as distinct from the two characters. And replace the class term entirely;

"substrate-echo" is not available.

5.3 The alternate candidates — positive-controlled

---

6. RECOMMENDATIONS FROM THIS AXIS

Scoped to what the canon context supports; the cross-lens synthesis belongs to the other waves.

Sub-fork 1 — ADMISSION. The context supports YES at class (b) (OBSERVE/CONTAIN, outside the

33/22), and more strongly than the charter's framing implies — because admission is closer to

ratification-of-the-already-wired than to greenfield minting. Five independent artifacts already

carry the class: a canonical ACTIVE hard-line row (HL_0080) names it by name; a registry is landed and

gate-declared; the Creature_Roster ontology columns with CONTAIN_BLIGHT in their vocabulary are

landed; two whole-arc through-line docs stage it Prologue→prestige; and the idea plus its sharpening

are both Josh-originated. A NO is not a no-op — it orphans a term inside a canonical hard line and

forces an HL_0080 rewrite. The 33/22 exclusion is structural (four gates, §4.1), not promissory. The

one number to declare at ratification: the containment sub-codex is separate from the bestiary

count, not an addition to it.

Sub-fork 2 — THE NAME. The context does not support the charter's opening position as written.

Two checkable defects: (i) "substrate-echo" as the class term collides with the live Substrate-Echo

naming method wired into enrich.py:59/674 and is semantically superseded by FU.1's blight

refinement — it is not available and should be replaced outright; (ii) bare "the Hollow" lands a

capital-H common noun into a corpus that already spends "the Hollow X" on two ratified boss

role-titles (Ch 2's first main boss, Ch 60's freed construct) and guards "hollow-earth" as an

excluded-fringe lineage under the same Vril-Society firewall the class must hold. Recommendation to

the naming wave: keep the hollow root (ACTIVE T1 canon via *cassus*; the resonance is the design's

own strongest argument) but run the full method on a distinguishing form, and mint a fresh class

term. "the Remainder" is collision-clean and semantically exact; the sigma forms are clean but fail

natural-voice.

Sub-fork 3 — THE REVEAL WINDOW. The charter's "pure atmosphere pre-Ch-76" is the **superseded §5

FORK-3(a) wording**. creature-system.md FU.1 explicitly updates it ("Reveal, refined (updates FORK

3)"), and five artifacts carry the refined split instead — including the landed registry's designed

reveal_tier const. Recommendation: rule the FU.1 split, not the §5 sentence — surface (a

negative-vril blight) legible from first appearance, because Ch-6's False Naga already puts

negative-vril corruption on stage; depth (the worn shape is what the depletion erased → the Grand Sage

substrate) Layer-3 / post-Ch-76 only. Add the third layer the whole-arc pass supplies: **extraction-scar

spawn loci not before Ch 38** (the pattern-silence boundary); deadzone loci are family-neutral and

unconstrained. This is the *reveal-safer* option, not the looser one — it stops the class leaning its

whole meaning on the reveal-locked substrate.

A fourth item no sub-fork covers — the landed row is a live do-not-invent breach. HW_0001

asserts chapter_window=CH_39-CH_65 and region_id=central_africa_congo — two cardinal

chapter/region assignments the wiring plan explicitly reserves to Josh — while dropping the

reveal_tier §17.9 encoding and the firewall_anchor 33/22 lock text, breaking the

spawn_locus_type enum, and omitting HW_0002 entirely. **This needs reconciling regardless of which

way the fork goes**, and it should not ride quietly inside a ratification.

---

7. THE STANDING RECORD — WHERE EVERY PIECE LIVES

---

8. POSITIVE CONTROLS — every zero in this document

Per the standing rule (a search that cannot match reports zero).

Sweep variants run: Hollow, hollow, hollowed, substrate-echo, substrate_echo, `substrate

echo, depleted dark, deadzone, vril-null, vril_null, negative vril, negative-vril`,

cassus, Unnumbered, the Remainder, Sigma-ghost, σ-echo, Hollow_Codex, HW_0001,

False Naga, HL_0057, HL_0058, HL_0080.

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