CR_0179_pey_and_bhutam.md

creatures/CR_0179_pey_and_bhutam.md

CR_0179 — the pey and the bhutam: the tradition's own malevolent spirits, faced un-rowed

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

STATUS: PROPOSAL-TIER design sheet, written to docs/proposals/bestiary/BESTIARY_ELEVATION_DOCTRINE.md

and critic-gated against its ten refusal tests. It cites canon rows and writes none. It mints no boss

row, no beat, no site and no drop row.

1. identity

chapter CH_07 · region south_india

collect_verb DOCUMENT;FIGHT · dex_completion_class WITNESS · cultural_depiction_required TRUE

region_native south_india · chapter_first_encounter CH_07

mesh_pipeline_type image_to_3d · generation_status pending

scientific_name, thread_anchor, familiar_slot_eligible, trade_8_tameable,

temperament_prior, spawn_rate, every husbandry cell, rare_variant, extinction_threat,

familiar_cross_ref, intelligence_tier, kit_ref. The row states the reason for each and the

reasons are correct; § 9 names them so a later enrichment does not read them as holes.

posture line binding — "care here is calibrated rather than inflated" [south_india.md:408-409].

= FOLKLORE_FACED (SELF_EVIDENT_IN_THE_GROUND, IN_SCOPE) and ontology_class = CONDEMNED

(RULED_IN_L11, RULING_10, IN_SCOPE) [CREATURE_DEMAND_RULED_STATE_L11.json § ruled_demand_table

→ CH_07 → CR_0179].

this row carries a populated folklore_attribution_source, a CONDEMNED ontology and a

mythologically-stylized style cell, and the § 3D ceiling rules that the moment a row gains a

folklore cell the sheet re-derives under the full grammar.

BE_ row" [@ CR_0179 :: notes]. § 6 is written to that tier and § 1.1 rules it before anything

else is authored.

@ CR_0160, @ CR_0039 · T0_Chapter_Index @ CH_07 :: folklore_entities_in_chapter ·

T0_Quest_Seed_Registry @ SEED_0030 · T0_Environment_Grammar_Registry @ EG_0012, @ EG_0020,

@ EG_0076-0079, @ EG_0082, @ EG_0088, @ EG_0089, @ EG_0090, @ EG_0093 ·

T0_RNG_Drop_Table (scanned for the row's declared anchor — see § 9) ·

docs/COMBAT_ENCOUNTER_SYSTEM.md:309 (the ruled firewall definition § 6.9 derives from) ·

build/3d/schema/anatomy_reference/HUMANOID.json · build/3d/schema/creature_archetype_map.json ·

docs/spine/CH_07.md L3, L10, L12, L17, L83, L84, L92-L105, L113-L115, L227, L252, L264, L269,

L271, L281, L301, L335 · _source/02_Tier_2_Region_Pages/south_india.md L217-L221, L359-L362,

L400-L404, L406-L412, L432-L433, L438-L440, L448-L449, L454-L455, L499-L518, L546-L553,

L1078-L1080, L1247, L1259-L1269, L1282-L1283 ·

docs/proposals/bestiary/sheets/CR_0177_soorasamharam_remnant.md and CR_0160_krasue_ap.md as the

set neighbour and the ratified precedent

1.1 THE STAGING RULING THIS SHEET IS BUILT AROUND, DISPOSED ON THE FACE

Two canon facts sit in apparent tension on this row and BOTH ARE HELD. Neither is reopened.

pey/bhutam malevolent-spirit register rides the folklore layer as ambient substrate, drawn as the

tradition holds it, never a rowed encounter" [CH_07.md:114].

combat_permission reads FOLKLORE_FACED and the ruled state carries combat_facing TRUE

[CREATURE_DEMAND_RULED_STATE_L11.json @ CR_0179]. The spine itself types this register on the

asset line — "the Surapadman-class asura and the pey/bhutam as folklore beings

(mythologically-stylized, faced as the tradition condemns them)" [CH_07.md:269] — on a line that

cites [SRC: T0_Creature_Roster] directly.

THE RECONCILIATION, AND IT IS THE ROW'S OWN, ADOPTED RATHER THAN INVENTED HERE. The row declares

the AMBIENT-HOSTILE tier and states exactly what it strikes: "fightable WITHOUT a BE_ row. The no-boss

ruling at CH_07.md:114 stands and is not reopened; what is struck is the false equation under it

(not-a-boss silently reading as not-encounterable)" [@ CR_0179 :: notes]. L114 is a STAGING sentence

sitting inside the § 9 boss-structure block whose every other bullet is a BE_ row [CH_07.md:112-115],

and all three of its clauses are about how the register is STAGED in this chapter. It does not rule

the being un-buildable or un-facable; the spine's own asset line rules the opposite at :269.

SO THIS SHEET DOES BOTH, AND THE DIVISION IS EXACT.

agency, real lethality and a real part economy. The demand is real and the anti-timid law binds: a

sheet that reduced this register to weather would fail the row, fail the ruled state, and take the

timid option the standing law names as usually wrong.

[DIRECTOR-RULED, WQ_0031 L14]. L114 forbids a ROWED encounter — its own parenthetical "(no registry

row)" is what the word means on that line — and it is silent on un-rowed ambient hostiles. So the

presence, the dread and the environmental pressure all stand AND the contact is real: a lethal,

un-rowed encounter that comes to the player on its own schedule, at night and on unfirewalled

ground, which is exactly the CR_0160 shape. § 6.9 carries the ruling in full with its legal ground

class enumerated, and § 6.9 is the part of this sheet a later lane is most likely to break.

CH_07-live rather than held for a later pass. What is not minted, by this sheet and by the ruling

both: no BE_ row, no beat, no fork, no site row edited or minted, and no spawn or drop row. The

encounter is staged by the REGISTER rather than by a row, which is the whole content of

"ambient-hostile" and the reason the tier exists.

THE PRECEDENT IS RATIFIED AND IS FOLLOWED IN KIND RATHER THAN RE-ARGUED, AND WHAT IT ACTUALLY DID IS

THE POINT: CR_0160 DID NOT REFUSE TO STAGE. It ruled that the row's "no encounter" was an

INFERENCE the cited line does not carry — "NEVER A BOSS is canon and binds absolutely; NO ENCOUNTER is

the row note's inference and does not, because the spine's own staging line outranks a registry note's

derivation" — and it then designed and staged a real NIGHT ENCOUNTER IN THE AMBIENT REGISTER, "a real

lethal threat that comes to the player rather than waiting to be visited," minting no BE_ row and

leaving the blank permission cell for the registry lane [CR_0160_krasue_ap.md:181-203, § 9]. It did

that on canon language WEAKER than this row's — a blank permission cell plus one spine asset line,

against this row's written FOLKLORE_FACED, its collect_verb FIGHT token and CH_07.md:269. So the

design obligation and the STAGING obligation are both stronger here, not merely identical, and § 6.9

follows the precedent in kind under the director's ruling.

1.2 THE ANTI-CONFLATION LAW, WHICH IS THE OTHER THING THIS SHEET IS BUILT AROUND

The spine names the asuras and the pey/bhutam as two distinct items on one folklore line — "the

Murugan six-abodes and Soorasamharam demon-war, the asuras (Surapadman, Tarakan, Singamukhan), the

pey/bhutam malevolent spirits, and the Siddha deathlessness legend" [CH_07.md:83] — and gives only the

asura a BE_ row and a fork [CH_07.md:113, :208-219]. The roster rules the consequence: pooling them

"would collapse a condemned MYTHIC DEMON of a named war-cycle into an ambient spirit register and lose

both" [@ CR_0179 :: notes], and the set neighbour's sheet states the same rule from the other side

[CR_0177_soorasamharam_remnant.md § 7].

**THE DESIGN OBLIGATION THAT FALLS OUT OF IT, AND IT GOVERNS EVERY AXIS IN § 4: A PEY MUST NEVER READ

AS A SMALL ASURA AT THE COMBAT CAMERA.** The discrimination is structural rather than decorative, and

it is stated as a contract the plate lane and the mesh lane both inherit:

the asura, CR_0177, landedthis register, CR_0179
ARENA scale — the body sets the arena's scaleTRUE_SCALE, and under human mass
ONE figure that divides into two and then fournever singular — a scatter, and the count is the read
planted, driving through both leg pairs into the hillnever standing — always hanging off something by its hands
solid, heavy, oppressing; the world goes still around itthin, light, and the world does not notice it at all
a seam running the body's long axis, and a head that is a joinno seam, no join, an ordinary head on an ordinary neck
reads by occlusion against hard daylight, on a bare hillreads by a dust crust catching lamplight, on walls and roadsides
a mythic demon of a NAMED war-cycle, faced once, on the spinea register with no name-stone, faced in this chapter with no row, no beat and no name

AND IT IS NEVER POOLED WITH THREE OTHER THINGS EITHER, per the row: not with the honored Siddha

deathless masters, who are HUMAN and live at T0_Character_Index @ CHAR_0048; not with Murugan or

Meenakshi, who are HONORED_inviolate in the chapter index's own folklore cell

[T0_Chapter_Index @ CH_07 :: folklore_entities_in_chapter]; and not with the corrupted

marma-assassin, who is a living man and BE_0007_S1 [CH_07.md:113].

2. base_species

**NO ANIMAL BASE AND NO CANON BODY PLAN. This sheet declares its archetype as the game's own choice and

then refuses to invent a single number on top of it.**

CR_0179 in NEEDS_CANON_BODY_PLAN, and every anatomy bucket scopes those rows out because "a

reference table that guessed one would be inventing creature canon" [HUMANOID.json § scope]. The

row's mesh_tags.morphology reads "folklore", a provenance word standing where a body plan belongs.

the spine's whole physical statement is that this is a malevolent-spirit register rendered

mythologically-stylized [CH_07.md:83, :269, :271].

human mass**, on three design grounds named as ours. The style register is exclusive —

mythologically-stylized for this being against realistic-ethnographic for the communities beside it

[CH_07.md:271] — and a register whose job is to read as legibly NOT-a-person needs the human

baseline to be legibly not. The § 1.2 contract needs a body inverting the asura's every physical

property, and the strongest inversion of a heavy planted arena-scale humanoid is a light hanging

under-scale one. And § 5's departures are all subtractions from a human body, which needs something

to subtract from.

Doctrine § 2.1's inline licence expired because an over-declared ROM licenses poses the solver

should refuse, so the goniometry is taken from

build/3d/schema/anatomy_reference/HUMANOID.json § sub_plans.human (reference_taxon *Homo

sapiens*), whose own warning is why the block matters: "Every range below is clinical goniometry,

which means a pose outside it is not stylised — it is an injury" [§ one_line]. § 9 boards the

census assignment as the registry-side decision it is.

DERIVED, EVERY VALUE THE TABLE'S:

departs from it and what that departure costs.

a PRESENT, LOAD-BEARING CLAVICLE; and three spinal curves — cervical lordosis, thoracic kyphosis,

lumbar lordosis — with the table's own note that "a straight-spine rig reads as a mannequin"

[§ segments].

180, axial rotation ±90; scapulothoracic elevation 0 to 60, protraction-retraction ±30, upward

rotation 0 to 60, with the note that "the last 60 deg of overhead reach comes from HERE, not the

shoulder"; elbow 0 to 150, negative being hyperextension and normal only to about -10; radioulnar

pronation-supination ±80; wrist flexion-extension -80 to +70 and radial-ulnar deviation -20 to +30;

hip flexion-extension -30 to 120, abduction-adduction -30 to +45, axial rotation ±45; knee 0 to 135

with axial rotation ±10 AVAILABLE ONLY IN FLEXION because the screw-home locks it at extension;

ankle dorsi-plantarflexion -20 to +50; subtalar inversion-eversion -35 to +15, "the joint that lets

a foot sit on a slope"; cervical spine summed at ±45 flexion-extension, ±45 lateral, ±80 axial; and

thoracolumbar summed at 0-80 flexion, 0-30 extension, ±35 lateral, ±45 axial, SUMMED over the chain

because "per-vertebra it is a few degrees, which is why a two-bone spine cannot make a real bend"

[§ joints, all values AAOS1965 / NORKIN2016].

chain of at least 4; two arm and two leg chains of at least 4 bones each; ten hand-digit chains of

at least 3; clavicle_L and clavicle_R REQUIRED bones; opposable_hallux_required false;

gait_sequence biped_alternating; bilateral symmetry required [§ rig_conformance]. § 5 raises

the digit chains and states where the extra bone attaches; it lowers nothing.

DEPARTURE RATHER THAN LEFT SILENT: gait_sequence biped_alternating.** The table requires an

alternating biped gait sequence and this body does not have one, because its feet never take load

(§ 4.2). The departure is a SUBSTITUTION rather than a deletion, and it keeps the field's own law:

the locomotor cycle is an alternating BRACHIAL sequence carried on the two arm chains at the same

0.5 phase offset, with a support phase that genuinely exists and simply lives in the hands, while

the leg chains trail as unloaded followers with their passive envelope untouched. Nothing about the

field is lowered or waived — it is relocated, and the relocation is the design's single strongest

distance-read. A rig-conformance gate reading gait_sequence literally will flag this row until an

archetype assignment lands; § 9 boards that with the archetype board rather than hiding it inside a

design note, because a silent departure on a conformance field is exactly the defect this block

exists to prevent.

TOOL.** "Goniometry measures the passive envelope. What a live animal reaches under its own power

is smaller, by an amount the sources do not separate" [§ unmeasured]. This being is built exactly

in that gap: its PASSIVE ranges are the table's, unchanged and unexceeded, and its ACTIVE range at

the hip, knee and ankle has collapsed to near nothing. That is what § 4's atrophy axis IS, stated

in the table's own vocabulary rather than as a new number.

MASS, STANCE, GAIT AND RESTING SILHOUETTE:

the soft tissue that should be on it, and the two hands and forearms carry most of what is left.

cart-rail, a gate-jamb, a tree-fork or a roof-eave, held by the hands, with the legs trailing and

bearing nothing. § 5 gives the skeletal account.

SUPPORT present — its absence is what makes a walk read as a run" [§ gait]. **THIS BODY NEVER

HAS DOUBLE SUPPORT AND NEVER HAS SINGLE SUPPORT EITHER**, because its feet never carry. That single

derived fact is the strongest distance-read in the design and it costs no effect: a human-shaped

thing crossing ground with no footfall cycle at all is wrong in black fill at any range, and no

player needs to be told why.

and roof height, thin everywhere except two hands and two forearms that are the wrong size for it,

with its legs hanging straight and still beneath.

3. lore_source

than paraphrased: "authentic living tamil condemned category ... the pey and the bhutam are the

tradition's OWN malevolent spirits and the two names are the spine's own vocabulary used verbatim

... the register runs at AMBIENT GRAIN and canon stages it as ambient substrate and never as a

rowed encounter ... it is set beside the protective demon slaying register of the soorasamharam and

beside the marma assassin's healer turned killer dread and all three are drawn as the tradition

holds them" [@ CR_0179 :: folklore_attribution_source].

and Malayali traditions "as they understand themselves — the malevolent asuras of the Tamil Murugan

war-cycle restored as the tradition's OWN condemned demons ... plus the pey/bhutam malevolent-spirit

register" [CH_07.md:3].

asuras (Surapadman, Tarakan, Singamukhan), the pey/bhutam malevolent spirits, and the Siddha

deathlessness legend are the chapter's living folklore, depicted as the tradition holds them"

[CH_07.md:83]; and the superstition facet ruling the register's TONE, "drawn as the tradition holds

them" [CH_07.md:84].

and the pey/bhutam as folklore beings (mythologically-stylized, faced as the tradition condemns

them)" [CH_07.md:269], and the exclusive style list at [CH_07.md:271].

the Soorasamharam asura-war, the pey/bhutam register, and the Murugan six-abodes" [CH_07.md:227];

the seed row's outcome line, "the malevolent-spirit register the chapter runs at ambient grain rides

the same folklore layer, drawn as the tradition holds it and never a rowed encounter"

[@ SEED_0030 :: canonical_outcomes]; and the region page's one line for it, "the ambient

malevolent-spirit register the spine carries without a rowed encounter" [south_india.md:1078-1080].

THE ATTESTATION CEILING, DECLARED ON THE FACE RATHER THAN PAPERED OVER, AND THE CONTROLS BOTH RUN.

_source/02_Tier_2_Region_Pages/south_india.md for "pey" and for "bhutam" as tradition-terms

returns ZERO. The page carries the register only descriptively, at the one Folklore Combat line

above. The row declares the same result and ranks the gap [@ CR_0179 :: folklore_attribution_source].

*When the Body Becomes All Eyes*, 544 chunks, "the keystone; the Section 3/4/5/6/7/10/12/13/14

anchor, and the only source on this shelf that carries the region's living practice at technique

grain" [south_india.md:1247] — resolves and is quoted SIX times below (the Sangam hero-stone

institution and its Kerala continuity, the deified kalari hero-images, the propitiation of deified

ancestor-heroes, the kalari's surrounding protective deities, the puttara's guardian deity, and the

imageless forest-goddess place). It simply carries nothing about this being.

southern vital-spot tradition in its own literature, rather than through the Malayali monograph's

comparative chapters" [south_india.md:1282-1283], listed under MUST-ACQUIRE. Every structural

claim in § 4 and § 5 is superseded in place the day a Tamil-side source lands and attests otherwise.

under this region slug is a parapsychology review that is a mis-sort, and "the presence of a

parapsychology corpus under a region whose canon carries a Siddha tradition is precisely the

adjacency the anti-fringe rule guards" [south_india.md:1259-1269]. Nothing on this sheet touches

it, and no claim here rests on it.

**THE LICENCE THIS SHEET BUILDS UNDER, QUOTED, because a lane that does not know it exists produces an

empty sheet.** HL_0002: "Claims about a LIVING culture's tradition, ritual, language, or sacred

practice trace to primary-source record (floors 1-3). Mythic monsters, boss encounters, dungeon/site

design, and adventure content carry fantasy license — grounded in the tradition's own material but

free to extrapolate for playable spectacle; they are not bound to a citable source"

[T0_Hard_Lines @ HL_0002]. The tradition's own material here is the register's existence, its name,

its condemned status and its ambient grain, all cited above. The body that carries them is ours.

THE TWO NAMES ARE ONE ROW AND THIS SHEET DOES NOT SPLIT THEM. Canon uses "pey/bhutam" as a

compound register word at six separate lines [CH_07.md:3, :83, :114, :227, :269, :271] and the chapter

index carries the single token PEY_BHUTAM_malevolent_spirits. So this sheet builds ONE body grammar

under both names and assigns neither name to a distinguishing form, because a corpus that attests no

distinguishing feature cannot support a taxonomy, and inventing one would be an invention wearing the

tradition's authority — the exact defect the anti-conflation law exists to stop, run in the other

direction. Where a Tamil-side source lands and separates them, the separation lands then and it lands

attested.

THE CITED REGIONAL MATERIAL THIS DESIGN ACTUALLY RESTS ON, and it is not about spirits at all. The

page carries, at technique grain and behind SRC_00262, an institutional account of what this region

does with its dead and with the ground around it: "in the Sangam age fallen heroes were deified by

planting stones inscribed with the hero's name and his valorous deeds, worshipped by the people of the

locality ... The continuity of that practice into the medieval Kerala propitiation of deified kalari

heroes is drawn in the record itself" [south_india.md:359-362]; the kalari keeps "small images of

locally deified kalari heroes, a legacy of the Sangam-age deification of fallen warriors" [:454-455];

the region's performance culture includes "the propitiation of deified ancestor-heroes" [:400-404];

and the tradition's protective register stands in its own spaces — the kalari's deities "surrounding

and suffusing the space with their protection" [:432-433], the puttara where "the guardian deity

resides, usually a form of the goddess, Bhagavati or Bhadrakali" [:438-440], and "a place with neither

image nor mound where the forest goddess resides" [:448-449].

**THE DESIGN ARGUMENT, DECLARED AS THE GAME'S OWN AND STATED IN ONE SENTENCE: this region's own record

says a death that is honoured gets a NAME, a STONE and a locality that worships it — so the game's

register of the tradition's condemned spirits is built as the exact inverse, the dead that got none of

the three.** No name on any stone, no locality, no propitiation, no seat, no mound, no image; a being

with nothing to be worshipped at. That is why § 4's primary axis is what it is, why the design never

routes through a person, and why the tradition reads here as the side that does the honouring rather

than the side that produces the horror. The inverse is ours; the institution it inverts is cited.

THE COUNTER-LINE FROM THE REGION PAGE, NAMED AND DISPOSED RATHER THAN STEPPED AROUND. Section 5

opens its malevolent block with a sentence that reads at first as a refusal of this whole subject:

"The malevolent register, which this region locates precisely and does not import. The tradition's own

condemned figure is not a monster but a misuse" [south_india.md:505-508]. Read in place, that

paragraph is scoped to the VITAL-SPOT tradition's own dark mirror — it continues into the chapter that

"is titled to heal and to harm" and lands on "[t]he corrupted individual the spine stages

(BE_0007_S1) sits exactly there and nowhere else" [south_india.md:506-510]. It is a rule about what

the Malayali martial-esoteric domain imports, and the page itself carries the pey/bhutam register

separately at :1078-1080. **THE CONSTRAINT IT NEVERTHELESS IMPOSES IS REAL AND IS ADOPTED: this

register is never routed through the kalari, the vital-spot art, the marma map, a practitioner, a

charlatan or a healer.** Those belong to BE_0007_S1 and to the page's charlatan seed

[south_india.md:510-518], and putting a spirit behind them would import exactly what the page

refuses. § 6.9 sites this register on the roadside and the street-edge and nowhere near the pit.

4. elevation

ONE-LINE SILHOUETTE READ: **a person-shaped frame with nothing left on it and two hands too big for

it, hanging off a wall by its fingers because it has no legs left to stand on — and there is never

only one.**

THREE AXES. The budget is two to four and three is spent; § 4.4 states what was deliberately not

spent and why.

4.1 PRIMARY — A4 HYPERTROPHY AND ATROPHY

ONE SYSTEM TAKEN FAR PAST BASELINE WHILE ANOTHER IS LET GO, and here both halves are the same

decision seen twice.

machine that is visible as bulk on an otherwise bare skeleton, and the hand is enlarged in

proportion with it — each digit carrying one additional phalangeal segment (§ 5 gives the

attachment and the ROM). Everything the body still does, it does with these.

gone, and the consequence is stated in the anatomy table's own terms rather than as a new number:

the PASSIVE goniometric envelope at hip, knee and ankle is unchanged and is exactly the table's,

while the ACTIVE range under the body's own power has collapsed — the gap the table itself declares

unmeasured [HUMANOID.json § unmeasured]. **THIS BODY CANNOT SUPPORT ITS OWN WEIGHT ON ITS

LEGS.** Not "chooses not to." Cannot.

mechanism is decoration: the body has been reduced to the one function it still has a use for.

What it wants is a purchase, and it has spent its entire remaining substance on being able to take

one and keep it. Vril alters real physics rather than exempting a body from it, so the trade is a

real trade with a real price, and the price is that it can never let go of the world without

falling out of the fight.

holding something; the arena is therefore a map of purchases; denying a purchase is a real tactic

that costs real capability; and the moment it moves a hand is the only moment it is not dangerous.

Nothing here is a multiplier — one system got everything and the rest paid for it, and both halves

are visible from across a street.

4.2 SUPPORTING — A10 NEGATIVE SPACE

The absent thing that reads, and there are three, each independently legible.

full digit count, both clavicles — and there is nothing on it. The thoracolumbar chain reads as a

chain because nothing covers it, and the scapula reads as a plate because nothing covers that

either. This is subtraction on a correct skeleton, which is the opposite of a blob.

absence is what makes a walk read as a run" [HUMANOID.json § gait]; this body has neither

double nor single support, because the feet never take load. On flat ground it hauls itself hand

over hand and its legs DRAG, leaving a two-line trail in dust that is the strongest sign-read in

the design.

player never learns how many are out; the second one is always found by hearing it rather than by

seeing it (§ 6.5). The absence here is an absence of information, and it is the axis's cheapest and

strongest spend.

4.3 SUPPORTING — A5 AGE AND STATE

The place written on the body, in material rather than in colour.

ground the being has crossed, packed in dry and layered. The region supplies its own palette

honestly: laterite red off the Ghats flank and monsoon gully, whose environment row gifts

material:laterite outright [@ EG_0090]; pale plain dust off the dry Tamil interior

[CH_07.md:10]; a fine soot off the craft-street quarter and its trade-home frontage [@ EG_0093].

The soot is sourced from EG_0093 ALONE and never from EG_0078: the precinct street frame is

firewalled ground under § 6.9's ruled definition (protected_care_ref HL_0001,

alteration_permanence_default hard_blocked) and this being is never on it, so crusting it with

that row's dust would site the body where the staging block forbids it.

player who has been paying attention can tell where one came in from before it reaches them. This

is the state ladder a photograph of anything cannot contain, and it is entirely material, entirely

postural and entirely light-law-free.

cook-fire or moon is already in the scene; the frame itself is matte and dark and reads by occlusion

against a lit wall. So the being is HARDEST to see against an open bright sky and EASIEST against

lit stone, which is a positioning fact the player can use and the creature can be denied.

4.4 EMISSION, AND THE AXIS DELIBERATELY NOT SPENT

emission only from the three emitting families by their own named mechanism. Nothing in this design

is self-lit: the crust is RETURN from a light already in the scene, exactly as the Flores mata

mbere and the CR_0160 wet-line marks are, and the frame is read by occlusion. There are no glowing

eyes, no aura, no rim-light without a source, no floating sigil and no emitter-less particle.

The primary axis already produces the one-line read — hands too big on a frame with nothing on it —

and that read is silhouette-borne, which means it survives black fill, icon size, night and

distance. Adding a second identifying feature would dilute it, and "a creature carrying three marks

carries none." If a later Tamil-side acquisition attests a mark for this register, that mark is

ATTESTED and becomes usable, and the law-compliant route for it is to REPLACE nothing (the hands

are structure, not a mark) and to sit on the body as return rather than as emission.

5. articulation_delta

curves, two arm and two leg chains of at least four bones each, both clavicles, sixty deform bones

minimum, bilateral symmetry, passive ROM exactly as declared and never exceeded.

THE ADDED SEGMENT, its attachment, its chain, its ROM and its load path.

distal phalanx as a fourth bone on each finger and thumb, raising the table's hand_digit chain

minimum from 3 to 4 on this body alone. It is a pure HINGE: flexion 0 to 90 degrees, ZERO extension

past neutral, zero abduction, zero axial rotation. It cannot straighten past flat and it cannot

spread.

segment through the three inherited phalanges, across the metacarpals, through the hypertrophied

flexor mass, up the radioulna, across the elbow at its inherited 0-150 hinge, into the glenohumeral

joint, and from there through the scapulothoracic synsarcosis STRUTTED BY THE CLAVICLE — which is

why the clavicle stays a required bone on this rig and why removing it would collapse the design

and not merely the pose [HUMANOID.json § segments, § rig_conformance].

one more than a person's, so the close is a visibly longer event with a distinct terminal LOCK at

90 degrees, and the lock is audible (§ 6.5).

THE HYPERTROPHY'S OWN COST, WHICH IS A ROM REDUCTION AND NOT A ROM EXPANSION.

flexor bulk is physically in the way of the rotation. **A HYPERTROPHY THAT COSTS RANGE IS A REAL

BODY.** No other range is altered anywhere on this rig, and this one is REDUCED, which is the only

direction a sheet may safely move a derived envelope: an under-declared range refuses poses, and an

over-declared one licenses injuries.

and a BLIND FACE. There is an arc on each side that the palm cannot be turned to reach without

moving the whole shoulder, and standing in it is a real, learnable, body-visible answer (§ 6.4,

shape 2).

THE POSTURE DEPARTURE, AND THE ONE THING IT CHANGES IN THE SILHOUETTE.

ALWAYS IN TENSION rather than in compression: it hangs. Under hang the lumbar lordosis flattens

toward neutral and the whole chain lengthens, so **the being is measurably TALLER hanging than it

would be standing**, and the transition between the two is a real animatable event rather than a

scale change. That is a silhouette state with no asset swap and no effect.

times and the solver still refuses anything outside it; what has gone is the drive, not the range.

The knee in particular never rotates at extension, per the table's own single most common bad-rig

tell.

sit on a slope" [HUMANOID.json § joints], and on a dragged leg it is what lets the trailing foot

lie flat along a kerb-line instead of standing proud of it. A dragged foot that stays rigid reads as

a prop.

NOTHING ELSE IS ADDED. No horn, no crest, no plate, no tail, no second jaw, no extra limb pair, no

wing, no mark, no seam and no join. One added bone per digit, one bulk change with its own cost, one

posture in tension. Three axes, one new structure, and the structure is a finger.

6. fight_grammar

6.1 The tier, and what this block does and does not mint

AMBIENT-HOSTILE, per the row's own declared tier: "fightable WITHOUT a BE_ row"

[@ CR_0179 :: notes]. **THIS SHEET MINTS NO BE_ ROW, NO BEAT, NO SITE, NO FORK, NO SPAWN ROW AND NO

DROP ROW.** The grammar below is CH_07-LIVE at that tier under the director's ruling, and § 6.9 states

the ruling, the ground it is legal on and the ground it is refused on.

THE ENCOUNTER VERBS ARE NOT ON A CANON ROW AND THE SHEET SAYS SO RATHER THAN BORROWING A TEMPLATE. The

roster row carries collect_verb DOCUMENT;FIGHT and dex_completion_class WITNESS and no verb pair,

because verbs live on boss rows and this row has none. So the verbs below are PROPOSED BY THIS SHEET

as design-side, boarded in § 9, and named as ours: HOLD / DENY — the creature holds a purchase and

the player denies it one. They are derived from the primary axis and from nothing else, and no later

lane should read them as canon until a registry pass writes them.

6.2 Part economy

HOME: BODY, declared by name per doctrine § 2.4.

partsilhouette fractionbreak eventpermanent subtractionlegibility gainmaterial
the hand, either side~0.09 each, oversized against a bare framethe digit chains fail at the added fourth segment and the hand will not lockit can no longer take or hold a VERTICAL purchase on that side; two-handed draw-ups are gone permanentlya one-handed haul is slower and its swing is wide and readable, so its next plant is predictablesee below
the forearm flexor mass, either side~0.06 eachthe bulk goes slack and the forearm reads thin like the rest of the bodygrip strength on that side drops to a hold it cannot re-take once releasedthe pronation ceiling collapses further, so the blind face widens and is easier to stand insee below

BOTH HANDS BROKEN IS THE FLOOR STATE AND IT IS NOT A KILL. A being with no vertical purchase is

grounded permanently, on the drag alone, and the encounter's whole geometry changes — which is the

part economy doing its job rather than a health bar counting down.

THE MATERIAL CURRENCY IS DECLARED ABSENT AND THE ABSENCE IS A FINDING RATHER THAN A DESIGN CHOICE.

The row's rng_drop_anchor cell reads DROP_CH07_PEY_BHUTAM_AMBIENT_RESIDUE while the row's own

notes say "rng_drop_anchor BLANK BY DESIGN," and a scan of T0_RNG_Drop_Table returns NO ROW OF

THAT ID. So this sheet designs no material payload, states that the completion payload is DOCUMENT and

WITNESS and the SQ1 lore [CH_07.md:227], and boards the dangling reference in § 9 rather than writing

a drop row from a design lane.

THE PURCHASES ARE NOT A SECOND PART ECONOMY AND THIS SHEET SAYS SO EXPLICITLY. The wall, the

kerb-stone, the cart-rail, the gate-jamb, the tree-fork and the eave that the creature holds are ARENA

features. They can be denied, occupied, wetted, lit or walked away from, and denying them is the

encounter's core tactic — but they have no break threshold, no break event and no material, they

belong to the place rather than to the creature, and calling them parts would inflate a two-part

economy into a false eight. Named here so no later lane mistakes a tactic for a part.

6.3 The opener and its variants

hand comes off and reaches across the path. Most legible, least punishing: one limb, one plane, a

long close on the fourth-segment lock, and a clean miss costs the creature its own re-plant.

back and the shoulder has to travel.

returning to rest, which teaches that the re-plant is not a rest.

Teaching order is a design field here: every dangerous move is a recognizable variant of the single

reach, so a player who has learned the opener has learned the shape of everything else.

6.4 Tell shapes, one answer each

tell shapebody origin — segment, chain, massthe one answercounter class worn on the body
ONE HAND RELEASES AND RE-PLANTSthe flexor mass on the free side unloads, the added phalanges open past the lock, and the whole body's weight transfers onto the other arm — the spine visibly lengthens as it takes the loadCLOSE NOW — it cannot strike while it is transferring, and this is the only window it givescommit window; strike on transfer
THE PALM TURNS AND STOPS SHORTthe radioulnar chain runs out at its reduced ±55 and the arm compensates by abducting the whole shoulder, which is a big, slow, obvious motion at the scapulaSTAND ON THE BLIND FACE — the arc its palm cannot be turned to reachpositioning
BOTH HANDS TAKE THE SAME PURCHASE AND THE BODY DRAWS UPboth flexor masses load together, the lumbar chain goes from tension into a short compression, and the whole frame shortens before it releasesDODGE — this is a whole-body drop and it commits utterly; nothing about it can be metdodge only
THE DIGIT CHAINS OPEN AND THE HAND IS PRESENTED FLATthe added fourth segment is held at 0 and the palm is offered as a contact surface, because it means to take hold of what comes into itPARRY — a presented contact surface is meetable, and meeting it costs the grip its lockparry only
WORLD TELL — THE DRAG-TRAIL STOPS AND THE DUST SETTLESnot on the creature at all: the two-line trail in the dust ends, which means the body has left the ground economy for the verticalBREAK THE VERTICAL LINE — get off the wall-side of the street and into open ground it cannot crossread

ONE SHAPE, ONE ANSWER throughout, across four distinct counter classes plus one world read. Shapes 1

and 3 both load the flexor masses and they are deliberately not confusable: one hand against two is a

count a player reads instantly in black fill, and the answers are opposite in kind (close against

give ground), which is exactly the cross-shape lesson the set is built to teach.

6.5 Escalation, on all four channels

wrong direction for the player: a being hanging by one hand is at its MOST dangerous, because the

other three limbs are all free. That is a state a player can name out loud before any meter

confirms it, and it inverts the intuition the first minute of the fight built.

as a passive consequence of the haul, pulled by the shoulder girdle, because nothing inside is

driving it. In the escalated state it moves on a rhythm of its own that the haul does not explain.

Nothing is added to the mesh; a passive motion becomes a driven one, and it is the first evidence

the thing has an inside.

the fourth phalanx locking on stone, one per plant, which is how a player learns to track it

without seeing it. The escalation is that the clicks stop being sequential and become SIMULTANEOUS,

and the meaning of that is unambiguous: there is more than one. The cohort arrives in the mix

before it arrives in the frame.

from directly overhead onto the player's own line, and the whole listening method built in the first

minutes stops working because the sound is no longer beside the player.

6.6 Relocation and turf

IT OWNS THE VERTICAL, NOT A ROOM. It enters along wall-lines, kerb-stones, cart-rails, gate-jambs,

tree-forks and eaves; it leaves along the same; and **it cannot cross open ground that offers no

purchase.** An open square, a bare threshing floor, a swept court and the middle of a wide road are

denied to it by its own anatomy rather than by an invisible wall, and a player who works that out has

been given a real tool by the design rather than by the level. It does not defend a place and it never

guards anything, which is a second hard discrimination from the asura, whose whole nature is holding

a stretch of ascent [CR_0177_soorasamharam_remnant.md § 6].

6.7 Chain meter

NONE IS AUTHORED, AFFIRMATIVELY. No canon row rules a non-kill path for this register, no BE_ row

carries pip_count or pip_reveal_threshold for it, and a design lane may not mint either. The

encounter's meter is physical and HUD-free: the contact count of § 6.5 and the trail of § 4.2 are both

readable states, and a player can tell how the encounter is going without looking away from it.

6.8 Agency

A moveset it chooses from, a geometry it owns and the player must take from it, a state it escalates

into on its own body, and a lethal intent it acts on. It is never staked out, never asleep, never

waiting to be visited and never defenceless — the failure Josh named by name. Where it appears at all,

it comes to the player.

6.9 STAGING — DIRECTOR-RULED, WQ_0031 L14, AND THE BLOCK THAT BINDS EVERY LANE DOWNSTREAM

**THE RULING, ON THIS SHEET'S FACE AND IN ITS SUBSTANCE. THE PEY AND THE BHUTAM ARE FACED IN CHAPTER 7

AT THE AMBIENT-HOSTILE REGISTER: a real, lethal, UN-ROWED encounter that comes to the player on its

own schedule.** [DIRECTOR-RULED, WQ_0031 L14.] The reasoning is the ruling's own and is recorded here

rather than re-derived: CH_07.md:114 forbids a ROWED encounter — its own parenthetical "(no registry

row)" is what defines the term on that line — and it is SILENT on un-rowed ambient hostiles. What

governs the silence is the roster row's own cells (combat_permission FOLKLORE_FACED; collect_verb

DOCUMENT;FIGHT), the spine's asset line at CH_07.md:269 staging this register "faced as the tradition

condemns them", and the ratified CR_0160 precedent, which staged a full ambient-register night

encounter on canon language weaker than this row's and minted no BE_ row (§ 1.1). Sections 6.2 through

6.8 are therefore CH_07-LIVE at this register. The canon line is quoted in full and is not

paraphrased, because everything below is a reading of it:

"ambient threat (no registry row): the pey/bhutam malevolent-spirit register rides the folklore
layer as ambient substrate, drawn as the tradition holds it, never a rowed encounter"
[CH_07.md:114]

WHAT IS STAGED IN CH_07, and both halves are real. THE AMBIENT SUBSTRATE, unchanged and still the

first thing the player meets: a two-line drag-trail in the dust of a roadside at first light, a dry

click from a wall-line that stops when the player turns, a shutter closed on a street where every

other shutter is open; the register named in the SQ1 lore the chapter pays out [CH_07.md:227;

@ SEED_0030 :: canonical_outcomes], read as L2 investigatable lore [CH_07.md:264], with the

tradition's own protective register standing against it as the region page records it

[south_india.md:432-433, :438-440]. AND THEN THE CONTACT, which the substrate is the approach to:

the encounter of §§ 6.2-6.8, at NIGHT and at LOW WITNESS, on unfirewalled ground, arriving on the

creature's schedule rather than the player's. The substrate is not replaced by the contact and the

contact is not decorated by the substrate; the first is how the register is learned and the second is

what it is.

THE FIREWALL, AND THE DEFINITION IS RULED RATHER THAN CHOSEN BY THIS SHEET. Nothing here is staged

on firewalled ground, where firewalled means what docs/COMBAT_ENCOUNTER_SYSTEM.md:309 says it means,

quoted: "The firewall is protected_care_ref naming any hard line or vril site, or

alteration_permanence_default reading hard_blocked. It is deliberately NOT env_boss_verb_disabled

... the column governs what a boss may weaponise back, never whether the surface has verbs at all."

THE IN-CHAPTER PROOF OF THAT COLUMN'S REAL MEANING IS IN THIS CHAPTER AND IS ALREADY LANDED:

BE_0007_S3, the chapter's one rowed mythic-being fight, stages on EG_0088, which carries

env_boss_verb_disabled TRUE. A flag that a landed boss fight sits on top of cannot be the flag that

decides whether a surface may carry a fight. The earlier draft of this block read it as exactly that

and the reading is struck.

FIREWALLED AND THEREFORE REFUSED, each verified cell by cell against the live rows, and the sacred

sites are "referenced not reproduced" [CH_07.md:93, :97, :103]:

hard_blocked. @ EG_0077 walled temple precinct court and ambulatory — HL_0001;HL_0007,

hard_blocked. @ EG_0078 temple-city street frame, the protected precinct fabric — HL_0001,

hard_blocked. @ EG_0079 consecrated tower mass and monolithic capstone — HL_0001;HL_0007,

hard_blocked. @ EG_0082 sunken kalari pit floor — HL_0001;HL_0007, hard_blocked. @ EG_0088

abode-hill pilgrim ascent way — HL_0001;HL_0005;HL_0007, hard_blocked. @ EG_0089 abode summit

shrine court — HL_0001;HL_0007, hard_blocked.

LEGAL GROUND, ENUMERATED AFFIRMATIVELY SO THE STAGING IS CHECKABLE RATHER THAN VAGUE, and every one of

these clears both firewall teeth on its own live cells:

alteration_permanence_default transient_combat.** It carries env_boss_verb_disabled TRUE and

that is not a firewall, per the ruled definition above. This is the chapter's one alterable

community ground and its own row says why it exists: the split was minted at apply time because

hard-blocking it "would have left the chapter with zero alterable community ground - care-tier

inflation, the named defect," and the row is a declared RUNG-3 precedent whose content is that "with

no firewall and no attested livelihood on the ground, refusing is the timid read and the timid read

is the defect" [@ EG_0093 :: notes]. It is a wall-and-frontage surface, which is a purchase

economy by construction (§ 4.1).

alteration_permanence_default heals_over, env_boss_verb_disabled FALSE.** The chapter's declared

WILD ground and "the only surface in it that may carry a scar" [@ EG_0090 :: notes], gravity-loaded,

with the gully cut and the flank's own rock as the purchases.

@ EG_0020 montane forest understory (CONCEALMENT, enemy_usable TRUE, care none, heals_over) and

@ EG_0012 forest canopy bough network (TRAVERSAL_SURFACE, care none, heals_over) — a purchase

economy by construction.

**THE SITE ROWS' ambient_threat LABELS DO NOT BAN THIS, AND THE READING IS THIS RULING'S RATHER THAN

CANON'S OWN WORDS.** Five CH_07 sites read low and two read moderate with the moderate named

[CH_07.md:101, :103]. The ruled reading, attributed here so no later lane cites canon for it: those

cells DESCRIBE EACH SITE'S ROWED STAGING — which typed encounters the site hosts — and they are not a

declaration that no un-rowed hostile may ever be present on that ground at night. The earlier draft of

this block argued the opposite, calling the absence of spare budget "the sharpest argument on the

sheet"; under this ruling that argument is struck, because it read a rowed-staging label as a

presence ban and no canon line says it is one. NO SITE ROW IS EDITED OR MINTED BY THIS LANE, and

none needs to be: an un-rowed register does not consume a site's threat budget, which is what makes it

un-rowed.

WHAT REMAINS FORBIDDEN IN CH_07, absolutely, and each is a thing a downstream lane might otherwise do:

this register's. The encounter is never a beat's content and never gates one.

rng_drop_anchor dangle is boarded rather than resolved (§ 9).

precinct, the gate, the tower mass, the pit floor, the ascent way or the summit court, and never on

any protected site in any chapter.

[south_india.md:505-510]; and never through a person, a house or an accusation, per § 7.

craft-street at trading hour would put the protected community in the frame, which § 7 forbids on

its own terms.

**A LANE THAT MINTS A BE_ ROW, A BEAT, A FORK OR A SITE ROW FOR THIS REGISTER HAS CONTRADICTED

CH_07.md:114, AND A LANE THAT STAGES IT ON FIREWALLED GROUND HAS CONTRADICTED THIS BLOCK. A LANE THAT

REMOVES THE CONTACT ALTOGETHER HAS CONTRADICTED THE RULING ABOVE, AND THAT IS THE DEFECT THIS BLOCK

WAS REWRITTEN TO STOP.**

7. care_read

the Tamil and Malayali communities, the Siddhas, the kalari and temple communities, the smiths and

healers and the honored Raghavendra "are allies and protected non-targets" [CH_07.md:252;

south_india.md:406-408, :546-553]. The read here is stronger than neutral — in this design the

tradition is the side that HONOURS its dead with a name and a stone [south_india.md:359-362] and

installs its protective deities around every space it uses [:432-433]. The community is the ward,

never the source.

spirits and the tradition itself wards them, so facing them villainizes nobody and the community is

the party being protected FROM them. The register is "rendered exactly as the tradition condemns

them, never softened, never hollywood-horrored and never flattened into generic movie ghosts"

[@ CR_0179 :: cultural_care_register]. Mythologically-stylized is a canon ruling on this being

specifically [CH_07.md:271] and is held: stylized for this one, realistic-ethnographic for every

community, temple, forge and kalari beside it.

suspicion is never routed through a named or living person, no accused and no afflicted person is

ever offered as a target, and the monstrous register stays on the spirit and is never a physiognomy

laid on real people [@ CR_0179 :: cultural_care_register]. Applied without exception: **NO NPC IS

EVER HINTED TO BE ONE, NO POSSESSION IS EVER STAGED, NO HOUSE IS EVER POINTED AT, NO ACCUSATION IS

EVER AN OBJECTIVE, NO AFFLICTION DIAGNOSIS IS EVER A MECHANIC.** The being is its own body from the

first frame and there is nothing behind it that belongs to a person — the Flores wa and CR_0160

krasue precedent applied where it binds hardest, and the reason § 5's body is a complete independent

skeleton rather than a person with something wrong with them.

SITS AGAINST IT RATHER THAN CLAIMING A CLEAN SWEEP OF SIX.** The row forbids authoring a habit,

etiology, possession mechanism, diagnostic, iconography or rite AS THE TRADITION'S OWN, beyond the

spine's words [@ CR_0179 :: folklore_attribution_source]. This sheet authors no habit, no

possession mechanism, no diagnostic, no iconography and no rite. **IT DOES AUTHOR AN ORIGIN FRAME

AND THE FRAME IS DECLARED HERE AFFIRMATIVELY AS THE GAME'S OWN: the hero-stone INVERSE of § 3** —

the dead that got no name, no stone, no locality and no propitiation. That is an etiology-class

statement, it is kept because it is the best thing on this sheet, and denying it would be the sheet

hiding an authored thing inside a disclaimer. It stands on HL_0002's fantasy licence, quoted in

full in § 3, which licences exactly this: a mythic monster grounded in the tradition's own material

and free to extrapolate for playable spectacle. **IT IS THE GAME'S ORIGIN FRAME FOR THE GAME'S

REGISTER AND NEVER A CLAIM ABOUT WHAT THE TAMIL TRADITION HOLDS** — no dex entry, bark, NPC line or

lore fragment written off this sheet may present it as the tradition's teaching, and § 8's plates

carry no inscription, stone or marker that would.

the distinction has to be stated or anti-timid pass 3 reads as special pleading.** The two fail

different tests. The battlefield-dead and blood-drinking framing is an EXTERNAL TRADITION CLAIM: it

would put a habit into a living tradition's mouth that this corpus attests nowhere, which is

cited-or-cut and the anti-fringe adjacency this region specifically guards

[south_india.md:1267-1269]. The hero-stone inverse imports nothing from outside: it is built by

INVERTING two institutions this corpus does carry at technique grain behind SRC_00262 — the

Sangam-age hero-stone deification and its Kerala continuity [south_india.md:359-362, :454-455] —

and an inversion of a cited institution asserts nothing about what anyone believes. The rule the two

cases share, stated once so a later lane can apply it rather than re-argue it: **THE GAME MAY AUTHOR

ITS OWN FRAME AND MAY NEVER AUTHOR SOMEONE ELSE'S ATTESTATION.** If a Tamil-side source lands and

attests an origin for this register, the attested one supersedes ours in place.

temple interior, worshipped image, hero-stone or ritual text is an asset, prop or mechanic; the

hero-stone institution is the design's cited ARGUMENT and never a thing the player handles; and the

page's hardest authoring rule binds — "no information is provided which any master requested remain

secret" [south_india.md:499-500].

inviolate, both typed HONORED_inviolate on the chapter index's folklore cell, and no deity name is

ever pinned onto a familiar or NPC — which is why the F2 peacock is PARAVANI [CH_07.md:335]. Nothing

in this design touches a deity, abode, precinct or vahana, and the peacock never enters this

register's frame.

vril-signature read; the substrate-perception onset waits at the Ch-15 crossing [CH_07.md:17, :281;

HL_0028 / HL_0017]. The player reads a trail in dust and a click on stone — craft-grade evidence,

not sight.

photographic-wildlife-template risk and the region page removes the excuse: "the shelf carries NO

zoological or ecological source for this region," so the page "authors no hunting mechanic, no

habitat rule and no population claim" [south_india.md:217-221] — a lane reaching for a wildlife

template here is reaching for a shelf that does not exist. It never routes through a

photographic-HUMAN template either, because a human-shaped being of a living tradition's

condemned-spirit register must never carry a real person's likeness. mesh_pipeline_type reads

image_to_3d, the concept-plate-then-mesh route, compatible provided the plate is attended; the

style cell MATCHES CH_07.md:271's exclusive list, so there is no style mismatch to board.

possession road — the register's most familiar and most dramatic form, and the one that puts an

afflicted person in the frame. Nothing was removed. The AIM was moved: off any person and onto a

body of the register's own, which is why the being is a complete independent skeleton and why the

encounter has no house at the end of it.

1. **SHOULD CHAPTER 7 CARRY UN-ROWED HOSTILE CONTACT FROM THIS REGISTER, OR ONLY ITS ATMOSPHERE?

THE BOLD READING WEIGHED AND TAKEN — DIRECTOR-RULED, WQ_0031 L14 — AND THE EARLIER DRAFT'S ANSWER

RECORDED AS THE TIMID ONE.** This is the question the pass actually had to answer, and the pass

as first run did not answer it: it asked instead whether the BEING should be designed, refused

the reduction to weather at the DESIGN layer, built the whole fight grammar — and then took the

reduction back at the STAGING layer by ruling the register un-encounterable anywhere in the

chapter. A REFUSAL THAT HAPPENS IN § 6.9 INSTEAD OF § 4 IS STILL A REFUSAL, and it is the

harder kind to see because it wears a canon citation and reads as discipline. That is the timid

direction, recorded as such rather than repaired quietly. THE RESOLUTION: CH_07.md:114 forbids a

ROWED encounter by its own parenthetical and is silent on un-rowed ambient hostiles, so the

register IS faced in this chapter at the ambient-hostile register, at night, on unfirewalled

ground, with no BE_ row, no beat, no fork and no site row (§ 6.9). Three grounds carry it — the

live combat_permission FOLKLORE_FACED with combat_facing TRUE, the collect_verb cell's own

FIGHT token, and the spine's asset line staging the register "faced as the tradition condemns

them" [CH_07.md:269] — plus the ratified CR_0160 precedent, which did the same thing on weaker

language. The standing calibration decides the direction and is quoted because it is the reason:

erring toward omission is the MORE costly error, not the safer one, because the call is

reversible and Josh is the backstop — while a staging refusal is invisible to every downstream

gate, so nothing would ever have caught it.

2. **IS THE DESIGN BOLD ENOUGH FOR R-17, OR IS A CLIMBING SKELETON A SAFE ANSWER? THE BOLD DIRECTION

WEIGHED AND TAKEN.** The register is softened nowhere: it is lethal, it hunts, it comes to the

player unasked, it arrives in numbers the player is never told, its escalation is the discovery

that there are more, and its central physical fact is a thing that means to take hold of a person

and can. The one restraint applied is a citation restraint rather than a care restraint, and pass

3 names it.

3. **SHOULD THE CORPSE-FIELD REGISTER HAVE BEEN BUILT — the battlefield-dead framing the wave brief

supplied? NOT REFUSED AS TOO STRONG; NOT BUILT, FOR A CITATION REASON, AND THE SHEET SAYS WHICH.**

Nothing in that register is too dark for this bar. It is not built because this corpus attests it

nowhere: the negative control returns zero, the Tamil-side source is an OPEN acquisition gate

[south_india.md:1282-1283], and the row declares a ceiling forbidding an authored etiology.

Authoring a blood-drinking habit as the tradition's claim would breach cited-or-cut and would be

an invention wearing the tradition's authority — the adjacency the anti-fringe rule guards in

exactly this region [south_india.md:1267-1269]. What is built instead is the hero-stone INVERSE

(§ 3): grounded in a real SRC_00262 institution, at least as dark, and costing nothing in weight.

**AND THE INVERSE IS ITSELF UNCITED, WHICH THIS PASS STATES RATHER THAN LETTING IT PASS AS THE

CITED OPTION.** The two are not treated the same and § 7's disposal says exactly why: the

battlefield-dead framing would author SOMEONE ELSE'S ATTESTATION, while the inverse authors THE

GAME'S OWN FRAME by inverting institutions this corpus does cite, and it is declared in § 7 as an

authored origin frame under HL_0002 rather than denied. **IF A TAMIL-SIDE SOURCE LANDS AND

ATTESTS THE BATTLEFIELD-DEAD REGISTER, IT IS BUILT, § 4 IS SUPERSEDED IN PLACE RATHER THAN

DEFENDED, AND THE ATTESTED ORIGIN REPLACES OURS.** § 9 boards it.

4. A PASS RUN TOWARD MORE CARE, WHICH FOUND SOMETHING AND TOOK IT. The bold instinct is the

possession form — the register's most dramatic shape, and the one that would give the encounter a

face. REFUSED, cost exact: it puts an afflicted or accused person in the target position, which

the row forbids in terms and which the Flores and Khmer precedents both settled. It is also worse

design — a hunt with a house at the end ends in an accusation; a hunt with no house ends in the

dark with the thing itself. Care answer and design answer coincide, which is usually the sign the

reframe was the right tool.

archetype choice for this row; the grip hypertrophy and the whole-body atrophy; the added fourth

phalanx, its 0-90 hinge and its lock; the weight path through the clavicle-strutted girdle; the

reduced ±55 pronation ceiling and the blind face it produces; the no-support gait and the drag

trail; the tension-lengthened spine and the taller-hanging state; the mineral crust and its three

regional forms; the never-singular cohort read; the five tell shapes and their answers; the

contact-count, driven-breath, simultaneous-click and drop-from-above escalations; the purchase

geometry and the open-ground denial; the HOLD/DENY verbs; the gait_sequence brachial substitution;

and the hero-stone-inverse ORIGIN FRAME, which § 7 declares affirmatively as authored rather than

filing it under "no etiology". **NOT INVENTED BY THIS SHEET AND NOT ITS TO REOPEN — the CH_07

ambient-hostile STAGING is DIRECTOR-RULED (WQ_0031 L14, § 6.9)**, as is the firewall definition it

applies [COMBAT_ENCOUNTER_SYSTEM.md:309]; this sheet implements both and argues neither.

CITED, and every one of these is canon or corpus: the register's existence, its two names, its

condemned status, its ambient grain, its mythologically-stylized style ruling, its SQ1 payload, its

Neophyte tier discipline, the Sangam hero-stone institution and its Kerala continuity, the kalari's

protective perimeter and the puttara, the region's dead-honouring performance culture, the shelf's

zoological absence, and the anti-conflation partners. DERIVED: every joint, range, segment

count, gait formalism and rig-conformance floor from HUMANOID.json, carried as passive-envelope

bounds and reduced in exactly one place, never expanded.

plates and design blocks only. The constraint inherits forward to every lane that later writes a

display name, dex entry, bark or item text from this material: the chapter's reveal_state is HELD

[CH_07.md:301], no House-of-Velheim name, family or pattern appears on any surface, Raghavendra's

UNAWARE status is untouched and he is not in this material at all, the Grand Sage is dark, and the

Sealed Letter's fairy-realm script is deliberately NOT identified before the Ch 8 reveal

[CH_07.md:115]. Nothing in this design identifies the script, the family or the letter, and nothing

in it can: the being has no text, no sigil, no inscription and no carried object of any kind.

8. plate_brief

Written affirmatively. Every line names what IS in frame, because the art graph zeroes its negative

conditioning and a line naming what to leave out feeds the model the nouns it meant to exclude.

country, held by both hands at chest height, its legs straight and still beneath it, the frame thin

everywhere and the two hands and forearms visibly the largest things on it. A cook-fire further down

the road is the only light in frame and it catches the dust crust packed into the rib spaces.

Mythologically-stylized register.

finger with the terminal segment locked flat at ninety degrees, the flexor mass of the forearm

bulked above it, and the stone's own texture where the grip sits.

across the path, the whole body's weight hanging from the other arm, the spine lengthened under

tension, the scapula of the loaded side riding high against the frame.

hand along a kerb-line with both legs trailing behind it and the two-line drag trail written in the

dust behind that — the sign-read and the body that makes it, in one frame.

distances, at three different mineral crusts (laterite red off @ EG_0090, pale plain dust off the

dry interior, and the craft-street soot of @ EG_0093 — the trade-home frontage, never the

protected precinct frame of @ EG_0078), so the count read and the regional state ladder land

together.

reach, the two-hand draw-up, and the ground haul, all four at one scale — judged in black fill alone

for whether the hands read oversized, whether the reach reads distinct from the draw-up, and whether

the frame reads as person-shaped and person-empty at the same time.

the dust. Every plate is set on ordinary unconsecrated ground — a roadside, a street-edge, a gully

flank. The frame holds the being, the surface it grips and the light already in the scene.

9. boarded_debts

Registry implications this sheet found and did not write. Each names its target row and column.

HIGHEST-PRIORITY REPAIR.** The cell reads FOLKLORE_FACED. The same row's notes say

"combat_permission DELIBERATELY BLANK on the CR_0160 rule ... FOLKLORE_FACED is REFUSED on this row

and should only ever be written if a later spine pass stages an encounter" — and then, further down

the same cell, the AMBIENT-HOSTILE (B22) append rules the being fightable without a BE_ row. The

append supersedes the earlier sentence and the written cell agrees with the append, so the ROW is

correct and its PROSE is stale in one clause. No gate can tell the two apart, and a lane reading the

notes top-down will conclude the permission cell is an error. REGISTRY LANE: strike or

supersede-in-place that sentence so the cell and its rationale agree.

cell reads DROP_CH07_PEY_BHUTAM_AMBIENT_RESIDUE; the notes say "rng_drop_anchor BLANK BY

DESIGN"; and a scan of T0_RNG_Drop_Table returns NO ROW WITH THAT ID. Three states, one row. § 6.2

designs no material payload because of it. REGISTRY LANE; the decision is genuinely open — either

the drop row lands or the anchor clears.

AND THIS SHEET TAKES NO SIDE, EXACTLY AS IT TAKES NONE ON THE OTHER TWO.** The cell reads

DOCUMENT;FIGHT. The same row's notes read "collect_verb DOCUMENT and dex_completion_class WITNESS

follow CR_0160 exactly, the un-bossed folklore-touch pairing" — a two-token cell against a one-token

rationale, with the FIGHT token unexplained anywhere in the note. Either the note is stale in one

clause the way the combat_permission note is, or the cell carries a token nothing in the row

authorised; both readings are live and this lane cannot tell them apart from outside the row.

REGISTRY LANE. Boarded together with the two above rather than separately, because **three

cell-versus-notes disagreements on ONE row is a row-level repair rather than three cell fixes**, and

a lane reading that notes cell top-down will conclude all three cells are errors.

creature_archetype_map.json places it in NEEDS_CANON_BODY_PLAN and every bucket scopes those rows

out [HUMANOID.json § scope]; mesh_tags.morphology reads "folklore", a provenance word standing

where a body plan belongs. THIS SHEET PROPOSES HUMANOID as its own declared design choice (§ 2)

and writes nothing. The rig-conformance gate has nothing to check against until it lands — and when

it does, it will flag this row on exactly one field, gait_sequence biped_alternating, which

§ 2 declares as a deliberate substitution (an alternating BRACHIAL cycle on the arm chains) rather

than a lowered floor. Boarded here so the flag arrives as a known departure with a stated

substitution rather than as a discovered defect.

"FOLKLORE_FACED currently implies a staged BE_ row, which is why this row had nowhere to land;

decoupling fightable from boss is a registry-schema item this row is the first consumer of"

[@ CR_0179 :: notes]. CR_0160 is the same shape from the other side, permission cell blank

instead of written [CR_0160_krasue_ap.md § 9]. Two rows in two chapters now need a

fightable-without-a-boss tier the schema cannot express. REGISTRY-SCHEMA LANE — and the related want

is a STAGING SCOPE field, so that "rowed" and "un-rowed but faced" stop having to be reconciled in

prose on every sheet that touches such a row. **THE DIRECTOR'S RULING (§ 6.9) MAKES THAT WANT SHARPER

RATHER THAN SOFTER:** the ruling holds in prose, on this sheet's face, and no cell anywhere in the

registry records that this register is faced un-rowed in CH_07 — so the one thing a later lane most

needs to know is the one thing no gate can read. Proposed as an extension-column question, never as

an edit; § 1.1 and § 6.9 hold it in prose meanwhile.

temple polychromy, laterite, Ghats green", the chapter's architecture-and-craft palette

[CH_07.md:271] pasted onto a being canon places on a roadside. A generator reading the cell is being

fed the forge and the gopuram. The identical string sits on CR_0039, CR_0177 and BE_0007_S3;

CR_0177's sheet boards the same class, so this is a chapter-wide paste rather than a row error.

"Composite � Tamil Sangam through medieval Siddha tradition" — verified live on this row this

pass, the same encoding defect CR_0177's sheet reports on CR_0039 and CR_0177, and also the

chapter's era string pasted onto a being with no era.

the Folklore Combat line (live: L1078-L1080) and L1255-L1256 for the § 16 acquisition gate (live:

L1282-L1283 for the Tamil-side source; L1280-L1281 is the Murugan gate). Every citation in this

sheet uses the verified current line, so sheet and row disagree on anchors until the row is

repaired. Same systematic class CR_0177's sheet boards. REGISTRY LANE.

MUST-ACQUIRE gate is live at south_india.md:1282-1283. Until it lands the citation floor is canon

prose plus the cited regional institutions of § 3, and anti-timid pass 3 states exactly what gets

rebuilt the day it does.

on at all. Five tell shapes across four counter classes plus one world read have no data home — the

same finding CR_0160's sheet reports, now measured twice in the un-bossed class.

(§ 6.1), named as ours because verb cells live on boss rows and this row has none. If the

ambient-hostile tier gets a schema home the verbs go with it; until then they are design prose and

no lane should read them as canon.

tier_classification, trophic_role and scientific_name on the cryptid-firewall and

attestation-ceiling reasoning; thread_anchor because no beat threads this register and claiming a

neighbouring beat's thread is forbidden; familiar_slot_eligible, trade_8_tameable,

temperament_prior, spawn_rate, every husbandry cell, rare_variant and extinction_threat per

the folklore precedent. Each is a decision, not a hole.

10. the ten refusal tests, self-run

archetype is a human skeleton with an added phalanx on every digit, a hypertrophied flexor mass with

a reduced pronation ceiling, an atrophied weight-bearing system that cannot stand, a gait with no

support phase at all, and a mineral crust in the joint hollows. A photograph of a person contains

none of the five.

distal to the existing distal phalanx, on ten named digit chains, as a pure hinge at 0-90 with zero

extension, abduction or rotation, and § 5 traces the weight path from that segment through the

metacarpals, flexor mass, radioulna, elbow, glenohumeral joint and the clavicle-strutted

scapulothoracic girdle. The root chain is derived from HUMANOID.json with every joint, range,

segment count and conformance floor named; the one modified range is REDUCED, never expanded; and

the one conformance field the design departs from — gait_sequence biped_alternating — is named in

§ 2 with its substitution stated and boarded in § 9, rather than omitted from the derivation list.

The dust crust is RETURN from a light already in the scene and the frame reads by occlusion against

lit stone; § 4.4 names the banned classes explicitly and refuses all of them.

reach, the two-hand draw-up and the ground haul are four distinguishable poses; the two hands are

the largest features on the outline and read at any range; and the wind-up (both hands loaded, frame

shortened) is distinguishable from the idle (both hands loaded, frame long) by the length of the

body itself. Both breakable parts are outline features at ~0.09 and ~0.06, and a hand that will not

lock is visible as a changed haul rather than as a HUD state.

world read. The two shapes sharing a body system (one hand versus two) are separated by a count a

player reads instantly and carry opposite answers in kind, which § 6.4 names as the intended

cross-shape lesson.

from it, a four-channel escalation on its own body, a lethal intent, and an entry that comes to the

player rather than waiting to be visited. It is never defenceless and never staked out.

own earlier failure of this very test rather than concealing it** — one taking the bold reading on

un-rowed hostile contact and naming the earlier draft's staging-refusal as the timid answer it was,

one weighing and taking the bold direction on register, one distinguishing a CITATION restraint from

a care restraint and naming what lands the day the source does, and one running toward more care and

taking its finding (the possession refusal).

uncited element carries an invention declaration in § 7, the HL_0002 fantasy licence is quoted as the

ground for the designed body and for the ONE authored origin frame § 7 declares affirmatively, and

both controls run and are reported: positive (SRC_00262, the shelf keystone, quoted six times) and

negative (zero "pey" and zero "bhutam" occurrences in the region page). The region page's own

counter-line at :505-508 is named and disposed rather than avoided.

reveal token appears anywhere; Raghavendra is not in this material; the Grand Sage is dark; the

Sealed Letter's script is not identified and cannot be, because the being carries no text, sigil,

inscription or object of any kind.

wildlife failure mode named and refused with the region page's own zoological-absence line behind

it; the photographic-human failure mode named and refused; image_to_3d verified as the

concept-plate-then-mesh route; and the style cell verified against CH_07.md:271's exclusive list

with no mismatch to board.

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