# 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.foes — the `foes` slice What waits in the valley. The hollow soldiers: their bodies, their AI (notice, close, wind up, strike, recover, stagger, die), the damage they do and take, and the souls they leave where they fall. Then the Ash Warden: its poise, its three phases, its telegraphed attacks, and its death. Owns `/zero/source/game/foes.module/` and `/zero/source/game/foes/`. Hangs its components on the mount entity `Game/foes`; every lockable enemy is an entity beneath it. References it must match: `design/references/05-the-ash-warden.png` and `design/references/01-in-play.png`. Read `design/spec.md` for the interface and what "done" means.