# 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.