hw { battery network thermal } — simulated device state. Drag the controls under the phone; effects react.state name = value — reactive state. text "Taps: {counter}" interpolates; button "+1" -> counter+1 mutates.toggle "label" -> var · slider "label" min..max -> var · list "label" ["a","b"] -> var — hardware-feel inputs.button "Sync" ! syncModels — ! invokes an effect. needs guards are checked against live hardware; failures explain themselves.needs operands resolve against hardware, state variables, document facts (doc { key: value }), and other effects' outcomes — needs auditSummary == pass runs that effect first, and a failed guard stops the chain with its reason named. Operators: == != >= <= > <. A fact nobody supplied fails closed; it never silently passes.verdict (pass · fail · blocked when the chain stopped on a fact nobody supplied), failed_guards (the failed guards, in order), and any boolean *_run marker. A screen list written [name] renders the state list of that name; quoted items render literally.effect name : Network + Battery { needs ... } — resource effects are explicit and enforced, not documented.on tap / swipe(dir) / longpress -> Screen. Layouts: stack(safe) respects notches.