The timing problem
A gait event unfolds quickly. If a system identifies a meaningful event but delivers its cue after the relevant phase has passed, the measurement may be correct while the intervention is poorly timed.
That distinction changes the product question. A rehabilitation device is not only a sensor, algorithm, or interface. It is a loop: observe, interpret, cue, record, and review.
What the loop has to preserve
The cue should be simple enough to understand without pulling attention away from walking. The clinician should be able to explain why it appears. The record should make later review possible without pretending that one signal represents the whole person.
- A defined event rather than a vague movement score
- A cue linked clearly to that event
- Timing that is tested rather than assumed
- A record that supports later clinical review
- A clinician-guided way to adjust or stop the workflow
Evidence and product reasoning are different
Clinical guidelines support structured, task-relevant rehabilitation, but they do not validate every implementation of real-time feedback. Product reasoning can identify a plausible mechanism. Only formal analytical, safety, usability, and clinical work can show whether a particular system performs as intended.
That is why internal founder testing is useful for integration and failure discovery, but cannot establish patient benefit.
How this shapes NUWAC
These principles shape the current NUWAC prototype: wearable gait sensing, timed haptic feedback, and a clinician-facing review workflow. Internal testing is being used to improve integration and document failure states. Formal patient studies have not yet begun.
The immediate work is not to make an efficacy claim. It is to improve repeatability and prepare a system that can be evaluated credibly.
Limitations
This note explains a product and clinical reasoning framework. It is not a treatment recommendation and does not establish that any specific feedback device improves outcomes.