Digital Twin

A ready-made digital twin: write one manifest of assets, metrics and KPIs, pick a layout, and get status colours, alarms, a KPI header, asset cards, a heatmap and a simulated shift. ONE write builds a working demo: update_track_state with { ui: { preset: "control-room" }, twin: { title, metrics, assets, kpis } } (the brief's quickstart has a complete example to copy). Layouts: control-room (KPI header, alarm journal rail, process strip), asset-focus (one hero asset, its card pinned), fleet (a list of assets down a rail) and kiosk (a hands-free tour). Assets are drawn from kits (cnc, press, robot-cell, booth, gantry, packer, tank, pump, cabinet, machine) on a site (hall, floor or pad, with an optional conveyor), or bind to your own imported model or primitives by `object` id. Readings come from the built-in simulator (give an asset `sim` ranges: faults arrive and clear on their own, and metrics follow the status) or from a real feed publishing <asset>.<metric> and <asset>.status. Clicking an asset, a strip chip, a journal row or a number key selects it, the camera flies there and its card opens with live trends; H toggles the heatmap, L the labels, Esc returns to the overview. Do not write rules, bindings or interactions for any of that: the manifest drives it, and the write receipt checks the manifest field by field. Without a manifest this is an empty scene with a timeline clock, and the lower-level route still works for anything the manifest does not cover: a datasource feed, telemetry widgets, colorRamp bindings and threshold rules.