BE_0002_S1_the_kelimutu_guardian.md

creatures/BE_0002_S1_the_kelimutu_guardian.md

BE_0002_S1 — the Kelimutu Guardian, the encounter: two bodies, one test

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):

T0_Boss_Attack_Rail · T0_Boss_Encounter_Registry · T0_Creature_Roster · docs/spine/CH_02.md · _source/02_Tier_2_Region_Pages/flores_island.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. The two bodies are designed on their own sheets

(CR_0001_wae_guardian_land_aspect.md, CR_0002_naga_tana_water_aspect.md); this sheet designs the

ENCOUNTER — how a two-animal guardian test reads, teaches, escalates and ends.

1. identity

• canon_id: BE_0002_S1
• canon_name: The Kelimutu Guardian (Komodo dragon / reticulated python)
• display_name: the Kelimutu Guardian
• chapter: CH_02, beat CH02_B03, seq 4, role core, mode combat
• region: flores_island · site recharge_waterfall
• boss_kind: sub · target_type fauna · care_tier standard
• primary_verb: evade · secondary_verb: strike · axis_split 30/45/25 (puzzle-forward)
• has_nonkill_path: TRUE · pip_count 5 · pip_reveal_threshold 1.0 · defeat_protected FALSE
• win_condition: PURGE;REDUCE · win_shape standard
• composure_nodes: puzzle_routed=constriction_lane_step · environmental=breath_rhythm_attune
• ws_writes: ws.serpent_reverence_marks (fought route only)
• register: ENCOUNTER
• rows_read: T0_Boss_Encounter_Registry @ BE_0002_S1 · T0_Creature_Roster @ CR_0001, CR_0002, CR_0005 · docs/spine/CH_02.md CH02_B03 and the serpent-reverence track · _source/02_Tier_2_Region_Pages/flores_island.md § 3

2. base_species

Two, and the encounter's whole identity is that they are not the same kind of body:

• CR_0001, a sprawling quadruped that tracks by sight and scent, turns its head by turning its

shoulders, and commits its whole mass to every attack.

• CR_0002, a limbless three-hundred-joint body that tracks without sight, has no centre to read, and

attacks by closing a shape the player is already standing inside.

The design consequence: the player cannot use one lesson on both. Everything that works on the

monitor — break line of sight, watch the head, punish the recovery — fails against the serpent, and

everything that works on the serpent — read the ground, leave the disc, never freeze — fails against

the monitor. THAT IS THE ENCOUNTER. It is the arc's first fight and it teaches, in one beat, that

reading a body is the game.

3. lore_source

• The pair is Thread 2's dual anchor and Thread 15's twin duality: the Komodo as apex predator of

land and the python as water-and-earth serpent, the thread's most physical chapter

[docs/spine/CH_02.md Thread 2, Thread 15].

• The framing is a GUARDIAN TEST that opens the recharge source, never a hunt of a protected animal —

and that framing governs staging and quest design, not player agency: the win never requires a kill,

and it never hardens into an animal that cannot be killed [flores_island.md § 3, quoted on the row's

own sources cell].

• The serpent half carries a living Manggarai tradition and its own sheet cites it. The land half

carries none and is ordinary fauna. The encounter therefore has an ASYMMETRIC care shape, and

section 7 states it rather than averaging it.

4. elevation

The two bodies carry their own axes. The ENCOUNTER's elevation is the pairing itself, and it has one

mechanism: ONE SPRING MADE BOTH OF THEM. The monitor wears the water as a chalk crust on its

underside; the serpent wears the ground as packed moss in its forward third. Same source, same

decades, two materials. A player who never learns a word of the lore still reads that these two

animals belong to this water, because the water is visibly ON them and on nothing else in the zone.

ONE-LINE ENCOUNTER READ: two old animals that have been here longer than the path has, wearing the

spring in two different materials, sharing a piece of ground neither will leave.

5. articulation_delta

Per body, on the body sheets. The encounter adds one shared rule: THE TWO NEVER OCCUPY THE SAME

GROUND. The serpent owns the water and the wet rock, the monitor owns the dry bank and the shallows'

edge, and the boundary between them is a real line on the arena floor that the player can see and

use. Crossing it is how the player buys a beat: standing in the water makes the monitor hesitate at

the margin, standing on dry stone puts the player outside the lane the serpent can close. Neither

animal follows the player onto the other's ground until the escalation.

6. fight_grammar

THE TEST IS VISIBLE FROM THE FIRST SECOND. pip_reveal_threshold is 1.0, which is the row saying

this is a test rather than a fight-first boss. The chain is five correct reads and a mistake wipes

it. The doctrine's defang tell is checked here explicitly: a guardian test is not a passive encounter,

it is a HARDER one, and this encounter is built to be harder than the fought route it sits beside.

THE FIVE PIPS, EACH A NAMED READ. Every pip is a body state the player answers, and the two animals

alternate so neither lesson goes stale:

1. The serpent's lane load — step across the loading side before the arc closes.

2. The monitor's gular pump — hold still through one full cadence at close range, which is the

opposite of everything the previous read taught.

3. The serpent's double load — one arc is a feint; read the ridge, not the arc.

4. The monitor's tail-sweep pivot — step INTO the pivot, not away from it.

5. The paired beat — both animals commit at once, and the only answer is the ground: cross the

boundary line so the monitor breaks at the margin and the serpent's arc closes on empty rock.

Complete the chain and the pair WITHDRAWS: the serpent unloads and slides under, the monitor drops off

its high walk and moves off the bank, and the source opens intact. That is the puzzle route, it costs

nothing, and it writes nothing.

THE FOUGHT ROUTE IS A REAL FIGHT AND IT IS NOT A PUNISHMENT. Fighting them down in the shallows opens

the same water and costs one ws.serpent_reverence_marks. Both are wins and the mark is the price of

the easier one, which is the beat's own sentence. The hide and claw come off the monitor

(DROP_BIGGAME_HIDE_MEAT). The mark is not an integrity tax and never touches ws.integrity_score.

SHAPE-TO-ANSWER, ENCOUNTER-WIDE: no shape carries two answers across the pair. The audit is worth

stating because a two-body encounter is exactly where a collision hides — the monitor's lunge and the

serpent's head strike are both a straight-line commit toward the player, and they are deliberately

DIFFERENT SHAPES: the lunge drops the whole body into a crouch first and travels along the ground; the

head strike falls from a raised S and travels down. Crouch-then-forward against raised-then-down. If a

build ever makes those two read alike, the encounter has lost its one-answer property and this line is

the ruler that catches it.

ESCALATION — the boundary breaks. The four channels are on the body sheets; the ENCOUNTER's escalation

announcement is spatial and it is the single most important beat in the fight: at the phase turn, the

monitor comes off the bank INTO the water. The rule the player has been using for the whole first

phase stops being true, and they can see it stop being true before any meter says so. The serpent

answers by taking the dry rock. The arena has inverted.

OPENER: the encounter leads with the serpent's lane load, because it is the safest thing either animal

does and the whole grammar of reading a loading body starts there.

RELOCATION AND TURF: the smaller monitors crowded at the fed spring (CR_0005 and juvenile

conspecifics) are present, they scatter when the guardian moves, and the guardian will break off the

player to displace or take one — canon's own sentence, and the encounter's free third party. A planted

carrion lure pulls it off the bank entirely and hands the shallows to the small ones for as long as

the bait holds.

WHAT THE PLAYER TAKES FORWARD: the two tracking modes. The monitor loses a player who breaks line of

sight; the serpent does not, because it is not using its eyes. Every stealth beat in the rest of the

chapter — the Quiet Step stalk, the Ebu Gogo layers, the wa in the dark — reads against the lesson

this fight teaches, and this is where the player learns that breaking sight is not a universal answer.

7. care_read

• COLLECTIVE READ: nothing collective is engaged by fighting animals, and the row's own care register

says so. The asymmetry is stated rather than averaged: the serpent half carries a living Manggarai

tradition's naga vocabulary and its own cultural_depiction_required TRUE, and the land half

carries none.

• ONTOLOGY ROUTING: both are ORDINARY_FAUNA under a guardian FRAMING. Framing governs staging, never

agency. The non-kill path exists, the kill path exists, the price of the kill path is one lore mark

on a serpent-reverence track, and nothing hardens.

• ROUTE: concept plates for both bodies, attended build. Never the photographic-wildlife template.
• ANTI-TIMID PASS, RECORDED: the reduction considered was to make the fought route feel bad — an

integrity penalty, a community reaction, a worse reward. REFUSED, and canon refuses it first: the

spine's own ruling is that both are wins, the mark is the price of the easier one, and it is not an

integrity tax. Care here means the choice has a consequence, not that one option is punished.

• INVENTION DECLARATION: the five-pip read sequence, the ground boundary and its inversion, and the

encounter-wide shape audit are INVENTED BY THIS SHEET. The verbs, counters, pip count, reveal

threshold, framing and the serpent-reverence write are CANON and are quoted rather than designed.

• REVEAL READ: clean. No pattern token exists to leak in this chapter.

8. plate_brief

• PLATE A, the meeting: both animals in one frame at the recharge source in hard midday light, the

serpent coiled in the water with its forebody raised, the monitor low on the dry bank, the wet line

between them visible on the rock. A player should be able to see the two territories in the

composition alone.

• PLATE B, the inversion: the same two animals with their ground swapped — the monitor standing in the

shallows on its high walk, the serpent up on the dry rock with the ridge loaded.

• PLATE C, the third party: two smaller monitors leaving frame as the guardian arrives, the size

relationship carrying the read.

9. boarded_debts

• @ BE_0002_S1 :: hitzone_parts, phase_trigger, escalation_vector, phase_voice_array are all

EMPTY. Sections 6 of this sheet and of the two body sheets are their content.

• T0_Boss_Attack_Rail has 0 rows. This encounter needs nine (five serpent shapes, four monitor

shapes), and the ONE-ANSWER rule cannot be gated until they exist.

• @ BE_0002_S1 :: ontology_class is EMPTY while both creature rows carry ORDINARY_FAUNA. Harmless

today, load-bearing the moment a lane routes generation by the boss row's class.

• The turf third party has no row. CR_0005 is present in the zone and this encounter uses it; whether

that is an encounter-composition field or stays prose is a registry-lane call.

• NAMING RESIDUE: the encounter is named for Kelimutu and sited at recharge_waterfall in the Liang

Bua vicinity. Pre-existing; named here so it is not inherited silently.

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