UX6 — Hardware status pills + device topology + sim/hardware switch (E6)

[jack-champagne]

Part of the seam UX-prototype track (Krishna interview). Priority: later — furthest-out surface.

What

The hardware surfaces: hardware status pills, a device view / topology, and a sim/hardware switch (sim side with noise/params, real-device side, ILC loop straddling it).

Krishna's signal (interview 2026-06-30, p2 + p5)

• "hardware status pills"; "device view topology?"; "monitors for expir[ation] · shot count counts"
• sim/hardware switch; "(sim noise/params)"

Where it sits

This is the interview-UX spec's v4 hardware crossover (Intonato QILC) — the furthest-out stage, well beyond v1 backend. Prototyping now is pure feedback probing, in Krishna's own domain.

Seam-prototype approach

Pills + a sim/hardware toggle are cheap static webview elements; the device topology is the expensive part — mock it minimally. Fake device/status fixtures.

Feedback questions for Krishna / Andrew

1. What belongs on a hardware status pill — device, calibration age, shot budget, up/down?
2. Is a sim/hardware toggle the right mental model, or do sim and hardware want separate surfaces?

Lanes

• Kate — pills + switch + minimal topology · Raghav — shell + contract test + device fixture · Jack/Krishna — what hardware state matters

Design freedom

Krishna's home turf — give it wide latitude to figure out what a hardware-side researcher actually needs.

Refs: spec-20260614-231647-amicode-interview-ux (v4 hardware crossover), Intonato.