# game.rules — ASHEN VIGIL's constants and rules The one sheet of paper every slice of ASHEN VIGIL argues from. `require("game.rules")` gives the game's constants — the title and the art-direction sentence, the palette in linear RGB, the sun, the three stats and what a level buys, the soul cost curve, the flask, every combat timing (light, heavy, roll, guard, the turn rates, poise), movement and stamina, lock-on, grace, death, the boss and the common foe, and the names of the five slice mounts the scene makes. It also carries the four pure rules the slices share rather than duplicate: `levelCost(level)`, `statsAt(levels)`, `inArc(swingYaw, hitYaw, arcDegrees)`, and the `SLICES` list. It touches no engine API and reads no scene state: it is data and arithmetic, so it can be called from a component, a scene build, a tool or a test with the same answer. A number that lives in two slices is a bug — it lives here instead. Who reads it: every slice (`game.vigil`, `game.valley`, `game.foes`, `game.screens`, `game.sound`) and `scenes/main.scene/build.luau`.

# game.vigil — the `vigil` slice The thing the player is. The Vigil's body — battered grey plate, tattered ash-grey cloak, great helm with a narrow horizontal visor slit, a straight longsword — its locomotion and stamina, and every verb of the fight: light swing, heavy swing, guard with a parry window, dodge-roll with invulnerability frames, and lock-on. It also owns the camera those verbs are played through, on the scene's `PlayerSetups/DefaultSocialPlayer/CameraRig`. Owns `/zero/source/game/vigil.module/` and `/zero/source/game/vigil/`. Hangs its components on the mount entity `Game/vigil`. References it must match: `design/references/03-the-vigil.png` and `design/references/01-in-play.png`. Read `design/spec.md` for the interface and what "done" means.

# game.valley.terrain — the shape of the Ashen Valley ONE height function, `T.height(x, z)`, is the authority on where the ground is. The rendered mesh, the physics heightfield and every landmark's footing are all sampled from it, so what is drawn and what is stood on are the same surface by construction rather than by agreement. `T.height` composes the valley out of its own parts, each a named term: the floor falling gently down-valley with the dead ground's roll, the valley walls climbing away from the centre line, the higher ridge on the +X side (the viewpoint the establishing shot is taken from), the raised shelf the chapel stands on, and the road — a corridor cut and flattened through all of the above so it stays walkable where the ground does not. Also here: `T.roadX(z)` (the road's centre line), `T.normalAt(x, z)` (the surface normal by central difference), `T.meshGeometry()` (the terrain mesh as positions/indices/normals/uvs), `T.collider()` (the same grid as a `HeightfieldCollider`'s rows, cols, extent and heights), and `T.roadGeometry()` (the road ribbon laid on the corridor the height function already cut). The named places — `T.CHAPEL`, `T.RIDGE_TOP`, `T.HEART` — are what the rest of the valley is laid against. Called by `game.valley` (which builds it) and `game.valley.landmarks` (which places everything standing on it) and by `game.foes` (which stands the Ash Warden's camp on it).