nx_iot_page.nx

nx_iot_page.nx -- EMIT the nishifamily.com/iot hub control panel. The UI surface for the IoT hub (operator directive 2026-06-20: "in everything we build we need a UI we are iterating on -- that's the big point of the nishifamily.com hosting"). This organ AUTHORS the page; no JS/HTML is hand-written elsewhere. Same emit -> push -> verify loop every property reuses (publishing is the separate sovereign step nx_aw_push, additive + vault-backed). DATA-DRIVEN (CLAUDE.md #11): the per-device control widgets are NOT hardcoded -- the page asks nx_iot_capability what each device class can do (cap flags) and renders exactly the right controls, and prints the capability JSON the /iot front-end would consume. Change a device's class and its controls change, with zero edits here. HONEST SCOPE this iteration (feedback-show-raw-output-no-overclaim): - READ-ONLY DASHBOARD, safe to be public: it surfaces the hub design, the data-driven control layout (demo devices), the auto-pair + self-heal state machines, and the MEASURED-exceed numbers. - The control widgets are the live UI surface but DO NOT actuate yet; actuation is wired in the next pass behind operator-only OPAQUE auth (a control panel must not be public -- the law in feedback-every-capability-needs-iterating-ui). We iterate from here. genealogy_id: NISHI_IOT_HUB_ROADMAP.md + project-iot-hub-multi-vendor-kickoff-2026-05-16 license_tier: ORIGINAL