[PIR][WP29] RF sensing modality router posture (ADR-332, stretch, ADR-only)

Open Beginner friendly
#898 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Read docs/research/perpetual-intelligence-runtime/10-wave4-evidence-review.md and 11-wave4-program-plan.md, then inspect docs/adr/ADR-332-rf-sensing-modality-router.md. Update the ADR to record the corrected modality attributions, performance and cost figures, common RuVector representation, and deferred implementation status. Done means the ADR accurately reflects the stated posture without adding implementation work.

Written by the indexing model from the issue text.

Description

adr phase-w4-3 pir stretch wave-4

Part of PIR Wave 4 — epic #837.

ADR-only this wave: record the modality-router posture (Wi-Fi ubiquity/coarse, IR-UWB fine-activity/lowest-cost, FMCW unseen-room robustness; common RuVector representation above all three). CORRECTED attributions from arXiv:2608.20322 (the brief swapped FMCW/IR-UWB): IR-UWB 89.0 F1 / EUR 14; FMCW 83.4 (83.8 unseen-room) / EUR 20; Wi-Fi 79.0 (68.8 unseen-room) / EUR 320; sleep >=92.6% all three. Paper under review at IEEE Access; dataset-only artifact (imec GitLab). Implementation deferred pending RuView coordination.

  • Evidence grade & artifact availability: docs/research/perpetual-intelligence-runtime/10-wave4-evidence-review.md (PR #892)
  • WP/ADR mapping, phases, and security gates: docs/research/perpetual-intelligence-runtime/11-wave4-program-plan.md (PR #892)
  • ADR: docs/adr/ADR-332-rf-sensing-modality-router.md

Depends on: none. Soft: ADR-330, ADR-331.

Dominant language
Rust
Stars
4.5k
Forks
603
Avg merge
23h 32m
Merged PRs (30d)
59

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruvnet/RuVector

All issues in ruvnet/RuVector

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.