The evidence is proven or strong, but this capability still needs a capability-specific ESP32 or Rust runtime adapter.
Intended capability
Evaluate the sensing evidence for “Tremor Band Progression Monitor” in a consented, ground-truthed study. This is not a medical device, clinical monitor, diagnosis, or emergency alert.
This describes the intended outcome. Readiness is needs edge adapter, evidence is class B, and a catalog mapping or recording is not proof of this outcome at a real site.
Solution blueprint
See the environment before installing it.
This exact kit is one of 191 first-class designs. It includes geometry, objects, nodes, wording, scenarios, installation, limitations, and catalog-bound readiness.
No rendered revision is available yet.
Bundled recording
A related Healthcare scene
This is one recorded vertical scenario. It is not separate validation of every capability in the catalog.
01 The physics
Resting tremor oscillates hands/forearms at 4-7Hz with amplitude in the mm-cm range — squarely inside the proven micro-Doppler band and spectrally distinct from voluntary motion (broadband) and breathing (0.1-0.5Hz).
02 Shared processing path
Edge Doppler-band summary -> seated-still episode detector (low bulk motion, breathing present) -> 4-7Hz band-fraction statistics per episode -> per-week trend vs the person's own baseline manifold; explicit non-diagnostic framing.
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
03 Validation plan
Literature anchors radar tremor sensing; own-hardware pilot with consented participants wearing a reference accelerometer, correlate band fraction vs actigraphy tremor index across 4 weeks.
04 Commercial hypothesis
For the neurology care team: 'A between-visit tremor trend from the living room — no wearable to forget, no camera to accept.'