* fix(signal): circular phase variance for ghost-tap guard (ADR-154 §7.4 #1) `phase_variance` computed a LINEAR sample variance over phase angles that wrap at ±π, so a tightly-clustered set straddling the branch cut reported spuriously HIGH dispersion — false-tripping the `> TAU` ghost-tap guard on real, tightly-clustered CIR taps. Replace with Mardia's circular variance V = 1 − R̄, bounded [0,1] and invariant to where the cluster sits on the circle. Re-derive the guard against the bounded metric via a named const `GHOST_TAP_CIRCULAR_VARIANCE_MAX` (the old TAU-scaled threshold is meaningless on [0,1]). Grade: metric fix MEASURED; threshold value DATA-GATED — a clean single-path ramp also sweeps the circle, so V alone cannot separate clean from unsanitized without labelled frames. Conservative default (0.99) errs toward never false-rejecting, strictly more permissive at the wrap boundary than the buggy linear guard. Fails-on-old test: `phase_variance_circular_not_fooled_by_branch_cut` — inlines the old linear variance to show it exceeds TAU on wrap-straddling phases while circular V≈0 and the guard no longer trips. Plus `phase_variance_circular_is_bounded_and_extremal` (V∈[0,1], V≈0 identical, V≈1 uniform). cargo test -p wifi-densepose-signal --no-default-features --features cir --lib → 432 passed, 0 failed. Co-Authored-By: claude-flow <ruv@ruv.net> * fix(signal): pin Welford n=0/n=1 finiteness guard (ADR-154 §7.4 #10) The shared `WelfordStats` (field_model.rs, used by longitudinal.rs and others) relies on `count < 2` guards in `variance`/`sample_variance`/`std_dev`/ `z_score` to stay finite at the boundaries. The guards existed but the n=0 boundary was UNTESTED — exactly the §4 divide-by-(n−1) family the ADR groups this with. Add `welford_finite_at_n0_and_n1` asserting every statistic is finite and returns the documented sentinel (0.0) at n=0 and n=1, plus load-bearing doc comments on the two guards. Fails-on-old proof: with the `sample_variance` guard removed, the test FAILS with "attempt to subtract with overflow" at the `(self.count - 1)` underflow (0usize − 1); `variance` would similarly yield 0.0/0.0 = NaN. The guard is restored; the test pins it so a future regression is caught. Grade: MEASURED (boundary finiteness is asserted; the guard is the §4-family fix made testable). cargo test -p wifi-densepose-signal --no-default-features --lib field_model → 22 passed, 0 failed. Co-Authored-By: claude-flow <ruv@ruv.net> * refactor(signal): de-magic adversarial thresholds + boundary tests (ADR-154 §7.4 #13) Lift the bare numeric literals buried in `check`/`check_consistency` into named, documented module consts (FIELD_MODEL_GINI_VIOLATION=0.8, ENERGY_RATIO_HIGH_VIOLATION=2.0, ENERGY_RATIO_LOW_VIOLATION=0.1, CONSISTENCY_ACTIVE_FRACTION_OF_MEAN=0.1, SCORE_W_* weights). VALUES UNCHANGED — each const equals the original literal; only names + pinning tests are new. Grade: DATA-GATED. The operating values stay empirical (defensible values need labelled spoofed/clean CSI — Wi-Spoof, §6.2/§7.3). The de-magicking + characterization tests are MEASURED: `tuning_consts_unchanged_from_literals`, `energy_ratio_high_boundary`, `energy_ratio_low_boundary`, `field_model_gini_boundary`, `consistency_active_fraction_boundary` pin the decision boundaries at/just-below/just-above each threshold, so a future data-driven retune is a visible, tested change. Fails-on-change proof: bumping ENERGY_RATIO_HIGH_VIOLATION 2.0→3.0 makes `energy_ratio_high_boundary` FAIL (restored). Operating values explicitly NOT changed. cargo test -p wifi-densepose-signal --no-default-features --lib ruvsense::adversarial → 20 passed, 0 failed. Co-Authored-By: claude-flow <ruv@ruv.net> * refactor(signal): de-magic coherence drift/gate thresholds (ADR-154 §7.4 #9) Lift the bare detection literals in `coherence.rs::classify_drift` (DRIFT_STABLE_SCORE=0.85, DRIFT_STEP_CHANGE_MAX_STALE=10) and the `coherence_gate.rs` Default impl (DEFAULT_ACCEPT_THRESHOLD=0.85, DEFAULT_REJECT_THRESHOLD=0.5, DEFAULT_MAX_STALE_FRAMES=200, DEFAULT_PREDICT_ONLY_NOISE=3.0) into named, documented consts. VALUES UNCHANGED. The gate already exposed these via GatePolicyConfig (config seam); this names + pins the defaults. Grade: DATA-GATED. Operating values stay empirical (defensible Z-score thresholds need labelled stable/drifting coherence traces). De-magicking + boundary tests are MEASURED: `classify_drift_stable_score_boundary`, `classify_drift_stale_count_boundary` pin the at/just-below/just-above decisions; `drift_consts_unchanged_from_literals` / `gate_default_consts_unchanged_from_literals` pin the values. Operating values explicitly NOT changed. cargo test -p wifi-densepose-signal --no-default-features --lib ruvsense::coherence → 40 passed, 0 failed. Co-Authored-By: claude-flow <ruv@ruv.net> * docs(adr-154): mark §7.4 P1 backlog cleared — Milestone-1 (#1,#10 RESOLVED; #9,#13 DATA-GATED) Update ADR-154 §7.4 backlog rows #1, #9, #10, #13 with commit refs + grades, the §7.4 intro count (four P1 items cleared, ~41 P2/P3 remain), the Horizon-ledger one-liner (Milestone-1 DONE), and the §8 honest-limits #1 line (metric now correct; threshold still DATA-GATED). Add CHANGELOG [Unreleased] entry. Grades: #1 RESOLVED (MEASURED metric / DATA-GATED threshold), #10 RESOLVED (MEASURED), #9 & #13 RESOLVED-PARTIAL (DATA-GATED — de-magicked + boundary tested, operating values unchanged). Validation: cargo test --workspace --no-default-features → 2057 passed, 0 failed; wifi-densepose-signal lib → 442 passed (no-default + --features cir); python archive/v1/data/proof/verify.py → VERDICT: PASS, hash f8e76f21…46f7a UNCHANGED (CIR ghost-tap guard is not on the deterministic proof path). Co-Authored-By: claude-flow <ruv@ruv.net> * fix(sensing-server): stop leaking internal errors in HTTP responses (ADR-080 #2) Six handlers in `main.rs` serialized the internal error `Display` straight into the JSON response body, leaking server internals to any client (ADR-080 finding #2, CWE-209; reframed onto the Rust boundary by ADR-164 G11): - edge_registry_endpoint: a panicked spawn_blocking `JoinError` ("task … panicked") in a 500, and the raw upstream error in a 503 - delete_model / delete_recording / start_recording: std::io::Error strings carrying OS detail / filesystem paths - calibration_start / calibration_stop: the FieldModel error chain New `error_response` module: `internal_error` / `internal_error_json` / `upstream_unavailable` log the full detail server-side only (tagged with a correlation id) and return a generic body (`{"error":"internal_error","correlation_id":…}`) — no `panicked`, no file paths, no Debug chain. The correlation id lets an operator join a client report to the exact server log line without ever shipping the detail. Pinned by 5 error_response tests, incl. a leak-substring guard (internal_error_body_does_not_leak_detail) verified to FAIL on the reverted old body (returns the panic message / path / "os error"). The HOMECORE sweep (ADR-161) covered homecore-server, not this crate. Co-Authored-By: claude-flow <ruv@ruv.net> * test(sensing-server): pin XFF-immunity + no-query-token (ADR-080 #1, #3) Findings #1 (XFF-spoofing bypass) and #3 (JWT-in-URL, CWE-598) were logged against the Python v1 API but are VERIFIED ABSENT on the current Rust sensing-server, so they get regression tests rather than redundant fixes: - #1 XFF: there is no IP-based rate-limiter or IP-allowlist to bypass, and neither security middleware reads a forwarded header. Added bearer_auth::xff_header_never_affects_auth_decision (spoofed X-Forwarded-For never flips a 401<->200 decision) and host_validation::forwarded_headers_never_bypass_host_allowlist (spoofed X-Forwarded-Host: localhost never lets Host: evil.com past the allowlist). - #3 JWT-in-URL: require_bearer reads the token only from the Authorization header; WS handlers take no query token; the sole Query extractor (EdgeRegistryParams) is a non-secret refresh flag. Added bearer_auth::query_string_token_is_never_accepted — ?token= / ?access_token= in the URL never authenticates (stays 401) while the header path still 200s. Verified to FAIL when a query-token path is injected into require_bearer. Co-Authored-By: claude-flow <ruv@ruv.net> * docs(adr-080): mark P0 security findings #1-#3 RESOLVED; close ADR-164 G11 - ADR-080: Status note + per-finding closure (#1 XFF and #3 JWT-in-URL verified absent + regression-pinned; #2 leaked errors fixed via the error_response module). Records the v1-vs-Rust boundary distinction explicitly: v1 paths remain archived; this closure governs the shipped Rust sensing-server. - ADR-164: Gap Register G11 and the Open/Gated Backlog entry marked RESOLVED with the fix + branch reference. - CHANGELOG: [Unreleased] -> ### Security entry covering all three findings. Co-Authored-By: claude-flow <ruv@ruv.net> * docs(adr): renumber 6 displaced ADRs to resolve duplicate-number collisions (ADR-164 G1) Resolves the 5 duplicate ADR numbers (6 displaced files) flagged by ADR-164 Gap Register item G1. Canonical keeper per number = first file committed at that number (date tie-broken by inbound cross-reference count / parent-appendix relationship). Displaced files renumbered to the next free numbers (166-171): 050 keeps provisioning-tool-enhancements (5 refs vs 1) -> ADR-166-quality-engineering-security-hardening 052 keeps tauri-desktop-frontend (parent ADR) -> ADR-167-ddd-bounded-contexts (its appendix) 147 keeps nvidia-cosmos/OccWorld (the actual ADR, has Status header) -> ADR-168-benchmark-proof (proof companion, no Status) -> ADR-169-adam-mode-light-theme (was untracked) 148 keeps drone-swarm-control-system (committed #862) -> ADR-170-yoga-mode-pose-system (was untracked) 149 keeps public-community-leaderboard-huggingface (committed 16:47 vs 17:38) -> ADR-171-swarm-benchmarking-evaluation-methodology Updates in-file `# ADR-NNN` headers and intra-file self-references (yoga-modes * docs(adr): repoint inbound cross-references to renumbered ADRs (166-171) Follow-up to the ADR renumbering (ADR-164 G1). Updates every inbound reference that pointed at a displaced ADR, disambiguating shared numbers by title/slug so only references to the DISPLACED topic move and keeper references stay put. ADR-168 (was 147 benchmark-proof): README, CHANGELOG, user-guide, proof-of-capabilities, research docs 00/03 — all path/label refs updated. ADR-169 (was 147 adam-mode) / ADR-170 (was 148 yoga-mode): docs/adr/README index. ADR-171 (was 149 swarm-benchmarking): all ruview-swarm eval code+docs (Cargo.toml, evals/, eval_swarm.rs, metrics/mod/report/runner.rs), research doc 03 (every §-ref matched ADR-171 sections, not AetherArena), 00-system-review, series README, CHANGELOG, and ADR-148's forward/"open issues" pointers. ADR-166 (was 050 quality-engineering / security-hardening): disambiguated from the ADR-050 provisioning KEEPER by topic. The HMAC/secure_tdm, directory-traversal, bind-address, and OTA-PSK-auth references in code comments (wifi-densepose-hardware Cargo.toml + secure_tdm.rs, sensing-server main.rs) and in ADR-052-tauri / ADR-167 all describe the security-hardening ADR -> ADR-166. ADR-167 (was 052 ddd-appendix): inbound appendix references. Index/registry updates: docs/adr/README.md, gap-analysis/census.md (rows + header count), gap-analysis/lens-findings.md (collision table marked RESOLVED), and ADR-164 Gap Register G1 marked RESOLVED with the full renumber map. Keeper references deliberately untouched: all ADR-147 OccWorld code, all ADR-148 drone-swarm code/docs, all ADR-149 AetherArena refs (incl. ADR-150's SSL/resampling refs, which ADR-150 explicitly binds to the AetherArena benchmark), ADR-050 provisioning refs, ADR-052 tauri refs. The frozen GitHub blob URLs in docs/adr/.issue-177-body.md (pinned to an old branch) are left as historical. Comment-only code edits; no behavior change. wifi-densepose-hardware compiles clean; the sensing-server build's sole blocker is the pre-existing upstream midstreamer-temporal-compare@0.2.1 registry crate, unrelated to these edits. Co-Authored-By: claude-flow <ruv@ruv.net> |
||
|---|---|---|
| .. | ||
| gap-analysis | ||
| .issue-177-body.md | ||
| ADR-001-wifi-mat-disaster-detection.md | ||
| ADR-002-ruvector-rvf-integration-strategy.md | ||
| ADR-003-rvf-cognitive-containers-csi.md | ||
| ADR-004-hnsw-vector-search-fingerprinting.md | ||
| ADR-005-sona-self-learning-pose-estimation.md | ||
| ADR-006-gnn-enhanced-csi-pattern-recognition.md | ||
| ADR-007-post-quantum-cryptography-secure-sensing.md | ||
| ADR-008-distributed-consensus-multi-ap.md | ||
| ADR-009-rvf-wasm-runtime-edge-deployment.md | ||
| ADR-010-witness-chains-audit-trail-integrity.md | ||
| ADR-011-python-proof-of-reality-mock-elimination.md | ||
| ADR-012-esp32-csi-sensor-mesh.md | ||
| ADR-013-feature-level-sensing-commodity-gear.md | ||
| ADR-014-sota-signal-processing.md | ||
| ADR-015-public-dataset-training-strategy.md | ||
| ADR-016-ruvector-integration.md | ||
| ADR-017-ruvector-signal-mat-integration.md | ||
| ADR-018-esp32-dev-implementation.md | ||
| ADR-019-sensing-only-ui-mode.md | ||
| ADR-020-rust-ruvector-ai-model-migration.md | ||
| ADR-021-vital-sign-detection-rvdna-pipeline.md | ||
| ADR-022-windows-wifi-enhanced-fidelity-ruvector.md | ||
| ADR-023-trained-densepose-model-ruvector-pipeline.md | ||
| ADR-024-contrastive-csi-embedding-model.md | ||
| ADR-025-macos-corewlan-wifi-sensing.md | ||
| ADR-026-survivor-track-lifecycle.md | ||
| ADR-027-cross-environment-domain-generalization.md | ||
| ADR-028-esp32-capability-audit.md | ||
| ADR-029-ruvsense-multistatic-sensing-mode.md | ||
| ADR-030-ruvsense-persistent-field-model.md | ||
| ADR-031-ruview-sensing-first-rf-mode.md | ||
| ADR-032-multistatic-mesh-security-hardening.md | ||
| ADR-033-crv-signal-line-sensing-integration.md | ||
| ADR-034-expo-mobile-app.md | ||
| ADR-035-live-sensing-ui-accuracy.md | ||
| ADR-036-rvf-training-pipeline-ui.md | ||
| ADR-037-multi-person-pose-detection.md | ||
| ADR-038-sublinear-goal-oriented-action-planning.md | ||
| ADR-039-esp32-edge-intelligence.md | ||
| ADR-040-wasm-programmable-sensing.md | ||
| ADR-041-wasm-module-collection.md | ||
| ADR-042-coherent-human-channel-imaging.md | ||
| ADR-043-sensing-server-ui-api-completion.md | ||
| ADR-044-geospatial-satellite-integration.md | ||
| ADR-045-amoled-display-support.md | ||
| ADR-046-android-tv-box-armbian-deployment.md | ||
| ADR-047-psychohistory-observatory-visualization.md | ||
| ADR-048-adaptive-csi-classifier.md | ||
| ADR-049-cross-platform-wifi-interface-detection.md | ||
| ADR-050-provisioning-tool-enhancements.md | ||
| ADR-052-tauri-desktop-frontend.md | ||
| ADR-053-ui-design-system.md | ||
| ADR-054-desktop-full-implementation.md | ||
| ADR-055-integrated-sensing-server.md | ||
| ADR-056-ruview-desktop-capabilities.md | ||
| ADR-057-firmware-csi-build-guard.md | ||
| ADR-058-ruvector-wasm-browser-pose-example.md | ||
| ADR-059-live-esp32-csi-pipeline.md | ||
| ADR-060-provision-channel-mac-filter.md | ||
| ADR-061-qemu-esp32s3-firmware-testing.md | ||
| ADR-062-qemu-swarm-configurator.md | ||
| ADR-063-mmwave-sensor-fusion.md | ||
| ADR-064-multimodal-ambient-intelligence.md | ||
| ADR-065-happiness-scoring-seed-bridge.md | ||
| ADR-066-esp32-swarm-seed-coordinator.md | ||
| ADR-067-ruvector-v2.0.5-upgrade.md | ||
| ADR-068-per-node-state-pipeline.md | ||
| ADR-069-cognitum-seed-csi-pipeline.md | ||
| ADR-070-self-supervised-pretraining.md | ||
| ADR-071-ruvllm-training-pipeline.md | ||
| ADR-072-wiflow-architecture.md | ||
| ADR-073-multifrequency-mesh-scan.md | ||
| ADR-074-spiking-neural-csi-sensing.md | ||
| ADR-075-mincut-person-separation.md | ||
| ADR-076-csi-spectrogram-embeddings.md | ||
| ADR-077-novel-rf-sensing-applications.md | ||
| ADR-078-multifreq-mesh-applications.md | ||
| ADR-079-camera-ground-truth-training.md | ||
| ADR-080-qe-remediation-plan.md | ||
| ADR-081-adaptive-csi-mesh-firmware-kernel.md | ||
| ADR-082-pose-tracker-confirmed-output-filter.md | ||
| ADR-083-per-cluster-pi-compute-hop.md | ||
| ADR-084-rabitq-similarity-sensor.md | ||
| ADR-085-rabitq-pipeline-expansion.md | ||
| ADR-086-edge-novelty-gate.md | ||
| ADR-089-nvsim-nv-diamond-simulator.md | ||
| ADR-090-nvsim-lindblad-extension.md | ||
| ADR-091-stand-off-radar-tier-research.md | ||
| ADR-092-nvsim-dashboard-implementation.md | ||
| ADR-093-dashboard-gap-analysis.md | ||
| ADR-094-pointcloud-github-pages-deployment.md | ||
| ADR-095-rvcsi-edge-rf-sensing-platform.md | ||
| ADR-096-rvcsi-ffi-crate-layout.md | ||
| ADR-097-adopt-rvcsi-as-ruview-csi-runtime.md | ||
| ADR-098-evaluate-midstream-fit.md | ||
| ADR-099-midstream-introspection-tap.md | ||
| ADR-100-cog-packaging-specification.md | ||
| ADR-101-pose-estimation-cog.md | ||
| ADR-102-edge-module-registry.md | ||
| ADR-103-learned-multi-person-counter.md | ||
| ADR-104-ruview-mcp-cli-distribution.md | ||
| ADR-105-federated-csi-training.md | ||
| ADR-106-dp-sgd-and-primitive-isolation.md | ||
| ADR-107-cross-installation-federation.md | ||
| ADR-108-kyber-post-quantum-key-exchange.md | ||
| ADR-109-dilithium-pqc-signatures.md | ||
| ADR-110-esp32-c6-firmware-extension.md | ||
| ADR-113-multistatic-placement-strategy.md | ||
| ADR-114-cog-quantum-vitals.md | ||
| ADR-115-home-assistant-integration.md | ||
| ADR-116-cog-ha-matter-seed.md | ||
| ADR-117-pip-wifi-densepose-modernization.md | ||
| ADR-118-bfld-beamforming-feedback-layer-for-detection.md | ||
| ADR-119-bfld-frame-format-and-wire-protocol.md | ||
| ADR-120-bfld-privacy-class-and-hash-rotation.md | ||
| ADR-121-bfld-identity-risk-scoring.md | ||
| ADR-122-bfld-ruview-ha-matter-exposure.md | ||
| ADR-123-bfld-capture-path-nexmon-and-esp32.md | ||
| ADR-124-rvagent-mcp-ruvector-npm-integration.md | ||
| ADR-125-ruview-apple-home-native-hap-bridge.md | ||
| ADR-126-ruview-native-ha-port-master.md | ||
| ADR-127-homecore-state-machine-rust.md | ||
| ADR-128-homecore-integration-plugin-system.md | ||
| ADR-129-homecore-automation-engine.md | ||
| ADR-130-homecore-rest-websocket-api.md | ||
| ADR-132-homecore-recorder-history-semantic-search.md | ||
| ADR-133-homecore-assist-ruflo.md | ||
| ADR-134-csi-to-cir-time-domain-multipath.md | ||
| ADR-135-empty-room-baseline-calibration.md | ||
| ADR-136-ruview-streaming-engine-frame-contracts.md | ||
| ADR-137-fusion-engine-quality-scoring-evidence.md | ||
| ADR-138-linkgroup-array-coordinator-clock-quality.md | ||
| ADR-139-worldgraph-environmental-digital-twin.md | ||
| ADR-140-semantic-state-record-and-agent-bridge.md | ||
| ADR-141-bfld-privacy-control-plane-modes-attestation.md | ||
| ADR-142-evolution-tracker-temporal-voxel-aggregation.md | ||
| ADR-143-rf-slam-reflector-discovery-anchor-learning.md | ||
| ADR-144-uwb-range-constraint-fusion.md | ||
| ADR-145-ablation-eval-harness-privacy-leakage.md | ||
| ADR-146-rf-encoder-multitask-heads-uncertainty.md | ||
| ADR-147-nvidia-cosmos-world-foundation-model-integration.md | ||
| ADR-148-drone-swarm-control-system.md | ||
| ADR-149-public-community-leaderboard-huggingface.md | ||
| ADR-150-rf-foundation-encoder.md | ||
| ADR-151-room-calibration-specialist-training.md | ||
| ADR-152-wifi-pose-sota-2026-intake.md | ||
| ADR-153-ieee-802-11bf-sensing-protocol-layer.md | ||
| ADR-154-signal-dsp-beyond-sota.md | ||
| ADR-155-nn-training-beyond-sota.md | ||
| ADR-156-ruvector-fusion-beyond-sota.md | ||
| ADR-157-hardware-sensing-beyond-sota.md | ||
| ADR-158-mat-worldmodel-beyond-sota.md | ||
| ADR-159-cognitum-appliance-beyond-sota.md | ||
| ADR-160-edge-skill-library-honest-labeling.md | ||
| ADR-161-homecore-server-layer-security.md | ||
| ADR-162-plugin-security-and-bounded-runmodes.md | ||
| ADR-163-edge-latency-measurement.md | ||
| ADR-164-adr-corpus-gap-analysis.md | ||
| ADR-165-homecore-migrate-from-home-assistant.md | ||
| ADR-166-quality-engineering-security-hardening.md | ||
| ADR-167-ddd-bounded-contexts.md | ||
| ADR-168-benchmark-proof.md | ||
| ADR-169-adam-mode-light-theme.md | ||
| ADR-170-yoga-mode-pose-system.md | ||
| ADR-171-swarm-benchmarking-evaluation-methodology.md | ||
| README.md | ||
README.md
Architecture Decision Records
This folder contains 45 Architecture Decision Records (ADRs) that document every significant technical choice in the RuView / WiFi-DensePose project.
Why ADRs?
Building a system that turns WiFi signals into human pose estimation involves hundreds of non-obvious decisions: which signal processing algorithms to use, how to bridge ESP32 firmware to a Rust pipeline, whether to run inference on-device or on a server, how to handle multi-person separation with limited subcarriers.
ADRs capture the context, options considered, decision made, and consequences for each of these choices. They serve three purposes:
-
Institutional memory — Six months from now, anyone (human or AI) can read why we chose IIR bandpass filters over FIR for vital sign extraction, not just see the code.
-
AI-assisted development — When an AI agent works on this codebase, ADRs give it the constraints and rationale it needs to make changes that align with the existing architecture. Without them, AI-generated code tends to drift — reinventing patterns that already exist, contradicting earlier decisions, or optimizing for the wrong tradeoffs.
-
Review checkpoints — Each ADR is a reviewable artifact. When a proposed change touches the architecture, the ADR forces the author to articulate tradeoffs before writing code, not after.
ADRs and Domain-Driven Design
The project uses Domain-Driven Design (DDD) to organize code into bounded contexts — each with its own language, types, and responsibilities. ADRs and DDD work together:
- ADRs define boundaries: ADR-029 (RuvSense) established multistatic sensing as a separate bounded context from single-node CSI. ADR-042 (CHCI) defined a new aggregate root for coherent channel imaging.
- DDD models define the language: The RuvSense domain model defines terms like "coherence gate", "dwell time", and "TDM slot" that ADRs reference precisely.
- Together they prevent drift: An AI agent reading ADR-039 knows that edge processing tiers are configured via NVS keys, not compile-time flags — because the ADR says so. The DDD model tells it which aggregate owns that configuration.
How ADRs are structured
Each ADR follows a consistent format:
- Context — What problem or gap prompted this decision
- Decision — What we chose to do and how
- Consequences — What improved, what got harder, and what risks remain
- References — Related ADRs, papers, and code paths
Statuses: Proposed (under discussion), Accepted (approved and/or implemented), Superseded (replaced by a later ADR).
ADR Index
Hardware and firmware
| ADR | Title | Status |
|---|---|---|
| ADR-012 | ESP32 CSI Sensor Mesh for Distributed Sensing | Accepted (partial) |
| ADR-018 | ESP32 Development Implementation Path | Proposed |
| ADR-028 | ESP32 Capability Audit and Witness Record | Accepted |
| ADR-029 | RuvSense Multistatic Sensing Mode (TDM, channel hopping) | Proposed |
| ADR-032 | Multistatic Mesh Security Hardening | Accepted |
| ADR-039 | ESP32-S3 Edge Intelligence Pipeline (on-device vitals) | Accepted (hardware-validated) |
| ADR-040 | WASM Programmable Sensing (Tier 3) | Accepted |
| ADR-041 | WASM Module Collection (65 edge modules) | Accepted (hardware-validated) |
| ADR-044 | Provisioning Tool Enhancements | Proposed |
| ADR-110 | ESP32-C6 firmware extension — Wi-Fi 6 / 802.15.4 / TWT / LP-core | Accepted, P1-P10 complete, firmware-side substrate closed at v0.7.0-esp32. Companion docs: WITNESS-LOG-110 (13 §A0.x entries · 99.56 % cross-board RX · 104.1 µs smoothed sync stdev · ≤100 µs target met), ADR-110-REVIEW-GUIDE (one-page reviewer tour), ADR-110-BRANCH-STATE (coordination map vs feat/adr-115-ha-mqtt-matter). Host decoders + tests: Python SyncPacketParser (10) + Rust wifi_densepose_hardware::SyncPacket (15), cross-language hex pin gates drift. |
Signal processing and sensing
| ADR | Title | Status |
|---|---|---|
| ADR-013 | Feature-Level Sensing on Commodity Gear | Accepted |
| ADR-014 | SOTA Signal Processing Algorithms | Accepted |
| ADR-021 | Vital Sign Detection (breathing, heart rate) | Partial |
| ADR-030 | Persistent Field Model and Drift Detection | Proposed |
| ADR-033 | CRV Signal Line Sensing Integration | Proposed |
| ADR-037 | Multi-Person Pose Detection from Single ESP32 | Proposed |
| ADR-042 | Coherent Human Channel Imaging (beyond CSI) | Proposed |
| ADR-134 | First-Class Channel Impulse Response (CIR) Support | Proposed |
| ADR-135 | Empty-Room Baseline Calibration (per-subcarrier Welford statistics) | Proposed |
Machine learning and training
| ADR | Title | Status |
|---|---|---|
| ADR-005 | SONA Self-Learning for Pose Estimation | Partial |
| ADR-006 | GNN-Enhanced CSI Pattern Recognition | Partial |
| ADR-015 | Public Dataset Strategy (MM-Fi, Wi-Pose) | Accepted |
| ADR-016 | RuVector Training Pipeline Integration | Accepted |
| ADR-017 | RuVector Signal + MAT Integration | Proposed |
| ADR-020 | Migrate AI Inference to Rust (ONNX Runtime) | Accepted |
| ADR-023 | Trained DensePose Model with RuVector Pipeline | Proposed |
| ADR-024 | Project AETHER: Contrastive CSI Embeddings | Required |
| ADR-027 | Project MERIDIAN: Cross-Environment Generalization | Proposed |
| ADR-149 | AetherArena: public spatial-intelligence benchmark on Hugging Face | Proposed |
| ADR-150 | RF Foundation Encoder: pose-preserving, subject/room/device-invariant CSI embedding | Proposed |
| ADR-151 | Per-Room Calibration & Specialized Model Training (room-first → bank of small ruVector specialists) | Proposed |
| ADR-152 | WiFi-Pose SOTA 2026 Intake: geometry-conditioned calibration, external benchmarks, foundation-encoder recipe | Proposed |
Platform and UI
| ADR | Title | Status |
|---|---|---|
| ADR-019 | Sensing-Only UI with Gaussian Splats | Accepted |
| ADR-022 | Windows WiFi Enhanced Fidelity (multi-BSSID) | Partial |
| ADR-025 | macOS CoreWLAN WiFi Sensing | Proposed |
| ADR-031 | RuView Sensing-First RF Mode | Proposed |
| ADR-034 | Expo React Native Mobile App | Accepted |
| ADR-035 | Live Sensing UI Accuracy and Data Transparency | Accepted |
| ADR-036 | Training Pipeline UI Integration | Proposed |
| ADR-043 | Sensing Server UI API Completion (14 endpoints) | Accepted |
| ADR-115 | Home Assistant integration via MQTT auto-discovery + Matter bridge (HA-DISCO + HA-FABRIC + HA-MIND) | Accepted (MQTT track) / Proposed (Matter SDK P8b) |
| ADR-169 | adam-mode — light theme toggle for the three.js realtime demo | Proposed |
| ADR-170 | yoga-mode — yoga pose detection, classification, and scoring for the three.js realtime demo | Proposed |
Architecture and infrastructure
| ADR | Title | Status |
|---|---|---|
| ADR-001 | WiFi-Mat Disaster Detection Architecture | Accepted |
| ADR-002 | RuVector RVF Integration Strategy | Superseded |
| ADR-003 | RVF Cognitive Containers for CSI | Proposed |
| ADR-004 | HNSW Vector Search for Fingerprinting | Partial |
| ADR-007 | Post-Quantum Cryptography for Sensing | Proposed |
| ADR-008 | Distributed Consensus for Multi-AP | Proposed |
| ADR-009 | RVF WASM Runtime for Edge Deployment | Proposed |
| ADR-010 | Witness Chains for Audit Trail Integrity | Proposed |
| ADR-011 | Proof-of-Reality and Mock Elimination | Proposed |
| ADR-026 | Survivor Track Lifecycle (MAT crate) | Accepted |
| ADR-038 | Sublinear GOAP for Roadmap Optimization | Proposed |
| ADR-095 | rvCSI — Edge RF Sensing Runtime Platform | Proposed |
| ADR-096 | rvCSI — Crate Topology, the napi-c Shim, and the napi-rs Node Surface | Proposed |
| ADR-097 | Adopt rvCSI as RuView's primary CSI runtime (phased adoption) | Proposed |
| ADR-098 | Evaluate ruvnet/midstream for RuView's CSI / WebSocket / mesh pipeline |
Rejected |
| ADR-099 | Adopt midstream as RuView's real-time introspection + low-latency tap | Proposed |
Related
- DDD Domain Models — Bounded context definitions, aggregate roots, and ubiquitous language
- User Guide — Setup, API reference, and hardware instructions
- Build Guide — Building from source