# assets/ui/art.module — the drawn material of the interface Everything the UI is made of that is not layout. - **Colour** — `Art.C` translates `Game.PALETTE` into CSS strings once, so the screens and the world can never drift apart. `Art.hex`, `Art.rgba`, `Art.mix` and `Art.grip(fraction)` build the rest. - **Type** — `Art.FONT.display` (Anton), `.tech` (BerkeleyMono), `.body` (Arimo). - **Chrome** — `Art.abs`, `Art.rule`, `Art.TICKS`, `Art.RAIN`, `Art.enter`, `Art.loop`. - **Art** — `Art.TOWER` (the Ironspine drawn as a tapering stack of vertebrae with ribs, plating, wreckage, torn cabling and the dark crown ring), `Art.RETICLE`, `Art.HOLD_RING`, `Art.CROWN`, `Art.PITON`, `Art.handSVG`, `Art.mouseSVG`, `Art.arcSVG`, `Art.windSVG`, `Art.keyCap`. Two rules learned here and kept: - A **wrapping label must not carry its own width** — the measure goes on a wrapper box, which is what `Art.para` builds. - **Text inside SVG markup does not use the engine's registered fonts**, so `Art.keyCap` is a styled box with a real label rather than SVG `<text>`. Nothing here reads or writes game state; it is pure drawing.

# game <!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. --> TODO: describe this module.

# game/live.module The one table the running game keeps across a hot reload. Editing a module re-evaluates every module that depends on it. `game.game` and `game.boot` are therefore re-run many times in a working session, and anything they held in a module-local table would be replaced by an empty one while the entities the slices built are still standing in the scene — the phase, the blackboard, the event listeners, the hold registry and the record of which slices are built, all quietly reset, with the game still looking correct and no longer moving. `live.module` depends on nothing, so nothing re-evaluates it, so the tables it hands out are the same tables for the whole session. It holds no logic. Anything with behaviour would have to change eventually, and the moment it changed it would stop being durable. ## Used by - `game/game.module` — `Game` itself, `Game.state`, the event bus, the hold registry, the part list. - `game/boot.module` — which slices are built, their module tables, their root entities.

# ui/hud.module — the suit instrumentation `Hud.build(view)` turns a snapshot into a widget tree. It is pure: it reads nothing and writes nothing. `ui/screens.module` owns the snapshot, the registration and the tick. ## What is on the glass - **Two grip plates**, hard left and hard right, one per hand, so a glance says *which* hand is dying. Each carries the hand's state word, the stamina meter tinted by `Game.gripColor`, the measured load in newtons, that load against `Game.C.gripBreakForce`, and whether the boot on that side is planted. Under a third of grip the plate breathes red; under a sixth it breathes twice as fast. - **The altitude tape**, right edge: the crown at `Game.C.crownHeight`, the sea at zero, the last piton marked in brass, and the climber's own height called out in large numerals. - **The wind strip**, top centre: bearing, newtons, and a gust flare. - **The run block**, top left: elapsed time, pitons set, falls taken. - **The reticle**, centre, with a ring and a tag on the hold `Game.pickHold` would actually take — the same call the hand makes, so the highlight can never lie. - **The beacon arc**, bottom centre, while the ignition ring is charging. - **The control prompt**, which fades out over the first half-minute of a climb. - **`MENU · ESC`**, a real button so the engine's keyboard-shortcut plumbing reaches the pause menu. ## The snapshot ``` { left, right, -- { anchored, slipping, load, stamina01, kind, footPlanted } altitude, lastAnchorY, anchorsSet, falls, timeText, windNewtons, wind01, windDeg, gusting, beacon01, reticle = { x, y, tint, hold = { x, y, kind, grip }? }, hintOpacity } ```

# staging The camera, and the three moments the camera exists for. Everything here drives the player's own `CameraRig` — the entity `camera.main()` resolves to. Nothing spawns a camera of its own, and adopting the rig clears its `Camera.behavior` so exactly one writer owns the transform. ## The gameplay camera Procedural, and reads only `Game.state`: - stands outboard of the column (the column is on the world axis, the climber is always on its skin) and orbits with the lateral part of `Game.state.aim` - tightens — closer, longer lens — while one hand carries load and the other is off the wall - climbs above the body and sinks its look point as the altitude rises, so the sea holds the bottom of the frame and the drop is never abstract - shakes on `Game.state.wind` and on a `"gust"` - on a fall: widens to `Game.C.camFovFalling`, drops its lag to `camLagFalling`, and sits below the body looking up the column, so the tower streams up out of frame ## The moments | Moment | Fires on | What it is | |---|---|---| | `opening` | phase → `intro` | Four shots: in over the sea, a helical rise up the column, into cloud onto the crown, then a cut to the base that settles exactly onto the gameplay pose. | | `beat` | first `"fall"` above 52 m | Time dips to 0.34, the camera snaps onto the hand as it opens, holds, then falls with the body. Fires once a run. | | `resolution` | phase → `won` | The camera leaves the body, cranes up past the crown holding the lit ring in frame, then lets the crown sink away into clear air. | The establishing shot behind the title screen is not a moment — it is a slow rising orbit that runs for as long as the title is up. ## What other slices call ```luau local Staging = require("game.staging") Staging.isCinematic() -- CLIMB drops input while this is true Staging.skip() -- SCREENS cuts the opening short; the phase still lands Staging.moment() -- "opening" | "beat" | "resolution" | "" ``` STAGING writes no field of `Game.state`. It moves the phase in one place only: entering `intro` starts the opening, and the opening ending sets `climb`. ## Authoring aids For screenshots, the trailer, and testing a frame without playing to it: ```luau Staging.play("opening") -- run a moment on demand Staging.seek(8.0) -- park it on second 8 and hold there Staging.hold(false) -- let the clock run again Staging.setTitleTime(24) -- park the establishing shot Staging.stageAt({ 5.4, 120, 0.2 }) -- frame the gameplay camera on a point Staging.stageAt({ 5.4, 120, 0.2 }, "fall") -- ...in the falling framing Staging.stageAt(nil) -- back to the live body Staging.pose() -- eye, look, fov, roll, moment, tick count ```