Integrate live phone and watch remote prototype with guarded motion control
This commit is contained in:
@@ -1,3 +1,22 @@
|
||||
# MotionCapture
|
||||
|
||||
Planned adapter: watch-only Core Motion acquisition and calibrated classification. No live implementation is present. Owner: workstream C in docs/agents/README.md. The integrator must establish injected protocols and source/test target membership before implementation. Keep platform APIs out of pure package modules.
|
||||
This workstream provides a watch-only `CMMotionManager` adapter and a pure
|
||||
calibrated classifier. The adapter is foreground/lifecycle-bound: it stops on
|
||||
inactive scene, relay loss, expiry, cancellation, or sensor failure. Samples
|
||||
are bounded and in memory only; no recording mode or raw traces are included.
|
||||
|
||||
The orientation transform (wrist side and crown orientation) and thresholds are
|
||||
versioned hypotheses pending physical validation. The package tests prove
|
||||
state-machine behavior only and are not evidence of reliable watch recognition.
|
||||
|
||||
## Evaluation report (pending hardware)
|
||||
|
||||
No Apple Watch or TV has been tested for this workstream. Precision, recall,
|
||||
incidental-movement false triggers, and the direction confusion matrix remain
|
||||
`pending physical evaluation`; do not infer them from synthetic fixtures.
|
||||
The required report should include per-direction TP/FP/FN, precision/recall,
|
||||
duplicate count, false triggers per armed hour, and a 4x4 actual-vs-predicted
|
||||
matrix split by wrist and crown orientation.
|
||||
|
||||
See `INTEGRATION-PROPOSAL.md` for target membership, permission-string, and
|
||||
lifecycle integration requirements.
|
||||
|
||||
Reference in New Issue
Block a user