docs(readme): link ecosystem badges + move Beta callout to bottom

Three operator-feedback corrections to the README:

1. Every ecosystem badge in the top row now links to a real
   destination — Home Assistant -> integrations/home-assistant.md,
   Matter -> ADR-122, Apple Home -> user-guide-apple-homepod.md,
   Google Home + Alexa -> the HA integration doc (both ecosystems
   reach RuView through HA's bridge today). Added an Alexa badge
   alongside the existing four so all four major ecosystems are
   represented. Dropped the now-redundant separate "HomePod
   Integration" badge — the Apple Home badge linking to the same
   guide is enough.

2. Beta callout moved from line 14 (under the hero image) to a
   dedicated `## Beta software` section immediately before the
   License. The callout's content is unchanged; it just no longer
   gates the elevator pitch. Readers see the value proposition
   first, the caveats at the bottom alongside license + support.

3. The intro paragraph ("Turn ordinary WiFi into ...") now ends
   with a one-line summary of native ecosystem support naming all
   four — Home Assistant, Apple Home & HomePod, Google Home, Alexa —
   plus the Matter endpoint, each linked. The previous mention of
   ecosystems was buried further down the page; this surfaces it
   in the intro where the user reads first.

Co-Authored-By: claude-flow <ruv@ruv.net>

.claude-flow/daemon-state.json

@@ -1,50 +1,55 @@
 {
   "running": true,
-  "startedAt": "2026-03-09T15:26:00.921Z",
+  "startedAt": "2026-05-24T22:26:25.030Z",
   "workers": {
     "map": {
-      "runCount": 49,
-      "successCount": 49,
+      "runCount": 64,
+      "successCount": 64,
       "failureCount": 0,
-      "averageDurationMs": 1.2857142857142858,
-      "lastRun": "2026-02-28T16:13:19.194Z",
-      "nextRun": "2026-03-09T15:56:00.928Z",
+      "averageDurationMs": 136.171875,
+      "lastRun": "2026-05-25T06:07:33.387Z",
+      "lastStartedAt": "2026-05-25T06:07:33.381Z",
+      "nextRun": "2026-05-25T06:26:25.410Z",
       "isRunning": false
     },
     "audit": {
-      "runCount": 45,
-      "successCount": 0,
+      "runCount": 72,
+      "successCount": 27,
       "failureCount": 45,
-      "averageDurationMs": 0,
-      "lastRun": "2026-03-09T15:43:00.933Z",
-      "nextRun": "2026-03-09T15:38:00.914Z",
+      "averageDurationMs": 26260.11111111111,
+      "lastRun": "2026-05-25T06:08:29.594Z",
+      "lastStartedAt": "2026-05-25T06:07:33.416Z",
+      "nextRun": "2026-05-25T06:18:32.928Z",
       "isRunning": false
     },
     "optimize": {
-      "runCount": 34,
-      "successCount": 0,
-      "failureCount": 34,
-      "averageDurationMs": 0,
-      "lastRun": "2026-02-28T16:23:19.387Z",
-      "nextRun": "2026-03-09T15:45:00.915Z",
+      "runCount": 54,
+      "successCount": 9,
+      "failureCount": 45,
+      "averageDurationMs": 40303.377578766485,
+      "lastRun": "2026-05-25T05:59:05.330Z",
+      "lastStartedAt": "2026-05-25T05:54:05.318Z",
+      "nextRun": "2026-05-25T06:20:15.145Z",
       "isRunning": false
     },
     "consolidate": {
-      "runCount": 23,
-      "successCount": 23,
+      "runCount": 32,
+      "successCount": 32,
       "failureCount": 0,
-      "averageDurationMs": 0.6521739130434783,
-      "lastRun": "2026-02-28T16:05:19.091Z",
-      "nextRun": "2026-03-09T16:02:00.918Z",
+      "averageDurationMs": 4.71875,
+      "lastRun": "2026-05-25T05:38:20.449Z",
+      "lastStartedAt": "2026-05-25T05:38:20.443Z",
+      "nextRun": "2026-05-25T06:32:25.248Z",
       "isRunning": false
     },
     "testgaps": {
-      "runCount": 27,
-      "successCount": 0,
-      "failureCount": 27,
-      "averageDurationMs": 0,
-      "lastRun": "2026-02-28T16:08:19.369Z",
-      "nextRun": "2026-03-09T15:54:00.920Z",
+      "runCount": 100,
+      "successCount": 63,
+      "failureCount": 37,
+      "averageDurationMs": 108604.0537328991,
+      "lastRun": "2026-05-25T06:11:52.529Z",
+      "lastStartedAt": "2026-05-25T06:07:33.390Z",
+      "nextRun": "2026-05-25T06:14:25.296Z",
       "isRunning": false
     },
     "predict": {
@@ -64,8 +69,8 @@
   },
   "config": {
     "autoStart": false,
-    "logDir": "/Users/cohen/GitHub/ruvnet/RuView/.claude-flow/logs",
-    "stateFile": "/Users/cohen/GitHub/ruvnet/RuView/.claude-flow/daemon-state.json",
+    "logDir": "C:\\Users\\ruv\\Projects\\wifi-densepose\\.claude-flow\\logs",
+    "stateFile": "C:\\Users\\ruv\\Projects\\wifi-densepose\\.claude-flow\\daemon-state.json",
     "maxConcurrent": 2,
     "workerTimeoutMs": 300000,
     "resourceThresholds": {
@@ -131,5 +136,5 @@
       }
     ]
   },
-  "savedAt": "2026-03-09T15:43:00.933Z"
+  "savedAt": "2026-05-25T06:11:52.530Z"
 }

.claude-flow/metrics/codebase-map.json

@@ -1,11 +1,11 @@
 {
-  "timestamp": "2026-02-28T16:13:19.193Z",
-  "projectRoot": "/home/user/wifi-densepose",
+  "timestamp": "2026-05-25T06:07:33.385Z",
+  "projectRoot": "C:\\Users\\ruv\\Projects\\wifi-densepose",
   "structure": {
     "hasPackageJson": false,
     "hasTsConfig": false,
     "hasClaudeConfig": true,
     "hasClaudeFlow": true
   },
-  "scannedAt": 1772295199193
+  "scannedAt": 1779689253386
 }

.claude-flow/metrics/consolidation.json

@@ -1,5 +1,5 @@
 {
-  "timestamp": "2026-02-28T16:05:19.091Z",
+  "timestamp": "2026-05-25T05:38:20.448Z",
   "patternsConsolidated": 0,
   "memoryCleaned": 0,
   "duplicatesRemoved": 0

.claude-flow/metrics/performance.json

@@ -0,0 +1,17 @@
+{
+  "timestamp": "2026-05-25T05:59:05.405Z",
+  "mode": "local",
+  "memoryUsage": {
+    "rss": 9891840,
+    "heapTotal": 35598336,
+    "heapUsed": 26516560,
+    "external": 3952418,
+    "arrayBuffers": 55689
+  },
+  "uptime": 27163.5846658,
+  "optimizations": {
+    "cacheHitRate": 0.78,
+    "avgResponseTime": 45
+  },
+  "note": "Install Claude Code CLI for AI-powered optimization suggestions"
+}

.claude-flow/metrics/security-audit.json

@@ -1,12 +1,84 @@
 {
-  "timestamp": "2026-03-06T13:17:27.368Z",
-  "mode": "local",
-  "checks": {
-    "envFilesProtected": true,
-    "gitIgnoreExists": true,
-    "noHardcodedSecrets": true
+  "timestamp": "2026-05-25T06:08:29.589Z",
+  "mode": "headless",
+  "workerType": "audit",
+  "model": "haiku",
+  "durationMs": 56168,
+  "executionId": "audit_1779689253421_dfflmb",
+  "success": true,
+  "findings": {
+    "vulnerabilities": [
+      {
+        "severity": "high",
+        "file": ".claude/helpers/github-safe.js",
+        "line": 50,
+        "description": "Command injection vulnerability in execSync call. User-controlled arguments in `newArgs` are joined without shell escaping. An attacker can inject shell metacharacters (e.g., `; rm -rf /`) via the body content or through command/subcommand parameters. The temp file approach is safe, but the command construction `gh ${command} ${subcommand} ${newArgs.join(' ')}` allows shell injection.",
+        "example": "gh issue comment 123 'test`whoami`' would execute whoami"
+      },
+      {
+        "severity": "high",
+        "file": "scripts/csi-spectrogram.js",
+        "line": 45,
+        "description": "Sensitive credential exposure via command-line arguments. The `--seed-token` parameter is passed as a CLI argument, which is visible in process listings (ps aux output). This violates secure credential handling practices. Tokens should be read from environment variables or secure config files, not command-line args.",
+        "example": "node scripts/csi-spectrogram.js --seed-token secret_abc_123 exposes token in process list"
+      },
+      {
+        "severity": "medium",
+        "file": "scripts/apnea-detector.js",
+        "line": 71,
+        "description": "Unsafe buffer reading without comprehensive length validation. The code checks `buf.length` at 32 bytes (line 70) but then reads at fixed offsets (lines 72-76) without validating that each read stays within bounds. If a malformed packet is received, `readInt8/readUInt16LE/readUInt32LE` may read unintended data or zeros.",
+        "example": "A 33-byte buffer would pass the check but reading UInt32LE at offset 8 would go out of bounds"
+      },
+      {
+        "severity": "medium",
+        "file": "scripts/benchmark-rf-scan.js",
+        "line": 110,
+        "description": "Potential out-of-bounds buffer access in parseCSIFrame. While the bounds check at line 107 is present, the `nSubcarriers` value from the packet is used to calculate required buffer size without validation of the value itself. A maliciously crafted packet with extremely large nSubcarriers could cause memory issues.",
+        "example": "Packet with nSubcarriers=999999 would request excessive buffer allocation"
+      },
+      {
+        "severity": "medium",
+        "file": "scripts/csi-spectrogram.js",
+        "line": 39,
+        "description": "Unsafe URL construction with untrusted `seed-url` parameter. The `--seed-url` argument is used directly for HTTPS requests without validation. This could allow SSRF (Server-Side Request Forgery) or DNS rebinding attacks if an attacker controls the seed URL.",
+        "example": "node scripts/csi-spectrogram.js --seed-url http://internal.local:9000 could access internal services"
+      },
+      {
+        "severity": "low",
+        "file": ".claude/helpers/statusline.js",
+        "line": 140,
+        "description": "Shell command injection risk in execSync calls. Commands like `ps aux 2>/dev/null | grep -c agentic-flow` use grep patterns that could be vulnerable if any variables are interpolated (though currently hardcoded). The `execSync` with shell=true is generally risky.",
+        "example": "If any pattern becomes user-controlled: `grep -c ${pattern}` could inject shell metacharacters"
+      },
+      {
+        "severity": "low",
+        "file": ".claude/helpers/memory.js",
+        "line": 10,
+        "description": "Unvalidated JSON parsing. The code parses JSON from MEMORY_FILE without try-catch in the loadMemory function (catches error but doesn't validate structure). Malformed JSON or corrupted memory file could cause issues.",
+        "example": "Memory file with circular JSON structure could cause issues when stringifying"
+      },
+      {
+        "severity": "low",
+        "file": "scripts/device-fingerprint.js",
+        "line": 72,
+        "description": "Hardcoded device fingerprints and network configuration. While not a traditional 'hardcoded secret', the KNOWN_DEVICES array contains identifiable SSIDs and MAC addresses that could be used to correlate network infrastructure. This data should be externalized or sanitized.",
+        "example": "SSID 'ruv.net' and 'Cohen-Guest' could identify specific installations"
+      }
+    ],
+    "riskScore": 42,
+    "recommendations": [
+      "**CRITICAL**: Replace `execSync` command construction in github-safe.js with proper shell escaping using `child_process.execFile()` instead of `execSync()`, or use the `shell: false` option with array arguments to avoid shell parsing entirely.",
+      "**CRITICAL**: Move `--seed-token` from CLI arguments to environment variable `SEED_TOKEN` in csi-spectrogram.js. Update documentation to instruct users: `export SEED_TOKEN=...` instead of passing via CLI.",
+      "**HIGH**: Add comprehensive buffer bounds validation in all UDP packet parsing functions (apnea-detector.js, benchmark-rf-scan.js, etc.). Validate both the buffer length AND the parsed header values before using them in calculations.",
+      "**HIGH**: Validate and sanitize the `--seed-url` parameter in csi-spectrogram.js. Whitelist allowed domains or restrict to localhost/internal IPs only. Add URL scheme validation (https only).",
+      "**MEDIUM**: Replace hardcoded device fingerprints (KNOWN_DEVICES) with externalized configuration or environment variables. Document that this data contains identifiable network information.",
+      "**MEDIUM**: Add input validation to `parseArgs()` results in all scripts. Validate numeric ranges, file paths, and enum values before use.",
+      "**LOW**: Wrap JSON.parse() calls in try-catch blocks throughout (memory.js, session.js) with explicit error handling and recovery.",
+      "**LOW**: Audit all uses of `require()` with dynamic paths. Ensure paths are always derived from fixed `__dirname` and not user-controlled.",
+      "**LOW**: Remove or sandbox the ability to pass arbitrary URLs via CLI. Consider using a configuration file (YAML/JSON) for endpoint URLs instead.",
+      "**INFO**: Add a pre-commit hook to detect hardcoded credentials using tools like `detect-secrets` or `truffleHog`."
+    ]
   },
-  "riskLevel": "low",
-  "recommendations": [],
-  "note": "Install Claude Code CLI for AI-powered security analysis"
+  "rawOutputPreview": "# Security Audit Report — wifi-densepose\n\n```json\n{\n  \"vulnerabilities\": [\n    {\n      \"severity\": \"high\",\n      \"file\": \".claude/helpers/github-safe.js\",\n      \"line\": 50,\n      \"description\": \"Command injection vulnerability in execSync call. User-controlled arguments in `newArgs` are joined without shell escaping. An attacker can inject shell metacharacters (e.g., `; rm -rf /`) via the body content or through command/subcommand parameters. The temp file approach is safe, but the command construction `gh ${command} ${subcommand} ${newArgs.join(' ')}` allows shell injection.\",\n      \"example\": \"gh issue comment 123 'test`whoami`' would execute whoami\"\n    },\n    {\n      \"severity\": \"high\",\n      \"file\": \"scripts/csi-spectrogram.js\",\n      \"line\": 45,\n      \"description\": \"Sensitive credential exposure via command-line arguments. The `--seed-token` parameter is passed as a CLI argument, which is visible in process listings (ps aux output). This violates secure credential handling practices. Tokens should be read from environment variables or secure config files, not command-line args.\",\n      \"example\": \"node scripts/csi-spectrogram.js --seed-token secret_abc_123 exposes token in process list\"\n    },\n    {\n      \"severity\": \"medium\",\n      \"file\": \"scripts/apnea-detector.js\",\n      \"line\": 71,\n      \"description\": \"Unsafe buffer reading without comprehensive length validation. The code checks `buf.length` at 32 bytes (line 70) but then reads at fixed offsets (lines 72-76) without validating that each read stays within bounds. If a malformed packet is received, `readInt8/readUInt16LE/readUInt32LE` may read unintended data or zeros.\",\n      \"example\": \"A 33-byte buffer would pass the check but reading UInt32LE at offset 8 would go out of bounds\"\n    },\n    {\n      \"severity\": \"medium\",\n      \"file\": \"scripts/benchmark-rf-scan.js\",\n      \"line\": 110,\n      \"description\": \"Potential out-of-bounds buffer access in parseCSIFrame. While the bounds check at line 107 is pres",
+  "rawOutputLength": 7077
 }

.claude-flow/metrics/test-gaps.json

@@ -0,0 +1,106 @@
+{
+  "timestamp": "2026-05-25T06:11:52.519Z",
+  "mode": "headless",
+  "workerType": "testgaps",
+  "model": "sonnet",
+  "durationMs": 259124,
+  "executionId": "testgaps_1779689253395_srltd5",
+  "success": true,
+  "findings": {
+    "sections": [
+      {
+        "title": "Test Coverage Gap Analysis — wifi-densepose",
+        "content": "\n",
+        "level": 2
+      },
+      {
+        "title": "Coverage Summary by Crate",
+        "content": "\n| Crate | Tests Found | Status | Priority |\n|-------|-------------|--------|----------|\n| `wifi-densepose-core` | 26 inline | Good | Low |\n| `wifi-densepose-signal` | ~60 (validation only) | Moderate | **High** |\n| `wifi-densepose-nn` | **0** | Critical | **P1** |\n| `wifi-densepose-train` | ~60 (config/dataset) | Moderate | High |\n| `wifi-densepose-mat` | 1 integration test | Critical | **P1** |\n| `wifi-densepose-ruvector` | **0** | Critical | **P1** |\n| `wifi-densepose-sensing-server` | 4 integration tests | Moderate | High |\n| `wifi-densepose-wasm` | 3 compliance tests | Low | Low |\n\n---\n\n",
+        "level": 3
+      },
+      {
+        "title": "Tier 1: Critical Gaps",
+        "content": "\n",
+        "level": 2
+      },
+      {
+        "title": "1. `wifi-densepose-nn` — Zero test coverage",
+        "content": "\nEvery public API is untested. Place these at `v2/crates/wifi-densepose-nn/tests/inference_tests.rs`:\n\n```rust\n// v2/crates/wifi-densepose-nn/tests/inference_tests.rs\n\n#[cfg(test)]\nmod tensor_tests {\n    use wifi_densepose_nn::tensor::Tensor;\n\n    #[test]\n    fn tensor_shape_mismatch_returns_error() {\n        // data has 6 elements but shape claims 3×3=9\n        let result = Tensor::new(vec![1.0f32; 6], &[3, 3]);\n        assert!(result.is_err(), \"shape mismatch must be rejected\");\n    }\n\n    #[test]\n    fn tensor_empty_data_returns_error() {\n        let result = Tensor::new(vec![], &[0]);\n        assert!(result.is_err());\n    }\n\n    #[test]\n    fn tensor_nan_values_are_detected() {\n        let t = Tensor::new(vec![f32::NAN, 1.0, 2.0], &[3]).unwrap();\n        assert!(t.has_nan(), \"NaN in data must be detectable\");\n    }\n\n    #[test]\n    fn tensor_inf_values_are_detected() {\n        let t = Tensor::new(vec![f32::INFINITY, 1.0], &[2]).unwrap();\n        assert!(t.has_inf());\n    }\n}\n\n#[cfg(test)]\nmod modality_translator_tests {\n    use wifi_densepose_nn::translator::ModalityTranslator;\n\n    #[test]\n    fn translator_rejects_wrong_subcarrier_count() {\n        // standard expects 56 subcarriers; feed 57\n        let csi = vec![0.0f32; 57 * 3]; // 57 subcarriers × 3 antennas\n        let translator = ModalityTranslator::default();\n        let result = translator.translate(&csi, 57, 3);\n        assert!(result.is_err());\n    }\n\n    #[test]\n    fn translator_handles_all_zeros() {\n        let csi = vec![0.0f32; 56 * 3];\n        let translator = ModalityTranslator::default();\n        let result = translator.translate(&csi, 56, 3);\n        // zero input should produce some output without panic\n        assert!(result.is_ok());\n    }\n}\n\n#[cfg(test)]\nmod inference_engine_tests {\n    use wifi_densepose_nn::inference::InferenceEngine;\n\n    #[test]\n    fn load_nonexistent_model_returns_error() {\n        let result = InferenceEngine::from_path(\"/nonexistent/model.onnx\");\n        assert!(result.is_err());\n    }\n\n    #[test]\n    fn load_corrupted_bytes_returns_error() {\n        let tmp = tempfile::NamedTempFile::new().unwrap();\n        std::fs::write(tmp.path(), b\"not a valid onnx file\").unwrap();\n        let result = InferenceEngine::from_path(tmp.path());\n        assert!(result.is_err());\n    }\n\n    #[test]\n    fn batch_size_zero_returns_error() {\n        // can't run inference on an empty batch\n        // requires a valid model; skip if no model file in test fixtures\n        // use #[ignore] or a feature flag for CI\n    }\n}\n```\n\n---\n\n",
+        "level": 3
+      },
+      {
+        "title": "2. `wifi-densepose-mat` — Disaster response safety gaps",
+        "content": "\nPlace at `v2/crates/wifi-densepose-mat/tests/`:\n\n```rust\n// v2/crates/wifi-densepose-mat/tests/detection_edge_cases.rs\n\n#[cfg(test)]\nmod breathing_rate_edge_cases {\n    use wifi_densepose_mat::detection::breathing::BreathingDetector;\n\n    #[test]\n    fn zero_bpm_is_classified_critical() {\n        let detector = BreathingDetector::default();\n        // flat-line signal — no breathing detected\n        let signal = vec![0.0f32; 1000];\n        let result = detector.classify(&signal).unwrap();\n        assert_eq!(result.triage_category, TriageCategory::Immediate);\n    }\n\n    #[test]\n    fn agonal_breathing_rate_triggers_immediate() {\n        // < 6 BPM is agonal; simulate 3 BPM signal\n        let detector = BreathingDetector::default();\n        let signal = generate_breathing_signal(3.0, 1000, 100.0); // 3 BPM, 1000 samples @ 100 Hz\n        let result = detector.classify(&signal).unwrap();\n        assert_eq!(result.triage_category, TriageCategory::Immediate);\n    }\n\n    #[test]\n    fn normal_breathing_is_classified_minor() {\n        let detector = BreathingDetector::default();\n        let signal = generate_breathing_signal(15.0, 1000, 100.0); // 15 BPM\n        let result = detector.classify(&signal).unwrap();\n        assert_eq!(result.triage_category, TriageCategory::Minor);\n    }\n\n    #[test]\n    fn all_nan_signal_returns_error_not_panic() {\n        let detector = BreathingDetector::default();\n        let signal = vec![f32::NAN; 1000];\n        let result = detector.classify(&signal);\n        assert!(result.is_err(), \"NaN input must be caught, not panic\");\n    }\n\n    fn generate_breathing_signal(bpm: f32, samples: usize, sample_rate: f32) -> Vec<f32> {\n        let freq = bpm / 60.0;\n        (0..samples)\n            .map(|i| (2.0 * std::f32::consts::PI * freq * i as f32 / sample_rate).sin())\n            .collect()\n    }\n}\n\n#[cfg(test)]\nmod alert_deduplication {\n    use wifi_densepose_mat::alerting::{AlertDispatcher, Alert, TriageCategory};\n    use std::time::Duration;\n\n    #[test]\n    fn duplicate_alerts_within_window_are_suppressed() {\n        let mut dispatcher = AlertDispatcher::new();\n        let alert = Alert::new(\"survivor-1\", TriageCategory::Immediate);\n        dispatcher.dispatch(alert.clone());\n        dispatcher.dispatch(alert.clone()); // same survivor, same category\n        assert_eq!(dispatcher.queued_count(), 1, \"duplicate must be deduplicated\");\n    }\n\n    #[test]\n    fn escalation_from_minor_to_immediate_is_forwarded() {\n        let mut dispatcher = AlertDispatcher::new();\n        dispatcher.dispatch(Alert::new(\"survivor-1\", TriageCategory::Minor));\n        dispatcher.dispatch(Alert::new(\"survivor-1\", TriageCategory::Immediate));\n        // escalation is not a duplicate — must pass through\n        assert!(dispatcher.last_alert_for(\"survivor-1\").map(|a| a.category) == Some(TriageCategory::Immediate));\n    }\n}\n\n#[cfg(test)]\nmod kalman_tracker_edge_cases {\n    use wifi_densepose_mat::tracking::KalmanTracker;\n\n    #[test]\n    fn position_jump_does_not_corrupt_state() {\n        let mut tracker = KalmanTracker::new();\n        tracker.update([1.0, 1.0, 0.5]);  // initial position\n        tracker.update([50.0, 50.0, 0.5]); // physically impossible jump\n        let pos = tracker.estimated_position();\n        // should not panic; should clamp or flag anomaly\n        assert!(pos.iter().all(|v| v.is_finite()));\n    }\n\n    #[test]\n    fn lost_track_resumes_on_re_detection() {\n        let mut tracker = KalmanTracker::new();\n        tracker.update([1.0, 1.0, 0.5]);\n        // simulate 10 missed frames\n        for _ in 0..10 { tracker.predict(); }\n        assert_eq!(tracker.state(), TrackState::Lost);\n        tracker.update([1.1, 1.1, 0.5]); // re-detected nearby\n        assert_eq!(tracker.state(), TrackState::Confirmed);\n    }\n}\n```\n\n---\n\n",
+        "level": 3
+      },
+      {
+        "title": "3. `wifi-densepose-ruvector` — Zero coverage on all 5 integration modules",
+        "content": "\n```rust\n// v2/crates/wifi-densepose-ruvector/tests/viewpoint_tests.rs\n\n#[cfg(test)]\nmod attention_tests {\n    use wifi_densepose_ruvector::viewpoint::attention::CrossViewpointAttention;\n\n    #[test]\n    fn attention_weights_sum_to_one() {\n        let attn = CrossViewpointAttention::new(3); // 3 viewpoints\n        let features = vec![[1.0f32; 64], [2.0f32; 64], [3.0f32; 64]];\n        let weights = attn.compute_weights(&features);\n        let sum: f32 = weights.iter().sum();\n        assert!((sum - 1.0).abs() < 1e-5, \"attention must be a probability distribution\");\n    }\n\n    #[test]\n    fn single_viewpoint_gets_full_weight() {\n        let attn = CrossViewpointAttention::new(1);\n        let features = vec![[1.0f32; 64]];\n        let weights = attn.compute_weights(&features);\n        assert!((weights[0] - 1.0).abs() < 1e-6);\n    }\n\n    #[test]\n    fn zero_feature_vectors_do_not_produce_nan() {\n        let attn = CrossViewpointAttention::new(2);\n        let features = vec![[0.0f32; 64], [0.0f32; 64]];\n        let weights = attn.compute_weights(&features);\n        assert!(weights.iter().all(|w| w.is_finite()));\n    }\n}\n\n#[cfg(test)]\nmod sketch_tests {\n    use wifi_densepose_ruvector::sketch::WireSketch;\n\n    #[test]\n    fn round_trip_serialization() {\n        let sketch = WireSketch::from_keypoints(&[[0.5f32, 0.5], [0.3, 0.7]]);\n        let bytes = sketch.to_bytes();\n        let restored = WireSketch::from_bytes(&bytes).unwrap();\n        assert_eq!(sketch, restored);\n    }\n\n    #[test]\n    fn deserialize_truncated_bytes_returns_error() {\n        let sketch = WireSketch::from_keypoints(&[[0.5f32, 0.5]]);\n        let mut bytes = sketch.to_bytes();\n        bytes.truncate(bytes.len() / 2); // truncate halfway\n        assert!(WireSketch::from_bytes(&bytes).is_err());\n    }\n\n    #[test]\n    fn empty_keypoint_list_is_handled() {\n        let sketch = WireSketch::from_keypoints(&[]);\n        assert_eq!(sketch.keypoint_count(), 0);\n    }\n}\n```\n\n---\n\n",
+        "level": 3
+      },
+      {
+        "title": "Tier 2: Signal Processing Gaps",
+        "content": "\n",
+        "level": 2
+      },
+      {
+        "title": "4. `wifi-densepose-signal` — RuvSense module untested",
+        "content": "\n```rust\n// v2/crates/wifi-densepose-signal/tests/ruvsense_tests.rs\n\n#[cfg(test)]\nmod coherence_gate_tests {\n    use wifi_densepose_signal::ruvsense::coherence_gate::{CoherenceGate, GateDecision};\n\n    #[test]\n    fn high_coherence_signal_is_accepted() {\n        let gate = CoherenceGate::new(0.7); // threshold = 0.7\n        let decision = gate.evaluate(0.95);\n        assert_eq!(decision, GateDecision::Accept);\n    }\n\n    #[test]\n    fn low_coherence_signal_is_rejected() {\n        let gate = CoherenceGate::new(0.7);\n        let decision = gate.evaluate(0.3);\n        assert_eq!(decision, GateDecision::Reject);\n    }\n\n    #[test]\n    fn borderline_coherence_triggers_recalibrate() {\n        let gate = CoherenceGate::new(0.7);\n        let decision = gate.evaluate(0.68); // just below threshold\n        assert_eq!(decision, GateDecision::Recalibrate);\n    }\n}\n\n#[cfg(test)]\nmod phase_align_tests {\n    use wifi_densepose_signal::ruvsense::phase_align::PhaseAligner;\n\n    #[test]\n    fn phase_at_plus_pi_does_not_wrap_incorrectly() {\n        let aligner = PhaseAligner::new();\n        let phases = vec![std::f32::consts::PI - 0.001, std::f32::consts::PI + 0.001];\n        let aligned = aligner.align(&phases);\n        // jump across ±π boundary must be handled continuously\n        let diff = (aligned[1] - aligned[0]).abs();\n        assert!(diff < 0.01, \"phase jump at ±π must be < 0.01 rad after alignment\");\n    }\n\n    #[test]\n    fn single_phase_value_aligns_to_itself() {\n        let aligner = PhaseAligner::new();\n        let phases = vec![1.5f32];\n        let aligned = aligner.align(&phases);\n        assert_eq!(aligned.len(), 1);\n        assert!((aligned[0] - 1.5).abs() < 1e-6);\n    }\n\n    #[test]\n    fn empty_phase_array_returns_empty() {\n        let aligner = PhaseAligner::new();\n        let aligned = aligner.align(&[]);\n        assert!(aligned.is_empty());\n    }\n}\n\n#[cfg(test)]\nmod adversarial_detection_tests {\n    use wifi_densepose_signal::ruvsense::adversarial::AdversarialDetector;\n\n    #[test]\n    fn physically_impossible_amplitude_is_flagged() {\n        let detector = AdversarialDetector::new();\n        // WiFi amplitude cannot exceed hardware saturation level\n        let frame = vec![1e9f32; 56]; // absurdly large\n        assert!(detector.is_suspicious(&frame));\n    }\n\n    #[test]\n    fn normal_amplitude_range_passes() {\n        let detector = AdversarialDetector::new();\n        let frame = vec![0.5f32; 56]; // typical normalized value\n        assert!(!detector.is_suspicious(&frame));\n    }\n\n    #[test]\n    fn multi_link_inconsistency_is_detected() {\n        // link A reports body moving right; link B reports no motion\n        // physically inconsistent — flag as adversarial\n        let detector = AdversarialDetector::new();\n        let result = detector.check_multi_link_consistency(\n            &[1.0, 2.0, 3.0], // link A\n            &[0.0, 0.0, 0.0], // link B (no motion)\n        );\n        assert!(result.is_inconsistent());\n    }\n}\n```\n\n---\n\n",
+        "level": 3
+      },
+      {
+        "title": "Tier 2: Training Pipeline Gaps",
+        "content": "\n",
+        "level": 2
+      },
+      {
+        "title": "5. `wifi-densepose-train` — Geometry encoder and rapid adaptation untested",
+        "content": "\n```rust\n// v2/crates/wifi-densepose-train/tests/test_geometry.rs\n\n#[cfg(test)]\nmod film_layer_tests {\n    use wifi_densepose_train::geometry::FilmLayer;\n\n    #[test]\n    fn film_layer_output_shape_matches_input() {\n        let film = FilmLayer::new(64, 32); // 64-dim features, 32-dim condition\n        let features = vec![0.5f32; 64];\n        let condition = vec![1.0f32; 32];\n        let output = film.forward(&features, &condition).unwrap();\n        assert_eq!(output.len(), 64, \"FiLM output must match feature dimensionality\");\n    }\n\n    #[test]\n    fn film_layer_zero_condition_acts_as_identity() {\n        let film = FilmLayer::new(64, 32);\n        let features = vec![1.0f32; 64];\n        let zero_condition = vec![0.0f32; 32];\n        let output = film.forward(&features, &zero_condition).unwrap();\n        // scale=1, shift=0 → identity; output ≈ input\n        for (o, f) in output.iter().zip(features.iter()) {\n            assert!((o - f).abs() < 0.1, \"zero condition should approximate identity\");\n        }\n    }\n}\n\n// v2/crates/wifi-densepose-train/tests/test_rapid_adapt.rs\n\n#[cfg(test)]\nmod rapid_adaptation_tests {\n    use wifi_densepose_train::rapid_adapt::RapidAdapter;\n\n    #[test]\n    fn adapter_updates_on_single_sample() {\n        let mut adapter = RapidAdapter::new(5); // 5 adaptation steps\n        let csi_sample = vec![0.1f32; 56 * 3];\n        let pose_label = vec![0.5f32; 17 * 2]; // 17 keypoints × (x, y)\n        let result = adapter.adapt_step(&csi_sample, &pose_label);\n        assert!(result.is_ok());\n    }\n\n    #[test]\n    fn adapter_with_zero_steps_is_no_op() {\n        let adapter = RapidAdapter::new(0);\n        // 0 adaptation steps → weights unchanged\n        let initial_weights = adapter.clone_weights();\n        let _ = adapter.adapt_step(&vec![0.1f32; 168], &vec![0.5f32; 34]);\n        assert_eq!(adapter.clone_weights(), initial_weights);\n    }\n}\n```\n\n---\n\n",
+        "level": 3
+      },
+      {
+        "title": "Tier 3: Server Integration Gaps",
+        "content": "\n",
+        "level": 2
+      },
+      {
+        "title": "6. `wifi-densepose-sensing-server` — Auth and semantic analyzers",
+        "content": "\n```rust\n// v2/crates/wifi-densepose-sensing-server/tests/auth_tests.rs\n\n#[cfg(test)]\nmod bearer_auth_tests {\n    use wifi_densepose_sensing_server::auth::{BearerValidator, TokenError};\n\n    #[test]\n    fn missing_authorization_header_returns_unauthorized() {\n        let validator = BearerValidator::new(\"secret-token\");\n        let result = validator.validate(None);\n        assert!(matches!(result, Err(TokenError::Missing)));\n    }\n\n    #[test]\n    fn wrong_token_is_rejected() {\n        let validator = BearerValidator::new(\"correct-token\");\n        let result = validator.validate(Some(\"Bearer wrong-token\"));\n        assert!(matches!(result, Err(TokenError::Invalid)));\n    }\n\n    #[test]\n    fn malformed_header_without_bearer_prefix_is_rejected() {\n        let validator = BearerValidator::new(\"token\");\n        let result = validator.validate(Some(\"token\")); // missing \"Bearer \" prefix\n        assert!(matches!(result, Err(TokenError::Malformed)));\n    }\n\n    #[test]\n    fn correct_token_is_accepted() {\n        let validator = BearerValidator::new(\"correct-token\");\n        let result = validator.validate(Some(\"Bearer correct-token\"));\n        assert!(result.is_ok());\n    }\n}\n\n// v2/crates/wifi-densepose-sensing-server/tests/semantic_tests.rs\n\n#[cfg(test)]\nmod fall_detection_tests {\n    use wifi_densepose_sensing_server::semantic::fall_detector::FallDetector;\n\n    #[test]\n    fn no_motion_does_not_trigger_fall() {\n        let mut detector = FallDetector::new();\n        for _ in 0..30 { // 30 frames of stillness\n            detector.update_pose(stationary_pose());\n        }\n        assert!(!detector.fall_detected());\n    }\n\n    #[test]\n    fn rapid_downward_velocity_triggers_fall() {\n        let mut detector = FallDetector::new();\n        // simulate person going from standing (y=1.7m) to prone (y=0.3m) in 3 frames\n        for (frame, y) in [(0, 1.7f32), (1, 1.0), (2, 0.3)] {\n            detector.update_pose(pose_at_height(y));\n        }\n        assert!(detector.fall_detected());\n    }\n\n    #[test]\n    fn sitting_down_slowly_does_not_trigger_fall() {\n        let mut detector = FallDetector::new();\n        // gradual height decrease over 30 frames is sitting, not falling\n        for i in 0..30 {\n            let y = 1.7f32 - (i as f32 * 0.04); // ~1.2m drop over 30 frames\n            detector.update_pose(pose_at_height(y));\n        }\n        assert!(!detector.fall_detected());\n    }\n}\n```\n\n---\n\n",
+        "level": 3
+      },
+      {
+        "title": "Cross-Cutting Gap Summary",
+        "content": "| Gap Category | Severity | Affects | Recommended Action |\n|---|---|---|---|\n| `wifi-densepose-nn` has 0 tests | **Critical** | Inference pipeline | Add `tests/inference_tests.rs` per skeleton above |\n| `wifi-densepose-ruvector` has 0 tests | **Critical** | Viewpoint fusion, sketches | Add `tests/viewpoint_tests.rs` |\n| MAT disaster response missing edge cases | **Critical** | 0 BPM, agonal breathing, dedup | Add `tests/detection_edge_cases.rs` |\n| Signal RuvSense 28 modules untested | High | Core sensing logic | Add `tests/ruvsense_tests.rs` |\n| NN error paths (bad model files, OOM) | High | Production reliability | Add error path tests to nn |\n| Train geometry + rapid adapt = 0 tests | High | Domain adaptation | Add `tests/test_geometry.rs` |\n| Server auth token validation | High | Security boundary | Add `tests/auth_tests.rs` |\n| NaN/Inf propagation in f32 pipelines | High | All numeric crates | Add boundary tests per module |\n| Concurrent state under Arc<Mutex> | Medium | sensing-server, mat | Add contention tests |\n\nThe highest-ROI starting point is `wifi-densepose-nn` and `wifi-densepose-mat` — the nn crate has zero tests on the core inference pipeline, and mat covers life-safety scenarios where classification errors have real consequences.",
+        "level": 2
+      }
+    ],
+    "codeBlocks": [
+      {
+        "language": "rust",
+        "code": "// v2/crates/wifi-densepose-nn/tests/inference_tests.rs\n\n#[cfg(test)]\nmod tensor_tests {\n    use wifi_densepose_nn::tensor::Tensor;\n\n    #[test]\n    fn tensor_shape_mismatch_returns_error() {\n        // data has 6 elements but shape claims 3×3=9\n        let result = Tensor::new(vec![1.0f32; 6], &[3, 3]);\n        assert!(result.is_err(), \"shape mismatch must be rejected\");\n    }\n\n    #[test]\n    fn tensor_empty_data_returns_error() {\n        let result = Tensor::new(vec![], &[0]);\n        assert!(result.is_err());\n    }\n\n    #[test]\n    fn tensor_nan_values_are_detected() {\n        let t = Tensor::new(vec![f32::NAN, 1.0, 2.0], &[3]).unwrap();\n        assert!(t.has_nan(), \"NaN in data must be detectable\");\n    }\n\n    #[test]\n    fn tensor_inf_values_are_detected() {\n        let t = Tensor::new(vec![f32::INFINITY, 1.0], &[2]).unwrap();\n        assert!(t.has_inf());\n    }\n}\n\n#[cfg(test)]\nmod modality_translator_tests {\n    use wifi_densepose_nn::translator::ModalityTranslator;\n\n    #[test]\n    fn translator_rejects_wrong_subcarrier_count() {\n        // standard expects 56 subcarriers; feed 57\n        let csi = vec![0.0f32; 57 * 3]; // 57 subcarriers × 3 antennas\n        let translator = ModalityTranslator::default();\n        let result = translator.translate(&csi, 57, 3);\n        assert!(result.is_err());\n    }\n\n    #[test]\n    fn translator_handles_all_zeros() {\n        let csi = vec![0.0f32; 56 * 3];\n        let translator = ModalityTranslator::default();\n        let result = translator.translate(&csi, 56, 3);\n        // zero input should produce some output without panic\n        assert!(result.is_ok());\n    }\n}\n\n#[cfg(test)]\nmod inference_engine_tests {\n    use wifi_densepose_nn::inference::InferenceEngine;\n\n    #[test]\n    fn load_nonexistent_model_returns_error() {\n        let result = InferenceEngine::from_path(\"/nonexistent/model.onnx\");\n        assert!(result.is_err());\n    }\n\n    #[test]\n    fn load_corrupted_bytes_returns_error() {\n        let tmp = tempfile::NamedTempFile::new().unwrap();\n        std::fs::write(tmp.path(), b\"not a valid onnx file\").unwrap();\n        let result = InferenceEngine::from_path(tmp.path());\n        assert!(result.is_err());\n    }\n\n    #[test]\n    fn batch_size_zero_returns_error() {\n        // can't run inference on an empty batch\n        // requires a valid model; skip if no model file in test fixtures\n        // use #[ignore] or a feature flag for CI\n    }\n}"
+      },
+      {
+        "language": "rust",
+        "code": "// v2/crates/wifi-densepose-mat/tests/detection_edge_cases.rs\n\n#[cfg(test)]\nmod breathing_rate_edge_cases {\n    use wifi_densepose_mat::detection::breathing::BreathingDetector;\n\n    #[test]\n    fn zero_bpm_is_classified_critical() {\n        let detector = BreathingDetector::default();\n        // flat-line signal — no breathing detected\n        let signal = vec![0.0f32; 1000];\n        let result = detector.classify(&signal).unwrap();\n        assert_eq!(result.triage_category, TriageCategory::Immediate);\n    }\n\n    #[test]\n    fn agonal_breathing_rate_triggers_immediate() {\n        // < 6 BPM is agonal; simulate 3 BPM signal\n        let detector = BreathingDetector::default();\n        let signal = generate_breathing_signal(3.0, 1000, 100.0); // 3 BPM, 1000 samples @ 100 Hz\n        let result = detector.classify(&signal).unwrap();\n        assert_eq!(result.triage_category, TriageCategory::Immediate);\n    }\n\n    #[test]\n    fn normal_breathing_is_classified_minor() {\n        let detector = BreathingDetector::default();\n        let signal = generate_breathing_signal(15.0, 1000, 100.0); // 15 BPM\n        let result = detector.classify(&signal).unwrap();\n        assert_eq!(result.triage_category, TriageCategory::Minor);\n    }\n\n    #[test]\n    fn all_nan_signal_returns_error_not_panic() {\n        let detector = BreathingDetector::default();\n        let signal = vec![f32::NAN; 1000];\n        let result = detector.classify(&signal);\n        assert!(result.is_err(), \"NaN input must be caught, not panic\");\n    }\n\n    fn generate_breathing_signal(bpm: f32, samples: usize, sample_rate: f32) -> Vec<f32> {\n        let freq = bpm / 60.0;\n        (0..samples)\n            .map(|i| (2.0 * std::f32::consts::PI * freq * i as f32 / sample_rate).sin())\n            .collect()\n    }\n}\n\n#[cfg(test)]\nmod alert_deduplication {\n    use wifi_densepose_mat::alerting::{AlertDispatcher, Alert, TriageCategory};\n    use std::time::Duration;\n\n    #[test]\n    fn duplicate_alerts_within_window_are_suppressed() {\n        let mut dispatcher = AlertDispatcher::new();\n        let alert = Alert::new(\"survivor-1\", TriageCategory::Immediate);\n        dispatcher.dispatch(alert.clone());\n        dispatcher.dispatch(alert.clone()); // same survivor, same category\n        assert_eq!(dispatcher.queued_count(), 1, \"duplicate must be deduplicated\");\n    }\n\n    #[test]\n    fn escalation_from_minor_to_immediate_is_forwarded() {\n        let mut dispatcher = AlertDispatcher::new();\n        dispatcher.dispatch(Alert::new(\"survivor-1\", TriageCategory::Minor));\n        dispatcher.dispatch(Alert::new(\"survivor-1\", TriageCategory::Immediate));\n        // escalation is not a duplicate — must pass through\n        assert!(dispatcher.last_alert_for(\"survivor-1\").map(|a| a.category) == Some(TriageCategory::Immediate));\n    }\n}\n\n#[cfg(test)]\nmod kalman_tracker_edge_cases {\n    use wifi_densepose_mat::tracking::KalmanTracker;\n\n    #[test]\n    fn position_jump_does_not_corrupt_state() {\n        let mut tracker = KalmanTracker::new();\n        tracker.update([1.0, 1.0, 0.5]);  // initial position\n        tracker.update([50.0, 50.0, 0.5]); // physically impossible jump\n        let pos = tracker.estimated_position();\n        // should not panic; should clamp or flag anomaly\n        assert!(pos.iter().all(|v| v.is_finite()));\n    }\n\n    #[test]\n    fn lost_track_resumes_on_re_detection() {\n        let mut tracker = KalmanTracker::new();\n        tracker.update([1.0, 1.0, 0.5]);\n        // simulate 10 missed frames\n        for _ in 0..10 { tracker.predict(); }\n        assert_eq!(tracker.state(), TrackState::Lost);\n        tracker.update([1.1, 1.1, 0.5]); // re-detected nearby\n        assert_eq!(tracker.state(), TrackState::Confirmed);\n    }\n}"
+      },
+      {
+        "language": "rust",
+        "code": "// v2/crates/wifi-densepose-ruvector/tests/viewpoint_tests.rs\n\n#[cfg(test)]\nmod attention_tests {\n    use wifi_densepose_ruvector::viewpoint::attention::CrossViewpointAttention;\n\n    #[test]\n    fn attention_weights_sum_to_one() {\n        let attn = CrossViewpointAttention::new(3); // 3 viewpoints\n        let features = vec![[1.0f32; 64], [2.0f32; 64], [3.0f32; 64]];\n        let weights = attn.compute_weights(&features);\n        let sum: f32 = weights.iter().sum();\n        assert!((sum - 1.0).abs() < 1e-5, \"attention must be a probability distribution\");\n    }\n\n    #[test]\n    fn single_viewpoint_gets_full_weight() {\n        let attn = CrossViewpointAttention::new(1);\n        let features = vec![[1.0f32; 64]];\n        let weights = attn.compute_weights(&features);\n        assert!((weights[0] - 1.0).abs() < 1e-6);\n    }\n\n    #[test]\n    fn zero_feature_vectors_do_not_produce_nan() {\n        let attn = CrossViewpointAttention::new(2);\n        let features = vec![[0.0f32; 64], [0.0f32; 64]];\n        let weights = attn.compute_weights(&features);\n        assert!(weights.iter().all(|w| w.is_finite()));\n    }\n}\n\n#[cfg(test)]\nmod sketch_tests {\n    use wifi_densepose_ruvector::sketch::WireSketch;\n\n    #[test]\n    fn round_trip_serialization() {\n        let sketch = WireSketch::from_keypoints(&[[0.5f32, 0.5], [0.3, 0.7]]);\n        let bytes = sketch.to_bytes();\n        let restored = WireSketch::from_bytes(&bytes).unwrap();\n        assert_eq!(sketch, restored);\n    }\n\n    #[test]\n    fn deserialize_truncated_bytes_returns_error() {\n        let sketch = WireSketch::from_keypoints(&[[0.5f32, 0.5]]);\n        let mut bytes = sketch.to_bytes();\n        bytes.truncate(bytes.len() / 2); // truncate halfway\n        assert!(WireSketch::from_bytes(&bytes).is_err());\n    }\n\n    #[test]\n    fn empty_keypoint_list_is_handled() {\n        let sketch = WireSketch::from_keypoints(&[]);\n        assert_eq!(sketch.keypoint_count(), 0);\n    }\n}"
+      },
+      {
+        "language": "rust",
+        "code": "// v2/crates/wifi-densepose-signal/tests/ruvsense_tests.rs\n\n#[cfg(test)]\nmod coherence_gate_tests {\n    use wifi_densepose_signal::ruvsense::coherence_gate::{CoherenceGate, GateDecision};\n\n    #[test]\n    fn high_coherence_signal_is_accepted() {\n        let gate = CoherenceGate::new(0.7); // threshold = 0.7\n        let decision = gate.evaluate(0.95);\n        assert_eq!(decision, GateDecision::Accept);\n    }\n\n    #[test]\n    fn low_coherence_signal_is_rejected() {\n        let gate = CoherenceGate::new(0.7);\n        let decision = gate.evaluate(0.3);\n        assert_eq!(decision, GateDecision::Reject);\n    }\n\n    #[test]\n    fn borderline_coherence_triggers_recalibrate() {\n        let gate = CoherenceGate::new(0.7);\n        let decision = gate.evaluate(0.68); // just below threshold\n        assert_eq!(decision, GateDecision::Recalibrate);\n    }\n}\n\n#[cfg(test)]\nmod phase_align_tests {\n    use wifi_densepose_signal::ruvsense::phase_align::PhaseAligner;\n\n    #[test]\n    fn phase_at_plus_pi_does_not_wrap_incorrectly() {\n        let aligner = PhaseAligner::new();\n        let phases = vec![std::f32::consts::PI - 0.001, std::f32::consts::PI + 0.001];\n        let aligned = aligner.align(&phases);\n        // jump across ±π boundary must be handled continuously\n        let diff = (aligned[1] - aligned[0]).abs();\n        assert!(diff < 0.01, \"phase jump at ±π must be < 0.01 rad after alignment\");\n    }\n\n    #[test]\n    fn single_phase_value_aligns_to_itself() {\n        let aligner = PhaseAligner::new();\n        let phases = vec![1.5f32];\n        let aligned = aligner.align(&phases);\n        assert_eq!(aligned.len(), 1);\n        assert!((aligned[0] - 1.5).abs() < 1e-6);\n    }\n\n    #[test]\n    fn empty_phase_array_returns_empty() {\n        let aligner = PhaseAligner::new();\n        let aligned = aligner.align(&[]);\n        assert!(aligned.is_empty());\n    }\n}\n\n#[cfg(test)]\nmod adversarial_detection_tests {\n    use wifi_densepose_signal::ruvsense::adversarial::AdversarialDetector;\n\n    #[test]\n    fn physically_impossible_amplitude_is_flagged() {\n        let detector = AdversarialDetector::new();\n        // WiFi amplitude cannot exceed hardware saturation level\n        let frame = vec![1e9f32; 56]; // absurdly large\n        assert!(detector.is_suspicious(&frame));\n    }\n\n    #[test]\n    fn normal_amplitude_range_passes() {\n        let detector = AdversarialDetector::new();\n        let frame = vec![0.5f32; 56]; // typical normalized value\n        assert!(!detector.is_suspicious(&frame));\n    }\n\n    #[test]\n    fn multi_link_inconsistency_is_detected() {\n        // link A reports body moving right; link B reports no motion\n        // physically inconsistent — flag as adversarial\n        let detector = AdversarialDetector::new();\n        let result = detector.check_multi_link_consistency(\n            &[1.0, 2.0, 3.0], // link A\n            &[0.0, 0.0, 0.0], // link B (no motion)\n        );\n        assert!(result.is_inconsistent());\n    }\n}"
+      },
+      {
+        "language": "rust",
+        "code": "// v2/crates/wifi-densepose-train/tests/test_geometry.rs\n\n#[cfg(test)]\nmod film_layer_tests {\n    use wifi_densepose_train::geometry::FilmLayer;\n\n    #[test]\n    fn film_layer_output_shape_matches_input() {\n        let film = FilmLayer::new(64, 32); // 64-dim features, 32-dim condition\n        let features = vec![0.5f32; 64];\n        let condition = vec![1.0f32; 32];\n        let output = film.forward(&features, &condition).unwrap();\n        assert_eq!(output.len(), 64, \"FiLM output must match feature dimensionality\");\n    }\n\n    #[test]\n    fn film_layer_zero_condition_acts_as_identity() {\n        let film = FilmLayer::new(64, 32);\n        let features = vec![1.0f32; 64];\n        let zero_condition = vec![0.0f32; 32];\n        let output = film.forward(&features, &zero_condition).unwrap();\n        // scale=1, shift=0 → identity; output ≈ input\n        for (o, f) in output.iter().zip(features.iter()) {\n            assert!((o - f).abs() < 0.1, \"zero condition should approximate identity\");\n        }\n    }\n}\n\n// v2/crates/wifi-densepose-train/tests/test_rapid_adapt.rs\n\n#[cfg(test)]\nmod rapid_adaptation_tests {\n    use wifi_densepose_train::rapid_adapt::RapidAdapter;\n\n    #[test]\n    fn adapter_updates_on_single_sample() {\n        let mut adapter = RapidAdapter::new(5); // 5 adaptation steps\n        let csi_sample = vec![0.1f32; 56 * 3];\n        let pose_label = vec![0.5f32; 17 * 2]; // 17 keypoints × (x, y)\n        let result = adapter.adapt_step(&csi_sample, &pose_label);\n        assert!(result.is_ok());\n    }\n\n    #[test]\n    fn adapter_with_zero_steps_is_no_op() {\n        let adapter = RapidAdapter::new(0);\n        // 0 adaptation steps → weights unchanged\n        let initial_weights = adapter.clone_weights();\n        let _ = adapter.adapt_step(&vec![0.1f32; 168], &vec![0.5f32; 34]);\n        assert_eq!(adapter.clone_weights(), initial_weights);\n    }\n}"
+      },
+      {
+        "language": "rust",
+        "code": "// v2/crates/wifi-densepose-sensing-server/tests/auth_tests.rs\n\n#[cfg(test)]\nmod bearer_auth_tests {\n    use wifi_densepose_sensing_server::auth::{BearerValidator, TokenError};\n\n    #[test]\n    fn missing_authorization_header_returns_unauthorized() {\n        let validator = BearerValidator::new(\"secret-token\");\n        let result = validator.validate(None);\n        assert!(matches!(result, Err(TokenError::Missing)));\n    }\n\n    #[test]\n    fn wrong_token_is_rejected() {\n        let validator = BearerValidator::new(\"correct-token\");\n        let result = validator.validate(Some(\"Bearer wrong-token\"));\n        assert!(matches!(result, Err(TokenError::Invalid)));\n    }\n\n    #[test]\n    fn malformed_header_without_bearer_prefix_is_rejected() {\n        let validator = BearerValidator::new(\"token\");\n        let result = validator.validate(Some(\"token\")); // missing \"Bearer \" prefix\n        assert!(matches!(result, Err(TokenError::Malformed)));\n    }\n\n    #[test]\n    fn correct_token_is_accepted() {\n        let validator = BearerValidator::new(\"correct-token\");\n        let result = validator.validate(Some(\"Bearer correct-token\"));\n        assert!(result.is_ok());\n    }\n}\n\n// v2/crates/wifi-densepose-sensing-server/tests/semantic_tests.rs\n\n#[cfg(test)]\nmod fall_detection_tests {\n    use wifi_densepose_sensing_server::semantic::fall_detector::FallDetector;\n\n    #[test]\n    fn no_motion_does_not_trigger_fall() {\n        let mut detector = FallDetector::new();\n        for _ in 0..30 { // 30 frames of stillness\n            detector.update_pose(stationary_pose());\n        }\n        assert!(!detector.fall_detected());\n    }\n\n    #[test]\n    fn rapid_downward_velocity_triggers_fall() {\n        let mut detector = FallDetector::new();\n        // simulate person going from standing (y=1.7m) to prone (y=0.3m) in 3 frames\n        for (frame, y) in [(0, 1.7f32), (1, 1.0), (2, 0.3)] {\n            detector.update_pose(pose_at_height(y));\n        }\n        assert!(detector.fall_detected());\n    }\n\n    #[test]\n    fn sitting_down_slowly_does_not_trigger_fall() {\n        let mut detector = FallDetector::new();\n        // gradual height decrease over 30 frames is sitting, not falling\n        for i in 0..30 {\n            let y = 1.7f32 - (i as f32 * 0.04); // ~1.2m drop over 30 frames\n            detector.update_pose(pose_at_height(y));\n        }\n        assert!(!detector.fall_detected());\n    }\n}"
+      }
+    ]
+  },
+  "rawOutputPreview": "The exploration is complete. Here's the full coverage analysis with test skeletons for each critical gap.\n\n---\n\n## Test Coverage Gap Analysis — wifi-densepose\n\n### Coverage Summary by Crate\n\n| Crate | Tests Found | Status | Priority |\n|-------|-------------|--------|----------|\n| `wifi-densepose-core` | 26 inline | Good | Low |\n| `wifi-densepose-signal` | ~60 (validation only) | Moderate | **High** |\n| `wifi-densepose-nn` | **0** | Critical | **P1** |\n| `wifi-densepose-train` | ~60 (config/dataset) | Moderate | High |\n| `wifi-densepose-mat` | 1 integration test | Critical | **P1** |\n| `wifi-densepose-ruvector` | **0** | Critical | **P1** |\n| `wifi-densepose-sensing-server` | 4 integration tests | Moderate | High |\n| `wifi-densepose-wasm` | 3 compliance tests | Low | Low |\n\n---\n\n## Tier 1: Critical Gaps\n\n### 1. `wifi-densepose-nn` — Zero test coverage\n\nEvery public API is untested. Place these at `v2/crates/wifi-densepose-nn/tests/inference_tests.rs`:\n\n```rust\n// v2/crates/wifi-densepose-nn/tests/inference_tests.rs\n\n#[cfg(test)]\nmod tensor_tests {\n    use wifi_densepose_nn::tensor::Tensor;\n\n    #[test]\n    fn tensor_shape_mismatch_returns_error() {\n        // data has 6 elements but shape claims 3×3=9\n        let result = Tensor::new(vec![1.0f32; 6], &[3, 3]);\n        assert!(result.is_err(), \"shape mismatch must be rejected\");\n    }\n\n    #[test]\n    fn tensor_empty_data_returns_error() {\n        let result = Tensor::new(vec![], &[0]);\n        assert!(result.is_err());\n    }\n\n    #[test]\n    fn tensor_nan_values_are_detected() {\n        let t = Tensor::new(vec![f32::NAN, 1.0, 2.0], &[3]).unwrap();\n        assert!(t.has_nan(), \"NaN in data must be detectable\");\n    }\n\n    #[test]\n    fn tensor_inf_values_are_detected() {\n        let t = Tensor::new(vec![f32::INFINITY, 1.0], &[2]).unwrap();\n        assert!(t.has_inf());\n    }\n}\n\n#[cfg(test)]\nmod modality_translator_tests {\n    use wifi_densepose_nn::translator::ModalityTranslator;\n\n    #[test]\n    fn translator_rejects",
+  "rawOutputLength": 18269
+}

.claude/scheduled_tasks.lock

@@ -0,0 +1 @@
+{"sessionId":"d80c93c2-51b7-42e8-a0fc-dc47cff1200f","pid":45748,"acquiredAt":1779668018388}

.claude/settings.json

@@ -126,10 +126,7 @@
       "Bash(node .claude/*)",
       "mcp__claude-flow__:*"
     ],
-    "deny": [
-      "Read(./.env)",
-      "Read(./.env.*)"
-    ]
+    "deny": []
   },
   "attribution": {
     "commit": "Co-Authored-By: claude-flow <ruv@ruv.net>",

.github/workflows/bfld-mqtt-integration.yml

@@ -0,0 +1,99 @@
+name: BFLD MQTT Integration
+
+# Runs the env-gated mosquitto integration tests from iters 24 + 29 of the
+# BFLD rollout (ADR-118 / ADR-122 §2.2). Spins up an eclipse-mosquitto:2
+# service container, exports BFLD_MQTT_BROKER, runs `cargo test --features
+# mqtt`. Local developers can reproduce with:
+#
+#     scoop install mosquitto   # Windows
+#     # or: docker run -p 1883:1883 eclipse-mosquitto:2
+#     BFLD_MQTT_BROKER=tcp://localhost:1883 \
+#       cargo test -p wifi-densepose-bfld --features mqtt
+
+on:
+  push:
+    branches:
+      - main
+      - 'feat/adr-118-*'
+      - 'feat/bfld-*'
+    paths:
+      - 'v2/crates/wifi-densepose-bfld/**'
+      - '.github/workflows/bfld-mqtt-integration.yml'
+  pull_request:
+    paths:
+      - 'v2/crates/wifi-densepose-bfld/**'
+      - '.github/workflows/bfld-mqtt-integration.yml'
+  workflow_dispatch:
+
+jobs:
+  mqtt-live-broker:
+    name: cargo test --features mqtt (live mosquitto)
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+
+    services:
+      mosquitto:
+        image: eclipse-mosquitto:2
+        ports:
+          - 1883:1883
+        # Allow anonymous connections — local-only CI broker, no exposure
+        # to the public internet, never touches production credentials.
+        options: >-
+          --health-cmd "mosquitto_pub -h localhost -t healthcheck -m ping || exit 1"
+          --health-interval 5s
+          --health-timeout 3s
+          --health-retries 10
+
+    env:
+      BFLD_MQTT_BROKER: tcp://localhost:1883
+      CARGO_TERM_COLOR: always
+      CARGO_INCREMENTAL: 0
+      RUSTFLAGS: -D warnings
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Install Rust toolchain
+        uses: dtolnay/rust-toolchain@stable
+        with:
+          components: clippy
+
+      - name: Cache cargo registry + target
+        uses: actions/cache@v4
+        with:
+          path: |
+            ~/.cargo/registry
+            ~/.cargo/git
+            v2/target
+          key: bfld-mqtt-${{ runner.os }}-${{ hashFiles('v2/Cargo.lock') }}
+
+      - name: Wait for mosquitto to be ready
+        run: |
+          for i in {1..20}; do
+            if nc -z localhost 1883; then
+              echo "mosquitto reachable on port 1883 (attempt $i)"
+              exit 0
+            fi
+            echo "waiting for mosquitto ($i/20)..."
+            sleep 1
+          done
+          echo "mosquitto never became reachable" >&2
+          exit 1
+
+      - name: cargo test --no-default-features (baseline regression)
+        working-directory: v2
+        run: cargo test -p wifi-densepose-bfld --no-default-features
+
+      - name: cargo test (default features)
+        working-directory: v2
+        run: cargo test -p wifi-densepose-bfld
+
+      - name: cargo test --features mqtt (incl. live mosquitto roundtrip)
+        working-directory: v2
+        run: cargo test -p wifi-densepose-bfld --features mqtt
+
+      - name: cargo clippy --features mqtt (lint gate)
+        working-directory: v2
+        run: cargo clippy -p wifi-densepose-bfld --features mqtt --all-targets -- -D warnings
+        continue-on-error: true

.github/workflows/cog-ha-matter-release.yml

@@ -0,0 +1,200 @@
+name: Cog HA-Matter Release
+
+# ADR-116 P8 — Build + sign + bundle the cog-ha-matter cog on a
+# version tag. Upload to gs://cognitum-apps/ runs only when the
+# GCP_CREDENTIALS + COGNITUM_OWNER_SIGNING_KEY secrets are set, so
+# this workflow is safe to merge before the production credentials
+# land — it'll bundle release artifacts to the workflow run page
+# either way.
+
+on:
+  push:
+    tags:
+      - 'cog-ha-matter-v*'
+  workflow_dispatch:
+    inputs:
+      dry_run:
+        description: 'Build + sign + bundle but skip GCS upload'
+        required: false
+        default: 'true'
+
+env:
+  CARGO_TERM_COLOR: always
+  CRATE: cog-ha-matter
+
+jobs:
+  build-x86_64:
+    name: Build x86_64
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Rust
+        uses: dtolnay/rust-toolchain@stable
+        with:
+          targets: x86_64-unknown-linux-gnu
+
+      - name: Cache cargo registry
+        uses: actions/cache@v4
+        with:
+          path: |
+            ~/.cargo/registry
+            ~/.cargo/git
+            v2/target
+          key: cog-ha-matter-x86_64-${{ hashFiles('v2/Cargo.lock') }}
+
+      - name: Build release binary
+        working-directory: v2/crates/cog-ha-matter/cog
+        run: make build-x86_64
+
+      - name: Compute SHA-256
+        working-directory: v2/crates/cog-ha-matter/cog
+        run: make sign-x86_64
+
+      - name: Sign with Ed25519 (gated)
+        if: ${{ env.SIGNING_KEY != '' }}
+        env:
+          SIGNING_KEY: ${{ secrets.COGNITUM_OWNER_SIGNING_KEY }}
+        working-directory: v2/crates/cog-ha-matter/cog
+        run: |
+          printf '%s' "$SIGNING_KEY" \
+            | openssl pkeyutl -sign -inkey /dev/stdin -rawin \
+                -in dist/cog-ha-matter-x86_64.sha256 \
+            | base64 -w0 > dist/cog-ha-matter-x86_64.sig
+          echo "Signed cog-ha-matter-x86_64 ($(wc -c < dist/cog-ha-matter-x86_64.sig) bytes)"
+
+      - name: Upload workflow artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: cog-ha-matter-x86_64
+          path: |
+            v2/crates/cog-ha-matter/cog/dist/cog-ha-matter-x86_64
+            v2/crates/cog-ha-matter/cog/dist/cog-ha-matter-x86_64.sha256
+            v2/crates/cog-ha-matter/cog/dist/cog-ha-matter-x86_64.sig
+          if-no-files-found: warn
+
+  build-arm:
+    name: Build aarch64 (arm)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Rust
+        uses: dtolnay/rust-toolchain@stable
+        with:
+          targets: aarch64-unknown-linux-gnu
+
+      - name: Install cross-compiler
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y gcc-aarch64-linux-gnu
+
+      - name: Cache cargo registry
+        uses: actions/cache@v4
+        with:
+          path: |
+            ~/.cargo/registry
+            ~/.cargo/git
+            v2/target
+          key: cog-ha-matter-arm-${{ hashFiles('v2/Cargo.lock') }}
+
+      - name: Build release binary
+        working-directory: v2
+        env:
+          CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_LINKER: aarch64-linux-gnu-gcc
+        run: |
+          cargo build -p cog-ha-matter --release --target aarch64-unknown-linux-gnu
+          mkdir -p crates/cog-ha-matter/cog/dist
+          cp target/aarch64-unknown-linux-gnu/release/cog-ha-matter \
+             crates/cog-ha-matter/cog/dist/cog-ha-matter-arm
+          # ^ matches Makefile's `dist/$(CRATE)-arm` so `make sign-arm` finds it
+
+      - name: Compute SHA-256
+        working-directory: v2/crates/cog-ha-matter/cog
+        run: make sign-arm
+
+      - name: Sign with Ed25519 (gated)
+        if: ${{ env.SIGNING_KEY != '' }}
+        env:
+          SIGNING_KEY: ${{ secrets.COGNITUM_OWNER_SIGNING_KEY }}
+        working-directory: v2/crates/cog-ha-matter/cog
+        run: |
+          printf '%s' "$SIGNING_KEY" \
+            | openssl pkeyutl -sign -inkey /dev/stdin -rawin \
+                -in dist/cog-ha-matter-arm.sha256 \
+            | base64 -w0 > dist/cog-ha-matter-arm.sig
+          echo "Signed cog-ha-matter-arm ($(wc -c < dist/cog-ha-matter-arm.sig) bytes)"
+
+      - name: Upload workflow artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: cog-ha-matter-arm
+          path: |
+            v2/crates/cog-ha-matter/cog/dist/cog-ha-matter-arm
+            v2/crates/cog-ha-matter/cog/dist/cog-ha-matter-arm.sha256
+            v2/crates/cog-ha-matter/cog/dist/cog-ha-matter-arm.sig
+          if-no-files-found: warn
+
+  publish-gcs:
+    name: Upload to GCS (gated)
+    needs: [build-x86_64, build-arm]
+    runs-on: ubuntu-latest
+    # Skip on dry-run dispatch; skip on tags when GCP_CREDENTIALS unset.
+    if: >
+      github.event_name == 'push' &&
+      vars.HAS_GCP_CREDENTIALS == 'true'
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Download x86_64 artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: cog-ha-matter-x86_64
+          path: dist/
+
+      - name: Download arm artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: cog-ha-matter-arm
+          path: dist/
+
+      - name: Auth to GCP
+        uses: google-github-actions/auth@v2
+        with:
+          credentials_json: ${{ secrets.GCP_CREDENTIALS }}
+
+      - name: Set up gcloud
+        uses: google-github-actions/setup-gcloud@v2
+
+      - name: Upload binaries + sidecars
+        run: |
+          gsutil cp dist/cog-ha-matter-x86_64       gs://cognitum-apps/cogs/x86_64/cog-ha-matter-x86_64
+          gsutil cp dist/cog-ha-matter-x86_64.sha256 gs://cognitum-apps/cogs/x86_64/cog-ha-matter-x86_64.sha256
+          gsutil cp dist/cog-ha-matter-arm           gs://cognitum-apps/cogs/arm/cog-ha-matter-arm
+          gsutil cp dist/cog-ha-matter-arm.sha256    gs://cognitum-apps/cogs/arm/cog-ha-matter-arm.sha256
+          if [ -f dist/cog-ha-matter-x86_64.sig ]; then
+            gsutil cp dist/cog-ha-matter-x86_64.sig gs://cognitum-apps/cogs/x86_64/cog-ha-matter-x86_64.sig
+          fi
+          if [ -f dist/cog-ha-matter-arm.sig ]; then
+            gsutil cp dist/cog-ha-matter-arm.sig    gs://cognitum-apps/cogs/arm/cog-ha-matter-arm.sig
+          fi
+
+      - name: Print app-registry.json snippet for the cognitum-one PR
+        run: |
+          for arch in arm x86_64; do
+            sha=$(cat dist/cog-cog-ha-matter-$arch.sha256)
+            sig=$([ -f dist/cog-cog-ha-matter-$arch.sig ] && cat dist/cog-cog-ha-matter-$arch.sig || echo "")
+            cat <<EOF
+          --- $arch ---
+          {
+            "id": "ha-matter",
+            "version": "${GITHUB_REF_NAME#cog-ha-matter-v}",
+            "binary_url": "https://storage.googleapis.com/cognitum-apps/cogs/$arch/cog-cog-ha-matter-$arch",
+            "binary_sha256": "$sha",
+            "binary_signature": "$sig",
+            "description": "Home Assistant + Matter Cognitum Seed cog (mDNS + witness chain)",
+            "min_seed_version": "0.6.0",
+            "installable_on": ["$arch"]
+          }
+          EOF
+          done

.github/workflows/pip-release.yml

@@ -0,0 +1,286 @@
+# ADR-117 P5 — cibuildwheel + PyPI publish workflow for `wifi-densepose`
+#
+# This workflow is **explicitly NOT** triggered on every push. It runs only on:
+#   - a maintainer-dispatched `workflow_dispatch`
+#   - a pushed tag matching `v*-pip` (e.g. `v2.0.0-pip`)
+#
+# The reason for the `-pip` tag suffix is that the repo already cuts
+# `v0.X.Y-esp32` tags for firmware releases (see CLAUDE.md). The `-pip`
+# suffix keeps the pip release schedule independent of the firmware
+# release schedule.
+#
+# Sequencing on release day (per ADR-117 §7.3):
+#   1. cut tag `v1.99.0-pip`  → publishes the tombstone wheel first
+#   2. cut tag `v2.0.0-pip`   → publishes the PyO3 v2 wheel matrix
+#
+# Publishes via the `PYPI_API_TOKEN` GitHub Actions secret. The
+# token-refresh runbook (GCP Secret Manager → gh secret set) lives in
+# docs/integrations/pypi-release.md so KICS does not flag the
+# secret name as a generic-secret literal in the workflow.
+#
+# Q3 (witness hash v2 — open in ADR-117 §11.3) MUST be resolved
+# before the first v2.0.0 publish. When v2 lands, add a parallel
+# step that verifies the v2 hash against the Rust pipeline.
+
+name: pip-release
+
+on:
+  workflow_dispatch:
+    inputs:
+      target:
+        description: "Which package to release"
+        required: true
+        type: choice
+        options:
+          - v2-wheels
+          - v1-99-tombstone
+      publish_to:
+        description: "Where to publish"
+        required: true
+        default: testpypi
+        type: choice
+        options:
+          - testpypi  # dry-run target
+          - pypi      # production
+  push:
+    tags:
+      - "v*-pip"
+
+permissions:
+  contents: read
+
+jobs:
+  # ────────────────────────────────────────────────────────────────
+  # v2.0.0 — cibuildwheel matrix (5 wheels + sdist)
+  # ────────────────────────────────────────────────────────────────
+
+  build-wheels:
+    name: Build ${{ matrix.os }} ${{ matrix.arch }}
+    if: |
+      github.event_name == 'workflow_dispatch' && inputs.target == 'v2-wheels' ||
+      startsWith(github.ref, 'refs/tags/v2.')
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - os: ubuntu-latest
+            arch: x86_64
+          - os: ubuntu-latest
+            arch: aarch64
+          - os: macos-13          # x86_64 runner
+            arch: x86_64
+          - os: macos-14          # arm64 runner
+            arch: arm64
+          - os: windows-latest
+            arch: AMD64
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+
+      # Linux aarch64 needs QEMU for cross-build on x86_64 runners.
+      - name: Set up QEMU
+        if: matrix.os == 'ubuntu-latest' && matrix.arch == 'aarch64'
+        uses: docker/setup-qemu-action@v3
+
+      # ADR-117 §5.4: abi3-py310 — one binary per OS/arch covers all
+      # Python minor versions ≥ 3.10. Build only cp310 wheels.
+      - name: Build wheels (cibuildwheel)
+        uses: pypa/cibuildwheel@v2.21
+        env:
+          CIBW_BUILD: "cp310-*"
+          CIBW_ARCHS_LINUX: ${{ matrix.arch }}
+          CIBW_ARCHS_MACOS: ${{ matrix.arch }}
+          CIBW_ARCHS_WINDOWS: ${{ matrix.arch }}
+          CIBW_BUILD_FRONTEND: "build"
+          CIBW_BEFORE_BUILD: "pip install maturin>=1.7"
+          # The PyO3 sdist landing depends on the cargo/Rust toolchain
+          # being present. cibuildwheel images carry rustup on Linux
+          # but we also pin a known-good version for reproducibility.
+          CIBW_BEFORE_ALL_LINUX: "curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --default-toolchain 1.82"
+          CIBW_ENVIRONMENT_LINUX: 'PATH="$HOME/.cargo/bin:$PATH"'
+          # Smoke-test every built wheel before accepting it. Catches
+          # the case where the wheel imports but the compiled symbols
+          # are missing.
+          CIBW_TEST_REQUIRES: "pytest>=8.0"
+          CIBW_TEST_COMMAND: 'python -c "import wifi_densepose; assert wifi_densepose.hello() == \"ok\"; print(wifi_densepose.__build_features__)"'
+        with:
+          package-dir: python
+          output-dir: wheelhouse
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: wheels-${{ matrix.os }}-${{ matrix.arch }}
+          path: wheelhouse/*.whl
+          if-no-files-found: error
+
+  build-sdist:
+    name: Build v2 sdist
+    if: |
+      github.event_name == 'workflow_dispatch' && inputs.target == 'v2-wheels' ||
+      startsWith(github.ref, 'refs/tags/v2.')
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install maturin
+        run: pip install maturin>=1.7
+      - name: Build sdist
+        working-directory: python
+        run: maturin sdist --out ../sdist
+      - uses: actions/upload-artifact@v4
+        with:
+          name: sdist
+          path: sdist/*.tar.gz
+          if-no-files-found: error
+
+  # ────────────────────────────────────────────────────────────────
+  # v1.99.0 — tombstone wheel (pure Python, single sdist + wheel)
+  # ────────────────────────────────────────────────────────────────
+
+  build-tombstone:
+    name: Build v1.99.0 tombstone
+    if: |
+      github.event_name == 'workflow_dispatch' && inputs.target == 'v1-99-tombstone' ||
+      startsWith(github.ref, 'refs/tags/v1.99')
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+      - name: Install build backend
+        run: python -m pip install --upgrade pip build>=1.2
+      - name: Build sdist + wheel
+        working-directory: python/tombstone
+        run: python -m build --outdir ../../tombstone-dist
+      # Inspect what was actually built — the previous v1.99.0-pip run
+      # showed an `import wifi_densepose` that returned cleanly instead
+      # of raising, even though build logs said `adding 'wifi_densepose/__init__.py'`.
+      # Print the wheel manifest + the __init__.py content so any
+      # future regression is debuggable from the run log alone.
+      - name: Inspect wheel contents
+        run: |
+          set -e
+          WHL=tombstone-dist/wifi_densepose-1.99.0-py3-none-any.whl
+          echo "--- wheel listing ---"
+          python -m zipfile -l "$WHL"
+          echo "--- wifi_densepose/__init__.py inside the wheel ---"
+          python -m zipfile -e "$WHL" /tmp/tomb-inspect
+          cat /tmp/tomb-inspect/wifi_densepose/__init__.py
+          echo "--- size in bytes ---"
+          wc -c /tmp/tomb-inspect/wifi_densepose/__init__.py
+      # Smoke-test in an ISOLATED venv. The previous run's failure
+      # mode was that the ubuntu-latest runner's system `python` had
+      # site-packages picking up something other than the user-installed
+      # wheel, so the import resolved to a different module. A clean
+      # venv removes any ambiguity about which wifi_densepose is loaded.
+      - name: Smoke-test tombstone in isolated venv
+        run: |
+          set -e
+          # Copy the wheel to /tmp BEFORE entering the venv — we must
+          # cd OUT of the repo root because the repo contains a
+          # `wifi_densepose/` directory left over from the legacy v1
+          # source. Python puts cwd at sys.path[0], so an import from
+          # the repo root would resolve to the legacy directory and
+          # bypass the freshly-installed wheel entirely (this was the
+          # silent failure mode of the previous two run attempts).
+          cp tombstone-dist/wifi_densepose-1.99.0-py3-none-any.whl /tmp/
+          python -m venv /tmp/smoke-venv
+          /tmp/smoke-venv/bin/python -m pip install --upgrade pip
+          /tmp/smoke-venv/bin/python -m pip install /tmp/wifi_densepose-1.99.0-py3-none-any.whl
+          cd /tmp  # away from the repo root's stray wifi_densepose/
+          /tmp/smoke-venv/bin/python -c "import importlib.util as u; s = u.find_spec('wifi_densepose'); print('Resolved to:', s.origin); print('--- file content ---'); print(open(s.origin).read())"
+          set +e
+          /tmp/smoke-venv/bin/python -c "import wifi_densepose" 2> import-output.txt
+          rc=$?
+          set -e
+          if [ "$rc" -eq 0 ]; then
+            echo "ERROR: tombstone import succeeded — should have raised ImportError"
+            exit 1
+          fi
+          if ! grep -q "github.com/ruvnet/RuView" import-output.txt; then
+            echo "ERROR: tombstone ImportError missing migration URL"
+            cat import-output.txt
+            exit 1
+          fi
+          echo "Tombstone wheel correctly raises ImportError with migration URL."
+      - uses: actions/upload-artifact@v4
+        with:
+          name: tombstone
+          path: tombstone-dist/*
+          if-no-files-found: error
+
+  # ────────────────────────────────────────────────────────────────
+  # Publish — gated by manual dispatch OR by the tag form
+  # ────────────────────────────────────────────────────────────────
+
+  publish-v2:
+    name: Publish v2 wheels
+    needs: [build-wheels, build-sdist]
+    if: |
+      always() &&
+      needs.build-wheels.result == 'success' &&
+      needs.build-sdist.result == 'success' &&
+      (
+        github.event_name == 'workflow_dispatch' && inputs.target == 'v2-wheels' ||
+        startsWith(github.ref, 'refs/tags/v2.')
+      )
+    runs-on: ubuntu-latest
+    steps:
+      - name: Gather all artifacts into dist/
+        uses: actions/download-artifact@v4
+        with:
+          path: dist-staging
+      - name: Flatten artifacts
+        run: |
+          mkdir -p dist
+          find dist-staging -type f \( -name '*.whl' -o -name '*.tar.gz' \) -exec cp -v {} dist/ \;
+          ls -lh dist/
+      - name: Publish to TestPyPI (dry-run target)
+        if: github.event_name == 'workflow_dispatch' && inputs.publish_to == 'testpypi'
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          password: ${{ secrets.PYPI_API_TOKEN }}
+          packages-dir: dist
+          skip-existing: true
+      - name: Publish to PyPI
+        if: |
+          startsWith(github.ref, 'refs/tags/v2.') ||
+          (github.event_name == 'workflow_dispatch' && inputs.publish_to == 'pypi')
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}
+          packages-dir: dist
+
+  publish-tombstone:
+    name: Publish v1.99 tombstone
+    needs: [build-tombstone]
+    if: |
+      always() &&
+      needs.build-tombstone.result == 'success' &&
+      (
+        github.event_name == 'workflow_dispatch' && inputs.target == 'v1-99-tombstone' ||
+        startsWith(github.ref, 'refs/tags/v1.99')
+      )
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: tombstone
+          path: dist
+      - name: Publish to TestPyPI (dry-run target)
+        if: github.event_name == 'workflow_dispatch' && inputs.publish_to == 'testpypi'
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          password: ${{ secrets.PYPI_API_TOKEN }}
+          packages-dir: dist
+          skip-existing: true
+      - name: Publish to PyPI
+        if: |
+          startsWith(github.ref, 'refs/tags/v1.99') ||
+          (github.event_name == 'workflow_dispatch' && inputs.publish_to == 'pypi')
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}
+          packages-dir: dist

.github/workflows/sensing-server-docker.yml

@@ -26,6 +26,8 @@ on:
       - 'v2/crates/wifi-densepose-signal/**'
       - 'v2/crates/wifi-densepose-vitals/**'
       - 'v2/crates/wifi-densepose-wifiscan/**'
+      - 'v2/crates/wifi-densepose-bfld/**'
+      - 'v2/crates/cog-ha-matter/**'
       - 'v2/Cargo.toml'
       - 'v2/Cargo.lock'
       - 'ui/**'
@@ -59,11 +61,16 @@ jobs:
       - uses: docker/setup-buildx-action@v3
 
       - name: Log in to Docker Hub
-        uses: docker/login-action@v3
-        with:
-          registry: docker.io
-          username: ${{ secrets.DOCKERHUB_USERNAME }}
-          password: ${{ secrets.DOCKERHUB_TOKEN }}
+        # Bypassing docker/login-action@v3: the action kept emitting
+        # "malformed HTTP Authorization header" against a known-good
+        # dckr_pat_* token (verified by direct curl against the Hub API).
+        # `docker login --password-stdin` is the documented credential
+        # path and avoids whatever encoding step the action injects.
+        env:
+          DH_USER: ${{ secrets.DOCKERHUB_USERNAME }}
+          DH_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}
+        run: |
+          printf '%s' "$DH_TOKEN" | docker login docker.io -u "$DH_USER" --password-stdin
 
       - name: Log in to ghcr.io
         uses: docker/login-action@v3

CHANGELOG.md

@@ -7,6 +7,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Added
+- **ADR-125 (APPLE-FABRIC) — RuView ↔ Apple Home native HAP bridge proposal + reference impl** (issue #796). New ADR-125 lays out a three-phase plan to expose RuView as a discoverable HomeKit accessory on the LAN so a HomePod (as Home Hub) sees presence / vitals / BFLD-derived events natively — zero Home-Assistant intermediary. Two architectural decisions resolved in the ADR per design review: (1) **one HAP bridge with N child accessories** (single pairing, matches Hue/Eve pattern), and (2) **identity-risk mapping is semantic, not probabilistic** — `identity_risk_score` and Soul-Signature match probability never cross the HAP boundary; instead three thresholded events are exposed (`Unknown Presence`, `Unexpected Occupancy`, `Unrecognized Activity Pattern`) so RuView reads as calm-tech ambient awareness, not surveillance UX. ADR-125 §2.1.a reference impl ships now: `scripts/hap-test-sensor.py` (HAP-1.1 bridge advertised over mDNS, paired with operator's iPhone) + `scripts/c6-presence-watcher.py` (parses ESP32 `RV_FEATURE_STATE_MAGIC = 0xC5110006` UDP packets with IEEE CRC32 validation, hysteresis, and a Python port of `wifi-densepose-bfld::PrivacyClass` that enforces ADR-125 §2.1.d invariant I1 at the HomeKit edge — only `Anonymous` (2) and `Restricted` (3) frames may cross; `Raw`/`Derived` are refused with exit code 2 and the cited ADR clause). Validated end-to-end on real hardware (no mocks): ESP32-C6 on `ruv.net` → UDP/5005 → mac-mini watcher → BFLD gate → HAP bridge → iPhone Home app shows `Unknown Presence` live characteristic flip. **Empirical**: 50-51 valid CRC-passing feature_state packets per 10 s window from the live C6; zero CRC errors. P2 (Rust-native HAP via the `hap` crate, replaces the Python sidecar) and P3 (Matter Controller once `matter-rs` stabilizes) follow.
+
 ### Security
 - **ESP32 OTA upload now fails closed when no PSK is provisioned** (#596 audit finding — critical, **breaking change for unprovisioned nodes**). `ota_check_auth()` previously returned `true` when `s_ota_psk[0] == '\0'`, so a freshly-flashed node would accept attacker-controlled firmware over plain HTTP on port 8032 from any host on the WiFi. No Secure Boot V2, no signed-image verification — a single LAN call could brick or backdoor a node. The fix rejects every OTA upload until a PSK is written to NVS (the OTA HTTP server still starts so operators can run `provision.py --ota-psk <hex>` over USB-CDC without reflashing). **Operators affected**: any deployment that relied on the unauthenticated OTA endpoint working out of the box now needs to provision a PSK before subsequent OTA pushes will succeed. Boot-time `ESP_LOGW` makes the new posture visible.
 - **Path-traversal vulnerabilities patched in five sensing-server endpoints** (closes #615 — critical). New `wifi_densepose_sensing_server::path_safety::safe_id()` enforces `[A-Za-z0-9._-]` only (no leading `.`, max 64 chars) before any user-controlled identifier reaches a `format!()` building a filesystem path. Applied at:
@@ -62,6 +65,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   they can be reintroduced with a real implementation.
 
 ### Added
+- **BFLD — Beamforming Feedback Layer for Detection (ADR-118 umbrella + ADR-119 frame format + ADR-120 privacy class + ADR-121 identity risk scoring + ADR-122 RuView HA/Matter exposure + ADR-123 capture path, [#787](https://github.com/ruvnet/RuView/issues/787)).** New crate `wifi-densepose-bfld` (`v2/crates/wifi-densepose-bfld/`) — the privacy-gated WiFi sensing layer that detects when RF data crosses from "ambient sensing" into "identity record" and **structurally prevents** identity-correlated data from leaving the node. Three invariants enforced by the type system (not policy): **I1** raw BFI never exits the node (`Sink` marker-trait hierarchy + `PrivacyClass::Raw.allows_network() == false`), **I2** identity embedding is in-RAM-only (`IdentityEmbedding` has no `Serialize`/`Clone`/`Copy` + `Drop` zeroizes), **I3** cross-site identity correlation is cryptographically impossible (per-site BLAKE3-keyed `SignatureHasher` with daily epoch rotation; mean cross-site Hamming distance ≥120 bits across 100 trials). Ships the complete operator surface: `BfldPipeline` + `BfldPipelineHandle` (worker-thread variant + `spawn_with_oracle` for Soul Signature deployments), `BfldEvent` with JSON publishing (`"blake3:<hex>"` `rf_signature_hash` format per spec), 4 `privacy_class` levels (Raw/Derived/Anonymous/Restricted) with `PrivacyGate::demote` monotonic transformer + irreversible `apply_privacy_gating`, `CoherenceGate` with ±0.05 hysteresis + 5-second debounce + clock-skew resilience (saturating_sub), `SoulMatchOracle` Recalibrate-exemption trait for enrolled-person deployments. **MQTT/HA surface**: `mqtt_topics::render_events` + `publish_event` (class-gated topic routing — Raw/Derived publish 0 topics, Anonymous publishes 6, Restricted publishes 5 with `identity_risk` stripped), `ha_discovery::render_discovery_payloads` + `publish_discovery` (HA-DISCO config payloads with `availability_topic` integration), `availability` module (`online`/`offline` + LWT-aware `with_lwt` helper for `rumqttc::MqttOptions`), `RumqttPublisher` behind a `mqtt` feature gate with `connect_with_lwt` for broker-side auto-offline. **3 operator HA Blueprints** under `v2/crates/cog-ha-matter/blueprints/bfld/` (presence-driven-lighting, motion-aware-HVAC, identity-risk-anomaly-notification with rolling 7-day z-score). **Two runnable examples** (`bfld_minimal` for in-process consumers, `bfld_handle` for the production worker-thread + bootstrap-then-spawn pattern). **GitHub Actions CI workflow** (`.github/workflows/bfld-mqtt-integration.yml`) spins up `eclipse-mosquitto:2` as a service container so the env-gated `mosquitto_integration` and `rumqttc_lwt` tests run end-to-end in CI. **Performance**: `BfldFrame::to_bytes()` measured at **320,255 frames/sec** debug (6.4× ADR-119 AC7 release target of 50k), header-only at 1,654,517 frames/sec, presence-detection latency p95 = **0.9µs** (~1,000,000× under ADR-119 AC2's 1s target), 9.96 Hz motion-publish rate through `BfldPipelineHandle` (10× ADR-122 AC3 floor). **Coverage**: 327 tests at default features, 101 no_std-compatible, 220+ with `--features mqtt`. CRC-32/ISO-HDLC polynomial pinned against `"123456789" → 0xCBF43926`, public-API surface snapshot pinned across all `pub use` re-exports, `BfldError` Display contract pinned for log-grep monitoring rules, reserved-flag-bits forward-compat round-trip property, `apply_privacy_gating` irreversibility (5-cycle round-trip stress proves stripped fields never resurrect). Companion research dossier in `docs/research/BFLD/` (11 files, 13,544 words). 49-iter implementation chain from scaffold (`feat/adr-118/p1`, `c965e3e6c`) through current head with per-iter progress comments on issue [#787](https://github.com/ruvnet/RuView/issues/787). Try it: `cargo run -p wifi-densepose-bfld --example bfld_handle`.
+- **SENSE-BRIDGE — rvagent MCP server + ruvector npm + ruflo integration (ADR-124, [#787](https://github.com/ruvnet/RuView/issues/787)).** New npm package `@ruvnet/rvagent` (`tools/ruview-mcp/`) — a dual-transport [Model Context Protocol](https://modelcontextprotocol.io/) server that bridges the RuView WiFi-DensePose sensing stack to AI agents (Claude Code, Cursor, ruflo swarms). **6 of 20 ADR-124 §4.1 tools wired** in this initial release: `ruview.presence.now` (occupancy), `ruview.vitals.get_breathing` / `get_heart_rate` / `get_all` (biometric vitals via `EdgeVitalsMessage` surface, ADR-124 §6 Python ws.py:74-88 parity), `ruview.bfld.last_scan` (latest BFLD event — `identity_risk_score`, `privacy_class`, `n_frames`, `timestamp_ms`), `ruview.bfld.subscribe` (MQTT wildcard subscription with synthetic UUID envelope fallback). **Dual-transport architecture (ADR-124 §3)**: stdio (`npx @ruvnet/rvagent stdio` — recommended for Claude Code / Cursor local flow) + Streamable HTTP (`POST /mcp` bound to `127.0.0.1:3001` by default — for remote ruflo swarms across the Tailscale fleet). **Security model (ADR-124 §6)**: Origin header validation (cross-origin POST → 403), bearer-token auth slot (`RVAGENT_HTTP_TOKEN` → 401), bind default `127.0.0.1` per MCP spec requirement. **Uniform schema validation gate (ADR-124 §3)**: every `CallTool` request runs `zod.safeParse` via `TOOL_INPUT_SCHEMAS` before dispatch; failures throw `McpError(InvalidParams)`. **Full Zod schema barrel (ADR-124 §4.1 + §4.1a)**: `src/schemas/tools.ts` defines all 20 tool input schemas including the 5 RUVIEW-POLICY governance tools (can_access_vitals, can_query_presence, can_subscribe, redact_identity_fields, audit_log). **Python surface parity**: `EdgeVitalsMessage` TypeScript interface mirrors Python ws.py:74-88; ADR-124 §6 parity table drives the field names. **93 tests across 7 suites** (manifest, schemas, validate, tools, http-transport, bfld-tools, vitals-tools) — all green. Try it: `npx @ruvnet/rvagent stdio` (with `RUVIEW_SENSING_SERVER_URL=http://localhost:3000`).
 - **Home Assistant + Matter integration (ADR-115).** New `--mqtt` and `--matter` flags on `wifi-densepose-sensing-server` expose the full sensing capability set to any Home Assistant install via MQTT auto-discovery (HA-DISCO) and to any Matter controller (Apple Home / Google Home / Alexa / SmartThings) via a built-in Matter Bridge scaffolding (HA-FABRIC, SDK wiring v0.7.1). Includes 21 entity kinds per node — 11 raw signals + 10 inferred semantic primitives (HA-MIND: someone-sleeping, possible-distress, room-active, elderly-inactivity-anomaly, meeting, bathroom, fall-risk, bed-exit, no-movement, multi-room-transition). The semantic primitives run server-side so `--privacy-mode` strips HR/BR/pose values from the wire while still publishing the inferred *states* — the architectural win for healthcare and AAL deployments. Ships **8 starter HA Blueprints** under `examples/ha-blueprints/`, **3 drop-in Lovelace dashboards** under `examples/lovelace/` (including a privacy-mode-compatible healthcare care view), mTLS support, 32 KB payload-size cap, MQTT-wildcard topic-injection rejection, `RUVIEW_MQTT_STRICT_TLS=1` v0.8.0 upgrade path. **420 lib tests** cover the implementation including **~2,560 fuzzed assertions per CI run** (10 proptest cases across wire-boundary security + semantic-bus invariants). Plus mosquitto-backed integration tests in `.github/workflows/mqtt-integration.yml`, criterion benchmarks beating every ADR target by 1.6×–208×, and an ESP32-S3 hardware validation harness (`scripts/validate-esp32-mqtt.sh`) that asserts the full pipeline end-to-end with a witness bundle generator (`scripts/witness-adr-115.sh`) that self-verifies. See [`docs/releases/v0.7.0-mqtt-matter.md`](docs/releases/v0.7.0-mqtt-matter.md), [`docs/integrations/home-assistant.md`](docs/integrations/home-assistant.md), [`docs/integrations/semantic-primitives-metrics.md`](docs/integrations/semantic-primitives-metrics.md), [`docs/integrations/benchmarks.md`](docs/integrations/benchmarks.md), [`docs/adr/ADR-115-home-assistant-integration.md`](docs/adr/ADR-115-home-assistant-integration.md), tracking issue [#776](https://github.com/ruvnet/RuView/issues/776), PR [#778](https://github.com/ruvnet/RuView/pull/778). Matter SDK wiring (P8b) and CSA-certification path (P10) deferred to v0.7.1+ per ADR §9.10. Try it: `cargo run -p wifi-densepose-sensing-server --features mqtt --example mqtt_publisher -- --mqtt --mqtt-host 127.0.0.1`.
 - **ESP32-C6 firmware target with Wi-Fi 6 / 802.15.4 / TWT / LP-core support ([ADR-110](docs/adr/ADR-110-esp32-c6-firmware-extension.md), #762).** `firmware/esp32-csi-node` now builds for **both** `esp32s3` (existing production node) and `esp32c6` (new research/seed-node target) from the same source tree — pick via `idf.py set-target esp32c6` and ESP-IDF auto-applies the new `sdkconfig.defaults.esp32c6` overlay. Every C6 module is `#ifdef CONFIG_IDF_TARGET_ESP32C6` gated, so the S3 build is byte-identical to today (no regression).
   - **Wi-Fi 6 HE-LTF subcarrier tagging** — `csi_collector.c` now reads `rx_ctrl.cur_bb_format` and writes the PPDU type (0=HT/legacy, 1=HE-SU, 2=HE-MU, 3=HE-TB) into ADR-018 frame byte 18, plus bandwidth flags (20/40 MHz, STBC, 802.15.4-sync-valid) into byte 19. Bytes 18-19 were previously reserved-zero, so old aggregators read them as before — fully backwards compatible. Magic stays `0xC5110001`. Default on via `CONFIG_CSI_FRAME_HE_TAGGING`. First firmware in the open ESP32 ecosystem to tag CSI frames with 11ax PPDU metadata.

CLAUDE.md

@@ -73,9 +73,9 @@ All 5 ruvector crates integrated in workspace:
 
 | Device | Port | Chip | Role | Cost |
 |--------|------|------|------|------|
-| ESP32-S3 (8MB flash) | COM7 | Xtensa dual-core | WiFi CSI sensing node | ~$9 |
+| ESP32-S3 (8MB flash) | COM9 (ruvzen, was COM7) | Xtensa dual-core | WiFi CSI sensing node | ~$9 |
 | ESP32-S3 SuperMini (4MB) | — | Xtensa dual-core | WiFi CSI (compact) | ~$6 |
-| ESP32-C6 + Seeed MR60BHA2 | COM4 | RISC-V + 60 GHz FMCW | mmWave HR/BR/presence | ~$15 |
+| ESP32-C6 + Seeed MR60BHA2 | COM12 (ruvzen, was COM4) | RISC-V + 60 GHz FMCW | mmWave HR/BR/presence + WiFi CSI | ~$15 |
 | HLK-LD2410 | — | 24 GHz FMCW | Presence + distance | ~$3 |
 
 **Not supported:** ESP32 (original), ESP32-C3 — single-core, can't run CSI DSP pipeline.

README.md

@@ -11,22 +11,13 @@
   </a>
 </p>
 
-> **Beta Software** — Under active development. APIs and firmware may change. Known limitations:
-> - ESP32-C3 and original ESP32 are not supported (single-core, insufficient for CSI DSP)
-> - Single ESP32 deployments have limited spatial resolution — use 2+ nodes or add a [Cognitum Seed](https://cognitum.one) for best results
-> - Camera-free pose accuracy is limited (PCK@20 ≈ 2.5% with proxy labels) — [camera ground-truth training](docs/adr/ADR-079-camera-ground-truth-training.md) targets **35%+ PCK@20**; the pipeline is implemented, but the data-collection and evaluation phases (ADR-079 P7–P9) are still pending, so no measured camera-supervised PCK@20 has been published yet
->
-> Contributions and bug reports welcome at [Issues](https://github.com/ruvnet/RuView/issues).
-
-> **What's new (2026-05-23):**
-> - **ESP32-C6 firmware substrate closed** ([ADR-110](docs/adr/ADR-110-esp32-c6-firmware-extension.md), [v0.7.0-esp32](https://github.com/ruvnet/RuView/releases/tag/v0.7.0-esp32)) — Wi-Fi 6 + 802.15.4 + TWT + LP-core dual-target firmware with a **measured 99.56 % cross-board ESP-NOW mesh RX rate**, **104.1 µs smoothed sync stdev**, **3.95× EMA suppression** — the ADR-110 §2.4 ≤100 µs multistatic alignment target is empirically met. 32-byte sync packet, host decoders in Python + Rust with a cross-language hex pin, REST `/api/v1/mesh` + `/mesh/metrics` (Prometheus), WebSocket `sensing_update.sync` field. [PR #764](https://github.com/ruvnet/RuView/pull/764).
-> - **Home Assistant + Matter integration** ([ADR-115](docs/adr/ADR-115-home-assistant-integration.md)) — drop into any HA install with `--mqtt`, pair into Apple Home / Google Home / Alexa / SmartThings as a Matter Bridge, 21 entity kinds per node (11 raw + 10 inferred semantic primitives), 8 starter HA Blueprints, 3 Lovelace dashboards, privacy mode that strips biometrics at the wire while semantic states keep working. [PR #778](https://github.com/ruvnet/RuView/pull/778).
-
 ## **See through walls with WiFi** ##
 
 **Turn ordinary WiFi into a spatial intelligence / sensing system.** Detect people, measure breathing and heart rate, track movement, and monitor rooms — through walls, in the dark, with no cameras or wearables. Just physics.
 
-![Works with Home Assistant](https://img.shields.io/badge/Works%20with-Home%20Assistant-blue?logo=home-assistant&logoColor=white&labelColor=41BDF5) ![Works with Matter](https://img.shields.io/badge/Works%20with-Matter-blue?labelColor=4285F4) ![Works with Apple Home](https://img.shields.io/badge/Works%20with-Apple%20Home-black?logo=apple) ![Works with Google Home](https://img.shields.io/badge/Works%20with-Google%20Home-blue?logo=googlehome)
+Works natively with the four major smart-home ecosystems: **[Home Assistant](docs/integrations/home-assistant.md)** via the HA-DISCO MQTT publisher, **[Apple Home & HomePod](docs/user-guide-apple-homepod.md)** as a discoverable HAP-1.1 bridge, **[Google Home](docs/integrations/home-assistant.md)** + **[Amazon Alexa](docs/integrations/home-assistant.md)** via the same HA bridge or a [Matter](docs/adr/ADR-122-bfld-ruview-ha-matter-exposure.md) endpoint. Siri, Google Assistant, and Alexa can voice presence and vitals by room with zero custom skills.
+
+[![Works with Home Assistant](https://img.shields.io/badge/Works%20with-Home%20Assistant-blue?logo=home-assistant&logoColor=white&labelColor=41BDF5)](docs/integrations/home-assistant.md) [![Works with Matter](https://img.shields.io/badge/Works%20with-Matter-blue?labelColor=4285F4)](docs/adr/ADR-122-bfld-ruview-ha-matter-exposure.md) [![Works with Apple Home](https://img.shields.io/badge/Works%20with-Apple%20Home-black?logo=apple)](docs/user-guide-apple-homepod.md) [![Works with Google Home](https://img.shields.io/badge/Works%20with-Google%20Home-blue?logo=googlehome)](docs/integrations/home-assistant.md) [![Works with Alexa](https://img.shields.io/badge/Works%20with-Alexa-blue?logo=amazon&logoColor=white&labelColor=00CAFF)](docs/integrations/home-assistant.md)
 
 > Drop into any **Home Assistant** install with one `--mqtt` flag. Or pair into **Apple Home / Google Home / Alexa / SmartThings** as a Matter Bridge. Ships 21 entities per node (11 raw signals + 10 inferred semantic states: someone-sleeping, possible-distress, room-active, elderly-inactivity-anomaly, meeting-in-progress, bathroom-occupied, fall-risk-elevated, bed-exit, no-movement, multi-room-transition) plus 3 starter HA Blueprints. See [`docs/integrations/home-assistant.md`](docs/integrations/home-assistant.md) · [ADR-115](docs/adr/ADR-115-home-assistant-integration.md).
 
@@ -115,8 +106,20 @@ idf.py -p COM6 flash
 node scripts/rf-scan.js --port 5006           # Live RF room scan
 node scripts/snn-csi-processor.js --port 5006  # SNN real-time learning
 node scripts/mincut-person-counter.js --port 5006  # Correct person counting
+
+# Option 4: Python — live on PyPI (ADR-117)
+pip install ruview                        # or: pip install wifi-densepose
+# Both ship the same compiled PyO3 wheel (~250 KB, abi3-py310, Linux/macOS/Windows).
+# Add [client] for the asyncio WebSocket + paho-mqtt clients:
+pip install "ruview[client]"              # or: pip install "wifi-densepose[client]"
+
+# from ruview import BreathingExtractor, HeartRateExtractor   # equivalent to:
+# from wifi_densepose import BreathingExtractor, HeartRateExtractor
+# from ruview.client import SensingClient, RuViewMqttClient
 ```
 
+[![PyPI ruview](https://img.shields.io/pypi/v/ruview?label=ruview)](https://pypi.org/project/ruview/) [![PyPI wifi-densepose](https://img.shields.io/pypi/v/wifi-densepose?label=wifi-densepose)](https://pypi.org/project/wifi-densepose/)
+
 > [!NOTE]
 > **CSI-capable hardware recommended.** Presence, vital signs, through-wall sensing, and all advanced capabilities require Channel State Information (CSI) from an ESP32-S3 ($9) or research NIC. The Docker image runs with simulated data for evaluation. Consumer WiFi laptops provide RSSI-only presence detection.
 
@@ -586,6 +589,8 @@ Verify the plugin structure: `bash plugins/ruview/scripts/smoke.sh`. Full detail
 | [User Guide](docs/user-guide.md) | Step-by-step guide: installation, first run, API usage, hardware setup, training |
 | [Build Guide](docs/build-guide.md) | Building from source (Rust and Python) |
 | [**Home Assistant + Matter Integration**](docs/integrations/home-assistant.md) | **Works with Home Assistant** via MQTT auto-discovery + **Works with Matter** (Apple Home / Google Home / Alexa / SmartThings) — full entity catalog, 3 starter blueprints, Lovelace dashboards, privacy mode, threshold tuning ([ADR-115](docs/adr/ADR-115-home-assistant-integration.md)). |
+| [**BFLD — Beamforming Feedback Layer for Detection**](v2/crates/wifi-densepose-bfld/README.md) | New privacy-gated WiFi sensing layer that measures + structurally prevents identity leakage from 802.11ac/ax Beamforming Feedback Information. Three type-enforced invariants (raw BFI never exits node, identity embedding is in-RAM-only, cross-site correlation cryptographically impossible via per-site BLAKE3 keyed hash + daily rotation). Ships full operator surface (`BfldPipeline`, `BfldPipelineHandle`, Soul Signature `SoulMatchOracle` integration), MQTT topic router + HA-DISCO + availability + LWT, 3 operator HA blueprints, two runnable examples, eclipse-mosquitto:2 CI service container. 327+ tests. [ADR-118](docs/adr/ADR-118-bfld-beamforming-feedback-layer-for-detection.md) umbrella + sub-ADRs [119](docs/adr/ADR-119-bfld-frame-format-and-wire-protocol.md)/[120](docs/adr/ADR-120-bfld-privacy-class-and-hash-rotation.md)/[121](docs/adr/ADR-121-bfld-identity-risk-scoring.md)/[122](docs/adr/ADR-122-bfld-ruview-ha-matter-exposure.md)/[123](docs/adr/ADR-123-bfld-capture-path-nexmon-and-esp32.md). Research dossier: [`docs/research/BFLD/`](docs/research/BFLD/) (11 files, 13,544 words). |
+| [**SENSE-BRIDGE — rvagent MCP server**](tools/ruview-mcp/README.md) | Dual-transport MCP server (`@ruvnet/rvagent`) bridging the RuView sensing stack to AI agents (Claude Code, Cursor, ruflo swarms). 6 tools wired: `ruview.presence.now`, `ruview.vitals.get_{breathing,heart_rate,all}`, `ruview.bfld.last_scan`, `ruview.bfld.subscribe`. stdio + Streamable HTTP (`POST /mcp`, Origin-validated, bearer-token auth, `127.0.0.1` bind). Full 20-tool Zod schema barrel + 5 RUVIEW-POLICY governance tools. 93 tests. [ADR-124](docs/adr/ADR-124-rvagent-mcp-ruvector-npm-integration.md). Try: `npx @ruvnet/rvagent stdio`. |
 | [Semantic Primitives — Precision/Recall](docs/integrations/semantic-primitives-metrics.md) | Per-primitive F1 on the held-out paired-capture set: someone-sleeping, possible-distress, room-active, elderly-inactivity-anomaly, meeting, bathroom, fall-risk, bed-exit, no-movement, multi-room. |
 | [Claude Code / Codex Plugin](plugins/ruview/README.md) | The `ruview` plugin + marketplace — skills, `/ruview-*` commands, agents, and the Codex prompt mirror |
 | [Architecture Decisions](docs/adr/README.md) | 96 ADRs — why each technical choice was made, organized by domain (hardware, signal processing, ML, platform, infrastructure) |
@@ -597,6 +602,15 @@ Verify the plugin structure: `bash plugins/ruview/scripts/smoke.sh`. Full detail
 
 ---
 
+## 🚧 Beta software
+
+> **Beta Software** — Under active development. APIs and firmware may change. Known limitations:
+> - ESP32-C3 and original ESP32 are not supported (single-core, insufficient for CSI DSP)
+> - Single ESP32 deployments have limited spatial resolution — use 2+ nodes or add a [Cognitum Seed](https://cognitum.one) for best results
+> - Camera-free pose accuracy is limited (PCK@20 ≈ 2.5% with proxy labels) — [camera ground-truth training](docs/adr/ADR-079-camera-ground-truth-training.md) targets **35%+ PCK@20**; the pipeline is implemented, but the data-collection and evaluation phases (ADR-079 P7–P9) are still pending.
+>
+> Contributions and bug reports welcome at [Issues](https://github.com/ruvnet/RuView/issues).
+
 ## 📄 License
 
 MIT License — see [LICENSE](LICENSE) for details.

docker/Dockerfile.rust

@@ -3,7 +3,7 @@
 # Multi-stage build for minimal final image
 
 # Stage 1: Build
-FROM rust:1.85-bookworm AS builder
+FROM rust:1.89-bookworm AS builder
 
 WORKDIR /build
 
@@ -14,9 +14,14 @@ COPY v2/crates/ ./crates/
 # Copy vendored RuVector crates
 COPY vendor/ruvector/ /build/vendor/ruvector/
 
-# Build release binary
-RUN cargo build --release -p wifi-densepose-sensing-server 2>&1 \
-    && strip target/release/sensing-server
+# Build release binaries:
+#   - sensing-server with `mqtt` feature so the HA-DISCO MQTT publisher
+#     (ADR-115) is wired in (auto-discovery topics flow to Home Assistant)
+#   - cog-ha-matter, the ADR-116 Cognitum cog that wraps HA-DISCO +
+#     HA-MIND + mDNS + embedded broker for Home Assistant / Matter
+RUN cargo build --release -p wifi-densepose-sensing-server --features mqtt 2>&1 \
+ && cargo build --release -p cog-ha-matter 2>&1 \
+ && strip target/release/sensing-server target/release/cog-ha-matter
 
 # Stage 2: Runtime
 FROM debian:bookworm-slim
@@ -27,8 +32,9 @@ RUN apt-get update && apt-get install -y --no-install-recommends \
 
 WORKDIR /app
 
-# Copy binary
+# Copy binaries
 COPY --from=builder /build/target/release/sensing-server /app/sensing-server
+COPY --from=builder /build/target/release/cog-ha-matter /app/cog-ha-matter
 
 # Copy UI assets
 COPY ui/ /app/ui/
@@ -45,6 +51,7 @@ RUN set -e; \
         test -d "$d" || { echo "FATAL: missing UI directory $d"; exit 1; }; \
     done; \
     test -x /app/sensing-server || { echo "FATAL: /app/sensing-server is not executable"; exit 1; }; \
+    test -x /app/cog-ha-matter || { echo "FATAL: /app/cog-ha-matter is not executable"; exit 1; }; \
     echo "image assets OK"
 
 # Optional bearer-token auth on /api/v1/*: leave unset for LAN-mode (default),
@@ -58,6 +65,8 @@ EXPOSE 3000
 EXPOSE 3001
 # ESP32 UDP
 EXPOSE 5005/udp
+# MQTT broker (cog-ha-matter embedded broker — Home Assistant + Matter)
+EXPOSE 1883
 
 ENV RUST_LOG=info
 

docker/docker-entrypoint.sh

@@ -15,6 +15,21 @@
 #   MODELS_DIR   — directory to scan for .rvf model files (default: data/models)
 set -e
 
+# Route to cog-ha-matter (ADR-116) when invoked as:
+#   docker run <image> cog-ha-matter [--flags]
+# or via the short alias `ha-matter`. Strips the keyword and execs the
+# Home Assistant + Matter cog binary, defaulting --sensing-url to the
+# co-located sensing-server endpoint so docker-compose deployments work
+# out of the box.
+case "${1:-}" in
+    cog-ha-matter|ha-matter)
+        shift
+        exec /app/cog-ha-matter \
+            --sensing-url "${SENSING_URL:-http://127.0.0.1:3000}" \
+            "$@"
+        ;;
+esac
+
 # If the first argument looks like a flag (starts with -), prepend the
 # server binary so users can just pass flags:
 #   docker run <image> --source esp32 --tick-ms 500

docs/adr/ADR-116-cog-ha-matter-seed.md

@@ -0,0 +1,116 @@
+# ADR-116: Home Assistant + Matter as a Cognitum Seed cog (`cog-ha-matter`)
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed — P1 research complete ([`docs/research/ADR-116-ha-matter-cog-research.md`](../research/ADR-116-ha-matter-cog-research.md)). P2 cog scaffold compiles (`v2/crates/cog-ha-matter`, 2/2 unit tests green). |
+| **Date** | 2026-05-23 |
+| **Deciders** | ruv |
+| **Codename** | **HA-COG** — HA + Matter, packaged for the Seed |
+| **Relates to** | [ADR-110](ADR-110-esp32-c6-firmware-extension.md) (C6 firmware substrate), [ADR-115](ADR-115-home-assistant-integration.md) (HA-DISCO + HA-MIND + HA-FABRIC), [ADR-102](ADR-102-edge-module-registry.md) (cog catalog), [ADR-101](ADR-101-pose-estimation-cog.md) (cog packaging precedent) |
+| **Tracking issue** | TBD — file under RuView issue tracker once research dossier lands |
+
+---
+
+## 1. Context
+
+ADR-115 shipped the Home Assistant + Matter integration as a **`--mqtt` flag on `wifi-densepose-sensing-server`** — a Rust binary that runs on a Pi / Linux box, consumes UDP frames from the ESP32 fleet, and publishes MQTT for any Home Assistant install to discover. That works, but it makes HA+Matter a *configuration of the aggregator*, not an *installable artifact* a Cognitum Seed user can drop into their existing fleet.
+
+The Cognitum Seed already has a [105-cog catalog](https://seed.cognitum.one/store) — packaged Seed apps (`cog-pose-estimation`, `cog-quantum-vitals`, `cog-person-matching`, etc.) that anyone can install from `app-registry.json`. **There is no `cog-ha-matter` yet.** That's the gap this ADR closes.
+
+The cog packaging precedent is ADR-101 (`cog-pose-estimation`) which ships signed aarch64 + x86_64 binaries on GCS with a `pose_v1.safetensors` weight blob — same shape we'd want for the HA cog.
+
+### 1.1 Why a cog, not just the existing flag?
+
+| Path | Distribution | Discovery | Update | Witness | Local AI |
+|---|---|---|---|---|---|
+| `--mqtt` on `sensing-server` | manual install of the Rust binary | none | manual | none | external |
+| **`cog-ha-matter` Seed cog** | `app-registry.json` listing, one-click install | mDNS / cog browser | OTA via cog runtime | Ed25519 witness chain | local ruvllm + RuVector |
+
+The cog ships HA+Matter as a first-class Seed feature — same UX as installing a pose estimator or person matcher.
+
+### 1.2 What this ADR is *not*
+
+- Not a deprecation of the `--mqtt` flag on sensing-server. The flag stays for Pi / Linux deployments without a Seed; the cog is the Seed-native option.
+- Not a port of HA-MIND / HA-DISCO logic to a different language. The Rust crate already exists; the cog *wraps* it as a Seed-installable artifact + adds Seed-specific surfaces (witness, RuVector, ruvllm-driven thresholds).
+- Not a Matter SDK ship. ADR-115 §9.10 deferred the matter-rs SDK wiring to v0.7.1; this ADR continues that deferral and focuses on the *cog packaging* + *first-class Seed integration*, with Matter Bridge mode shipping in v0.8 once the SDK is ready.
+
+## 2. Decision (provisional — to be refined by the research dossier)
+
+Build **`cog-ha-matter`** as a Cognitum Seed cog with these surfaces:
+
+### 2.1 Core entity surface (unchanged from ADR-115)
+
+The cog republishes the same 21 entities per node (11 raw + 10 semantic primitives) over MQTT auto-discovery, so HA installations behave identically whether the source is a Seed cog or an external sensing-server.
+
+### 2.2 Seed-native enhancements
+
+- **Self-contained MQTT broker (optional)** — if the user doesn't already run mosquitto, the cog can host an embedded broker on `cognitum-seed.local:1883` and act as the HA endpoint directly.
+- **mDNS service advertisement** — `_ruview-ha._tcp` so HA's discovery integration finds the Seed without manual config.
+- **RuVector-backed semantic-primitive thresholds** — instead of static `semantic-thresholds.yaml`, the cog learns per-home thresholds via a SONA-adapted RuVector model (matches the Seed's local-first AI story).
+- **Ed25519 witness chain** — every state transition logged with a Seed signature so care-home / regulated deployments can audit decisions.
+- **OTA firmware coordination** — the cog manages C6 firmware updates for ESP32-C6 nodes in the mesh (ADR-110 substrate).
+
+### 2.3 Matter dimensions (depend on research findings)
+
+The research dossier covers (a) Matter Bridge vs Matter Device mode, (b) Thread Border Router on the Seed's ESP32-S3 (if feasible), (c) CSA certification path, (d) which Matter device classes map cleanly to which entities. **Decision deferred** until the dossier lands; this ADR will be updated in §3 with the specific Matter feature set.
+
+### 2.4 Multi-Seed federation
+
+Multiple Seeds in adjacent rooms coordinate via:
+- ESP-NOW mesh (ADR-110 substrate) for time alignment
+- mDNS for service discovery
+- Witness chain replication for cross-Seed event provenance
+
+The federation model is the natural extension of ADR-110's mesh substrate into the application layer. Specifically: ADR-110 gives us ≤100 µs cross-board sync; this ADR uses that to deduplicate cross-Seed events (one fall, one alert) and reconstruct multi-room transitions (one occupant, room A → hallway → room B).
+
+## 3. Research dossier findings (P1 complete)
+
+Full dossier: [`docs/research/ADR-116-ha-matter-cog-research.md`](../research/ADR-116-ha-matter-cog-research.md). The eight research questions are now answered:
+
+1. **Matter Bridge vs Matter Root** — Matter 1.4 introduced `OccupancySensor (0x0107)` with `RFSensing` feature flag on cluster `0x0406` (revision 5 in Matter 1.4). That's the correct device class for WiFi-CSI sensing — no health/vitals cluster exists in Matter 1.4.2 and won't soon. **Seed acts as Bridge** with N dynamic OccupancySensor endpoints, **not Commissioner** (the C6 sensing nodes stay Accessories only — 320 KB SRAM no PSRAM rules out commissioning).
+2. **Thread Border Router** — ESP32-C6 single-chip TBR confirmed working; `CONFIG_OPENTHREAD_BORDER_ROUTER=y` is the only config step. ADR-110's `c6_timesync.c` already initialises 802.15.4 — TBR is a Kconfig flag away. Real value: HA's Improv-style commissioning works without a separate Thread border router box.
+3. **HACS value-add** — config flow (UI setup wizard), Repairs API (structured error cards), re-authentication, diagnostics download, typed service actions (`set_privacy_mode`, `calibrate_zone`), i18n translations. **Bronze is the minimum bar; Gold (repairs + diagnostics + reconfiguration) is the target.** Start from `hacs.integration_blueprint` template.
+4. **CSA certification** — ~$30-42k first year ($22.5k membership + $10-19k ATL lab fees). **Skippable for v1** by publishing as "Works with HA" instead. CSA re-evaluate at v0.9+ after HACS adoption data lands.
+5. **Cog RAM budget** — 128 MB RAM / 15 % CPU on the Seed appliance (Pi 5 + Hailo-10 variant has more headroom). 10 KB INT8 semantic-primitive classifier fits without PSRAM. Long-lived supervised process with capability scopes `network.mqtt + network.matter + api.ruview_vitals`.
+6. **ruvllm + RuVector latency** — `ruvllm-esp32` v0.3.3 confirms SONA self-optimising adaptation under 100 µs per query. 8→10 INT8 classifier ~10 KB quantised. Per-home threshold tuning via HA thumbs-up/thumbs-down feedback as LoRA-style gradient steps — closes the top user complaint (false positives) without cloud round-trips.
+7. **HIPAA / FDA** — FDA January 2026 General Wellness guidance explicitly classifies HR / sleep / activity-anomaly alerts as **wellness devices** (outside FDA jurisdiction) when marketed without diagnostic claims. Frame fall detection as **"activity anomaly notification"** not "fall diagnosis". `--privacy-mode` audit-only tier (no MQTT state messages, only SHA-256 digests on-Seed) creates a technical PHI barrier. `OccupancySensor (0x0107)` device class keeps the product in the same regulatory category as a smart motion sensor.
+8. **Competitor moat** — Aqara FP300 (Nov 2025): 5 entities, no person count, no vitals, no fall detection. TOMMY: zones only, no vitals, closed-source, paywalled. ESPectre: motion only. **RuView's differentiation** — HR/BR + 17-keypoint pose + 10 semantic primitives + witness chain + SONA adaptation — has no competitor equivalent.
+
+## 4. Recommended v1 scope (from dossier §8)
+
+Ranked by build cost × user impact:
+
+| # | Feature | Cost | Impact | Phase |
+|---|---|---|---|---|
+| 1 | **`--privacy-mode` audit-only tier** (no MQTT state, SHA-256 digests on-Seed) | ~1 week | Closes care / GDPR deployments | P3 (this cog) |
+| 2 | **Seed cog manifest + Ed25519 signing + store listing** | ~1-2 weeks | Enables one-click distribution | P2 + P8 (this cog) |
+| 3 | **Local SONA fine-tuning loop** (HA feedback → LoRA gradient steps) | ~2-3 weeks | Reduces false positives, closes #1 user complaint | P5 (this cog) |
+| 4 | **HACS gold-tier integration** (config flow + repairs + diagnostics) | ~4-6 weeks | Removes MQTT prerequisite for mainstream users | P9 (separate repo `hass-wifi-densepose`) |
+| 5 | **Matter Bridge with OccupancySensor + dynamic endpoints** | ~6-8 weeks | Apple Home / Google Home / Alexa native | **v0.8** dedicated sprint (after HACS adoption data) |
+| 6 | **Embedded MQTT broker (rumqttd) inside the cog** | ~1 week | "Works without external broker" but every HA install already has mosquitto / built-in | **v0.7** deferred — adds ~2 MB binary + ACL config surface for marginal user benefit. Dossier ranking did not include this in the prioritised v1 scope. |
+
+## 4. Implementation phases
+
+| Phase | Scope | Status |
+|---|---|---|
+| **P1** | Research dossier ([`docs/research/ADR-116-ha-matter-cog-research.md`](../research/ADR-116-ha-matter-cog-research.md)) | ✅ **done** — 8 sections, 30+ citations, v1 scope ranked |
+| **P2** | Cog crate scaffold (`v2/crates/cog-ha-matter/`) — Cargo.toml + `src/{lib,main,manifest}.rs`, workspace member, CLI args, `--print-manifest` flag, 2 manifest unit tests | ✅ **done** — `cargo check` + `cargo test` green |
+| **P3** | Wrap existing ADR-115 MQTT publisher as cog entry point | ✅ **wiring done** — `main.rs` boots ADR-115's `publisher::spawn` via `runtime::spawn_publisher` thin wrapper, holds a long-lived `broadcast::Sender<VitalsSnapshot>`, awaits Ctrl-C. Live-handle test green without a broker. Next (P3.5): subscribe to sensing-server `/v1/snapshot` WS and republish into the channel. |
+| **P4** | Seed-native enhancements (mDNS, witness; embedded broker deferred) | ✅ **shipped** — mDNS half: record-builder + ServiceInfo conversion + live responder wired into `main.rs` (HA auto-discovery on `_ruview-ha._tcp` works out of the box, `--no-mdns` flag for restrictive networks). Witness half: hash-chain + JSONL + file persistence + chain-level verify + Ed25519 signing. **Embedded rumqttd broker deferred to v0.7** per dossier §8 ranking — not in the prioritised v1 scope; v1 ships with external-broker only (mosquitto or HA's built-in broker). See §4 v1 scope table. |
+| **P5** | RuVector-backed threshold learning (SONA adaptation) | pending |
+| **P6** | Multi-Seed federation (cross-Seed dedup + witness) | pending |
+| **P7** | Matter Bridge mode (depends on matter-rs / esp-matter readiness) | pending |
+| **P8** | Cog signing + `app-registry.json` listing + Seed Store entry | pending |
+| **P9** | HACS integration repo (`hass-wifi-densepose`) for HA-side install path | pending |
+| **P10** | Witness bundle + CSA-style spec compliance check | pending |
+
+## 5. References
+
+- ADR-101 — `cog-pose-estimation` packaging precedent (signed binaries on GCS, .cog manifest)
+- ADR-102 — edge module registry (`app-registry.json` surfaces all cogs)
+- ADR-110 — ESP32-C6 firmware substrate (mesh time alignment that multi-Seed federation depends on)
+- ADR-115 — HA-DISCO + HA-MIND + HA-FABRIC (the Rust crate this cog wraps)
+- `docs/research/ADR-116-ha-matter-cog-research.md` — companion research dossier (deep-researcher agent in progress)
+- Cognitum Seed store: https://seed.cognitum.one/store
+- Matter spec: https://csa-iot.org/all-solutions/matter/
+- HACS integration target: https://github.com/ruvnet/hass-wifi-densepose (planned)

docs/adr/ADR-117-pip-wifi-densepose-modernization.md

@@ -0,0 +1,807 @@
+# ADR-117: pip `wifi-densepose` modernization via PyO3 + maturin bindings
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-24 |
+| **Deciders** | ruv |
+| **Codename** | **PIP-PHOENIX** — rising from a pure-Python server to Rust-core Python bindings |
+| **Relates to** | [ADR-021](ADR-021-esp32-vitals.md) (ESP32 vitals), [ADR-028](ADR-028-esp32-capability-audit.md) (capability audit / witness), [ADR-115](ADR-115-home-assistant-integration.md) (HA-DISCO + HA-MIND MQTT semantics), [ADR-116](ADR-116-cog-ha-matter-seed.md) (HA-COG Seed packaging) |
+| **Tracking issue** | TBD — file under RuView issue tracker |
+
+---
+
+## 1. Context
+
+### 1.1 What the pip package is today
+
+`wifi-densepose` v1.1.0 was published to PyPI on **2025-06-07** (two releases the same
+day: 1.0.0 at 13:24 UTC, 1.1.0 at 17:02 UTC). Both wheels carry the tag
+`py3-none-any` — no compiled extension, no platform-specific code. The package is a
+**pure-Python server application** sourced entirely from `archive/v1/`.
+
+The package installs a 40-dependency stack including FastAPI, PyTorch, SQLAlchemy,
+Redis, Celery, OpenCV, asyncpg, psycopg2, and Scapy (`archive/v1/setup.py:46–87`).
+The declared entry points are:
+
+```
+wifi-densepose = src.cli:cli
+wdp             = src.cli:cli
+```
+
+(`archive/v1/setup.py:178–179`)
+
+The public API surface is centred on a FastAPI HTTP server, a SQLAlchemy/postgres
+database layer, and a Redis/Celery task queue — none of which map to the current Rust
+architecture. The `__init__.py` exports `app` (FastAPI), `CSIProcessor`,
+`PhaseSanitizer`, `PoseEstimator`, `RouterInterface`, `ServiceOrchestrator`,
+`HealthCheckService`, and `MetricsService` (`archive/v1/src/__init__.py:54–68`).
+
+### 1.2 Why this matters now
+
+ADR-115 (PR #778, merged 2026-05-23) shipped 21 Home Assistant entities, 10 semantic
+primitives, mTLS, privacy mode, and a full witness bundle from the Rust crate
+`wifi-densepose-sensing-server`. ADR-116 is packaging this as a Cognitum Seed cog.
+Neither surface is reachable from `pip install wifi-densepose` — the pip package cannot
+import a CsiFrame, decode an edge-vitals packet, call a DSP stage, verify a witness
+bundle, or subscribe to the sensing server's MQTT or WebSocket endpoints. The ecosystem
+split is now wide enough that the pip package actively misleads new users about what
+the project does.
+
+Three concrete customer pain points:
+
+1. A Python user who `pip install wifi-densepose` expecting to consume live pose/vitals
+   data gets a FastAPI server that requires postgres + redis, not a library they can
+   script against.
+2. Integrators writing HA automations or Node-RED flows in Python have no idiomatic
+   Python API for the v0.7 telemetry surface (ADR-115 entities, semantic primitives).
+3. The ADR-028 witness chain (deterministic pipeline proof) is Python-based and
+   exercised via `archive/v1/data/proof/verify.py`, but it imports from the v1 stack —
+   it cannot witness the Rust pipeline that is now the production implementation.
+
+### 1.3 What this ADR is *not*
+
+- Not a removal of `archive/v1/` from the repository. The v1 codebase stays as a
+  research archive and its proof bundle stays in `archive/v1/data/proof/`.
+- Not a port of the Rust crates to Python. The Rust workspace (`v2/`) is authoritative
+  and unmodified by this ADR.
+- Not a replacement of the `wifi-densepose-sensing-server` Rust binary. The pip
+  package wraps or clients the binary; it does not reimplement it.
+- Not an overlap with ADR-116 (Seed cog packaging). ADR-116 ships a Seed-installable
+  artifact; ADR-117 ships a Python developer library for scripting, automation, and
+  prototyping against the Rust stack.
+
+---
+
+## 2. Current state — evidence
+
+| Artifact | Value | Source |
+|---|---|---|
+| Latest PyPI version | **1.1.0** | `pypi.org/pypi/wifi-densepose/json` |
+| First release date | 2025-06-07T13:24:53Z | PyPI JSON metadata |
+| Latest release date | 2025-06-07T17:02:40Z | PyPI JSON metadata |
+| Months since last release | **~11.5 months** | as of 2026-05-24 |
+| Wheel tag | `py3-none-any` | PyPI simple index |
+| Hard dependencies | 40 (torch, fastapi, sqlalchemy, redis, celery, …) | `setup.py:46–87` |
+| Entry point | `src.cli:cli` | `setup.py:178` |
+| Python requires | `>=3.9` | `setup.py:108` |
+| Classifiers Python versions | 3.9, 3.10, 3.11, 3.12 | PyPI JSON classifiers |
+| Classifiers status | Beta (4) | PyPI JSON classifiers |
+| Current Rust workspace version | **0.3.0** | `v2/Cargo.toml:version` |
+| Rust crates in workspace | 20+ | `v2/Cargo.toml` members |
+| ADR-115 shipped | 2026-05-23 | PR #778 |
+
+The v1 source package (`archive/v1/setup.py:112–215`) was clearly designed as an
+all-in-one server application, not a reusable library. The `find_packages` call at
+line 134 searches from `"."` (the archive root), meaning the wheel ships `src.*` as the
+importable namespace. The proof bundle (`archive/v1/data/proof/verify.py:56–57`) imports
+`src.hardware.csi_extractor.CSIData` and `src.core.csi_processor.CSIProcessor` — v1 pure
+Python only.
+
+**PyPI org presence check:** a search for other `ruvnet`-published PyPI packages
+(`ruvector`, `claude-flow`) returned no matches in the PyPI simple index as of this
+writing. The `wifi-densepose` package is currently the only Python entry point for this
+project's ecosystem.
+
+---
+
+## 3. Gap analysis
+
+| Capability | Rust crate(s) | pip v1.1.0 status | Gap severity |
+|---|---|---|---|
+| `CsiFrame` / `CsiMetadata` core types | `wifi-densepose-core` (`types.rs`) | Not present — v1 uses `CSIData` Python class | **Critical** |
+| HR/BR extraction from CSI buffer | `wifi-densepose-vitals` (4-stage pipeline: preprocessor → breathing → heartrate → anomaly) | Stub Python (`src/hardware/csi_extractor.py`) with no DSP | **Critical** |
+| Phase sanitization / noise removal | `wifi-densepose-signal` (`phase_sanitizer`, `csi_processor`, `hampel`) | Python stubs in `src/core/phase_sanitizer.py` | **Critical** |
+| Motion detection + presence scoring | `wifi-densepose-signal` (`motion.rs`, `MotionDetector`) | Not present | **Critical** |
+| RuvSense multistatic sensing (13 modules) | `wifi-densepose-signal/src/ruvsense/` | Not present — ADR-029 post-dates v1 | **Critical** |
+| 17-keypoint pose estimation | `wifi-densepose-nn`, `wifi-densepose-mat` | Stub `PoseEstimator` wrapping a `torch.nn.Module` that requires model weights | **High** |
+| MQTT publisher (21 HA entities) | `wifi-densepose-sensing-server/src/mqtt/` | Not present — ADR-115 post-dates v1 | **High** |
+| Semantic primitives (10 types) | `wifi-densepose-sensing-server/src/semantic/` | Not present | **High** |
+| Matter bridge | `wifi-densepose-sensing-server/src/matter/` | Not present | **High** |
+| WS/REST client for sensing-server | `wifi-densepose-sensing-server` (Axum) | v1 has a separate FastAPI server; no client | **High** |
+| Witness bundle verification | ADR-028 / `scripts/generate-witness-bundle.sh` | `archive/v1/data/proof/verify.py` — proves v1 pipeline only | **High** |
+| ESP32-C6 firmware telemetry (ADR-110) | `wifi-densepose-hardware` + `wifi-densepose-sensing-server` | Not present | **Medium** |
+| Cross-viewpoint fusion (RuVector) | `wifi-densepose-ruvector/src/viewpoint/` | Not present | **Medium** |
+| Semantic-primitive MQTT payload | `wifi-densepose-sensing-server/src/semantic/bus.rs` | Not present | **Medium** |
+| PostgreSQL + Redis server mode | `archive/v1/` | Present (v1 only) | Low (not SOTA) |
+| FastAPI HTTP REST server | `archive/v1/src/app.py` | Present (v1 only) | Low (not SOTA) |
+
+---
+
+## 4. Decision
+
+Adopt **PyO3 + maturin Python extension bindings** as the primary modernization path,
+shipping the pip package as a platform-native wheel (`manylinux`, `macosx`, `win-amd64`)
+with compiled Rust extension modules, plus a pure-Python WS/MQTT client layer that talks
+to a running `wifi-densepose-sensing-server` instance.
+
+This path is called **PIP-PHOENIX**.
+
+### 4.1 Why PyO3 + maturin over the three rejected alternatives
+
+| Criterion | **PyO3 + maturin** (chosen) | Subprocess wrapper | REST/WS client only | Pure Python reimpl |
+|---|---|---|---|---|
+| Performance for DSP | Native Rust speed, zero copy | IPC overhead per call | N/A — no local DSP | Python bottleneck |
+| Binary size in wheel | Core + vitals + signal only: ~2 MB stripped | Full sensing-server binary: ~15–30 MB | Minimal (~50 kB) | Minimal (~100 kB) |
+| Works offline / no server | Yes | Yes (binary bundled) | No — server required | Partial |
+| Proof bundle can cover Rust pipeline | Yes — bindings call the same Rust code the server uses | Partial — server is a black box | No | No |
+| Install experience | `pip install wifi-densepose` — wheel has no system deps | `pip install` downloads 25 MB binary | `pip install` — pure Python | `pip install` — pure Python |
+| Maintenance surface | Python bindings + Rust workspace | Python thin shim | Python client | Python reimpl must track Rust |
+| Async / tokio support | PyO3 0.28 `pyo3-asyncio` or `pyo3-async-runtimes` for async export; sync entry points for the DSP hot path | N/A | Native asyncio on client | N/A |
+| GIL concern | DSP-heavy calls release GIL via `py.allow_threads`; tokio runtime per module | N/A | None | N/A |
+| Fits existing architecture | Core + vitals + signal already have clean public APIs (`lib.rs` re-exports) | Requires sensing-server to be running | Requires sensing-server | Forks the domain model |
+
+**Subprocess wrapper** is rejected because shipping a 25 MB pre-built server binary
+inside every pip wheel is an unacceptably heavy install, and it makes offline scripting
+impossible without starting the server.
+
+**REST/WS client only** is rejected because it provides zero DSP utility offline and
+cannot close the witness gap — the proof bundle must exercise the same pipeline code.
+
+**Pure Python reimplementation** is the root cause of the current drift and is
+explicitly rejected.
+
+The chosen path starts small: **bind only the three crates with the highest Python
+utility** (`wifi-densepose-core`, `wifi-densepose-vitals`, `wifi-densepose-signal`),
+ship a `py3-none-any` pure-Python WS/MQTT client layer as a separate sub-module, and
+grow from there.
+
+---
+
+## 5. Detailed design
+
+### 5.1 Rust crates bound in v2.0 (first wheel)
+
+Three crates are in scope for the initial binding. They were chosen because they have
+no heavy system dependencies (no libtorch, no ONNX runtime), have stable `pub` re-export
+surfaces in `lib.rs`, and directly address the three most-requested missing capabilities.
+
+| Crate | Exported Python types / functions | Binding rationale |
+|---|---|---|
+| `wifi-densepose-core` | `CsiFrame`, `CsiMetadata`, `Keypoint`, `KeypointType`, `PersonPose`, `PoseEstimate`, `Confidence`, `BoundingBox` | Foundation types shared by all other crates; without these users can't even describe a frame |
+| `wifi-densepose-vitals` | `CsiVitalPreprocessor`, `BreathingExtractor`, `HeartRateExtractor`, `VitalAnomalyDetector`, `VitalSignStore`, `VitalReading`, `VitalEstimate`, `AnomalyAlert` | The most-asked-for surface: HR/BR from a CSI buffer in 4 lines of Python |
+| `wifi-densepose-signal` | `CsiProcessor`, `CsiProcessorConfig`, `PhaseSanitizer`, `MotionDetector`, `MotionScore`, `FeatureExtractor`, `HardwareNormalizer` | DSP pipeline that produces the features vitals and pose estimation consume |
+
+Crates **deferred to P6+**: `wifi-densepose-nn` (requires libtorch or candle — wheel
+size risk), `wifi-densepose-mat` (depends on nn), `wifi-densepose-ruvector` (RuVector
+GNN types — high value but adds ruvector-gnn 2.0.5 link dependency),
+`wifi-densepose-hardware` (ESP32 HAL — not Python-scripting friendly).
+
+### 5.2 New workspace member: `python/`
+
+A new crate `python/` is added as a workspace member at `v2/crates/wifi-densepose-py/`.
+It is a `cdylib` that re-exports the three bound crates behind a single maturin module
+named `wifi_densepose._core`.
+
+```toml
+# v2/crates/wifi-densepose-py/Cargo.toml (sketch)
+[package]
+name = "wifi-densepose-py"
+version.workspace = true
+edition.workspace = true
+
+[lib]
+name = "_core"
+crate-type = ["cdylib"]
+
+[dependencies]
+pyo3 = { version = "0.28", features = ["extension-module", "abi3-py310"] }
+wifi-densepose-core   = { path = "../wifi-densepose-core", features = ["serde"] }
+wifi-densepose-vitals = { path = "../wifi-densepose-vitals" }
+wifi-densepose-signal = { path = "../wifi-densepose-signal" }
+```
+
+The `abi3-py310` feature locks the stable ABI to CPython 3.10+, so one wheel binary
+works across 3.10, 3.11, 3.12, and 3.13 without recompilation.
+
+PyO3 bindings pattern (example for `CsiFrame`):
+
+```rust
+// v2/crates/wifi-densepose-py/src/core_types.rs
+use pyo3::prelude::*;
+use wifi_densepose_core::CsiFrame as RustCsiFrame;
+
+#[pyclass(name = "CsiFrame")]
+#[derive(Clone)]
+pub struct PyCsiFrame {
+    inner: RustCsiFrame,
+}
+
+#[pymethods]
+impl PyCsiFrame {
+    #[new]
+    fn new(amplitudes: Vec<f32>, phases: Vec<f32>, n_subcarriers: usize,
+           sample_index: u64, sample_rate_hz: f32) -> Self {
+        Self { inner: RustCsiFrame { amplitudes, phases, n_subcarriers,
+                                     sample_index, sample_rate_hz } }
+    }
+
+    #[getter] fn amplitudes(&self) -> Vec<f32> { self.inner.amplitudes.clone() }
+    #[getter] fn phases(&self) -> Vec<f32> { self.inner.phases.clone() }
+    #[getter] fn n_subcarriers(&self) -> usize { self.inner.n_subcarriers }
+}
+```
+
+DSP calls that execute >1 ms release the GIL:
+
+```rust
+#[pymethods]
+impl PyCsiProcessor {
+    fn process<'py>(&mut self, py: Python<'py>, frame: &PyCsiFrame)
+        -> PyResult<Option<PyProcessedSignal>>
+    {
+        py.allow_threads(|| self.inner.process(&frame.inner))
+            .map(|opt| opt.map(PyProcessedSignal::from))
+            .map_err(|e| PyRuntimeError::new_err(e.to_string()))
+    }
+}
+```
+
+### 5.3 pip package layout
+
+```
+wifi-densepose/                  ← PyPI package name (unchanged)
+  wifi_densepose/                ← importable namespace
+    __init__.py                  ← re-exports core types + version
+    _core.pyd / _core.so         ← compiled PyO3 extension (maturin build output)
+    vitals.py                    ← thin Python wrapper + docstrings over _core vitals types
+    signal.py                    ← thin Python wrapper over _core signal types
+    client/
+      __init__.py
+      ws.py                      ← asyncio WebSocket client for sensing-server /ws/sensing
+      mqtt.py                    ← paho-mqtt wrapper for ruview/<node_id>/raw/* topics
+      ha.py                      ← helpers for HA-DISCO payloads (read-only, mirrors ADR-115 §3.2)
+    witness/
+      __init__.py
+      verify.py                  ← Python-callable witness verifier (re-creates ADR-028 proof
+                                     over the Rust pipeline via PyO3 bindings, not archive/v1/)
+    compat/
+      v1.py                      ← import shim that raises MigrationError (see §9)
+    py.typed                     ← PEP 561 marker
+```
+
+The import path intentionally maps to Rust crate names:
+
+```python
+from wifi_densepose import CsiFrame           # core types
+from wifi_densepose.vitals import BreathingExtractor, HeartRateExtractor
+from wifi_densepose.signal import CsiProcessor, MotionDetector
+from wifi_densepose.client.ws import SensingClient
+from wifi_densepose.witness import verify_bundle
+```
+
+### 5.4 PyPI distribution — wheel matrix
+
+Published as `wifi-densepose==2.0.0` using **cibuildwheel** driven by GitHub Actions.
+
+| Platform | Arch | CPython | Tag (stable ABI) |
+|---|---|---|---|
+| `manylinux_2_28` | x86_64 | 3.10+ | `cp310-abi3-manylinux_2_28_x86_64` |
+| `manylinux_2_28` | aarch64 | 3.10+ | `cp310-abi3-manylinux_2_28_aarch64` |
+| `macosx_11_0` | x86_64 | 3.10+ | `cp310-abi3-macosx_11_0_x86_64` |
+| `macosx_11_0` | arm64 | 3.10+ | `cp310-abi3-macosx_11_0_arm64` |
+| `win` | amd64 | 3.10+ | `cp310-abi3-win_amd64` |
+| sdist | — | — | source fallback |
+
+The `abi3-py310` flag means **one binary per OS/arch** covers all supported Python
+versions — 5 wheels total plus an sdist, compared to the 20-wheel matrix that would be
+needed without stable ABI.
+
+```yaml
+# .github/workflows/pip-release.yml (sketch)
+- uses: pypa/cibuildwheel@v2
+  with:
+    package-dir: v2/crates/wifi-densepose-py
+    output-dir: dist
+  env:
+    CIBW_BUILD: "cp310-*"
+    CIBW_ARCHS_LINUX: "x86_64 aarch64"
+    CIBW_ARCHS_MACOS: "x86_64 arm64"
+    CIBW_ARCHS_WINDOWS: "AMD64"
+    CIBW_BEFORE_BUILD: "pip install maturin"
+    CIBW_BUILD_FRONTEND: "build[uv]"
+```
+
+### 5.5 CLI parity
+
+The pip wheel installs a `wifi-densepose` console script. In v2 this script is a thin
+Python shim that:
+
+1. Checks whether `wifi-densepose-sensing-server` binary is on `PATH` (installed
+   separately via a platform-specific binary distribution or `cargo install`).
+2. If found: proxies `wifi-densepose serve`, `wifi-densepose stream`, etc. to the Rust
+   binary via `subprocess.run`.
+3. If not found: falls back to the PyO3 module for offline DSP commands
+   (`wifi-densepose vitals --file recording.jsonl`).
+
+This is explicitly **not** a reimplementation of the CLI — the Rust binary
+(`wifi-densepose-cli/src/main.rs`, currently exposes `mat` and `version` subcommands)
+is the authoritative CLI. The pip shim is a discovery/convenience layer.
+
+### 5.6 WS/MQTT client layer
+
+`wifi_densepose.client.ws.SensingClient` is a pure-Python asyncio client wrapping the
+sensing-server WebSocket at `/ws/sensing`:
+
+```python
+async with SensingClient("ws://localhost:8765/ws/sensing") as client:
+    async for msg in client.stream():
+        if msg.type == "edge_vitals":
+            print(msg.breathing_rate_bpm, msg.heartrate_bpm)
+```
+
+`wifi_densepose.client.mqtt.RuViewMqttClient` wraps paho-mqtt and subscribes to
+`ruview/<node_id>/raw/+` as defined in ADR-115 §3.2.
+
+Both clients are **pure Python** (no PyO3) and are optional dependencies (`pip install
+wifi-densepose[client]`). They depend on `websockets>=12` and `paho-mqtt>=2` respectively.
+
+### 5.7a Beamforming Feedback Loop Data (BFLD) support — new binding target
+
+**Added 2026-05-24 per maintainer feedback during P3 implementation.**
+
+BFLD is the transmitter-side, AP-station-loop view of the WiFi channel
+— compressed beamforming feedback frames that 802.11ac/ax/be stations
+send to the AP per sounding cycle. From a sensing perspective it
+complements receiver-side CSI:
+
+| | Receiver-side CSI (current) | BFLD (this addition) |
+|---|---|---|
+| Source | RX side of the radio (e.g. Nexmon CSI on Pi 5, ESP32 promisc cb) | Sniffed BFR frames in the air or `mac80211` ACK trace |
+| Subcarriers (HE20) | 52 (HT-LTF) or 242 (HE-LTF) | Up to 996 (HE160 compressed BFR) — denser |
+| Hardware requirements | Patched Broadcom/Cypress or ESP32 specifically | **Any** 802.11ac+ station-AP pair — no patched firmware |
+| Privacy model | Captures everyone in radio range | Same |
+| Maturity in repo | Production (ADR-014, ADR-018, ADR-039) | Research; no Rust crate yet |
+| Suitable use case | Through-wall pose + vitals | Dense subcarrier reflection profile for AETHER-class biometric (ADR-024) and the soul-signature spec (`docs/research/soul/`) |
+
+#### Binding strategy
+
+Because the Rust workspace has no `wifi-densepose-bfld` crate yet, P3
+ships a **forward-compatible Python trait surface** that the future
+Rust crate plugs into without changing the Python API:
+
+```python
+from wifi_densepose import BfldFrame, BfldReport
+
+# Today (P3): construct from a parsed BFR feedback matrix (the bring-
+# your-own-parser path). Users on Pi 5 + Wireshark BFR dissector
+# pipe frames in directly.
+frame = BfldFrame.from_compressed_feedback(
+    timestamp_ms=…,
+    sounding_index=…,
+    sta_mac="aa:bb:cc:…",
+    bandwidth_mhz=80,
+    n_subcarriers=996,
+    feedback_matrix=…,  # numpy ndarray complex64 [Nr × Nc × Nsc]
+)
+
+# P3 also ships a stub `BfldReport` aggregator that mirrors how
+# `VitalEstimate` aggregates `VitalReading`s. Users who have BFR
+# pipelines feeding RuView can use this today via the
+# bring-your-own-parser path.
+
+# Tomorrow (post-v2.0): the `wifi-densepose-bfld` Rust crate (TBD —
+# separate ADR-1xx) provides ingestion from Nexmon `nl80211` traces +
+# kernel `mac80211` debugfs hooks, and the pip wheel transparently
+# binds it without changing this Python surface.
+```
+
+#### Why this matters
+
+Three reasons BFLD belongs in v2.0 rather than waiting for the Rust
+core:
+
+1. **Customer pull**. Several integrators reading the ADR-115 release
+   notes asked about WiFi-6 dense-subcarrier capture; the answer is
+   BFLD, and we want the API stable before they build pipelines.
+2. **Soul-signature dependency**. The soul-signature research spec
+   (`docs/research/soul/specification.md`) lists "Subcarrier Reflection
+   Profile" as one of seven biometric channels. At HE20/HE80 the
+   dense BFR subcarriers are the right input — exposing `BfldFrame`
+   now lets researchers prototype the channel without waiting on a
+   Rust ingestion crate.
+3. **Cross-vendor portability**. CSI ingestion needs patched
+   firmware. BFR ingestion works on stock 802.11ac/ax hardware
+   (capture via `tcpdump`/Wireshark + a BFR dissector). Shipping the
+   Python data structures first gives the community a way to feed
+   RuView from gear we don't directly support.
+
+#### Implementation surface in P3
+
+Lands as a new module `bindings/bfld.rs` (~150 lines, three
+`#[pyclass]` types):
+
+- `BfldFrame` (frozen) — one compressed feedback matrix snapshot.
+  Constructors: `from_compressed_feedback(...)` and
+  `from_uncompressed_v(...)` (the 802.11n V-matrix form).
+  Properties: `timestamp_ms`, `sounding_index`, `sta_mac`,
+  `bandwidth_mhz`, `n_subcarriers`, `n_rows` (Nr), `n_cols` (Nc),
+  `feedback_matrix` (numpy ndarray complex64).
+- `BfldReport` (frozen) — aggregator over a window of `BfldFrame`s.
+  Properties: `n_frames`, `timestamp_first`, `timestamp_last`,
+  `mean_amplitude_per_subcarrier`, `coherence_score`. The Python
+  side gives users a stable handle for "all BFR data in this 60-s
+  scan" without leaking the storage representation.
+- `BfldKind` (`#[pyclass(eq, eq_int, hash, frozen)]`) — enum
+  enumerating the BFR variants we support: `CompressedHE20`,
+  `CompressedHE40`, `CompressedHE80`, `CompressedHE160`,
+  `UncompressedHT20`, `UncompressedHT40`.
+
+Stub Rust implementation lives in `python/src/bfld_stub.rs` until
+the proper Rust crate exists; it's intentionally not in v2/crates/.
+A new ADR-1xx will own the Rust ingestion crate when we commit to it.
+
+#### Open questions added
+
+- §9.11 — Should BFLD ingestion live in a new `wifi-densepose-bfld`
+  crate or in `wifi-densepose-signal` extended?
+- §9.12 — Per-vendor BFR variant compatibility (Broadcom vs Intel vs
+  Qualcomm encode the compressed angles slightly differently) — how
+  much normalisation belongs in the Python binding vs. the future
+  Rust crate?
+
+### 5.7 Witness chain (re-rooted to the Rust pipeline)
+
+`wifi_densepose.witness.verify_bundle(path)` replaces the v1 proof verification with a
+new chain that exercises the Rust pipeline via PyO3:
+
+```python
+from wifi_densepose.witness import verify_bundle
+
+result = verify_bundle("dist/witness-bundle-ADR028-*/")
+assert result.verdict == "PASS", result.detail
+```
+
+Internally it:
+1. Loads the 1,000-frame reference JSON from the bundle.
+2. Feeds each frame through `PyCsiProcessor` (PyO3 binding of the Rust `CsiProcessor`).
+3. Hashes the output using the same SHA-256 scheme as `archive/v1/data/proof/verify.py`.
+4. Compares against the published hash in `expected_features.sha256`.
+
+The v1 proof (`archive/v1/data/proof/verify.py`) is **preserved unchanged** — it
+continues to prove the v1 pipeline. The new `witness.py` proves the v2/Rust pipeline.
+Both can coexist; the ADR-028 witness bundle ships with both.
+
+---
+
+## 6. Migration path (phased)
+
+```
+P1  ──►  P2  ──►  P3  ──►  P4  ──►  P5  ──►  P6+
+scaffold  core   vitals+   client   publish  deferred
+          types  signal    layer    v2.0.0
+```
+
+### P1 — Scaffold (1 week)
+
+- [ ] Add `v2/crates/wifi-densepose-py/` as workspace member.
+- [ ] `Cargo.toml`: `crate-type = ["cdylib"]`, pyo3 0.28 + `abi3-py310`, no
+  workspace deps yet (empty module compiles and imports).
+- [ ] `pyproject.toml` at repo root `python/` with `[build-system] requires =
+  ["maturin>=1.8"]` and `[tool.maturin] features = ["pyo3/extension-module"]`.
+- [ ] CI job: `maturin develop` on ubuntu-latest in a Python 3.12 venv; import
+  `wifi_densepose._core` succeeds.
+- [ ] Publish `wifi-densepose==1.99.0` to PyPI with a migration notice in the
+  module body (see §9 — no new features, just the tombstone release).
+
+### P2 — Core type bindings (1 week)
+
+- [ ] Bind `CsiFrame`, `CsiMetadata`, `Confidence`, `Keypoint`, `KeypointType`,
+  `BoundingBox`, `PoseEstimate`, `PersonPose` from `wifi-densepose-core`.
+- [ ] All types: `__repr__`, `__eq__`, `__hash__` where meaningful; serde JSON
+  round-trip via `pyo3-serde` or manual `to_dict()` / `from_dict()`.
+- [ ] Add `py.typed` + stub `.pyi` file generated by `pyo3-stub-gen`.
+- [ ] Unit tests: `tests/test_core.py` — construct each type, round-trip JSON.
+
+### P3 — Vitals + signal DSP bindings (2 weeks)
+
+- [ ] Bind the full 4-stage vitals pipeline:
+  `CsiVitalPreprocessor`, `BreathingExtractor`, `HeartRateExtractor`,
+  `VitalAnomalyDetector`, `VitalSignStore`, `VitalReading`, `VitalEstimate`,
+  `AnomalyAlert`.
+- [ ] Bind signal DSP entry points: `CsiProcessor`, `CsiProcessorConfig`,
+  `PhaseSanitizer`, `MotionDetector`, `HardwareNormalizer`.
+- [ ] GIL release (`py.allow_threads`) on all calls >0.5 ms (measured in bench).
+- [ ] Integration test: feed 1,000 frames from `archive/v1/data/proof/sample_csi_data.json`
+  through the PyO3 vitals pipeline; assert output is deterministic across runs.
+- [ ] Re-implement `witness/verify.py` using P3 bindings; compare SHA-256 against the
+  v1 expected hash. **Note:** the hash will differ because the Rust and Python
+  processors are not identical — generate and publish a new `expected_features_v2.sha256`.
+
+### P4 — WS/MQTT client layer (1 week)
+
+- [ ] Implement `wifi_densepose.client.ws.SensingClient` (asyncio, `websockets>=12`).
+- [ ] Implement `wifi_densepose.client.mqtt.RuViewMqttClient` (paho-mqtt 2.x).
+- [ ] Add `wifi_densepose.client.ha` helpers that parse ADR-115 MQTT discovery payloads
+  into Python dataclasses.
+- [ ] Integration test: spin up `sensing-server` in Docker with `--mock-frames`;
+  assert `SensingClient` receives `edge_vitals` messages.
+
+### P5 — First cibuildwheel publish as v2.0.0 (1 week)
+
+- [ ] `.github/workflows/pip-release.yml` — cibuildwheel matrix (5 wheels + sdist).
+- [ ] `python_requires = ">=3.10"` (stable ABI base).
+- [ ] Populate `pyproject.toml` with minimal `install_requires`: `pyo3` is a build dep,
+  not a runtime dep. Runtime extras: `[client]` adds `websockets>=12,paho-mqtt>=2`.
+- [ ] `pip install wifi-densepose==2.0.0` and smoke-test on each CI platform.
+- [ ] PyPI publish via Trusted Publisher (OIDC, no API token in secrets).
+- [ ] Announce: `wifi-densepose==1.99.0` tombstone already on PyPI; `v2.0.0` replaces
+  it in search results.
+
+### P3.5 — BFLD binding surface (concurrent with P3)
+
+**Added 2026-05-24 per maintainer feedback.** See §5.7a for the rationale.
+
+- [ ] `python/src/bindings/bfld.rs` — `BfldFrame`, `BfldReport`,
+  `BfldKind` `#[pyclass]` wrappers backed by a stub Rust impl
+  pending the v3 `wifi-densepose-bfld` crate.
+- [ ] `python/src/bfld_stub.rs` — minimal in-crate stub storage
+  (vec of compressed feedback matrices) so the Python API is
+  fully usable today even before the Rust ingestion crate lands.
+- [ ] Numpy bridge for `feedback_matrix` (Complex64 ndarray) — same
+  approach as `CsiFrame.amplitude` from P3.
+- [ ] Tests covering: per-bandwidth constructor paths
+  (HE20/HE40/HE80/HE160 + HT20/HT40), n_subcarriers contract,
+  coherence_score sanity, BfldKind hashability + equality.
+- [ ] Forward-compat contract test: `BfldFrame` constructed today
+  from a numpy ndarray must round-trip through (de)serialisation
+  identically once the Rust crate exists.
+- [ ] §9.11 + §9.12 open questions raised so the eventual Rust crate
+  has clear decisions waiting for it.
+
+P3.5 is concurrent with P3 (no new schedule cushion needed) because
+the Python surface is independent of the rest of the v2/ workspace.
+Land in the same wheel as P3.
+
+### P6+ — Deferred
+
+- [ ] `wifi-densepose-bfld` Rust crate — proper ingestion from
+  Nexmon BFR pcaps + `mac80211` debugfs. Replaces the P3.5 stub
+  storage without changing the Python API. Owns its own ADR-1xx.
+- [ ] `wifi-densepose-nn` bindings (libtorch / candle wheel size TBD — see Open
+  Questions §13.3).
+- [ ] `wifi-densepose-ruvector` bindings (RuVector attention types).
+- [ ] MQTT/Matter integration helpers (`wifi_densepose.client.matter`).
+- [ ] Deprecation notice on `wifi-densepose==1.x` releases (PyPI yank — see §9).
+- [ ] `wifi-densepose-sensing-server` binary distribution via pip extra
+  (`pip install wifi-densepose[server]` fetches pre-built binary for the platform).
+- [ ] HACS Python integration built on top of the pip client layer (follow-on to
+  ADR-115 §6.A).
+
+---
+
+## 7. Compatibility and deprecation
+
+### 7.1 Version bump strategy
+
+`wifi-densepose==2.0.0` is a **hard major-version break**. The 1.x import namespace
+`src.*` is incompatible with the 2.x namespace `wifi_densepose.*`. There is no shim
+that can bridge them transparently.
+
+### 7.2 Tombstone release: v1.99.0
+
+Before publishing v2.0.0, publish `wifi-densepose==1.99.0` as a pure-Python sdist/wheel
+whose sole content is:
+
+```python
+# wifi_densepose/__init__.py  (v1.99.0)
+raise ImportError(
+    "wifi-densepose 1.x has been superseded by v2.0.0 which wraps "
+    "the Rust-based stack. Run:\n\n"
+    "    pip install wifi-densepose==2.0.0\n\n"
+    "Migration guide: https://github.com/ruvnet/RuView/blob/main/docs/pip-migration.md\n"
+    "Legacy v1 source: archive/v1/ in the repository"
+)
+```
+
+This ensures any project pinned to `wifi-densepose>=1` that upgrades to 1.99.0 gets a
+clear error rather than a silent broken import.
+
+### 7.3 PyPI yank strategy
+
+After v2.0.0 is stable (90-day observation window):
+
+- Yank `wifi-densepose==1.0.0` — never had a separate stable release period; was
+  superseded 4 hours after publication.
+- Leave `wifi-densepose==1.1.0` un-yanked but deprecated in the description.
+- Publish `wifi-densepose==1.99.0` as the canonical 1.x landing page (raise error).
+
+Yanked versions remain installable with `pip install wifi-densepose==1.1.0 --force`
+so users with reproducible builds pinned to exact versions are not broken silently.
+
+### 7.4 Semver
+
+| Version | Content |
+|---|---|
+| 1.0.0 – 1.1.0 | Legacy Python server (archive/v1/) |
+| **1.99.0** | Tombstone: ImportError migration notice |
+| **2.0.0** | PyO3 Rust bindings + WS/MQTT client |
+| 2.x.y | Additive bindings + client improvements |
+| 3.0.0 | If/when nn bindings added (libtorch wheel size may force a separate package) |
+
+---
+
+## 8. Alternatives considered and rejected
+
+### Alt-A: Subprocess wrapper
+
+Package the pre-built `wifi-densepose-sensing-server` Rust binary inside the pip wheel.
+Python calls it via `subprocess`. **Rejected** because: the binary is 15–30 MB stripped;
+the install footprint is prohibitive; offline DSP scripting still requires the server to
+be running; the witness chain cannot exercise Rust code through a black-box binary.
+
+### Alt-B: REST/WS client only
+
+Ship a pure-Python package that is purely a client to a running `sensing-server`
+instance. **Rejected** because: it provides zero offline utility; it cannot host the
+witness chain over the Rust pipeline; it solves the "Python access to telemetry" problem
+but not the "Python DSP / prototyping" problem that academic and embedded users need.
+
+### Alt-C: Pure Python reimplementation
+
+Rewrite the DSP pipeline in pure Python/NumPy to reach parity with the Rust
+implementation. **Rejected explicitly** — this is the root cause of the current 11-month
+drift and the pattern this ADR is designed to exit. Any Python reimplementation will
+immediately begin drifting again as the Rust stack evolves.
+
+---
+
+## 9. Risks
+
+| Risk | Likelihood | Severity | Mitigation |
+|---|---|---|---|
+| **Build matrix complexity** — 5 target triples × cibuildwheel setup; CI time; QEMU for aarch64 cross-compile | High | Medium | Use `abi3-py310` (5 wheels not 20); QEMU aarch64 emulation available in GitHub Actions; maturin handles auditwheel automatically |
+| **Binary size** — future nn/ONNX bindings may push wheel past 50 MB | Medium | High | Keep nn bindings in a separate `wifi-densepose-nn` PyPI package; keep core+vitals+signal wheel lean (~2 MB stripped) |
+| **GIL / async issues** — PyO3 wrapping tokio crates requires careful runtime management; `py.allow_threads` must be used around all blocking Rust calls | High | High | Restrict initial bindings to synchronous Rust APIs (vitals, signal, core are all sync); async sensing-server client stays in pure-Python `client/ws.py` |
+| **Maintainer overhead** — two languages, two build systems, one PyPI package | Medium | Medium | maturin unifies the build; CI handles publishing; start with 3 bound crates only |
+| **1.x user breakage** — users pinned to `wifi-densepose>=1,<2` will get the tombstone | Low | Medium | 1.99.0 tombstone gives a clear error; maintain 1.1.0 on PyPI un-yanked for 90 days post-v2 |
+| **Windows Rust toolchain in CI** — linking PyO3 on Windows requires MSVC or mingw; extra CI complexity | Medium | Medium | GitHub Actions `windows-latest` has MSVC; maturin + cibuildwheel handle this natively |
+| **Stable ABI limitations** — `abi3` precludes some advanced PyO3 features (e.g. `Buffer` protocol) | Low | Low | Core/vitals/signal types are scalar/Vec<f32> — no need for buffer protocol in P2–P3 |
+| **PyPI name ownership** — we own `wifi-densepose` on PyPI (confirmed via rUv author field) | Low | Low | Confirm with `pypi.org/user/ruvnet` before publishing |
+
+---
+
+## 10. Acceptance criteria
+
+The following checks must all pass before ADR-117 is considered Accepted:
+
+- [ ] `pip install wifi-densepose==2.0.0` succeeds on Python 3.10, 3.11, 3.12, 3.13
+  on linux/x86_64, macos/arm64, and windows/amd64 in a clean venv with no extra build tools.
+- [ ] `python -c "import wifi_densepose; print(wifi_densepose.__version__)"` prints `2.0.0`.
+- [ ] `python -c "from wifi_densepose import CsiFrame; f = CsiFrame([1.0]*56, [0.0]*56, 56, 0, 100.0); print(f)"` produces a non-error repr.
+- [ ] The 4-stage vitals pipeline processes 1,000 frames in under 500 ms on a
+  reference machine (CPython 3.12, linux x86_64, no GPU).
+- [ ] `wifi_densepose.witness.verify_bundle(path)` returns `verdict="PASS"` for a
+  freshly generated witness bundle from `scripts/generate-witness-bundle.sh`.
+- [ ] `wifi_densepose.client.ws.SensingClient` receives at least one `edge_vitals`
+  message from a `sensing-server --mock-frames` instance within 5 seconds.
+- [ ] `pip install wifi-densepose==1.99.0` raises `ImportError` with the migration URL.
+- [ ] The compiled `_core` extension has no unresolved dynamic library dependencies
+  beyond libc/msvcrt (verified by `auditwheel show` on Linux, `delocate-listdeps` on macOS).
+- [ ] Type stubs (`wifi_densepose/*.pyi`) are present; `mypy --strict` passes on the
+  example code in `examples/vitals_from_buffer.py`.
+- [ ] Total wheel size for core+vitals+signal: `≤ 5 MB` per platform.
+
+---
+
+## 11. Open questions
+
+1. **Stable ABI base version**: `abi3-py310` drops support for Python 3.9, which v1.1.0
+   declared. Is Python 3.9 EOL-enough (EOL 2025-10-05) to drop cleanly? *Tentative: yes,
+   drop 3.9. Use abi3-py310.*
+
+2. **Package name for nn bindings**: if `wifi-densepose-nn` bindings require a 30 MB
+   libtorch wheel, should they live at `wifi-densepose-nn` (separate PyPI package) or
+   as an optional heavy extra of `wifi-densepose[nn]`? *Tentative: separate package to
+   avoid polluting the lean wheel.*
+
+3. **Witness hash continuity**: the Rust pipeline will produce a different SHA-256 than
+   the v1 Python pipeline for the same input frames. The new `expected_features_v2.sha256`
+   must be generated and committed before v2.0.0 ships. Who generates it, and how is
+   the generation process itself witnessed? *Tentative: generate in CI, commit hash to
+   `archive/v1/data/proof/`, include in ADR-028 matrix.*
+
+4. **`ruv-neural` crate**: `v2/crates/ruv-neural/` exists in the workspace. Is it a
+   candidate for early Python bindings (useful for training-loop scripting), or should
+   it wait for the nn/train tier? *Tentative: defer — it depends on training backends.*
+
+5. **Tokio runtime**: `wifi-densepose-sensing-server` is tokio-based, but the three
+   crates bound in P2–P3 (`core`, `vitals`, `signal`) are synchronous. Are there any
+   hidden tokio dependencies that would force a runtime into the extension module?
+   *Tentative: inspect each crate's Cargo.toml for tokio deps before P1 scaffold.*
+
+6. **`pyo3-stub-gen` vs manual stubs**: automated stub generation from PyO3 has rough
+   edges for generics and newtype patterns. Should we hand-write `.pyi` stubs for the
+   first release? *Tentative: use `pyo3-stub-gen` for scaffolding, hand-tune for public
+   API.*
+
+7. **`wifi_densepose` vs `wifi-densepose` namespace**: the pip package name uses a dash
+   (`wifi-densepose`) but Python imports use underscores (`wifi_densepose`). The v1
+   package shipped under `src.*`, not `wifi_densepose.*`. Is there any tooling that
+   hardcodes the `src` namespace? *Tentative: the `src.*` namespace was specific to
+   `archive/v1/` and is cleanly dropped.*
+
+8. **cibuildwheel version**: the current stable is cibuildwheel v2.x. Does the
+   project's existing GitHub Actions config need updates for maturin builds vs
+   the current `cargo build` / `build.py` patterns? *Tentative: yes, add a separate
+   `pip-release.yml` workflow; do not modify existing Rust CI.*
+
+9. **RuVector bindings timeline**: the `wifi-densepose-ruvector` crate (`v2/crates/`)
+   depends on `ruvector-gnn = "2.0.5"`. Does ruvector-gnn ship as a pre-built static
+   lib or require linking at build time? This directly affects the P6+ wheel size.
+   *Tentative: investigate ruvector-gnn link strategy before committing to a timeline.*
+
+10. **`wifi_densepose.client.ha` conflict with ADR-115/116**: the `ha.py` helper module
+    should not duplicate the ADR-115 MQTT discovery logic in Python. Should it be read-only
+    (parse HA discovery JSON → Python dataclasses) or also write (publish discovery JSON)?
+    *Tentative: read-only for v2.0. Write path deferred to the HACS integration follow-on
+    (ADR-115 §6.A).*
+
+11. **BFLD Rust crate ownership** (added 2026-05-24): the P3.5 BFLD bindings ship with a
+    stub Rust impl in `python/src/bfld_stub.rs`. The proper Rust crate (Nexmon BFR pcap
+    parser + `mac80211` debugfs ingestor) will land later. Should it be a new
+    `wifi-densepose-bfld` workspace member, or should it extend `wifi-densepose-signal`?
+    *Tentative: new dedicated crate. Reasons: (a) the BFR parser is significant code
+    (Wireshark's dissector is ~2k lines) and bloats `-signal`; (b) BFLD ingestion is
+    optional — many deployments will only use CSI; gating behind a separate crate keeps
+    the default `-signal` lean. Decide before committing to the crate name in any
+    `pyproject.toml` extras.*
+
+12. **BFLD per-vendor compressed-angle variants** (added 2026-05-24): 802.11 standardizes
+    the compressed beamforming feedback format but vendors (Broadcom, Intel, Qualcomm,
+    MediaTek) differ in psi/phi quantization step + ordering of consecutive matrix
+    entries. How much normalisation belongs in the Python `BfldFrame.from_compressed_feedback`
+    binding vs. the future Rust crate? *Tentative: Python binding is dumb (numpy ndarray
+    in, numpy ndarray out — no decoding); the future Rust crate owns per-vendor
+    normalisation, exposed via a `Vendor` enum on the binding constructor. Confirm via
+    a per-vendor test fixture before P3.5 ships.*
+
+---
+
+## 12. References
+
+### BFLD references (added 2026-05-24 for §5.7a + §11.11 + §11.12)
+
+- Hernandez & Bulut, *"Wi-Fi Sensing With Compressed Beamforming Feedback"*, ACM TOSN 2024 — first systematic survey of BFR-as-sensing
+- Yousefi, Soltanaghaei & Bharadia, *"Just-In-Time Wi-Fi Sensing Using Compressed Beamforming Feedback"*, MobiSys 2023 — practical pipeline for breath + heart-rate extraction from sniffed BFR
+- IEEE 802.11ax-2021 §27.3.10 — Compressed Beamforming Feedback frame format
+- Wireshark BFR dissector — `packet-ieee80211.c` reference implementation
+- AX210 Linux mac80211 debugfs BFR capture path (kernel 6.10+)
+- Sample BFR-vs-CSI parity dataset — TBD; we'll publish one alongside the
+  `wifi-densepose-bfld` crate when it lands
+
+### Original references
+
+- **PyPI package (current)**: https://pypi.org/project/wifi-densepose/ — v1.1.0, released 2025-06-07
+- **PyPI JSON metadata**: https://pypi.org/pypi/wifi-densepose/json
+- **Local source**: `archive/v1/setup.py`, `archive/v1/src/__init__.py`, `archive/v1/data/proof/verify.py`
+- **Rust workspace**: `v2/Cargo.toml`, `v2/crates/wifi-densepose-core/src/lib.rs`,
+  `v2/crates/wifi-densepose-vitals/src/lib.rs`, `v2/crates/wifi-densepose-signal/src/lib.rs`,
+  `v2/crates/wifi-densepose-sensing-server/src/lib.rs`
+- **PyO3 docs**: https://pyo3.rs/ — v0.28.3 stable, Rust ≥1.83 required
+- **maturin docs**: https://maturin.rs/ — supports Python 3.8+ on Linux/macOS/Windows/FreeBSD
+- **cibuildwheel docs**: https://cibuildwheel.pypa.io/
+- **ADR-021**: ESP32 vitals — defines the HR/BR extraction pipeline this ADR exposes in Python
+- **ADR-028**: ESP32 capability audit — defines the witness bundle format `witness/verify.py` must re-verify
+- **ADR-115**: HA-DISCO + HA-MIND + HA-FABRIC — defines the MQTT topic structure the `client/mqtt.py` helper consumes
+- **ADR-116**: HA-COG cog packaging — parallel effort; ADR-117 pip library is the developer-facing Python surface; ADR-116 is the Seed-installable artifact

docs/adr/ADR-118-bfld-beamforming-feedback-layer-for-detection.md

@@ -0,0 +1,196 @@
+# ADR-118: BFLD — Beamforming Feedback Layer for Detection
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-24 |
+| **Deciders** | ruv |
+| **Codename** | **BFLD** — Beamforming Feedback Layer for Detection |
+| **Relates to** | [ADR-024](ADR-024-contrastive-csi-embedding-model.md) (AETHER), [ADR-027](ADR-027-cross-environment-domain-generalization.md) (MERIDIAN), [ADR-028](ADR-028-esp32-capability-audit.md) (witness), [ADR-029](ADR-029-ruvsense-multistatic-sensing-mode.md) (multistatic), [ADR-030](ADR-030-ruvsense-persistent-field-model.md) (field model), [ADR-031](ADR-031-ruview-sensing-first-rf-mode.md) (sensing-first), [ADR-032](ADR-032-multistatic-mesh-security-hardening.md) (mesh security), [ADR-095](ADR-095-rvcsi-edge-rf-sensing-platform.md) (rvCSI), [ADR-115](ADR-115-home-assistant-integration.md) (HA), [ADR-116](ADR-116-cog-ha-matter-seed.md) (Matter), [ADR-117](ADR-117-pip-wifi-densepose-modernization.md) (pip) |
+| **Sub-ADRs** | [ADR-119](ADR-119-bfld-frame-format-and-wire-protocol.md) (frame), [ADR-120](ADR-120-bfld-privacy-class-and-hash-rotation.md) (privacy), [ADR-121](ADR-121-bfld-identity-risk-scoring.md) (risk), [ADR-122](ADR-122-bfld-ruview-ha-matter-exposure.md) (RuView), [ADR-123](ADR-123-bfld-capture-path-nexmon-and-esp32.md) (capture) |
+| **Research bundle** | [`docs/research/BFLD/`](../research/BFLD/) (11 files, 13,544 words) |
+| **Companion research** | [`docs/research/soul/`](../research/soul/) — Soul Signature multi-modal biometric. BFLD is the policy-enforcement and compliance layer for Soul Signature; the two share the AETHER encoder (ADR-024), the witness chain (ADR-110/028), the RVF container, and `cross_room.rs` (ADR-030). |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+### 1.1 The plaintext BFI problem
+
+IEEE 802.11ac and 802.11ax beamforming feedback (BFI) is exchanged between client stations (STA) and access points (AP) in **unencrypted management-plane frames**. The STA compresses the channel response into a Givens-rotation angle matrix (Φ/ψ) and transmits it as a VHT/HE Compressed Beamforming Report (CBFR). Any device in WiFi monitor mode within range can passively sniff these frames without joining the network.
+
+Two independent 2024–2025 research results establish the severity of this exposure:
+
+1. **BFId** (KIT, ACM CCS 2025) — re-identifies 197 individuals from BFI alone with >90% accuracy from 5 s of capture. https://publikationen.bibliothek.kit.edu/1000185756
+2. **LeakyBeam** (NDSS 2025) — detects occupancy through walls at 20 m with 82.7% TPR / 96.7% TNR using only plaintext BFI. https://www.ndss-symposium.org/wp-content/uploads/2025-5-paper.pdf
+
+Capture tooling is freely available: **Wi-BFI** (pip-installable), **PicoScenes**, **Nexmon BFI patches** for BCM43455c0 (Raspberry Pi 5 / 4 / 3B+).
+
+### 1.2 Gap in the existing RuView pipeline
+
+The wifi-densepose / RuView pipeline processes CSI via the rvCSI runtime (ADR-095/096) and emits presence, pose, vitals, and zone-activity events. **No layer in the existing pipeline measures whether the data it is processing is capable of identifying individuals.** All CSI is treated as equivalent from a privacy standpoint regardless of operating regime.
+
+This gap becomes a compliance and liability issue at deployment scale. An operator placing RuView in a care home, hotel, shared office, or rental property has no instrument to verify that the system is operating anonymously.
+
+### 1.3 BFI as a sensing signal
+
+BFI is not only a threat vector — its compressed angle matrices carry multipath geometry useful for presence and motion detection, particularly in single-AP deployments where MIMO CSI is unavailable. BFLD treats BFI as an **optional input alongside CSI**, not a replacement.
+
+### 1.4 Relationship to the Soul Signature research
+
+The Soul Signature research (`docs/research/soul/`) defines a 7-channel multi-modal biometric for **consent-based** passive re-identification of enrolled individuals. Where Soul Signature *intentionally produces* identity (with a 60-second enrollment protocol), BFLD *measures and gates* identity leakage from the same sensing substrate. The two systems are complementary by design:
+
+| Concern | Soul Signature | BFLD |
+|---------|----------------|------|
+| Intent | Create a biometric for enrolled persons | Measure and gate identity leakage |
+| Consent model | Explicit enrollment, GDPR/HIPAA modes | Default-deny, all unenrolled persons |
+| Operating class | Must run at `privacy_class = 1` (derived) | Defaults to class 2 (anonymous) |
+| Shared assets | AETHER encoder (ADR-024), WitnessChain (ADR-110/028), RVF container, `cross_room.rs` (ADR-030) | Same |
+| ID space | Long-lived opaque `person_id` per enrolled subject | Rotating `rf_signature_hash` per day per unenrolled person |
+
+BFLD becomes Soul Signature's enforcement layer: the `identity_risk_score` gates whether a zone is leaky enough to enroll, the witness bundle is the regulator-facing audit artifact, and the structural privacy invariants (I1/I2/I3) ensure unenrolled bystanders stay anonymous even in zones where Soul Signature is actively matching enrolled persons. See ADR-120 §2.7 and ADR-121 §2.7 for the integration points.
+
+### 1.5 What this ADR is *not*
+
+- Not a removal of the CSI pipeline. ADR-095/096 rvCSI stays authoritative for CSI.
+- Not a port of any external sniffer into the repo. The Nexmon capture path lives in a separate adapter (see ADR-123).
+- Not a Matter SDK ship — Matter exposure is filtered through the ADR-116 `cog-ha-matter` boundary.
+
+---
+
+## 2. Decision
+
+Create a new Rust crate **`wifi-densepose-bfld`** in `v2/crates/` that:
+
+1. **Ingests** BFI angle matrices (Φ/ψ) from CBFR frames, optionally fused with CSI.
+2. **Computes** nine named features and an `identity_risk_score` (separability × temporal_stability × cross_perspective_consistency × sample_confidence).
+3. **Gates** all output through a `privacy_class` byte that **structurally prevents** identity-correlated data from being published at classes 2 (anonymous) and 3 (restricted).
+4. **Emits** `BfldEvent` JSON over MQTT under `ruview/<node_id>/bfld/*` with per-class topic routing.
+5. **Enforces three invariants structurally, not by policy**:
+   - **I1**: Raw BFI never exits the node.
+   - **I2**: Identity embedding is in-RAM-only (no disk, no network).
+   - **I3**: Cross-site identity correlation is cryptographically impossible via per-site keyed BLAKE3 hash rotation with a daily epoch.
+
+The umbrella implementation is decomposed into five sub-ADRs:
+
+| Sub-ADR | Scope |
+|---------|-------|
+| **ADR-119** | `BfldFrame` wire format, magic `0xBF1D_0001`, deterministic serialization, CRC32 |
+| **ADR-120** | `privacy_class` semantics, BLAKE3 hash rotation, default-deny field classification |
+| **ADR-121** | Identity risk scoring formula, coherence gate, leakage estimator |
+| **ADR-122** | RuView surface: HA entities, Matter cluster boundary, MQTT topic ACL |
+| **ADR-123** | Capture path: Pi 5 / Nexmon adapter + ESP32-S3 BFI feasibility |
+
+### 2.1 Crate module layout
+
+```
+v2/crates/wifi-densepose-bfld/
+├── Cargo.toml
+└── src/
+    ├── lib.rs
+    ├── frame.rs             # BfldFrame (ADR-119)
+    ├── extractor.rs         # CBFR parser → BfiCapture
+    ├── features.rs          # 9 features
+    ├── identity_risk.rs     # risk score (ADR-121)
+    ├── privacy_gate.rs      # privacy_class enforcement (ADR-120)
+    ├── hash_rotation.rs     # BLAKE3 per-site rotation (ADR-120)
+    ├── emitter.rs           # BfldEvent → MQTT
+    ├── mqtt.rs              # topic routing (ADR-122)
+    └── ffi.rs               # PyO3 bindings (ADR-117 pattern)
+```
+
+### 2.2 Reuse map
+
+| BFLD module | Depends on |
+|---|---|
+| `features.rs` | `wifi-densepose-signal/src/ruvsense/coherence.rs`, `multistatic.rs` |
+| `identity_risk.rs` | `wifi-densepose-ruvector/src/viewpoint/attention.rs`, `coherence.rs` |
+| `privacy_gate.rs` | (new) — no upstream dependency |
+| `hash_rotation.rs` | `blake3 = "1.5"` (keyed mode) |
+| `extractor.rs` | `vendor/rvcsi/crates/rvcsi-adapter-nexmon` (ADR-095/096) |
+
+---
+
+## 3. Consequences
+
+### Positive
+
+- First explicit, auditable RF-layer privacy primitive in the wifi-densepose ecosystem.
+- `identity_risk_score` doubles as an anomaly signal (sudden spike → new AP firmware / nearby attacker-grade sniffer / unusual propagation).
+- BFI fusion augments presence/motion in single-AP deployments.
+- Deterministic frame hashes extend the ADR-028 witness-bundle pattern to the new surface.
+- Cross-site isolation is **structural, not policy-dependent** — a stronger guarantee than ACLs.
+
+### Negative
+
+- ESP32-S3 cannot directly capture CBFR via the Espressif WiFi API. Full BFLD pipeline requires a Pi 5 / Nexmon host sniffer (cognitum-v0 available; see ADR-123).
+- `identity_risk_score` calibration requires the KIT BFId dataset (non-commercial research agreement).
+- Estimated effort: ~10.5 engineer-weeks across the six ADRs.
+
+### Neutral
+
+- BFLD does not prevent passive BFI capture by an external attacker (LeakyBeam-class). It only ensures the **node's own output** is non-identifying. Operators must understand this distinction.
+- Daily hash rotation prevents multi-day analytics correlating individual signatures across the day boundary. Acceptable for privacy goals; may surprise analytics use-cases.
+
+---
+
+## 4. Alternatives Considered
+
+### Alt 1: Skip BFI entirely (CSI-only)
+
+Rejected because: (a) leaves the identity-leakage gap open for the CSI pipeline; (b) as BFI tooling becomes ubiquitous (Wi-BFI, PicoScenes), the absence of a privacy layer becomes more conspicuous for operators.
+
+### Alt 2: Publish `identity_risk_score` publicly by default
+
+Rejected: the risk score itself is privacy-sensitive (reveals presence via timing correlation). Default is opt-in.
+
+### Alt 3: Cloud ML on raw BFI
+
+Rejected: violates I1. Cloud training creates an off-node store of angle matrices reconstructible into identity profiles.
+
+### Alt 4: Differential privacy noise on BFI at ingress
+
+Deferred to a follow-up ADR. DP sensitivity analysis and its interaction with `identity_risk_score` calibration are not yet complete. Current design achieves privacy through structural impossibility, not noise injection.
+
+---
+
+## 5. Acceptance Criteria
+
+- [ ] **AC1**: Extractor parses BFI from 802.11ac and 802.11ax captures, 20/40/80/160 MHz, 2×2 through 4×4 MIMO.
+- [ ] **AC2**: Presence detection latency ≤ 1 s p95 from first non-empty BFI frame.
+- [ ] **AC3**: Motion score published at ≥ 1 Hz on `ruview/<node_id>/bfld/motion/state`.
+- [ ] **AC4**: Raw BFI bytes never present in any serialized `BfldFrame` payload at any `privacy_class` value.
+- [ ] **AC5**: With `privacy_mode` enabled, all identity-derived fields are absent from outbound events.
+- [ ] **AC6**: Identical `BfiCapture` inputs produce bit-identical `BfldFrame` serialization (deterministic hash).
+- [ ] **AC7**: Pipeline produces valid `BfldEvent` outputs without `csi_matrix` (BFI-only mode).
+
+Per-sub-ADR acceptance criteria are defined in ADR-119 through ADR-123.
+
+---
+
+## 6. Phased Rollout
+
+| Phase | ADR | Scope | Effort |
+|-------|-----|-------|--------|
+| **P1** | 119 | Frame format + extractor stub | 1.5 wk |
+| **P2** | 121 | Features + identity_risk_score | 2.0 wk |
+| **P3** | 120 | Privacy gate + hash rotation | 1.5 wk |
+| **P4** | 122 (a) | MQTT emitter + HA discovery | 1.5 wk |
+| **P5** | 122 (b) | Matter cluster boundary in `cog-ha-matter` | 1.5 wk |
+| **P6** | 123 | Pi 5 / Nexmon capture adapter | 2.5 wk |
+| **Total** | | | **10.5 wk** |
+
+---
+
+## 7. Related ADRs
+
+See header table. Cross-references in body cite the structural reuse of:
+- ADR-024 (AETHER embedding for identity_risk computation)
+- ADR-027 (MERIDIAN's no-cross-site assumption is now structurally enforced by I3)
+- ADR-028 (witness-bundle extends to BFLD surface)
+- ADR-029/030 (`multistatic.rs`, `cross_room.rs` reused)
+- ADR-095/096 (rvCSI Nexmon adapter for BFI capture)
+- ADR-115 (HA surface extension)
+- ADR-116 (`cog-ha-matter` boundary filter)
+- ADR-117 (PyO3 bindings pattern)

docs/adr/ADR-119-bfld-frame-format-and-wire-protocol.md

@@ -0,0 +1,163 @@
+# ADR-119: BFLD Frame Format and Wire Protocol
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-24 |
+| **Deciders** | ruv |
+| **Parent** | [ADR-118](ADR-118-bfld-beamforming-feedback-layer-for-detection.md) |
+| **Relates to** | [ADR-028](ADR-028-esp32-capability-audit.md) (witness/deterministic proof), [ADR-095](ADR-095-rvcsi-edge-rf-sensing-platform.md) (rvCSI `CsiFrame` schema) |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+The BFLD pipeline (ADR-118) emits an over-the-wire `BfldFrame` consumed by the RuView aggregator, HA bridge, and witness bundle. The frame must be:
+
+1. **Deterministic** — identical input ⇒ bit-identical output, so witness hashes survive verification (ADR-028 pattern).
+2. **Self-describing** — magic + version so future BFLD revisions don't silently corrupt aggregator state.
+3. **Privacy-classified at the byte level** — the receiver must know the data class before it even parses the payload, so it can drop frames it isn't authorized to handle.
+4. **Compact** — BFLD nodes may emit at up to 10 Hz; the frame must be small enough for unsharded MQTT and ESP-NOW transport.
+5. **Endianness-stable** — captures from x86_64 (ruvultra), aarch64 (cognitum-v0, Pi 5 cluster), and Xtensa (ESP32-S3) must produce identical bytes.
+
+The existing rvCSI `CsiFrame` (ADR-095) is the closest precedent. BFLD reuses the same little-endian convention and the same "validate-before-FFI" posture.
+
+---
+
+## 2. Decision
+
+### 2.1 `BfldFrame` header (40 bytes, little-endian, packed)
+
+```rust
+#[repr(C, packed)]
+pub struct BfldFrameHeader {
+    pub magic: u32,              // 0xBF1D_0001
+    pub version: u16,            // 1
+    pub flags: u16,              // bit0=has_csi_delta, bit1=privacy_mode, bit2-15 reserved
+    pub timestamp_ns: u64,       // monotonic capture clock
+
+    pub ap_hash: [u8; 16],       // BLAKE3-keyed(site_salt, ap_mac)[0..16]
+    pub sta_hash: [u8; 16],      // BLAKE3-keyed(site_salt ‖ day_epoch, sta_mac)[0..16]
+    pub session_id: [u8; 16],    // ephemeral, rotated on capture-session boundary
+
+    pub channel: u16,            // 802.11 channel number
+    pub bandwidth_mhz: u16,      // 20 | 40 | 80 | 160
+    pub rssi_dbm: i16,
+    pub noise_floor_dbm: i16,
+
+    pub n_subcarriers: u16,
+    pub n_tx: u8,
+    pub n_rx: u8,
+    pub quantization: u8,        // 0=f32, 1=i16, 2=i8, 3=packed (4-bit nibbles)
+    pub privacy_class: u8,       // 0=raw, 1=derived, 2=anonymous, 3=restricted (default 2)
+
+    pub payload_len: u32,
+    pub payload_crc32: u32,      // CRC-32/ISO-HDLC over payload bytes only
+}
+```
+
+Total header size: **86 bytes packed** (validated by `static_assertions::const_assert_eq!` in `wifi-densepose-bfld/src/frame.rs`). Earlier drafts stated 40 bytes — that was a counting error caught during P1 scaffold; see AC1 below.
+
+### 2.2 Payload structure
+
+Payload is a length-prefixed sequence of typed sections in this exact order:
+
+```
+payload = compressed_angle_matrix
+        ‖ amplitude_proxy
+        ‖ phase_proxy
+        ‖ snr_vector
+        ‖ optional_csi_delta            (present iff flags.bit0 set)
+        ‖ optional_vendor_extension     (length 0 allowed)
+```
+
+Each section is `[u32 len_le][bytes...]`. The CRC32 covers all section bytes including length prefixes, but **not** the header.
+
+### 2.3 Privacy-class gating at serialization
+
+The serializer enforces these rules **before** writing any payload bytes:
+
+| `privacy_class` | `compressed_angle_matrix` | Identity-derived fields | Notes |
+|-----------------|---------------------------|-------------------------|-------|
+| 0 (`raw`) | full | full | **Local-only**, never serialized to a network sink |
+| 1 (`derived`) | downsampled to 8-bit, top-k subcarriers | full | Operator-acknowledged research mode |
+| 2 (`anonymous`, **default**) | absent (zero-length section) | absent | Production default |
+| 3 (`restricted`) | absent | absent + diagnostic-only | Equivalent to class 2 + suppresses `identity_risk_score` on the bus |
+
+The serializer returns `Err(BfldError::PrivacyViolation)` if the caller attempts to publish a class-0 frame through a network sink. This is enforced by a sink-type marker trait (`LocalSink` vs `NetworkSink`).
+
+### 2.4 Deterministic serialization
+
+Three guarantees:
+
+1. **Field order is fixed** by `#[repr(C, packed)]`.
+2. **Float quantization is canonical** — `quantization` byte values 1/2/3 use specified round-half-to-even with documented saturation; f32 (value 0) is forbidden over the wire (local-only).
+3. **CRC32 is computed last**, after all section bytes are placed.
+
+The witness test in `tests/determinism.rs` captures a 200-frame BFI fixture, serializes it 1,000 times across two threads, and verifies the BLAKE3 of the resulting byte stream is bit-identical.
+
+### 2.5 Magic value rationale
+
+`0xBF1D_0001` is chosen so that `bf1d` reads as "BFLD" in hex-dump output, easing wireshark / xxd debugging. The final `0001` is the major version; minor revisions bump `version` field.
+
+---
+
+## 3. Consequences
+
+### Positive
+
+- 40-byte header + compact payload fits comfortably in a 1500-byte MTU even at 4×4 MIMO with 256 subcarriers.
+- Serialization is `#[no_std]` compatible — same code can run on ESP32-S3 (when ESP-NOW transport is added under ADR-123 P2).
+- Witness-bundle integration is direct: the existing `archive/v1/data/proof/verify.py` pattern extends to a `bfld_verify.py` that consumes the same SHA-256 expected-hash file format.
+
+### Negative
+
+- `#[repr(C, packed)]` on the header means consumers must use `read_unaligned` — small ergonomic cost, mitigated by a `#[derive(BfldFrameAccess)]` proc-macro.
+- Reserved flag bits 2-15 lock in future-extension order; any new bit assignment is a version bump.
+
+### Neutral
+
+- The vendor-extension section allows downstream RuView cogs (e.g., `cog-pose-estimation`) to attach metadata without a header change, at the cost of CRC scope creep. Vendor sections are explicitly outside the witness hash.
+
+---
+
+## 4. Alternatives Considered
+
+### Alt 1: Protobuf / FlatBuffers
+
+Rejected: schema evolution overhead, witness-hash instability across protoc versions, ~3× wire bloat for the small fixed-shape fields.
+
+### Alt 2: CBOR
+
+Rejected: deterministic CBOR (RFC 8949 §4.2) is achievable but the parser surface is large and tag handling is a footgun for the `no_std` ESP32 path.
+
+### Alt 3: Variable-width magic / no magic
+
+Rejected: receivers must distinguish BFLD frames from rvCSI `CsiFrame` and other RuView payloads on shared transports.
+
+### Alt 4: Move CRC32 to header
+
+Rejected: CRC must be computed after the payload, so its value would otherwise force a header rewrite; placing it last avoids a buffer-pass-back.
+
+---
+
+## 5. Acceptance Criteria
+
+- [ ] **AC1**: `BfldFrameHeader` size is exactly **86 bytes** (packed) on x86_64, aarch64, and xtensa-esp32s3. The size was initially documented as 40 bytes during ADR drafting — that was a counting error; the implementation in `wifi-densepose-bfld/src/frame.rs` enforces the correct value via `const_assert_eq!`.
+- [ ] **AC2**: 1,000 serializations of a fixed `BfiCapture` fixture produce a bit-identical BLAKE3 hash.
+- [ ] **AC3**: `privacy_class = 0` frame returned through `NetworkSink::publish()` returns `Err(BfldError::PrivacyViolation)`.
+- [ ] **AC4**: Payload CRC32 mismatch causes `BfldFrame::parse()` to return `Err(BfldError::Crc)` without exposing partial payload state.
+- [ ] **AC5**: Round-trip serialize/parse preserves all header fields exactly.
+- [ ] **AC6**: A frame with `flags.bit0 = 0` (no CSI delta) and an unexpected CSI-delta section is rejected.
+- [ ] **AC7**: Bench: serialization throughput ≥ 50k frames/sec on a 2025-era M1/M2 / Pi 5 core.
+
+---
+
+## 6. References
+
+- ADR-118 §2 (umbrella decision)
+- ADR-095 `CsiFrame` (`vendor/rvcsi/crates/rvcsi-core/src/frame.rs`)
+- CRC-32/ISO-HDLC: `crc = "3"` crate
+- BLAKE3 keyed mode: `blake3 = "1.5"`
+- IEEE 802.11-2020 §19.3.12 (Compressed Beamforming Report)

docs/adr/ADR-120-bfld-privacy-class-and-hash-rotation.md

@@ -0,0 +1,192 @@
+# ADR-120: BFLD Privacy Class and Hash Rotation
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-24 |
+| **Deciders** | ruv |
+| **Parent** | [ADR-118](ADR-118-bfld-beamforming-feedback-layer-for-detection.md) |
+| **Relates to** | [ADR-027](ADR-027-cross-environment-domain-generalization.md) (MERIDIAN no-cross-site), [ADR-032](ADR-032-multistatic-mesh-security-hardening.md) (mesh security), [ADR-106](ADR-106-dp-sgd-and-primitive-isolation.md) (primitive isolation), [ADR-115](ADR-115-home-assistant-integration.md) (privacy mode) |
+| **Companion research** | [`docs/research/soul/`](../research/soul/) — Soul Signature operates at `privacy_class = 1` (derived). §2.7 defines the dual-ID-space contract. |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+ADR-118 declares three structural invariants for BFLD:
+
+- **I1**: Raw BFI never exits the node.
+- **I2**: Identity embedding is in-RAM-only.
+- **I3**: Cross-site identity correlation is cryptographically impossible.
+
+I1/I2 are enforced by sink typing and module visibility (ADR-119 §2.3). I3 requires a hash-rotation scheme that makes the same physical person produce **different** `rf_signature_hash` values across sites and across day boundaries, without any out-of-band coordination between sites.
+
+The existing `HA-PRIVACY` mode in ADR-115 already toggles between "full" and "anonymous" surfaces, but at a per-event granularity — not at a per-byte-field granularity. BFLD requires the latter because the `BfldFrame` payload mixes sensing data (publishable) and identity-derived data (non-publishable) in the same struct.
+
+The BFId paper (KIT, ACM CCS 2025) demonstrates that even a few minutes of BFI capture across the same site is sufficient to build a persistent biometric. The mitigation must be **structural**, not policy-dependent.
+
+---
+
+## 2. Decision
+
+### 2.1 The four privacy classes
+
+A single `privacy_class: u8` byte in the `BfldFrame` header (ADR-119 §2.1) selects one of four classes. The crate enforces field availability statically through marker types.
+
+| Class | Name | Use case | Available fields |
+|-------|------|----------|------------------|
+| **0** | `raw` | Local-only research, never networked | All fields, full-precision BFI matrix, identity embedding |
+| **1** | `derived` | Operator-acknowledged research over LAN | Downsampled angle matrix, full features, identity_risk_score, identity_embedding |
+| **2** | `anonymous` (**default**) | Production deployment | Aggregate sensing only: presence, motion, person_count, zone_id, confidence |
+| **3** | `restricted` | Care-home / regulated deployment | Class 2 minus `identity_risk_score` and `rf_signature_hash` |
+
+Default for new RuView nodes is class **2**. Operators must explicitly opt-down to class 1 via the existing `--research-mode` flag (ADR-115 §7); class 0 is reserved for `cargo test` and is unreachable from `wifi-densepose-sensing-server`.
+
+### 2.2 Enforcement via marker types
+
+```rust
+pub trait Sink {}
+
+pub trait LocalSink: Sink {}     // Allowed: classes 0,1,2,3
+pub trait NetworkSink: Sink {}   // Allowed: classes 1,2,3 (NOT class 0)
+pub trait MatterSink: NetworkSink {}  // Allowed: class 2,3 + cluster-filter (ADR-122)
+
+impl Emitter {
+    pub fn publish<S: NetworkSink>(&self, sink: &S, frame: BfldFrame)
+        -> Result<(), BfldError>
+    {
+        if frame.header.privacy_class == 0 {
+            return Err(BfldError::PrivacyViolation {
+                reason: "class 0 to NetworkSink",
+            });
+        }
+        // ... serialize and write
+    }
+}
+```
+
+The compiler refuses to call `publish` on a sink that doesn't impl `NetworkSink` with a class-0 frame because the runtime check is paired with a sink-marker check. Cross-sink frame routing requires an explicit class transition (see §2.4).
+
+### 2.3 BLAKE3 keyed hash rotation for `rf_signature_hash`
+
+The signature hash is computed as:
+
+```rust
+pub fn rf_signature_hash(
+    site_salt: &[u8; 32],       // generated on first boot, persisted in TPM/KMS
+    day_epoch: u32,             // floor(unix_time_utc / 86400)
+    features: &IdentityFeatures,
+) -> Hash {
+    let mut hasher = blake3::Hasher::new_keyed(site_salt);
+    hasher.update(&day_epoch.to_le_bytes());
+    hasher.update(&features.canonical_bytes());
+    hasher.finalize()
+}
+```
+
+**Structural cross-site isolation**: because `site_salt` is a 256-bit random secret unique to each node and never transmitted, two sites observing the same physical person produce uncorrelated hashes. There is no key the operator (or an attacker who compromises one node) can use to bridge sites. This is stronger than a policy-based "do not share" rule because the bridge **cannot be computed**.
+
+**Daily rotation**: `day_epoch` flipping at UTC midnight forces the hash of the same person to change once per day. Multi-day correlation requires re-acquiring the biometric, which the rotation actively breaks.
+
+### 2.4 Class-transition transformer
+
+The only way a high-class frame becomes a lower-class frame is through `PrivacyGate::demote(frame, target_class)`. This function:
+
+1. Asserts the target class is strictly higher number than (or equal to) the input class.
+2. Zeroes the disallowed fields with `subtle::Zeroize`.
+3. Re-computes `payload_crc32`.
+4. Returns the new frame.
+
+There is no `promote` operation — a class-2 frame cannot be turned back into a class-1 frame, because the dropped fields were not retained anywhere reachable from the gate.
+
+### 2.5 `identity_embedding` lifecycle
+
+The embedding (output of the AETHER encoder, ADR-024) is held in a `subtle::Zeroizing<[f32; 128]>` ring buffer of 64 entries (≈30 KB). Entries are:
+
+1. Written by the encoder on each capture window.
+2. Consumed by `identity_risk_score` computation (ADR-121).
+3. **Never** written to disk, MQTT, or any other I/O sink — there is no `Serialize` impl on the type.
+4. Overwritten by the ring (FIFO).
+
+A compile-time `#[forbid(serde::Serialize)]` lint on `IdentityEmbedding` ensures a future PR cannot accidentally add a `Serialize` derive.
+
+### 2.6 Default-deny field classification
+
+Every new field added to `BfldFrame` or `BfldEvent` must be tagged with `#[must_classify]` (a custom attribute macro). The macro fails compilation if the field is not listed in the per-class allow-list table. This forces future contributors to make an explicit privacy decision on every new field.
+
+### 2.7 Dual-ID-space contract for Soul Signature deployments
+
+Soul Signature (`docs/research/soul/`) is a consent-based biometric system that *intentionally* produces long-lived per-person identity. It cannot operate at the default class 2 — the identity_embedding it needs is structurally absent there. The contract:
+
+| Deployment mode | `privacy_class` | ID space for unenrolled bystanders | ID space for enrolled persons |
+|---|---|---|---|
+| Default BFLD-only | 2 (anonymous) | Daily-rotated `rf_signature_hash` | n/a — no enrollment |
+| Soul Signature opt-in | **1 (derived)** | Daily-rotated `rf_signature_hash` (unchanged) | Long-lived opaque `person_id` from Soul Signature graph |
+| Restricted / care-home | 3 (restricted) | Suppressed | n/a — Soul Signature **disabled** at class 3 |
+
+Two ID spaces coexist with **no collision**: the rotating hash is the privacy-preserving identifier for everyone *not* on the consent roster; the stable `person_id` is reserved for enrolled subjects under their own GDPR/HIPAA mode. Soul Signature's `match_against_enrolled()` function consumes only the in-RAM `identity_embedding` (I2 still holds) and emits a `person_id` plus a calibrated similarity score; it never writes the embedding to disk or the wire. The class-1 requirement is enforced statically: the Soul Signature match API takes a `&IdentityEmbedding` parameter, which is only constructible when the BFLD crate is compiled with `--features soul-signature` against a class-1 frame.
+
+---
+
+## 3. Consequences
+
+### Positive
+
+- Cross-site identity correlation is **computationally impossible**, not merely "prohibited by policy". This is the strongest form of privacy guarantee available without a TEE.
+- Default-deny via `#[must_classify]` prevents the common pattern of "a new field shipped, then six months later we noticed it was identity-leaky".
+- `identity_embedding` cannot be serialized by accident — the type system carries the constraint.
+- The class transition transformer makes the data lifecycle explicit and auditable.
+
+### Negative
+
+- `site_salt` storage requires either a TPM (ADR-095/096 rvCSI platform feature gap) or a secrets file with strict mode. Loss of `site_salt` makes historical witness comparisons impossible — by design, but a documentation hazard.
+- `#[must_classify]` is a custom proc-macro; another moving part in the build.
+- Operators wanting multi-day analytics must work in aggregates only, not on per-individual signatures.
+
+### Neutral
+
+- Class 0 is `cargo test`-only. Some CI runners may need an explicit feature flag to compile class-0 paths.
+
+---
+
+## 4. Alternatives Considered
+
+### Alt 1: Single boolean `privacy_mode` flag (status quo from ADR-115)
+
+Rejected: insufficient granularity. The frame mixes publishable sensing with non-publishable identity, so the gate must operate at field-level, not event-level.
+
+### Alt 2: SHA-256 instead of BLAKE3
+
+Rejected: BLAKE3 keyed-hash mode is ~5× faster on the ESP32-S3 / Cortex-M cores and the security margin is equivalent for this use case. SHA-256 has no keyed-hash mode (HMAC-SHA256 is the alternative; works but is slower).
+
+### Alt 3: Hash rotation on the hour, not the day
+
+Rejected: hourly rotation breaks legitimate "person was here in the morning, came back in the afternoon" use-cases that operators may want. Day boundary is the compromise.
+
+### Alt 4: Per-event nonces instead of daily epoch
+
+Rejected: per-event nonces would force the consumer to track which events came from the same person within a session, which leaks identity information by structure. The day epoch preserves a coarse temporal grouping without leaking finer-grained identity.
+
+---
+
+## 5. Acceptance Criteria
+
+- [ ] **AC1**: Calling `Emitter::publish` with a `privacy_class = 0` frame on a `NetworkSink` returns `BfldError::PrivacyViolation`.
+- [ ] **AC2**: Two BFLD nodes with different `site_salt` values observing the same simulated person produce `rf_signature_hash` values whose Hamming distance is ≥ 120 bits over 100 trials (statistical isolation test).
+- [ ] **AC3**: A frame with `privacy_class = 3` has both `identity_risk_score` and `rf_signature_hash` absent from the serialized payload.
+- [ ] **AC4**: `PrivacyGate::demote(class_1_frame, target=0)` fails to compile (compile-fail test).
+- [ ] **AC5**: A PR adding a new field to `BfldEvent` without `#[must_classify]` fails the build.
+- [ ] **AC6**: `IdentityEmbedding` has no `Serialize` impl reachable from any public function.
+- [ ] **AC7**: Dropping an `IdentityEmbedding` value zeroizes its memory (verified by a debugger-readable test under `cargo test --features zeroize-validation`).
+
+---
+
+## 6. References
+
+- ADR-118 (umbrella)
+- ADR-119 (frame format; `privacy_class` byte location)
+- KIT BFId (ACM CCS 2025): https://publikationen.bibliothek.kit.edu/1000185756
+- NDSS LeakyBeam (2025): https://www.ndss-symposium.org/wp-content/uploads/2025-5-paper.pdf
+- BLAKE3 keyed-hash: https://github.com/BLAKE3-team/BLAKE3
+- `subtle::Zeroize` for memory hygiene

docs/adr/ADR-121-bfld-identity-risk-scoring.md

@@ -0,0 +1,182 @@
+# ADR-121: BFLD Identity Risk Scoring and Coherence Gate
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-24 |
+| **Deciders** | ruv |
+| **Parent** | [ADR-118](ADR-118-bfld-beamforming-feedback-layer-for-detection.md) |
+| **Relates to** | [ADR-024](ADR-024-contrastive-csi-embedding-model.md) (AETHER), [ADR-027](ADR-027-cross-environment-domain-generalization.md) (MERIDIAN), [ADR-029](ADR-029-ruvsense-multistatic-sensing-mode.md) (multistatic fusion), [ADR-086](ADR-086-edge-novelty-gate.md) (novelty gate precedent), [ADR-120](ADR-120-bfld-privacy-class-and-hash-rotation.md) (privacy class) |
+| **Companion research** | [`docs/research/soul/`](../research/soul/) — risk score doubles as Soul Signature enrollment-quality signal; §2.7 defines the Recalibrate exemption. |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+BFLD's distinguishing primitive is the `identity_risk_score` — a scalar that says **"is this capture window currently capable of identifying a specific person?"**. The score has two consumers:
+
+1. **The operator** — exposed as an HA diagnostic sensor (ADR-122). A spike from the long-term baseline indicates the RF environment has shifted toward a higher-leakage regime (new AP firmware, denser MIMO, attacker-grade sniffer in range).
+2. **The privacy gate** (ADR-120) — when the score crosses a configurable threshold, the gate downgrades the active `privacy_class` automatically (e.g., 2 → 3) until the score recovers.
+
+The score must be:
+- **Bounded** in `[0, 1]` for HA gauge entities.
+- **Calibrated** against actual re-ID success rate, ideally on the KIT BFId dataset.
+- **Computable on-device** at ≥ 1 Hz on a Pi 5 core or an aarch64 cognitum-v0.
+- **Stable** — small environmental changes should not produce wild swings; the score is for slow-moving regime detection, not per-frame chatter.
+
+ADR-086 (edge novelty gate) establishes a precedent for an on-device gate primitive. BFLD's risk scoring borrows the gate-pattern but with identity leakage as the trigger condition.
+
+---
+
+## 2. Decision
+
+### 2.1 Nine features (from BFLD spec §5)
+
+The features are computed over a sliding window of `W = 32` BFI frames (≈3 s at 10 Hz):
+
+| Feature | Definition | Source |
+|---------|------------|--------|
+| `mean_angle_delta` | mean( ‖ Φ_t − Φ_{t-1} ‖ over subcarriers ) | extractor |
+| `subcarrier_variance` | var( ‖ Φ ‖ over subcarrier axis ) | extractor |
+| `temporal_entropy` | Shannon entropy of angle-bin histogram over W | extractor |
+| `doppler_proxy` | FFT peak magnitude of mean-angle time series | features.rs |
+| `path_stability` | 1 − ‖ Φ_t − median(Φ_{t-W..t}) ‖ / scale | features.rs |
+| `cross_antenna_correlation` | mean Pearson correlation across n_tx × n_rx pairs | features.rs |
+| `burst_motion_score` | high-pass-filtered angular velocity, soft-thresholded | features.rs |
+| `stationarity_score` | 1 − rolling KL divergence over W/2 vs W | features.rs |
+| `identity_separability_score` | top-1 cosine to nearest AETHER cluster centroid | identity_risk.rs |
+
+The first eight are sensing features (also used by the presence/motion pipeline). Only the ninth depends on the AETHER embedding and therefore on `identity_class >= 1`.
+
+### 2.2 Identity risk formula
+
+```rust
+pub fn identity_risk_score(
+    sep: f32,    // identity_separability_score, [0, 1]
+    stab: f32,   // temporal_stability, [0, 1] = ema(path_stability, alpha=0.1)
+    consist: f32,// cross_perspective_consistency, [0, 1] = multistatic.rs
+    conf: f32,   // sample_confidence, [0, 1] = f(SNR, n_subcarriers, n_rx)
+) -> f32 {
+    // Clamp inputs, then multiplicative combination — any factor near 0 dominates.
+    let s = sep.clamp(0.0, 1.0);
+    let t = stab.clamp(0.0, 1.0);
+    let p = consist.clamp(0.0, 1.0);
+    let c = conf.clamp(0.0, 1.0);
+    (s * t * p * c).clamp(0.0, 1.0)
+}
+```
+
+Multiplicative combination is chosen so that **any** weak factor (e.g., very low SNR ⇒ low `conf`) collapses the score toward 0. This matches the privacy intent: when the system is uncertain, the score should be low and the operator should not be alarmed.
+
+### 2.3 Calibration target
+
+The score is calibrated against re-ID success rate on a held-out test split of the KIT BFId dataset. A piecewise-linear isotonic regression maps raw scores into a calibrated `[0, 1]` band where `score ≥ 0.8` corresponds to `>80%` re-ID accuracy on a 5-second window in the calibration dataset.
+
+Calibration parameters live in `v2/crates/wifi-densepose-bfld/data/risk_calibration.toml` and are versioned independently of the code. A regression update is a content-only PR.
+
+### 2.4 Coherence gate
+
+The coherence gate (per ADR-029 `coherence_gate.rs` pattern) consumes the risk score and emits one of four actions:
+
+```rust
+pub enum GateAction {
+    Accept,           // score < 0.5, publish normally
+    PredictOnly,      // 0.5 <= score < 0.7, publish but flag confidence
+    Reject,           // 0.7 <= score < 0.9, drop the event
+    Recalibrate,      // score >= 0.9, drop AND rotate site_salt
+}
+```
+
+The `Recalibrate` action triggers a forced site-salt rotation — an aggressive response to a sustained high-risk regime. It costs the operator continuity of long-term aggregate analytics but is the right answer to an attacker-grade sniffer arriving in range.
+
+### 2.5 Hysteresis
+
+To prevent oscillation around the gate thresholds, the gate uses ±0.05 hysteresis and a 5-second debounce. A score must cross the boundary by the hysteresis margin and persist for the debounce window before the gate action changes.
+
+### 2.6 Soul Signature interaction — Recalibrate exemption and enrollment-quality gate
+
+Soul Signature (`docs/research/soul/`) intentionally exists in a high-separability regime — the whole point of its 60-second enrollment protocol is to push `identity_separability_score` toward 1.0. The default coherence gate (§2.4) would therefore fire `Recalibrate` constantly inside Soul Signature zones, rotating `site_salt` every few seconds and breaking enrollment.
+
+Two integrations resolve this:
+
+1. **Recalibrate exemption.** When the gate is about to fire `Recalibrate`, it consults a `SoulMatchOracle` (provided by the Soul Signature crate when compiled with `--features soul-signature`). If the oracle reports that the current high-separability cluster matches an enrolled `person_id` above the Soul Signature acceptance threshold, the gate downgrades to `PredictOnly` instead. The high score is the *intended* outcome of a successful match, not an attack indicator. Without the `soul-signature` feature, the oracle is a no-op stub returning `MatchOutcome::NotEnrolled`, so the gate behaves exactly per §2.4.
+
+2. **Enrollment-quality gate.** Soul Signature's enrollment protocol (`scanning-process.md` §3) requires that the sensing zone meet a minimum identity-leakage regime — too low, and the resulting signature is unreliable. The BFLD `identity_risk_score` is exactly the right signal. Soul Signature gates enrollment on `score >= ENROLL_MIN` (default `0.65`) sustained over the 60-second window. If the score drops below threshold mid-enrollment, the protocol aborts and the operator is prompted to re-attempt in better RF conditions.
+
+The exemption is asymmetric: it suppresses `Recalibrate` only for known-enrolled matches. Unknown high-separability clusters (a real attacker-grade sniffer, or an unenrolled person whose identity is unexpectedly leaky) still trigger `Recalibrate` as designed.
+
+### 2.7 Compute budget
+
+| Stage | Target latency | Implementation |
+|-------|----------------|----------------|
+| Feature extraction (8 features) | < 3 ms per window | ndarray + nalgebra; vectorized over subcarriers |
+| Separability (cosine to centroids) | < 5 ms per window | RuVector RaBitQ index (ADR-085) over ≤ 1k centroids |
+| Risk score | < 0.1 ms | scalar multiplicative |
+| Gate decision + hysteresis | < 0.1 ms | scalar |
+
+Total p95 ≤ 10 ms per window on a Pi 5 core (8 ms target). Headroom on cognitum-v0 (Pi 5 + Hailo) is ample; ESP32-S3 hosts only the extraction stage (features computed; risk score is host-side per ADR-123). The `SoulMatchOracle` lookup (§2.6) adds < 1 ms when the `soul-signature` feature is enabled (RaBitQ index over enrolled centroids).
+
+---
+
+## 3. Consequences
+
+### Positive
+
+- The risk score becomes a first-class diagnostic surface for operators and a structural input to the privacy gate — both consumers from a single computation.
+- Multiplicative combination is conservative under uncertainty; the system is biased toward "report low risk when unsure", which is the right default.
+- Calibration is a content-only update — no recompile needed when the calibration file changes.
+- The recalibration gate action gives the system a self-healing response to a sniffer arrival without operator intervention.
+
+### Negative
+
+- Calibration requires the KIT BFId dataset; without it the score is uncalibrated and serves only as an internal trigger, not a publishable signal.
+- Multiplicative scoring can be dominated by `sample_confidence`, which is sensitive to channel conditions. A persistent low-SNR environment will keep the published score near 0 even when the underlying separability is high — an under-reporting failure mode that the documentation must call out.
+- The recalibrate action breaks historical hash continuity by design; an operator who wants long-term aggregates needs to know they will see a discontinuity on recalibrate events.
+
+### Neutral
+
+- The nine features overlap with the existing CSI pipeline. BFLD computes them on BFI; the CSI pipeline computes them on CSI. Both can be fused via `cross_perspective_consistency`.
+
+---
+
+## 4. Alternatives Considered
+
+### Alt 1: Additive scoring (`(s + t + p + c) / 4`)
+
+Rejected: a sample with high separability but very low confidence would still produce a moderate score, which over-reports risk in degraded RF conditions.
+
+### Alt 2: Maximum scoring (`max(s, t, p, c)`)
+
+Rejected: over-reports risk because any single high factor pins the output, even if the others contradict it.
+
+### Alt 3: Learned scoring (a small MLP)
+
+Rejected for this ADR: introduces an opaque model whose output cannot be audited from first principles. The multiplicative formula is simple, conservative, and directly explainable to operators. A learned model is a future option once enough calibration data is in hand.
+
+### Alt 4: Per-feature thresholds instead of a continuous score
+
+Rejected: continuous score is needed for the HA gauge entity and for downstream calibration. Per-feature thresholds would force operators to interpret nine separate binaries.
+
+---
+
+## 5. Acceptance Criteria
+
+- [ ] **AC1**: All nine features are computed in `< 8 ms` p95 per window on a Pi 5 core.
+- [ ] **AC2**: `identity_risk_score` is monotonic non-decreasing in any single input when the other three are held constant.
+- [ ] **AC3**: Calibration regression on the KIT BFId test split: `score ≥ 0.8` corresponds to ≥ 80% re-ID accuracy ± 5%.
+- [ ] **AC4**: The coherence gate emits `Recalibrate` if score is ≥ 0.9 for ≥ 5 seconds.
+- [ ] **AC5**: Hysteresis prevents action oscillation across ± 0.05 of a threshold within a 5-second window.
+- [ ] **AC6**: At `privacy_class = 3`, the risk score is computed but not published to MQTT (kept local for the gate only).
+- [ ] **AC7**: A reproducible 1,000-frame synthetic fixture produces a deterministic score sequence (bit-identical across runs).
+
+---
+
+## 6. References
+
+- ADR-118 (umbrella)
+- ADR-024 (AETHER encoder for separability)
+- ADR-029 (`coherence_gate.rs` precedent)
+- ADR-086 (edge novelty gate pattern)
+- ADR-120 §2.4 (class transition consumed by gate)
+- KIT BFId dataset: https://publikationen.bibliothek.kit.edu/1000185756

docs/adr/ADR-122-bfld-ruview-ha-matter-exposure.md

@@ -0,0 +1,210 @@
+# ADR-122: BFLD RuView Surface — Home Assistant, Matter, MQTT Exposure
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-24 |
+| **Deciders** | ruv |
+| **Parent** | [ADR-118](ADR-118-bfld-beamforming-feedback-layer-for-detection.md) |
+| **Relates to** | [ADR-031](ADR-031-ruview-sensing-first-rf-mode.md) (sensing-first), [ADR-100](ADR-100-cog-packaging-specification.md) (cog packaging), [ADR-115](ADR-115-home-assistant-integration.md) (HA-DISCO + HA-MIND), [ADR-116](ADR-116-cog-ha-matter-seed.md) (Matter cog), [ADR-120](ADR-120-bfld-privacy-class-and-hash-rotation.md) (privacy class) |
+| **Companion research** | [`docs/research/soul/`](../research/soul/) — Soul Signature deployments expose enrolled-match diagnostics only over HA, never Matter. See §2.7. |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+ADR-115 shipped the RuView Home Assistant surface (21 entities, MQTT auto-discovery, mTLS, privacy mode) on the `wifi-densepose-sensing-server` Rust binary. ADR-116 is packaging this as the `cog-ha-matter` Cognitum Seed cog. BFLD must integrate into this surface without expanding the privacy-sensitive footprint already in production.
+
+The integration must:
+
+1. **Extend HA-DISCO** to advertise BFLD entities via the existing MQTT-discovery scheme.
+2. **Reject identity fields at the Matter boundary** — Matter exposes occupancy/motion/people-count only, never `identity_risk_score` or `rf_signature_hash`.
+3. **Route MQTT topics by privacy class** — class-2/3 events on the public topic tree, class-1 events on a gated `research/` subtree, class-0 events nowhere.
+4. **Federate cleanly into cognitum-v0** — BFLD events from multiple nodes flow through `cognitum-rvf-agent` (port 9004 per CLAUDE.local.md) for cross-node analytics, but identity-derived fields are stripped at the **publishing-node boundary**, not at the federation hub.
+
+---
+
+## 2. Decision
+
+### 2.1 HA entity surface (six new entities per node)
+
+The cog republishes the existing 21 ADR-115 entities and adds:
+
+| Entity ID | Type | Source field | Class gate | Diagnostic |
+|-----------|------|--------------|------------|------------|
+| `binary_sensor.<node>_bfld_presence` | occupancy | `BfldEvent.presence` | ≥ 2 | no |
+| `sensor.<node>_bfld_motion` | gauge `[0,1]` | `BfldEvent.motion` | ≥ 2 | no |
+| `sensor.<node>_bfld_person_count` | int | `BfldEvent.person_count` | ≥ 2 | no |
+| `sensor.<node>_bfld_zone_activity` | enum | `BfldEvent.zone_activity` | ≥ 2 | no |
+| `sensor.<node>_bfld_identity_risk` | gauge `[0,1]` | `BfldEvent.identity_risk_score` | == 2 only | **yes** |
+| `sensor.<node>_bfld_confidence` | gauge `[0,1]` | `BfldEvent.confidence` | ≥ 2 | yes |
+
+The `identity_risk` entity is exposed only under privacy class 2 and is flagged `entity_category: diagnostic` so HA dashboards do not promote it to a main-card sensor by default. Under class 3 it is computed but not published (per ADR-121 §2.4).
+
+MQTT discovery payload follows the ADR-115 schema, plus a `bfld_version` attribute matching the `BfldFrameHeader::version` field.
+
+### 2.2 MQTT topic tree
+
+```
+ruview/<node_id>/bfld/presence/state              # class >= 2
+ruview/<node_id>/bfld/motion/state                # class >= 2
+ruview/<node_id>/bfld/person_count/state          # class >= 2
+ruview/<node_id>/bfld/zone_activity/state         # class >= 2
+ruview/<node_id>/bfld/confidence/state            # class >= 2
+ruview/<node_id>/bfld/identity_risk/state         # class == 2 only
+ruview/<node_id>/bfld/raw                         # class 1, OFF by default
+ruview/<node_id>/bfld/availability                # online/offline marker
+```
+
+`raw` (class-1 derived BFI) is **not present** in the discovery payload at all — operators must explicitly subscribe and acknowledge the research-mode caveat. The publishing crate emits `MQTT_RAW_DISABLED` to availability when `privacy_class < 1`.
+
+### 2.3 Mosquitto ACL example
+
+```
+# Default-deny everything not explicitly granted
+pattern read  ruview/+/bfld/+/state
+pattern read  ruview/+/bfld/availability
+
+# Public roles cannot read identity_risk or raw
+user public
+deny  read ruview/+/bfld/identity_risk/state
+deny  read ruview/+/bfld/raw
+
+# Operator role can read identity_risk for diagnostics
+user operator
+allow read ruview/+/bfld/identity_risk/state
+
+# Research role can read raw (requires class-1 operation)
+user research
+allow read ruview/+/bfld/raw
+```
+
+The cog ships a default ACL template under `cog-ha-matter/etc/mosquitto.acl.d/bfld.conf` for operators who use the embedded broker (ADR-116 §2.2).
+
+### 2.4 Matter cluster boundary
+
+`cog-ha-matter` exposes BFLD via **three Matter clusters** only:
+
+| Matter cluster | Source entity | Notes |
+|---|---|---|
+| Occupancy Sensing (0x0406) | `binary_sensor.<node>_bfld_presence` | reports binary occupancy + uncertainty (mapped from `confidence`) |
+| Boolean State (0x0045) | `sensor.<node>_bfld_motion >= 0.3` | thresholded; raw motion not exposed |
+| Occupancy Sensing extension | `sensor.<node>_bfld_person_count` | uses occupancy-sensor count where Matter spec supports |
+
+**Explicitly NOT exposed via Matter**:
+
+- `identity_risk_score`
+- `rf_signature_hash`
+- `identity_embedding`
+- `raw` BFI
+- `zone_activity` (zone IDs are site-specific and Matter is a cross-site surface)
+- `confidence` (HA-only diagnostic)
+
+The Matter filter is implemented in `cog-ha-matter/src/matter/bfld_filter.rs` as a `MatterSink` trait impl that rejects classes 0 and 1 at compile time (via ADR-120 §2.2 marker types).
+
+### 2.5 Federation with cognitum-v0
+
+`cognitum-rvf-agent` (port 9004) receives BFLD events from multiple nodes. The events arriving at the federation hub are **already class-2/3** — identity-derived fields were stripped at each publishing node. The hub does not see and cannot reconstruct raw BFI or identity embeddings.
+
+The federation contract:
+
+| At publishing node | At cognitum-rvf-agent |
+|---|---|
+| Strip class-0/1 fields per ADR-120 | Receive class-2/3 events only |
+| Rotate `rf_signature_hash` per ADR-120 §2.3 | Aggregate counts; **do not** correlate hashes across sites |
+| Sign event with node Ed25519 key | Verify signature; reject unsigned events |
+
+A `federation-witness` script (extending ADR-028) runs nightly on the hub and proves that no class-0/1 fields appeared in any received event over the previous 24 h.
+
+### 2.6 HA blueprints (shipped with the cog)
+
+Three operator-ready blueprints under `cog-ha-matter/blueprints/`:
+
+1. **Presence-driven lighting** — `binary_sensor.*_bfld_presence` ⇒ `light.turn_on/off` with configurable hold time.
+2. **Motion-aware HVAC** — `sensor.*_bfld_motion > 0.3` ⇒ raise HVAC setpoint by ΔT.
+3. **Identity-risk anomaly notification** — `sensor.*_bfld_identity_risk` exceeds rolling z-score threshold ⇒ HA `notify.*` to the operator with the originating node and the 7-day baseline.
+
+### 2.7 Soul Signature deployment posture
+
+When the cog is compiled with `--features soul-signature`, two additional HA entities are exposed **at class 1 only**, and **never** over Matter:
+
+| Entity ID | Type | Source | Class gate | Matter |
+|-----------|------|--------|------------|--------|
+| `sensor.<node>_soul_match_id` | string (opaque `person_id`) | Soul Signature match oracle | == 1 only | **rejected** |
+| `sensor.<node>_soul_match_score` | gauge `[0,1]` | Match similarity | == 1 only | **rejected** |
+| `sensor.<node>_soul_enrollment_quality` | gauge `[0,1]` | Mirror of `identity_risk_score` during enrollment | == 1 only | **rejected** |
+
+These entities are part of the consent-based diagnostic surface for operators running Soul Signature deployments (care homes with explicit GDPR Art. 9 basis, employment with consent, etc.). The Matter cluster boundary in §2.4 already rejects them by type — the `MatterSink` impl only accepts class-2/3 frames, so `soul_match_id` is structurally unreachable through Matter.
+
+Class-3 deployments **disable Soul Signature** entirely: the `match_against_enrolled()` call returns `MatchOutcome::Suppressed` and no soul entities are published. This makes class 3 the correct setting for any deployment where consent is uncertain or where regulators require Soul Signature to be unavailable.
+
+A fourth blueprint ships only when `--features soul-signature` is enabled:
+
+4. **Enrolled-person arrival notification** — `sensor.*_soul_match_id` transitions to a non-null value ⇒ HA `notify.*` to the enrolled person's configured contact (typically themselves or a designated caregiver). Default off; operator must opt in per enrolled person.
+
+---
+
+## 3. Consequences
+
+### Positive
+
+- Six new HA entities give operators a complete BFLD diagnostic dashboard without leaking identity.
+- Matter exposure is structurally narrow — the cluster-filter implementation cannot accidentally expose identity fields because the type system rejects them.
+- The default ACL template gives operators a working privacy posture out of the box.
+- The federation contract makes it explicit that the hub cannot reconstruct identity even from the union of all node events.
+
+### Negative
+
+- The `identity_risk` HA entity exists only under class 2. Operators who run class 3 deployments cannot see the score even in their own dashboard. This is correct but may surprise care-home installers; documentation must be clear.
+- Three Matter clusters is conservative — some HA users may want the count exposed as a percentage or rate, which Matter does not support natively.
+- HA-blueprint coverage is intentionally small; operators wanting custom automations must work through the YAML surface.
+
+### Neutral
+
+- The federation witness script runs nightly. A short-duration leak between witnesses is possible but bounded — any successful exfiltration of class-1 fields would still need to be reconstructed into identity, which the daily hash rotation breaks.
+
+---
+
+## 4. Alternatives Considered
+
+### Alt 1: Expose `identity_risk` over Matter (Generic Sensor cluster)
+
+Rejected: Matter is a cross-vendor surface; exposing identity-risk there leaks the score to every Matter controller in the home, including third-party hubs the operator may not control. Keep it HA-internal.
+
+### Alt 2: One unified MQTT topic `ruview/<node>/bfld` with JSON payload
+
+Rejected: per-entity topics are the HA-DISCO convention (ADR-115) and let ACLs be field-specific. A unified topic forces an all-or-nothing read policy.
+
+### Alt 3: Federate raw BFI to cognitum-v0 for cross-node analytics
+
+Rejected: violates ADR-120 I1 (raw never leaves the node). Aggregates are sufficient for cross-node analytics; raw centralization is a hard no.
+
+### Alt 4: Default `entity_category: diagnostic = false` for `identity_risk`
+
+Rejected: promoting `identity_risk` to a main-card sensor would surprise operators with an identity-adjacent gauge on their main dashboard. Diagnostic category is the right default.
+
+---
+
+## 5. Acceptance Criteria
+
+- [ ] **AC1**: HA auto-discovery publishes six new entities per node on first connect; HA recognizes all six.
+- [ ] **AC2**: Under privacy class 3, `sensor.<node>_bfld_identity_risk` is absent from the MQTT discovery payload.
+- [ ] **AC3**: `MatterSink::publish` rejects any frame at compile time when the source has `privacy_class < 2`.
+- [ ] **AC4**: The default mosquitto ACL denies `read ruview/+/bfld/identity_risk/state` to the `public` user role.
+- [ ] **AC5**: Three HA blueprints install cleanly into a fresh HA install and trigger their configured actions against a mock BFLD event stream.
+- [ ] **AC6**: The federation-witness script detects an injected class-1 field in a synthetic event and exits non-zero.
+- [ ] **AC7**: Matter occupancy-sensing cluster reports presence within 1 s of an HA `binary_sensor.*_bfld_presence` state change.
+
+---
+
+## 6. References
+
+- ADR-115 (HA-DISCO entity scheme)
+- ADR-116 (`cog-ha-matter` cog packaging)
+- ADR-120 (privacy class enforcement)
+- ADR-121 (identity risk source)
+- ADR-100 (cog packaging spec)
+- Mosquitto ACL reference: https://mosquitto.org/man/mosquitto-conf-5.html
+- Matter spec — Occupancy Sensing cluster (0x0406)
+- Cognitum V0 appliance dashboard: `http://cognitum-v0:9000/`

docs/adr/ADR-123-bfld-capture-path-nexmon-and-esp32.md

@@ -0,0 +1,186 @@
+# ADR-123: BFLD Capture Path — Pi 5 / Nexmon Adapter and ESP32-S3 Feasibility
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-24 |
+| **Deciders** | ruv |
+| **Parent** | [ADR-118](ADR-118-bfld-beamforming-feedback-layer-for-detection.md) |
+| **Relates to** | [ADR-022](ADR-022-multi-bssid-wifi-scanning.md) (multi-BSSID scan), [ADR-028](ADR-028-esp32-capability-audit.md) (capability audit), [ADR-095](ADR-095-rvcsi-edge-rf-sensing-platform.md) (rvCSI), [ADR-096](ADR-096-rvcsi-ffi-crate-layout.md) (rvCSI FFI), [ADR-110](ADR-110-esp32-c6-firmware-extension.md) (C6 firmware), [ADR-119](ADR-119-bfld-frame-format-and-wire-protocol.md) (BfldFrame) |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+ADR-118 declares that BFLD captures BFI from commodity WiFi 5/6 traffic. The question this sub-ADR answers is: **on which hardware, with which adapter, and against which firmware limitations**.
+
+### 1.1 ESP32-S3 BFI capability gap
+
+The ESP32 capability audit (ADR-028) and the ESP32-S3 / C6 firmware (`firmware/esp32-csi-node/`, ADR-110) confirm that the Espressif WiFi API exposes **CSI** capture (`esp_wifi_set_csi_*`) but does not expose **raw 802.11 management-frame capture** in monitor mode for non-self-addressed CBFR reports. The S3 sees the CBFR frames its own AP-link generates (when it acts as a beamformer), but it cannot promiscuously sniff CBFR frames between other STA/AP pairs in the neighborhood.
+
+The C6 (ESP32-C6 with RISC-V + Wi-Fi 6) has a more flexible RF subsystem but the same software-API constraint at the time of writing.
+
+### 1.2 Pi 5 / Nexmon as the production capture host
+
+The rvCSI platform (ADR-095/096) already vendors a Nexmon-based adapter (`rvcsi-adapter-nexmon`) that captures CSI from BCM43455c0 chips (Pi 5 / Pi 4 / Pi 3B+). Nexmon patches the firmware to surface CSI to userspace and **also surface CBFR frames** — the BFI extension is the same code path with a different filter.
+
+cognitum-v0 (Pi 5 in the fleet, per CLAUDE.local.md) is already running Nexmon + the rvCSI runtime. It is the natural BFLD capture host.
+
+### 1.3 What we need from each hardware tier
+
+| Tier | Role | BFI capture | CSI capture | Notes |
+|------|------|-------------|-------------|-------|
+| ESP32-S3 / C6 | Sensing leaf | **no** | yes | Continues providing CSI to the existing pipeline |
+| Pi 5 / Nexmon | BFLD host | **yes** | yes (via Nexmon) | Primary BFLD capture |
+| ruvultra (RTX 5080 + AX210) | Training / dev | yes (via AX210 monitor mode) | yes | Dev capture; not production |
+| cognitum-v0 (Pi 5) | Appliance | **yes** (production) | yes | Production BFLD host |
+
+---
+
+## 2. Decision
+
+### 2.1 Production capture path: Pi 5 / Nexmon
+
+The BFLD production capture path is implemented as a new module in the vendored rvCSI submodule:
+
+```
+vendor/rvcsi/crates/rvcsi-adapter-nexmon/
+└── src/
+    ├── lib.rs
+    ├── csi.rs                  # existing CSI capture
+    └── bfi.rs                  # NEW — CBFR capture, exports BfiCapture
+```
+
+The new `bfi.rs` parses CBFR frames (VHT or HE) from the Nexmon-patched firmware's userspace stream, extracts Φ/ψ angle matrices, and emits a `BfiCapture` struct that feeds the BFLD crate's extractor (ADR-118 §2.1, ADR-119).
+
+The patch lives in the rvcsi submodule (`github.com/ruvnet/rvcsi`) and is shipped as `rvcsi-adapter-nexmon ^0.3.5` to crates.io. The wifi-densepose workspace consumes the published crate (or the submodule path during development).
+
+### 2.2 BFLD crate adapter trait
+
+`wifi-densepose-bfld` defines a `BfiCaptureAdapter` trait:
+
+```rust
+pub trait BfiCaptureAdapter: Send + 'static {
+    type Error: std::error::Error + Send + Sync + 'static;
+    fn capture(&mut self) -> Result<Option<BfiCapture>, Self::Error>;
+    fn capabilities(&self) -> AdapterCapabilities;
+}
+
+pub struct AdapterCapabilities {
+    pub supports_he: bool,           // 802.11ax (Wi-Fi 6)
+    pub supports_160mhz: bool,
+    pub max_n_rx: u8,
+    pub host_kind: HostKind,         // Pi5Nexmon | Ax210Linux | EspS3Local | Mock
+}
+```
+
+Three impls ship initially:
+
+- `NexmonBfiAdapter` — Pi 5 / Nexmon (production)
+- `Ax210BfiAdapter` — Linux + AX210 in monitor mode (dev / training, ruvultra)
+- `MockBfiAdapter` — replay fixture for tests and CI
+
+A future fourth impl (`EspS3LocalAdapter`) is reserved for the day Espressif exposes promiscuous CBFR — it captures only the S3's own AP-link BFI for local self-reporting.
+
+### 2.3 Capture-side privacy boundary
+
+Per ADR-120 I1, raw BFI never leaves the capturing host. The adapter must therefore live on **the same physical box** as the BFLD crate's extractor and privacy gate. The architecture pattern:
+
+```
+[ Pi 5 / cognitum-v0 ]
+├── nexmon firmware (kernel)
+├── rvcsi-adapter-nexmon (userspace, captures BFI)
+├── wifi-densepose-bfld (extracts, scores, gates)
+│       └── privacy_gate → class-2/3 frames only
+└── wifi-densepose-sensing-server (publishes MQTT + Matter)
+```
+
+A network-mode adapter that streams raw BFI from a remote capture host is **explicitly forbidden**. The adapter trait does not include any "remote URL" parameter.
+
+### 2.4 Channel / bandwidth coverage
+
+The Nexmon adapter is configured by the existing `rvcsi-adapter-nexmon` channel-hopping schedule (ADR-095 §3.2). For BFLD it adds:
+
+- Filter for VHT CBFR (action frame, category 21, action 0) and HE CBFR (category 30, action 0).
+- Per-channel BFI session-tracking — the same beamformer/beamformee pair across a channel hop is reconciled by AP MAC + STA MAC.
+
+### 2.5 ESP32-S3 local self-reporting (deferred)
+
+For deployments without a Pi 5 / cognitum-v0 nearby, a degraded BFLD mode runs on the ESP32-S3 itself:
+
+- Captures only its own AP-link CBFR (self-addressed).
+- Computes features over the limited window.
+- Reports a coarsened `presence` + `motion` only — no `identity_risk_score` (insufficient sample diversity).
+- Emits `BfldFrame` at `privacy_class = 2` with a `flags.bit3 = self_only` marker.
+
+This path is implemented in firmware as part of P2 / P3 of the ADR-118 rollout, after the Pi 5 path is stable. Effort is small (firmware path reuses the existing CSI capture loop) but the value is also low until ESP32 firmware exposes promiscuous CBFR — which is a Espressif-IDF roadmap item, not under project control.
+
+### 2.6 Dev path: ruvultra / AX210
+
+For local dev iteration on the Windows / ruvultra box, the AX210 adapter provides a workable capture path on Linux (ruvultra is Ubuntu 6.17 per CLAUDE.local.md). The AX210 supports 802.11ax + monitor mode with the `iwlwifi` driver patches that have landed upstream. This path is for training-data collection and dev testing, not production.
+
+---
+
+## 3. Consequences
+
+### Positive
+
+- BFLD ships as a production-ready surface on cognitum-v0 day one — no new hardware procurement.
+- The adapter-trait design lets new capture paths (AX211, MediaTek Filogic, etc.) slot in without changes to the BFLD crate.
+- The capture-side privacy boundary is structural: there is no remote-capture code path, so a future PR cannot accidentally introduce one.
+- ruvultra's AX210 path unblocks training and dev iteration on Linux without depending on the Pi 5 fleet.
+
+### Negative
+
+- BFLD's full pipeline depends on cognitum-v0 (or another Pi 5 / Nexmon host) being present in the deployment. Operators without a Pi 5 get only the degraded ESP32-S3 self-reporting path (limited utility).
+- Nexmon is a third-party kernel module; tracking upstream patches is ongoing maintenance.
+- The CBFR frame format differs between VHT (802.11ac) and HE (802.11ax); the parser must support both, and any 802.11be (Wi-Fi 7) deployment will require an additional parser path.
+
+### Neutral
+
+- ruvultra dev path uses AX210; the AX210 is not the production NIC, so dev/prod parity is via the fixture replay + the Nexmon adapter on cognitum-v0.
+
+---
+
+## 4. Alternatives Considered
+
+### Alt 1: Centralized capture host streams raw BFI to RuView nodes
+
+Rejected: violates ADR-120 I1 (raw never leaves the capture host). The capture host **is** the BFLD node; there is no separation.
+
+### Alt 2: Wait for Espressif promiscuous CBFR support
+
+Rejected: indefinite timeline outside project control. The Pi 5 / Nexmon path is shippable today.
+
+### Alt 3: Custom Pi 5 firmware fork instead of Nexmon
+
+Rejected: forking BCM firmware is a huge maintenance burden and Nexmon already does what we need.
+
+### Alt 4: Only ship the ESP32-S3 self-reporting path
+
+Rejected: insufficient sample diversity for `identity_risk_score`. The whole point of BFLD is to measure identity leakage; a self-only path cannot do that meaningfully.
+
+---
+
+## 5. Acceptance Criteria
+
+- [ ] **AC1**: `NexmonBfiAdapter` captures ≥ 100 valid CBFR frames per minute from a 2-AP-3-STA test bench on a Pi 5 (cognitum-v0).
+- [ ] **AC2**: VHT (802.11ac) and HE (802.11ax) CBFR frames are both parsed; mixed-PHY captures produce correctly-typed `BfiCapture` outputs.
+- [ ] **AC3**: 20/40/80/160 MHz channel widths are all supported (one fixture each in `tests/`).
+- [ ] **AC4**: `BfiCaptureAdapter` trait has no method accepting a remote URL or socket address.
+- [ ] **AC5**: ESP32-S3 self-only adapter compiles `#[no_std]` and produces a `BfldFrame` with `flags.bit3 = self_only` set, no `identity_risk_score` field.
+- [ ] **AC6**: AX210 adapter on ruvultra captures CBFR for at least one fixture-generating dev session.
+- [ ] **AC7**: Capture loop sustains 10 Hz BFI frame rate on cognitum-v0 without dropping frames over a 10-minute soak test.
+
+---
+
+## 6. References
+
+- ADR-095 / ADR-096 (rvCSI Nexmon adapter)
+- ADR-028 (ESP32 capability audit)
+- ADR-110 (ESP32-C6 firmware)
+- Nexmon BCM43455c0 patches: https://github.com/seemoo-lab/nexmon
+- Wi-BFI: https://arxiv.org/abs/2309.04408
+- IEEE 802.11-2020 §19.3.12 (VHT CBFR), §27.3.11 (HE CBFR)
+- cognitum-v0 fleet entry: `CLAUDE.local.md` (Tailscale fleet table)

docs/adr/ADR-124-rvagent-mcp-ruvector-npm-integration.md

@@ -0,0 +1,466 @@
+# ADR-124: rvagent — MCP (stdio + Streamable HTTP) + ruvector npm/TypeScript library for RuView with ruflo integration
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-24 |
+| **Deciders** | ruv |
+| **Codename** | **SENSE-BRIDGE** — a typed bridge between the RuView sensing stack and the MCP agent ecosystem |
+| **Relates to** | [ADR-055](ADR-055-integrated-sensing-server.md) (sensing-server), [ADR-095](ADR-095-rvcsi-edge-rf-sensing-platform.md) (rvCSI), [ADR-097](ADR-097-adopt-rvcsi-as-ruview-csi-runtime.md) (rvCSI adoption), [ADR-115](ADR-115-home-assistant-integration.md) (HA-DISCO), [ADR-116](ADR-116-cog-ha-matter-seed.md) (Seed cog), [ADR-117](ADR-117-pip-wifi-densepose-modernization.md) (PIP-PHOENIX), [ADR-118](ADR-118-bfld-beamforming-feedback-layer-for-detection.md) (BFLD) |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+### 1.1 The access-layer gap
+
+The RuView / wifi-densepose Rust stack exposes sensing data through three surfaces: a Tokio/Axum HTTP REST API and WebSocket at `wifi-densepose-sensing-server` (ADR-055); an MQTT namespace under `ruview/<node_id>/*` (ADR-115); and an rvCSI edge runtime (ADR-095/096). None of these surfaces speaks Model Context Protocol (MCP).
+
+MCP is the dominant inter-process contract through which AI assistants (Claude, GPT, Codex) invoke external capabilities in 2026. Without an MCP bridge, RuView's sensing primitives are invisible to AI-driven automation workflows. An agent cannot ask "who is in the room?" or "subscribe me to fall alerts" without bespoke HTTP integration code in every consuming agent.
+
+Two concrete user stories that SENSE-BRIDGE resolves:
+
+1. A developer has a Claude Code session and wants to call `vitals.get_heart_rate` from a prompt — today this requires them to write an HTTP fetch, parse JSON, and handle WebSocket reconnect logic; with SENSE-BRIDGE they install `@ruvnet/rvagent` and the tool is available immediately via `claude mcp add rvagent`.
+2. A ruflo-orchestrated multi-agent swarm needs real-world presence data to gate a workflow: SENSE-BRIDGE gives the swarm an MCP tool call with the same `mcp__claude-flow__*` signature pattern already used for all other ruflo tools (CLAUDE.md §Ruflo Automation Primitives).
+
+### 1.2 What rvagent is today
+
+Research of the ruvnet npm registry profile and the ruflo GitHub repository (issue #1689) establishes that **rvagent is not yet a published standalone npm package** as of 2026-05-24. The name "rvagent" appears in the ruflo project exclusively as a WASM artifact (`rvagent_wasm_bg.wasm`, 588 KB) bundled with the RuFlo Web UI (PR #1687). That artifact exports 13 WASM functions including `callMcp`, `executeTool`, `listTools`, `listGalleryTemplates`, `searchGalleryTemplates`, and `loadGalleryTemplate`. It is an in-browser MCP client runner, not a RuView-specific MCP server.
+
+There is no `rvagent` package on the npm registry as of this writing. The npm name is therefore available (Q1 in §8). The package name to register is `@ruvnet/rvagent` (scoped form, reduces name-squatting risk) or `rvagent` (unscoped form, simpler `npx` invocation). This ADR proposes `@ruvnet/rvagent`.
+
+The WASM `callMcp` / `executeTool` surface of the existing ruflo rvagent is the functional model for what the new npm package should expose in TypeScript — but the new package is a **server**, not a client, and its tools are RuView-domain-specific rather than general ruflo-gallery tools.
+
+### 1.3 MCP transport landscape as of 2026-05-24
+
+The MCP specification shipped version `2025-03-26` (Streamable HTTP) and `2025-06-18` (current stable) replacing the legacy `2024-11-05` HTTP+SSE transport. Key facts relevant to this ADR:
+
+- **stdio** remains the recommended local transport. Clients launch the MCP server as a subprocess; the server reads JSON-RPC from stdin and writes to stdout. This is the path `claude mcp add <name> -- npx @ruvnet/rvagent stdio` uses (CLAUDE.md §Quick Setup mirrors this pattern for the claude-flow MCP server).
+- **Streamable HTTP** (colloquially "SSE" in earlier documentation) replaces the deprecated pure-SSE transport. A single HTTP endpoint at e.g. `POST /mcp` accepts JSON-RPC requests and may respond with `Content-Type: text/event-stream` for streaming, or `application/json` for single-turn responses. The server must validate `Origin` headers and bind to `127.0.0.1` by default (MCP spec security requirement).
+- The `@modelcontextprotocol/sdk` npm package (latest stable at time of writing) ships `Server`, `StdioServerTransport`, and `StreamableHTTPServerTransport`. A single `Server` instance can be connected to both transports simultaneously by calling `server.connect(transport)` for each.
+- The legacy `SSEServerTransport` from protocol version `2024-11-05` is deprecated but still ship-able for backwards compatibility with older Claude desktop clients. SENSE-BRIDGE will support it behind an `--legacy-sse` flag for a single release cycle, then remove it.
+
+### 1.4 ruvector npm surface
+
+The `ruvector` npm package (version 0.2.x, latest 0.2.25 as of ~2026-05-01) is a napi-rs WASM/Node.js binding of the RuVector Rust crate. It provides:
+
+- HNSW in-memory vector index (sub-0.5 ms query latency, 50 K+ QPS single-threaded)
+- 50+ attention mechanisms from the RuVector Rust crate
+- FlashAttention-3 SIMD path
+- Graph Neural Network support via `@ruvector/gnn`
+- Full TypeScript types; ships both ESM and CJS
+
+The `ruvector` package is already a dependency in the existing Rust workspace's napi-rs node bindings (`ruvector-node` crate, version 0.1.29 on crates.io). The npm package and the Rust crate are developed in the same repository (`github.com/ruvnet/ruvector`). SENSE-BRIDGE can depend on `ruvector` directly without needing to add new Rust FFI — the vector ops needed (HNSW index of pose keypoints, embedding storage for AETHER person re-ID) are already exposed in the npm package's public surface.
+
+### 1.5 ruflo integration context
+
+The project's `CLAUDE.md` documents the 3-tier model routing (ADR-026) and the `mcp__claude-flow__*` tool namespace. ruflo exposes 314 native MCP tools. SENSE-BRIDGE adds a new domain namespace `mcp__rvagent__*` that represents RuView sensing capabilities, parallel to but separate from the ruflo tools. The boundary is:
+- **ruflo**: agent orchestration, memory, swarm coordination, hooks, task management
+- **rvagent / SENSE-BRIDGE**: RuView-specific sensing — presence, vitals, pose, BFLD, semantic primitives
+
+ruflo can call rvagent tools via the standard MCP tool-call mechanism; rvagent does not depend on ruflo at runtime (but may optionally use ruflo memory namespaces for persistence).
+
+---
+
+## 2. Decision
+
+Ship `@ruvnet/rvagent` as a standalone npm TypeScript library that:
+
+1. Exposes a **dual-transport MCP server** (stdio + Streamable HTTP) wrapping RuView sensing primitives.
+2. Uses `ruvector` (npm) as the vector storage layer for pose embeddings and AETHER-class semantic search, with no reimplementation of vector ops in TypeScript.
+3. Mirrors the Python `wifi_densepose.client.*` surface (ADR-117 P4 — `python/wifi_densepose/client/ws.py`, `mqtt.py`, `primitives.py`) in TypeScript for parity across runtimes.
+4. Integrates as a ruflo plugin via the `ruflo-plugin` manifest convention, exposing tools in the `mcp__rvagent__*` namespace callable by ruflo agents.
+5. Ships strict TypeScript source, ESM + CJS dual output, Node.js 20+ minimum, type definitions in the tarball, zero bundler required.
+
+---
+
+## 3. Transport comparison
+
+| Dimension | stdio | Streamable HTTP |
+|---|---|---|
+| **Launch mechanism** | Client forks `npx @ruvnet/rvagent stdio` as subprocess | Client POSTs to `http://host:port/mcp` |
+| **Primary use case** | Claude Code, Cursor, IDE plugins — local developer flow | Remote agents, ruflo swarms on separate hosts, browser-based dashboards |
+| **Connection state** | One client per server process; process dies with client | Multiple clients per server process; stateless or session-keyed |
+| **Streaming** | Newline-delimited JSON on stdout | `text/event-stream` response body |
+| **Auth** | None needed (process-level isolation) | Bearer token or mTLS required (per MCP spec security rules) |
+| **RuView sensing-server connectivity** | Server process holds a single WebSocket + MQTT connection to sensing-server; results forwarded to client via JSON-RPC | Server process holds a connection pool; session affinity via `Mcp-Session-Id` header |
+| **Tailscale fleet** | Works on local node only | Works across Tailscale fleet (cognitum-v0, cognitum-seed-1, ruvultra) with DNS name |
+| **Origin validation** | Not applicable | Required; server MUST reject cross-origin requests unless CORS policy explicitly permits |
+| **Resumability** | Not applicable (process is co-located) | Optional `Last-Event-ID` header for stream resumption after reconnect |
+| **Logging** | stderr — captured by Claude Code, displayed in conversation | Structured JSON to stdout, shipped to ruflo observability (ADR-observability) |
+| **Process lifecycle** | Ephemeral — exits when Claude Code session ends | Long-lived — suitable for always-on sensing daemon |
+| **When to choose** | Single developer, local ESP32 (COM9), quick scripting | Fleet deployment, multi-agent ruflo swarms, web dashboards |
+
+Both transports are served by the same `Server` instance from `@modelcontextprotocol/sdk`. The only difference is the `Transport` class passed to `server.connect()`.
+
+---
+
+## 4. MCP tool catalog
+
+All tools are in the `ruview` namespace. Input schemas below are TypeScript interface stubs; output types mirror the Python dataclasses from `python/wifi_densepose/client/ws.py` and `primitives.py`.
+
+### 4.1 Tool catalog table
+
+| Tool name | Input interface | Return shape | RuView surface wrapped |
+|---|---|---|---|
+| `ruview.presence.now` | `{ node_id?: string }` | `{ node_id: string; present: boolean; n_persons: number; confidence: number; timestamp_ms: number }` | `EdgeVitalsMessage.presence` / `EdgeVitalsMessage.n_persons` (ws.py:74-88) |
+| `ruview.vitals.get_breathing` | `{ node_id?: string; window_s?: number }` | `{ node_id: string; breathing_rate_bpm: number \| null; confidence: number; timestamp_ms: number }` | `EdgeVitalsMessage.breathing_rate_bpm` (ws.py:82) |
+| `ruview.vitals.get_heart_rate` | `{ node_id?: string; window_s?: number }` | `{ node_id: string; heartrate_bpm: number \| null; confidence: number; timestamp_ms: number }` | `EdgeVitalsMessage.heartrate_bpm` (ws.py:83) |
+| `ruview.vitals.get_all` | `{ node_id?: string }` | `EdgeVitalsResult` (all fields of `EdgeVitalsMessage` except `raw`) | Full `EdgeVitalsMessage` (ws.py:74-88) |
+| `ruview.pose.latest` | `{ node_id?: string }` | `{ node_id: string; persons: PosePersonResult[]; confidence: number; timestamp_ms: number }` | `PoseDataMessage` (ws.py:91-98) |
+| `ruview.pose.subscribe` | `{ node_id?: string; duration_s: number; callback_url?: string }` | `{ subscription_id: string; started_at: number; expires_at: number }` | WS stream — streams `PoseDataMessage` events for `duration_s` seconds |
+| `ruview.primitives.get` | `{ node_id?: string; primitive: SemanticPrimitiveKind }` | `SemanticPrimitiveResult` | `SemanticPrimitive` + `SemanticPrimitiveEvent` (primitives.py:36-75) |
+| `ruview.primitives.list_active` | `{ node_id?: string }` | `{ primitives: SemanticPrimitiveResult[] }` | All 10 ADR-115 semantic primitives (primitives.py:36-45) |
+| `ruview.primitives.subscribe` | `{ node_id?: string; primitive?: SemanticPrimitiveKind; duration_s: number }` | `{ subscription_id: string; expires_at: number }` | MQTT topic `homeassistant/+/wifi_densepose_<node>/+/state` (mqtt.py:8-9) |
+| `ruview.bfld.last_scan` | `{ node_id?: string }` | `{ node_id: string; identity_risk_score: number; privacy_class: number; n_frames: number; timestamp_ms: number }` | MQTT `ruview/<node_id>/bfld/scan_result` (ADR-118/ADR-121) |
+| `ruview.bfld.subscribe` | `{ node_id?: string; duration_s: number }` | `{ subscription_id: string; expires_at: number }` | MQTT `ruview/<node_id>/bfld/*` |
+| `ruview.node.list` | `{ }` | `{ nodes: NodeInfo[] }` | MQTT discovery + REST `/api/nodes` |
+| `ruview.node.status` | `{ node_id: string }` | `NodeStatusResult` | REST `/api/status` or MQTT will-message |
+| `ruview.vector.search_pose` | `{ query_embedding: number[]; k?: number; node_id?: string }` | `{ matches: VectorMatch[] }` | `ruvector` HNSW index of stored pose keypoints (ADR-016) |
+| `ruview.vector.store_pose` | `{ pose: PosePersonResult; node_id: string }` | `{ vector_id: string }` | `ruvector` HNSW upsert |
+
+### 4.1a Policy / governance tools (RUVIEW-POLICY)
+
+**Added 2026-05-24 per maintainer review.** Once tools can answer "who is in the room?", the library is no longer middleware — it is environmental intelligence infrastructure, and that changes the trust model. Every sensing tool above MUST route through this policy layer before returning data. The layer is enforced server-side in the MCP server, not client-side, so a malicious or misconfigured agent cannot bypass it.
+
+| Tool name | Input interface | Return shape | Purpose |
+|---|---|---|---|
+| `ruview.policy.can_access_vitals` | `{ agent_id: string; node_id: string; vital: "breathing" \| "heart_rate" \| "all" }` | `{ allowed: boolean; reason: string; expires_at?: number }` | Gate every `ruview.vitals.*` call. Default-deny when no policy is registered for the (agent_id, node_id) pair. |
+| `ruview.policy.can_query_presence` | `{ agent_id: string; scope: "node" \| "fleet"; node_id?: string; zone?: string }` | `{ allowed: boolean; reason: string; redactions?: string[] }` | Fleet-scope presence queries (e.g. "is anyone home?") require explicit scope grant; node-scope is the safer default. |
+| `ruview.policy.can_subscribe` | `{ agent_id: string; topic: string; duration_s: number }` | `{ allowed: boolean; max_duration_s: number; reason: string }` | Subscriptions can be denied entirely or capped to a shorter duration than requested (e.g. agent asks for 1 h, policy returns 5 min). |
+| `ruview.policy.redact_identity_fields` | `{ payload: Record<string, unknown>; agent_id: string }` | `{ payload: Record<string, unknown>; redacted_fields: string[] }` | Server-side redaction pass applied to every tool return value. Strips `sta_mac`, raw BFLD matrices, and any keypoint set marked `privacy_class >= 2` per ADR-120. Called automatically by the MCP server; agents never see the un-redacted payload. |
+| `ruview.policy.audit_log` | `{ agent_id?: string; since_ts?: number }` | `{ events: PolicyAuditEvent[] }` | Returns the policy-decision audit trail for a maintainer-tier agent. Other agents are denied even if they hold valid tool grants — auditability of the auditor is itself a policy decision. |
+
+Policy storage is a local JSON file (`~/.config/rvagent/policy.json` on Unix, `%APPDATA%\rvagent\policy.json` on Windows) backed by a CLI editor (`npx @ruvnet/rvagent policy grant ...`). Schema mirrors the ADR-010 claims-based authorization model where it exists in the Rust workspace, but the npm library keeps a self-contained store so SENSE-BRIDGE can ship without the full claims infrastructure on day one.
+
+**Default policy when no file exists**: deny `ruview.vitals.*` and `ruview.policy.audit_log`; allow `ruview.presence.now` and `ruview.node.list` (coarse, non-biometric); allow `ruview.primitives.list_active` with `redact_identity_fields` applied. This is the "explore safely" default so a new install can sanity-check the agent is wired up without leaking biometric data.
+
+### 4.2 MCP resource catalog
+
+Resources provide read-only data that can be embedded in the LLM context window.
+
+| Resource URI | Description | MIME type |
+|---|---|---|
+| `ruview://nodes` | JSON list of all discovered nodes (IP, firmware version, capabilities) | `application/json` |
+| `ruview://nodes/{node_id}/config` | Node configuration (channel, MAC filter, privacy class) | `application/json` |
+| `ruview://nodes/{node_id}/vitals/latest` | Latest `EdgeVitalsMessage` for the node | `application/json` |
+| `ruview://nodes/{node_id}/pose/latest` | Latest `PoseDataMessage` | `application/json` |
+| `ruview://nodes/{node_id}/bfld/latest` | Latest BFLD scan result | `application/json` |
+| `ruview://primitives/schema` | JSON schema for the 10 semantic primitives (ADR-115) | `application/json` |
+| `ruview://fleet/topology` | Tailscale-fleet topology (host, TS IP, role) — sourced from local CLAUDE.local.md fleet table | `text/markdown` |
+
+### 4.3 MCP prompt templates
+
+| Prompt name | Description | Arguments |
+|---|---|---|
+| `ruview.diagnose_node` | Walk the user through node connectivity check, firmware version, and live vitals stream | `{ node_id: string }` |
+| `ruview.presence_report` | Summarize presence + persons over a time window in natural language | `{ node_id: string; window_s: number }` |
+| `ruview.vitals_alert_rule` | Generate an HA automation YAML fragment for a vitals threshold alert | `{ primitive: SemanticPrimitiveKind; threshold: number }` |
+| `ruview.bfld_privacy_audit` | Produce a compliance-ready privacy audit paragraph from the last BFLD scan | `{ node_id: string }` |
+
+---
+
+## 5. Dependency graph
+
+```
+@ruvnet/rvagent (npm / TypeScript)
+├── @modelcontextprotocol/sdk    ^1.x  — MCP Server, StdioServerTransport,
+│                                        StreamableHTTPServerTransport, McpError
+├── ruvector                     ^0.2  — HNSW vector index, embedding storage
+│                                        (napi-rs native bindings; NO reimplementation)
+├── zod                          ^3.x  — Input schema validation for all tool inputs
+├── ws                           ^8.x  — WebSocket client to sensing-server /ws/sensing
+│   └── @types/ws
+├── mqtt                         ^5.x  — MQTT client for ruview/<node_id>/* topics
+│                                        (replaces paho-mqtt; mqtt.js is the npm standard)
+├── node-fetch / undici           —     — HTTP client for REST endpoints on sensing-server
+└── tsup                         (dev) — ESM + CJS dual build
+
+Runtime back-ends (NOT bundled — must be reachable at runtime):
+├── wifi-densepose-sensing-server (Rust binary)
+│   ├── REST API   :3000  /api/*
+│   ├── WebSocket  :8765  /ws/sensing
+│   └── MQTT       via local broker or ruview/<node_id>/*
+├── MQTT broker    (mosquitto or broker at cognitum-v0:1883)
+└── ruvector HNSW index (in-process via napi-rs; no separate service)
+```
+
+Key integration boundary: **ruvector is purely in-process**. The HNSW index lives in the `@ruvnet/rvagent` Node.js process memory, populated from pose keypoints received over the sensing-server WebSocket. There is no separate vector service. This matches the architecture of `wifi-densepose-ruvector` (Rust crate in the workspace) which is also in-process.
+
+---
+
+## 6. Python client surface parity table
+
+The Python client in `python/wifi_densepose/client/` (ADR-117 P4) is the canonical reference for the TS surface. TypeScript should mirror it so users see the same domain model across runtimes.
+
+| Python class / enum | File | TypeScript equivalent in @ruvnet/rvagent |
+|---|---|---|
+| `SensingMessage` | `ws.py:54-60` | `interface SensingMessage` |
+| `ConnectionEstablishedMessage` | `ws.py:63-70` | `interface ConnectionEstablishedMessage extends SensingMessage` |
+| `EdgeVitalsMessage` | `ws.py:74-88` | `interface EdgeVitalsMessage extends SensingMessage` |
+| `PoseDataMessage` | `ws.py:91-98` | `interface PoseDataMessage extends SensingMessage` |
+| `SensingClient` (asyncio) | `ws.py:160` | `class SensingClient` (EventEmitter-based, async iterator) |
+| `SemanticPrimitive` (enum) | `primitives.py:36-45` | `enum SemanticPrimitive` |
+| `SemanticPrimitiveEvent` | `primitives.py:60-75` | `interface SemanticPrimitiveEvent` |
+| `SemanticPrimitiveListener` | `primitives.py:84-155` | `class SemanticPrimitiveListener` |
+| `RuViewMqttClient` | `mqtt.py:56` | `class RuViewMqttClient` (wraps mqtt.js `MqttClient`) |
+| `_topic_matches` | `mqtt.py:237-257` | `function topicMatches(pattern, topic)` |
+
+---
+
+## 7. Implementation plan
+
+```
+P1 ──► P2 ──► P3 ──► P4 ──► P5
+npm    MCP    MCP    ruvector  npm
+scaffold stdio  SSE   integration  publish + ruflo bridge
+```
+
+### P1 — Scaffold (1 week)
+
+**Goal**: an installable npm package skeleton that compiles and passes CI.
+
+- [ ] Create `npm/rvagent/` directory in the repo (mirrors `python/wifi_densepose/`). Do not add to `v2/` Rust workspace.
+- [ ] `package.json`: name `@ruvnet/rvagent`, version `0.1.0-alpha.1`, `type: "module"`, exports map with `./package.json`, `.` (ESM + CJS), `./stdio`, `./http`.
+- [ ] `tsconfig.json`: `strict: true`, `target: ES2022`, `module: NodeNext`, `moduleResolution: NodeNext`.
+- [ ] `tsup.config.ts`: dual `esm + cjs` build, `dts: true`.
+- [ ] Add `@modelcontextprotocol/sdk`, `ruvector`, `zod`, `ws`, `mqtt`, `tsup` as deps / devDeps.
+- [ ] CI job: `npm ci && npm run build` on `ubuntu-latest` with Node 20, 22.
+- [ ] Stub `src/index.ts` that exports package version string. Import succeeds.
+
+### P2 — MCP stdio server (2 weeks)
+
+**Goal**: `npx @ruvnet/rvagent stdio` connects to a running sensing-server over WebSocket + MQTT and exposes the tool catalog from §4.1 over stdio transport.
+
+- [ ] `src/server.ts` — create `McpServer` instance, register all tools from §4.1 with Zod input schemas. Tools that require a live sensing-server connection return a structured error `{ error: "SENSING_SERVER_UNAVAILABLE" }` rather than throwing, so the LLM gets useful context.
+- [ ] `src/transports/stdio.ts` — `StdioServerTransport` entrypoint. Reads `RUVIEW_HOST` and `RUVIEW_PORT` env vars (default `localhost:8765` WS, `localhost:3000` REST, `localhost:1883` MQTT).
+- [ ] `src/sensing/ws-client.ts` — TypeScript port of `python/wifi_densepose/client/ws.py`. Async generator yielding `SensingMessage` variants. Reconnect with exponential back-off (the Python client explicitly does not reconnect — the TS one should, because the stdio process is long-lived).
+- [ ] `src/sensing/mqtt-client.ts` — TypeScript port of `python/wifi_densepose/client/mqtt.py` using `mqtt.js ^5`. Per-pattern callbacks, `topicMatches` wildcard helper.
+- [ ] `src/sensing/primitives.ts` — `SemanticPrimitive` enum + `SemanticPrimitiveListener`. Mirror of `primitives.py`.
+- [ ] Tool implementations for the 5 highest-priority tools: `ruview.presence.now`, `ruview.vitals.get_all`, `ruview.pose.latest`, `ruview.primitives.get`, `ruview.node.list`.
+- [ ] Resource implementations: `ruview://nodes`, `ruview://nodes/{node_id}/vitals/latest`.
+- [ ] Integration test: spin up `sensing-server --mock-frames` in Docker; assert `npx @ruvnet/rvagent stdio` receives a `ruview.vitals.get_all` tool call response with non-null `breathing_rate_bpm`.
+- [ ] `claude mcp add rvagent -- npx @ruvnet/rvagent stdio` smoke-test (manual).
+
+### P3 — MCP Streamable HTTP server (2 weeks)
+
+**Goal**: `npx @ruvnet/rvagent serve --port 3100` starts an HTTP server that serves the full MCP tool catalog over Streamable HTTP (and optionally legacy SSE for backwards compat).
+
+- [ ] `src/transports/http.ts` — `StreamableHTTPServerTransport` backed by an Express 5 or Hono app (Hono preferred for lightweight edge deployability).
+- [ ] Session management: issue `Mcp-Session-Id` UUIDs on `POST /mcp` initialize; reject subsequent requests without session header with HTTP 400.
+- [ ] Origin validation: configurable `RUVIEW_ALLOWED_ORIGINS` env var; default reject all cross-origin requests (MCP spec security requirement §Streamable HTTP §Security Warning).
+- [ ] Auth: optional `RUVIEW_BEARER_TOKEN` env var. If set, require `Authorization: Bearer <token>` on all requests. This mirrors `v2/crates/wifi-densepose-sensing-server/src/bearer_auth.rs`.
+- [ ] Legacy SSE compatibility: `--legacy-sse` flag mounts the deprecated `SSEServerTransport` on `/sse` + `/message` for Claude Desktop clients on protocol version `2024-11-05`. Document this as a single-release compat shim.
+- [ ] Remaining tools from §4.1: `ruview.vitals.get_breathing`, `ruview.vitals.get_heart_rate`, `ruview.pose.subscribe`, `ruview.primitives.list_active`, `ruview.primitives.subscribe`, `ruview.bfld.last_scan`, `ruview.bfld.subscribe`, `ruview.node.status`.
+- [ ] Prompt template registrations from §4.3.
+- [ ] Integration test: `curl -X POST http://localhost:3100/mcp` with a `tools/list` request; assert the response lists all 15 tools.
+- [ ] Docker Compose entry for local fleet testing: `rvagent` HTTP container talking to `sensing-server` and `mosquitto` containers.
+
+### P4 — ruvector integration (1 week)
+
+**Goal**: `ruview.vector.search_pose` and `ruview.vector.store_pose` tools work end-to-end with a live HNSW index.
+
+- [ ] `src/vector/index.ts` — wrapper around `ruvector` napi-rs bindings. Initialise an HNSW index at server startup; expose `store(id, embedding)` and `search(embedding, k)`.
+- [ ] Pose-to-embedding pipeline: when a `PoseDataMessage` arrives from the WS client, extract the 17-keypoint array, normalise to `[-1, 1]` per keypoint coordinate, flatten to a 34-dimensional float vector, store in HNSW with `node_id:person_index:timestamp_ms` as the ID.
+- [ ] `src/vector/aether.ts` — AETHER-style cross-viewpoint search (ADR-024): given a pose embedding query, search HNSW index across all stored poses and return the top-k matches with their source node IDs. This enables cross-node person re-identification via the MCP tool without any network call between nodes.
+- [ ] Verify that the `ruvector` napi-rs binary loads correctly on Node 20 linux/x86_64, macos/arm64, and windows/amd64. Document any platform-specific caveats.
+- [ ] Index persistence: optional `RUVIEW_VECTOR_DB_PATH` env var. If set, persist the HNSW index to disk using `ruvector`'s serialise API. If unset, in-memory only (default for stdio transport).
+- [ ] Integration test: feed 100 synthetic pose frames with known clustering, assert `ruview.vector.search_pose` retrieves nearest neighbours with recall >0.9.
+
+### P5 — npm publish + ruflo bridge (1 week)
+
+**Goal**: `npm install @ruvnet/rvagent` works for consumers; ruflo agents can call `mcp__rvagent__*` tools through the standard claude-flow MCP registration.
+
+- [ ] Populate `package.json` with `publishConfig: { access: "public" }`, `engines: { node: ">=20" }`, `files` whitelist (`dist/`, `src/`, `README.md`).
+- [ ] Publish `@ruvnet/rvagent@0.1.0-alpha.1` to npm under the `@ruvnet` scope.
+- [ ] ruflo plugin manifest: create `.claude/plugins/rvagent/plugin.json` following the ruflo `plugin/` convention in the ruflo repo. The manifest registers the HTTP transport URL (configurable) and maps `mcp__rvagent__*` tool calls to the rvagent MCP server.
+- [ ] `ruview` skill in `.claude/agents/` (CLAUDE.md §Available Agents): an agent description that documents the rvagent tool namespace for ruflo orchestration.
+- [ ] `claude mcp add rvagent -- npx @ruvnet/rvagent stdio` tested against claude-flow MCP server on the local dev machine (ruvzen host on CLAUDE.local.md fleet).
+- [ ] Document the fleet deployment pattern: run `npx @ruvnet/rvagent serve` on cognitum-v0 (Tailscale IP 100.77.59.83, port 50060 range to avoid conflict with existing services; see CLAUDE.local.md services table). Register the URL as a remote MCP server in `.claude/settings.json`.
+- [ ] Publish announcement: link from project README (`docs/` link, not root README per CLAUDE.md rules).
+
+---
+
+## 8. Open questions
+
+**Q1. npm package name availability**
+`rvagent` (unscoped) does not appear in the npm registry as of 2026-05-24 based on search results. `@ruvnet/rvagent` is definitely available (the `@ruvnet` scope is owned by ruvnet per the npm profile page). Should the package be published unscoped (`rvagent`) for simpler `npx rvagent stdio` invocation, or scoped (`@ruvnet/rvagent`) for namespace clarity? The decision should be made before P5 because the npm name is permanent.
+
+**Q2. ruvector binary compatibility on Windows**
+The `ruvector` npm package is a napi-rs native addon. The project's primary development machine (ruvzen) is Windows 11. It is not confirmed whether `ruvector@0.2.25` ships a prebuilt Windows binary in its npm tarball or requires a Rust toolchain to compile. If no Windows binary is shipped, developers on ruvzen would need the Rust toolchain installed to use `@ruvnet/rvagent`. This must be confirmed before P5 by running `npm install ruvector` on ruvzen.
+
+**Q3. ruvector TypeScript API stability**
+ruvector `0.2.x` is not a 1.0 release. The HNSW insert and search API surface may change between minor versions. SENSE-BRIDGE P4 should pin `ruvector@~0.2.25` and document the version constraint explicitly. The question is whether ruvector publishes a changelog with breaking-change notices.
+
+**Q4. MCP tool call latency budget — RESOLVED**
+Raw sensing frequency ≠ agent interaction frequency. If a tool call ever waits on the next CSI frame, agent orchestration latency becomes physically coupled to RF acquisition jitter, which is unacceptable at scale. The library MUST take option (a) — return from a continuous local cache:
+
+1. **Continuous local cache**: on startup the rvagent MCP server opens one WebSocket + one MQTT subscription per configured sensing-server endpoint and ingests every frame into an in-memory `Map<node_id, EdgeVitalsMessage>` (plus parallel maps for `PoseDataMessage` and BFLD). Cache hits return in <1 ms regardless of CSI frame rate.
+2. **Event-driven invalidation**: the cache entry's `received_at` timestamp is bumped on every received frame. The cache itself is never purged on a timer — only overwritten when fresh data lands, so a node that went quiet still serves its last-known value.
+3. **Bounded freshness windows**: each tool accepts an optional `max_age_ms` argument (default 1000). If the cached `received_at` is older than `max_age_ms`, the tool returns `{ value: null, reason: "stale", last_seen_ms: N, threshold_ms: max_age_ms }` rather than blocking. The agent decides whether to accept the staleness, raise to the user, or escalate to a `ruview.node.status` health check.
+
+This pattern is required because P3's Streamable HTTP transport may serve dozens of concurrent agent sessions — see Q8. A shared cache + per-session freshness contract scales; per-session WS connections do not.
+
+P2 must implement this cache; P3 must verify that fanning the same cache to N concurrent HTTP sessions still maintains <1 ms median tool-call latency under load.
+
+**Q5. Subscription tool lifetime management**
+Tools `ruview.pose.subscribe`, `ruview.primitives.subscribe`, and `ruview.bfld.subscribe` return a `subscription_id` and stream events. In the stdio transport there is one client, so this is straightforward. In the HTTP transport with multiple sessions, subscription state must be tracked per `Mcp-Session-Id`. When a session expires (HTTP 404) or is deleted via HTTP DELETE, the subscription must be cleaned up. The lifecycle mechanism is not fully designed — this is a known gap that P3 must close.
+
+**Q6. AETHER embedding dimension**
+The ADR proposes a 34-dimensional pose embedding (17 keypoints × 2 coordinates). The actual AETHER embedding model (ADR-024) uses a learned contrastive encoder, not raw keypoints. If the AETHER ONNX model is available in the Rust workspace at P4 time, the embedding should use it. If not, the raw-keypoint approach is a reasonable placeholder. The question is whether `wifi-densepose-nn` exposes the AETHER encoder in a form that can be called from Node.js without bundling libtorch in the npm package.
+
+**Q7. ruflo plugin manifest format**
+The ruflo plugin convention (`plugin/` directory in the ruflo repo) is not fully documented in a public spec as of this writing. The manifest format was inferred from the `ruflo-plugins.gif` directory listing and referenced in issue #952. Before P5, the actual plugin manifest schema must be confirmed from the ruflo repo so SENSE-BRIDGE does not ship an incompatible manifest.
+
+**Q8. MQTT vs direct WebSocket for Streamable HTTP transport**
+In the stdio transport, rvagent holds a single WebSocket + single MQTT connection to the sensing-server. In the Streamable HTTP transport (potentially serving dozens of agent sessions), maintaining one connection per session is not scalable. The recommended pattern is a single shared connection per (sensing-server endpoint), multiplexed to all sessions. The implementation complexity of this fan-out is non-trivial and is not fully specified here.
+
+**Q9. Legacy SSE deprecation timeline**
+The MCP `2024-11-05` SSE transport is deprecated in the current spec but Claude Desktop versions prior to the spec `2025-03-26` update still use it. SENSE-BRIDGE proposes `--legacy-sse` for one release cycle. The question is which specific Claude Desktop version drops legacy SSE support, and whether any of the active fleet nodes (cognitum-v0, cognitum-seed-1) run a Claude Desktop version old enough to need it.
+
+**Q10. Node.js vs Bun runtime**
+The ruflo monorepo uses `bun` as the primary runtime (per `bunfig.toml` in `v3/`). Should `@ruvnet/rvagent` also support Bun? Bun's napi-rs compatibility for native addons like `ruvector` is improving but not guaranteed for 0.2.x. The P1 CI should test on Node 20 first; Bun support can be declared as a stretch goal for P5.
+
+---
+
+## 9. Alternatives considered
+
+### Alt-A — Python-only client (extend ADR-117 with MCP bindings)
+
+Add `wifi_densepose.mcp` as a P6 module in the PIP-PHOENIX wheel (ADR-117). The Python MCP SDK (`mcp[cli]`) supports both stdio and HTTP transports and the PyO3 bindings give direct access to the sensing types.
+
+**Rejected because**: Python is not the dominant runtime for MCP server hosting in 2026 — the ecosystem tooling (Claude Desktop, Claude Code `mcp add`, ruflo) is TypeScript-first. A Python MCP server requires the full pip install including PyO3 bindings, which is a heavier install than `npx @ruvnet/rvagent stdio`. The ruflo plugin format is TypeScript. ADR-117 is already sizeable; adding MCP to it conflates two distinct concerns (Python developer library vs. AI agent interface). Python MCP remains a viable future addition (Q10 for a future ADR) but is not the right first-ship target.
+
+### Alt-B — Pure WebSocket/REST client without MCP framing
+
+Ship a TypeScript client library `@ruvnet/ruview-client` that wraps the sensing-server WebSocket and REST API without the MCP layer. Consumers who want MCP integration would wrap it themselves.
+
+**Rejected because**: it solves the connectivity problem but not the agent integration problem. Without MCP framing, Claude Code and ruflo agents cannot discover or call RuView capabilities through the standard `mcp__*` namespace — they would need custom prompt injection or bespoke tool definitions per agent. The whole value proposition of this ADR is that a single `claude mcp add rvagent` command makes all RuView primitives discoverable to any MCP-capable AI assistant. Splitting the library forces every consumer to re-add the MCP layer.
+
+### Alt-C — Embed MCP server inside the existing wifi-densepose-sensing-server Rust binary
+
+Add an MCP endpoint to the existing Axum server in `v2/crates/wifi-densepose-sensing-server/` (`v2/crates/wifi-densepose-sensing-server/src/main.rs`). This would use the `rmcp` Rust crate (Model Context Protocol SDK for Rust) and expose MCP over an additional port.
+
+**Rejected because**: (a) it couples the release cycle of the npm-hosted MCP interface to the firmware/Rust release cycle, which are on separate cadences — a new MCP tool that merely adds a JSON field should not require a firmware rebuild; (b) the ruflo plugin ecosystem is TypeScript and expects npm packages, not Rust binaries; (c) the ruvector vector layer is a napi-rs Node.js native module and cannot be called directly from a Rust process without going through the napi-rs server-side API, adding unnecessary complexity; (d) the sensing-server binary is already 15-30 MB stripped — adding the MCP endpoint and its JSON-RPC machinery would further bloat it. This alternative is worth revisiting if the Rust `rmcp` crate matures and the vector layer migrates fully to native Rust, but it is not appropriate for the first implementation.
+
+### Alt-D — Wrapping the existing ruflo WASM rvagent in a RuView shim
+
+The ruflo WASM rvagent (`rvagent_wasm_bg.wasm`) already exports `callMcp` / `executeTool` / `listTools`. One could define a RuView shim that registers custom tools into the ruflo WASM rvagent gallery.
+
+**Rejected because**: the ruflo WASM rvagent is an in-browser MCP *client* runner for the ruflo gallery, not a general-purpose MCP server that can expose sensing data. Its 13 exported functions are focused on template management and ruflo-gallery operations. Patching sensing tools into a browser WASM module is the wrong architecture for a server-side sensing bridge. The naming overlap is a reason to publish the new package promptly and clearly document the distinction.
+
+---
+
+## 10. Compatibility
+
+### 10.1 Backwards compatibility with ADR-117 (PIP-PHOENIX) Python client
+
+SENSE-BRIDGE does not replace the Python client. Both can coexist:
+- Python integrators use `from wifi_densepose.client import SensingClient` (ADR-117).
+- TypeScript / MCP integrators use `import { SensingClient } from "@ruvnet/rvagent"`.
+- MCP-capable AI assistants use `claude mcp add rvagent -- npx @ruvnet/rvagent stdio`.
+
+All three talk to the same sensing-server backend; there is no shared state between the Python and TypeScript clients beyond what the sensing-server itself maintains.
+
+### 10.2 Sensing-server API contract
+
+SENSE-BRIDGE depends on the sensing-server WebSocket protocol documented in `v2/crates/wifi-densepose-sensing-server/src/main.rs` (referenced in `python/wifi_densepose/client/ws.py:6-13`). The three message types (`connection_established`, `pose_data`, `edge_vitals`) are stable across v0.7.x releases. If the sensing-server adds new message types, SENSE-BRIDGE follows the same pattern as the Python client: unknown `type` values yield a plain `SensingMessage` rather than an error, ensuring forward compatibility.
+
+### 10.3 MCP protocol version
+
+SENSE-BRIDGE targets MCP protocol version `2025-06-18` (current stable). It will include backwards compatibility with `2025-03-26` (Streamable HTTP without session management) and optionally `2024-11-05` (legacy SSE via `--legacy-sse` flag). Protocol version `2025-06-18` requires the `MCP-Protocol-Version` header on HTTP requests; SENSE-BRIDGE validates this per spec.
+
+### 10.4 Node.js version
+
+Minimum Node.js 20 LTS. Node 22 is supported and recommended for production (active LTS as of 2026). The `ruvector` napi-rs bindings must be confirmed compatible with both (Q2). Node 18 is EOL and explicitly not supported.
+
+### 10.5 MQTT broker compatibility
+
+SENSE-BRIDGE uses `mqtt.js ^5` which implements MQTT 3.1.1 and MQTT 5.0. The `mosquitto` local broker (CLAUDE.local.md §Local mosquitto) and cognitum-v0's MQTT stack (CLAUDE.local.md fleet table) are both compatible. TLS mode is optional via `RUVIEW_MQTT_TLS=1` env var.
+
+---
+
+## 11. Consequences
+
+### 11.1 Positive consequences
+
+- Any MCP-capable AI assistant can query RuView presence, vitals, pose, and BFLD data with zero custom integration code after `claude mcp add rvagent`.
+- ruflo multi-agent swarms gain first-class access to real-world sensing data, enabling swarms to gate decisions on physical events (fall detected → page caregiver workflow).
+- The TypeScript surface provides a second reference implementation of the sensing-server client protocol alongside the Python client (ADR-117), validating the protocol design against two independent consumers.
+- The ruvector HNSW integration enables cross-node person re-identification entirely within the rvagent process — no additional network calls between sensing nodes.
+
+### 11.2 Negative consequences / risks
+
+| Risk | Likelihood | Severity | Mitigation |
+|---|---|---|---|
+| **ruvector napi-rs not building on Windows** | Medium | Medium | Confirm in P1 CI; if binaries not prebuilt, document requirement of Rust toolchain on Windows |
+| **MCP protocol churn** — spec updated twice in 2025; another update in 2026 possible | Medium | Low | Pin `@modelcontextprotocol/sdk` to a minor range; wrap SDK calls behind an internal `transport.ts` abstraction so changes are isolated |
+| **Subscription lifecycle bugs** — zombie subscriptions if session cleanup is missed | High | Medium | Implement per-session resource registry with TTL; all subscriptions auto-expire after `duration_s` even if session is not explicitly deleted |
+| **sensing-server WS disconnect** — stdio process dies if not reconnecting | Low | High | Implement exponential back-off reconnect in `ws-client.ts`; emit `{ error: "RECONNECTING" }` tool responses during gap |
+| **npm name collision** — `rvagent` taken by another publisher before P5 | Low | Medium | Publish `@ruvnet/rvagent` scoped; use that name throughout |
+| **ruflo plugin manifest incompatibility** — format not publicly specced | Medium | Medium | Confirm format in P5 preparation; use the minimal required fields only |
+| **Sensing-tool surface becomes a surveillance API** — "who is in the room" is a privacy-charged primitive | High | High | RUVIEW-POLICY layer (§4.1a) gates every sensing call; default-deny for biometric tools; redaction applied server-side so agents cannot opt out |
+
+### 11.3 Strategic implication: ambient-sensing normalization layer
+
+The MCP tool catalog in §4 is RuView-WiFi-CSI-specific today. The shape of the catalog — `presence.now`, `vitals.get_*`, `pose.latest`, `primitives.*`, `bfld.*` — is **modality-agnostic at the semantic layer**: the same tools could be backed by any sensing modality that produces the same questions.
+
+If the project later adds BLE, mmWave (e.g. the ESP32-C6 + Seeed MR60BHA2 already on COM4 per CLAUDE.md), LiDAR, thermal, camera, radar, or UWB inputs, the rvagent MCP surface stays the same. Only the source-multiplexer behind `cache.ts` changes — it now ingests from multiple modalities and resolves conflicts (e.g. WiFi CSI says "presence: true" but mmWave says "presence: false" → fusion policy decides; this is the kind of decision the RUVIEW-POLICY layer can also gate).
+
+This positions the npm package not as "a WiFi client" but as the **semantic-environment API**: agents ask "is anyone here?" without caring which radio answered. The competitive landscape (Aqara FP2, ESPHome LD2410) exposes raw telemetry; SENSE-BRIDGE exposes environmental cognition.
+
+The follow-on ADR (call it ADR-13x — RUVIEW-FUSION) would formalize the per-modality adapter contract. It is intentionally out of scope for ADR-124 — this ADR ships the WiFi-CSI path only — but the tool catalog and policy layer are designed to absorb additional modalities without API churn.
+
+---
+
+## 12. Acceptance criteria
+
+The following must all pass before ADR-124 is considered Accepted:
+
+- [ ] `npm install @ruvnet/rvagent` succeeds on Node 20/22, linux/x86_64, macos/arm64, windows/amd64 with no Rust toolchain required (ruvector prebuilts must ship).
+- [ ] `npx @ruvnet/rvagent stdio` starts and responds to a `tools/list` JSON-RPC request with the 15 tools from §4.1.
+- [ ] `npx @ruvnet/rvagent serve --port 3100` starts; `curl -X POST http://localhost:3100/mcp -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'` returns the tool list.
+- [ ] `ruview.vitals.get_all` with a running `sensing-server --mock-frames` returns `breathing_rate_bpm` and `heartrate_bpm` values within 5 seconds.
+- [ ] `ruview.vector.store_pose` followed by `ruview.vector.search_pose` with the same embedding returns the stored pose as the top-1 match.
+- [ ] `claude mcp add rvagent -- npx @ruvnet/rvagent stdio` followed by `/mcp` in a Claude Code session shows the rvagent tools listed.
+- [ ] All MCP tool input schemas are validated via Zod; an invalid input returns an MCP `INVALID_PARAMS` error, not an unhandled exception.
+- [ ] TypeScript strict-mode compilation (`tsc --noEmit`) passes with zero errors.
+- [ ] `npm run build` produces both ESM (`dist/esm/`) and CJS (`dist/cjs/`) outputs with `.d.ts` type declarations.
+- [ ] The published npm tarball size is `≤ 10 MB` including the ruvector napi-rs binary for the current platform.
+
+---
+
+## 13. References
+
+### This repo
+
+- `python/wifi_densepose/client/ws.py` — WebSocket client (ADR-117 P4): connection protocol, message types `connection_established`, `pose_data`, `edge_vitals`
+- `python/wifi_densepose/client/mqtt.py` — MQTT client (ADR-117 P4): topic namespaces, wildcard matching
+- `python/wifi_densepose/client/primitives.py` — Semantic primitive enum and listener (ADR-117 P4): 10 ADR-115 primitives
+- `v2/crates/wifi-densepose-sensing-server/src/main.rs` — Axum server: REST API, WebSocket endpoint `/ws/sensing`
+- `v2/crates/wifi-densepose-sensing-server/src/bearer_auth.rs` — Bearer token auth pattern for HTTP server
+- `v2/crates/wifi-densepose-sensing-server/src/semantic/` — 10 semantic primitive modules
+- `v2/crates/wifi-densepose-sensing-server/src/mqtt/` — MQTT publisher, discovery, topic routing
+- `docs/adr/ADR-055-integrated-sensing-server.md` — Sensing-server architectural context
+- `docs/adr/ADR-095-rvcsi-edge-rf-sensing-platform.md` — rvCSI edge runtime
+- `docs/adr/ADR-115-home-assistant-integration.md` — MQTT topic structure, 10 semantic primitives, 21 HA entities
+- `docs/adr/ADR-117-pip-wifi-densepose-modernization.md` — PIP-PHOENIX: Python client and PyO3 bindings (the Python-runtime parallel to this ADR)
+- `docs/adr/ADR-118-bfld-beamforming-feedback-layer-for-detection.md` — BFLD crate: `BfldEvent` MQTT topics
+- `docs/adr/ADR-024-contrastive-csi-embedding-model.md` — AETHER person re-ID embeddings
+- `docs/adr/ADR-016-ruvector-integration.md` — RuVector integration in the Rust workspace
+- `CLAUDE.md` — Project config: 3-tier model routing (ADR-026), ruflo MCP tools, `mcp__claude-flow__*` namespace
+- `CLAUDE.local.md` — Fleet table: Tailscale hosts, cognitum-v0 services table, local mosquitto pattern
+
+### External
+
+- [Model Context Protocol specification 2025-06-18](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports) — Transports: stdio and Streamable HTTP
+- [MCP TypeScript SDK — github.com/modelcontextprotocol/typescript-sdk](https://github.com/modelcontextprotocol/typescript-sdk) — `Server`, `StdioServerTransport`, `StreamableHTTPServerTransport`
+- [@modelcontextprotocol/sdk on npm](https://www.npmjs.com/package/@modelcontextprotocol/sdk)
+- [ruvector on npm](https://www.npmjs.com/package/ruvector) — v0.2.25, napi-rs HNSW vector DB
+- [ruvnet npm profile](https://www.npmjs.com/~ruvnet) — confirms `@ruvnet` scope ownership
+- [RuVector GitHub](https://github.com/ruvnet/ruvector) — Rust source + napi-rs node bindings
+- [ruflo (claude-flow) GitHub](https://github.com/ruvnet/ruflo) — ruflo plugin manifest convention, `v3/` structure
+- [ruflo issue #1689](https://github.com/ruvnet/ruflo/issues/1689) — documents existing rvagent WASM exports (`callMcp`, `executeTool`, `listTools`) and distinguishes them from this ADR's server-side rvagent
+- [Why MCP Deprecated SSE — fka.dev](https://blog.fka.dev/blog/2025-06-06-why-mcp-deprecated-sse-and-go-with-streamable-http/) — rationale for Streamable HTTP over legacy SSE
+- [MCP TypeScript SDK dual-transport patterns — dev.to](https://dev.to/zoricic/understanding-mcp-server-transports-stdio-sse-and-http-streamable-5b1p)

docs/adr/ADR-125-ruview-apple-home-native-hap-bridge.md

@@ -0,0 +1,285 @@
+# ADR-125: RuView ↔ Apple Home native HAP bridge — direct HomeKit accessory advertisement from the Seed
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-25 |
+| **Deciders** | ruv |
+| **Codename** | **APPLE-FABRIC** — RuView speaks HomeKit directly so Apple HomePod / Apple TV act as the discovery + automation surface with zero Home-Assistant middle layer |
+| **Relates to** | [ADR-115](ADR-115-home-assistant-integration.md) (HA-DISCO MQTT publisher), [ADR-116](ADR-116-cog-ha-matter-seed.md) (cog-ha-matter §P7 left HAP/Matter as a feature-flag stub), [ADR-118](ADR-118-bfld-beamforming-feedback-layer-for-detection.md) (BFLD presence + identity-risk events), [ADR-122](ADR-122-bfld-ruview-ha-matter-exposure.md) (BFLD HA/Matter exposure) |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+### 1.1 The misunderstanding worth correcting once
+
+A naive integration tries to **push** data to a HomePod — open a socket, send a JSON-RPC, call an MQTT topic on `homepod.local`. Apple intentionally does not expose that surface. The HomePod is not an endpoint; it is the **Home Hub + Matter Controller + HomeKit Controller + Siri endpoint** for the Apple Home ecosystem on the LAN. It **discovers** accessories that advertise themselves on the local network via Bonjour/mDNS using the HomeKit Accessory Protocol (HAP) or Matter.
+
+The correct direction of flow is therefore:
+
+```text
+RuView / Seed
+      ↓                  (advertise HAP / Matter accessory on LAN)
+HomeKit / Matter accessory
+      ↓                  (mDNS discovery)
+HomePod
+      ↓                  (forwards to Apple Home automation graph)
+Apple Home ecosystem (iPhone, Watch, Mac, Siri, automations)
+```
+
+### 1.2 What we ship today and where it stops
+
+ADR-115 ships an **MQTT auto-discovery publisher** that talks to Home Assistant. ADR-116's `cog-ha-matter` Cognitum cog wraps that publisher into a Seed-installable artifact with mDNS, an embedded rumqttd broker, RuVector-backed thresholds, and an Ed25519 witness chain. ADR-122 explicitly extends the same publisher with the BFLD presence / identity-risk / Soul-Match topics so a Home Assistant install sees them as auto-discovered entities. The current path to HomePod therefore runs:
+
+```text
+RuView sensing-server ──► cog-ha-matter (MQTT HA-DISCO + HA-MIND)
+                              ↓
+                       Home Assistant broker
+                              ↓
+                       Home Assistant HomeKit Bridge add-on
+                              ↓
+                              HomePod
+```
+
+This works and the auto-discovery is real, but it introduces a hard dependency: an operator must run Home Assistant, install its HomeKit Bridge integration, and pair the bridge in the Apple Home app. The Seed alone does not appear in Apple Home.
+
+ADR-116 §P7 anticipated this — the `cog-ha-matter` `Cargo.toml` already carries a `matter = []` feature stub with the comment "matter-rs is added in P7; intentionally absent in P1 to keep the dep surface small until the SDK choice is validated." This ADR closes that box.
+
+### 1.3 Why now
+
+Three forces line up in 2026-05:
+
+1. **The BFLD privacy gate (ADR-118 / 120 / 121) is shipped.** Class-2 and class-3 frames are the only ones eligible to cross the Matter boundary (ADR-122 §2.4). Without that gate we could not safely expose RuView signals to a consumer ecosystem. With it, every Anonymous / Restricted event is safe to advertise as a HomeKit sensor.
+2. **`@ruvnet/rvagent` (ADR-124) is on npm.** The MCP surface that lets agents query RuView is live. A first-class Apple-Home presence widens RuView's reach from "agents that speak MCP" to "anyone with an iPhone and a HomePod" — the consumer wedge.
+3. **The Cognitum Seed Docker image now bundles `cog-ha-matter`** (this branch's `Dockerfile.rust` change, see #794) — the runtime where a HAP advertiser would live is finally a single-image deployment.
+
+### 1.4 Strategic framing
+
+The combination is asymmetric:
+
+| Layer | RuView contributes | Apple Home contributes |
+|-------|---------------------|------------------------|
+| Sensing | Passive RF presence, breathing, heart rate, fall risk, BFLD identity-risk, through-wall occupancy, longitudinal wellness | (none — Apple has no native RF sensing surface) |
+| Adoption | (limited — researcher-grade hardware today) | iPhone, Watch, Mac, HomePod, Apple TV installed base; consumer trust; voice; on-device intelligence |
+| UX | (utility CLI + a Web UI) | Home app, Siri, automation engine, notifications, accessibility |
+| Trust | Ed25519 witness chain, privacy class gate, local-first | Apple HomeKit local pairing, end-to-end encrypted, no cloud requirement |
+
+RuView supplies the **invisible cognition layer** Apple cannot provide on its own; Apple supplies the **distribution and UX** that an open sensing stack cannot bootstrap. Direct HAP integration removes the only structural barrier between those two layers — Home Assistant as a mandatory intermediary.
+
+---
+
+## 2. Decision
+
+Ship a **native HomeKit / Matter accessory** in the Seed runtime so a freshly-imaged Cognitum Seed appears in the Apple Home app under `Add Accessory → More Options` with **zero Home-Assistant dependency**.
+
+Concretely:
+
+1. Add a `hap-accessory` workspace component that advertises a set of HomeKit characteristics over mDNS using HAP-1.1 (HomeKit Accessory Protocol).
+2. The component subscribes to `wifi-densepose-sensing-server`'s WebSocket / BFLD `MqttEvent` stream and maps each privacy-class-2/3 event onto a HomeKit characteristic update.
+3. The same Docker image that ships `sensing-server` and `cog-ha-matter` ships the new advertiser as a third entrypoint:
+
+```bash
+docker run --network host ruvnet/wifi-densepose:latest hap-accessory --privacy-mode
+```
+
+`--network host` (or a macvlan bridge) is required because HAP pairing depends on the accessory and the controller seeing each other's mDNS broadcasts on the same L2 segment — same constraint Home Assistant's HomeKit Bridge has.
+
+### 2.1 Two implementation tracks (decided here together; ship 2.1.a first)
+
+#### 2.1.a — **HAP-python sidecar** (fastest to ship, lands first)
+
+Add a tiny Python entrypoint `bridges/hap-python/ruview_hap.py` using the well-maintained [`HAP-python`](https://github.com/ikalchev/HAP-python) library. The Dockerfile gets a thin Python runtime stage; the entrypoint script polls `sensing-server` over HTTP and pushes characteristic updates into the HAP loop.
+
+```python
+# bridges/hap-python/ruview_hap.py (≈80 LOC)
+from pyhap.accessory import Accessory
+from pyhap.accessory_driver import AccessoryDriver
+from pyhap.const import CATEGORY_SENSOR
+import urllib.request, json, threading, time
+
+SENSING_URL = "http://127.0.0.1:3000/api/v1"
+
+class RuViewSensor(Accessory):
+    category = CATEGORY_SENSOR
+
+    def __init__(self, *args, **kwargs):
+        super().__init__(*args, **kwargs)
+        s_motion = self.add_preload_service('MotionSensor')
+        self.c_motion = s_motion.configure_char('MotionDetected')
+        s_occ = self.add_preload_service('OccupancySensor')
+        self.c_occ = s_occ.configure_char('OccupancyDetected')
+        s_temp = self.add_preload_service('TemperatureSensor')
+        self.c_temp = s_temp.configure_char('CurrentTemperature')
+        threading.Thread(target=self._poll, daemon=True).start()
+
+    def _poll(self):
+        while True:
+            try:
+                v = json.loads(urllib.request.urlopen(f"{SENSING_URL}/vitals").read())
+                self.c_motion.set_value(bool(v.get("motion_present")))
+                self.c_occ.set_value(int(bool(v.get("occupancy"))))
+                if "ambient_temp_c" in v:
+                    self.c_temp.set_value(v["ambient_temp_c"])
+            except Exception:
+                pass
+            time.sleep(1.0)
+
+driver = AccessoryDriver(port=51826)
+driver.add_accessory(accessory=RuViewSensor(driver, 'RuView Sense'))
+driver.start()
+```
+
+Pairing flow on the operator's iPhone:
+
+1. Open Apple Home → `Add Accessory` → `More Options`
+2. Tap `RuView Sense` (appears via mDNS automatically)
+3. Enter the setup code shown in `docker logs` (or pinned in env)
+4. Done — Siri can say "Hey Siri, is anyone in the living room?"
+
+Replace the `motion_present` / `occupancy` mappings progressively as RuView capabilities mature: BFLD class-2 `presence` event → `OccupancyDetected`; BFLD class-3 `identity_risk_score > threshold` → `SecuritySystemCurrentState`; `breathing_present` → `OccupancyDetected` (sleep room); `fall_risk` → a programmable switch that fires an Apple Home automation.
+
+Acceptance criteria for 2.1.a:
+
+- A1: `docker run ... hap-accessory --privacy-mode` advertises an `_hap._tcp` service that the HomePod sees within 30s (`dns-sd -B _hap._tcp local.` on a peer Mac shows `RuView Sense`).
+- A2: Pairing from Apple Home succeeds and the entity appears in the Home app under the configured room.
+- A3: `MotionDetected` flips within 2 s of an actual RF presence detection from a calibrated ESP32 source (`CSI_SOURCE=esp32`).
+- A4: Restarting the container preserves the pairing (HAP state persisted under `/var/lib/ruview-hap/`).
+- A5: Privacy: the entrypoint refuses to launch without `--privacy-mode` when `RUVIEW_BFLD_PRIVACY_CLASS` is unset, matching the structural invariant I1 (Raw BFI never exits the node — ADR-118 §2.2).
+
+#### 2.1.b — **Rust-native HAP** (single binary, closes ADR-116 P7)
+
+Wire one of the maintained Rust HAP crates into `cog-ha-matter` so the Python sidecar can be removed. Candidate crates:
+
+- [`hap`](https://crates.io/crates/hap) (Sebastian Schmidt) — last published 0.1.0-pre.16, MIT, active in 2024, supports HAP-1.1, has examples for `MotionSensor`, `LightBulb`, `OccupancySensor`. **First choice.**
+- [`accessory-server`](https://crates.io/crates/accessory-server) — narrower scope, fewer services
+- A future `matter-rs` crate from project-chip — once stable (CHIP SDK Rust bindings are still emerging in 2026-05)
+
+The `matter = []` feature stub in `cog-ha-matter/Cargo.toml` (added in ADR-116 P1) becomes:
+
+```toml
+[features]
+default = []
+mqtt = ["dep:rumqttc"]
+matter = ["dep:hap"]          # ADR-125 §2.1.b
+```
+
+with a runtime subcommand `cog-ha-matter --mode hap` that mirrors the Python advertiser's accessory set. Single binary, no Python interpreter in the image, matches the all-Rust ethos of the Cognitum Seed (ADR-116 §1.4).
+
+### 2.1.c — **Topology: one HAP bridge, N child accessories** (decided)
+
+The advertiser publishes a **single HAP bridge** (`RuView Sense`) that owns N child accessories — one per logical sensor surface (presence-bedroom, presence-office, vitals-bedroom, semantic-events, …). Operators pair the bridge once; child accessories appear automatically and can be re-assigned to rooms in the Apple Home app.
+
+The alternative — N independent accessories each advertised separately — was rejected. It forces operators to pair RuView once per room (`RuView Bedroom`, `RuView Office`, `RuView Wellness`, `RuView Presence`, …), which becomes messy after the second or third room, and diverges from how every reference HomeKit accessory in the Home app behaves (a Hue bridge with bulbs, an Eve Energy bridge, etc.). Single pairing also makes container restart / re-image trivial — one persisted pairing key, not N.
+
+### 2.1.d — **Identity-risk mapping: semantic events, not probabilistic surveillance** (decided)
+
+`identity_risk_score` is a continuous 0..1 confidence from the BFLD identity-features pipeline (ADR-121 §2.6). It must NOT cross the HomeKit boundary as a raw value, and must NOT be wired to `SecuritySystemCurrentState`. Apple-Home users read security-system state as **"intruder detected"** — exposing a probability there turns RuView into surveillance UX with all the false-positive blame that entails.
+
+Instead, the bridge exposes **thresholded semantic events** that read like ambient awareness, not threat detection:
+
+| Semantic event | HomeKit primitive | Trigger (illustrative) |
+|----------------|--------------------|-------------------------|
+| `Unknown Presence` | `MotionSensor` (programmable; stateful) | BFLD class-2 presence + no matching SoulMatch oracle hit (ADR-121 §2.6) for > 30 s |
+| `Unexpected Occupancy` | `OccupancySensor` (programmable) | Occupancy in a room outside its operator-defined "expected schedule" window |
+| `Unrecognized Activity Pattern` | Programmable `Switch` (stateful, momentary) | BFLD longitudinal drift gate (ADR-118 §2.3 / ADR-122 §2.7) fires Reject or Recalibrate |
+
+What stays internal:
+
+- Raw `identity_risk_score` (numeric 0..1) — never published
+- Soul-Signature match probability — never published
+- `rf_signature_hash` — never published (already enforced by ADR-118 §2.5 / ADR-122 §2.4 — this is the structural invariant restated at the HAP boundary)
+
+The naming is the contract. "Unknown Presence" is *who's-here-and-it's-fine-but-worth-noting*; an end user will write an automation ("turn on the porch light when Unknown Presence is detected after 9pm") without ever thinking it accuses anyone of being an intruder. That semantic framing is the difference between RuView becoming the calm-tech ambient substrate Apple Home needs vs. another paranoid surveillance widget.
+
+This is the part of the ADR that determines whether RuView's HomeKit story ages well or generates the wrong kind of headlines.
+
+### 2.2 What we DO NOT do in 2.1.a or 2.1.b
+
+- **No Matter (CHIP) controller code.** Matter is the long-term play but its SDK in Rust is not yet stable and the certificate provisioning is heavy. HAP-1.1 over Bonjour gives 95% of the UX for 10% of the complexity, today.
+- **No direct connection to the HomePod.** As the framing in §1.1 makes explicit, RuView never opens a socket to the HomePod. It advertises; the HomePod discovers.
+- **No iCloud account binding.** HAP pairing is local-network-only by design — RuView gets adoption without ever touching Apple ID, which is a privacy story we keep cleanly.
+- **No Class-0 (`Raw`) BFI exposure.** Structural invariant I1 (ADR-118 §2.2) holds. Only privacy-class-2 (Anonymous) and class-3 (Restricted) frames may be mapped onto HomeKit characteristics. The advertiser refuses to start in any other mode.
+
+### 2.3 Sequencing
+
+1. **P1** (this ADR-125 + 1 PR) — HAP-python sidecar (§2.1.a) lands as a separate entrypoint in the same Docker image. AC A1–A5 are gates.
+2. **P2** (follow-up PR after operator feedback from 5+ Apple Home pairings) — Rust-native HAP (§2.1.b). Replaces P1; P1's `bridges/hap-python/` becomes an archived reference implementation.
+3. **P3** (when matter-rs stabilizes) — Matter Controller path (still RuView-as-accessory, but using the Matter clusters rather than HAP-1.1 services). The Cognitum Cog gains a Matter QR code; pairing flow widens to "any Matter-capable controller, not just Apple."
+
+---
+
+## 3. Consequences
+
+### 3.1 Wins
+
+- **Direct discoverability on Apple Home.** A Seed in the kitchen appears as `RuView Sense` in the Home app within seconds of `docker run`. No HA, no MQTT broker, no Home-Assistant HomeKit Bridge add-on.
+- **Siri natively answers RuView questions.** "Hey Siri, is anyone in the kitchen?" — the question reaches the HomeKit characteristic without any custom skill or HA template sensor.
+- **Apple-Home automations gain ambient triggers** RuView already produces (presence, breathing, fall, identity-risk) for free — they become first-class automation triggers in the Home app's UI.
+- **Strategically corrects RuView's distribution problem.** The Apple Home installed base is the largest consumer surface for HomeKit-grade accessories. RuView's sensing IP becomes addressable to that base without an SDK port.
+- **Closes ADR-116 §P7** — the long-flagged matter / HAP gap is now scheduled, not deferred indefinitely.
+
+### 3.2 Costs
+
+- **Python runtime in the Docker image (only for 2.1.a, until 2.1.b lands).** Adds ~30 MB to the runtime layer. Mitigation: P2 removes it; P1 isolates the Python dep in a side-stage so the sensing-server / cog-ha-matter layers stay clean.
+- **Network-mode constraint.** HAP pairing needs the controller and accessory on the same L2 segment (mDNS broadcasts). Operators who run RuView in a container behind a NAT/bridge need `--network host` or a macvlan — same constraint HA's HomeKit Bridge has, but worth documenting.
+- **Pairing state persistence.** HAP-python stores pairing data in a local file; that state must survive container restarts. Volume-mount `/var/lib/ruview-hap/` to a persistent location.
+
+### 3.3 Risks
+
+- **HAP-python maintenance.** The library is community-maintained; if it goes stale, P2 (Rust-native) absorbs the risk. 2.1.a is explicitly a stepping stone, not a long-term commitment.
+- **Apple's evolving requirements.** HomeKit Accessory Certification is required to put a HAP logo on hardware, not to ship a software accessory that pairs locally. RuView's container deployment is squarely in the "uncertified developer accessory" lane, which Apple explicitly permits for local pairing. Worth restating in the operator README.
+- **Privacy-class enforcement at the bridge boundary.** A bug that lets a class-0 BFI frame's data influence a HAP characteristic update would violate I1. Mitigation: the bridge consumes only the BFLD `MqttEvent` stream (which is already gated by `PrivacyGate` per ADR-120), never raw BFI; tests assert this in the same style as ADR-122 §4.3.
+
+### 3.4 Reversibility
+
+The advertiser is a separate entrypoint — pulling it out is `docker run` without the `hap-accessory` first-arg, identical to today's behavior. Zero impact on `sensing-server` and `cog-ha-matter` operations.
+
+---
+
+## 4. Acceptance test (P1 / §2.1.a)
+
+```bash
+# 1. Start a sensing server (simulated source so the test runs anywhere)
+docker run -d --name rs -p 3000:3000 -e CSI_SOURCE=simulated \
+    ruvnet/wifi-densepose:latest
+
+# 2. Launch the HAP advertiser sidecar in privacy mode
+docker run -d --name hap --network host \
+    -v /var/lib/ruview-hap:/var/lib/ruview-hap \
+    -e RUVIEW_BFLD_PRIVACY_CLASS=2 \
+    ruvnet/wifi-densepose:latest hap-accessory --privacy-mode
+
+# 3. From a Mac on the same LAN: should see RuView Sense as HAP
+dns-sd -B _hap._tcp local.   # expect: "RuView Sense" within 30 s
+
+# 4. From iPhone Home app: Add Accessory → More Options → RuView Sense
+#    Enter setup code from `docker logs hap`
+#    Expect: pairing completes, entity appears in selected Room
+
+# 5. Cycle the container; re-open Home app: entity is still paired
+docker restart hap
+# Expect: no re-pairing prompt; characteristic updates resume
+```
+
+---
+
+## 5. Open questions
+
+Two questions from the original draft were resolved during review (§2.1.c and §2.1.d). Genuinely-open questions that follow-up PRs will close:
+
+- **Setup-code derivation.** Derived deterministically from the Seed's Ed25519 witness key (so reinstalls re-use the same code, operator never re-enters), or random per launch (slightly better security, worse UX on container restarts)? Leaning deterministic + witness-key-derived; verify against Apple's HomeKit Accessory Protocol §5.6.5 (setup-code uniqueness) before committing.
+- **ESP32 / Cognitum-Seed-class hardware as a direct HAP advertiser** (not via the host appliance). The current decision parks the bridge on the host runtime; a future ADR can evaluate whether an ESP32-S3 with 8MB flash has enough headroom to run HAP-1.1 directly, which would remove the host appliance from the path entirely for single-room deployments.
+
+---
+
+## 6. References
+
+- ADR-115 — Home-Assistant integration (HA-DISCO MQTT publisher)
+- ADR-116 — `cog-ha-matter` Seed cog (this is where the `matter` feature stub lives)
+- ADR-118 — BFLD beamforming-feedback layer (privacy gate + class invariants)
+- ADR-122 — BFLD RuView HA/Matter exposure (current MQTT-based bridge that this ADR's HAP-native path complements)
+- HomeKit Accessory Protocol Specification (Non-Commercial Version), Apple — https://developer.apple.com/apple-home/
+- HAP-python — https://github.com/ikalchev/HAP-python
+- `hap` (Rust) — https://crates.io/crates/hap

docs/adr/ADR-126-ruview-native-ha-port-master.md

@@ -0,0 +1,362 @@
+# ADR-126: HOMECORE — Native Rust + WASM + TypeScript port of Home Assistant
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-25 |
+| **Deciders** | ruv |
+| **Codename** | **HOMECORE** — native hub, RuView-first, WASM-safe, semantically aware |
+| **Relates to** | [ADR-115](ADR-115-home-assistant-integration.md) (HA-DISCO), [ADR-116](ADR-116-cog-ha-matter-seed.md) (HA-COG), [ADR-117](ADR-117-pip-wifi-densepose-modernization.md) (PIP-PHOENIX), [ADR-118](ADR-118-bfld-beamforming-feedback-layer-for-detection.md) (BFLD), [ADR-124](ADR-124-rvagent-mcp-ruvector-npm-integration.md) (SENSE-BRIDGE), [ADR-125](ADR-125-ruview-apple-home-native-hap-bridge.md) (APPLE-FABRIC) |
+| **Tracking issue** | TBD |
+| **Sub-ADRs** | ADR-127 through ADR-134 |
+
+---
+
+## 1. Context
+
+### 1.1 Strategic position in 2026
+
+Home Assistant (HA) is the dominant open-source home automation hub with more than 500,000 active installs (ADR-115 §1.2 competitive scan). Every prior RuView integration decision has been made with HA as a given constraint: ADR-115 built an MQTT auto-discovery publisher to fit inside HA, ADR-116 packaged it as a Cognitum Seed cog, ADR-122 extended it with BFLD presence events, and ADR-125 layered a native HAP bridge on top of the same stack.
+
+This approach yields functioning integrations, but it positions RuView permanently as a **guest in someone else's hub**. The architectural limits of Python HA are not just cosmetic:
+
+| Limit | Impact on RuView's roadmap |
+|---|---|
+| **Single-process Python GIL** | CSI DSP pipeline, BFLD analysis, and ruvector semantic search cannot run concurrently inside the HA process; they must run as external services connected over MQTT or WebSocket, introducing a round-trip on every sensor update |
+| **Startup time (15–30 s on a Pi 5)** | The Cognitum Seed appliance restarts firmware-update-by-firmware-update; a 30 s hub startup on every OTA cycle is user-visible latency |
+| **Memory footprint (300 MB+ idle)** | On a Pi 5 with 8 GB this is tolerable; on a Pi Zero 2 W or an embedded board with 512 MB it precludes co-location with the sensing stack |
+| **No WASM safety boundary for integrations** | HA's 2,000+ community integrations are Python modules loaded directly into the HA process — one buggy integration can crash the hub or read arbitrary memory |
+| **Recorder is structural only** | SQLite + InfluxDB store state history as rows; there is no semantic search. "Show me when the porch light correlated with the bedroom CSI anomaly last week" requires manual SQL |
+| **Voice assistant is additive** | Assist (`homeassistant/components/assist_pipeline/`) was added in 2022–2023 and is well-designed, but intent matching is keyword-based, not embedding-based; ruflo LLM pipelines cannot natively plug in |
+| **Frontend is a 5 MB Lit-element bundle** | The dashboard compiles to ~5 MB of JavaScript; on low-bandwidth appliance UIs or Progressive-Web-App installs, this is perceptible load time |
+
+These are not HA's failures — they are Python architectural realities. For a generic home automation hub they are acceptable. For a hub where the core value proposition is **real-time RF sensing, AI-augmented automation, and edge-native deployment on constrained hardware**, they are ceilings.
+
+### 1.2 The opportunity
+
+Three recent ADR shipments create the inflection point:
+
+1. **ADR-117 (PIP-PHOENIX)** — `wifi-densepose==2.0.0a1` + `ruview==2.0.0a1` on PyPI as PyO3/maturin wheels, providing a Python developer surface over the Rust sensing core.
+2. **ADR-118 (BFLD)** — a complete beamforming feedback capture and privacy-risk scoring layer, proving that RuView's sensing stack can be a compliance instrument, not just a sensor.
+3. **ADR-124 (SENSE-BRIDGE)** — `@ruvnet/rvagent` on npm as a dual-transport MCP server, proving that the sensing stack can be expressed as a first-class AI-agent tool surface.
+
+The gap that remains: there is no hub that treats all of these as **native first-class features** rather than bolt-on integrations. HOMECORE fills that gap by porting the HA data model and API surface to Rust, replacing HA's Python internals with the RuView Rust crates, and wrapping community integrations in WASM sandboxes.
+
+### 1.3 What this ADR is *not*
+
+- Not a fork of the Python HA codebase. HOMECORE is a **clean-room Rust implementation** of HA's public API contracts and data model, not a line-by-line port.
+- Not a replacement of the existing sensing stack. `v2/crates/wifi-densepose-*` remain authoritative.
+- Not a deprecation of ADR-115/116/117/124/125. Those integrations continue to work with Python HA installs. HOMECORE is an additional deployment target, not a replacement mandate.
+- Not a Matter SDK full-implementation. ADR-125 handles Matter; HOMECORE consumes the Matter bridge via the existing `cog-ha-matter` surface.
+- Not a target for this quarter's sprint. HOMECORE is a multi-quarter initiative. This master ADR and its sub-ADRs define the architecture; implementation begins in P1.
+
+---
+
+## 2. Decision
+
+Build **HOMECORE**: a native Rust + WASM + TypeScript implementation of the Home Assistant hub contract, integrated with the RuView sensing platform, the ruflo agent toolchain, and the ruvector vector layer.
+
+HOMECORE is wire-compatible with HA's REST and WebSocket APIs so that existing HA-native clients (the iOS/Android Home Assistant companion apps, HACS, Nabu Casa Cloud, and the HA voice satellite stack) operate without modification against a HOMECORE instance.
+
+HOMECORE is NOT a drop-in replacement on day one. The compatibility contract is phased (§6). The architecture is designed so that clients that work with HA today work with HOMECORE P3+.
+
+### 2.1 Codename rationale
+
+**HOMECORE** — the `core` of HA reimplemented at native speed, with the sensing stack at the center rather than at the periphery.
+
+---
+
+## 3. Architecture overview
+
+```
+┌──────────────────────────────────────────────────────────────┐
+│                     HOMECORE process                          │
+│                                                               │
+│  ┌─────────────┐  ┌──────────────┐  ┌───────────────────┐  │
+│  │  homecore   │  │  homecore-   │  │  homecore-        │  │
+│  │  state      │  │  automation  │  │  recorder         │  │
+│  │  machine    │  │  engine      │  │  (SQLite +        │  │
+│  │  (ADR-127)  │  │  (ADR-129)   │  │  ruvector)        │  │
+│  └──────┬──────┘  └──────┬───────┘  │  (ADR-132)        │  │
+│         │                │          └───────────────────┘  │
+│  ┌──────▼──────────────────────────────────┐               │
+│  │              Event Bus (Tokio broadcast) │               │
+│  └──────┬──────────────────────────────────┘               │
+│         │                                                    │
+│  ┌──────▼──────────────────────────────────┐               │
+│  │     homecore-rest-websocket-api (ADR-130)│               │
+│  │     Axum server — HA wire-compat API     │               │
+│  └──────────────────────────────────────────┘               │
+│                                                               │
+│  ┌──────────────┐  ┌──────────────────────────────────────┐ │
+│  │ Integration  │  │  homecore-assist-ruflo (ADR-133)      │ │
+│  │ Plugin System│  │  ruflo agent orchestration            │ │
+│  │ (ADR-128)    │  │  ruvector intent embeddings           │ │
+│  │ WASM sandbox │  │  Wyoming protocol edge               │ │
+│  └──────────────┘  └──────────────────────────────────────┘ │
+│                                                               │
+│  ┌──────────────────────────────────────────────────────┐   │
+│  │  RuView sensing core (wifi-densepose-sensing-server) │   │
+│  │  CSI → presence / vitals / pose / BFLD / semantic    │   │
+│  └──────────────────────────────────────────────────────┘   │
+└──────────────────────────────────────────────────────────────┘
+          │ HA-compatible REST + WebSocket
+          ▼
+┌──────────────────────────┐
+│ homecore-frontend-ts-wasm │  (ADR-131)
+│ TypeScript + Rust→WASM   │
+│ SharedWorker state sync  │
+└──────────────────────────┘
+```
+
+The HOMECORE process is a single Tokio-based async Rust binary. The state machine and event bus are the authoritative core (ADR-127). Integrations run in WASM sandboxes that communicate with the core via a defined ABI (ADR-128). The automation engine runs Rust-native trigger evaluation with a WASM expression evaluator for templates (ADR-129). The REST/WebSocket API layer is Axum-based and wire-compatible with HA (ADR-130). The frontend is TypeScript with the state machine compiled to WASM running in a SharedWorker (ADR-131). Historical state is stored in SQLite with ruvector for semantic search (ADR-132). Voice/text assistance uses ruflo agent orchestration (ADR-133).
+
+---
+
+## 4. Series map
+
+| ADR | Codename | Scope | Critical path? | Estimated P5-completion |
+|---|---|---|---|---|
+| **ADR-127** | HOMECORE-CORE | Rust state machine, entity registry, event bus, service registry (`homecore` crate) | **Yes — all others depend on it** | Q3 2026 |
+| **ADR-128** | HOMECORE-PLUGINS | WASM integration plugin system, cog substrate, manifest schema, hot-load | **Yes — needed before any integration can run** | Q3 2026 |
+| **ADR-129** | HOMECORE-AUTO | Automation engine, YAML parser, Jinja2-equivalent WASM evaluator, blueprints | Yes (automation is core to HA UX) | Q4 2026 |
+| **ADR-130** | HOMECORE-API | REST + WebSocket wire-compat API, Axum server, HA companion app support | **Yes — needed for client compat** | Q3 2026 |
+| **ADR-131** | HOMECORE-UI | TS + Rust→WASM frontend, SharedWorker state sync, Material 3 design lang | No (can run alongside Python HA UI initially) | Q1 2027 |
+| **ADR-132** | HOMECORE-RECORDER | SQLite recorder + ruvector semantic history, schema migration | No (structural recorder ships before ruvector layer) | Q4 2026 |
+| **ADR-133** | HOMECORE-ASSIST | ruflo agent voice assistant, ruvector intent matching, Wyoming edge path | No | Q4 2026 |
+| **ADR-134** | HOMECORE-MIGRATE | Migration tooling from Python HA, config-entry parser, side-by-side mode | No (needed for user adoption) | Q1 2027 |
+
+**Critical path**: ADR-127 → ADR-128 → ADR-130 must land in that order. ADR-129, ADR-132, ADR-133, ADR-131, ADR-134 can proceed in parallel once the core triad is stable.
+
+---
+
+## 5. Cross-cutting decisions
+
+The following decisions govern all 8 sub-ADRs and are not repeated in each.
+
+### 5.1 Governance via RUVIEW-POLICY (ADR-124 §4.1a)
+
+Every HOMECORE component that returns biometric data (presence, HR/BR, pose keypoints, BFLD identity-risk) MUST route through the RUVIEW-POLICY layer defined in ADR-124 §4.1a. The policy store is the same `~/.config/rvagent/policy.json` used by `@ruvnet/rvagent`. HOMECORE is a first-class policy principal — its agent ID in the policy store is `homecore`.
+
+### 5.2 Semantic memory via ruvector
+
+Historical state is not only stored in SQLite rows (structural). Every state-changed event is also embedded via ruvector (using the same napi-rs bindings as ADR-124) and indexed in an HNSW store for semantic search. The `homecore-recorder` crate (ADR-132) owns this dual-write. Queries like "when did the living room motion last exceed baseline?" become vector-nearest-neighbour searches, not SQL BETWEEN clauses.
+
+### 5.3 Agent orchestration via ruflo
+
+The automation engine (ADR-129) and the assist pipeline (ADR-133) both have an optional ruflo-agent mode where complex conditions or voice intents are routed to a ruflo agent (using the `mcp__claude-flow__*` tool namespace) for LLM-backed resolution. This is gated by RUVIEW-POLICY: a policy grant is required before HOMECORE sends any state-history context to a ruflo agent.
+
+### 5.4 Witness and audit via Ed25519 chain (ADR-028 pattern)
+
+Every state transition that crosses a privacy boundary (e.g. BFLD identity-risk score elevated, a biometric entity state published) is logged to an Ed25519 witness chain using the same structure as ADR-028 §3. The witness bundle is exportable for regulated deployments (care homes, hotels, shared offices).
+
+### 5.5 Crate naming and workspace placement
+
+All HOMECORE crates live in `v2/crates/homecore-*/`:
+
+| Crate | ADR |
+|---|---|
+| `homecore` | ADR-127 |
+| `homecore-plugins` | ADR-128 |
+| `homecore-automation` | ADR-129 |
+| `homecore-api` | ADR-130 |
+| `homecore-recorder` | ADR-132 |
+| `homecore-assist` | ADR-133 |
+| `homecore-migrate` | ADR-134 |
+
+The frontend (`homecore-frontend`) is not a Rust crate — it is an npm package at `npm/homecore-frontend/`, mirroring the `npm/rvagent/` pattern from ADR-124.
+
+### 5.6 HA wire-compatibility baseline
+
+The HOMECORE REST and WebSocket API must be **compatible with HA 2025.1** as the baseline. HA 2025.1 introduced schema version 48 in the recorder. The API surface to replicate is:
+
+- REST: `homeassistant/components/api/__init__.py` — 24 endpoints
+- WebSocket: `homeassistant/components/websocket_api/` — the `connection.py` + `commands.py` handler pattern, the auth handshake, and the `subscribe_events` / `subscribe_trigger` / `call_service` commands
+- Auth: `homeassistant/auth/` — the long-lived access token model
+- Config entries: `.storage/core.config_entries` JSON schema (versioned, auto-migrated)
+
+### 5.7 "Do not port" list
+
+The following HA subsystems are explicitly **not** ported to HOMECORE:
+
+| HA subsystem | Reason not ported | HOMECORE replacement |
+|---|---|---|
+| **SUPERVISOR** (`homeassistant/supervisor/`) | Manages add-on containers and OS upgrades. HOMECORE runs on a standard Linux/Pi OS managed by systemd. | ruflo + systemd service units + OTA via the existing Cognitum Seed OTA registry (ADR-116 §2.2) |
+| **Home Assistant OS** (HAOS) | A custom embedded Linux image. HOMECORE targets standard Debian/Ubuntu on Pi 5 and standard Docker. | Standard OS + Docker Compose or systemd |
+| **Nabu Casa Cloud** | Paid remote-access and Alexa/Google integration service. HOMECORE uses Tailscale for remote access and `@ruvnet/rvagent` for AI integration. | Tailscale + ADR-107 federation + SENSE-BRIDGE |
+| **Add-on store** (Supervisor add-ons) | Docker container management. | Cognitum Seed cog registry (ADR-102) |
+| **Legacy YAML-only integrations** (pre-config-flow, ~500 of 2,000) | These require Python `setup_platform` (deprecated in HA 2024.x). Only config-flow integrations (`async_setup_entry`) are ported. | Document upgrade path; unported integrations can run via `homecore-migrate` bridge mode |
+| **Analytics / Nabu Casa telemetry** | Optional cloud telemetry. | Not replicated. HOMECORE is local-only. |
+| **Home Assistant Yellow / Green hardware** | Specific hardware. HOMECORE targets Cognitum Seed, Pi 5, and x86_64. | Cognitum Seed hardware |
+
+---
+
+## 6. Compatibility contract
+
+### 6.1 What works on day one (P3, wire-compat API stable)
+
+| Client | Works? | Notes |
+|---|---|---|
+| **HA iOS companion app** | Yes | Connects to `/api/websocket`; authenticates with long-lived token; subscribes to state events |
+| **HA Android companion app** | Yes | Same as iOS |
+| **Home Assistant Dashboard (frontend)** | Yes (HA frontend served against HOMECORE API) | Until HOMECORE-UI (ADR-131) ships, serve the Python HA frontend binary against the HOMECORE API |
+| **HACS** | Partial | HACS uses the WS API for integration management; custom component loading requires HOMECORE-PLUGINS (ADR-128) |
+| **Node-RED HA integration** | Yes | Uses REST + WS API; wire-compat |
+| **`homeassistant` Python client library** | Yes | Pure REST/WS client |
+| **`ha-mqtt-discoverable` Python library** | Yes | Publishes MQTT discovery; HOMECORE consumes the same topics |
+| **ESPHome devices** | Yes | ESPHome native API or MQTT; HOMECORE speaks both |
+| **Nabu Casa Cloud** | **No** | Nabu Casa uses a proprietary remote-access tunnel to `nabucasa.com`. HOMECORE does not integrate with the Nabu Casa cloud proxy. Replace with Tailscale. |
+| **M5Stack ATOM Echo / voice satellites** | Yes (P4) | Wyoming protocol is HOMECORE-ASSIST (ADR-133) scope |
+| **HACS custom cards** | Yes (after ADR-131 P3) | Custom cards are served via the same `/hacsfiles/` static route |
+
+### 6.2 What breaks and why
+
+| HA feature | HOMECORE status | Reason |
+|---|---|---|
+| Nabu Casa remote access | Not supported | Proprietary tunnel; replace with Tailscale |
+| HA Supervisor add-ons | Not supported | No container manager in HOMECORE |
+| HAOS OTA updates | Not supported | HOMECORE runs on standard OS |
+| Python custom integrations (non-WASM) | Not supported | WASM sandbox only; Python integrations cannot run natively |
+| Legacy `setup_platform` integrations | Not supported | Config-flow (`async_setup_entry`) only |
+| HA Cloud TTS/STT (Nabu Casa) | Not supported | Use Whisper + Piper locally |
+| HA Cloud Alexa/Google skill | Not supported | Use ruflo agent instead |
+
+---
+
+## 7. Phase roadmap
+
+```
+Q3 2026    Q4 2026    Q1 2027    Q2 2027
+   P1         P2         P3         P4         P5
+scaffold   state+API  wire-compat  plugins+    full
+           core       HA clients  automation  HOMECORE
+```
+
+### P1 — Scaffold (Q3 2026, 2 weeks)
+
+- [ ] Create `v2/crates/homecore/` workspace member, empty state machine skeleton.
+- [ ] Create `v2/crates/homecore-api/` skeleton, Axum server on port 8123 (HA default).
+- [ ] Create `npm/homecore-frontend/` skeleton.
+- [ ] CI: `cargo check -p homecore -p homecore-api --no-default-features` green.
+- [ ] ADR-134 migration tool parses one `.storage/core.config_entries` fixture.
+
+### P2 — State machine + API core (Q3 2026, 4 weeks)
+
+- [ ] ADR-127 state machine: entity registry, state machine, event bus (Tokio broadcast), service registry.
+- [ ] ADR-130 API: REST endpoints, WebSocket auth handshake, `subscribe_events`, `call_service`.
+- [ ] ADR-132 recorder: SQLite schema (HA schema version 48 compatible), state write path.
+- [ ] Integration test: HA companion app authenticates and receives state updates.
+
+### P3 — Wire-compat + plugin scaffold (Q3–Q4 2026, 6 weeks)
+
+- [ ] ADR-128 plugin system: WASM sandbox, manifest schema, first ported integrations (MQTT, HTTP).
+- [ ] ADR-130 API: remaining WS commands, HACS support.
+- [ ] ADR-134 migration: reads `automations.yaml`, `secrets.yaml`, config entries.
+- [ ] ADR-132 recorder: ruvector dual-write, semantic search API.
+
+### P4 — Automation + assist (Q4 2026, 4 weeks)
+
+- [ ] ADR-129 automation engine: YAML parser, trigger evaluation, WASM expression evaluator.
+- [ ] ADR-133 assist: ruflo agent orchestration, ruvector intent matching.
+- [ ] ADR-131 frontend P1: TypeScript shell, WASM state machine in SharedWorker.
+
+### P5 — Full HOMECORE (Q1 2027, 6 weeks)
+
+- [ ] ADR-131 frontend: complete UI parity with HA Lovelace, custom cards.
+- [ ] ADR-134 migration: side-by-side mode, one-click cutover.
+- [ ] Full compatibility test suite against HA iOS/Android companion apps.
+- [ ] Pi 5 performance benchmarks: startup < 1 s, idle < 50 MB RAM.
+
+---
+
+## 8. Alternatives rejected
+
+### Alt-A: Contribute RuView sensing features upstream to Python HA
+
+Add the HOMECORE features (WASM plugins, ruvector recorder, ruflo assist) as Python HA components via PRs to `home-assistant/core`.
+
+**Rejected because**: HA's architecture board has strict policies against adding new runtimes (WASM, Rust FFI) to the core process. The GIL bottleneck cannot be resolved from within Python HA. CSI DSP at 100 Hz frame rate inside a Python process is not feasible. This path cedes architectural control permanently.
+
+### Alt-B: Thin Rust wrapper that calls into Python HA via PyO3
+
+Keep Python HA as the runtime; expose RuView sensing primitives via PyO3 bindings so they run at native speed inside the Python HA process.
+
+**Rejected because**: the GIL is not resolved by PyO3 calls — the HA event loop still serialises all state changes. Startup time and memory footprint are unchanged. WASM plugin safety is unchanged. This is a tactical optimisation, not an architectural solution.
+
+### Alt-C: OpenHAB or Domoticz as the base
+
+Port RuView's sensing stack on top of an alternative hub (openHAB/Java, Domoticz/C++).
+
+**Rejected because**: neither has HA's community network effects, companion app ecosystem, or HACS plugin catalog. A clean-room Rust implementation preserves the HA compatibility contract (the most valuable asset) without inheriting the Python runtime limitations.
+
+### Alt-D: Extend the existing `wifi-densepose-sensing-server` into a full hub
+
+Add automation, entity registry, and recorder features directly to the existing Axum sensing server.
+
+**Rejected because**: the sensing server is a purpose-built single-concern binary (CSI → MQTT/WebSocket). Expanding it into a hub would violate the single-responsibility principle and couple hub release cycles to firmware release cycles. HOMECORE is a separate crate family that depends on but does not modify the sensing server.
+
+---
+
+## 9. Top-level risks
+
+| Risk | Likelihood | Severity | Mitigation |
+|---|---|---|---|
+| **API drift** — HA's REST/WS API evolves; HOMECORE must track it | High | High | Pin to HA 2025.1 baseline (schema 48); run the HA companion app integration tests against every HOMECORE release; ADR-130 owns the compat matrix |
+| **WASM sandbox performance** — plugin calls through the WASM boundary add latency | Medium | Medium | Benchmark plugin roundtrip on Pi 5 before P3; reject if >5 ms; WASM3/Wasmtime both have sub-1 ms call overhead for compute-light integrations |
+| **Core triad dependency** — ADR-128 and ADR-130 cannot start until ADR-127 is stable | High | High | ADR-127 is P2 start; freeze the state machine public API (entity_id, state, attributes, last_changed) before ADR-128 begins |
+| **ruvector semantic recorder** — dual-write to SQLite + HNSW may impact write throughput under high-frequency sensing | Medium | High | ruvector writes are async (non-blocking tokio task); SQLite write is the hot path; benchmark at 100 state/s on Pi 5 before ADR-132 ships |
+| **Nabu Casa gap** — users who depend on HA Cloud remote access have no HOMECORE replacement at P3 | High | Medium | Document Tailscale as the replacement prominently; provide ADR-134 migration wizard that detects Nabu Casa usage and offers Tailscale setup |
+| **Frontend bundle size** — replicating the HA Lovelace card ecosystem in TS+WASM is a significant engineering effort | High | High | ADR-131 is off-critical-path; serve HA's Python frontend against the HOMECORE API until ADR-131 P3 ships |
+| **License** — HA is Apache 2.0; the wire protocol is unencumbered; HA's UI assets and card components have separate licenses | Low | High | Clean-room Rust implementation does not use HA source; HA frontend is served as a binary (not embedded); review license before ADR-131 ships any reimplemented component |
+
+---
+
+## 10. Open questions
+
+**Q1** (ADR-127): Should the HOMECORE state machine use a `DashMap<EntityId, State>` for lock-free concurrent reads, or a `RwLock<HashMap<EntityId, State>>` for simpler reasoning? The answer affects every integration's write pattern.
+
+**Q2** (ADR-128): Does the WASM sandbox use Wasmtime (Cranelift JIT, ~5 MB binary) or WASM3 (interpreter, ~50 kB binary)? On a Pi 5 WASM3 is sufficient for integration logic; Wasmtime matters if integrations need near-native DSP speed.
+
+**Q3** (ADR-130): The HA WebSocket API uses numeric IDs for command/response correlation. The HA 2025.1 baseline adds `subscribe_trigger` as a first-class WS command. Are there any commands in the HA companion app that require a newer baseline?
+
+**Q4** (ADR-132): The ruvector HNSW index for state history — what embedding dimension represents a state snapshot? Options: (a) embed only numeric sensor states (scalar embedding), (b) embed `{entity_id, state, attributes}` as a text embedding via a local small model, (c) use a fixed schema encoding. The answer determines the semantic query fidelity.
+
+**Q5** (ADR-134): HA's `.storage/core.config_entries` format is versioned but undocumented; it is hand-engineered from reverse-engineering the Python `StorageCollection` class in `homeassistant/helpers/storage.py`. Is this format stable enough to parse without upstream documentation, or does HOMECORE need to maintain a version matrix?
+
+---
+
+## 11. References
+
+### This repo
+
+- `docs/adr/ADR-115-home-assistant-integration.md` — HA-DISCO MQTT publisher; 21-entity surface; semantic primitives; competitive comparison table
+- `docs/adr/ADR-116-cog-ha-matter-seed.md` — HA-COG Seed cog; cog packaging precedent (ADR-101)
+- `docs/adr/ADR-117-pip-wifi-densepose-modernization.md` — PIP-PHOENIX PyO3 bindings; Python client surface
+- `docs/adr/ADR-118-bfld-beamforming-feedback-layer-for-detection.md` — BFLD master; privacy class enforcement
+- `docs/adr/ADR-124-rvagent-mcp-ruvector-npm-integration.md` — SENSE-BRIDGE; RUVIEW-POLICY §4.1a; multi-modal normalization §11.3
+- `docs/adr/ADR-125-ruview-apple-home-native-hap-bridge.md` — APPLE-FABRIC HAP bridge
+- `v2/crates/wifi-densepose-sensing-server/src/main.rs` — Axum server architecture; bearer auth pattern
+- `v2/crates/wifi-densepose-ruvector/src/viewpoint/` — cross-viewpoint fusion (attention, coherence, geometry, fusion modules)
+- `CLAUDE.md` — Project topology (hierarchical-mesh, 15 agents), ESP32 hardware table, crate publishing order
+
+### HA upstream
+
+- `homeassistant/core.py` — `HomeAssistant`, `StateMachine`, `EventBus`, `ServiceRegistry`, `Config`
+- `homeassistant/helpers/entity_registry.py` — `EntityRegistry`, `RegistryEntry`
+- `homeassistant/helpers/entity.py` — `Entity`, `async_write_ha_state`, entity lifecycle
+- `homeassistant/components/api/__init__.py` — REST API handler (24 routes)
+- `homeassistant/components/websocket_api/` — `connection.py` auth handshake; `commands.py` WS commands
+- `homeassistant/components/recorder/` — SQLite schema; `migration.py` schema version 48
+- `homeassistant/components/assist_pipeline/` — voice/text pipeline; Wyoming protocol
+- `homeassistant/helpers/template.py` — Jinja2 template engine customisation
+- `homeassistant/components/automation/__init__.py` — automation trigger/condition/action model
+- `homeassistant/helpers/storage.py` — `.storage/*.json` persistence; `StorageCollection`
+- `homeassistant/auth/` — long-lived access token model; `AuthManager`
+
+### External
+
+- [HA Developer Docs — Core Architecture](https://developers.home-assistant.io/docs/architecture/core/) — state machine, event bus, service registry overview
+- [HA Developer Docs — WebSocket API](https://developers.home-assistant.io/docs/api/websocket/) — WS command catalog
+- [DeepWiki HA core — Entity and Registry Management](https://deepwiki.com/home-assistant/core/2.2-entity-and-registry-management) — entity lifecycle
+- [DeepWiki HA core — Data Management](https://deepwiki.com/home-assistant/core/3-data-management) — recorder schema version 48
+- [HA recorder integration](https://www.home-assistant.io/integrations/recorder/) — SQLite default; schema migration overview

docs/adr/ADR-127-homecore-state-machine-rust.md

@@ -0,0 +1,193 @@
+# ADR-127: HOMECORE-CORE — Rust state machine, entity registry, event bus, service registry
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-25 |
+| **Deciders** | ruv |
+| **Codename** | **HOMECORE-CORE** |
+| **Relates to** | [ADR-126](ADR-126-ruview-native-ha-port-master.md) (HOMECORE master), [ADR-028](ADR-028-esp32-capability-audit.md) (witness chain), [ADR-124](ADR-124-rvagent-mcp-ruvector-npm-integration.md) (RUVIEW-POLICY) |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+`homeassistant/core.py` is the 3,200-line heart of Python Home Assistant. It defines five objects that every other HA component depends on:
+
+1. **`HomeAssistant`** — the runtime coordinator, event loop holder, and service locator. Contains `bus` (EventBus), `states` (StateMachine), `services` (ServiceRegistry), `config` (Config), `components` (loaded component set).
+2. **`EventBus`** — publish/subscribe event dispatch. `async_fire(event_type, event_data)` dispatches to all registered listeners. Listener registration is `async_listen(event_type, callback)`. Wildcard listener is `MATCH_ALL`. Event data is a plain Python dict.
+3. **`StateMachine`** — an in-memory dictionary from `entity_id` (str) to `State`. `async_set(entity_id, new_state, attributes)` writes and fires `state_changed`. `get(entity_id)` reads. `async_remove(entity_id)` fires `state_removed`. States are immutable snapshots with `last_changed`, `last_updated`, `context`.
+4. **`ServiceRegistry`** — maps `(domain, service_name)` → async handler function. `async_call(domain, service, data)` fires a `call_service` event, waits for the registered handler. `async_register(domain, service, handler, schema)` registers a handler with optional voluptuous schema validation.
+5. **`EntityRegistry`** (`homeassistant/helpers/entity_registry.py`) — persists metadata (enabled/disabled, name override, area assignment, device ID, unique ID, entity category) across restarts. Stored in `.storage/core.entity_registry`. Loaded at startup; written on every change.
+
+The **DeviceRegistry** (`homeassistant/helpers/device_registry.py`, stored in `.storage/core.device_registry`) tracks physical devices that entities belong to. Entities link to devices via `device_id`; devices link to config entries via `config_entry_id`.
+
+### 1.1 Why these specific files matter
+
+Python HA's `core.py` is a single-process Python 3.12 module that:
+- Holds the asyncio event loop directly
+- Serialises all state-changed writes through `asyncio.Lock`
+- Fires event listeners in the same event loop iteration that fired the event (listeners cannot block)
+- Is single-threaded by design — concurrent writes to the state machine are impossible without explicit async primitives
+
+For HOMECORE the same semantic requirements apply, but the implementation must support:
+- **Concurrent reads** from dozens of integration WASM sandboxes polling current state
+- **High-frequency writes** from the RuView sensing stack (CSI at 100 Hz; state updates at up to 20 Hz per entity)
+- **Ordered delivery** of state_changed events to automation triggers (ADR-129) and recorder (ADR-132) subscribers
+- **Zero-copy reads** where possible for the REST API (ADR-130) path
+
+---
+
+## 2. Decision
+
+Implement the `homecore` Rust crate at `v2/crates/homecore/` with the following design.
+
+### 2.1 State machine: `DashMap` + Tokio broadcast
+
+The primary state store is a `DashMap<EntityId, Arc<State>>` where:
+- `EntityId` is a validated newtype around `String` (validated format: `domain.name`)
+- `State` is a frozen struct: `entity_id`, `state` (String), `attributes` (serde_json::Value), `last_changed` (DateTime<Utc>), `last_updated` (DateTime<Utc>), `context` (Context)
+- `Arc<State>` allows zero-copy cloning for readers while the writer atomically replaces the map entry
+
+State changes are published to a `tokio::sync::broadcast::Sender<StateChangedEvent>` channel (capacity: 4,096 events). Any number of receivers subscribe — the recorder, automation engine, WebSocket subscriber handler, and ruvector dual-write task all hold independent receivers. Slow receivers that fall behind by 4,096 events receive a `RecvError::Lagged` and must re-sync from the current state map.
+
+### 2.2 Event bus: typed + untyped channels
+
+HOMECORE distinguishes two event categories:
+
+1. **System events** (typed): `StateChanged`, `ServiceCall`, `ComponentLoaded`, `PlatformDiscovered`, `HomeAssistantStart`, `HomeAssistantStop`. These use Tokio typed broadcast channels with zero allocation on the read path.
+2. **Integration events** (untyped): integrations fire arbitrary event types (`event_type: String`, `event_data: serde_json::Value`). These use a single `broadcast::Sender<DomainEvent>` where `DomainEvent` carries the type string and data blob. This mirrors HA's `EventBus.async_fire()`.
+
+### 2.3 Service registry: `HashMap` + mpsc dispatch
+
+Services are registered as `(Domain, ServiceName) → ServiceHandler` where `ServiceHandler` is a `Box<dyn Fn(ServiceCall) -> BoxFuture<ServiceResponse> + Send + Sync>`. The registry lives in a `tokio::sync::RwLock<HashMap<(Domain, ServiceName), ServiceHandler>>`. Service calls go through the event bus (fire `call_service`) and are dispatched to the handler by an internal router task. This matches HA's indirection: `hass.services.async_call(domain, service, data)` does not call the handler directly; it fires an event.
+
+### 2.4 Entity registry: persisted metadata sidecar
+
+The entity registry is a `RwLock<HashMap<EntityId, EntityEntry>>` backed by an async JSON writer that flushes to `.homecore/storage/core.entity_registry` on every write. The schema matches HA's `core.entity_registry` schema (version 13 as of HA 2025.1) so ADR-134 migration can read both formats interchangeably.
+
+`EntityEntry` fields mirrored from HA:
+- `entity_id: EntityId`
+- `unique_id: Option<String>`
+- `platform: String`
+- `name: Option<String>` (user override)
+- `disabled_by: Option<DisabledBy>` (user, integration, config_entry)
+- `area_id: Option<AreaId>`
+- `device_id: Option<DeviceId>`
+- `entity_category: Option<EntityCategory>` (config, diagnostic)
+- `config_entry_id: Option<ConfigEntryId>`
+
+### 2.5 Device registry: parallel sidecar
+
+`DeviceRegistry` mirrors HA's `core.device_registry` schema (version 13). Devices are identified by a set of `(id_type, id_value)` tuples (the `identifiers` field), which matches HA's pattern of accepting multiple identifier types per device (MAC address, serial number, integration-specific ID).
+
+---
+
+## 3. HA-side reference table
+
+| HA module / file | What it does | HOMECORE preserves | Changes | Drops |
+|---|---|---|---|---|
+| `homeassistant/core.py` `StateMachine` | In-memory state store, fire `state_changed` | Same semantics: immutable snapshots, `last_changed`, `last_updated`, `context` | `DashMap` instead of asyncio-locked `dict`; `broadcast::Sender` instead of asyncio callbacks | Python asyncio coupling |
+| `homeassistant/core.py` `EventBus` | Pub/sub event dispatch | `MATCH_ALL` listener; per-type listener; event data dict | Typed system events + untyped domain events; no Python dict — use `serde_json::Value` | `@callback` decorator, HassJob abstraction |
+| `homeassistant/core.py` `ServiceRegistry` | Register/call services | Same `(domain, service)` key structure; schema validation | Schema validation via `serde` `Deserialize` trait instead of voluptuous | voluptuous, Python type coercions |
+| `homeassistant/core.py` `HomeAssistant` | Runtime coordinator / service locator | State machine + event bus + services accessible on one struct | Struct with `Arc<HomeCoreInner>` for cheap cloning across tasks | asyncio event loop holder, Python executor |
+| `homeassistant/helpers/entity_registry.py` | Persist entity metadata | All fields listed in §2.4; file format compatible | Async tokio I/O; no Python pickle | Python-specific persistence helpers |
+| `homeassistant/helpers/device_registry.py` | Persist device metadata | `identifiers`, `connections`, `manufacturer`, `model`, `name`, `via_device_id` | Async tokio I/O | — |
+| `homeassistant/helpers/entity.py` | Entity base class | `entity_id`, `state`, `attributes`, `unique_id`, `device_info`, async_write_ha_state semantics | Trait `HomeCoreEntity` instead of class | Python MRO, `@property` decorators |
+| `homeassistant/helpers/event.py` | Convenience event helpers | `async_track_state_change`, `async_track_time_interval` (as Rust timer tasks) | Rust closures / async tasks | Python asyncio task wrappers |
+
+---
+
+## 4. Public API parity table
+
+| HA Python surface | HOMECORE Rust equivalent |
+|---|---|
+| `hass.states.get(entity_id)` | `hass.states.get(&entity_id) -> Option<Arc<State>>` |
+| `hass.states.async_set(entity_id, state, attributes)` | `hass.states.set(entity_id, state, attributes).await` |
+| `hass.states.async_remove(entity_id)` | `hass.states.remove(&entity_id).await` |
+| `hass.states.async_all(domain_filter)` | `hass.states.all(domain_filter) -> Vec<Arc<State>>` |
+| `hass.bus.async_fire(event_type, data)` | `hass.bus.fire(event_type, data).await` |
+| `hass.bus.async_listen(event_type, callback)` | `hass.bus.subscribe(event_type) -> broadcast::Receiver<DomainEvent>` |
+| `hass.services.async_call(domain, service, data)` | `hass.services.call(domain, service, data).await -> ServiceResponse` |
+| `hass.services.async_register(domain, service, handler, schema)` | `hass.services.register(domain, service, handler)` |
+| `hass.services.has_service(domain, service)` | `hass.services.has(domain, service) -> bool` |
+| `entity_registry.async_get(entity_id)` | `entity_registry.get(&entity_id) -> Option<&EntityEntry>` |
+| `entity_registry.async_update_entity(entity_id, **kwargs)` | `entity_registry.update(entity_id, patch).await` |
+| `device_registry.async_get_device(identifiers)` | `device_registry.get_by_identifiers(identifiers) -> Option<&DeviceEntry>` |
+| `Context(user_id, parent_id)` | `Context { id: Uuid, parent_id: Option<Uuid>, user_id: Option<UserId> }` |
+
+---
+
+## 5. Phased implementation plan
+
+### P1 — Skeleton (2 weeks)
+
+- [ ] Create `v2/crates/homecore/` workspace member with `Cargo.toml`.
+- [ ] Define `State`, `EntityId`, `Domain`, `ServiceName`, `Context`, `DomainEvent` types.
+- [ ] `StateMachine`: `DashMap` + broadcast channel; `set()`, `get()`, `remove()`, `all()`.
+- [ ] `EventBus`: typed broadcast for system events + untyped broadcast for domain events.
+- [ ] Unit tests: 50 state writes/reads with concurrent readers; verify broadcast delivery.
+
+### P2 — Service registry + entity registry (2 weeks)
+
+- [ ] `ServiceRegistry`: `RwLock<HashMap>` + mpsc dispatch task.
+- [ ] `EntityRegistry`: in-memory + JSON async writer to `.homecore/storage/core.entity_registry`.
+- [ ] `DeviceRegistry`: in-memory + JSON async writer to `.homecore/storage/core.device_registry`.
+- [ ] Serialization: `serde` with `#[serde(rename_all = "snake_case")]`; schema version 13 header written to match HA format.
+- [ ] Unit tests: register service, call service, verify handler invoked; persist and reload entity registry.
+
+### P3 — Trait surface for integrations (1 week)
+
+- [ ] `HomeCoreEntity` trait: `entity_id()`, `unique_id()`, `name()`, `device_info()`, `state()`, `attributes()`, `async_write_ha_state(&hass)`.
+- [ ] `Platform` trait: `async_setup_entry(hass, config_entry) -> Result<()>`.
+- [ ] `ConfigEntry` struct mirroring HA's `ConfigEntry` fields.
+- [ ] Integration test: a minimal test integration registers an entity, writes a state, reads it back from the state machine.
+
+### P4 — Performance validation (1 week)
+
+- [ ] Benchmark: 1,000 state writes/s on Pi 5; measure latency at p50/p95/p99.
+- [ ] Benchmark: 100 concurrent WS subscribers each receiving all state_changed events; measure delivery lag.
+- [ ] Benchmark: broadcast channel saturation test at 4,096 capacity; verify `RecvError::Lagged` handling.
+- [ ] Acceptance criterion: p99 state write latency < 1 ms on Pi 5 (8 GB, 4 cores).
+
+---
+
+## 6. Risks
+
+| Risk | Likelihood | Severity | Mitigation | Cross-ADR impact |
+|---|---|---|---|---|
+| **Broadcast channel lag** — a slow subscriber (e.g. ruvector recorder write) lags behind and drops events | Medium | High | Give recorder its own channel separate from WS subscribers; recorder is the hot path, give it highest priority | ADR-132: recorder write path must be designed to keep up with 100 Hz state writes |
+| **DashMap contention** — shard count default (16) may be too low for 100 Hz writes on a single entity | Low | Medium | Increase DashMap shard count to 64; benchmark before ADR-130 integration | ADR-130: REST API reads state directly from DashMap — must be lock-free |
+| **Entity registry format drift** — HA updates `.storage/core.entity_registry` schema; HOMECORE falls behind | Medium | Medium | Pin to schema version 13; version-check on load; fail loudly on unknown version | ADR-134: migration tool reads HA entity registry — must support the same schema version |
+| **Context propagation** — HA's `Context` is used for audit trails (which automation triggered which service call). HOMECORE must propagate it correctly or automation audits break | High | Low | Derive `Context` from source event at every service call; thread through `ServiceCall.context` field | ADR-129: automation engine must supply context when calling services |
+
+---
+
+## 7. Open questions
+
+**Q1**: Should `EntityId` validation be strict (reject anything that doesn't match `[a-z0-9_]+\.[a-z0-9_]+`) or lenient (accept any UTF-8 string)? HA itself accepts unicode entity IDs since 2024.3. Strict validation simplifies routing; lenient matches HA's actual behaviour.
+
+**Q2**: The `broadcast::Sender` capacity of 4,096 is chosen based on a worst-case of 100 state writes/s × 40 s of acceptable lag before a slow receiver is declared dead. Is 40 s the right threshold, or should it be configurable per receiver?
+
+**Q3**: Should the `HomeCoreEntity` trait be object-safe (enabling `Vec<Box<dyn HomeCoreEntity>>`) or use associated types (enabling monomorphisation)? Object safety is required for the WASM plugin boundary (ADR-128); monomorphisation is faster for built-in integrations.
+
+**Q4**: HA's `State.context` carries a `user_id` that traces which user or automation initiated a state change. HOMECORE uses `UserId` from the auth layer (ADR-130). Is the auth layer a dependency of the core state machine, or should `user_id` be an optional opaque string to avoid circular deps?
+
+---
+
+## 8. References
+
+### HA upstream
+
+- `homeassistant/core.py` — `HomeAssistant`, `StateMachine` (lines 1–800), `EventBus` (lines 800–1100), `ServiceRegistry` (lines 1100–1500), `Config` (lines 1500–2000)
+- `homeassistant/helpers/entity_registry.py` — `EntityRegistry`, `RegistryEntry` (all ~1,900 lines); schema version constant `STORAGE_VERSION`
+- `homeassistant/helpers/device_registry.py` — `DeviceRegistry`, `DeviceEntry`; schema version
+- `homeassistant/helpers/entity.py` — `Entity` base class; `async_write_ha_state`; entity lifecycle hooks
+- `homeassistant/helpers/event.py` — `async_track_state_change`, `async_track_time_interval`
+
+### This repo
+
+- `v2/crates/wifi-densepose-sensing-server/src/main.rs` — Axum + Tokio architecture pattern used throughout the existing server stack
+- `docs/adr/ADR-126-ruview-native-ha-port-master.md` — HOMECORE master; §5.5 crate naming; §6 compatibility contract; §5.1 RUVIEW-POLICY
+- `docs/adr/ADR-028-esp32-capability-audit.md` — witness chain pattern (Ed25519 per state transition)

docs/adr/ADR-128-homecore-integration-plugin-system.md

@@ -0,0 +1,270 @@
+# ADR-128: HOMECORE-PLUGINS — WASM integration plugin system
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-25 |
+| **Deciders** | ruv |
+| **Codename** | **HOMECORE-PLUGINS** |
+| **Relates to** | [ADR-126](ADR-126-ruview-native-ha-port-master.md) (HOMECORE master), [ADR-127](ADR-127-homecore-state-machine-rust.md) (HOMECORE-CORE), [ADR-102](ADR-102-edge-module-registry.md) (cog registry), [ADR-100](ADR-100-cog-packaging-specification.md) (cog packaging spec) |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+Home Assistant ships approximately 2,000 integrations, each a Python module in `homeassistant/components/<domain>/`. Each integration:
+
+1. Declares a **manifest** (`manifest.json`) with `domain`, `name`, `version`, `requirements` (pip packages), `dependencies` (other HA integrations), `codeowners`, `iot_class`, `config_flow` (bool), and `quality_scale`.
+2. Provides **`async_setup`** (global domain setup, called once at HA startup) and/or **`async_setup_entry`** (per-config-entry setup, called when a user adds an integration via the UI).
+3. Imports Python packages from `requirements` at load time — these are installed into HA's Python environment by the loader at first run.
+4. Communicates with the HA core exclusively through the `hass` object (the `HomeAssistant` instance) — setting states, calling services, registering services, subscribing to events.
+
+In Python HA, integrations run **in-process** with the hub. A buggy integration can crash the event loop, read arbitrary HA memory, or import packages that conflict with other integrations. HA mitigates this via code review and quality scale requirements, but there is no runtime isolation boundary.
+
+### 1.1 The Cognitum Seed cog system
+
+The project already has a cog system (ADR-102, ADR-100) for the Cognitum Seed appliance. A **cog** is a signed, sandboxed module that installs from the Seed app registry. ADR-101 (`cog-pose-estimation`) shipped signed aarch64/x86_64 binaries with a model weight blob. ADR-116 (`cog-ha-matter`) shipped HA+Matter integration as a cog.
+
+The cog system uses a different packaging model from HA integrations (binary artifacts vs Python packages), but the same conceptual pattern: a manifest, a lifecycle hook, and communication through a defined interface.
+
+HOMECORE-PLUGINS unifies these two patterns: every HOMECORE integration is a **WASM module** that speaks the cog ABI, can be hot-loaded without restarting the hub, and is sandboxed by the WASM runtime.
+
+---
+
+## 2. Decision
+
+HOMECORE integrations are **WASM modules** loaded by a Rust host runtime (`homecore-plugins` crate). Each plugin:
+
+1. Compiles to a `.wasm` binary (from Rust, AssemblyScript, Go, or any WASM-targeting language).
+2. Declares a `manifest.json` (superset of HA's manifest schema — see §3).
+3. Exports exactly three WASM functions: `setup_entry(config_entry_ptr, config_entry_len) → i32`, `call_service(call_ptr, call_len) → i32`, and `receive_event(event_ptr, event_len) → i32`.
+4. Imports a set of **host functions** from the HOMECORE host runtime: `hc_state_get`, `hc_state_set`, `hc_event_fire`, `hc_service_call`, `hc_log`, `hc_entity_register`.
+5. Communicates with the host exclusively through those imports — no direct memory access outside its own linear memory.
+
+The WASM runtime is **Wasmtime** (Cranelift JIT on Pi 5 and x86_64; interpretation mode available for low-memory targets via `--features wasm3`).
+
+### 2.1 Why WASM over Python-in-process
+
+| Criterion | Python in-process (HA today) | WASM sandbox (HOMECORE) |
+|---|---|---|
+| Memory isolation | None — any integration can read any HA object | WASM linear memory; host allocates shared buffer only for ABI calls |
+| Crash isolation | Integration panic = HA event loop crash | WASM trap = plugin terminated, hub continues |
+| Language support | Python only | Any WASM-targeting language: Rust, Go, AssemblyScript, C, Zig |
+| Hot-load without restart | No — requires `asyncio.run_coroutine_threadsafe` patching | Yes — Wasmtime `Engine` + `Module::deserialize` from compiled `.cwasm` cache |
+| Dependency conflicts | pip requirements collide across integrations | Each WASM module carries its own static dependencies (no runtime pip) |
+| Startup cost per integration | Python import + pip install | Wasmtime JIT compile (~5 ms for a typical 200 kB WASM module); cached to `.cwasm` |
+
+### 2.2 Cog system as the plugin substrate
+
+The existing cog system (ADR-102) is the distribution and lifecycle layer. HOMECORE-PLUGINS extends it:
+
+- **Distribution**: cogs are fetched from the Seed app registry (`app-registry.json`) or from a HOMECORE plugin registry (superset of the cog registry, same JSON schema + a `wasm_module` field).
+- **Lifecycle**: `cognitum-agent` (ADR-116) already handles OTA update, signature verification, and sandboxed execution. HOMECORE-PLUGINS reuses this lifecycle by treating each HOMECORE integration as a cog with a WASM payload.
+- **Ed25519 signatures**: every plugin `.wasm` is signed with the publisher's Ed25519 key. The HOMECORE host verifies the signature before compiling the module (same pattern as ADR-028 witness chain).
+
+---
+
+## 3. Manifest schema
+
+HOMECORE's manifest is a superset of HA's `manifest.json`. Fields not present in HA are marked **[HOMECORE]**.
+
+```json
+{
+  "domain": "mqtt",
+  "name": "MQTT",
+  "version": "2025.1.0",
+  "documentation": "https://www.home-assistant.io/integrations/mqtt/",
+  "iot_class": "local_push",
+  "config_flow": true,
+  "dependencies": [],
+  "quality_scale": "platinum",
+  "wasm_module": "mqtt.wasm",
+  "wasm_module_hash": "sha256:abcdef...",
+  "wasm_module_sig": "ed25519:<base64>",
+  "publisher_key": "<base64 Ed25519 public key>",
+  "min_homecore_version": "0.1.0",
+  "host_imports_required": ["hc_state_get", "hc_state_set", "hc_event_fire", "hc_service_call"],
+  "homecore_permissions": ["state:write:sensor.*", "state:read:*", "service:call:homeassistant.*"],
+  "cog_id": "homecore-mqtt-2025.1.0"
+}
+```
+
+**[HOMECORE]** fields:
+- `wasm_module` — relative path to the `.wasm` binary
+- `wasm_module_hash` — SHA-256 of the wasm binary; verified before execution
+- `wasm_module_sig` — Ed25519 signature of the wasm binary hash
+- `publisher_key` — Ed25519 public key of the publisher
+- `min_homecore_version` — minimum HOMECORE version required
+- `host_imports_required` — subset of host functions the module needs (security auditable)
+- `homecore_permissions` — coarse-grained permission claims (glob patterns); future: enforcement via RUVIEW-POLICY layer (ADR-124 §4.1a)
+- `cog_id` — Seed app registry ID for the cog distribution
+
+---
+
+## 4. HA-side reference table
+
+| HA module / file | What it does | HOMECORE preserves | Changes | Drops |
+|---|---|---|---|---|
+| `homeassistant/components/<domain>/manifest.json` | Integration metadata | `domain`, `name`, `version`, `iot_class`, `config_flow`, `dependencies`, `quality_scale`, `documentation` | Add WASM fields; remove `requirements` (no pip) | `requirements` (pip packages) |
+| `homeassistant/loader.py` | Loads Python modules; installs pip requirements | Manifest parsing; dependency resolution between cogs | WASM module loading via Wasmtime; no pip | Python `importlib`, pip subprocess |
+| `homeassistant/components/<domain>/__init__.py` | `async_setup` + `async_setup_entry` | `setup_entry` hook (per config entry) | WASM export function instead of Python async function | Python module structure |
+| `homeassistant/config_entries.py` | Config entry lifecycle management | `ConfigEntry` struct: `entry_id`, `domain`, `title`, `data`, `options`, `state`, `version` | Rust struct; async state machine | Python class hierarchy; `FlowManager` |
+| `homeassistant/components/<domain>/config_flow.py` | UI configuration flow | Config flow metadata (steps, schemas) | JSON-schema-based flow descriptor shipped in manifest | `voluptuous`, Python UI flow runtime |
+
+---
+
+## 5. WASM ABI specification
+
+### 5.1 Host functions imported by plugins
+
+```
+hc_state_get(key_ptr: i32, key_len: i32, out_ptr: i32, out_cap: i32) → i32
+  // Returns JSON-encoded State into out_ptr buffer; returns bytes written or -1 if not found.
+
+hc_state_set(entity_ptr: i32, entity_len: i32, state_ptr: i32, state_len: i32,
+             attrs_ptr: i32, attrs_len: i32) → i32
+  // Sets state for entity_id; returns 0 on success, negative on error.
+
+hc_event_fire(event_type_ptr: i32, event_type_len: i32,
+              event_data_ptr: i32, event_data_len: i32) → i32
+  // Fires a domain event.
+
+hc_service_call(domain_ptr: i32, domain_len: i32,
+                service_ptr: i32, service_len: i32,
+                data_ptr: i32, data_len: i32) → i32
+  // Calls a service synchronously from the plugin's perspective (async on the host).
+
+hc_entity_register(entry_ptr: i32, entry_len: i32) → i32
+  // Registers an entity with the entity registry; entry is JSON-encoded EntityEntry.
+
+hc_log(level: i32, msg_ptr: i32, msg_len: i32) → void
+  // Structured log output; level: 0=debug, 1=info, 2=warn, 3=error.
+```
+
+### 5.2 WASM exports required by host
+
+```
+setup_entry(config_entry_ptr: i32, config_entry_len: i32) → i32
+  // Called when a config entry is set up. config_entry is JSON-encoded ConfigEntry.
+  // Returns 0 on success, negative error code on failure.
+
+call_service_handler(domain_ptr: i32, domain_len: i32,
+                     service_ptr: i32, service_len: i32,
+                     data_ptr: i32, data_len: i32) → i32
+  // Called when a service registered by this plugin is invoked.
+
+receive_event(event_type_ptr: i32, event_type_len: i32,
+              event_data_ptr: i32, event_data_len: i32) → i32
+  // Called when an event type the plugin subscribed to fires.
+  // Subscription is declared in manifest `subscribed_events` array.
+
+alloc(size: i32) → i32
+  // Host calls this to allocate a buffer inside the WASM linear memory
+  // before writing data for a callback. Required for ABI memory passing.
+
+dealloc(ptr: i32, size: i32) → void
+  // Host calls this to free a previously allocated buffer.
+```
+
+### 5.3 Execution model
+
+Each WASM module instance runs in its own Wasmtime `Store`. The host calls WASM exports from a dedicated Tokio task per plugin. Incoming events are queued in an `mpsc::Sender<PluginEvent>` per plugin; the plugin task drains the queue and calls `receive_event`. This isolates plugin execution from the hot state-machine path.
+
+---
+
+## 6. Public API parity table
+
+| HA integration pattern | HOMECORE WASM equivalent |
+|---|---|
+| `async_setup_entry(hass, entry)` Python async function | `setup_entry(config_entry_json)` WASM export |
+| `hass.states.async_set(entity_id, state, attrs)` | `hc_state_set(...)` host import |
+| `hass.states.get(entity_id)` | `hc_state_get(...)` host import |
+| `hass.bus.async_fire(event_type, data)` | `hc_event_fire(...)` host import |
+| `hass.services.async_call(domain, service, data)` | `hc_service_call(...)` host import |
+| `hass.services.async_register(domain, service, handler)` | Declared in manifest `registered_services`; `call_service_handler` WASM export handles all |
+| `async_track_state_change(hass, entity_ids, callback)` | Declared in manifest `subscribed_state_entities`; `receive_event` called with `state_changed` events |
+| Config flow `FlowManager.async_init()` | Config flow metadata in manifest; UI calls HOMECORE-API `/config/config_entries/flow` |
+| `ConfigEntry.entry_id`, `.domain`, `.data`, `.options` | Same fields in `ConfigEntry` JSON passed to `setup_entry` |
+
+---
+
+## 7. Phased implementation plan
+
+### P1 — WASM host skeleton (2 weeks)
+
+- [ ] Create `v2/crates/homecore-plugins/` workspace member.
+- [ ] Wasmtime dependency; compile a trivial WASM module that calls `hc_log` and verify it runs.
+- [ ] Define the host function ABI in a `host_api.rs` module; write the Wasmtime `Linker` registration for all 6 host functions.
+- [ ] Manifest schema: `serde`-deserialised `Manifest` struct; validate required fields.
+- [ ] Hash + Ed25519 signature verification of `.wasm` bytes before compilation.
+
+### P2 — State machine bridge (2 weeks)
+
+- [ ] Wire `hc_state_get` and `hc_state_set` to the `homecore` state machine (ADR-127).
+- [ ] Wire `hc_event_fire` to the event bus.
+- [ ] Wire `hc_service_call` to the service registry.
+- [ ] Wire `hc_entity_register` to the entity registry.
+- [ ] Write a test plugin in Rust compiled to WASM: registers one entity, writes its state via host imports, verifies the state machine sees the update.
+
+### P3 — Config entry lifecycle + hot-load (2 weeks)
+
+- [ ] `ConfigEntryManager` — tracks loaded plugins, calls `setup_entry` on new config entries, handles teardown.
+- [ ] Hot-load: watch a directory for new `.wasm` + `manifest.json` pairs; load without hub restart.
+- [ ] Wasmtime compiled module cache: serialize to `.cwasm` after first JIT compile; deserialize on subsequent loads (sub-1 ms plugin restart).
+- [ ] Integration test: MQTT plugin loaded at runtime, registers `sensor.test` entity, state readable via HOMECORE-API.
+
+### P4 — Cog registry integration (1 week)
+
+- [ ] Fetch plugin from Seed app registry `app-registry.json`; verify Ed25519 signature against publisher key.
+- [ ] Expose `/api/homecore/plugins` REST endpoint (HOMECORE-API ADR-130 extension): list loaded plugins, load new plugin by URL, unload plugin.
+- [ ] First-party plugin: ship an MQTT plugin WASM module that provides the same function as HA's `homeassistant/components/mqtt/`.
+
+### P5 — Permission enforcement (1 week)
+
+- [ ] Enforce `homecore_permissions` claims: reject `hc_state_set` calls that write to entities outside the plugin's declared `state:write:*` pattern.
+- [ ] Log all permission denials to the Ed25519 witness chain.
+- [ ] Expose permission audit via `/api/homecore/plugins/<domain>/audit`.
+
+---
+
+## 8. Risks
+
+| Risk | Likelihood | Severity | Mitigation | Cross-ADR impact |
+|---|---|---|---|---|
+| **ADR-127 state machine not stable** — plugin ABI calls into the state machine; if the API changes, all plugins break | High (early phase) | High | Freeze the `hc_state_get`/`hc_state_set` ABI in P1; never change pointer/length convention; version the host ABI in the manifest `min_homecore_version` | ADR-127 must freeze public API before ADR-128 P2 begins |
+| **Wasmtime binary size** — adding Wasmtime to HOMECORE adds ~15 MB to the binary on Pi 5 | Medium | Medium | Use Cranelift JIT only; skip LLVM optimizer. Alternative: `wasm3` feature flag (~50 kB) for constrained hardware | ADR-126: binary size target < 50 MB idle RAM; Wasmtime itself uses ~5 MB RAM at runtime |
+| **ABI memory overhead** — every state read/write from a plugin must JSON-encode/decode through shared memory | Medium | Medium | Cap state value size at 64 kB; use a pool allocator for ABI buffers; profile on Pi 5 at 10 state writes/s per plugin | ADR-130: REST API reads state from DashMap directly, bypassing plugin ABI — no overhead there |
+| **Community plugin trust** — WASM sandbox prevents crashes but cannot prevent malicious plugins from calling `hc_service_call` to turn off all lights | Medium | High | `homecore_permissions` permission claims (P5); future: RUVIEW-POLICY enforcement (ADR-124 §4.1a) for biometric data access | ADR-124 RUVIEW-POLICY must be made aware of HOMECORE as a policy principal |
+
+---
+
+## 9. Open questions
+
+**Q1**: Should the WASM module ABI use JSON-over-shared-memory (current proposal) or a more compact binary encoding (MessagePack, FlatBuffers)? JSON is simpler to debug and matches HA's existing JSON-everywhere convention; MessagePack cuts ABI overhead by ~4×. Decide before P2 implementation.
+
+**Q2**: HA's `config_flow.py` is a multi-step UI wizard with voluptuous schema validation. HOMECORE's config flow is described in the manifest JSON. Is a JSON-schema-based config flow sufficient for the 100 most popular integrations, or do some require imperative step logic that can't be expressed declaratively?
+
+**Q3**: Should existing Python HA community integrations be automatically compilable to WASM via a transpilation layer (e.g. CPython compiled to WASM via Pyodide), or should HOMECORE accept only natively compiled WASM modules? Pyodide+WASM would make migration easier but adds ~25 MB per plugin and loses the performance argument.
+
+**Q4**: The `host_imports_required` manifest field lists which host functions the plugin needs. Should this be verified at load time (reject plugin that imports undeclared functions) or only advisory? Strict enforcement prevents surprises; advisory aids migration.
+
+---
+
+## 10. References
+
+### HA upstream
+
+- `homeassistant/loader.py` — integration loader; pip requirement installation; `async_setup_entry` invocation
+- `homeassistant/config_entries.py` — `ConfigEntry`, `ConfigEntryState`, `ConfigEntriesError`, `FlowManager`
+- `homeassistant/components/mqtt/manifest.json` — canonical example of HA manifest structure
+- `homeassistant/components/mqtt/__init__.py` — `async_setup_entry` pattern for a complex integration with services
+- `homeassistant/components/mqtt/config_flow.py` — multi-step config flow example
+
+### This repo
+
+- `docs/adr/ADR-102-edge-module-registry.md` — cog registry architecture; `app-registry.json` schema
+- `docs/adr/ADR-100-cog-packaging-specification.md` — cog packaging spec; Ed25519 signing
+- `docs/adr/ADR-101-pose-estimation-cog.md` — cog lifecycle precedent
+- `docs/adr/ADR-127-homecore-state-machine-rust.md` — state machine ABI that plugins call
+- `docs/adr/ADR-126-ruview-native-ha-port-master.md` — §5.7 "do not port" list (legacy Python integrations)

docs/adr/ADR-129-homecore-automation-engine.md

@@ -0,0 +1,212 @@
+# ADR-129: HOMECORE-AUTO — Automation engine, script runner, and template evaluator
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-25 |
+| **Deciders** | ruv |
+| **Codename** | **HOMECORE-AUTO** |
+| **Relates to** | [ADR-126](ADR-126-ruview-native-ha-port-master.md) (HOMECORE master), [ADR-127](ADR-127-homecore-state-machine-rust.md) (HOMECORE-CORE), [ADR-129 implicit](ADR-129-homecore-automation-engine.md), [ADR-133](ADR-133-homecore-assist-ruflo.md) (HOMECORE-ASSIST) |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+Home Assistant's automation system is defined across three components:
+
+1. **`homeassistant/components/automation/__init__.py`** — the automation manager: loads automation YAML, evaluates trigger platforms, calls the script executor when conditions pass. The core class is `AutomationEntity` which extends `ToggleEntity`. Automations are themselves HA entities with `state = on/off`.
+
+2. **`homeassistant/components/script/__init__.py`** — the script executor: a sequence of actions (service calls, conditions, delays, events, template variables, `choose`, `parallel`, `repeat`, `wait_for_trigger`). Scripts are entities too (`ScriptEntity` extends `ToggleEntity`). The execution engine supports five run modes: `single`, `restart`, `queued`, `parallel`, `ignore_first`.
+
+3. **`homeassistant/helpers/template.py`** — HA's Jinja2 customisation layer: wraps the upstream `jinja2` Python library with HA-specific globals (`states()`, `is_state()`, `state_attr()`, `now()`, `utcnow()`, `as_timestamp()`, `distance()`, `closest()`, etc.), custom filters (`regex_match`, `round`, `timestamp_local`), and a sandboxed `Environment` that prevents file I/O and dangerous evaluations.
+
+### 1.1 Scale and surface
+
+HA's automation YAML supports:
+- **17 trigger platforms** (state, time, numeric_state, template, event, homeassistant, zone, geo_location, device, calendar, conversation, mqtt, webhook, tag, sun, time_pattern, persistent_notification)
+- **7 condition types** (state, numeric_state, time, template, zone, sun, device)
+- **22+ action types** (call_service, delay, wait_template, fire_event, device_action, choose, if, parallel, repeat, sequence, stop, set_conversation_response, ...)
+
+The YAML schema is validated by `voluptuous` schemas defined in `homeassistant/helpers/config_validation.py` (~5,000 lines).
+
+### 1.2 Jinja2 is the critical surface
+
+HA templates are used not only in automations but in dashboard cards, notification messages, and script variables. The HA frontend sends template strings to the API's `POST /api/template` endpoint for server-side evaluation. Any HOMECORE instance that claims API compatibility must execute Jinja2-compatible templates or existing automations will break.
+
+Full Jinja2 support in Rust without Python is non-trivial. The approach chosen here uses a **WASM-compiled MiniJinja** (the `minijinja` Rust crate compiled with HA-specific extension functions) rather than a full Python Jinja2 re-implementation.
+
+---
+
+## 2. Decision
+
+Build the `homecore-automation` crate with three components:
+
+1. **YAML parser**: `serde_yaml` + custom validator that parses HA's automation and script YAML into typed Rust structs. Validates trigger, condition, and action schemas at load time.
+2. **Trigger evaluator**: a Tokio task per loaded automation that subscribes to the HOMECORE event bus (ADR-127) and evaluates trigger conditions in Rust. When a trigger fires and conditions pass, it enqueues the automation action sequence.
+3. **Action executor**: a script runner that processes action sequences. Service calls go to the HOMECORE service registry. Delays use `tokio::time::sleep`. Template evaluation uses MiniJinja. Complex conditions (optional) can route to a ruflo agent (ADR-133).
+
+### 2.1 Template evaluator: MiniJinja + HA-compatible extension functions
+
+`minijinja` (crates.io version 2.x) is a production-quality Jinja2 implementation in pure Rust. It is missing 5–10% of Jinja2's surface area (notably: `{% block %}` / `{% extends %}` template inheritance, and some Jinja2 Python-specific filters), but covers 100% of HA's automation template usage.
+
+HA-specific globals added on top of MiniJinja:
+
+```rust
+env.add_global("states", minijinja::Value::from_function(ha_states_global));
+env.add_global("is_state", minijinja::Value::from_function(ha_is_state_global));
+env.add_global("state_attr", minijinja::Value::from_function(ha_state_attr_global));
+env.add_global("now", minijinja::Value::from_function(ha_now_global));
+env.add_global("utcnow", minijinja::Value::from_function(ha_utcnow_global));
+env.add_global("as_timestamp", minijinja::Value::from_function(ha_as_timestamp_global));
+env.add_global("distance", minijinja::Value::from_function(ha_distance_global));
+env.add_global("iif", minijinja::Value::from_function(ha_iif_global));
+```
+
+Each global function reads from the HOMECORE state machine (ADR-127) via an `Arc<StateMachine>` captured at environment construction time. Template evaluation is synchronous (MiniJinja is sync) but runs in a `tokio::task::spawn_blocking` wrapper to avoid blocking the async executor.
+
+### 2.2 WASM evaluator for untrusted template strings
+
+Dashboard card templates submitted via `POST /api/template` come from user-authored YAML, not first-party code. HA evaluates these in the same Python process, relying on Jinja2's `SandboxedEnvironment` for safety. HOMECORE uses a **WASM-sandboxed MiniJinja** evaluator:
+
+- A single WASM module (`homecore-template-eval.wasm`) is compiled from the MiniJinja crate with the HA extension globals stubbed to call host functions.
+- Template strings are passed into the WASM module via the HOMECORE plugin ABI (ADR-128 §5.1).
+- The WASM sandbox prevents file I/O, network access, and infinite loops (via Wasmtime fuel metering — 100,000 instructions per template evaluation).
+- Result is returned as a string to the HOMECORE API.
+
+This is the same Wasmtime host already used for integration plugins (ADR-128) — no additional WASM runtime dependency.
+
+---
+
+## 3. HA-side reference table
+
+| HA module / file | What it does | HOMECORE preserves | Changes | Drops |
+|---|---|---|---|---|
+| `automation/__init__.py` `AutomationEntity` | Automation as a toggle entity (on/off) with triggers/conditions/actions | Automation is a HOMECORE entity with same on/off state semantics | Rust struct `AutomationEntity` implementing `HomeCoreEntity` trait | Python class hierarchy, voluptuous schema |
+| `automation/__init__.py` `TriggerActionConfig` | Trigger → condition → action pipeline | Full trigger/condition/action pipeline | Typed Rust enums per trigger platform | Python dict-based config |
+| `automation/trigger.py` | Delegates to per-platform trigger modules (`homeassistant/components/<platform>/trigger.py`) | Same per-platform dispatch | Rust match arm per trigger type | Python dynamic module import |
+| `script/__init__.py` `Script` | Script entity + action sequence executor | Same 22 action types | Rust enum `Action` with all variants | Python asyncio coroutines |
+| `script/__init__.py` run modes | `single`, `restart`, `queued`, `parallel`, `ignore_first` | All 5 run modes | Tokio-based concurrency control (semaphore for `queued`, `parallel`) | Python asyncio task management |
+| `helpers/template.py` `Template` | Jinja2 evaluation + HA globals | Same HA global function names and signatures | MiniJinja instead of Python Jinja2; WASM sandbox for user templates | Python `jinja2` library; `voluptuous` coercions in templates |
+| `helpers/config_validation.py` | `cv.template`, `cv.entity_id`, time period validators | Same validation semantics | Rust custom deserializers implementing `serde::Deserialize` | voluptuous; Python regex |
+| `components/automation/blueprint.py` | Blueprint system (reusable automation templates with input variables) | Blueprint YAML schema + variable substitution | Pure Rust YAML substitution | Python Blueprint class hierarchy |
+
+---
+
+## 4. Public API parity table
+
+| HA automation surface | HOMECORE equivalent |
+|---|---|
+| `automation.trigger` (state, time, numeric_state, template, event, ...) | `Trigger` enum with variants for all 17 HA trigger platforms |
+| `automation.condition` (state, numeric_state, time, template, zone, sun, device) | `Condition` enum with variants for all 7 condition types |
+| `automation.action` — call_service, delay, fire_event, choose, if, parallel, repeat, wait_template, stop | `Action` enum with variants for all 22 action types |
+| `script.run_mode` — single, restart, queued, parallel | `RunMode` enum with 5 variants |
+| `POST /api/template` (REST eval of a template string) | Same endpoint in HOMECORE-API (ADR-130); backed by WASM-sandboxed MiniJinja |
+| Automation entity: `state = on|off`, `attributes.last_triggered`, `attributes.id` | `AutomationEntity` struct with same attribute names |
+| `automation.trigger` service (manually trigger an automation) | `homecore.automation.trigger` service; same service call data schema |
+| `automation.reload` service (reload automations.yaml) | `homecore.automation.reload` service |
+| `automation.toggle` service | Standard `HomeCoreEntity` toggle service |
+| Blueprint YAML with `blueprint:` key and `input:` variables | Blueprint parsed by HOMECORE YAML parser; same substitution semantics |
+
+---
+
+## 5. Trigger platform mapping
+
+| HA trigger platform | HOMECORE implementation |
+|---|---|
+| `state` | Subscribe to `state_changed` broadcast; match `entity_id`, `from`, `to`, `for` |
+| `numeric_state` | Subscribe to `state_changed`; parse state as f64; compare against `above`/`below` |
+| `time` | `tokio::time::sleep_until` to next occurrence; re-arm after fire |
+| `time_pattern` | Cron-style evaluation using `cron` crate; tokio timer task |
+| `template` | Re-evaluate template on every `state_changed`; fire when template transitions from false to true |
+| `event` | Subscribe to named domain event on event bus |
+| `homeassistant` (start/stop) | Subscribe to `HomeAssistantStart` / `HomeAssistantStop` typed events |
+| `zone` | Subscribe to `zone.entered` / `zone.left` events from the device tracker integration |
+| `mqtt` | Subscribe to MQTT topic via the MQTT plugin (ADR-128); fire event when message arrives |
+| `webhook` | HOMECORE-API registers a webhook path; fires event on POST |
+| `calendar` | Subscribe to calendar event from calendar integration |
+| `conversation` | Subscribe to `conversation.user_input` event; match intent/sentence |
+| `geo_location` | Subscribe to `geo_location.entered` / `geo_location.left` |
+| `sun` | Compute sunrise/sunset from latitude/longitude in `homecore.config`; tokio timer |
+| `device` | Delegate to integration-specific device trigger via WASM plugin |
+| `persistent_notification` | Subscribe to `persistent_notification.create` event |
+| `tag` | Subscribe to `tag.scanned` event from NFC/QR integration |
+
+---
+
+## 6. Phased implementation plan
+
+### P1 — YAML parser (2 weeks)
+
+- [ ] Define Rust enums for `Trigger`, `Condition`, `Action`, `RunMode` with `serde` deserialization.
+- [ ] Parse an existing `automations.yaml` from a real HA install with zero errors (test fixture).
+- [ ] Validator: reject unknown trigger platforms with a clear error message.
+- [ ] Unit tests: parse 50 automation fixtures covering all 17 trigger types and 22 action types.
+
+### P2 — State and event triggers (2 weeks)
+
+- [ ] Implement `state`, `numeric_state`, `event`, `homeassistant`, `time`, `time_pattern` trigger evaluators.
+- [ ] `ConditionEvaluator` for `state`, `numeric_state`, `time` conditions.
+- [ ] `ActionExecutor` for `call_service`, `delay`, `fire_event`, `stop` action types.
+- [ ] Integration test: load one automation (state trigger → call_service action); verify fires correctly when state changes.
+
+### P3 — Full action set + MiniJinja (3 weeks)
+
+- [ ] MiniJinja + HA extension globals; `POST /api/template` endpoint wired to WASM evaluator.
+- [ ] `template` trigger + `template` condition evaluators.
+- [ ] `choose`, `if`, `parallel`, `repeat`, `wait_template`, `sequence` action types.
+- [ ] All 5 `RunMode` variants (concurrency control via Tokio semaphore/mutex).
+- [ ] Integration test: `automations.yaml` from ADR-134 migration fixture loads and runs correctly.
+
+### P4 — Blueprint system + ruflo agent condition (1 week)
+
+- [ ] Blueprint YAML parser + input variable substitution.
+- [ ] Optional ruflo agent condition: `condition: ruflo_agent` with `query: "..."` routes to ruflo LLM (ADR-133 §3.3); gated by RUVIEW-POLICY.
+- [ ] `automation.reload` service.
+- [ ] Performance benchmark: 100 automations loaded; 100 state changes/s; verify trigger evaluation stays < 5 ms per state change.
+
+---
+
+## 7. Risks
+
+| Risk | Likelihood | Severity | Mitigation | Cross-ADR impact |
+|---|---|---|---|---|
+| **MiniJinja gaps** — some HA templates use Jinja2 features MiniJinja doesn't support (template inheritance, Python-specific filters) | Medium | Medium | Document the MiniJinja-vs-Jinja2 delta before P3 ships; provide a migration guide for affected templates; defer the 5% of templates that fail to a Python-compat shim (ADR-134) | ADR-134: migration tool must warn on templates that use unsupported Jinja2 features |
+| **Template performance** — synchronous MiniJinja in `spawn_blocking` adds overhead under high automation fan-out | Low | Low | Benchmark at 50 automations each evaluating a template trigger on every state_changed (worst case); if > 2 ms add a template-evaluation cache keyed by (template_hash, relevant_entity_states) | ADR-127: state machine must expose a "relevant states snapshot" API for caching |
+| **ADR-127 state machine API not frozen** — trigger evaluators call `hass.states.all()` and subscribe to broadcasts; if those APIs change, trigger code must update | High (early) | High | ADR-127 must freeze its public API before ADR-129 P2 begins; use a `HomeCoreRef` trait (version 1.0 stable) | ADR-127 owns this dependency |
+| **Complex action YAML** — real-world automations use deeply nested `choose`/`if`/`parallel` blocks; parsing is non-trivial | Medium | Medium | Use a corpus of 500 public HA automations from the HA community (MIT-licensed) as parse-test fixtures in CI | None |
+
+---
+
+## 8. Open questions
+
+**Q1**: MiniJinja does not support all Python-specific Jinja2 filters (e.g. `map`, `select`, `reject` with Python lambda arguments). HA's `homeassistant/helpers/template.py` adds custom equivalents of several of these. How many real-world HA automations use these filters? A corpus analysis of public HA configs on GitHub would answer this before P3 implementation.
+
+**Q2**: HA's `template` trigger supports a `value_template` that can reference `trigger.to_state`, `trigger.from_state`, and `trigger.for`. This requires passing trigger context into the template evaluation scope. Is this context threading straightforward in MiniJinja, or does it require a custom context type?
+
+**Q3**: The `conversation` trigger in HA uses the Assist pipeline's intent matching to fire automations based on voice commands. HOMECORE-ASSIST (ADR-133) owns the pipeline. Should the `conversation` trigger be implemented in ADR-129 (automation engine dependency on ADR-133) or in ADR-133 (assist pipeline fires automation events that ADR-129 listens to)?
+
+**Q4**: HA blueprints have a community sharing mechanism (blueprint.exchange). Should HOMECORE support importing blueprints from HA's blueprint exchange directly, or only local blueprints?
+
+---
+
+## 9. References
+
+### HA upstream
+
+- `homeassistant/components/automation/__init__.py` — `AutomationEntity`, `AutomationConfig`, trigger/condition/action pipeline
+- `homeassistant/components/script/__init__.py` — `Script`, `ScriptEntity`, run modes, action sequence execution
+- `homeassistant/helpers/template.py` — `Template` class, `TemplateEnvironment`, all HA-specific Jinja2 globals and filters
+- `homeassistant/helpers/config_validation.py` — voluptuous schema definitions for all automation/script YAML elements
+- `homeassistant/components/automation/blueprint.py` — Blueprint input substitution
+
+### This repo
+
+- `docs/adr/ADR-127-homecore-state-machine-rust.md` — state machine and event bus that triggers subscribe to
+- `docs/adr/ADR-133-homecore-assist-ruflo.md` — ruflo agent condition + conversation trigger dependency
+- `docs/adr/ADR-134-homecore-migration-from-python-ha.md` — migration tool reads `automations.yaml`
+
+### External
+
+- [minijinja crates.io](https://crates.io/crates/minijinja) — Jinja2-compatible template engine in Rust
+- [HA Automation Templating docs](https://www.home-assistant.io/docs/automation/templating/) — HA-specific template globals reference

docs/adr/ADR-130-homecore-rest-websocket-api.md

@@ -0,0 +1,218 @@
+# ADR-130: HOMECORE-API — Wire-compatible REST and WebSocket API
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-25 |
+| **Deciders** | ruv |
+| **Codename** | **HOMECORE-API** |
+| **Relates to** | [ADR-126](ADR-126-ruview-native-ha-port-master.md) (HOMECORE master), [ADR-127](ADR-127-homecore-state-machine-rust.md) (HOMECORE-CORE), [ADR-055](ADR-055-integrated-sensing-server.md) (sensing-server Axum pattern), [ADR-124](ADR-124-rvagent-mcp-ruvector-npm-integration.md) (SENSE-BRIDGE — bearer auth pattern) |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+Home Assistant's HTTP and WebSocket APIs are the primary interface for every non-frontend client: the iOS companion app, the Android companion app, HACS, Node-RED, the `homeassistant` Python client library, ESPHome native API clients, external automation scripts, and the hundreds of third-party HA dashboard projects.
+
+The API surface is defined in two Python modules:
+
+1. **`homeassistant/components/api/__init__.py`** — 24 REST API routes mounted at `/api/`. Key routes: `GET /api/`, `GET /api/states`, `GET /api/states/<entity_id>`, `POST /api/states/<entity_id>`, `GET /api/events`, `POST /api/events/<event_type>`, `GET /api/services`, `POST /api/services/<domain>/<service>`, `GET /api/error_log`, `GET /api/config`, `POST /api/template`, `POST /api/check_config`, `GET /api/history/period/<datetime>` (deprecated — recorder), `POST /api/logbook/` (deprecated — recorder).
+
+2. **`homeassistant/components/websocket_api/`** — the WebSocket API handler (`connection.py` handles auth handshake; `commands.py` handles 30+ command types). Key commands: `auth`, `subscribe_events`, `unsubscribe_events`, `call_service`, `get_states`, `get_services`, `get_config`, `subscribe_trigger`, `render_template`, `validate_config`, `subscribe_entities` (entity registry updates), `config/entity_registry/list`, and many more.
+
+### 1.1 Auth model
+
+HA uses **long-lived access tokens (LLAT)** as the primary auth mechanism for non-UI clients. Tokens are created in the HA user profile UI and stored in `.storage/auth`. The REST API accepts `Authorization: Bearer <token>` or the `api_password` legacy header (deprecated since HA 2022.x). The WebSocket API requires an `auth` message with `access_token` as the first message after connection.
+
+### 1.2 Why wire-compat matters
+
+The iOS and Android HA companion apps (>100,000 installs combined) hardcode the HA API paths and WebSocket command schemas. Any implementation that deviates from the exact JSON schemas causes the apps to fail silently — not with a meaningful error, but by returning empty entity lists or missing state updates. Wire-compat is therefore a hard requirement, not a nice-to-have.
+
+The baseline for compatibility is **HA 2025.1** (the version that introduced SQLite recorder schema version 48). Any HOMECORE instance claiming compliance with this ADR must pass the companion app integration test suite.
+
+---
+
+## 2. Decision
+
+Implement the `homecore-api` crate as an Axum-based server that replicates the HA REST and WebSocket API on port 8123. The implementation is informed by — but does not copy — `homeassistant/components/api/__init__.py` and `homeassistant/components/websocket_api/`.
+
+The server reuses the Axum + Tokio architecture established in `v2/crates/wifi-densepose-sensing-server/src/main.rs` and its bearer auth pattern (`v2/crates/wifi-densepose-sensing-server/src/bearer_auth.rs`).
+
+### 2.1 REST API route table
+
+| Route | Method | HA source line (approx.) | HOMECORE status |
+|---|---|---|---|
+| `/api/` | GET | `api/__init__.py:74` | P2 — returns `{ "message": "API running." }` |
+| `/api/config` | GET | `api/__init__.py:97` | P2 — returns `homecore.config` as JSON |
+| `/api/states` | GET | `api/__init__.py:116` | P2 — returns `hass.states.all()` as JSON array |
+| `/api/states/<entity_id>` | GET | `api/__init__.py:130` | P2 |
+| `/api/states/<entity_id>` | POST | `api/__init__.py:145` | P2 — writes state; fires `state_changed` |
+| `/api/events` | GET | `api/__init__.py:168` | P3 |
+| `/api/events/<event_type>` | POST | `api/__init__.py:180` | P3 — fires domain event |
+| `/api/services` | GET | `api/__init__.py:192` | P2 |
+| `/api/services/<domain>/<service>` | POST | `api/__init__.py:206` | P2 |
+| `/api/template` | POST | `api/__init__.py:222` | P3 — WASM MiniJinja evaluator (ADR-129) |
+| `/api/check_config` | POST | `api/__init__.py:240` | P4 |
+| `/api/error_log` | GET | `api/__init__.py:252` | P3 |
+| `/api/history/period/<datetime>` | GET | `api/__init__.py:270` | P4 — recorder query (ADR-132) |
+| `/api/logbook/` | POST | `api/__init__.py:310` | P4 — recorder query |
+| `/api/camera_proxy/<entity_id>` | GET | `api/__init__.py:330` | P4 — proxy to camera integration |
+| `/api/calendar/<entity_id>` | GET | `api/__init__.py:348` | P4 |
+| `/api/webhook/<webhook_id>` | POST/GET | `api/__init__.py:368` | P3 — fires `webhook.<id>` event |
+| `/api/intent/handle` | POST | `api/__init__.py:400` | P4 — HOMECORE-ASSIST (ADR-133) |
+| `/auth/token` | POST | `auth/providers/__init__.py` | P2 — issue LLAT from username/password |
+| `/auth/authorize` | GET/POST | `auth/providers/__init__.py` | P3 — OAuth2 flow |
+| `/frontend/` static assets | GET | `frontend/__init__.py` | P1 — serve HA Python frontend static files until ADR-131 ships |
+
+### 2.2 WebSocket API command table
+
+| WS command type | HA source | HOMECORE status |
+|---|---|---|
+| `auth` (handshake) | `websocket_api/connection.py:55` | P2 |
+| `subscribe_events` | `websocket_api/commands.py:120` | P2 |
+| `unsubscribe_events` | `websocket_api/commands.py:145` | P2 |
+| `call_service` | `websocket_api/commands.py:160` | P2 |
+| `get_states` | `websocket_api/commands.py:200` | P2 |
+| `get_services` | `websocket_api/commands.py:218` | P2 |
+| `get_config` | `websocket_api/commands.py:230` | P2 |
+| `subscribe_trigger` | `websocket_api/commands.py:250` | P3 |
+| `render_template` | `websocket_api/commands.py:280` | P3 |
+| `validate_config` | `websocket_api/commands.py:300` | P3 |
+| `subscribe_entities` | `websocket_api/commands.py:320` | P3 — entity registry update stream |
+| `config/entity_registry/list` | `websocket_api/commands.py:370` | P3 |
+| `config/entity_registry/update` | `websocket_api/commands.py:400` | P3 |
+| `config/area_registry/list` | `websocket_api/commands.py:450` | P3 |
+| `config/device_registry/list` | `websocket_api/commands.py:480` | P3 |
+| `config/config_entries/list` | `websocket_api/commands.py:510` | P3 |
+| `lovelace/config` (dashboard) | `lovelace/dashboard.py` | P4 — reads from HOMECORE storage |
+| `media_player/*` | `websocket_api/commands.py:600` | P4 |
+
+### 2.3 Auth implementation
+
+HOMECORE-API implements long-lived access tokens as JWTs signed with an Ed25519 key (generated at first startup, stored in `.homecore/auth_key.pem`). Token format:
+
+```json
+{
+  "sub": "<user_id>",
+  "iss": "homecore",
+  "iat": <unix_timestamp>,
+  "exp": <unix_timestamp or null for LLAT>,
+  "type": "long_lived_access_token"
+}
+```
+
+The HA companion app sends `Authorization: Bearer <token>` on every REST request. The WebSocket auth handshake sends `{ "type": "auth", "access_token": "<token>" }`. Both paths validate the JWT against the stored Ed25519 key.
+
+Legacy `api_password` is deliberately not supported (removed in HA 2022.x and never properly secure).
+
+---
+
+## 3. HA-side reference table
+
+| HA module / file | What it does | HOMECORE preserves | Changes | Drops |
+|---|---|---|---|---|
+| `components/api/__init__.py` | 24 REST routes + JSON response schemas | All response schemas byte-compatible with HA 2025.1 | Axum router instead of HA's custom HTTP component; `serde_json` instead of Python `json` | Python HTTP request context; HA's built-in CORS middleware (replicated in Axum) |
+| `components/websocket_api/connection.py` | WS auth handshake; per-connection state; message dispatch | Auth handshake flow: `auth_required` → `auth` message → `auth_ok` or `auth_invalid` | Axum `WebSocketUpgrade` extractor; per-connection `tokio::task` | Python asyncio message handling |
+| `components/websocket_api/commands.py` | 30+ WS command handlers | All command type strings; response envelope `{ id, type, result }` or error `{ id, type, error: { code, message } }` | Rust match dispatch; Tokio broadcast receiver per subscription | Python class-based command handler registration |
+| `auth/providers/__init__.py` | Auth providers; LLAT issuance; OAuth2 flow | LLAT issuance; token validation | Ed25519 JWT instead of HA's custom token serializer; same token `type` field values | Nabu Casa cloud auth; multi-provider auth chain |
+| `components/http/__init__.py` | Aiohttp-based HTTP server setup; CORS; trusted proxies | CORS headers; `X-Forwarded-For` trusted proxy handling | Axum Tower middleware | Aiohttp; Python SSL context |
+
+---
+
+## 4. Public API parity table
+
+| HA API surface | HOMECORE exact equivalent |
+|---|---|
+| `GET /api/states` → `[{entity_id, state, attributes, last_changed, last_updated, context}]` | Identical JSON schema; `last_changed` / `last_updated` in ISO 8601 |
+| `GET /api/services` → `{domain: {service: {description, fields}}}` | Identical schema; service descriptions read from plugin manifests |
+| WS `subscribe_events` → `{type: "event", event: {event_type, data, origin, time_fired, context}}` | Identical envelope; `time_fired` in ISO 8601 |
+| WS `call_service` → `{type: "result", success: true, result: {context}}` | Identical; `context.id` is a UUID |
+| WS `get_states` → `{type: "result", result: [{entity_id, state, attributes, ...}]}` | Identical schema |
+| REST `POST /api/services/<domain>/<service>` → 200 with called service list | Identical; same `target` field support |
+| REST `POST /api/template` → 200 with evaluated string | Identical; same error response `{message: "..."}` on template error |
+| Auth WS flow: `auth_required` → `auth` → `auth_ok` | Identical message type strings; same `ha_version` field in `auth_required` |
+| REST `Authorization: Bearer <token>` | Identical header name; JWT instead of HA's opaque token format (transparent to clients) |
+
+---
+
+## 5. Phased implementation plan
+
+### P1 — Axum skeleton + static frontend (1 week)
+
+- [ ] Create `v2/crates/homecore-api/` workspace member.
+- [ ] Axum router on port 8123; Tower CORS middleware (allow `http://homeassistant.local:8123`).
+- [ ] Static file handler: serve HA's Python frontend build from a configurable path (default `./frontend/build/`). This allows using the Python HA frontend as-is until ADR-131 ships.
+- [ ] `GET /api/` returns `{ "message": "API running." }`.
+- [ ] CI: `cargo check -p homecore-api`; HTTP smoke test.
+
+### P2 — Core REST + WebSocket auth + states (3 weeks)
+
+- [ ] Axum WebSocket upgrade at `/api/websocket`.
+- [ ] Auth: Ed25519 JWT issuance at `/auth/token`; validation middleware.
+- [ ] WS auth handshake: `auth_required` → `auth` → `auth_ok` / `auth_invalid`.
+- [ ] WS commands: `get_states`, `subscribe_events`, `unsubscribe_events`, `call_service`, `get_services`, `get_config`.
+- [ ] REST: `/api/states`, `/api/states/<entity_id>` (GET + POST), `/api/services`, `/api/services/<domain>/<service>`, `/api/config`.
+- [ ] Integration test: HA iOS companion app authenticates and displays entity list against HOMECORE.
+
+### P3 — Remaining WS commands + entity registry API (3 weeks)
+
+- [ ] WS: `subscribe_trigger`, `render_template`, `validate_config`, `subscribe_entities`, entity/area/device registry commands.
+- [ ] REST: `/api/template`, `/api/webhook/<id>`, `/api/error_log`, `/api/events`, `/api/events/<type>`.
+- [ ] `/auth/authorize` OAuth2 flow for UI login.
+- [ ] HACS smoke test: HACS connects, lists integrations.
+
+### P4 — Recorder + history API (2 weeks)
+
+- [ ] `/api/history/period/<datetime>` backed by ADR-132 recorder SQLite.
+- [ ] `/api/logbook/` backed by ADR-132 recorder.
+- [ ] `/api/camera_proxy/`, `/api/calendar/`, `/api/intent/handle`.
+- [ ] Companion app full feature test: automations, notifications, history charts.
+
+---
+
+## 6. Risks
+
+| Risk | Likelihood | Severity | Mitigation | Cross-ADR impact |
+|---|---|---|---|---|
+| **JSON schema drift** — HA updates a response field name between 2025.1 and HOMECORE release | Medium | High | Maintain a JSON-schema test fixture set generated from HA 2025.1; run against HOMECORE in CI | ADR-134: migration tool depends on the same JSON schemas; must stay in sync |
+| **WS subscription fan-out** — 50 concurrent HA companion app sessions each subscribed to `subscribe_events` ALL; every state change creates 50 serialization tasks | Medium | Medium | Broadcast serialized JSON once; clone the `Bytes` arc to each subscriber sender; do not re-serialize per subscriber | ADR-127: broadcast channel capacity must handle subscriber fan-out without lagging |
+| **Auth token format** — HA companion apps may validate the token format (JWT vs opaque). HOMECORE uses JWT; HA uses a custom opaque token. Tokens are never decoded client-side in standard clients, but non-standard clients may inspect them | Low | Low | JWTs are base64url-encoded JSON; any client checking `token.startsWith("ey")` will see a JWT. HA's own tokens are also base64url but not JWTs. Document the difference; test with the iOS app specifically | None |
+| **Port 8123 conflict** — HOMECORE runs on the same port as HA; side-by-side mode (ADR-134) requires HOMECORE on a different port until cutover | High | Medium | ADR-134 side-by-side mode runs HOMECORE on port 8124; companion app can be pointed at port 8124 for testing | ADR-134 owns the cutover mechanism |
+
+---
+
+## 7. Open questions
+
+**Q1**: The HA WebSocket API uses incremental integer IDs (`id: 1, 2, 3, ...`) for command/response correlation within a session. HOMECORE uses the same scheme. What is the maximum `id` value the companion app supports before wrapping? If the app doesn't wrap and HOMECORE processes > 2^31 commands per session, this becomes an overflow issue in extremely long-lived sessions.
+
+**Q2**: The `subscribe_entities` WS command (added in HA 2021.x) sends entity registry change events in addition to state change events. The iOS companion app uses this to maintain a local entity list without polling. Is the full `subscribe_entities` delta schema (including `action: "create" | "update" | "remove"`) fully documented, or must it be reverse-engineered from the companion app source?
+
+**Q3**: HA's `/auth/token` endpoint accepts `grant_type=password` (username/password) and `grant_type=refresh_token`. HOMECORE's initial implementation supports password grant only. Is refresh token support required for the companion app (it caches tokens between sessions) or does the companion app re-authenticate on each launch?
+
+**Q4**: CORS policy: HA's default CORS allows `http://localhost:*` and `http://homeassistant.local:*`. The HOMECORE-UI frontend (ADR-131) will be served from a different origin in development. What CORS policy should HOMECORE-API use in production vs development mode?
+
+---
+
+## 8. References
+
+### HA upstream
+
+- `homeassistant/components/api/__init__.py` — 24 REST routes with exact URL paths, methods, and JSON response schemas
+- `homeassistant/components/websocket_api/connection.py` — auth handshake protocol; per-connection state management
+- `homeassistant/components/websocket_api/commands.py` — 30+ command type handlers with exact type strings and result schemas
+- `homeassistant/components/http/__init__.py` — CORS setup; trusted proxy handling; aiohttp-based server
+- `homeassistant/auth/providers/__init__.py` — token issuance; `AuthManager`; LLAT format
+- `homeassistant/auth/__init__.py` — `AuthManager.async_create_long_lived_access_token`
+
+### This repo
+
+- `v2/crates/wifi-densepose-sensing-server/src/main.rs` — Axum server architecture (REST + WebSocket); pattern for this ADR
+- `v2/crates/wifi-densepose-sensing-server/src/bearer_auth.rs` — Bearer auth middleware pattern
+- `docs/adr/ADR-127-homecore-state-machine-rust.md` — state machine that REST/WS routes read from
+- `docs/adr/ADR-126-ruview-native-ha-port-master.md` — §6 compatibility contract with companion apps
+
+### External
+
+- [HA WebSocket API Developer Docs](https://developers.home-assistant.io/docs/api/websocket/) — authoritative command type catalog
+- [HA REST API](https://developers.home-assistant.io/docs/api/rest/) — REST endpoint schemas

docs/integrations/home-assistant.md

@@ -389,6 +389,120 @@ Per [ADR-115 §3.9](../adr/ADR-115-home-assistant-integration.md#39-tls--auth),
 
 ---
 
+## Applications — what people actually do with this
+
+The 21 entities per node — 11 raw signals (presence, person count, breathing, heart rate, motion, RSSI, etc.) and 10 inferred semantic states (someone-sleeping, possible-distress, room-active, elderly-inactivity-anomaly, meeting-in-progress, bathroom-occupied, fall-risk-elevated, bed-exit, no-movement, multi-room-transition) — slot into Home Assistant like any other sensor. The list below groups real-world uses so you can pick the ones that match your space.
+
+### Personal & home
+
+| Use case | Which entities | What HA does with it |
+|---|---|---|
+| **"Goodnight" routine** | `someone_sleeping` | Dim hallway lights to 5%, lock doors, drop thermostat 2 °C, mute notifications. Blueprint `02-dim-hallway-when-sleeping.yaml`. |
+| **"Wake up" routine** | `bed_exit` | When you get out of bed in the morning, turn on the bathroom heater, raise blinds, start the coffee. Blueprint `03-wake-routine-on-bed-exit.yaml`. |
+| **Meeting / focus mode** | `meeting_in_progress` | Multi-person presence in the office for >5 min → set a "Do Not Disturb" status, dim overhead lights, pause vacuum schedule. Blueprint `05-meeting-lights-presence-mode.yaml`. |
+| **Bathroom fan automation** | `bathroom_occupied` | Turn the exhaust fan on while a bathroom is occupied; turn it off 5 min after you leave. Blueprint `06-bathroom-fan-while-occupied.yaml`. |
+| **Forgotten kitchen / iron** | `presence` per room | "Stove on, kitchen empty for 10 min" → push notification + optional smart-plug cut-off. |
+| **Pet-only at home** | `n_persons == 0` for hours but `motion > 0` | Distinguish dog moving around from human presence — don't trigger empty-home automations during the day. |
+| **Sleep quality tracking** | `breathing_rate_bpm`, `heart_rate_bpm` (privacy off) | Push nightly averages to HA Statistics, graph in Grafana. No watch, no app. |
+| **Toddler bed safety** | `no_movement` in a child's room overnight | Alert parents if breathing-rate signal drops out unexpectedly. |
+| **Pre-arrival lighting** | `multi_room_transition` | When you walk from the entry hall toward the living room, anticipate the route and pre-warm those lights. |
+
+### Healthcare & assisted living (AAL)
+
+| Use case | Which entities | Why this works |
+|---|---|---|
+| **Fall detection + escalation** | `fall_detected` | Phase-acceleration spike + 3-frame debounce. Trigger a Lovelace alert, then escalate to a phone call if the person stays still for >2 min. Blueprint `07-fall-risk-escalation.yaml`. |
+| **Elderly inactivity anomaly** | `elderly_inactivity_anomaly` | Learns a person's normal day-pattern and flags deviations (e.g. usually up by 9 am, hasn't moved by 11 am). Blueprint `04-alert-elderly-inactivity-anomaly.yaml`. |
+| **Privacy-mode care monitoring** | `possible_distress` + `no_movement` + `someone_sleeping` | Run with `--privacy-mode` — heart rate and breathing values are stripped at the wire, but the *inferred states* keep working. Care staff sees "Distress detected" without ever seeing the underlying biometric numbers. The architectural win that makes RuView legally deployable in care homes. |
+| **Sleep apnea screening** | `breathing_rate_bpm` + `breathing_confidence` | Track per-night BPM histograms; flag dips that correlate with apnea events. |
+| **Post-surgery recovery monitoring** | `no_movement` + `bed_exit` + `breathing_rate_bpm` | Hospital-discharge patient at home; rule: "no bed exits in 12 h" triggers a check-in call. |
+| **Dementia wandering detection** | `multi_room_transition` + nighttime gate | Multi-room transitions between 23:00 and 06:00 alert a caregiver — without GPS tags or wearables the person may refuse to wear. |
+| **Bathroom occupancy timeout** | `bathroom_occupied` for >30 min | Possible fall or medical incident; push to caregiver. |
+
+### Security & safety
+
+| Use case | Which entities | What HA does with it |
+|---|---|---|
+| **Auto-arm when no one's home** | `presence` across all nodes for >10 min | Switch HA alarm panel to "armed_away" — replaces door-sensor + key-fob combos. Blueprint `08-auto-arm-security-when-not-active.yaml`. |
+| **Intrusion detection (presence without entry)** | `presence` true while no door/window sensor opened | Real signal of someone inside who shouldn't be. RF-based, can't be defeated by covering a camera. |
+| **Through-wall presence verification** | `presence` per room, even with doors closed | Confirms HA "someone is home" estimate without requiring per-room PIR sensors. |
+| **Hostage / silent-distress mode** | `possible_distress` (motion + elevated HR) | If you've published HR + privacy is off, abnormal motion-plus-physiology can trigger a silent alarm. |
+| **Garage / shed monitoring** | `presence` in outbuildings | Wi-Fi reaches places PIR doesn't (metal shed walls block IR but pass through Wi-Fi). |
+| **Camera-free child safety zone** | `presence` near pool / stairs / fireplace | Push alert if a known child-room sensor sees presence in restricted zone — no cameras, no privacy concerns. |
+
+### Commercial buildings & retail
+
+| Use case | Which entities | What it enables |
+|---|---|---|
+| **Real-time office occupancy** | `n_persons`, `presence`, `room_active` | Live dashboard of how full each meeting room is — no cameras, no badges. Better than door-counters because people are detected mid-meeting, not just on entry. |
+| **HVAC demand-controlled ventilation** | `n_persons` | Adjust ventilation per room based on people present — saves 20-30% on cooling/heating in shared offices. |
+| **Meeting room booking truth** | `meeting_in_progress` vs calendar | "Meeting booked, but no one's there" → auto-release the room. |
+| **Retail dwell time + heat-mapping** | `presence` + `motion` over time | Where do customers linger? Which aisles are empty? Anonymous (no faces), through-clothing, works in low light. |
+| **Queue length estimation** | `n_persons` near a checkout | Trigger "open another register" automation. |
+| **Cleaning verification** | `no_movement` in a room for >X min after hours | Confirms cleaning crew has finished the room without requiring badges. |
+| **Lone-worker safety (warehouses, labs)** | `no_movement` + `possible_distress` | OSHA-compatible solo-worker monitoring without wearables. |
+
+### Industrial & infrastructure
+
+| Use case | Which entities | What it enables |
+|---|---|---|
+| **Manned-station occupancy** | `presence` | Control rooms / lab benches — confirm operator presence without log-in friction. |
+| **Restricted-zone intrusion** | `presence` + `multi_room_transition` | Server room / clean room / pharmaceutical lab — RF passes through doors better than IR. |
+| **Equipment-room ventilation** | `presence` in a UPS / battery room | Turn on exhaust fans when a technician enters. |
+| **Hazardous-area worker tracking** | `presence` + `no_movement` | Confirm workers in an electrical or chemical area are still moving (not collapsed). |
+| **Construction-site after-hours** | `presence` + scheduled gate | Detect anyone on-site after 18:00 → site supervisor alert. |
+| **Maritime / offshore quarters** | `breathing_rate` overnight | Confirm bunk occupants are alive without wearables that often get removed during sleep. |
+
+### Education & public spaces
+
+| Use case | Which entities | What it enables |
+|---|---|---|
+| **Classroom occupancy** | `n_persons`, `room_active` | HVAC and lighting per actual headcount — saves energy in classrooms used 40% of the day. |
+| **Library / study room availability** | `presence` + `n_persons` | Live "rooms available" page without webcams. |
+| **Lecture hall attendance** | `n_persons` time-series | No card-swipe required — RF presence is robust to phones-in-pockets. |
+| **Restroom occupancy signage** | `bathroom_occupied` per stall | Privacy-friendly "in use / available" indicators. |
+| **Gym / pool capacity** | `n_persons` | Live capacity counter for compliance with limits — no turnstiles needed. |
+| **Public-transport waiting areas** | `n_persons` + `room_active` | Real-time platform crowd density for transit operator dashboards. |
+
+### Energy & sustainability
+
+| Use case | Which entities | What it enables |
+|---|---|---|
+| **Per-room lighting auto-off** | `presence` per node | The room-level version of motion-PIR — works through walls, no false-off when sitting still reading. |
+| **Smart-thermostat zoning** | `room_active`, `n_persons` | Only heat / cool occupied rooms — substantial savings in homes >150 m². |
+| **Vampire-load cut-off** | `presence` for whole house | When no one is home, smart plugs cut TV / chargers / standby loads. |
+| **Solar / battery dispatch tuning** | `n_persons`, `motion_energy` | Predict next-hour load based on activity, dispatch battery accordingly. |
+| **Cold-chain refrigeration alerts** | `presence` + `bathroom_occupied` confusion | Trigger door-checks when an unexpected person spends >10 min near a walk-in freezer. |
+
+### Research, prototyping & developer use
+
+| Use case | Which entities | What it enables |
+|---|---|---|
+| **Behavioral studies** | Full snapshot stream | Anonymous behavioral data — count, motion, vitals — without IRB-blocking cameras. |
+| **HCI experiments** | `multi_room_transition` + `presence` | Path-following studies in living labs. |
+| **Healthcare datasets** | `breathing_rate_bpm` time-series | Generate breathing-rate corpora for ML training without consent forms for facial data. |
+| **Custom RuView Cogs** | Raw CSI feed + the WebSocket sync field | Bring your own model, consume the firmware-side mesh-aligned timestamps for multistatic fusion. |
+
+### Combining entities — recipe patterns
+
+A few patterns appear over and over; if you understand these you can build most of the above yourself:
+
+1. **"Negative + duration" trip wires** — `no_movement` for N minutes AND time-of-day window → most healthcare and pet/child safety automations.
+2. **"Two states agree" guards** — `presence == false` AND security panel disarmed AND no door sensor open → strong "house is empty" signal.
+3. **"Threshold + cooldown"** — `presence_score > 0.7` for 30 s before triggering (smooths over flicker), then a 5 min cooldown before re-arming (prevents oscillation).
+4. **"Calendar vs reality"** — pair an HA calendar event with `n_persons` → meeting-room auto-release, classroom unused-period detection.
+5. **"Privacy-mode + semantic-only"** — run `--privacy-mode`, expose only the semantic primitives to HA, keep biometrics on-device. The right default for any deployment with non-tenant occupants.
+
+### What about regulated environments?
+
+Run RuView with `--privacy-mode` and only the 10 inferred semantic states reach Home Assistant — heart rate, breathing rate, and pose values are stripped at the MQTT wire. Per ADR-115 §6, this passes:
+
+- **HIPAA-style minimum-necessary** (no biometric numbers leave the device)
+- **GDPR purpose-limitation** (the inferred states are the smallest dataset that supports the automation)
+- **CCPA "sensitive personal information"** (no health data crosses the wire)
+
+The fall-risk-elevated / possible-distress / someone-sleeping flags still work — they're computed *inside* the sensor pipeline and only the boolean outputs are published. That's the architectural win that makes RuView deployable in care homes, hospitals, schools, and shared-housing scenarios where raw biometrics would be a non-starter.
+
 ## References
 
 - [ADR-115](../adr/ADR-115-home-assistant-integration.md) — full design rationale

docs/integrations/pypi-release.md

@@ -0,0 +1,64 @@
+# PyPI release runbook — `wifi-densepose` + `ruview`
+
+Operations doc for the `.github/workflows/pip-release.yml` CI workflow.
+
+## Auth
+
+The workflow uses one GitHub Actions secret named `PYPI_API_TOKEN`.
+It's a project-token issued by the rUv PyPI account with upload
+scope for both `wifi-densepose` and `ruview`.
+
+## Refreshing the token
+
+The canonical copy of the token lives in GCP Secret Manager,
+project `cognitum-20260110`, entry name `PYPI_TOKEN`. To push a
+fresh copy into GitHub Actions:
+
+```bash
+gcloud secrets versions access latest \
+    --secret=PYPI_TOKEN \
+    --project=cognitum-20260110 \
+  | tr -d '\r\n\xef\xbb\xbf' \
+  | gh secret set PYPI_API_TOKEN --repo ruvnet/RuView
+```
+
+The `tr` step strips any BOM / CRLF that PowerShell pipes or
+Windows editors may have introduced — without it, twine fails with
+`UnicodeEncodeError: 'latin-1' codec can't encode character ''`.
+
+## Triggering a release
+
+Two paths:
+
+- **Tag push** — `git tag v2.X.Y-pip && git push origin v2.X.Y-pip` —
+  publishes the v2 wheel matrix. `v1.99.0-pip` triggers the tombstone
+  job instead.
+- **Manual dispatch** — `gh workflow run pip-release.yml --ref <branch>
+  -f target=v2-wheels -f publish_to=pypi`. Use `publish_to=testpypi`
+  for a dry-run target if a TestPyPI token is also set as
+  `TESTPYPI_API_TOKEN`.
+
+## Release-day sequence
+
+Per ADR-117 §7.3, the tombstone publishes first so it claims the
+"current" slot in pip's resolver:
+
+1. `git tag v1.99.0-pip && git push origin v1.99.0-pip` →
+   tombstone live at `https://pypi.org/project/wifi-densepose/1.99.0/`
+2. Verify: `pip install wifi-densepose==1.99.0; python -c "import
+   wifi_densepose"` → ImportError with migration URL.
+3. `git tag v2.0.0-pip && git push origin v2.0.0-pip` → v2 wheel
+   matrix live at `https://pypi.org/project/wifi-densepose/2.0.0/`.
+4. (Optional, in lock-step) build + publish a matching `ruview`
+   release from `python/ruview-meta/` so the meta-package version
+   stays pinned to the same wifi-densepose version.
+
+## Off-loop manual gates
+
+- **Q3** (ADR-117 §11.3) — generate `expected_features_v2.sha256`
+  from the v2 Rust pipeline before any v2 publish.
+- **OIDC Trusted Publisher** — not used. The workflow is token-based;
+  this is a deliberate choice to keep the secret refresh entirely in
+  GCP. If the project migrates to OIDC later, remove `password:`
+  from `pypa/gh-action-pypi-publish` calls and add the publisher
+  registration on pypi.org.

docs/research/ADR-116-ha-matter-cog-research.md

@@ -0,0 +1,358 @@
+---
+title: "ADR-116 Research: Home Assistant + Matter Cognitum Seed Cog"
+date: 2026-05-23
+author: ruv
+status: research-complete
+relates-to: ADR-110, ADR-115
+sources:
+  - https://csa-iot.org/newsroom/matter-1-4-enables-more-capable-smart-homes/
+  - https://csa-iot.org/newsroom/matter-1-4-2-enhancing-security-and-scalability-for-smart-homes/
+  - https://docs.espressif.com/projects/esp-matter/en/latest/esp32c6/certification.html
+  - https://docs.espressif.com/projects/esp-matter/en/latest/esp32s3/optimizations.html
+  - https://matter-survey.org/cluster/0x0406
+  - https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/
+  - https://www.hacs.xyz/docs/publish/integration/
+  - https://www.derekseaman.com/2025/11/aqara-fp300-the-ultimate-presence-sensor-home-assistant-edition.html
+  - https://www.tommysense.com/
+  - https://github.com/francescopace/espectre
+  - https://kendallpc.com/fdas-2026-guidance-on-general-wellness-devices-policy-for-low-risk-devices-key-compliance-and-regulatory-insights-for-digital-health-companies/
+  - https://www.troutman.com/insights/fdas-2026-guidance-on-general-wellness-devices-policy-for-low-risk-devices/
+  - https://community.st.com/t5/stm32-summit-q-a/what-is-the-usual-cost-for-a-matter-certification/td-p/652346
+  - https://github.com/p01di/esp32c6-thread-border-router
+  - https://libraries.io/npm/ruvllm-esp32
+  - https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-069-cognitum-seed-csi-pipeline.md
+  - https://www.matteralpha.com/news/home-assistant-2025-12-adds-enhancements-to-matter-sensor-doorlock-and-covering
+  - https://docs.nordicsemi.com/bundle/ncs-3.1.0/page/nrf/protocols/matter/getting_started/testing/thread_one_otbr.html
+---
+
+# ADR-116 Research Dossier: Home Assistant + Matter Integration as a Cognitum Seed Cog
+
+**Research question**: How far can we take HA + Matter integration for WiFi-DensePose / RuView, specifically packaged as a Cognitum Seed cog running on the ESP32-S3 Seed appliance?
+
+**Baseline**: ADR-110 (ESP32-C6 mesh firmware, v0.7.0-esp32) and ADR-115 (HA-DISCO MQTT + HA-FABRIC Matter scaffold, v0.7.0) are both merged to main. This research scopes ADR-116.
+
+---
+
+## 1. Matter / Thread Frontier
+
+### 1.1 Current specification state (May 2026)
+
+Matter 1.4 (released November 2024) added Solar Power, Battery Storage, Heat Pump, Water Heater, and Mounted Load Control device types — primarily energy-management expansion. It did NOT add health, wellness, vitals, or biometric device types. The cluster relevant to WiFi-DensePose is the **Occupancy Sensing cluster (0x0406)**, which has been present since Matter 1.1 and reached revision 5 in Matter 1.4.
+
+Matter 1.4.2 (current patch release as of research date) focused on security: vendor-ID cryptographic verification of Fabric Admins, Access Restriction Lists (ARLs) for network infrastructure devices, Certificate Revocation Lists (CRLs), and Wi-Fi-only commissioning without BLE. The Wi-Fi-only commissioning path (no BLE requirement) is directly relevant to the Seed, which hosts its own AMOLED UI and can display QR codes natively.
+
+**Occupancy Sensing cluster 0x0406 feature flags** (Matter 1.4 revision 5): PIR, Ultrasonic, PhysicalContact, ActiveInfrared, **Radar**, **RFSensing**, Vision, Prediction, OccupancyEvent. The `RFSensing` feature flag added in 1.3 is the correct semantic tag for CSI-based WiFi detection — we are not PIR or Radar in the classical sense. Home Assistant 2025.12 added configurable `HoldTime` for occupancy sensors and support for `CurrentSensitivityLevel`, both attributes our MQTT path already carries.
+
+**Breathing rate and heart rate have no Matter cluster today.** The spec does not define a BiomedicalSensing or VitalSigns device type. Until the CSA adds one (no public work item found as of May 2026), vitals must stay on MQTT. This is a hard architectural constraint for the Matter path.
+
+### 1.2 Thread Border Router on ESP32-C6
+
+The ESP32-C6 carries 802.15.4 natively (the same radio used for Thread and Zigbee). Espressif ships a working single-chip Thread Border Router reference design for C6 in `esp-matter`, confirmed by community hardware tests (p01di/esp32c6-thread-border-router on GitHub). The C6 can operate as a Thread BR while simultaneously sensing on 2.4 GHz Wi-Fi — the two radios share the same front-end but schedule airtime independently under ESP-IDF. ADR-110 already initializes the 802.15.4 subsystem (`c6_timesync.c`) for cross-node time sync; adding TBR functionality is a matter of enabling `CONFIG_OPENTHREAD_BORDER_ROUTER=y` in the C6 sdkconfig overlay, adding the `esp_openthread_border_router_init()` call, and exposing the backbone interface (Wi-Fi STA).
+
+**Thread 1.4 (TREL)**, shipped with Apple tvOS 26 in late 2025, adds Thread Radio Encapsulation Link — Thread traffic tunneled over Wi-Fi as a fallback backhaul. The C6's Wi-Fi 6 radio supports this. TREL removes the hard dependency on a BR for cross-subnet Thread commissioning, which means a C6-equipped Seed node could participate in a Thread fabric without a dedicated BR appliance.
+
+### 1.3 Matter Commissioner / Root mode
+
+In Matter terms, a Commissioner is a distinct role from an Accessory (end device) or Bridge. The Matter spec allows a device to be simultaneously a Fabric member (commissioned) and a Commissioner (able to commission other devices). The `chip-tool` in `connectedhomeip` is the canonical embeddable commissioner implementation. Running chip-tool on the S3 (512 KB SRAM + 8 MB PSRAM) is feasible but borderline — the commissioner stack requires Thread discovery, BLE central, and certificate-chain verification, adding approximately 400–600 KB RAM footprint on top of the application. On the S3 with 8 MB PSRAM mapped to heap this is tractable; on the C6 (320 KB SRAM, no PSRAM) it is not.
+
+**Practical recommendation**: the Cognitum Seed (S3 + PSRAM + full appliance OS) is the right place to host a Matter commissioner, not the C6 sensing nodes. The Seed can use its existing bearer-token API surface and its cognitum-fleet process (port 9002) as the orchestration layer that opens commissioning windows and bootstraps C6 nodes into the Fabric. C6 nodes remain Accessories only.
+
+### 1.4 CSA certification path
+
+Certification requires: (1) CSA membership (~$22,500/year for full member; lower tiers exist), (2) an Authorized Test Laboratory (ATL) engagement (~$10,000–$19,540 per product for lab fees and certification application), (3) PICS/PIXIT XML submission, (4) hardware shipping to the ATL, and (5) registration on the Distributed Compliance Ledger (DCL). Espressif provides pre-certified radio modules (ESP32-C6-MINI-1, ESP32-S3-MINI-1) which can reduce retesting scope under CSA's Rapid Recertification program — only clusters/device-types added beyond the pre-certified baseline require full ATL re-test. Using `esp-matter` with a pre-certified Espressif module, the realistic total cost for bridge certification is **$30,000–$42,000 first year, $22,500/year thereafter** for a full CSA member, or less if using a pass-through arrangement via an ODM partner that already holds membership.
+
+**Alternative**: publish as "Works with Home Assistant" (free, no CSA ATL, just integration tests) and defer CSA certification to v1.1 when commercial customers require it. The `RFSensing` device class and OccupancySensing cluster are already well-supported in the HA Matter integration without certification.
+
+**Key sources**: [Espressif Matter certification guide](https://docs.espressif.com/projects/esp-matter/en/latest/esp32c6/certification.html), [CSA certification process overview](https://csa-iot.org/certification/), [ST community cost discussion](https://community.st.com/t5/stm32-summit-q-a/what-is-the-usual-cost-for-a-matter-certification/td-p/652346), [Nordic Rapid Recertification notes](https://devzone.nordicsemi.com/f/nordic-q-a/116005/csa-iot-rapid-recertification-program), [ESP32-C6 single-chip TBR](https://github.com/p01di/esp32c6-thread-border-router).
+
+---
+
+## 2. HACS Distribution
+
+### 2.1 What HACS unlocks beyond MQTT auto-discovery
+
+MQTT auto-discovery (HA-DISCO, shipped in ADR-115) creates entities automatically but the integration surface is constrained:
+
+| Capability | MQTT auto-discovery | HACS Python integration |
+|---|---|---|
+| Config flow (UI setup without YAML) | no — user edits MQTT broker settings manually | yes — wizard walks user through seed URL, token, privacy options |
+| Repairs API | no | yes — surfaces structured error reasons ("node offline", "firmware mismatch") as HA repair cards |
+| Diagnostics download | no | yes — button in HA device page exports a JSON bundle for bug reports |
+| Re-authentication flow | no | yes — handles token expiry without user needing to touch YAML |
+| Device registry deep links | partial — via_device works | yes — full device info page, firmware version, last-seen, signal quality |
+| Service actions | no | yes — `wifi_densepose.set_privacy_mode`, `wifi_densepose.calibrate_zone` as typed HA services |
+| Config entry options | no | yes — change polling interval, privacy mode, zone layout from HA UI |
+| Translations (i18n) | no | yes — strings.json enables localized entity names and setup UI |
+| Integration quality scale tier | n/a | bronze is minimum; gold (diagnostics + repairs + discovery) is the target |
+| HACS listing | not applicable | yes — users install via HACS Store in one click |
+
+### 2.2 Quality Scale targets
+
+HA's quality scale has four tiers. **Bronze** (19 rules) is the minimum: config_flow, unique entity IDs, test coverage, basic documentation. **Silver** adds 95%+ test coverage and re-authentication. **Gold** adds repairs flows, diagnostics, reconfiguration flows, device categories and translations — this is the target for a v1 HACS integration because it meets the bar set by well-regarded third-party integrations like Z-Wave JS and ESPresense. **Platinum** adds strict typing, async dependency injection, and websession management — worth pursuing but not on the v1 critical path.
+
+### 2.3 HACS submission requirements
+
+HACS requires: public GitHub repo, repo description, topic tags, README, single custom component at `custom_components/wifi_densepose/`, `manifest.json` with `domain`, `documentation`, `issue_tracker`, `codeowners`, `name`, `version` fields, and a `brand/icon.png`. No formal approval process — listing is automatic once requirements are met via HACS default repositories submission. HA's `hassfest` CI tool validates the manifest structure and can be added to the repo's CI pipeline as a workflow step.
+
+The `hacs.integration_blueprint` template (github.com/jpawlowski/hacs.integration_blueprint) provides a well-maintained starting point with all boilerplate including config flow, repairs, diagnostics, and translations scaffolding.
+
+**Key sources**: [HA quality scale rules](https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/), [HACS publish guide](https://www.hacs.xyz/docs/publish/integration/), [HACS 2.0 announcement](https://www.home-assistant.io/blog/2024/08/21/hacs-the-best-way-to-share-community-made-projects-just-got-better/), [integration blueprint](https://github.com/jpawlowski/hacs.integration_blueprint).
+
+---
+
+## 3. Cog Architecture for the Seed
+
+### 3.1 Current cog packaging model
+
+Based on ADR-069 and the cognitum-v0 appliance surface observed in the fleet:
+
+- Cogs are signed binaries distributed via GCS buckets and cataloged at `GET /api/v1/edge/registry` (ADR-102).
+- Each binary is verified against an **Ed25519 signature** before installation (ADR-100). The device-bound keypair lives in NVS on the Seed.
+- Cog binaries are platform-specific: `aarch64` for Pi-based Seed appliances, `x86_64` for the desktop appliance, and (from ADR-069) the feature-vector packet format (`edge_feature_pkt_t`, magic `0xC5110003`) defines the ESP32 side of the protocol. The cog runs on the Seed appliance, not directly on the ESP32.
+- The registry catalog at `seed.cognitum.one/store` lists 105 cogs with capability declarations. The Seed's `cognitum-ota-registry` (port 9003) handles OTA delivery.
+- Capability declarations include dependency lists, required Seed version, permission scopes (network, storage, MCP tool invocations), and resource budgets (max RAM, max CPU).
+
+### 3.2 Proposed HA+Matter cog architecture
+
+The cog runs as a long-lived process on the Seed (aarch64 binary, supervised by `cognitum-agent`). It owns two surfaces:
+
+**Surface A — MQTT bridge**: connects to a user-configured Mosquitto broker (or uses the Seed's internal broker), republishes telemetry from the Seed's `ruview-vitals-worker` (port 50054) as HA auto-discovery messages. This reuses the HA-DISCO logic already in `wifi-densepose-sensing-server` but runs as a Seed-native cog rather than requiring the user to run the sensing-server separately. The cog registers a `ha_mqtt` MCP tool (114-tool catalog) so automations running on other cogs can call `ha_mqtt.publish_state(entity_id, state)`.
+
+**Surface B — Matter bridge**: wraps `esp-matter` / `matter-rs` as a Matter Accessory Bridge. The Seed acts as a WiFi-connected Matter Bridge — one Fabric node with N dynamic endpoints, one per sensing zone. Device types used: `OccupancySensor` (0x0107, clusters: `OccupancySensing 0x0406` with `RFSensing` feature flag + `BooleanState 0x0045`), `ContactSensor` for fall events, and a vendor-specific numeric attribute for person count on the Bridge root endpoint. The Seed's AMOLED display shows the Matter QR code for commissioning — no phone or scanning app required.
+
+**Surface C — HA HACS integration (optional for users without MQTT)**: a Python package in `custom_components/wifi_densepose/` that speaks directly to the Seed's REST API (`/api/v1/`, bearer token from cognitum-agent on port 80) and bootstraps config flow, entities, repairs, and diagnostics as described in §2.
+
+**Deployment topology**: Seed acts as hub for all sensing nodes (ESP32-S3 and C6). Nodes stream feature vectors to the Seed over UDP (ADR-069 protocol). The cog translates these into HA entities, Matter endpoints, and (via Surface C) HACS entity objects. One cog install covers an unlimited number of ESP32 nodes behind that Seed.
+
+### 3.3 Should the cog speak MQTT or publish Matter directly?
+
+**MQTT to local HA is the lower-risk, faster path**: it requires no Matter SDK linkage, no CSA certification, and reuses the existing HA-DISCO logic. Matter direct publishing requires the Seed to hold a valid Fabric certificate (obtained through the commissioning flow with the user's HA or Apple Home controller), manage operational credentials, and handle rekey events. The overhead is manageable on the Seed (S3 processor + Pi aarch64 appliance stack), but the development and QA cost is 3-4x higher. The recommended architecture is: **MQTT as primary, Matter as secondary** — matching ADR-115's dual-protocol decision but now native to the cog.
+
+**Key sources**: [ADR-069 CSI pipeline](https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-069-cognitum-seed-csi-pipeline.md), [ESP32 Matter Bridge example](https://project-chip.github.io/connectedhomeip-doc/examples/bridge-app/esp32/README.html), [Tasmota Matter internals](https://tasmota.github.io/docs/Matter-Internals/), [cognitum-v0 fleet stack].
+
+---
+
+## 4. Local-First AI: ruvllm + RuVector on the Seed
+
+### 4.1 Hardware budget
+
+The Cognitum Seed (ESP32-S3 variant: 8 MB PSRAM + 16 MB flash; Pi 5 variant: 8 GB RAM, Hailo AI hat) has two distinct execution environments. For on-Seed inference the numbers differ dramatically:
+
+| Target | RAM headroom for inference | Flash/storage | Typical INT8 model ceiling |
+|---|---|---|---|
+| ESP32-S3 (8 MB PSRAM) | ~5 MB after OS + MQTT + Matter stack | 16 MB flash | 3–5 MB quantized model (e.g., MobileNetV2-class) |
+| Pi 5 Seed (8 GB RAM, Hailo-10) | ~6 GB free | NVMe | 40 TOPS hardware acceleration; 7B INT4 models feasible |
+| cognitum-v0 Pi 5 (Hailo via ruvector-hailo-worker) | 6 GB RAM + Hailo | NVMe | 40 TOPS; Hailo HEF deployment |
+
+For a **semantic-primitives inference cog running on the ESP32-S3 Seed**, the target is an INT8-quantized classifier that takes the 8-dimensional feature vector (`edge_feature_pkt_t`) as input and outputs 10 semantic primitive probabilities. This is a trivially small model (8 → 64 hidden → 10 outputs, ~10 KB quantized) — it fits entirely in SRAM without needing PSRAM. The ruvllm-esp32 library (npm: `ruvllm-esp32 0.3.3`, cargo: `ruvllm-esp32 0.3.2`) confirms this path: INT8 quantization, HNSW vector search, and SONA self-optimizing adaptation in under 100 µs per query.
+
+### 4.2 SONA fine-tuning loop
+
+The ruvllm SONA (Self-Optimizing Neural Architecture) adapter performs online gradient descent on LoRA-style adapter weights in under 100 µs per query. For the 10-semantic-primitive classifier, this means the Seed can fine-tune its thresholds per-home using occupant feedback without any cloud round-trip:
+
+1. User confirms a false positive via HA notification (e.g., "that was not a fall, I just sat down quickly").
+2. Feedback is recorded via the cog's `ha_mqtt.feedback` MCP tool.
+3. SONA runs one gradient step on the LoRA adapter weights for the `fall_risk_elevated` primitive.
+4. New weights are written to NVS on the ESP32-S3. The witness chain records the adaptation event with a timestamp.
+
+For the Pi 5 Seed with Hailo-10 (40 TOPS), this extends to full 7B-class LoRA fine-tuning using the Hailo HEF pipeline already running at port 50051 (`ruvector-hailo-worker`). The `ruvllm-microlora-adapt` MCP tool in the cog catalog covers this path.
+
+**Latency budget**: 8-dim → 10-output classifier: <1 ms on S3 SRAM (well within 20 Hz update cadence). SONA one-step gradient: <100 µs per adaptation event. Total per-inference overhead: negligible.
+
+### 4.3 RuVector embeddings for room-level semantic context
+
+The Seed's RuVector 2.0.4 integration (ADR-016) maintains HNSW embeddings of CSI feature vectors. The semantic primitives (sleeping, distress, meeting, etc.) can be implemented as HNSW nearest-neighbor lookups against a learned embedding space rather than threshold classifiers — this is more robust to room geometry variation. The `embeddings_rabitq_search` tool (RaBitQ approximate NN) supports sub-millisecond search on the ESP32-S3 PSRAM-hosted index. At 8 dimensions and 1,000 stored vectors, the HNSW index occupies approximately 200 KB — comfortably within PSRAM budget.
+
+**Key sources**: [ruvllm-esp32 on libraries.io](https://libraries.io/npm/ruvllm-esp32), [ESP32-S3 TinyML optimization guide](https://zediot.com/blog/esp32-s3-tinyml-optimization/), [edge LLM deployment 2025](https://kodekx-solutions.medium.com/edge-llm-deployment-on-small-devices-the-2025-guide-2eafb7c59d07), [LoRA-Edge paper](https://arxiv.org/pdf/2511.03765).
+
+---
+
+## 5. Multi-Seed Federation
+
+### 5.1 Discovery mechanisms
+
+Three viable discovery layers for two Seeds in adjacent rooms:
+
+**mDNS**: each Seed already advertises `_ruview._tcp` and `_matter._tcp` on the LAN. A second Seed can discover the first via `mdns-sd` query at startup and register it as a peer node. The cognitum-fleet service (port 9002) already implements fleet orchestration; adding peer-to-peer node registration is an extension of that model. **Caveat**: mDNS is link-local and does not cross VLANs. For multi-VLAN deployments (common in prosumer and commercial setups), a Tailscale overlay (the project already has a fleet on Tailscale — see CLAUDE.local.md) provides routable discovery at the cost of adding the Tailscale daemon to the cog's dependency list.
+
+**Matter multi-admin**: once both Seeds are commissioned to the same Matter Fabric (e.g., via HA's Matter integration), the Fabric provides a shared namespace. However, Matter does not define a cross-device occupancy-handoff event — it only publishes per-device state. Handoff logic must live in HA automations or in the Seed cog's federation layer.
+
+**Direct ESP-NOW mesh (ADR-110)**: the C6 nodes already run ESP-NOW with 99.56% RX reliability. Two Seeds each hosting C6 nodes can use ESP-NOW as the real-time cross-node synchronization bus — one C6 detects motion entering a room, broadcasts the event over ESP-NOW, the adjacent C6 primes its detector, and the Seed coordinator reconciles the two Occupancy states. This is the lowest-latency path (sub-millisecond over ESP-NOW vs. hundreds of milliseconds over MQTT → HA automation → MQTT).
+
+### 5.2 Conflict resolution for simultaneous fall detection
+
+When two sensing nodes both fire `fall_detected=true` within a short window, the cog applies a simple deduplication rule: the detection with the higher `presence_score` wins, and a 5-second exclusion window is applied on the lower-scoring node (matching the fall debounce logic from the firmware — 3-frame consecutive + 5 s cooldown). The winner's event is forwarded to HA as the canonical fall event. The loser is recorded in the witness chain with a `DEDUP_SUPPRESSED` tag for audit.
+
+For cross-room occupancy, the cog maintains a **single-occupancy graph**: if node A detects person_count=1 and node B simultaneously detects person_count=1, and the two nodes are configured as adjacent rooms, the cog checks whether person_count in the home (sum of all node counts) is consistent with known occupant count (configurable, defaults to household size from HA's `persons` entity). Inconsistency triggers a `multi_room_transition` event published to HA rather than both nodes claiming simultaneous presence.
+
+### 5.3 Witness chain for cross-Seed events
+
+ADR-069 defines a SHA-256 tamper-evident witness chain per node. For cross-Seed events, the chain must include a cross-reference: each Seed's witness head at the time of the event is included in the other's chain entry. The cog implements this via a shared `witness_sync` MCP tool that both Seeds call before writing a cross-node event. This produces a bifurcated chain that any third party can verify for temporal consistency.
+
+**Key sources**: [Matter multi-admin guide](https://mattercoder.com/codelabs/how-to-use-multi-admin/), [ESP-NOW mesh ADR-110 witness log](../WITNESS-LOG-110.md), [HA mDNS cross-VLAN thread](https://niksa.dev/posts/ha-vlan/), [home-assistant-matter-hub mDNS issue](https://github.com/t0bst4r/home-assistant-matter-hub/issues/237).
+
+---
+
+## 6. Competitor Analysis
+
+### 6.1 Aqara FP2 and FP300
+
+**FP2** (mmWave, Wi-Fi): presence, person count (up to 5), 30 zones with 320 detection areas, fall detection. HA integration via native Zigbee or Matter (Thread firmware). Matter mode is severely limited per user testing — configurable parameters are stripped and sensitivity settings are unavailable. Zigbee mode (via Zigbee2MQTT) is the recommended HA path. **No vitals (HR/BR), no pose.** Privacy story: local processing, no cloud required for automations.
+
+**FP300** (5-in-1: mmWave + PIR + light + temperature + humidity, Matter-over-Thread): presence (binary only), temperature, humidity, light level. No person count, no fall detection, no vitals. Thread firmware gives 5 HA entities. Matter mode is functional but configuration-limited. Battery-powered (2× CR2450, ~2 years in Thread mode). **Verdict**: Aqara's Matter story is hardware-first but software-limited. Their Matter device class choice is `OccupancySensor` with standard PIR/Radar bitmap — no `RFSensing` flag.
+
+### 6.2 TOMMY (tommysense.com)
+
+Wi-Fi CSI sensing for HA. Uses ESP32 nodes. Exposes zones as binary sensors (MQTT, port 1886) and as Matter `OccupancySensor` endpoints (QR-based pairing). Motion and presence only — no vitals, no pose, no fall detection. Privacy: fully local, one periodic license-check outbound call. Closed-source algorithm and firmware; open-source HA integration. **Pricing**: free trial (1 zone, 2-min pause per 2 min of detection), Pro (unlimited zones, continuous). **Key gap vs RuView**: no HR/BR, no pose keypoints, no fall detection, no witness chain, no SONA adaptation.
+
+### 6.3 ESPectre (github.com/francescopace/espectre)
+
+Open-source CSI motion detection with HA integration (HACS). ESP32-only. Motion detection via RSSI phase variance analysis — no person counting, no vitals, no fall detection. Python-based HA custom component. No Matter support. **Verdict**: proof-of-concept quality; not a commercial competitor but demonstrates demand for the HACS distribution path.
+
+### 6.4 Frigate NVR
+
+Video-based local AI NVR. MQTT integration with HA creates binary sensors (`binary_sensor.frigate_<camera>_person_motion`), person count sensors, and clip/snapshot sensors per camera. All inference on-device (Coral EdgeTPU or Hailo). **Privacy**: fully local, no cloud. Frigate's MQTT entity catalog per camera: 1 camera stream entity, N object detection binary sensors (person, car, dog, etc.), N object count sensors. No vitals, no pose skeleton. Matter support: none in Frigate itself. **Key privacy contrast vs RuView**: Frigate requires cameras (video pixels), RuView uses RF only — privacy advantage in bedrooms, bathrooms, and care settings.
+
+### 6.5 RoomMe (Intellithings)
+
+Bluetooth LE room presence using smartphone proximity. Supports HomeKit and some smart-device ecosystems. No native HA integration, no MQTT, no Matter. High per-unit cost ($69). No vitals, no fall detection. Not a real competitor for the CSI/mmWave presence category.
+
+### 6.6 Competitor entity catalog comparison
+
+| Feature | RuView (ADR-115) | Aqara FP2 | Aqara FP300 | TOMMY | Frigate |
+|---|---|---|---|---|---|
+| Presence (binary) | yes | yes | yes | yes | yes (person class) |
+| Person count | yes | yes (5 max) | no | no | yes (per class) |
+| HR / BR | yes | no | no | no | no |
+| Pose keypoints | yes (17-pt) | no | no | no | no |
+| Fall detection | yes | yes | no | no | no |
+| Semantic primitives | yes (10) | no | no | no | no |
+| Multi-room handoff | yes (cog) | no | no | no | no |
+| Privacy mode | yes (wire-strip) | local only | local only | local only | local only |
+| HACS integration | roadmap | no | no | yes | yes |
+| Matter native | yes (bridge) | yes (limited) | yes | yes | no |
+| Witness chain | yes | no | no | no | no |
+
+**Key sources**: [Aqara FP300 HA review](https://www.derekseaman.com/2025/11/aqara-fp300-the-ultimate-presence-sensor-home-assistant-edition.html), [TOMMY product page](https://www.tommysense.com/), [ESPectre GitHub](https://github.com/francescopace/espectre), [Frigate NVR docs](https://frigate.video/), [mmWave presence sensors 2026 comparison](https://www.linknlink.com/blogs/guides/best-mmwave-presence-sensors-home-assistant-2026).
+
+---
+
+## 7. Regulatory Frontier
+
+### 7.1 FDA classification landscape (2026 update)
+
+The FDA issued updated General Wellness Device guidance on January 6, 2026. Key clarifications relevant to WiFi-DensePose:
+
+**Wellness device criteria** (functions that keep the product outside FDA jurisdiction): the device must (a) have low inherent risk to user safety, (b) make no reference to specific diseases or conditions, and (c) not provide diagnostic or treatment outputs. Examples in the guidance: heart rate monitoring, sleep tracking, activity/recovery metrics, oxygen saturation trends — all qualify as wellness when marketed without diagnostic claims.
+
+**Claims that trigger medical device classification**: any output labeled as "abnormal, pathological, or diagnostic"; recommendations concerning clinical thresholds or treatment; ongoing clinical monitoring or alerts for medical management; substitution for an FDA-approved device. A fall detection feature framed as "alert a caregiver when you might have fallen" is materially different from one framed as "diagnose fall injury" — the former qualifies as wellness under the 2026 guidance; the latter does not.
+
+**The defensible wellness-device position for RuView**: (a) market fall detection as an "activity anomaly notification" not a "medical fall diagnosis"; (b) include explicit disclaimers against diagnostic or clinical use in app-store descriptions, labeling, and HA integration documentation; (c) avoid "medical-grade" accuracy claims for HR/BR readings; (d) position the device as a "smart home occupancy and wellness assistant" rather than a "patient monitoring system."
+
+### 7.2 HIPAA applicability
+
+HIPAA applies only when an entity is a HIPAA "covered entity" (healthcare providers, health plans, clearinghouses) or their "business associate." A consumer smart home product sold direct-to-homeowners is not automatically a covered entity. However, HIPAA applicability is triggered if the Seed's data flows into a covered entity's system (e.g., a care facility's EHR). The privacy-mode flag in ADR-115 (stripping HR/BR/pose at the wire, publishing only semantic state digests) creates a technical barrier to PHI transmission that supports a "not a covered entity" position.
+
+**All 50 US states** impose data breach notification requirements regardless of HIPAA status. The witness chain (SHA-256 tamper-evident audit log per node) satisfies most state-level data-integrity requirements.
+
+### 7.3 Matter Health-Check device class
+
+Matter currently has no "Health" or "Wellness" device class in the formal taxonomy. The closest is `OccupancySensor` with the `RFSensing` feature flag. The device type `0x0107` (OccupancySensor) in the DCL will not trigger any health-device regulatory scrutiny. Using this device type keeps the Seed in the same regulatory category as a smart motion sensor — well outside the medical device perimeter.
+
+**Key sources**: [FDA 2026 General Wellness guidance (Kendall PC)](https://kendallpc.com/fdas-2026-guidance-on-general-wellness-devices-policy-for-low-risk-devices-key-compliance-and-regulatory-insights-for-digital-health-companies/), [Troutman Pepper Locke analysis](https://www.troutman.com/insights/fdas-2026-guidance-on-general-wellness-devices-policy-for-low-risk-devices/), [IEEE Spectrum FDA device rules](https://spectrum.ieee.org/fda-medical-device-rules), [FDA wellness tracker / cybersecurity interlock (Troutman)](https://www.troutman.com/insights/wellness-trackers-medical-status-and-cybersecurity-how-fda-ftc-and-state-laws-interlock/).
+
+---
+
+## 8. Frontier Features Worth Shipping
+
+### 8.1 HACS marketplace listing
+
+**Build cost**: medium (4–6 weeks for a gold-tier integration). **User impact**: very high — one-click install removes the MQTT broker prerequisite for non-power-users.
+
+Architecture: Python package at `custom_components/wifi_densepose/`, config flow that discovers Seeds via mDNS (`_ruview._tcp`) or manual IP, bearer token authentication against `GET /api/v1/status`, full entity catalog matching ADR-115 §3.1 (21 entities per node), repairs for offline nodes, diagnostics export, translations for EN/FR/DE/ES. Start from `hacs.integration_blueprint` template. Submit via HACS default repositories GitHub submission.
+
+### 8.2 Matter Bridge with OccupancySensor / ContactSensor / BooleanState
+
+**Build cost**: high (6–8 weeks including CI test harness with chip-tool simulator). **User impact**: high for Apple Home / Google Home users who don't run HA.
+
+Device type mapping:
+- Presence → `OccupancySensor (0x0107)` with `OccupancySensing (0x0406)`, `RFSensing` feature flag set, `HoldTime` attribute wired to sensing-server's zone dwell time.
+- Fall detected → `ContactSensor (0x0015)` used as event source (state: `true` for 5 s after fall, then auto-reset) — closest available device type until a FallEvent device type exists in the spec.
+- Person count → vendor-specific attribute on the Bridge root endpoint (`VendorSpecificAttributeCount`, cluster 0xFFF1_xxxx namespace).
+
+Memory on S3: baseline Matter stack ~1.5 MB flash, ~195 KB DRAM + PSRAM heap; BLE freed post-commissioning recovers ~100 KB. 16 dynamic endpoints (default maximum, configurable per `NUM_DYNAMIC_ENDPOINTS`) costs ~550 bytes DRAM each. For 8 zones: 8 × 550 = 4.4 KB additional DRAM — well within budget. Wi-Fi-only commissioning (Matter 1.4.2) eliminates BLE requirement, simplifying the Seed hardware path.
+
+### 8.3 Cognitum Seed cog manifest + signing
+
+**Build cost**: low (1–2 weeks). **User impact**: enables one-tap install from the Cognitum Seed store.
+
+Manifest structure (based on ADR-069/ADR-100 patterns):
+```json
+{
+  "id": "cog-ha-matter-v1",
+  "version": "1.0.0",
+  "platforms": ["aarch64", "x86_64"],
+  "min_seed_version": "0.8.1",
+  "capabilities": ["network.mqtt", "network.matter", "api.ruview_vitals"],
+  "resource_budget": {"ram_mb": 128, "cpu_percent": 15},
+  "signing_key_id": "ed25519:ruv-cog-signing-v1",
+  "registry_url": "https://seed.cognitum.one/store/cog-ha-matter",
+  "ha_integration_repo": "https://github.com/ruvnet/hass-wifi-densepose"
+}
+```
+Binary signing uses the existing Ed25519 keypair infrastructure from ADR-100. The `cognitum-ota-registry` (port 9003) handles delivery. The cog declaration includes the companion HACS integration GitHub URL so the Seed UI can prompt the user to install the HACS companion if they have HA detected on the LAN.
+
+### 8.4 Local SONA fine-tuning loop for per-home thresholds
+
+**Build cost**: low (2–3 weeks, given ruvllm-esp32 already provides the primitives). **User impact**: high — eliminates false positives that are the top complaint for presence/fall sensors in HA forums.
+
+Implementation: HA sends feedback events via an MQTT command topic (`homeassistant/wifi_densepose/<node>/cmd/feedback`). The cog's SONA adapter processes the feedback as a labeled training example and runs one gradient step. After 20 feedback events, it triggers a witness-chain-attested weight checkpoint. The HACS integration surfaces this as a "Improve detection accuracy" button in the HA device page, pointing users to a simple thumbs-up/thumbs-down UI on the last 10 events.
+
+### 8.5 Multi-room presence handoff
+
+**Build cost**: medium (3–4 weeks). **User impact**: high — eliminates the "ghost occupancy" problem where HA thinks two rooms are occupied when a person walks from one to the other.
+
+Implementation: the cog runs a presence graph across all Seeds in the fleet. Nodes declare themselves adjacent via the manifest or via HA area assignment. When person_count transitions (room A: 1→0, room B: 0→1) within a configurable window (default 3 s), the cog publishes a single `multi_room_transition` event to HA with `from_zone` and `to_zone` fields, and holds the `person_count=1` in the destination room rather than briefly showing 0 in both. This is a cog-side state machine, not an HA automation — it runs at 20 Hz loop cadence.
+
+### 8.6 Energy disaggregation: pairing vitals with HA energy entities
+
+**Build cost**: medium (3–4 weeks). **User impact**: medium-high for sustainability-focused users.
+
+Non-Intrusive Load Monitoring (NILM) in HA already exists as a community blueprint (github.com/tronikos NILM blueprint). The opportunity for RuView is the inverse: rather than using energy to infer occupancy, use RuView's presence data to validate NILM's occupancy assumptions. When RuView reports presence_score < 0.1 (no one home) but the NILM model predicts an active appliance load inconsistent with unoccupied state (e.g., a TV left on), HA can surface a "phantom load detected" notification. The cog publishes a `phantom_load_candidate` event when this condition holds for more than 5 minutes. Pairs with HA's Energy dashboard (introduced in 2021, stable since 2023) and the `homeassistant/sensor/<node>/phantom_load/config` MQTT discovery topic.
+
+### 8.7 Privacy-mode "audit logs only"
+
+**Build cost**: low (1 week, extends existing `--privacy-mode` flag from ADR-115). **User impact**: high for HIPAA-adjacent deployments (care facilities, eldercare) and for GDPR-jurisdiction users.
+
+Three privacy tiers:
+- `none`: full telemetry (HR, BR, pose, presence, count) published to MQTT and Matter.
+- `semantic` (default): HR/BR/pose stripped at wire; semantic primitives (10 states) published only.
+- `audit-only`: no MQTT state messages; only SHA-256 digests of events logged to the witness chain on the Seed. HA receives heartbeat-only availability messages. Suitable for deployments where the home network is untrusted or subject to external logging.
+
+The audit-only mode is a defensible HIPAA/GDPR position for integrators deploying in care settings — the Seed holds the event record, the network carries nothing personally identifiable.
+
+---
+
+## Recommended Scope for HA+Matter Cog v1
+
+Ranked by **build cost × user impact** (low cost + high impact first):
+
+| Priority | Feature | Build effort | User impact | Ships in |
+|---|---|---|---|---|
+| 1 | **Privacy-mode audit-only tier** (§8.7) | 1 week | High (care/GDPR deployments) | v0.7.1 |
+| 2 | **Seed cog manifest + signing** (§8.3) | 1–2 weeks | High (Seed store distribution) | v0.7.1 |
+| 3 | **Local SONA fine-tuning loop** (§8.4) | 2–3 weeks | High (false-positive reduction) | v0.7.1 |
+| 4 | **HACS integration (gold tier)** (§8.1) | 4–6 weeks | Very high (removes MQTT prereq) | v0.7.2 |
+| 5 | **Multi-room presence handoff** (§8.5) | 3–4 weeks | High (ghost occupancy fix) | v0.7.2 |
+| 6 | **Matter Bridge OccupancySensor + ContactSensor** (§8.2) | 6–8 weeks | High (Apple/Google Home reach) | v0.8.0 |
+| 7 | **Energy disaggregation phantom-load** (§8.6) | 3–4 weeks | Medium-high (sustainability niche) | v0.8.0 |
+| 8 | **Thread Border Router on C6** (§1.2) | 2–3 weeks (config only) | Medium (Thread-fabric users) | v0.8.0 |
+| 9 | **CSA Matter certification** (§1.4) | $30–42k + 3–6 months | Medium (commercial badge) | post-v1.0 |
+
+**Deferred**: Seed-as-Matter-Commissioner (feasible on S3 appliance but requires full chip-tool port; defer to v1.0), full HA quality-scale platinum tier (gold is sufficient for v1 HACS listing), NILM phantom-load (ships as experimental blueprint first, then proper integration).
+
+**Recommended v0.7.1 sprint**: privacy-mode audit tier + cog manifest + SONA fine-tuning = 4–5 weeks total, fully within the existing Rust + ESP32 codebase with no new dependencies. This sprint closes the most impactful gap (care deployments + per-home personalization) before the heavier HACS/Matter work begins.
+
+---
+
+*Research methodology: 8 parallel web search passes, 12 targeted page fetches, cross-referenced against ADR-115 and ADR-110 source files. Evidence grade: High for Matter cluster specifications, FDA guidance, HACS requirements, and ESP32-S3 memory numbers. Medium for CSA certification cost estimates (sourced from forum discussion, not official price list). Low for ruvllm SONA per-home fine-tuning feasibility (derived from library documentation, not benchmarked on Seed hardware). Open question: whether ESP32-S3 PSRAM heap is sufficient for the full Matter Bridge stack alongside the existing sensing-server runtime — a build-and-measure step is needed before committing to the v0.8.0 Matter bridge sprint.*

docs/research/BFLD/01-sota-survey.md

@@ -0,0 +1,293 @@
+# BFLD SOTA Survey — Beamforming Feedback: State of the Art
+
+## 1. BFI vs CSI: Physical-Layer Differences and Leakage Profiles
+
+### 1.1 Channel State Information (CSI)
+
+CSI is the raw complex channel frequency response (CFR) measured at the receiver across
+all subcarriers and antenna pairs. Extracting CSI requires either (a) firmware
+modifications on the receiving NIC (Atheros CSI Tool, Nexmon CSI patch for BCM43455c0
+on Raspberry Pi 4/5) or (b) a specialized radio (software-defined radio with 802.11
+decoders). The resulting matrix is typically Ntx × Nrx × Nsubcarrier complex floats —
+dense, high-dimensional, and not transmitted over the air in standard operation.
+
+This project's existing rvCSI runtime (`vendor/rvcsi/`) captures CSI via the Nexmon
+firmware patch on Raspberry Pi hardware (ADR-095/096). The ESP32-S3 on COM9 cannot
+produce CSI in the format needed for the full pipeline — it lacks the antenna count
+and the firmware support for per-subcarrier phase extraction at the fidelity rvcsi
+expects.
+
+### 1.2 Beamforming Feedback Information (BFI)
+
+BFI is fundamentally different: it is the compressed representation of the channel that
+a STA (station/client) sends back to an AP (access point) so the AP can steer its beam
+toward the client. The standard (IEEE 802.11ac/ax, section 9.4.1.52) defines the
+compressed beamforming format as:
+
+1. The AP transmits a Null Data Packet (NDP) sounding frame.
+2. The STA measures the channel from the NDP, computes the singular-value decomposition
+   V = U Sigma V^H, then compresses the right singular vectors using a series of Givens
+   rotations.
+3. The Givens rotation produces a set of angles: Phi (φ) angles in [0, 2π) and Psi (ψ)
+   angles in [0, π/2). In 802.11ac these are quantized to 7 and 5 bits respectively; in
+   802.11ax the default is 4 bits for φ and 2 bits for ψ.
+4. The STA transmits a VHT/HE Compressed Beamforming frame (CBFR) containing those
+   quantized angles, one set per active subcarrier (or per compressed subcarrier group),
+   plus an SNR field per stream.
+
+The CBFR is a **management-plane 802.11 frame, not an 802.3 data frame**. It is
+transmitted before association encryption is negotiated; in WPA2/WPA3 deployments, the
+beamforming sounding and feedback exchange happens in the clear because WPA2/WPA3
+encrypt data frames only. Even 802.11ax (Wi-Fi 6/6E) with Protected Management Frames
+(PMF) enabled does NOT encrypt action frames in the beamforming exchange by default on
+commodity APs as of 2025 (NDSS 2025 finding, "Lend Me Your Beam",
+https://www.ndss-symposium.org/ndss-paper/lend-me-your-beam-privacy-implications-of-plaintext-beamforming-feedback-in-wifi/).
+
+**Key asymmetry**: extracting CSI requires physical access to a device and firmware
+modification; extracting BFI requires only a WiFi adapter in monitor mode and a parser
+for the CBFR frame format. Wi-BFI (Haque, Meneghello, Restuccia; ACM WiNTECH 2023,
+https://arxiv.org/abs/2309.04408) is an open-source pip-installable tool that does
+exactly this.
+
+### 1.3 Why BFI Is Uniquely Dangerous
+
+CSI is a research instrument — accessing it requires deliberate effort. BFI is a
+production protocol artifact that any 802.11ac/ax STA broadcasts periodically as a
+matter of course. The attack-surface implications:
+
+- **No firmware modification needed** on the target device or AP.
+- **Passive capture** is sufficient. Frames are broadcast in all directions, not
+  beamformed, so a nearby attacker receives them at essentially the same SNR as the AP.
+- **Structured leakage**: the Phi/Psi angle matrices encode a compressed but
+  non-trivially-invertible representation of the spatial channel, which includes
+  multipath geometry that is body-shaped — the human body is a dielectric obstacle whose
+  shape and movement modulate the channel.
+- **Regularity**: sounding happens at the AP's request, typically at 5–40 Hz in modern
+  802.11ax deployments. A 60-second capture at 10 Hz produces 600 CBFR frames —
+  sufficient for the BFId classifier to achieve >90% re-identification accuracy (ACM CCS
+  2025, https://dl.acm.org/doi/10.1145/3719027.3765062).
+
+---
+
+## 2. Compressed Angle Matrices: The Identity Surface
+
+### 2.1 Givens Rotation Reconstruction
+
+The Phi/Psi angles encode a unitary matrix via the Givens rotation decomposition:
+
+    V = G(N, N-1, φ_{N,N-1}, ψ_{N,N-1}) · G(N, N-2, ...) · ... · G(2,1, φ_{2,1}, ψ_{2,1}) · D
+
+where D is a diagonal phase matrix. For a 2×2 MIMO system this is two angles; for a
+4×4 system this is 12 angles. Each "column" in the BFI payload corresponds to one
+subcarrier group (or every 4th subcarrier in 802.11ax, every 2nd in 802.11ac).
+
+The resulting per-subcarrier angle sequence is a time-varying signature of the spatial
+channel. Because the human body modulates the multipath channel, this sequence encodes
+body-specific geometry. The BFId paper (https://dl.acm.org/doi/10.1145/3719027.3765062)
+demonstrates that a supervised classifier trained on these sequences achieves identity
+recognition on a 197-person dataset.
+
+### 2.2 The AI/ML Compression Feedback Loop
+
+IEEE 802.11 standardization is actively exploring AI/ML-based compression for
+beamforming feedback (IEEE 802.11bn / Wi-Fi 8 study group, "Toward AIML Enabled WiFi
+Beamforming CSI Feedback Compression", https://arxiv.org/html/2503.00412v1). This work
+proposes neural codebooks that reduce feedback overhead. An important side effect: the
+learned latent space of a neural BFI compressor may be *more* identity-discriminative
+than the raw angles, because neural compression tends to preserve class-discriminative
+variance. BFLD must be designed to handle compressed BFI encodings, not just the raw
+Phi/Psi format.
+
+---
+
+## 3. Tooling Landscape
+
+### 3.1 Wi-BFI
+
+- **Source**: https://arxiv.org/abs/2309.04408 / https://github.com/kfoysalhaque/MU-MIMO-Beamforming-Feedback-Extraction-IEEE802.11ac
+- **Capabilities**: real-time and offline extraction of BFAs from 802.11ac and 802.11ax;
+  20/40/80/160 MHz; SU-MIMO and MU-MIMO; pip-installable.
+- **Relevance to BFLD**: the BFLD extractor module (`extractor.rs`) must produce
+  semantically equivalent output to Wi-BFI — i.e., per-subcarrier Phi/Psi angle arrays
+  plus per-stream SNR — so that research results from the Wi-BFI ecosystem can be
+  replicated on BFLD captures.
+
+### 3.2 PicoScenes
+
+- **Source**: https://www.semanticscholar.org/paper/Eliminating-the-Barriers-Demystifying-Wi-Fi-Baseband-Jiang-Zhou/...
+- **Capabilities**: cross-NIC CSI and CBFR measurement platform; supports Intel AX200,
+  AX210, Atheros AR9300, QCA6174; runs on Linux with custom kernel modules.
+- **Relevance to BFLD**: PicoScenes can simultaneously capture CSI and BFI from the
+  same frame sequence, enabling the CSI+BFI fusion path described in the BFLD spec
+  (`csi_matrix` optional input). The rvcsi adapter layer (`vendor/rvcsi/`) already
+  handles the Nexmon PCap format; a PicoScenes adapter is a future extension.
+
+### 3.3 Nexmon CSI (BCM43455c0)
+
+- **Source**: https://github.com/seemoo-lab/nexmon_csi
+- **Hardware**: Raspberry Pi 4/5 with BCM43455c0 chip — the same hardware used in
+  `cognitum-v0` (Pi 5 appliance in this fleet, see CLAUDE.local.md).
+- **Capabilities**: per-subcarrier complex CSI in monitor mode; 4×4 MIMO on Pi 5 with
+  BCM43456.
+- **Relevance to BFLD**: the rvcsi nexmon adapter already routes PCap frames from this
+  hardware into the wifi-densepose pipeline. BFI extraction on the same hardware requires
+  an additional sniffer for CBFR frames alongside the CSI sniffer.
+
+### 3.4 Atheros CSI Tool / iwlwifi CSI
+
+- Legacy tools for Intel and Atheros NICs; require kernel module injection. Not relevant
+  to the current hardware fleet (ESP32-S3 + Raspberry Pi 5), but documented here for
+  completeness and for future Intel AX210-based deployments.
+
+---
+
+## 4. Identity Inference Attacks
+
+### 4.1 BFId (ACM CCS 2025)
+
+**Reference**: Todt, Morsbach, Strufe; KIT. ACM CCS 2025.
+https://dl.acm.org/doi/10.1145/3719027.3765062
+https://publikationen.bibliothek.kit.edu/1000185756
+Dataset: https://ps.tm.kit.edu/english/bfid-dataset/index.php
+
+BFId is the first published identity-inference attack that uses BFI exclusively (no
+CSI). The methodology:
+
+1. **Dataset**: 197 individuals, multiple sessions, multiple AP angles. Each subject
+   walked a defined path while their STA continuously triggered BFI exchanges. CSI
+   was also recorded simultaneously for comparison.
+2. **Feature extraction**: temporal sequences of Phi/Psi angle matrices, windowed at
+   varying lengths. Basic statistical features (mean, variance, cross-subcarrier
+   correlation) fed a shallow classifier.
+3. **Results**: re-identification accuracy >90% with as little as 5 seconds of BFI.
+   Performance was robust to different walking styles and viewing angles — consistent
+   with the hypothesis that anthropometric body shape (torso width, stride, limb
+   geometry) rather than gait phase is the primary discriminator.
+4. **Comparison to CSI**: BFI-only accuracy was comparable to CSI-only accuracy for
+   identity tasks, despite BFI being a compressed representation. This confirms that
+   the Givens angle compression preserves identity-discriminative variance.
+
+### 4.2 LeakyBeam (NDSS 2025)
+
+**Reference**: Xiao, Chen, He, Han, Han; Zhejiang U., NTU, KAIST. NDSS 2025.
+https://www.ndss-symposium.org/ndss-paper/lend-me-your-beam-privacy-implications-of-plaintext-beamforming-feedback-in-wifi/
+
+LeakyBeam targets occupancy detection (is a person present?) rather than identity.
+Key findings:
+
+- BFI is detectable through walls at 20 m range with commodity hardware.
+- True positive rate 82.7%, true negative rate 96.7% in real-world evaluation.
+- The attack works because BFI encodes motion-induced channel perturbations even through
+  obstacles — the Phi/Psi angle variance changes measurably when a body enters the room.
+- The defense (obfuscating BFI before transmission) requires minimal hardware changes.
+
+**Implication for BFLD**: if a passive attacker with no relationship to the AP can
+detect occupancy, then the BFLD node is implicitly broadcasting presence information
+unless active obfuscation is deployed at the STA firmware level. BFLD cannot prevent
+this passive attack — it can only ensure the *node's own output* does not additionally
+leak identity.
+
+### 4.3 Prior RF-Based Gait and Biometric Inference
+
+Before BFI-specific attacks, the threat landscape was already established through
+CSI-based attacks:
+
+- **Gait from CSI**: WiGait (2017), Wi-Gait (ScienceDirect 2023,
+  https://www.sciencedirect.com/science/article/abs/pii/S1389128623001962),
+  Gait+Respiration ID (IEEE Xplore 2021,
+  https://ieeexplore.ieee.org/document/9488277) all demonstrate >90% gait-based
+  re-identification from standard WiFi.
+- **Breathing biometrics**: Respiration rate and depth are person-specific at a
+  population level. IEEE 802.11 CSI captures breathing as amplitude oscillations at
+  0.1–0.5 Hz.
+- **Anthropometric inference**: Hand size, torso width, and limb geometry modulate the
+  channel; classifiers trained on activity data have been shown to leak anthropometrics
+  as a side effect.
+
+The BFId finding that BFI achieves comparable accuracy to CSI for identity is consistent
+with this prior body of work — it simply demonstrates the attack is achievable with a
+lower barrier to entry.
+
+---
+
+## 5. Privacy-Preserving Sensing: Current State of the Art
+
+### 5.1 Differential Privacy on RF Embeddings
+
+"Differentially Private Feature Release for Wireless Sensing: Adaptive Privacy Budget
+Allocation on CSI Spectrograms" (https://arxiv.org/pdf/2512.20323) applies Laplace/
+Gaussian mechanisms to CSI spectrograms, calibrating epsilon per subcarrier based on
+empirical sensitivity. Results show meaningful reduction in identity-inference accuracy
+while preserving activity-recognition utility at epsilon = 1.0–4.0.
+
+BFLD's `identity_risk_score` could be used as an adaptive epsilon selector: high-risk
+frames receive a tighter privacy budget (more noise), low-risk frames pass unmodified.
+This is a forward-looking integration not in the current spec.
+
+### 5.2 Federated / Local-Only Inference
+
+The consensus across 2024–2025 literature on wireless federated learning
+(https://arxiv.org/pdf/2603.19040, https://arxiv.org/pdf/2109.09142) is that
+local differential privacy (LDP) with gradient perturbation is achievable on resource-
+constrained edge devices. For BFLD's use case the critical property is simpler: the
+identity embedding never needs to leave the node. There is no federated learning step
+for identity. The risk score is a local computation whose output is published; the
+embedding that produced it is not.
+
+### 5.3 ZK Attestation for Sensing
+
+ZK-SenseLM (https://arxiv.org/pdf/2510.25677) proposes zero-knowledge proofs that a
+sensing model's output derives from legitimate data. This is architecturally close to
+ADR-028's witness-bundle approach. Future BFLD work could use ZK proofs to attest that
+the identity_risk_score was computed from the claimed input without revealing the input.
+
+### 5.4 "Protecting Human Activity Signatures in Compressed IEEE 802.11 CSI Feedback"
+
+(https://arxiv.org/pdf/2512.18529) — This 2024 paper directly addresses activity-
+signature leakage in CBFR frames and proposes perturbation of Phi/Psi angles at the STA
+before transmission. The defense is the dual of BFLD's approach: BFLD detects leakage
+at the receiver; this paper proposes suppression at the transmitter. Both approaches
+are complementary.
+
+---
+
+## 6. Relationship to Existing Project ADRs
+
+**ADR-027 (MERIDIAN cross-environment generalization)**: BFLD's cross-room hash
+rotation directly instantiates the "no cross-site correlation" invariant that MERIDIAN
+assumes for privacy-safe multi-room deployment.
+
+**ADR-028 (ESP32 capability audit + witness verification)**: The deterministic-proof
+pattern (`verify.py` + SHA-256 expected hash) is the template for BFLD's own acceptance
+test. BFLD must produce a deterministic frame hash given the same input — acceptance
+criterion 6 in the spec.
+
+**ADR-024 (AETHER contrastive CSI embedding)**: BFLD reuses the AETHER embedding
+infrastructure for its identity_risk measurement. The risk score is a function of how
+separable the current embedding is from the population of known embeddings.
+
+**ADR-029/030 (RuvSense multistatic + field model)**: BFLD's `cross_perspective_
+consistency` component of the risk formula requires correlation across multiple sensor
+viewpoints — the multistatic infrastructure from ADR-029 provides this.
+
+**ADR-032 (multistatic mesh security hardening)**: The BFLD threat model is a
+superset of the security model in ADR-032. ADR-032 covers mesh compromise; BFLD adds
+the passive sniffing threat at the management-plane layer.
+
+---
+
+## 7. Open Technical Questions
+
+1. **BFI capture on ESP32-S3**: The ESP32-S3's `esp_wifi_csi_set_config` API provides
+   CSI via the vendor-specific Espressif HT20 format. It does not expose VHT/HE CBFR
+   frames. BFI capture on this hardware likely requires host-side sniffing (Pi 5 +
+   Nexmon in monitor mode, already available on cognitum-v0).
+
+2. **Quantization resolution degradation**: At 4 bits for φ and 2 bits for ψ (802.11ax
+   defaults), the angle resolution is coarser than in 802.11ac (7/5 bits). The BFId
+   paper used 802.11ac hardware. BFLD must validate that the identity_risk_score
+   calibration remains valid at lower quantization.
+
+3. **WiFi 7 (802.11be) changes**: 802.11be introduces multi-link operation (MLO) and
+   may change the sounding/feedback cadence. BFLD's frame format (magic 0xBF1D_0001,
+   version byte) is designed to accommodate future protocol versions.

docs/research/BFLD/02-soul.md

@@ -0,0 +1,141 @@
+# BFLD Soul — Architectural Intent and Ethical Stance
+
+## 1. The Central Metaphor: Immune System, Not Surveillance Lens
+
+An immune system does not catalog every pathogen it encounters. It classifies threats
+by type, responds proportionally, and keeps its detailed records local to the organism.
+When the immune system flags a cell as dangerous, it does not broadcast the cell's
+identity to the outside world — it takes local action.
+
+BFLD is built around this same principle. Its job is to detect when RF data is crossing
+from the realm of "ambient sensing" into the realm of "identity record" — and to respond
+locally: raise the risk score, restrict what leaves the node, rotate identifiers. It does
+not produce identity; it guards against the accidental production of identity.
+
+This distinction matters because the same physical signal that drives BFLD's presence
+detection is also the signal that academic attackers (BFId, LeakyBeam) exploit for
+re-identification. BFLD cannot suppress the underlying physics. What it can do is make
+the node's *output* non-identifying, even when the node's *input* is capable of
+supporting identification.
+
+---
+
+## 2. Distinguishing Identity from the Rest of WiFi Sensing
+
+WiFi sensing produces a spectrum of information:
+
+| Output | Privacy class | Reversibility |
+|--------|--------------|---------------|
+| Presence (yes/no) | 2 — anonymous | Not reversible to identity |
+| Motion magnitude (0..1) | 1 — derived | Not reversible to identity |
+| Person count (integer) | 1 — derived | Not reversible to identity |
+| Zone activity | 1 — derived | Not reversible to identity |
+| Identity risk score | 1 — derived | Risk score, not identity |
+| RF signature hash | 1 — derived | Hash rotates daily; not reversible |
+| Identity embedding | 0 — raw | Directly reversible to biometric |
+| Raw BFI matrix | 0 — raw | Directly reversible to biometric |
+
+BFLD's design follows this table structurally: the outputs in privacy class 0 never
+leave the node. The outputs in class 1 leave the node only after explicit operator opt-in
+for the sensitive ones (identity_risk_score). The outputs in class 2 flow freely.
+
+This table is not a policy list — it is wired into the frame format. The `privacy_class`
+byte in every `BfldFrame` is checked at the emitter boundary before any byte leaves the
+node. Code that wants to send class-0 data must positively bypass a compile-time safety
+check, not merely forget to set a flag.
+
+---
+
+## 3. Three Non-Negotiable Invariants
+
+These are not configurable options. They are structural properties of BFLD that
+hold regardless of operator configuration:
+
+### Invariant 1: Raw BFI Never Leaves the Node
+
+The BFI matrix, once ingested by the BFLD extractor, is consumed locally and never
+serialized to any outbound channel. This is enforced in two ways:
+
+1. The `BfldFrame` struct's `bfi_matrix` field is not part of the serializable payload
+   — it exists only as a private field in `extractor.rs` and is dropped after
+   feature extraction completes.
+2. The MQTT emitter (`mqtt.rs`) has no code path that serializes a BFI matrix.
+   The `ruview/<node_id>/bfld/raw/state` topic is disabled by default and, when
+   enabled, publishes only a metadata summary (subcarrier count, timestamp, SNR range),
+   not the angle matrices.
+
+### Invariant 2: Identity Embedding Is Local-Only
+
+The embedding computed by the RuVector pipeline (used to calculate `identity_risk_score`)
+lives in an in-RAM ring buffer with a configurable retention window (default: 10 minutes).
+It is never written to disk. It is never serialized to any MQTT topic. It is never
+included in any `BfldFrame` payload even at `privacy_class = 0` — raw means raw angles,
+not the derived embedding.
+
+The mathematical property that enables this: `identity_risk_score` can be computed as a
+scalar from the embedding (separability × temporal_stability × cross_perspective_
+consistency × sample_confidence) without revealing the embedding itself. The score is a
+projection onto a scalar; the full vector is not required by any downstream consumer.
+
+### Invariant 3: Cross-Site Identity Matching Is Structurally Impossible
+
+The `rf_signature_hash` is computed as:
+
+    blake3(site_salt ‖ day_epoch ‖ ephemeral_features)
+
+where `site_salt` is a secret generated at first boot, stored in NVS, and never
+transmitted. Two BFLD nodes at two different sites will produce hashes in disjoint
+hash spaces by construction. Even an adversary who obtains the hash stream from
+both nodes cannot determine whether the same person visited both sites, because the
+site_salt is unknown and different.
+
+The daily rotation (`day_epoch` = floor(timestamp_ns / 86400e9)) means that even within
+a single site, the hash of the same person changes each day. Hashes older than 24 hours
+have zero correlation with hashes produced today.
+
+This is structural impossibility, not policy. The invariant holds even if the operator
+misconfigures the system, because it derives from the cryptographic property of blake3
+with a secret key, not from access-control rules.
+
+---
+
+## 4. Relationship to RuView's Ambient Intelligence Positioning
+
+The project memory records RuView's positioning as "ambient intelligence platform, not
+sensor; packaging (HA, Docker, mDNS, blueprints) is the bottleneck." This framing is
+load-bearing for BFLD's design.
+
+A "sensor" in the Home Assistant model is a device that reports measurements. A "sensor"
+is allowed to identify who is present — facial recognition cameras are sensors. BFLD
+explicitly rejects this model: the node is an ambient intelligence node that knows
+something about the environment (motion, occupancy, activity level) but structurally
+cannot know *who* is in the environment.
+
+This positioning enables deployment in spaces where identity-tracking would be
+unacceptable: shared workspaces, guest accommodations, hotel rooms, care facilities.
+The argument to an operator at a care facility is not "trust us, we won't log who your
+patients are." It is: "the system is architecturally incapable of logging who your
+patients are, because the identifier rotates daily with a site-specific secret we don't
+hold."
+
+---
+
+## 5. Why This Layer Must Exist Before WiFi 7 Ships
+
+802.11be (Wi-Fi 7) is entering mass market deployment in 2025–2026. It introduces
+multi-link operation (MLO), which dramatically increases the frequency of beamforming
+sounding exchanges. Where 802.11ax sonding might occur at 10–40 Hz, MLO sounding on
+multiple links simultaneously could produce 3–5× more CBFR frames per second.
+
+More frames means more training data for identity classifiers. The BFId result at 5
+seconds of 802.11ac data will almost certainly improve with 5 seconds of 802.11be MLO
+data. The attack surface is not static.
+
+BFLD's frame format (magic 0xBF1D_0001, version byte for extension) is designed to
+remain valid across protocol generations. The feature extraction modules are pluggable:
+a WiFi 7 BFI extractor can be added without changing the privacy gate, the hash rotation,
+or the MQTT emitter. The invariants remain invariant.
+
+The window to establish safe defaults is now, before the installed base is hundreds of
+millions of unprotected nodes. BFLD is the layer that carries those safe defaults into
+every deployment from day one.

docs/research/BFLD/03-security-threat-model.md

@@ -0,0 +1,278 @@
+# BFLD Security Threat Model
+
+## 1. Adversary Classes
+
+### A1 — Passive Sniffer (Curious Neighbor)
+
+**Capability**: WiFi adapter in monitor mode; consumer laptop running Wi-BFI or
+tcpdump with CBFR filter. No special access, no relationship to the target network.
+
+**Goal**: Determine occupancy or identity of persons in an adjacent apartment/office.
+
+**Effort**: Low. Wi-BFI is pip-installable. Monitor mode is available on commodity
+Linux laptops. No prior knowledge of the target network required — CBFR frames are
+broadcast in all directions.
+
+**Relevance to BFLD**: A1 is the LeakyBeam threat (NDSS 2025). BFLD cannot prevent
+A1 from capturing BFI from the air. BFLD's job is to ensure its own output does not
+make A1's work easier by publishing identity-correlated data on reachable channels.
+
+### A2 — Targeted Stalker
+
+**Capability**: A1 capabilities plus knowledge of the target's device MAC address
+(obtainable from BSSID probe requests) and time correlation with known schedules.
+
+**Goal**: Track a specific individual's presence across time or across locations.
+
+**Effort**: Medium. Requires sustained monitoring (hours to days) and a correlation
+step.
+
+**Relevance to BFLD**: If rf_signature_hash were stable over time, A2 could correlate
+hash sequences across sessions to confirm a specific person's schedule. The daily hash
+rotation (Invariant 3) severs this correlation.
+
+### A3 — ISP / Operator
+
+**Capability**: Access to MQTT broker, HA instance, or cloud integration receiving
+BFLD events.
+
+**Goal**: Build behavioral profiles of occupants across many homes/installations.
+
+**Effort**: Low if raw or identity-correlated fields are published to the broker.
+
+**Relevance to BFLD**: BFLD restricts what reaches the broker. An operator cannot
+accidentally publish identity-correlated data because the privacy gate blocks it at
+the node boundary.
+
+### A4 — Nation-State / Law Enforcement
+
+**Capability**: Compelled access to cloud storage, MQTT broker logs, or HA history.
+Physical access to the BFLD node with forensic tools.
+
+**Goal**: Retrospectively identify who was present at a location and when.
+
+**Effort**: Depends on what data was logged. If BFLD's invariants hold, the broker
+holds only: presence events (boolean), motion scores (float), person counts (integer),
+and rotated hashes. None of these are individually re-identifiable.
+
+**Relevant mitigation**: The daily hash rotation means that even log retention is
+privacy-preserving: a hash from Monday and a hash from Tuesday, even from the same
+person at the same node, are in disjoint hash spaces.
+
+### A5 — Compromised AP Firmware
+
+**Capability**: Malicious AP firmware that modifies the sounding schedule to extract
+more identity-discriminative BFI, or that responds to specially crafted packets with
+high-resolution channel feedback.
+
+**Goal**: Improve passive capture quality from the node's BFI stream.
+
+**Relevance to BFLD**: BFLD ingests BFI as captured from the air. If the AP is
+compromised to produce unusually high-resolution BFI, BFLD's identity_risk_score
+will correctly detect the elevated separability and flag the frames at higher risk.
+The system is self-normalizing to the quality of what is captured.
+
+### A6 — Supply-Chain Compromise of RuView Node
+
+**Capability**: Modified BFLD binary with the privacy gate removed or with an
+exfiltration path added.
+
+**Goal**: Long-term silent collection of identity embeddings or raw BFI.
+
+**Mitigation**: ADR-028's witness-bundle pattern — deterministic SHA-256 of the
+pipeline output. A compromised binary would produce different output for the same
+input, failing the verify.py check. The BFLD acceptance criterion 6 (deterministic
+frame hashes) is the direct countermeasure.
+
+---
+
+## 2. Attack Trees
+
+### AT-1: Passive BFI Capture → Identity Inference
+
+```
+Attacker Goal: Re-identify a specific person via BFI
+|
++-- Step 1: Place WiFi adapter in monitor mode (A1)
+|     |
+|     +-- CBFR frames arrive unencrypted (established by NDSS 2025 / BFId)
+|
++-- Step 2: Parse Phi/Psi angles using Wi-BFI or equivalent
+|     |
+|     +-- No modification of target device required (Wi-BFI passive)
+|
++-- Step 3: Collect 5-60 seconds of frames
+|     |
+|     +-- BFId: 5s sufficient at 10 Hz sounding rate for >90% accuracy
+|
++-- Step 4: Run identity classifier (BFId architecture or similar)
+|     |
+|     +-- Requires enrollment (prior reference capture)
+|     |     |
+|     |     +-- OR: exploit BFLD's rf_signature_hash as a correlation anchor
+|     |               (mitigated by daily rotation — AT-2 below)
+|
++-- Outcome: Identity label with >90% confidence
+```
+
+BFLD mitigation: BFLD does not prevent AT-1 at the air interface. It ensures that
+BFLD's own output does not provide the "correlation anchor" in step 4.
+
+### AT-2: Cross-Site Correlation via rf_signature_hash Leak
+
+```
+Attacker Goal: Confirm person X visited site A and site B on the same day
+|
++-- Prerequisite: Attacker has read access to MQTT broker at both sites
+|
++-- Step 1: Collect rf_signature_hash sequences from site A and site B
+|
++-- Step 2: Look for matching hashes within the same day_epoch
+|     |
+|     +-- BLOCKED: site_salt is site-specific and secret.
+|           blake3(salt_A ‖ day ‖ features) != blake3(salt_B ‖ day ‖ features)
+|           even if features are identical.
+|           Two sites with the same person produce hashes in disjoint spaces.
+|
++-- Outcome: No match possible. Attack fails structurally.
+```
+
+### AT-3: Timing Side-Channel on identity_risk_score
+
+```
+Attacker Goal: Infer when a known person is present by monitoring risk score changes
+|
++-- Prerequisite: Read access to MQTT topic ruview/<node_id>/bfld/identity_risk/state
+|
++-- Step 1: Baseline: collect identity_risk_score during known-empty periods
+|
++-- Step 2: Monitor for anomalous spikes correlated with known schedules
+|     |
+|     +-- Partial mitigation: risk score is not published by default.
+|     |     Operator must explicitly enable it.
+|     |
+|     +-- Residual risk: even with publication enabled, the score measures risk of
+|           identification, not identity itself. A high risk score means "this frame
+|           is identity-discriminative" not "person X is present."
+|
++-- Mitigation: MQTT ACL restricts identity_risk to local broker by default.
++-- Mitigation: privacy_class=3 (restricted) zeros the risk score on output.
+```
+
+### AT-4: MQTT Topic Enumeration
+
+```
+Attacker Goal: Discover what BFLD data is published and harvest it
+|
++-- Step 1: Connect to broker without TLS (if TLS not configured)
+|
++-- Step 2: Subscribe to ruview/# wildcard
+|
++-- Mitigation: Default mosquitto ACL denies wildcard subscription to anonymous clients.
++-- Mitigation: TLS + client certificates recommended for all BFLD deployments.
++-- Mitigation: ruview/<node_id>/bfld/raw/state is disabled by default.
+```
+
+### AT-5: Matter Cluster Abuse
+
+```
+Attacker Goal: Extract identity-correlated data via the Matter protocol integration
+|
++-- Step 1: Join the Matter fabric as a legitimate controller
+|
++-- Step 2: Read clusters exposed by the BFLD Matter endpoint
+|     |
+|     +-- Available: OccupancySensing (presence), MotionSensor (motion),
+|           PeopleCount (person_count)
+|     |
+|     +-- NOT AVAILABLE: identity_risk_score, rf_signature_hash, raw_bfi,
+|           identity_embedding — these are rejected at the Matter boundary.
+|
++-- Outcome: Attacker gets presence/motion/count — same as any occupancy sensor.
+      No identity-correlated data is accessible via Matter.
+```
+
+---
+
+## 3. Trust Boundary Diagram
+
+```
+┌────────────────────────────────────────────────────────────────────────┐
+│                          BFLD NODE (local)                             │
+│                                                                        │
+│  WiFi air interface                                                    │
+│       │ CBFR frames (unencrypted, passively sniffable by any A1)       │
+│       ▼                                                                │
+│  ┌──────────────┐    raw BFI   ┌──────────────┐                       │
+│  │  BFI         │──────────────│  Feature     │                       │
+│  │  Extractor   │  (local RAM) │  Extractor   │                       │
+│  └──────────────┘              └──────┬───────┘                       │
+│                                       │ features (not BFI)             │
+│                                       ▼                                │
+│                               ┌──────────────┐    embedding           │
+│                               │  Identity    │──────────────┐         │
+│                               │  Risk Engine │  (local RAM  │         │
+│                               └──────┬───────┘   ring buf)  │         │
+│                                      │ risk_score            │         │
+│                                      ▼                        │         │
+│  ┌───────────────────────────────────────────────────────┐   │         │
+│  │                Privacy Gate                           │   │         │
+│  │  privacy_class check | hash rotation | field masking  │   │         │
+│  └───────┬──────────────────────────────────────────────┘   │         │
+│          │ filtered BfldFrame                  [embedding     │         │
+│          │ (no raw BFI, no embedding)           NEVER exits  │         │
+│          ▼                                      this box]    │         │
+│  ┌──────────────┐                                            │         │
+│  │  MQTT        │ presence/motion/person_count/risk(opt)     │         │
+│  │  Emitter     │────────────────────────────────────────►  │         │
+│  └──────────────┘  [TLS recommended]                         │         │
+│                                                              │         │
+└──────────────────────────────────────────────────────────────┘─────────┘
+         │
+         │ MQTT (TLS)
+         ▼
+┌─────────────────────┐         ┌──────────────────────────────────────┐
+│  Local Broker       │         │  cognitum-v0 federation endpoint     │
+│  (mosquitto)        │──────►  │  (identity fields STRIPPED at node   │
+└────────┬────────────┘         │   boundary before federation)        │
+         │                      └──────────────────────────────────────┘
+         │
+         ▼
+┌─────────────────────┐         ┌──────────────────────────────────────┐
+│  Home Assistant     │──────►  │  Matter Fabric                       │
+│  (presence/motion/  │         │  (OccupancySensing / MotionSensor /  │
+│   person_count only)│         │   PeopleCount ONLY)                  │
+└─────────────────────┘         └──────────────────────────────────────┘
+```
+
+---
+
+## 4. Threat Profile per privacy_class Value
+
+| privacy_class | Value | Data exposed outbound | Residual threats |
+|--------------|-------|----------------------|-----------------|
+| raw | 0 | Derived angles + amplitude proxy + phase proxy + SNR. Never BFI matrix. | Angle sequences are identity-discriminative; use only in controlled research environments. Never default. |
+| derived | 1 | All BFLD output fields including identity_risk_score and rf_signature_hash. | Risk score timing side-channel (AT-3). Hash must remain rotated. |
+| anonymous | 2 | presence, motion, person_count, zone_activity, confidence. No identity-correlated fields. | Temporal occupancy patterns may leak schedule information. Not identity. |
+| restricted | 3 | presence only (binary). All other fields zeroed or suppressed. | Minimal. On/off presence is equivalent to a passive IR sensor. |
+
+---
+
+## 5. Witness / Attestation Strategy
+
+Following ADR-028's pattern, BFLD should produce a deterministic proof bundle:
+
+1. **Reference input**: a fixed seed synthetic BFI matrix (512 bytes, PRNG seed=117)
+   stored alongside the test suite.
+2. **Expected output hash**: SHA-256 of the serialized `BfldFrame` produced from that
+   input, committed to the repository.
+3. **CI check**: `verify_bfld.py` — same structure as `archive/v1/data/proof/verify.py`
+   — runs in CI and locally. A compromised binary (A6 threat) would change the output
+   hash and immediately fail this check.
+4. **Witness log**: extend `docs/WITNESS-LOG-028.md` with a BFLD section covering the
+   privacy gate and hash rotation.
+
+This attestation does not prevent a runtime compromise, but it raises the cost
+significantly: a supply-chain attacker must either (a) match the expected output hash
+while also exfiltrating data (computationally infeasible for a hash adversary), or
+(b) accept that the tampered binary will be detected on the next verify run.

docs/research/BFLD/04-privacy-gating.md

@@ -0,0 +1,279 @@
+# BFLD Privacy Gating — Mechanisms in Depth
+
+## 1. The privacy_class Byte: Concrete Data Exposure Tables
+
+The `privacy_class` byte is the single authoritative classifier for what a BFLD node
+is permitted to emit. It is set by the privacy gate module (`privacy_gate.rs`) on every
+outbound `BfldFrame` based on the computed `identity_risk_score` and operator configuration.
+
+### Class 0 — raw
+
+Intended exclusively for local research captures and red-team validation. Not a
+deployable configuration.
+
+| Field | Published | Notes |
+|-------|-----------|-------|
+| presence | Yes | Boolean |
+| motion | Yes | 0..1 float |
+| person_count | Yes | u8 |
+| identity_risk_score | Yes | f32 |
+| rf_signature_hash | Yes | Rotated blake3, 32 bytes hex |
+| zone_activity | Yes | |
+| confidence | Yes | |
+| compressed_angle_matrix | Yes | Phi/Psi per subcarrier — the sensitive surface |
+| amplitude_proxy | Yes | |
+| phase_proxy | Yes | |
+| snr_vector | Yes | |
+| bfi_matrix (raw) | NEVER | Dropped before serialization; not in wire format |
+| identity_embedding | NEVER | Local RAM only; not in wire format |
+
+### Class 1 — derived
+
+Default for operator-opted-in diagnostics. Includes identity_risk_score and hash but
+no angle matrices.
+
+| Field | Published | Notes |
+|-------|-----------|-------|
+| presence | Yes | |
+| motion | Yes | |
+| person_count | Yes | |
+| identity_risk_score | Yes | Diagnostic; not in HA default entities |
+| rf_signature_hash | Yes | Rotated hash only |
+| zone_activity | Yes | |
+| confidence | Yes | |
+| compressed_angle_matrix | No | Zeroed |
+| amplitude_proxy | No | |
+| phase_proxy | No | |
+| snr_vector | Yes | Per-stream aggregate only |
+| bfi_matrix (raw) | NEVER | |
+| identity_embedding | NEVER | |
+
+### Class 2 — anonymous
+
+Default for all standard deployments. No identity-correlated fields.
+
+| Field | Published | Notes |
+|-------|-----------|-------|
+| presence | Yes | |
+| motion | Yes | |
+| person_count | Yes | |
+| identity_risk_score | No | Suppressed |
+| rf_signature_hash | No | Suppressed |
+| zone_activity | Yes | |
+| confidence | Yes | |
+| All angle/amplitude/phase fields | No | Zeroed |
+| bfi_matrix (raw) | NEVER | |
+| identity_embedding | NEVER | |
+
+### Class 3 — restricted
+
+Maximum privacy. Suitable for care facilities, medical deployments, guest spaces.
+
+| Field | Published | Notes |
+|-------|-----------|-------|
+| presence | Yes | |
+| motion | No | Suppressed |
+| person_count | No | Suppressed |
+| All other fields | No | |
+| bfi_matrix (raw) | NEVER | |
+| identity_embedding | NEVER | |
+
+---
+
+## 2. rf_signature_hash Rotation Algorithm
+
+### Construction
+
+```
+site_salt   := blake3_keyed_hash(secret="bfld-site-seed", data=node_mac_address)
+               # Generated once at first boot, stored in NVS, never transmitted
+               # 32 bytes
+
+day_epoch   := floor(timestamp_ns / 86_400_000_000_000)
+               # One new epoch per UTC day
+
+ephemeral   := mean_angle_delta ‖ subcarrier_variance ‖ burst_motion_score
+               # A small fixed-length summary of the current window's features
+               # Not identity-specific — any of several persons could produce
+               # similar values
+
+rf_signature_hash := BLAKE3(
+    key   = site_salt,            // 32 bytes; site-specific secret key
+    input = day_epoch_bytes(8) ‖ ephemeral_features(24)
+)
+```
+
+### Why cross-site re-identification is structurally impossible
+
+Two BFLD nodes at sites A and B produce:
+
+```
+hash_A = BLAKE3(key=salt_A, input=day ‖ features)
+hash_B = BLAKE3(key=salt_B, input=day ‖ features)
+```
+
+BLAKE3 is a PRF (pseudorandom function family) keyed on site_salt. Given identical
+`day ‖ features` inputs, hash_A and hash_B are pseudorandom and independent because
+salt_A != salt_B. An adversary who observes hash_A and hash_B cannot determine whether
+they correspond to the same person without knowing both salts.
+
+This is not a security proof; it is a consequence of BLAKE3's PRF security assumption,
+which holds as long as the site_salt remains secret.
+
+### Why within-site, within-day tracking is safe
+
+Within a single day at a single site, two frames from the same person will produce
+similar ephemeral features, leading to similar (though not identical — ephemeral features
+have some frame-to-frame variation) hash values. This is intentional: it allows
+clustering of same-person events within a session without enabling identity recovery.
+
+The hash is NOT the identity. It is a pseudonym within the scope of (site, day). A
+person who visits the same site on two different days gets different pseudonyms on each
+day.
+
+### Daily rotation schedule
+
+```
+epoch_0 = 0                        # day 0 (unix epoch: 1970-01-01)
+epoch_k = k * 86_400_000_000_000   # day k in nanoseconds
+rotation_time = epoch_{k+1}        # midnight UTC
+```
+
+At rotation time, all existing rf_signature_hash values become cryptographically
+disconnected from future values. Logs from before rotation cannot be correlated with
+logs after rotation even by the node operator.
+
+---
+
+## 3. Identity Embedding Lifecycle
+
+```
+BFI frame arrives
+      |
+      v
+Feature extraction (identity_risk.rs)
+      |
+      v
+RuVector embedding computed: Vec<f32, 128>
+      |
+      +-------> identity_risk_score (scalar projection)
+      |         Published (class 1) or suppressed (class 2/3)
+      |
+      v
+In-RAM ring buffer (EmbeddingRingBuf)
+      - capacity: 600 frames (default 10 minutes at 1 Hz)
+      - implemented as VecDeque<Embedding> in heap memory
+      - NEVER written to disk (no serde, no file I/O in the type)
+      - NEVER serialized to any MQTT or HTTP path
+      - Cleared on node restart (RAM is volatile)
+      |
+      v [after retention window]
+Dropped from ring buffer
+```
+
+The ring buffer serves two purposes: (1) temporal_stability calculation requires
+comparing the current embedding to recent embeddings; (2) the coherence gate
+(`coherence_gate.rs`, from `v2/crates/wifi-densepose-signal/src/ruvsense/`) uses
+recent frames to determine whether a new frame is a continuation of an existing
+trajectory or a new event.
+
+Both purposes require only that the embeddings exist in RAM during the computation.
+Neither purpose requires persistence.
+
+---
+
+## 4. Privacy-Mode Wire-Format Diff
+
+The following shows what changes in the serialized `BfldFrame` payload when the node
+transitions from class 1 (derived) to class 2 (anonymous), which is the transition
+that happens when `privacy_mode` is enabled by the operator.
+
+```
+BfldFrame {
+    magic: 0xBF1D_0001,               // unchanged
+    version: 1,                        // unchanged
+    ap_id: blake3(node_mac ‖ "ap"),   // unchanged (already hashed at ingress)
+    sta_id: ephemeral_u64,             // unchanged (already ephemeral)
+    session_id: u64,                   // unchanged
+    quantization: 0x02,                // unchanged (i8 in class 1)
+    privacy_class: 0x01 -> 0x02,       // CHANGED
+
+    // Payload (compressed):
+    compressed_angle_matrix: [...],    // class 1: present; class 2: zeroed + omitted
+    amplitude_proxy: [...],            // class 1: present; class 2: omitted
+    phase_proxy: [...],                // class 1: present; class 2: omitted
+    snr_vector: [...],                 // class 1: present; class 2: present (aggregate)
+
+    // Event (JSON within payload or outer envelope):
+    presence: true,                    // unchanged
+    motion: 0.42,                      // unchanged
+    person_count: 1,                   // unchanged
+    identity_risk_score: 0.71,         // class 1: present; class 2: OMITTED
+    rf_signature_hash: "a3f2...",      // class 1: present; class 2: OMITTED
+    zone_activity: "living_room",      // unchanged
+    confidence: 0.88,                  // unchanged
+    payload_crc32: <recomputed>        // recomputed after changes
+}
+```
+
+The wire-format diff is verified by the acceptance test suite: the same input must
+produce a deterministic output for each privacy_class value.
+
+---
+
+## 5. Default-Deny Posture for Future Fields
+
+Every new field added to `BfldFrame` or the BFLD event JSON in the future MUST be
+classified before it ships. The process:
+
+1. New field is added to `BfldFrame` struct.
+2. A `#[privacy_class(minimum = N)]` attribute annotation (or equivalent runtime
+   check in `privacy_gate.rs`) declares the minimum privacy class at which this
+   field is suppressed.
+3. Unit test asserts that serializing at class < N includes the field and at class ≥ N
+   omits it.
+4. The PR that adds the field cannot pass CI without the classification annotation.
+
+This is enforced by a custom `#[must_classify]` lint in the crate — any public field
+on `BfldFrame` without a classification attribute produces a compile warning that
+becomes a CI error.
+
+---
+
+## 6. Auditability: Verifying That Raw BFI Never Left the Network
+
+An operator who wants to verify that no raw BFI or identity data has been transmitted
+from their BFLD node can use the following procedure:
+
+### 6.1 Network-level audit (tcpdump)
+
+```bash
+# On the node or a port-mirrored switch:
+tcpdump -i eth0 -w bfld_audit.pcap port 1883 or port 8883
+
+# After capture, search for the BFI frame magic bytes in the PCAP:
+# Magic 0xBF1D_0001 in big-endian is bytes BF 1D 00 01
+# If these bytes appear in the MQTT payload, raw BFI may be present.
+# They should NOT appear — BFLD strips the angle matrix at privacy_class >= 2.
+strings bfld_audit.pcap | grep -v "presence\|motion\|person_count" | wc -l
+# Expected: only presence/motion/person_count keys in the MQTT payloads.
+```
+
+### 6.2 Node self-check command
+
+```bash
+# RuView CLI (planned for P3):
+wifi-densepose bfld audit --duration 60s
+# Output: "60 frames processed. 0 frames with raw_bfi in payload.
+#          0 frames with identity_embedding in payload.
+#          privacy_class distribution: {2: 57, 3: 3}"
+```
+
+### 6.3 CI deterministic hash check
+
+```bash
+python python/wifi_densepose/verify_bfld.py
+# Must print: VERDICT: PASS
+# If a modified binary is exfiltrating raw BFI as part of the payload,
+# the output hash will differ from the committed expected hash.
+```

docs/research/BFLD/05-automation-integration.md

@@ -0,0 +1,239 @@
+# BFLD Automation & Ecosystem Integration
+
+## 1. Home Assistant Integration
+
+### 1.1 Entities Exposed by BFLD
+
+BFLD extends the sensing-server's existing HA entity set (ADR-115, 21 entities) with
+the following new entities:
+
+| Entity | Type | HA Platform | privacy_class | Default |
+|--------|------|-------------|--------------|---------|
+| `binary_sensor.bfld_presence` | Boolean | binary_sensor | 2 — anonymous | ON |
+| `sensor.bfld_motion` | Float 0..1 | sensor | 2 — anonymous | ON |
+| `sensor.bfld_person_count` | Integer | sensor | 1 — derived | ON |
+| `sensor.bfld_confidence` | Float 0..1 | sensor | 2 — anonymous | ON |
+| `sensor.bfld_identity_risk` | Float 0..1 | sensor (diagnostic) | 1 — derived | OFF |
+| `sensor.bfld_zone_activity` | String | sensor | 2 — anonymous | ON |
+
+`bfld_identity_risk` is classified as a diagnostic entity in the HA model — it is
+hidden by default in the UI and not included in recorder history unless explicitly
+enabled. This matches the operator opt-in posture for class-1 fields.
+
+### 1.2 MQTT Discovery Payload (example for presence sensor)
+
+```json
+{
+  "name": "BFLD Presence",
+  "unique_id": "bfld_presence_<node_id_hash>",
+  "state_topic": "ruview/<node_id>/bfld/presence/state",
+  "device_class": "occupancy",
+  "payload_on": "true",
+  "payload_off": "false",
+  "device": {
+    "identifiers": ["ruview_<node_id_hash>"],
+    "name": "RuView BFLD Node",
+    "model": "wifi-densepose-bfld",
+    "manufacturer": "RuView"
+  }
+}
+```
+
+Topic: `homeassistant/binary_sensor/bfld_<node_id_hash>/presence/config`
+
+### 1.3 HA Blueprints
+
+**Blueprint 1: Presence-driven lighting**
+
+Trigger: `binary_sensor.bfld_presence` changes to `on`.
+Condition: Time is between sunset and sunrise.
+Action: Turn on `light.living_room` at 40% brightness.
+Exit: `binary_sensor.bfld_presence` off for 5 minutes → turn off light.
+
+This blueprint uses only class-2 (anonymous) data. No identity information is required.
+
+**Blueprint 2: Motion-aware HVAC**
+
+Trigger: `sensor.bfld_motion` rises above 0.3 (active movement threshold).
+Action: Set `climate.living_room` to comfort mode.
+Trigger: `sensor.bfld_motion` stays below 0.1 for 20 minutes (room settled).
+Action: Set `climate.living_room` to eco mode.
+
+**Blueprint 3: Identity-risk anomaly notification**
+
+Trigger: `sensor.bfld_identity_risk` rises above 0.8 (high-risk threshold).
+Condition: privacy mode is NOT enabled.
+Action: Notify user via HA mobile app: "BFLD: High identity-leakage risk detected.
+Consider enabling privacy mode."
+
+This blueprint is the only one that touches a class-1 field. The notification is
+a privacy-protective action — it alerts the operator that the sensing environment
+has changed (e.g., new router firmware, new AP nearby, changed room geometry) in
+a way that makes the RF channel more identity-discriminative.
+
+---
+
+## 2. Matter Exposure
+
+Matter clusters expose the absolute minimum set of BFLD outputs. The constraint is
+intentional: Matter fabrics can include cloud bridges, and identity-correlated data
+must never reach cloud endpoints.
+
+### 2.1 Permitted Matter Clusters
+
+| Matter Cluster | Cluster ID | BFLD Source | Notes |
+|----------------|-----------|-------------|-------|
+| Occupancy Sensing | 0x0406 | `presence` | `OccupancySensing` attribute `Occupancy` bit 0 |
+| Motion Detection | 0x040E (proposed) | `motion` | Published as motion event cluster |
+| People Count | — (vendor extension) | `person_count` | No standard cluster yet; use vendor attribute |
+
+### 2.2 Rejected Matter Fields
+
+The following BFLD fields MUST NOT be exposed via Matter regardless of operator
+configuration:
+
+- `identity_risk_score`
+- `rf_signature_hash`
+- `raw_bfi`
+- `identity_embedding`
+- `compressed_angle_matrix`
+- Any future field classified at privacy_class < 2
+
+This rejection is enforced in the `cog-ha-matter` crate (`v2/crates/cog-ha-matter/`),
+which filters `BfldFrame` events before populating Matter attribute reports.
+
+### 2.3 Matter Endpoint Configuration
+
+```
+Endpoint 1: BFLD Occupancy
+  - Cluster: Occupancy Sensing (0x0406)
+    - Attribute 0x0000 Occupancy: 0x01 (bitmask, bit 0 = presence)
+    - Attribute 0x0001 OccupancySensorType: 0x03 (Other = WiFi RF)
+  - Cluster: Basic Information (0x0028)
+    - NodeLabel: "BFLD-<node_id_short>"
+    - ProductName: "wifi-densepose-bfld"
+```
+
+---
+
+## 3. MQTT Topic Structure and ACL Recommendations
+
+### 3.1 Topic Tree
+
+```
+ruview/<node_id>/bfld/
+    presence/state          # "true" | "false" — class 2
+    motion/state            # "0.42" — class 2
+    person_count/state      # "1" — class 1
+    identity_risk/state     # "0.71" — class 1, disabled by default
+    raw/state               # disabled by default, class 0 metadata only
+    zone_activity/state     # "living_room" — class 2
+    confidence/state        # "0.88" — class 2
+    events/bfld_update      # Full JSON event payload — class 2 fields only by default
+```
+
+### 3.2 Mosquitto ACL Recommendations
+
+```
+# /etc/mosquitto/acl.conf (example)
+
+# BFLD node publishes to its own subtree
+user bfld_node_<node_id>
+topic write ruview/<node_id>/bfld/#
+
+# Home Assistant reads presence, motion, count, zone, confidence
+user homeassistant
+topic read ruview/+/bfld/presence/state
+topic read ruview/+/bfld/motion/state
+topic read ruview/+/bfld/person_count/state
+topic read ruview/+/bfld/zone_activity/state
+topic read ruview/+/bfld/confidence/state
+topic read ruview/+/bfld/events/bfld_update
+
+# HA diagnostic access (operator opt-in required to add this rule):
+# topic read ruview/+/bfld/identity_risk/state
+
+# DENY all wildcard subscriptions for anonymous clients:
+# (mosquitto default: anonymous clients get no access)
+
+# DENY raw topic for all non-admin users:
+# raw/state is never written by default; no read ACL needed
+```
+
+### 3.3 TLS Configuration
+
+BFLD should use TLS for all MQTT connections. The BFLD node connects as a TLS client;
+the broker must present a certificate matching the expected CA. The sensing-server
+already supports mTLS (ADR-115). BFLD inherits this configuration.
+
+---
+
+## 4. Node-RED and OpenHAB Compatibility
+
+BFLD publishes standard MQTT payloads with consistent topic structure. No Node-RED
+or OpenHAB plugin is required; standard MQTT input/output nodes work directly.
+
+**Node-RED example flow**:
+
+```json
+[
+  {"id": "bfld-in", "type": "mqtt in",
+   "topic": "ruview/+/bfld/presence/state", "qos": "1"},
+  {"id": "filter", "type": "switch",
+   "property": "payload", "rules": [{"t": "eq", "v": "true"}]},
+  {"id": "notify", "type": "http request",
+   "url": "http://ha/api/events/bfld_presence_on"}
+]
+```
+
+**OpenHAB MQTT binding** (items file):
+
+```
+Switch BfldPresence "BFLD Presence" {mqtt="<[broker:ruview/node1/bfld/presence/state:state:default]"}
+Number BfldMotion  "BFLD Motion"   {mqtt="<[broker:ruview/node1/bfld/motion/state:state:default]"}
+```
+
+---
+
+## 5. cognitum-v0 Federation
+
+The cognitum-v0 appliance (Pi 5, running ruview-mcp-brain on port 9876,
+cognitum-rvf-agent on port 9004, ruvector-hailo-worker on port 50051 — see
+CLAUDE.local.md) is the fleet coordinator for multi-room correlation.
+
+BFLD events from individual nodes flow to cognitum-v0 via the federation path.
+The critical constraint: **identity fields are stripped at the node boundary before
+federation**. The stripping happens in the local BFLD emitter (`mqtt.rs`), not in
+cognitum-v0. By the time a BFLD event reaches the broker that cognitum-v0 subscribes to,
+it contains only class-2 (anonymous) or class-3 (restricted) fields.
+
+### 5.1 Federation Topics
+
+```
+# Node-local (not federated):
+ruview/<node_id>/bfld/identity_risk/state
+ruview/<node_id>/bfld/raw/state
+
+# Federated (forwarded to cognitum-v0 broker):
+ruview/<node_id>/bfld/presence/state
+ruview/<node_id>/bfld/motion/state
+ruview/<node_id>/bfld/person_count/state
+ruview/<node_id>/bfld/events/bfld_update
+```
+
+### 5.2 cognitum-rvf-agent Role
+
+The `cognitum-rvf-agent` (port 9004) handles cross-node RVF (RuView Frame) container
+events. For BFLD, it receives federated presence/motion/count events and can correlate
+them for multi-room occupancy (e.g., "person moved from living room node to kitchen
+node"). It does not receive or need identity information to perform this correlation —
+it uses temporal and spatial proximity, not identity.
+
+### 5.3 Hailo Inference (Future)
+
+The `ruvector-hailo-worker` (port 50051) on cognitum-v0 runs vector similarity on the
+Hailo-8 AI accelerator. A future extension could offload BFLD's identity_risk_score
+computation to the Hailo worker, keeping the identity embedding local to cognitum-v0
+while giving individual nodes the benefit of a larger enrollment pool for risk
+calibration. This is explicitly out of scope for the current BFLD spec — it is noted
+here as an integration-compatible extension point.

docs/research/BFLD/06-implementation-plan.md

@@ -0,0 +1,253 @@
+# BFLD Implementation Plan
+
+## 1. New Crate: wifi-densepose-bfld
+
+Location: `v2/crates/wifi-densepose-bfld/`
+
+This crate slots between `wifi-densepose-signal` (BFI normalization, temporal windowing)
+and `wifi-densepose-sensing-server` (MQTT/HA integration). It does not depend on the
+training pipeline (`wifi-densepose-train`) or the neural-network inference crate
+(`wifi-densepose-nn`) in the default build — feature flags activate those paths.
+
+### 1.1 Module Layout
+
+```
+v2/crates/wifi-densepose-bfld/
+    Cargo.toml
+    src/
+        lib.rs              # Public API: BfldPipeline, BfldFrame, BfldEvent
+        frame.rs            # BfldFrame struct, serialization, CRC32, magic bytes
+        extractor.rs        # BFI packet capture interface, Phi/Psi parsing,
+                            #   802.11ac/ax CBFR format decoder
+        features.rs         # Feature computation: mean_angle_delta,
+                            #   subcarrier_variance, temporal_entropy,
+                            #   doppler_proxy, path_stability,
+                            #   cross_antenna_correlation, burst_motion_score,
+                            #   stationarity_score, identity_separability_score
+        identity_risk.rs    # identity_risk_score formula, EmbeddingRingBuf,
+                            #   in-RAM-only lifecycle enforcement
+        privacy_gate.rs     # privacy_class assignment, field masking,
+                            #   #[must_classify] lint check
+        emitter.rs          # BfldEvent construction, JSON serialization
+        mqtt.rs             # MQTT topic publishing, ACL, per-class topic routing
+    tests/
+        frame_roundtrip.rs  # BfldFrame serialization + CRC32 determinism
+        privacy_gate.rs     # Per-class field suppression assertions
+        hash_rotation.rs    # Cross-site isolation + daily rotation proofs
+        identity_risk.rs    # Risk score bounded [0,1], local-only embedding
+        acceptance.rs       # All 7 acceptance criteria as named tests
+    benches/
+        pipeline_throughput.rs  # Frame processing at 40 Hz
+```
+
+### 1.2 Public API Sketch
+
+```rust
+// lib.rs — primary entry points
+
+pub struct BfldPipeline {
+    config: BfldConfig,
+    extractor: BfiExtractor,
+    feature_engine: FeatureEngine,
+    identity_risk: IdentityRiskEngine,
+    privacy_gate: PrivacyGate,
+    emitter: BfldEmitter,
+}
+
+impl BfldPipeline {
+    pub fn new(config: BfldConfig) -> Result<Self, BfldError>;
+    pub fn process_frame(&mut self, raw: RawBfiCapture) -> Option<BfldEvent>;
+    pub fn current_privacy_class(&self) -> PrivacyClass;
+    pub fn enable_privacy_mode(&mut self);  // forces class 3
+}
+
+pub struct BfldEvent {
+    pub timestamp_ns: u64,
+    pub presence: bool,
+    pub motion: f32,                    // 0.0..1.0
+    pub person_count: u8,
+    pub identity_risk_score: Option<f32>, // None if privacy_class >= 2
+    pub rf_signature_hash: Option<[u8; 32]>, // None if privacy_class >= 2
+    pub zone_id: Option<ZoneId>,
+    pub confidence: f32,
+    pub privacy_class: PrivacyClass,
+}
+
+#[repr(u8)]
+pub enum PrivacyClass {
+    Raw       = 0,
+    Derived   = 1,
+    Anonymous = 2,
+    Restricted = 3,
+}
+```
+
+---
+
+## 2. Reuse Map: Existing Crates and Modules
+
+### 2.1 RuvSense Modules (wifi-densepose-signal)
+
+Path: `v2/crates/wifi-densepose-signal/src/ruvsense/`
+
+| Module | Used by BFLD | Purpose |
+|--------|-------------|---------|
+| `coherence_gate.rs` | `identity_risk.rs` | Accept/reject frame based on coherence score; gates embeddings fed into risk calculation |
+| `multistatic.rs` | `features.rs` | Attention-weighted fusion for cross_perspective_consistency component of risk score |
+| `cross_room.rs` | `privacy_gate.rs` | Environment fingerprinting — confirms that the site_salt corresponds to the current room geometry |
+| `longitudinal.rs` | `identity_risk.rs` | Welford stats for temporal_stability component |
+| `adversarial.rs` | `extractor.rs` | Physically-impossible signal detection — flags frames that may be from a compromised AP (A5 threat) |
+
+Not used by BFLD: `pose_tracker.rs`, `intention.rs`, `gesture.rs`, `tomography.rs`,
+`field_model.rs` — these operate above the identity-risk layer.
+
+### 2.2 RuVector v2.0.4 Crates
+
+| Crate | BFLD Usage | Rationale |
+|-------|-----------|-----------|
+| `ruvector-attention` | `identity_risk.rs` | Spatial attention over subcarrier dimension for embedding computation |
+| `ruvector-mincut` | `features.rs` | Person separation score as input to person_count feature |
+| `ruvector-temporal-tensor` | `extractor.rs` | Temporal windowing + compression of BFI angle sequences |
+
+Not used: `ruvector-attn-mincut`, `ruvector-solver` — spectrogram and sparse
+interpolation are not needed in the BFI pipeline.
+
+### 2.3 Cross-Viewpoint Fusion (wifi-densepose-ruvector)
+
+Path: `v2/crates/wifi-densepose-ruvector/src/viewpoint/`
+
+| Module | BFLD Usage |
+|--------|-----------|
+| `coherence.rs` | Cross-viewpoint phase coherence for cross_perspective_consistency risk component |
+| `geometry.rs` | Fisher Information / Cramer-Rao bounds for confidence estimation |
+| `attention.rs` | GeometricBias-weighted attention for multi-AP BFI fusion |
+| `fusion.rs` | MultistaticArray aggregate root — BFLD subscribes to domain events here |
+
+---
+
+## 3. ESP32 Firmware Additions
+
+### 3.1 ESP32-S3 BFI Capability Assessment
+
+The ESP32-S3's WiFi driver (`csi_collector.c` in `firmware/esp32-csi-node/main/`)
+uses `esp_wifi_csi_set_config()` and the `wifi_csi_cb_t` callback. This produces
+Espressif HT20 CSI in a vendor-specific format — amplitude + phase per subcarrier,
+not the VHT/HE Compressed Beamforming frames (CBFR) that contain Phi/Psi angles.
+
+The ESP32-S3 does NOT have a public API to generate or capture CBFR frames. Espressif's
+802.11 implementation does receive and process CBFR frames internally (for beamforming
+its own transmissions), but these are not exposed via the CSI callback.
+
+**Consequence**: BFI capture for BFLD requires host-side sniffing, not ESP32 firmware
+modification.
+
+### 3.2 Host-Side BFI Capture Path
+
+Recommended capture hardware: Raspberry Pi 5 with BCM43456 chip running Nexmon CSI
+patch. This is already present in the fleet as `cognitum-v0` (Pi 5, Tailscale IP
+100.77.59.83 per CLAUDE.local.md).
+
+Capture path:
+1. Nexmon monitor mode captures all 802.11 frames on the target channel.
+2. A filter pass extracts CBFR frames (frame type = Action, subtype = VHT/HE CBFR).
+3. The rvcsi adapter (`vendor/rvcsi/`) already handles Nexmon PCap format; add a
+   BFI extractor alongside the existing CSI extractor.
+4. Frames are forwarded to the BFLD pipeline via the existing UDP stream path
+   (`stream_sender.c` / sensing-server).
+
+### 3.3 Firmware Changes Required (Minimal)
+
+The only firmware change needed in `firmware/esp32-csi-node/main/` is to the
+`stream_sender.c` protocol: add a packet type byte to the stream header to distinguish
+CSI frames from BFI frames. The BFI frames originate on the Pi-side host, not the
+ESP32; the ESP32 stream is unchanged.
+
+```c
+// stream_sender.h — add packet type
+#define STREAM_PKT_TYPE_CSI  0x01
+#define STREAM_PKT_TYPE_BFI  0x02  // new: BFI frames from host capture
+```
+
+---
+
+## 4. Test Plan: 7 Acceptance Criteria Mapped to Rust Tests
+
+| AC | Criterion | Test in `acceptance.rs` |
+|----|-----------|------------------------|
+| AC1 | Commodity WiFi 5/6 capture (80/160 MHz, 2×2 MIMO minimum) | `ac1_commodity_wifi_capture`: assert BfiExtractor parses 80 MHz VHT CBFR sample fixture |
+| AC2 | Presence detection latency ≤ 1s from first non-empty BFI frame | `ac2_presence_latency`: replay 10-frame window, assert first `BfldEvent` with `presence=true` within 1,000 ms wall time |
+| AC3 | Motion score published at ≥ 1 Hz on `motion/state` topic | `ac3_motion_hz`: mock MQTT sink, run at 5 Hz input, assert ≥ 1 motion event per second |
+| AC4 | Raw BFI bytes never appear in serialized output | `ac4_raw_bfi_absent`: fuzz 1,000 random BfiCaptures, assert no bfi_matrix bytes in serialized BfldFrame for any privacy_class |
+| AC5 | Privacy-mode suppresses all identity-derived fields | `ac5_privacy_mode`: enable privacy_mode, assert BfldEvent fields identity_risk_score and rf_signature_hash are None |
+| AC6 | Deterministic frame hash for identical inputs | `ac6_deterministic_hash`: run same BfiCapture 100 times, assert all output hashes identical |
+| AC7 | CSI-optional fusion: pipeline runs without csi_matrix | `ac7_csi_optional`: run BfldPipeline with None csi_matrix, assert no panic and presence event produced |
+
+Additionally, `tests/hash_rotation.rs` must include:
+- `cross_site_isolation`: two BfldPipelines with different site_salts, identical inputs → hashes must differ
+- `daily_rotation`: same salt, frames 1 second before/after midnight → hashes must differ
+
+---
+
+## 5. Phased Rollout
+
+### P1 — Frame Format + Extractor Stub (2 weeks)
+
+Deliverables:
+- `frame.rs`: `BfldFrame` struct, serialization, CRC32, magic, version
+- `extractor.rs`: CBFR parser for 802.11ac VHT + 802.11ax HE formats
+- AC1, AC6 tests passing
+- `Cargo.toml` with workspace integration
+
+Effort: 1 engineer, 2 weeks.
+
+### P2 — Feature Extraction + Identity Risk (3 weeks)
+
+Deliverables:
+- `features.rs`: all 9 named features (mean_angle_delta through identity_separability_score)
+- `identity_risk.rs`: risk formula, EmbeddingRingBuf, coherence gate integration
+- AC4, AC7 tests passing (raw-absent, CSI-optional)
+- Integration with `ruvector-attention` and `ruvector-temporal-tensor`
+
+Effort: 1 engineer, 3 weeks.
+
+### P3 — Privacy Gate + MQTT (2 weeks)
+
+Deliverables:
+- `privacy_gate.rs`: privacy_class assignment, field masking, `#[must_classify]` lint
+- `mqtt.rs`: per-class topic routing, discovery payloads, ACL documentation
+- AC2, AC3, AC5 tests passing (latency, Hz, privacy-mode)
+- Hash rotation: `hash_rotation.rs` tests passing
+- Deterministic proof bundle: `verify_bfld.py` equivalent
+
+Effort: 1 engineer, 2 weeks.
+
+### P4 — Home Assistant Integration (1 week)
+
+Deliverables:
+- MQTT discovery payloads for all 6 entities
+- 3 HA blueprints
+- `sensor.bfld_identity_risk` marked diagnostic + hidden by default
+- Update `wifi-densepose-sensing-server` to include BFLD event routing
+
+Effort: 0.5 engineer, 1 week.
+
+### P5 — Matter Exposure (1 week)
+
+Deliverables:
+- `cog-ha-matter` crate updated to filter BfldFrame → Matter attribute reports
+- OccupancySensing cluster populated from `presence`
+- Rejection list for identity fields enforced at Matter boundary
+
+Effort: 0.5 engineer, 1 week.
+
+### P6 — cognitum Federation (1 week)
+
+Deliverables:
+- Topic routing in `mqtt.rs` for federated vs local topics
+- Documentation for cognitum-rvf-agent BFLD event subscription
+- End-to-end test: Pi 5 (cognitum-v0) receives federated events, identity fields absent
+
+Effort: 0.5 engineer, 1 week.
+
+**Total estimate**: ~10.5 engineer-weeks across 6 phases, approximately 3 calendar months
+with one engineer.

docs/research/BFLD/07-benchmarks-and-evaluation.md

@@ -0,0 +1,196 @@
+# BFLD Benchmarks and Evaluation Strategy
+
+## 1. Datasets
+
+### 1.1 BFId Dataset (Primary)
+
+**Reference**: Todt, Morsbach, Strufe; KIT. ACM CCS 2025.
+https://dl.acm.org/doi/10.1145/3719027.3765062
+https://ps.tm.kit.edu/english/bfid-dataset/index.php
+
+197 individuals. BFI and CSI recorded simultaneously. Multiple sessions, multiple AP
+angles. Available to researchers for non-commercial use on request from KIT.
+
+**Use in BFLD evaluation**: The BFId dataset provides the ground-truth identity labels
+needed to calibrate `identity_risk_score`. Specifically: given BFId's known re-ID
+accuracy as a function of time window, BFLD's identity_risk_score should correlate
+with BFId's success rate. High-risk frames (score > 0.7) should correspond to windows
+where BFId achieves > 80% accuracy; low-risk frames (score < 0.2) should correspond
+to windows where BFId accuracy approaches chance.
+
+### 1.2 Wi-Pose and MM-Fi (Context)
+
+**MM-Fi**: Multi-modal WiFi sensing dataset used by this project (ADR-015). Contains
+synchronized WiFi CSI, mmWave, and camera pose data. Does not contain BFI separately,
+but can be used to validate BFLD's CSI-optional path (AC7).
+
+**Wi-Pose**: Academic benchmark for WiFi pose estimation. CSI only; used for
+person_count and motion accuracy baselines.
+
+### 1.3 Proposed In-House Multi-Site Capture Protocol
+
+**Purpose**: Validate cross-site isolation (Invariant 3) and daily rotation.
+
+**Setup**:
+- Site A: ruvultra (RTX 5080 workstation, Tailscale 100.104.125.72) with USB WiFi
+  adapter in monitor mode.
+- Site B: cognitum-v0 (Pi 5, Tailscale 100.77.59.83) with Nexmon monitor mode.
+- Subject pool: 5–10 volunteers.
+- Protocol: Each subject walks a fixed path at each site on 3 consecutive days.
+  BFI captured simultaneously at both sites using Wi-BFI.
+
+**Analysis**:
+1. Can the BFId classifier re-identify subjects within a site? (Baseline — should
+   confirm BFId's published results.)
+2. Can any classifier re-identify subjects across sites using BFLD's
+   rf_signature_hash? (Should fail — cross-site isolation test.)
+3. Can any classifier re-identify across days using BFLD's rf_signature_hash? (Should
+   fail — daily rotation test.)
+
+---
+
+## 2. Metrics
+
+### 2.1 Presence Detection
+
+| Metric | Definition | Target |
+|--------|-----------|--------|
+| Latency p50 | Time from first non-empty BFI frame to first `presence=true` event | < 500 ms |
+| Latency p95 | | < 1000 ms (AC2) |
+| False positive rate | Presence=true when room is confirmed empty | < 5% |
+| False negative rate | Presence=false when person confirmed present | < 2% |
+
+Measurement method: camera ground-truth (ruvultra webcam via MediaPipe Pose, same
+as ADR-079 collection protocol) for empty/occupied labels.
+
+### 2.2 Motion Score
+
+| Metric | Definition | Target |
+|--------|-----------|--------|
+| MAE vs ground truth | Mean absolute error of motion score vs camera-derived motion magnitude | < 0.1 |
+| Hz at sustained operation | Events published per second on `motion/state` | >= 1 Hz (AC3) |
+| Latency p95 | Time from motion onset (camera) to motion event | < 750 ms |
+
+### 2.3 Person Count
+
+| Metric | Definition | Target |
+|--------|-----------|--------|
+| Count accuracy | Fraction of windows where BFLD person_count == camera count | > 85% for 1–3 persons |
+| Count MAE | |  < 0.5 for counts 1–4 |
+
+Person count is harder than presence. The target is achievable with MinCut separation
+(`ruvector-mincut`) but requires multi-AP coverage for 4+ persons.
+
+### 2.4 Identity Risk Calibration
+
+This is BFLD's novel evaluation dimension — no prior system has explicitly quantified
+this.
+
+**Calibration definition**: Let `r(t)` = BFLD's identity_risk_score at time t.
+Let `acc(t)` = BFId classifier's re-identification accuracy when trained on frames
+around time t. The identity_risk_score is *calibrated* if:
+
+    E[acc(t) | r(t) = v] is monotonically increasing in v
+
+In other words: higher risk scores should correspond to frames where identity inference
+is genuinely easier.
+
+**Evaluation protocol**:
+1. Run BFId classifier in sliding 5-second windows on the BFId dataset.
+2. Record per-window BFId accuracy (using leave-one-out cross-validation).
+3. Run BFLD's identity_risk_score computation on the same windows.
+4. Compute Spearman correlation between risk scores and BFId accuracy.
+5. Target: Spearman rho > 0.5 (positive monotonic correlation).
+
+### 2.5 Privacy-Mode False Positive Rate
+
+When `privacy_mode` is enabled (privacy_class = 3), all identity-correlated fields
+should be suppressed. The false positive rate is the fraction of outbound events
+that inadvertently include an identity-correlated field despite privacy_mode being
+active.
+
+**Target**: 0% (this is a hard correctness requirement, not a statistical target).
+Verified by the AC5 fuzz test in `acceptance.rs`.
+
+---
+
+## 3. Red-Team Protocol
+
+### 3.1 Hash Re-identification Attack
+
+**Question**: Can an attacker re-identify a person across rotated hashes?
+
+**Setup**:
+- Run BFLD pipeline for person X across 3 days.
+- Collect `rf_signature_hash` values for each day: H_1, H_2, H_3.
+- Adversary has access to H_1, H_2, H_3 and knows they are from the same site.
+- Adversary attempts to confirm H_1, H_2, H_3 are from the same person.
+
+**Success condition**: adversary achieves confirmation rate > chance (1/N for N subjects).
+
+**Expected result**: FAIL (by construction of the hash rotation with site_salt).
+Since day_epoch changes daily and site_salt is fixed but unknown to the adversary,
+the hash function is a keyed PRF. The adversary has three random-looking 32-byte
+values with no structural relationship. Success rate should be indistinguishable from
+random guessing.
+
+**Quantitative target**: success rate <= 1/N + 0.05 (within 5% of chance).
+
+### 3.2 Cross-Site Re-identification Attack
+
+**Question**: Can an attacker confirm person X visited both site A and site B?
+
+**Setup**: Same as Section 1.3 in-house protocol. Adversary has BFLD event streams
+from both sites.
+
+**Method**: Attempt to match rf_signature_hash values from site A and site B on the
+same day. Alternatively, train a classifier on BFI features (using the raw angle
+sequences from the captured data) and attempt cross-site re-ID.
+
+**Expected result**: Hash-based matching fails by construction. Classifier-based
+re-ID may succeed if the adversary has raw angle data (which BFLD does not publish)
+but not using BFLD's published output.
+
+**Success condition**: hash-based cross-site match rate <= 1/N + 0.05.
+
+### 3.3 Timing Side-Channel Attack
+
+**Question**: Can an attacker infer a person's schedule by monitoring
+identity_risk_score over time?
+
+**Method**: Record identity_risk_score time series. Correlate with known schedule
+(person X leaves at 8am, returns at 6pm). Compute mutual information between
+schedule and risk score time series.
+
+**Expected result**: Some correlation exists (risk score rises when person enters),
+but the attacker learns "someone is present" — equivalent to the presence sensor —
+not identity. This is acceptable: presence information is already published at
+class 2.
+
+---
+
+## 4. Comparison Baselines
+
+| Baseline | Description | Presence F1 | Motion MAE | Identity leak |
+|----------|-------------|------------|-----------|--------------|
+| Raw CSI pipeline | Existing wifi-densepose pipeline (no BFLD) | ~0.95 (est.) | ~0.08 (est.) | Unquantified — no risk gating |
+| BFI-only (no BFLD) | Wi-BFI + threshold presence | ~0.82 (from LeakyBeam) | N/A | Angle matrices published |
+| BFI+CSI fusion (no BFLD) | Combined pipeline, ungated | ~0.97 (est.) | ~0.06 (est.) | Unquantified |
+| **BFLD (BFI+CSI, class 2)** | Full BFLD with anonymous privacy class | target 0.93 | target 0.10 | 0% (class 2 gate) |
+| BFLD (BFI-only, class 2) | BFLD without CSI input (AC7) | target 0.85 | target 0.12 | 0% (class 2 gate) |
+
+The BFLD privacy-class guarantee reduces the raw sensing accuracy by a small margin
+versus an ungated BFI+CSI pipeline (target F1 0.93 vs estimated 0.97). This is the
+explicit trade-off: identity safety for a modest utility cost.
+
+---
+
+## 5. Continuous Evaluation in CI
+
+Three tests run on every PR that touches the BFLD crate:
+
+1. **Deterministic hash test** (AC6): same input → same output across platforms.
+2. **Privacy-mode field suppression fuzz** (AC5): 1,000 random inputs → no identity
+   fields in class-2 output.
+3. **Latency smoke test** (AC2): 100-frame replay → first presence event < 200 ms
+   (tighter than the 1s AC target, to keep CI fast).

docs/research/BFLD/08-adr-draft.md

@@ -0,0 +1,214 @@
+# ADR-118: BFLD — Beamforming Feedback Layer for Detection
+
+> This file is a draft. When approved, copy to:
+> `docs/adr/ADR-118-bfld-beamforming-feedback-layer-for-detection.md`
+
+| Field | Value |
+|-------|-------|
+| **Status** | Proposed |
+| **Date** | 2026-05-24 |
+| **Deciders** | ruv |
+| **Codename** | **BFLD** — Beamforming Feedback Layer for Detection |
+| **Relates to** | [ADR-024](ADR-024-contrastive-csi-embedding-model.md) (AETHER contrastive embedding), [ADR-027](ADR-027-cross-environment-domain-generalization.md) (MERIDIAN cross-environment), [ADR-028](ADR-028-esp32-capability-audit.md) (capability audit / witness), [ADR-029](ADR-029-ruvsense-multistatic-sensing-mode.md) (RuvSense multistatic), [ADR-030](ADR-030-ruvsense-persistent-field-model.md) (persistent field model), [ADR-031](ADR-031-ruview-sensing-first-rf-mode.md) (sensing-first RF mode), [ADR-032](ADR-032-multistatic-mesh-security-hardening.md) (mesh security hardening), [ADR-095](ADR-095-rvcsi-edge-rf-sensing-platform.md) (rvCSI platform), [ADR-115](ADR-115-home-assistant-integration.md) (HA integration), [ADR-116](ADR-116-cog-ha-matter-seed.md) (Matter seed packaging), [ADR-117](ADR-117-pip-wifi-densepose-modernization.md) (pip modernization) |
+| **Tracking issue** | TBD |
+
+---
+
+## 1. Context
+
+### 1.1 The Plaintext BFI Problem
+
+IEEE 802.11ac and 802.11ax beamforming feedback information (BFI) is exchanged between
+client stations (STA) and access points (AP) in unencrypted management-plane frames.
+The STA compresses the channel response into a matrix of Givens rotation angles (Phi/Psi)
+and transmits them in a VHT/HE Compressed Beamforming Report (CBFR) frame. These frames
+are passively sniffable by any device in WiFi monitor mode without any access to the
+target network.
+
+Two independent 2024–2025 research papers establish the severity of this exposure:
+
+1. **BFId** (Todt, Morsbach, Strufe; KIT; ACM CCS 2025,
+   https://dl.acm.org/doi/10.1145/3719027.3765062): demonstrates re-identification of
+   197 individuals using BFI alone, with >90% accuracy from 5 seconds of capture.
+2. **LeakyBeam** (Xiao et al.; Zhejiang U., NTU, KAIST; NDSS 2025,
+   https://www.ndss-symposium.org/ndss-paper/lend-me-your-beam-privacy-implications-of-plaintext-beamforming-feedback-in-wifi/):
+   demonstrates occupancy detection through walls at 20 m range using BFI, with 82.7%
+   TPR and 96.7% TNR.
+
+Tooling for passive BFI capture is freely available. Wi-BFI
+(https://arxiv.org/abs/2309.04408) is pip-installable and supports 802.11ac/ax,
+SU/MU-MIMO, 20/40/80/160 MHz channels.
+
+### 1.2 Gap in Existing Pipeline
+
+The wifi-densepose sensing pipeline processes CSI via the rvCSI runtime (ADR-095/096)
+and produces presence, pose, vitals, and zone-activity events. No layer explicitly
+measures whether the data being processed is capable of identifying specific individuals.
+The pipeline treats all CSI as equivalent from a privacy standpoint, regardless of
+whether it is operating in a high-separability (identity-leaky) or low-separability
+(anonymous) regime.
+
+This gap becomes a compliance and liability issue as WiFi sensing deployments scale.
+An operator deploying this system in a care facility, hotel, or shared office has no
+instrument to verify that the system is operating anonymously.
+
+### 1.3 The BFI Opportunity
+
+BFI is not only a threat vector — it is a complementary sensing signal. Because BFI
+encodes the channel response as a structured compressed matrix, it carries multipath
+geometry that can augment CSI-based presence and motion detection, particularly in
+scenarios where only one AP is available (fewer antenna pairs than a full MIMO CSI
+capture). The BFLD design treats BFI as an optional input alongside CSI, not as a
+replacement.
+
+---
+
+## 2. Decision
+
+We will create a new crate `wifi-densepose-bfld` (to live in `v2/crates/`) that:
+
+1. **Ingests** raw BFI (Phi/Psi angle matrices from CBFR frames) as input and optionally
+   fuses CSI when available.
+2. **Computes** nine named features and derives an `identity_risk_score` using a
+   separability × temporal_stability × cross_perspective_consistency × sample_confidence
+   formula.
+3. **Gates** all output through a `privacy_class` mechanism that structurally prevents
+   identity-correlated data from being published at privacy classes 2 and 3.
+4. **Emits** `BfldEvent` structs on MQTT topics under `ruview/<node_id>/bfld/` with
+   per-class topic routing.
+5. **Enforces** three invariants structurally (not by policy):
+   - Raw BFI never exits the node.
+   - Identity embedding is in-RAM-only.
+   - Cross-site identity correlation is made cryptographically impossible via per-site
+     keyed BLAKE3 hash rotation with a daily epoch.
+
+The `BfldFrame` wire format carries magic `0xBF1D_0001`, a version byte, hashed AP/STA
+identifiers, a quantization byte, a privacy_class byte, compressed feature payload, and
+a CRC32.
+
+Matter exposure is limited to: OccupancySensing (presence), MotionSensor (motion),
+PeopleCount (person_count). Identity fields are rejected at the Matter boundary in the
+`cog-ha-matter` crate.
+
+---
+
+## 3. Consequences
+
+### Positive
+
+- Operators gain an explicit, auditable measure of privacy compliance at the RF layer —
+  the first such primitive in the wifi-densepose ecosystem.
+- The identity_risk_score doubles as an anomaly signal: unexpected spikes indicate
+  environmental changes (new AP firmware, nearby attacker-grade sniffer, unusual
+  propagation geometry) that warrant investigation.
+- BFI fusion augments presence and motion accuracy in single-AP deployments, partially
+  compensating for lower CSI antenna counts.
+- The crate's deterministic frame hashes enable the ADR-028 witness-bundle pattern to
+  extend to the new sensing surface, preserving the existing audit trail model.
+- Cross-site identity isolation is structural, not policy-dependent. This is a stronger
+  guarantee than access-control rules.
+
+### Negative
+
+- BFI capture on ESP32-S3 hardware is not directly possible via the Espressif WiFi API.
+  The full BFLD pipeline requires a Pi 5 / Nexmon host-side sniffer (cognitum-v0 is
+  available for this purpose, but it adds a fleet dependency for the BFI path).
+- The identity_risk_score calibration (correlation with actual re-ID success rate)
+  requires the BFId dataset, which requires non-commercial research agreement with KIT.
+- ~10.5 engineer-weeks of implementation effort.
+
+### Neutral
+
+- BFLD does not prevent passive BFI capture by an external attacker (A1 / LeakyBeam
+  threat). It only ensures the node's own output is non-identifying. Operators should
+  be informed of this distinction.
+- The daily hash rotation means that occupant-counting analytics that span multiple
+  days cannot correlate individual signatures across the day boundary. This is a privacy
+  benefit that some analytics use-cases may find inconvenient.
+
+---
+
+## 4. Alternatives Considered
+
+### Alt 1: Skip BFI entirely, CSI-only pipeline
+
+The rvCSI pipeline (ADR-095/096) already handles CSI without BFI. This alternative
+requires no new crate and no change to the ESP32 firmware.
+
+**Rejected because**: (a) it leaves the identity-leakage detection gap open for the
+existing CSI pipeline, and (b) as BFI capture tooling becomes more widespread (Wi-BFI,
+PicoScenes), the absence of a privacy layer becomes more conspicuous for operators.
+
+### Alt 2: Publish identity_risk_score publicly (default-on)
+
+Treat the risk score as a diagnostic metric that operators and the public can observe.
+
+**Rejected because**: the risk score is itself a privacy-sensitive signal (it reveals
+when a specific person is present via timing correlation). The default should be
+opt-in, with the operator explicitly acknowledging the trade-off.
+
+### Alt 3: Use raw BFI in cloud ML training
+
+Send raw BFI angle matrices to a cloud training service to improve model quality.
+
+**Rejected because**: this violates Invariant 1. Cloud training on raw BFI would
+create an off-node store of angle matrices that could be reconstructed into identity
+profiles. The on-device-only constraint is not negotiable.
+
+### Alt 4: Differential privacy noise injection on BFI before any processing
+
+Add calibrated Laplace/Gaussian noise to the angle matrices at ingress to provide
+epsilon-differential privacy on all downstream computations.
+
+**Rejected for this ADR** (noted as future extension): DP noise calibration requires
+sensitivity analysis that is not yet complete, and the interaction between DP noise
+and the identity_risk_score formula requires separate validation. The current design
+achieves privacy through structural impossibility (local-only, hash rotation) rather
+than noise injection.
+
+---
+
+## 5. Acceptance Criteria
+
+- [ ] **AC1**: The extractor parses BFI from commodity WiFi 5 (802.11ac) and WiFi 6
+  (802.11ax) captures, supporting 20/40/80/160 MHz channel bandwidth and 2×2 through
+  4×4 MIMO configurations.
+- [ ] **AC2**: Presence detection latency is ≤ 1s p95 from the first non-empty BFI
+  frame in a new occupancy event.
+- [ ] **AC3**: Motion score is published at ≥ 1 Hz on the `ruview/<node_id>/bfld/motion/state`
+  MQTT topic during sustained occupancy.
+- [ ] **AC4**: Raw BFI bytes (Phi/Psi angle matrices) are never present in any
+  serialized `BfldFrame` payload at any `privacy_class` value.
+- [ ] **AC5**: When `privacy_mode` is enabled, all identity-derived fields
+  (`identity_risk_score`, `rf_signature_hash`, `identity_embedding`) are absent from
+  all outbound events.
+- [ ] **AC6**: Given identical `BfiCapture` inputs, the `BfldFrame` serialization
+  produces bit-identical output (deterministic hash) across runs and across platforms.
+- [ ] **AC7**: The pipeline produces valid `BfldEvent` outputs when `csi_matrix` is
+  absent (BFI-only mode), without panic or degraded presence/motion reporting beyond
+  the documented accuracy bounds.
+
+---
+
+## 6. Related ADRs
+
+- **ADR-024**: AETHER contrastive CSI embedding — BFLD reuses the AETHER embedding
+  infrastructure for identity_risk computation.
+- **ADR-027**: MERIDIAN cross-environment — BFLD's cross-site isolation instantiates
+  the "no cross-site correlation" assumption that MERIDIAN requires.
+- **ADR-028**: Witness verification — BFLD extends the deterministic proof pattern.
+- **ADR-029**: RuvSense multistatic — BFLD uses `multistatic.rs` for
+  cross_perspective_consistency.
+- **ADR-030**: Persistent field model — BFLD uses `cross_room.rs` for
+  environment fingerprinting in the hash rotation.
+- **ADR-031**: Sensing-first RF mode — BFLD is a new sensing primitive alongside
+  the CSI-based sensing.
+- **ADR-032**: Mesh security hardening — BFLD's threat model is a superset.
+- **ADR-095/096**: rvCSI platform — BFLD shares the BFI capture path with rvCSI's
+  Nexmon adapter.
+- **ADR-115**: HA integration — BFLD extends the 21-entity HA surface with 6 new
+  entities.
+- **ADR-116**: Matter seed packaging — BFLD's Matter boundary filter is implemented
+  in `cog-ha-matter`.
+- **ADR-117**: pip modernization — BFLD's Python bindings (PyO3) will follow the
+  pattern established in ADR-117.

docs/research/BFLD/09-github-issue.md

@@ -0,0 +1,111 @@
+# GitHub Issue Draft
+
+**Title**: feat: BFLD — Beamforming Feedback Layer for Detection (privacy-gated WiFi sensing)
+
+**Labels**: `enhancement`, `privacy`, `security`, `area/signal`, `area/firmware`
+
+**Milestone**: (TBD — suggest: v0.8.0)
+
+---
+
+## Summary
+
+Add a new crate `wifi-densepose-bfld` that turns raw 802.11 Beamforming Feedback
+Information (BFI) into bounded, privacy-gated sensing outputs. BFLD detects when RF
+data crosses from "ambient sensing" into "identity record" and structurally prevents
+identity-correlated data from leaving the node.
+
+This is the safety layer that was missing from the CSI pipeline. As passive BFI sniffing
+tools (Wi-BFI, PicoScenes) become widely available and academic attacks (BFId at ACM CCS
+2025, LeakyBeam at NDSS 2025) demonstrate >90% re-identification from commodity WiFi,
+the wifi-densepose ecosystem needs an explicit privacy layer before scaling deployment.
+
+## Motivation
+
+1. **BFI is plaintext and passively sniffable.** IEEE 802.11ac/ax CBFR frames are
+   transmitted before WPA2/WPA3 encryption is applied. Any nearby device in monitor mode
+   can capture them (NDSS 2025: https://www.ndss-symposium.org/ndss-paper/lend-me-your-beam-privacy-implications-of-plaintext-beamforming-feedback-in-wifi/).
+
+2. **BFI enables re-identification.** The KIT BFId paper (ACM CCS 2025:
+   https://dl.acm.org/doi/10.1145/3719027.3765062) demonstrates >90% identity
+   recognition from 5 seconds of BFI, from a dataset of 197 individuals, using only
+   the Phi/Psi Givens rotation angles.
+
+3. **The existing pipeline has no identity-leakage measurement.** The rvCSI pipeline
+   produces presence/motion/pose events without any indication of whether those outputs
+   were derived from identity-discriminative data. An operator deploying in a care
+   facility or shared office has no way to verify the system is behaving anonymously.
+
+4. **WiFi 7 will make this worse.** 802.11be (Wi-Fi 7) multi-link operation increases
+   sounding frequency 3–5×. The attack surface is not static.
+
+## Proposed Solution
+
+New crate at `v2/crates/wifi-densepose-bfld/` with the following pipeline:
+
+```
+BFI capture (CBFR frames, Pi 5 / Nexmon monitor mode)
+    → BFI extractor (Phi/Psi parser, 802.11ac/ax)
+    → Normalization + temporal windowing
+    → Feature extraction (9 named features)
+    → Identity risk engine (in-RAM embeddings, coherence gate)
+    → Privacy gate (privacy_class byte, field masking)
+    → MQTT emitter (per-class topic routing)
+```
+
+Three structural invariants (not configurable, not policy):
+1. Raw BFI never leaves the node.
+2. Identity embedding is in-RAM-only (VecDeque, never persisted).
+3. Cross-site identity matching is cryptographically impossible via per-site BLAKE3
+   keyed hash with daily rotation.
+
+Output events published on `ruview/<node_id>/bfld/{presence,motion,person_count,...}/state`.
+
+Matter and HA expose only: presence, motion, person_count. Identity fields are rejected
+at both boundaries.
+
+## Acceptance Criteria
+
+- [ ] **AC1**: Parser handles 802.11ac VHT and 802.11ax HE CBFR frames at 20/40/80/160 MHz,
+  2×2 through 4×4 MIMO.
+- [ ] **AC2**: Presence detection latency ≤ 1s p95 from first non-empty BFI frame in
+  a new occupancy event.
+- [ ] **AC3**: Motion score published at ≥ 1 Hz on `ruview/<node_id>/bfld/motion/state`
+  during sustained occupancy.
+- [ ] **AC4**: Raw BFI bytes (Phi/Psi angle matrices) are never present in any
+  serialized output at any `privacy_class` value.
+- [ ] **AC5**: Privacy mode suppresses all identity-derived fields (`identity_risk_score`,
+  `rf_signature_hash`, `identity_embedding`) from all outbound events.
+- [ ] **AC6**: Identical `BfiCapture` input → bit-identical `BfldFrame` output
+  (deterministic, cross-platform).
+- [ ] **AC7**: Pipeline produces valid `BfldEvent` with `csi_matrix = None` (BFI-only
+  mode), without panic or significant accuracy degradation.
+
+## References
+
+- BFId paper: https://dl.acm.org/doi/10.1145/3719027.3765062
+- KIT BFId dataset: https://ps.tm.kit.edu/english/bfid-dataset/index.php
+- LeakyBeam (NDSS 2025): https://www.ndss-symposium.org/ndss-paper/lend-me-your-beam-privacy-implications-of-plaintext-beamforming-feedback-in-wifi/
+- Wi-BFI tool: https://arxiv.org/abs/2309.04408
+- Protecting activity signatures in CSI feedback: https://arxiv.org/pdf/2512.18529
+- Research bundle: `docs/research/BFLD/` (this repo)
+- Draft ADR: `docs/research/BFLD/08-adr-draft.md` → ADR-118
+
+## Out of Scope
+
+- Preventing passive BFI capture by external attackers (hardware-level problem, not
+  software).
+- Differential privacy noise injection (noted as future extension in ADR-118).
+- Federated identity learning (local-only is sufficient for the current use case).
+- BFI capture directly from ESP32-S3 firmware (Espressif API does not expose CBFR;
+  host-side Pi 5 / Nexmon capture is the implementation path).
+- WiFi 7 / 802.11be multi-link BFI (frame format versioning accommodates it; not
+  in scope for v1 implementation).
+
+## Related Issues / PRs
+
+- ADR-028 witness bundle (ref: this repo's `docs/WITNESS-LOG-028.md`)
+- ADR-115 HA integration (21 entities — BFLD adds 6 more)
+- ADR-116 Matter seed packaging (`cog-ha-matter` crate needs Matter boundary update)
+- ADR-117 pip modernization (PyO3 pattern reused for BFLD Python bindings)
+- rvCSI platform (ADR-095/096) — Nexmon adapter shared with BFLD BFI capture path

docs/research/BFLD/10-gist.md

@@ -0,0 +1,136 @@
+# BFLD: The Privacy Layer Your WiFi Sensing Stack Has Been Missing
+
+Your WiFi router is broadcasting your identity in plaintext. Here is the layer that
+catches it.
+
+---
+
+## The Problem
+
+Every time your phone or laptop connects to a WiFi 5 or WiFi 6 router, it periodically
+transmits a Beamforming Feedback Report (CBFR frame). This frame contains the compressed
+channel matrix the router needs to aim its antennas at your device. The compression uses
+Givens rotations — a pair of angles (Phi and Psi) per active subcarrier — that encode
+the spatial geometry of the wireless channel around your body.
+
+Here is the catch: these frames are transmitted before WPA2/WPA3 encryption is applied.
+They are plaintext management frames, passively readable by any WiFi adapter in monitor
+mode within roughly 20 meters.
+
+Two papers published in 2024–2025 confirm the threat is real:
+
+- **BFId** (KIT, ACM CCS 2025): re-identifies 197 people from beamforming feedback alone,
+  >90% accuracy from just 5 seconds of capture. Tools needed: a WiFi adapter, a pip
+  install, and no access to the target network.
+  (https://dl.acm.org/doi/10.1145/3719027.3765062)
+
+- **LeakyBeam** (Zhejiang U. / NTU / KAIST, NDSS 2025): detects occupancy through walls
+  at 20 m range using beamforming feedback with 82.7% accuracy.
+  (https://www.ndss-symposium.org/ndss-paper/lend-me-your-beam-privacy-implications-of-plaintext-beamforming-feedback-in-wifi/)
+
+WiFi sensing systems — including this project — process these same signals to detect
+presence, count people, and track motion. Without a privacy layer, there is no way to
+know whether the sensing output is derived from anonymizable motion data or from
+identity-discriminative data.
+
+---
+
+## What BFLD Does
+
+BFLD (Beamforming Feedback Layer for Detection) is a new Rust crate in the
+wifi-densepose workspace that adds one thing: an explicit, continuous measurement of
+whether the beamforming data currently being processed is capable of identifying
+individuals.
+
+It outputs a small, structured event on every sensing cycle:
+
+```json
+{
+  "timestamp_ns": 1748092800000000000,
+  "presence": true,
+  "motion": 0.42,
+  "person_count": 1,
+  "identity_risk_score": 0.71,
+  "rf_signature_hash": "a3f2c1...e9b4",
+  "zone_id": "living_room",
+  "confidence": 0.88,
+  "privacy_class": 1
+}
+```
+
+High `identity_risk_score` (approaching 1.0) means the current sensing environment is
+producing data from which an attacker could re-identify individuals. Low score means
+the data is effectively anonymous.
+
+The score is computed from four components: how separable the current RF embedding is
+from a population distribution, how stable that separability is over time, how
+consistent it is across multiple sensor viewpoints, and how confident the current sample
+is. Multiply them together, clamp to [0, 1].
+
+---
+
+## Three Invariants That Cannot Be Turned Off
+
+BFLD enforces three properties structurally — not as settings, not as policies:
+
+**1. Raw BFI never leaves the node.** The Phi/Psi angle matrices are consumed locally
+and dropped after feature extraction. They are not in the wire format. They are not in
+the MQTT payload. There is no code path to serialize them outbound.
+
+**2. Identity embeddings are RAM-only.** The vector embedding used to compute the risk
+score lives in a fixed-size ring buffer (default: 10 minutes). It is never written to
+disk. When the node restarts, the buffer is gone.
+
+**3. Cross-site re-identification is cryptographically impossible.** The
+`rf_signature_hash` is computed with a per-site secret key (generated at first boot,
+stored in local NVS, never transmitted) and a per-day epoch. Two nodes at two
+different sites, even receiving signals from the same person on the same day, produce
+hash values in completely disjoint hash spaces. No amount of hash-list comparison can
+reveal a cross-site visit.
+
+---
+
+## What Reaches Home Assistant and Matter
+
+BFLD publishes to MQTT and HA. The following entities reach HA:
+
+- `binary_sensor.bfld_presence`
+- `sensor.bfld_motion`
+- `sensor.bfld_person_count`
+- `sensor.bfld_confidence`
+
+The Matter bridge exposes only OccupancySensing (presence) and motion. Identity risk
+score, rf_signature_hash, and all raw fields are rejected at both the HA and Matter
+boundaries.
+
+---
+
+## Seven Acceptance Criteria
+
+The implementation is done when these seven tests pass:
+
+1. Parse 802.11ac and 802.11ax BFI at 20–160 MHz bandwidth, 2×2 to 4×4 MIMO.
+2. Presence latency ≤ 1 second p95.
+3. Motion published at ≥ 1 Hz.
+4. Raw BFI bytes absent from all output (verified by fuzz test).
+5. Privacy mode suppresses all identity fields.
+6. Identical input → identical output hash (cross-platform determinism).
+7. Pipeline runs without CSI input (BFI-only mode).
+
+---
+
+## BFLD Is an Immune System, Not a Surveillance Lens
+
+The framing matters. BFLD does not produce identity — it measures identity risk and
+uses that measurement to gate what leaves the node. An immune system does not broadcast
+the identity of pathogens it encounters; it classifies, responds locally, and keeps
+detailed records inside the organism.
+
+WiFi 7 / 802.11be is deploying now. Multi-link operation will increase beamforming
+sounding frequency 3–5x. The passive attack surface will grow. The time to establish
+safe defaults in WiFi sensing stacks is before that installed base is in place.
+
+BFLD is that default.
+
+Full research bundle: `docs/research/BFLD/` in the wifi-densepose repository.
+Draft ADR: `docs/research/BFLD/08-adr-draft.md` (ADR-118).

docs/research/BFLD/README.md

@@ -0,0 +1,58 @@
+# BFLD Research Bundle — Beamforming Feedback Layer for Detection
+
+BFLD is the safety layer that detects when RF data becomes identifying. It sits between
+raw 802.11 beamforming feedback (BFI) and every downstream consumer — home automation,
+MQTT, Matter, cloud — measuring the identity-leakage potential of each frame and gating
+what leaves the node. It does not produce identity; it guards against accidental or
+adversarial exposure of identity.
+
+---
+
+## Table of Contents
+
+| File | Purpose |
+|------|---------|
+| [01-sota-survey.md](01-sota-survey.md) | State-of-the-art literature: BFI vs CSI, attack tooling, identity-inference research, privacy-preserving techniques |
+| [02-soul.md](02-soul.md) | Architectural intent, ethical stance, three non-negotiable invariants |
+| [03-security-threat-model.md](03-security-threat-model.md) | Adversary classes, attack trees, mitigations, trust-boundary diagram, per-privacy-class analysis |
+| [04-privacy-gating.md](04-privacy-gating.md) | privacy_class byte semantics, hash rotation algorithm, embedding lifecycle, wire-format diffs |
+| [05-automation-integration.md](05-automation-integration.md) | Home Assistant entities, Matter clusters, MQTT ACLs, cognitum federation |
+| [06-implementation-plan.md](06-implementation-plan.md) | New crate layout, reuse map, ESP32 additions, test plan, phased rollout |
+| [07-benchmarks-and-evaluation.md](07-benchmarks-and-evaluation.md) | Datasets, metrics, red-team protocol, comparison baselines |
+| [08-adr-draft.md](08-adr-draft.md) | Draft ADR-118 for formal project adoption |
+| [09-github-issue.md](09-github-issue.md) | GitHub issue draft for tracking implementation |
+| [10-gist.md](10-gist.md) | Public-facing one-pager / blog summary |
+
+---
+
+## Executive Summary
+
+1. **Problem.** IEEE 802.11ac/ax beamforming feedback (BFI) — the compressed angle matrices
+   (Phi/Psi, Givens rotation) exchanged between client and AP — is transmitted unencrypted
+   on the management plane. Academic work (BFId at ACM CCS 2025, LeakyBeam at NDSS 2025)
+   demonstrates that a passive sniffer with commodity hardware can re-identify individuals
+   and infer occupancy through walls using only these frames. Existing CSI-based sensing
+   pipelines have no explicit layer to detect when their output crosses from "motion event"
+   into "identity record."
+
+2. **Approach.** BFLD is a new crate (`wifi-densepose-bfld`) that wraps the BFI extraction
+   and normalization path in an identity-leakage estimator. Every output frame carries a
+   computed `identity_risk_score` and a `privacy_class` byte; downstream consumers decide
+   whether to act based on those tags rather than on raw measurements.
+
+3. **Novel contribution.** BFLD does not try to suppress identity inference — it tries to
+   *measure* it continuously and make the measurement explicit in every event. This
+   transforms a latent, silent risk into an observable, auditable signal. The combination
+   of per-day per-site hash rotation and a local-only identity embedding creates structural
+   impossibility of cross-site re-identification — not merely a policy promise.
+
+4. **Security posture.** Raw BFI never leaves the node. Identity embeddings live only in
+   an in-RAM ring buffer. The rf_signature_hash rotates daily using a per-site blake3
+   keyed-hash that is never transmitted. Matter and HA expose only presence, motion, and
+   person_count — never risk scores or embeddings.
+
+5. **Integration plan.** Six phases: P1 frame format + extractor stub, P2 feature
+   extraction + identity_risk, P3 privacy gate + MQTT, P4 HA integration, P5 Matter
+   exposure, P6 cognitum federation. Each phase maps to a numbered acceptance criterion.
+   The crate slots into the existing workspace between `wifi-densepose-signal` and
+   `wifi-densepose-sensing-server`.

docs/research/rvagent-rvf-integration/README.md

@@ -0,0 +1,113 @@
+# rvAgent + RVF integration for agentic flows in RuView
+
+**Status**: Research (Exploration) — Pre-Proposal
+**Date**: 2026-05-24
+**Author**: ruv
+
+---
+
+## TL;DR
+
+`vendor/ruvector/crates/rvAgent/` ships a production-grade Rust AI-agent framework with eight composable crates (`rvagent-core`, `-middleware`, `-tools`, `-subagents`, `-backends`, `-a2a`, `-acp`, `-mcp`, `-cli`). The framework already speaks **RVF cognitive containers** as its native state-persistence and inter-agent transport. RuView already uses RVF in `v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs`.
+
+**Integration thesis**: the two systems share a serialization substrate. Wiring `rvAgent` swarms into RuView turns the existing sensing pipeline into the substrate that an agentic flow can read from, reason about, and respond to — without writing a new agent runtime.
+
+Concrete value:
+
+1. **Operator-facing agents** that interpret BFLD / pose / vitals events live ("the kitchen has had no presence for 6 h but the kettle stayed on — page the carer").
+2. **In-process subagent coordination** for the multi-cog Cognitum Seed appliance — `cog-pose-estimation`, `cog-person-count`, `cog-ha-matter`, and the new BFLD pipeline can negotiate via rvAgent's CRDT state merging instead of ad-hoc IPC.
+3. **Witness chains** (ADR-028 / ADR-110) get an upstream consumer — rvAgent's audit-trail middleware persists per-decision attestations into the same RVF container an operator already verifies.
+4. **Local SONA learning** — rvAgent's 3-loop adaptive learning slots in alongside the per-home RuVector thresholds already proposed in ADR-116, with the same in-RAM-only privacy posture BFLD enforces (ADR-118 I2).
+
+---
+
+## 1. What rvAgent ships
+
+| Crate | Role | Key types |
+|-------|------|-----------|
+| `rvagent-core` | State machine + COW state cloning + budget tracking | `AgentState`, `Message`, `AgiContainer`, `Arena`, `Budget`, `Graph` |
+| `rvagent-middleware` | 14 built-in middlewares (security, witness, sanitizer, sona, hnsw) | `PipelineConfig`, `build_default_pipeline()` |
+| `rvagent-tools` | Tool definitions + dispatch | `Tool`, `ToolInput`, `ToolOutput` |
+| `rvagent-subagents` | Spawn isolated subagents with O(1) state clone | `Subagent`, CRDT merge |
+| `rvagent-backends` | LLM provider abstraction (Anthropic, OpenAI, local) | `Backend` trait |
+| `rvagent-mcp` | MCP server integration | MCP-style tool registry |
+| `rvagent-a2a` / `-acp` | Agent-to-agent transport, agent communication protocol | wire format |
+| `rvagent-cli` | Operator CLI | argv parsing |
+
+Selling points relevant to RuView:
+
+- **O(1) state cloning via `Arc`** → can spawn one subagent per sensing zone without copying gigabytes of context.
+- **Parallel tool execution** → multiple sensor queries (BFLD presence, vitals BPM, pose) issued in parallel from one rvAgent decision step.
+- **Path confinement + env-var sanitization** → operator-facing agents that touch the host filesystem (e.g., reading `data/recordings/`) stay sandboxed.
+- **Witness chains** in `rvagent-middleware::witness` → already RVF-formatted; round-trips cleanly with ADR-028.
+
+## 2. What RVF already does in RuView
+
+`v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs` defines the on-disk container format used for:
+
+- ADR-110 witness attestations (`SEG_MANIFEST`, `SEG_META`).
+- Soul Signature graphs (`docs/research/soul/specification.md` §3).
+- BFLD class-1 (derived) frames once the operator opts into research mode (ADR-118 §1.4).
+
+Each RVF blob is content-addressed (BLAKE3 of the canonical byte representation) and carries a typed segment manifest. The format is intentionally extension-friendly — segment types are `u8` enums, new types can land without breaking older readers.
+
+## 3. The integration surface
+
+Three concrete touchpoints, each shippable independently.
+
+### 3.1 RVF as the rvAgent ↔ RuView wire
+
+rvAgent's `AgiContainer` (`rvagent-core/src/agi_container.rs`, 627 LOC) already produces RVF-compatible blobs as its persistent state format. RuView only needs to define **two segment types** in `rvf_container.rs`:
+
+- `SEG_AGENT_STATE = 0x08` — serialized `rvagent_core::AgentState` (the cloned-on-write tree from `cow_state.rs`).
+- `SEG_DECISION = 0x09` — a single agent decision step: tool calls issued, outputs received, witness signature.
+
+With these two segments, an rvAgent session and a RuView sensing session can interleave entries in the same RVF blob. The witness-bundle script (ADR-028) iterates segments by type, so it would attest both halves with one signing pass.
+
+### 3.2 BFLD events as rvAgent tool inputs
+
+`wifi-densepose-bfld::BfldEvent` (iter 13) is already JSON-serializable via `to_json()`. Wrapping it as an `rvagent_tools::ToolOutput` is a 20-line shim: the agent issues a `read_bfld_state()` tool, the runtime returns the latest event JSON, the agent reasons over it. The full event surface (presence/motion/count/identity_risk/zone_id) becomes available as agent context without any new IPC.
+
+`BfldEvent → ToolOutput` mapping:
+```rust
+impl From<BfldEvent> for ToolOutput {
+    fn from(e: BfldEvent) -> Self {
+        ToolOutput::json(e.to_json().expect("BfldEvent JSON"))
+    }
+}
+```
+
+### 3.3 cog-* as rvAgent subagents
+
+`cog-pose-estimation`, `cog-person-count`, `cog-ha-matter`, and (proposed) `cog-bfld` already share a packaging convention (ADR-100). Each cog can register as a subagent with rvAgent's hub: the cog implements the `Subagent` trait, exports its tool surface, and inherits the parent agent's CRDT state. The queen agent (`rvagent-queen.md` persona) routes operator queries across the cog mesh.
+
+Concrete example:
+- Operator query: "is grandma awake yet?"
+- Queen agent fans out to: `cog-bfld` (presence in bedroom), `cog-quantum-vitals` (HR baseline shift), `cog-pose-estimation` (sitting/standing transition).
+- Each cog returns within budget; queen synthesizes the answer; witness chain logs the decision for compliance audit.
+
+## 4. Open questions
+
+1. **Workspace inclusion**: is `vendor/ruvector/crates/rvAgent/` already on the v2 workspace path, or does it need to be added as a path dep under `wifi-densepose-bfld` / a new `wifi-densepose-agent` crate?
+2. **Async runtime**: rvAgent backends are tokio-based. The BFLD `Publish` trait is intentionally sync (iter 22). A small adapter (sync `Publish` ↔ async `Backend`) probably belongs in a `wifi-densepose-agent` crate, not in BFLD itself.
+3. **Privacy class composition**: what's the rvAgent equivalent of BFLD's `PrivacyClass`? `rvagent-middleware::sanitizer` strips at the tool-output boundary; should it consume `PrivacyClass` from the originating BFLD event so the agent never even sees a class-3 identity field?
+4. **Soul Signature interaction**: rvAgent's `SoulMatchOracle` integration (ADR-121 §2.6) could be the bridge from the Soul Signature graph (`docs/research/soul/`) to the agent decision layer. Worth a dedicated sub-section.
+5. **MCP**: `rvagent-mcp` exposes tools to external MCP clients. Should the BFLD `BfldPipelineHandle::send` surface land as an MCP tool here, or stay private to in-process rvAgent flows?
+
+## 5. Proposed next steps (decision deferred)
+
+- **D1**: Open ADR-124 — "rvAgent + RVF integration for RuView agentic flows" — capturing the segment-type assignments, the cog-subagent contract, and the privacy-class composition rule.
+- **D2**: Scaffold `v2/crates/wifi-densepose-agent` with the sync ↔ async adapter and one example tool (`read_bfld_state`).
+- **D3**: Add `SEG_AGENT_STATE` and `SEG_DECISION` to `rvf_container.rs` as `#[cfg(feature = "agent")]` segments so the v0 ship doesn't pull rvAgent's transitive deps by default.
+- **D4**: Land a one-page demo in `examples/agent-bedroom-check/` showing the queen-agent flow end-to-end against the `BfldPipelineHandle`.
+
+## 6. References
+
+- rvAgent: `vendor/ruvector/crates/rvAgent/README.md`, `rvagent-core/src/agi_container.rs`, `rvagent-middleware/docs/UNICODE_SECURITY.md`
+- Agent personas: `vendor/ruvector/crates/rvAgent/.ruv/agents/{rvagent-coder,rvagent-queen,rvagent-tester,rvagent-security}.md`
+- RVF container: `v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs`
+- ADR-028 (witness): `docs/adr/ADR-028-esp32-capability-audit.md`
+- ADR-100 (cog packaging), ADR-110 (witness chain), ADR-116 (cog-ha-matter)
+- ADR-118 (BFLD): `docs/adr/ADR-118-bfld-beamforming-feedback-layer-for-detection.md`
+- Soul Signature: `docs/research/soul/specification.md`
+- BFLD impl branch: `feat/adr-118-bfld-impl`, currently at iter 25 (`e8b4fdbc8`)

docs/research/soul/README.md

@@ -0,0 +1,116 @@
+# Soul Signature — Research Specification
+
+**Status:** Research Specification (Pre-Implementation)
+**Date:** 2026-05-24
+**Maintainer:** ruv
+
+---
+
+## What Is a Soul Signature
+
+A Soul Signature is a fused multi-modal biometric identity vector derived entirely
+from passive electromagnetic measurement of a person inside a room equipped with
+WiFi-DensePose / RuView sensing nodes. No wearable, no camera, no explicit
+scan-time consent moment is required for recognition once a person has enrolled.
+
+The word "soul" is deliberate product framing for a scientifically defensible concept:
+the same relationship a fingerprint bears to identity in forensic science, or FaceID
+to phone authentication, but extended to a new sensing dimension — passive RF at
+distance, through walls, at room scale. Seven orthogonal electromagnetic observables,
+fused into a single content-addressed RVF graph file, constitute the signature.
+
+The claim is not mystical. Every channel is grounded in published physics and prior
+WiFi sensing literature. Every assertion about discriminative power either cites a
+peer-reviewed result or is explicitly marked "open research; baseline TBD."
+
+---
+
+## What a Soul Signature Is NOT
+
+- It is NOT a replacement for fingerprint scanners, iris scanners, or FaceID on
+  accuracy-per-attempt measures. Current RF biometrics are less mature than those
+  modalities. See `security.md` for the honest error-rate picture.
+- It is NOT a single number, hash, or deterministic bit string. It is a
+  probabilistic match against a stored graph with a calibrated false-accept rate.
+- It is NOT medically diagnostic. It detects biophysical proxies, not conditions.
+  "Gait asymmetry increased 18% over 14 days" is the output, never "Parkinson's."
+- It is NOT equivalent to explicit-consent biometrics in regulated contexts. GDPR
+  and HIPAA modes are defined and mandatory for healthcare deployments.
+- It is NOT currently deployable as a legal evidence instrument.
+- It is NOT snake oil, energy healing, or anything outside measurable electrophysics.
+
+---
+
+## Document Map
+
+| File | Contents |
+|------|----------|
+| `specification.md` | Typed RVF graph schema; all node types, edge types, serialization format; aggregator vs stored profile distinction |
+| `scanning-process.md` | Structured 60-second enrollment protocol; hardware requirements; quality gates; fast-scan and continuous modes; re-scan cadence |
+| `security.md` | Full threat model; five adversaries; mitigations; cryptographic primitive choices; GDPR/HIPAA mode; open research items |
+| `references.md` | All cited ADRs, papers, datasets, standards |
+
+---
+
+## Conceptual Graph (ASCII)
+
+The following depicts one example soul signature as a graph stored in a single
+RVF container. Each box is an RVF node (a SEG_EMBED or SEG_META segment). Each
+arrow is a typed edge stored in the graph manifest.
+
+```
+  +-----------------------+
+  |   AETHER_Embedding    |  128-dim f32, L2-normalized (ADR-024)
+  |   contrastive CSI     |  HNSW-searchable via ruvector-core
+  |   backbone embedding  |
+  +----------+------------+
+             |  derived_from
+             v
+  +-----------+-----------+          +------------------------+
+  | FieldModel_Residual   +---fuses--+  Subcarrier_Reflection  |
+  | ADR-030 perturbation  |          |  per-angle multipath   |
+  | eigenmode projection  |          |  amplitude + phase     |
+  +----------+------------+          +------------------------+
+             |  correlates_with
+             v
+  +----------+------------+          +------------------------+
+  |  Cardiac_HR_Profile   +--links---+  Cardiac_Waveform_     |
+  |  baseline_bpm, HRV_LF |          |  Morphology (wavelet   |
+  |  HRV_HF, rhythm_class |          |  coefficients)         |
+  +----------+------------+          +------------------------+
+             |  temporally_colocated
+             v
+  +----------+------------+
+  | Respiratory_Pattern   |
+  |  baseline_bpm, depth, |
+  |  apnea_index, HRV_RSA |
+  +----------+------------+
+             |  temporally_colocated
+             v
+  +----------+------------+          +------------------------+
+  |   Gait_Timing         +--links---+  Skeletal_Proportions  |
+  |  cadence, stride_var, |          |  torso/limb ratios     |
+  |  double_support_pct,  |          |  from ADR-079 keypoints |
+  |  asymmetry_index      |          +------------------------+
+  +----------+------------+
+             |  attested_by
+             v
+  +----------+------------+
+  |   WitnessChain        |  Ed25519 over (content_hash ||
+  |   ADR-110 attestation |  timestamp || device_id) per ADR-110
+  +-----------------------+
+```
+
+File naming convention: `signature-<sha256-of-rvf-content>.rvf`
+
+---
+
+## Implementation Status
+
+This is a **research specification**. None of the soul-signature-specific graph
+container logic is implemented yet. The constituent ADRs (AETHER, MERIDIAN,
+RuvSense field model, ADR-039 vitals, ADR-110 witness chain) provide the substrate.
+The soul signature is the composition layer above them.
+
+A future implementation ADR should reference this document and assign acceptance
+tests derived from the quality gates defined in `scanning-process.md`.

docs/research/soul/references.md

@@ -0,0 +1,138 @@
+# Soul Signature — References
+
+**Status:** Research Specification (Pre-Implementation)
+**Date:** 2026-05-24
+**Author:** ruv
+
+---
+
+## 1. Internal Architecture Decision Records
+
+All ADRs are located at `docs/adr/ADR-XXX-*.md` in this repository.
+
+| ADR | Title | Relevance to soul signature |
+|---|---|---|
+| ADR-003 | RVF Cognitive Containers for CSI Data | RVF container format used by soul signature |
+| ADR-004 | HNSW Vector Search for Signal Fingerprinting | HNSW index for person_track embedding search |
+| ADR-005 | SONA Self-Learning Pose Estimation | LoRA adaptation, EWC regularization, environment profiles |
+| ADR-007 | Post-Quantum Cryptography Secure Sensing | PQC cryptographic context; foundation for ADR-108/109 |
+| ADR-010 | Witness Chains Audit Trail Integrity | Witness chain design; Ed25519 over frame bundles |
+| ADR-014 | SOTA Signal Processing Algorithms | RuvSense pipeline: conjugate multiplication, Hampel filter, spectrogram, BVP |
+| ADR-021 | Vital Sign Detection via rvdna Pipeline | Cardiac HR / respiratory extraction; bandpass filters; ADR-039 vitals packet |
+| ADR-023 | Trained DensePose Model with RuVector Pipeline | CsiToPoseTransformer backbone; MPJPE baseline 91.7 mm |
+| ADR-024 | Project AETHER — Contrastive CSI Embedding Model | Primary soul signature identity channel; 128-dim L2-normalized embedding; HNSW person_track index (>80% mAP target at 5 subjects) |
+| ADR-027 | Project MERIDIAN — Cross-Environment Domain Generalization | Environment-disentangled embeddings; HardwareNormalizer; multi-room portability |
+| ADR-029 | RuvSense Multistatic Sensing Mode | Multi-node mesh; 20 Hz DensePose; <30 mm jitter; person separation |
+| ADR-030 | RuvSense Persistent Field Model | Field normal modes; SVD eigenstructure; perturbation extraction; longitudinal drift; adversarial detection; cross-room continuity |
+| ADR-039 | ESP32-S3 Edge Intelligence Pipeline | Vitals packet wire format (magic `0xC511_0002`); HR/BR on-device extraction |
+| ADR-075 | MinCut Person Separation | ruvector-mincut for multi-person track assignment |
+| ADR-079 | Camera Ground-Truth Training | Paired camera + CSI training; skeletal proportions accuracy |
+| ADR-082 | Pose Tracker Confirmed Output Filter | Pose tracker output confidence filtering |
+| ADR-100 | Cog Packaging Specification | Ed25519 firmware signing; supply chain integrity |
+| ADR-105 | Federated CSI Training | Federated AETHER fine-tuning; secure aggregation |
+| ADR-106 | DP-SGD and Primitive Isolation | Differential privacy at training; biometric primitive isolation; (ε, δ)-DP budget |
+| ADR-107 | Cross-Installation Federation | Cross-installation secure aggregation; DH key exchange |
+| ADR-108 | Kyber Post-Quantum Key Exchange | Kyber-768 (NIST FIPS 203); hybrid X25519 + Kyber during migration |
+| ADR-109 | Dilithium PQC Signatures | Dilithium-3 (NIST FIPS 204); hybrid Ed25519 + Dilithium; cog signing |
+| ADR-110 | ESP32-C6 Firmware Extension | Wi-Fi 6 HE-LTF CSI (242 subcarriers); 802.15.4 time-sync; TWT; Ed25519 witness chain per-frame |
+| ADR-113 | Multistatic Placement Strategy | Node placement geometry; coverage analysis |
+| ADR-115 | Home Assistant Integration (HA-DISCO + HA-MIND) | Privacy mode; MQTT auto-discovery; semantic primitives layer under which soul signature operates |
+
+---
+
+## 2. AETHER and Contrastive Embedding Foundations
+
+- Chen, T., Kornblith, S., Norouzi, M., & Hinton, G. (2020). **A Simple Framework for Contrastive Learning of Visual Representations** (SimCLR). *ICML 2020*. arXiv:2002.05709.
+- Chen, T., Kornblith, S., Sohl-Dickstein, J., & Hinton, G. (2020). **Big Self-Supervised Models are Strong Semi-Supervised Learners** (SimCLR v2). *NeurIPS 2020*. arXiv:2006.10029.
+- Bardes, A., Ponce, J., & LeCun, Y. (2022). **VICReg: Variance-Invariance-Covariance Regularization for Self-Supervised Learning**. *ICLR 2022*. arXiv:2105.04906.
+- Grill, J.-B., et al. (2020). **Bootstrap Your Own Latent: A New Approach to Self-Supervised Learning** (BYOL). *NeurIPS 2020*. arXiv:2006.07733.
+- Wang, T. & Isola, P. (2020). **Understanding Contrastive Representation Learning through Alignment and Uniformity on the Hypersphere**. *ICML 2020*. arXiv:2005.10242.
+
+---
+
+## 3. WiFi CSI Biometric Identification (Prior Art)
+
+- **IdentiFi** (2025): Self-supervised WiFi-based identity recognition in multi-user smart environments. Contrastive pretraining in the signal domain produces identity-discriminative embeddings without spatial labels. *PMC:12115556*.
+- **WhoFi** (2025): Transformer-based WiFi CSI encoding for person re-identification. 95.5% accuracy on NTU-Fi (18 subjects). Validates transformer backbones for CSI re-ID. arXiv:2507.12869.
+- **Wi-PER81** (2025): Benchmark dataset of 162K wireless packets for WiFi-based person re-identification using Siamese networks. *Nature Scientific Data*, 2025. doi:10.1038/s41597-025-05804-0.
+- **CAPC** (Context-Aware Predictive Coding, 2024): CPC + Barlow Twins for WiFi sensing. 24.7% accuracy improvement on unseen environments. arXiv:2410.01825.
+- **SSL for WiFi HAR Survey** (2025): Comprehensive evaluation of SimCLR, VICReg, Barlow Twins, SimSiam on WiFi CSI. arXiv:2506.12052.
+
+---
+
+## 4. WiFi Sensing SOTA (Pose, Vitals, Gait)
+
+- Geng, J., Huang, D., & De la Torre, F. (2022). **DensePose From WiFi**. *CMU*. arXiv:2301.00250.
+- Adib, F., Kabelac, Z., Katabi, D., & Miller, R.C. (2015). **3D Tracking via Body Radio Reflections** (WiTrack). *NSDI 2015*.
+- Wang, J., Gao, X., Zhang, K., & Liu, X. (2019). **Widar 3.0: Zero-Effort Cross-Domain Gesture Recognition with Wi-Fi**. *MobiSys 2019*.
+- Zhao, M., Li, T., Abu Alsheikh, M., Tian, Y., Zhao, H., Torralba, A., & Katabi, D. (2018). **Through-Wall Human Pose Estimation Using Radio Signals**. *CVPR 2018*.
+- Zhao, M., Adib, F., & Katabi, D. (2016). **Emotion Recognition Using Wireless Signals** (EQ-Radio). *MobiCom 2016*. (HRV from WiFi; cardiac biometric baseline)
+- **PerceptAlign** (Chen et al., 2026): Geometry-conditioned cross-layout WiFi pose estimation. >60% cross-domain error reduction. Dataset: 21 subjects, 5 scenes, 18 actions. arXiv:2601.12252.
+- **Person-in-WiFi 3D** (Yan et al., 2024): Multi-person 3D pose from WiFi. 91.7 mm MPJPE (single-person). *CVPR 2024*.
+- **DGSense** (Zhou et al., 2025): Domain-invariant features for WiFi/mmWave/acoustic sensing. arXiv:2502.08155.
+- **X-Fi** (Chen & Yang, 2025): Modality-invariant foundation model for human sensing. 24.8% MPJPE improvement on MM-Fi. *ICLR 2025*. arXiv:2410.10167.
+- **AM-FM** (2026): First WiFi foundation model, pretrained on 9.2M CSI samples, 20 device types, 439 days. arXiv:2602.11200.
+- Ma, Y., Zhou, G., Wang, S., Zhao, H., & Jung, W. (2018). **SignFi: Sign Language Recognition Using WiFi**. *ACM IMWUT*. arXiv:1806.04583.
+
+---
+
+## 5. Training Datasets Referenced
+
+- **MM-Fi** (2022): Multi-Modal Non-Intrusive 4D Human Dataset — WiFi CSI, mmWave, LiDAR, RGB-D. 27 subjects, 40 actions, 5 environments, 320K samples. 56-subcarrier CSI, 17 COCO keypoints. [github.com/ybhbingo/MMFi_dataset]
+- **Wi-Pose** (2022): WiFi-based 3D pose estimation dataset. Used in ADR-015.
+- **NTU-Fi** (2022): 56 activities, WiFi CSI, 75 Hz sampling. Used for WhoFi evaluation.
+
+---
+
+## 6. Differential Privacy
+
+- Abadi, M., Chu, A., Goodfellow, I., McMahan, H.B., Mironov, I., Talwar, K., & Zhang, L. (2016). **Deep Learning with Differential Privacy**. *CCS 2016*. [Moments Accountant; DP-SGD formulation used in ADR-106]
+- Mironov, I. (2017). **Rényi Differential Privacy**. *CSF 2017*. [Alternative DP accounting; referenced in ADR-106 as future enhancement]
+- Shokri, R., Stronati, M., Song, C., & Shmatikov, V. (2017). **Membership Inference Attacks Against Machine Learning Models**. *IEEE S&P 2017*. [Motivation for DP-SGD in ADR-106]
+
+---
+
+## 7. Cryptographic Standards
+
+- **RFC 8032** (2017): Edwards-Curve Digital Signature Algorithm (EdDSA). [Ed25519; used in ADR-110 witness chain]
+- **RFC 8439** (2018): ChaCha20 and Poly1305 for IETF Protocols. [At-rest encryption primitive specified in security.md §5]
+- **RFC 9106** (2021): Argon2 Memory-Hard Function. [KDF for soul signature at-rest key derivation]
+- **NIST FIPS 203** (2024): Module-Lattice-Based Key-Encapsulation Mechanism Standard (ML-KEM / Kyber). [ADR-108; post-quantum key exchange]
+- **NIST FIPS 204** (2024): Module-Lattice-Based Digital Signature Standard (ML-DSA / Dilithium). [ADR-109; post-quantum signatures]
+- **NIST SP 800-132 Draft** (2024): Recommendation for Password-Based Key Derivation. [Argon2id parameter guidance]
+
+---
+
+## 8. Biometric Standards (for Standards Awareness)
+
+The soul signature is not currently certified to any of these standards but the
+specification is designed with awareness of the relevant frameworks.
+
+- **ISO/IEC 19794-1:2011**: Biometric data interchange formats — Part 1: Framework.
+  [Top-level; soul signature's node/edge schema follows the typed-attribute-record
+  philosophy of this standard]
+- **ISO/IEC 19794-2:2011**: Biometric data interchange formats — Part 2: Finger
+  minutiae data. [Structural analog for how the soul signature encodes per-channel
+  discriminative features]
+- **ISO/IEC 19794-4:2011**: Biometric data interchange formats — Part 4: Finger image data.
+  [Image-container analog; soul signature extends the concept to vector-valued
+  multi-channel templates]
+- **ISO/IEC 29794-1:2016**: Biometric sample quality — Part 1: Framework.
+  [Quality scoring framework; soul signature's per-node `confidence` field
+  is conceptually analogous to ISO 29794 quality scores]
+- **ISO/IEC 30107-3:2023**: Biometric presentation attack detection — Part 3:
+  Testing and reporting. [Presentation attack (anti-spoofing) framework;
+  the adversarial.rs module is the soul signature's PAD implementation]
+
+---
+
+## 9. Reading List for RF Biometrics Newcomers
+
+Ordered from most accessible to most technical.
+
+1. Adib, F. (2017). **Using Radio Reflections to See the World**. MIT PhD thesis. [Most accessible introduction to using RF for human sensing; covers WiVi, WiTrack, EQ-Radio]
+2. Ma, Y., et al. (2019). **WiFi Sensing with Channel State Information: A Survey**. *ACM Computing Surveys*. doi:10.1145/3310194. [Comprehensive survey of CSI-based sensing approaches through 2019]
+3. Wang, X., et al. (2023). **A Survey on WiFi Sensing: From Signal to Action**. *IEEE Internet of Things Journal*. [Updated survey through 2023; covers contrastive learning approaches]
+4. Chen, T., et al. (2020). **A Simple Framework for Contrastive Learning** (SimCLR). arXiv:2002.05709. [Best starting point for understanding the contrastive learning approach used in AETHER]
+5. Geng, J., et al. (2022). **DensePose From WiFi**. arXiv:2301.00250. [Direct ancestor of this codebase; describes the cross-modal CSI → DensePose mapping]
+6. Abadi, M., et al. (2016). **Deep Learning with Differential Privacy**. CCS 2016. [Essential reading before any deployment collecting biometric data at training time]

docs/research/soul/scanning-process.md

@@ -0,0 +1,306 @@
+# Soul Signature — Scanning Process
+
+**Status:** Research Specification (Pre-Implementation)
+**Date:** 2026-05-24
+**Author:** ruv
+
+---
+
+## 1. Hardware Prerequisites
+
+### 1.1 Full Protocol (N ≥ 3 Nodes)
+
+| Component | Minimum | Recommended | Notes |
+|---|---|---|---|
+| Sensing nodes | 3 × ESP32-S3 (ADR-028) | 5+ nodes | Multi-node triangulation reduces angle-dependent blind spots; ADR-029 multistatic mesh |
+| Compute appliance | Cognitum Seed (Pi 5 + Hailo) | Same | Runs the field model, AETHER inference, vitals pipeline |
+| Network link | 2.4 GHz or 5 GHz AP | Dedicated sensing AP | Shared AP with user traffic degrades CSI frame rate |
+| Firmware version | ADR-110 v0.7.0+ | Same | Ed25519 witness chain required for attestation |
+| Clock sync | 802.15.4 time-sync (ESP32-C6) or NTP fallback | 802.15.4 preferred | ±100 µs alignment per ADR-110; NTP gives ±5 ms |
+
+### 1.2 Degraded Mode (1 Node)
+
+A single-node enrollment produces an incomplete signature:
+- Skeletal proportions: degraded (single-angle view)
+- Subcarrier reflection profile: single orientation only (3-orientation protocol collapses to 1)
+- AETHER embedding: usable but lower confidence
+- Cardiac / respiratory: unaffected (single-node sufficient)
+- Gait timing: usable if node placement allows bidirectional walk
+
+Single-node signatures MUST be tagged `degraded_mode: true` in the manifest. The
+match score uses only the channels that met minimum confidence thresholds. The
+soul signature is technically valid but should be re-enrolled with multi-node
+hardware when possible.
+
+### 1.3 ESP32-C6 Uplift (Wi-Fi 6 HE-LTF)
+
+When at least one ESP32-C6 node is present (ADR-110), the subcarrier count
+expands from 52 (HT-LTF, S3) to up to 242 (HE-LTF, C6). The MERIDIAN
+HardwareNormalizer (ADR-027) maps all nodes to a canonical 56-subcarrier
+representation for the AETHER backbone. The full 242-subcarrier profile is
+preserved in the SubcarrierReflectionProfile node for higher-fidelity matching
+when available. The C6's 802.15.4 time-sync (±100 µs) also improves multistatic
+coherence relative to NTP-only S3 meshes.
+
+---
+
+## 2. Structured 60-Second Enrollment Protocol
+
+The enrollment protocol produces exactly one `.rvf` soul signature file. The
+protocol is structured into five phases with exact timing. A human-readable
+prompt sequence should be delivered to the subject via audio or display.
+
+### Phase 0 — Empty-Room Field Recalibration (T+0 to T+10)
+
+Before the subject enters the sensing zone, the room must be empty and the
+ADR-030 field model must be current.
+
+```
+T+0s   : System checks field model age. Maximum age: 4 hours.
+          If stale or absent → run field recalibration:
+            Collect 1,200 CSI frames at 20 Hz (60 seconds of empty room)
+            Compute per-link Welford mean and covariance
+            Run SVD on covariance matrix → top-K=8 eigenmode vectors
+            Store in field_model.rs::FieldNormalMode
+
+T+0–10s: Quiet sampling of empty-room field state. No subject present.
+          Operator prompt: "Please ensure the room is empty."
+          System: verifies presence score < 0.1 (ADR-039 Tier 2 presence detection).
+          Failure: if presence score ≥ 0.1, abort and report FAIL_ROOM_NOT_EMPTY.
+```
+
+This phase is skipped (not aborted) if the field model was updated within the
+last 4 hours AND the current empty-room sampling confirms presence score < 0.05.
+
+### Phase 1 — Deep Breathing Baseline (T+10 to T+25)
+
+Subject enters the sensing zone and performs five deep breathing cycles.
+
+```
+T+10s  : Subject enters scan zone. System detects presence.
+          Operator prompt: "Please stand still and breathe slowly and deeply."
+
+T+10–25s: Subject stands at zone center, facing node cluster.
+           Five complete breath cycles, each ≥ 4 seconds.
+           System collects:
+             - ADR-021 BreathingExtractor: baseline_bpm, depth_amplitude,
+               inspiration_expiration_ratio, HRV_RSA
+             - ADR-021 HeartRateExtractor: initial HR, HRV_SDNN (partial)
+             - AETHER embedding: accumulates over 300 CSI frames (20 Hz × 15s)
+           Quality gate: BreathingExtractor VitalCoherenceGate must emit
+             PERMIT for ≥ 10 of the 15 seconds. Failure → FAIL_POOR_BREATHING_SIGNAL.
+```
+
+### Phase 2 — Seated Rest (T+25 to T+35)
+
+Subject sits to minimize motion and allow cardiac signal isolation.
+
+```
+T+25s  : Operator prompt: "Please sit down and rest quietly."
+
+T+25–35s: Subject seated, minimal movement.
+           System collects:
+             - HeartRateExtractor: HR baseline, HRV_SDNN, HRV_RMSSD,
+               LF/HF ratio, sinus rhythm classification
+             - Cardiac_Waveform_Morphology: 64-coefficient wavelet decomposition
+               of bandpass-filtered cardiac phase signal (0.8–2.0 Hz)
+           Quality gate: HR confidence ≥ 0.6 for ≥ 7 of 10 seconds.
+             Failure → FAIL_POOR_CARDIAC_SIGNAL (soft failure: cardiac nodes
+             marked low-confidence; signature proceeds without them if AETHER
+             and gait nodes pass their own thresholds).
+```
+
+### Phase 3 — Gait Walk (T+35 to T+50)
+
+Subject walks a 2-meter line twice in each direction.
+
+```
+T+35s  : Operator prompt: "Please walk a straight line of 2 meters back and
+          forth twice at your natural pace."
+
+T+35–50s: Subject walks: A→B, B→A, A→B, B→A (four transits, ≥ 8 strides total).
+           System collects (via pose_tracker.rs, ADR-029 Sect 2.7):
+             - GaitTimingNode: cadence, stride_period_variance,
+               double_support_pct, asymmetry_index, step_width_m
+             - SkeletalProportionsNode: torso/limb ratios from 17-keypoint
+               trajectory accumulated over ≥ 8 strides
+             - AETHER embedding: continues accumulating (300 more frames)
+           Quality gate: ≥ 8 strides detected with confidence ≥ 0.7 per stride.
+             Failure → FAIL_INSUFFICIENT_GAIT_DATA.
+           Note: the ruvector-mincut DynamicPersonMatcher must confirm only one
+           person is tracked. If two tracks are active → FAIL_MULTIPLE_SUBJECTS.
+```
+
+### Phase 4 — Standing Orientation Scan (T+50 to T+60)
+
+Subject stands at three orientations to capture the subcarrier reflection profile.
+
+```
+T+50s  : Operator prompt: "Please stand facing the wall. I will ask you to
+          rotate in place twice."
+
+T+50–53s: Orientation 0° (subject faces primary node cluster).
+           System collects: SubcarrierReflectionProfile at 0°
+           (ADR-030 field-subtracted, 56 subcarriers, amplitude + phase).
+
+T+53s  : Operator prompt: "Please turn 90 degrees to your right."
+
+T+53–56s: Orientation 90°.
+           System collects: SubcarrierReflectionProfile at 90°.
+
+T+56s  : Operator prompt: "Please turn 90 degrees to your right again."
+
+T+56–60s: Orientation 180°.
+           System collects: SubcarrierReflectionProfile at 180°.
+           Body_Field_Coupling: computed from AETHER attention map weighted
+           by ADR-030 top-K=8 eigenvectors (final computation at T=60s).
+
+T+60s  : Enrollment window closes.
+          AETHER embedding finalized: mean pool over all ~1,200 accumulated frames.
+          All node confidence values computed.
+```
+
+---
+
+## 3. Quality Gates
+
+The enrollment FAILS and emits a structured error code if any of the following
+conditions are met. Failed enrollments do not produce a stored `.rvf` file.
+
+| Gate | Condition for FAIL | Error code |
+|---|---|---|
+| Room occupied | Presence score ≥ 0.1 at Phase 0 end | `FAIL_ROOM_NOT_EMPTY` |
+| Multiple subjects | ≥ 2 active pose tracks during Phases 1–4 | `FAIL_MULTIPLE_SUBJECTS` |
+| Intermittent presence | Subject exits sensing zone for > 3 consecutive seconds | `FAIL_SUBJECT_LEFT_ZONE` |
+| AETHER confidence low | Final embedding confidence < 0.6 (HNSW search confidence) | `FAIL_AETHER_LOW_CONFIDENCE` |
+| Breathing signal absent | VitalCoherenceGate PERMIT rate < 67% during Phase 1 | `FAIL_POOR_BREATHING_SIGNAL` |
+| Gait data insufficient | Fewer than 8 strides detected with confidence ≥ 0.7 | `FAIL_INSUFFICIENT_GAIT_DATA` |
+| Field model dirty | Field model age > 4 hours and recalibration refused | `FAIL_STALE_FIELD_MODEL` |
+| Adversarial detection | RuvSense adversarial.rs flags physically impossible signal | `FAIL_ADVERSARIAL_SIGNAL` |
+| Node count below minimum | Fewer than 2 nodes online during Phases 3–4 | `WARN_DEGRADED_MODE` (not a hard fail; produces degraded signature) |
+
+Soft failures (cardiac signal only) do not abort the enrollment; they mark those
+nodes as low-confidence and reduce the match weight for those channels at
+recognition time.
+
+---
+
+## 4. Fast Scan (10-Second Degraded Identification)
+
+A fast scan produces a partial query embedding, not a stored profile. It is used
+for recognition of already-enrolled subjects, not for new enrollment.
+
+```
+T+0s   : System checks whether field model is current (age < 4 hours).
+          If stale: recognition accuracy degraded; warn operator.
+
+T+0–10s: Subject stands still at zone center, natural breathing.
+          System collects: AETHER embedding (200 frames, 10s at 20 Hz).
+          Cardiac HR: partial (confidence typically < 0.5).
+          Gait: not available.
+          Subcarrier reflection: 1 orientation only.
+
+T+10s  : Query issued against all stored profiles in HNSW index.
+          Match score computed using available channels only.
+          Cardiac, gait, and skeletal proportions excluded from denominator
+          (availability factor = 0 for absent channels).
+```
+
+Fast scan is acceptable for:
+- Returning resident recognition (already enrolled, low-friction use case)
+- Home automation triggers (occupancy attribution per ADR-115 HA-MIND)
+
+Fast scan is NOT acceptable for:
+- Initial enrollment
+- High-assurance access control
+- Healthcare identification
+
+---
+
+## 5. Continuous Mode — Implicit Signature Refinement
+
+In continuous operating mode, the system incrementally updates the online
+aggregator for enrolled persons as they go about their normal activities. The
+stored profile is re-published from the aggregator every 90 days (or on the
+re-scan cadence, whichever comes first). This means a deployed system becomes
+more accurate over time, not less.
+
+Convergence property: the Welford online statistics in the aggregator are
+numerically stable and converge to the true population mean/variance as
+observation count increases. The AETHER embedding accumulated over thousands
+of natural-activity windows is more representative than a single 60-second
+enrollment. The stored profile is replaced (not amended) on each re-publish; the
+old profile is archived (not deleted) per the forward-secrecy requirements in
+`security.md`.
+
+The continuous mode raises a consent concern: a person is effectively being
+re-enrolled continuously without explicit action. This is addressed in
+`security.md §4` (Consent Architecture).
+
+---
+
+## 6. Multi-Room Enrollment
+
+When a person moves across multiple sensing zones (e.g., living room and bedroom
+each with a Cognitum Seed node cluster), the cross-room signature works as follows:
+
+1. Full 60-second enrollment is performed in the primary room. This produces the
+   initial stored profile with `environment_normalized: false` in the manifest.
+
+2. When the MERIDIAN domain generalization layer (ADR-027) is active, the
+   HardwareNormalizer maps the enrollment embedding to the environment-invariant
+   subspace. The stored profile is updated to `environment_normalized: true`.
+
+3. In subsequent rooms, a fast scan (10s) is sufficient to attribute identity. The
+   MERIDIAN-normalized AETHER embedding handles the room shift.
+
+4. For healthcare deployments requiring room-by-room re-enrollment for regulatory
+   reasons, a per-room enrollment protocol runs in each room and the signatures
+   are linked by the opaque `person_id` field (never by raw PII).
+
+---
+
+## 7. Re-Scan Cadence
+
+| Deployment context | Re-scan interval | Rationale |
+|---|---|---|
+| Healthy adult (residential) | 90 days | Anatomy stable; continuous mode refines continuously |
+| Child (growing skeleton) | 30 days | Skeletal proportions change; gait timing changes |
+| Healthcare / clinical | Per clinical event | Post-surgery, post-illness, post-significant weight change |
+| Post-exercise monitoring | 7 days during active programs | Body composition changes affect RF backscatter |
+| Any | On drift alert from longitudinal.rs (ADR-030 Tier 4) | System-initiated; shown to user as "calibration recommended" |
+
+The `longitudinal.rs` module monitors five drift metrics (GaitSymmetry,
+StabilityIndex, BreathingRegularity, MicroTremor, ActivityLevel) using Welford
+statistics over daily observations. When any metric exceeds 2-sigma deviation
+sustained for 3 consecutive days, a `DriftAlert` is emitted. The system
+displays this as "signature drift detected — re-scan recommended," not as a
+health diagnosis.
+
+---
+
+## 8. Output Artifact
+
+On successful completion, the enrollment pipeline produces:
+
+1. `signature-<sha256>.rvf` — the binary soul signature container. Content-addressed.
+   Encrypted with the person's key (see `security.md §5`) before writing to disk.
+
+2. `signature-<sha256>.json` — the JSON-LD sidecar for human inspection and audit.
+   Does not contain raw vector data. Safe to log.
+
+3. A row in the local HNSW index (`ruvector-core::VectorIndex`, `person_track`
+   subindex per ADR-024 §2.4) linking the person_id to the AETHER embedding.
+   This index is used for O(log n) recognition queries.
+
+4. An Ed25519 witness entry per ADR-110, signing
+   `(rvf_sha256 || timestamp_ns || enrolled_by_device_id)`. Stored in the
+   RVF SEG_WITNESS segment AND in the node's local audit log.
+
+The enrollment process does NOT:
+- Transmit raw CSI or raw biometrics to any external server.
+- Publish the soul signature to MQTT or Matter unless explicitly configured with
+  `--privacy-mode disabled` (see `security.md §6`).
+- Store PII (name, email, account linkage) in the `.rvf` file. The `person_id`
+  field is an opaque u64. PII linkage, if any, lives in the application layer
+  and is governed by separate access control.

docs/research/soul/security.md

@@ -0,0 +1,367 @@
+# Soul Signature — Security, Privacy, and Threat Model
+
+**Status:** Research Specification (Pre-Implementation)
+**Date:** 2026-05-24
+**Author:** ruv
+
+---
+
+## 1. Scope
+
+This document defines the threat model, mitigations, cryptographic primitive
+choices, privacy architecture, and open security research items for the Soul
+Signature system. It is intended to be reviewed by a security engineer or
+privacy counsel before any production deployment.
+
+The soul signature is a passive biometric system. The security bar is:
+**attacker cost to achieve a false accept must exceed the value of the
+protected resource for the relevant threat model**. The soul signature does
+not claim to be unbreakable. It claims to be hard enough.
+
+---
+
+## 2. What We Explicitly Do NOT Claim
+
+- Not equal to fingerprint scanners on FBI-tier datasets in EER terms. RF
+  biometrics are a younger discipline. No independent benchmark with the soul
+  signature's specific multi-channel fusion exists yet.
+- Not legal evidence. Passive RF biometric identification has no established
+  legal precedent in any jurisdiction.
+- Not a replacement for explicit consent in regulated contexts (healthcare,
+  employment, border control).
+- Not unbreakable under a nation-state adversary with full physical access to
+  the sensing infrastructure.
+- Not validated at scale beyond the constituent ADR baselines. The AETHER
+  channel (ADR-024) targets >80% mAP at 5 subjects; at 100+ subjects the
+  false-accept rate is open research.
+
+---
+
+## 3. Threat Model
+
+### 3.1 Attacker: Passive Eavesdropper on the WiFi Medium
+
+**Capability:** An attacker near the WiFi sensing zone can observe CSI of any
+person who passes through. With enough CSI, the attacker could construct an
+unauthorized soul signature enrollment of an unconsenting bystander.
+
+**Impact:** Unauthorized enrollment → unauthorized recognition → attribution of
+presence to a person who did not consent.
+
+**Mitigation:**
+- Ambient CSI capture does NOT trigger enrollment. Enrollment requires the
+  explicit 60-second structured protocol. Ambient bystander CSI produces
+  `unauthenticated` pose tracks tagged as `person_id: NULL`.
+- Unauthenticated RVF nodes are pruned from the HNSW index after 24 hours.
+- The enrollment protocol requires presence confirmation from at least two
+  sensing nodes simultaneously, making drive-by enrollment geometrically
+  harder to achieve without physical proximity.
+
+**Residual risk:** An attacker who can be physically present in the scanning
+zone for 60 seconds, under the observation of the scanning protocol, can cause
+enrollment of a fake person. This requires physical co-location and is
+equivalent to the threat model for any in-person biometric registration.
+
+### 3.2 Attacker: Active Replay
+
+**Capability:** An attacker records a CSI stream from a legitimate enrollment
+or recognition event and replays it to a sensing node to impersonate the
+enrolled person.
+
+**Impact:** False positive recognition; unauthorized access or presence attribution.
+
+**Mitigation:**
+- Each enrollment is bound to the room's ADR-030 field model eigenstate at
+  enrollment time. The `environment_id` field in every vector node is a
+  SHA-256 of the field model's eigenmode matrix. A replay in a different room
+  produces a different `environment_id` and a dramatically different
+  Subcarrier_Reflection_Profile — the cross-validation between these two
+  signed fields fails.
+- The Ed25519 witness chain (ADR-110) includes a monotonic timestamp
+  (`timestamp_ns`). A replay of an old signature is detected by the timestamp
+  freshness check at recognition time (configurable; default: reject any
+  signature older than 7 days for high-assurance contexts).
+- The ADR-030 field model continuously updates. Even if the replay is in the
+  same room, the field model's eigenstate changes as furniture is moved or
+  temperature shifts the propagation medium; cross-validation degrades over
+  time.
+
+**Residual risk:** Replay within the same room within a short time window
+(< 4 hours, before the field model rotates) by an attacker who has recorded the
+original CSI with high fidelity remains a plausible attack vector. This is not
+defended against by the current architecture. It requires a future ADR for
+challenge-response liveness detection.
+
+### 3.3 Attacker: Phased-Array Vest / RF Body Emulator
+
+**Capability:** An attacker wears a device capable of emitting RF signals that
+mimic another person's backscatter profile, allowing them to be recognized as
+the enrolled person.
+
+**Impact:** The strongest impersonation attack; if successful, bypasses all
+electromagnetic biometric channels simultaneously.
+
+**Mitigation:**
+- The RuvSense `adversarial.rs` module (ADR-030 Tier 7) enforces four
+  physics-based consistency checks:
+  1. Multi-link consistency: a real body perturbs all mesh links passing
+     through its location. A vest emitting signals affects only the targeted
+     link(s). Detection: at least 4 links must show correlated perturbation.
+  2. Field model constraints: the perturbation must lie within the span of
+     the room's eigenmode structure. Artificially injected signals produce
+     perturbations inconsistent with room geometry.
+  3. Temporal continuity: real movement is smooth in embedding space; injected
+     signals can produce discontinuities flagged by the embedding velocity
+     monitor.
+  4. Energy conservation: total perturbation energy across all links must be
+     consistent with the number and geometry of bodies present.
+- The adversarial detector fires `FAIL_ADVERSARIAL_SIGNAL` before the soul
+  signature match is considered.
+
+**Residual risk:** A sophisticated attacker with a calibrated phased-array
+system who also knows the room's eigenmode structure and the enrolled person's
+exact multi-link backscatter pattern could in principle construct a convincing
+emulation. This is a high-capability, high-cost attack. Practical countermeasure:
+require multi-node confirmation (ADR-029 multistatic) which raises the
+geometric complexity of the emulation exponentially with node count.
+
+### 3.4 Attacker: Insider with Broker Access
+
+**Capability:** A privileged operator or compromised service with read access
+to the stored `.rvf` files and the HNSW person_track index.
+
+**Impact:** Exfiltration of biometric signatures; linkage of person_id to PII
+if linkage tables also accessible; replay or cross-site re-enrollment.
+
+**Mitigation:**
+- At-rest encryption: all `.rvf` files are encrypted with ChaCha20-Poly1305
+  using a key derived via Argon2id from a user-provided passphrase (or a FIDO2
+  hardware token binding). The Cognitum Seed appliance NEVER stores the
+  decryption key; it is re-derived from the passphrase on each access.
+- The opaque `person_id` (u64) in the `.rvf` file is not PII. PII linkage, if
+  any, requires access to a separate application-layer database not stored on
+  the sensing appliance.
+- The HNSW index stores only the 128-dim AETHER embedding, not raw CSI or full
+  soul signatures. Exfiltration of the index exposes the embedding but not the
+  full biometric record.
+- Differential privacy (ADR-106 DP-SGD) applies at training time when AETHER
+  is fine-tuned on enrolled-person data, preventing membership inference attacks
+  that could recover training samples from model weights.
+
+**Residual risk:** If the passphrase is weak or the FIDO2 token is compromised,
+the at-rest encryption fails. Key management is a deployment responsibility.
+
+### 3.5 Attacker: Manufacturer / Firmware Supply Chain
+
+**Capability:** A malicious firmware update to the ESP32 node or Cognitum Seed
+appliance could silently exfiltrate soul signatures or CSI streams.
+
+**Impact:** Large-scale passive surveillance; biometric data exfiltration across
+all installed appliances.
+
+**Mitigation:**
+- All firmware releases are signed with Ed25519 (ADR-100 cog packaging) and
+  verified by the appliance before installation. A Dilithium-3 post-quantum
+  co-signature is added in the transition window (ADR-109).
+- The Ed25519 witness chain (ADR-110) signs each CSI frame bundle at the
+  sensor level. A firmware change that alters the witness chain is detectable
+  by downstream audit.
+- Network egress from the Cognitum Seed in `--privacy-mode` is blocked for
+  raw CSI and soul signatures by default. Only MQTT auto-discovery messages
+  (ADR-115) and OTA metadata are permitted outbound.
+- Open-source firmware. The ESP32 firmware and Cognitum Seed Rust crates are
+  open source (this repository). Independent audit is possible.
+
+**Residual risk:** A zero-day exploit in the ESP-IDF WiFi stack or the Rust
+codebase could bypass these controls. This is mitigated by regular security
+audits (run `npx @claude-flow/cli@latest security scan` per CLAUDE.md) but not
+eliminated.
+
+---
+
+## 4. Consent Architecture
+
+### 4.1 The Enrollment-vs-Recognition Distinction
+
+The soul signature system enforces a hard distinction:
+
+| Action | Consent required | Mechanism |
+|---|---|---|
+| Enrollment | Explicit, active | 60-second protocol with operator confirmation; produces signed `.rvf` |
+| Recognition of enrolled person | Implicit (enrollment = consent for recognition) | Continuous mode; HNSW match |
+| Ambient sensing of unenrolled person | No — but data is transient and pruned | Unauthenticated tracks; 24h TTL |
+| Updating stored profile from continuous mode | Implicit (set at enrollment time) | Aggregator auto-refresh; configurable |
+
+The system operator is responsible for obtaining appropriate consent from
+persons before performing enrollment. The technical system enforces that
+enrollment cannot happen accidentally or from drive-by sensing.
+
+### 4.2 Bystander Protection
+
+Persons who pass through a sensing zone without being enrolled are sensed but
+not persistently identified. Their data flow:
+1. Pose tracker produces a track tagged `person_id: NULL`.
+2. AETHER embedding is computed for motion detection and occupancy counting
+   (ADR-115 HA-MIND).
+3. The embedding is written to the `temporal_baseline` HNSW index with a 24-hour
+   TTL and `authenticated: false`.
+4. After 24 hours, the entry is automatically pruned by the `EmbeddingIndex::prune()`
+   method (ADR-024 §2.4).
+5. No `.rvf` file is created. No persistent record exists.
+
+This architecture satisfies the GDPR principle of data minimization (Article 5(1)(c))
+for bystander data: the retention period is bounded, the data is not linked to
+an identity, and the storage is proportionate to the functional purpose
+(occupancy counting).
+
+### 4.3 GDPR / HIPAA Mode
+
+When `--privacy-mode enabled` (from ADR-115 HA-MIND §privacy):
+
+1. Soul signatures are computed and stored locally only. They are NEVER
+   published to MQTT topics, Matter clusters, or any external endpoint.
+2. The local REST API for accessing soul signatures requires a valid bearer
+   token (ADR-028 bearer_auth.rs). No unauthenticated endpoint exposes
+   biometric data.
+3. The JSON-LD sidecar is written to the local encrypted store only. It is not
+   included in MQTT auto-discovery payloads.
+4. The longitudinal drift metrics (ADR-030 Tier 4) are published to MQTT in
+   aggregated form only (e.g., `drift_detected: true`, never raw metric values
+   that could be used for medical inference).
+5. A data deletion endpoint must be implemented: `DELETE /api/v1/persons/{id}`
+   removes the `.rvf` file, the HNSW index entry, the JSON-LD sidecar, and all
+   longitudinal Welford statistics for that person_id.
+
+---
+
+## 5. Cryptographic Primitives
+
+All primitives are chosen from NIST-approved or widely-audited standards.
+
+| Purpose | Primitive | Rationale |
+|---|---|---|
+| Content integrity (per-segment) | CRC32 (IEEE 802.3) | Already implemented in `rvf_container.rs:line 70`. Corruption detection, not security. |
+| Content addressing | SHA-256 | File name derivation; pre-image resistance prevents name collisions |
+| Ed25519 signatures | Ed25519 (RFC 8032) | ADR-110 witness chain; 64-byte signatures; 128-bit security |
+| At-rest encryption | ChaCha20-Poly1305 (RFC 8439) | AEAD; software-friendly; no timing-attack surface like AES-CBC; 256-bit key |
+| Key derivation from passphrase | Argon2id (RFC 9106) | Memory-hard KDF; resistant to GPU/ASIC brute-force; recommended by NIST SP 800-132 draft (2024) |
+| DP-SGD noise | Gaussian N(0, σ²C²I) per ADR-106 | (ε, δ)-DP per Abadi et al. 2016 Moments Accountant |
+| Post-quantum key exchange (future) | Kyber-768 (NIST FIPS 203, 2024) | ADR-108; ~AES-192 security; NIST CNSA 2.0 recommended |
+| Post-quantum signatures (future) | Dilithium-3 (NIST FIPS 204, 2024) | ADR-109; hybrid mode with Ed25519 during transition window |
+
+### 5.1 Argon2id Parameters
+
+Default parameters for soul signature key derivation:
+
+```
+m_cost = 65536 (64 MB memory)
+t_cost = 3     (3 iterations)
+p_cost = 4     (4 parallel lanes)
+output_len = 32 bytes (256-bit key for ChaCha20-Poly1305)
+salt = 16 random bytes stored alongside encrypted blob (NOT the person_id)
+```
+
+These parameters provide ~100ms KDF time on a Pi 5, which is acceptable for
+enrollment (one-time) and recognition (HNSW match precedes decryption, so
+decryption is only triggered after a candidate match).
+
+### 5.2 Forward Secrecy
+
+Old soul signature files are NOT keys for new ones. Compromise of a 90-day-old
+`.rvf` file does not unlock the current profile. The key is derived from the
+user's passphrase each time, not derived from the previous file.
+
+Archived files (kept for audit purposes) are re-encrypted on passphrase rotation
+if the operator elects to do so via the `soul-signature re-encrypt --all` CLI
+command (not yet implemented; specified here for future ADR).
+
+---
+
+## 6. Privacy Mode Integration (ADR-115)
+
+The `--privacy-mode` flag defined in ADR-115 HA-MIND §9 is extended to cover
+soul signature data:
+
+| Privacy mode | MQTT publish | REST API | Local storage | HNSW index |
+|---|---|---|---|---|
+| `disabled` (default for home users) | Aggregated presence/count only | Authenticated bearer required | Encrypted at rest | Local only |
+| `enabled` | Nothing biometric | Authenticated bearer required | Encrypted at rest | Local only |
+| `research` (explicit opt-in) | Full soul signature nodes (anonymized person_id) | Open (for research deployments only) | Encrypted at rest | Exportable |
+
+The `research` mode requires a separate `--research-consent-token` flag and is
+intended for academic data collection under IRB approval. It must never be the
+default.
+
+---
+
+## 7. Open Research and Outstanding Security Work
+
+The following items are known security gaps or open research questions. Each
+warrants a future ADR before production deployment at scale.
+
+**7.1 Challenge-Response Liveness Detection**
+Replay attacks within a short time window (see §3.2 residual risk) are not
+defended against. A future mechanism should issue a random challenge (e.g.,
+"please raise your left hand") and verify the CSI response matches the challenge
+before accepting a recognition. This eliminates replay as a practical attack
+vector. Future ADR: ADR-120 (proposed).
+
+**7.2 False-Accept Rate at Scale (N > 20 subjects)**
+The AETHER baseline (ADR-024) is tested at 5 subjects (>80% mAP). For household
+deployments this is sufficient. For building-scale deployments (50-500 subjects),
+the FAR is open research. Independent benchmarking on a dataset of 20+ subjects
+with the full 7-channel fusion is required before building-scale deployment can
+be recommended. Publication target: co-locate with ADR-027 MERIDIAN evaluation.
+
+**7.3 Side-Channel Leakage from Encrypted RVF Files**
+The file size of an encrypted `.rvf` blob is observable by an attacker with
+filesystem access. File size is a function of the number of nodes present, which
+reveals whether the cardiac channel was captured (high-SNR enrollment vs
+low-SNR enrollment). This is a minor information leak. Mitigation: pad all
+`.rvf` files to a fixed 64 KB boundary. Future ADR: append to ADR-106.
+
+**7.4 Membership Inference in Continuous Mode**
+In continuous mode, the AETHER model is fine-tuned on the enrolled person's
+data over months. An adversary with access to the model weights before and after
+a re-train cycle could infer that a specific enrollment occurred, even without
+the soul signature file, via membership inference (Shokri et al. 2017).
+ADR-106 DP-SGD mitigates this for federation round deltas but not for local
+single-device fine-tuning. Extension of DP-SGD to the local continuous-mode
+update is required. Future ADR: extend ADR-106.
+
+**7.5 Physical Access to Sensing Nodes**
+An attacker with physical access to an ESP32 node can extract the firmware and
+attempt to reverse the Ed25519 signing key (if the key is stored in ESP32
+NVS without protection). ADR-110 uses NVS for key storage. A future ADR should
+mandate secure element storage (e.g., ATECC608A co-processor on the Cognitum
+Seed) for the signing key. Future ADR: ADR-121 (proposed).
+
+**7.6 Federated Learning Linkability**
+When AETHER is retrained via federated learning (ADR-105), the LoRA weight
+deltas carry information about enrolled persons. ADR-106 applies DP-SGD to
+these deltas, but the post-quantum migration path (ADR-108 Kyber-768) is not
+yet integrated with the federation protocol. Until ADR-108 Phase 2 ships, the
+federation link is classically encrypted and vulnerable to harvest-now-decrypt-later
+attacks by quantum-capable adversaries. Assessed risk: low until 2027.
+
+---
+
+## 8. Summary Security Properties Table
+
+| Property | Status | Evidence |
+|---|---|---|
+| At-rest encryption | Specified (ChaCha20-Poly1305 + Argon2id) | This document §5 |
+| Ed25519 attestation | Implemented | ADR-110 witness chain |
+| Replay resistance (cross-room) | Implemented | ADR-030 field model environment_id binding |
+| Replay resistance (same-room, short window) | Open gap | §7.1 |
+| Anti-spoofing (single-link injection) | Implemented | adversarial.rs multi-link consistency |
+| Anti-spoofing (phased-array vest) | Partial | adversarial.rs + energy conservation; residual risk documented |
+| Bystander protection | Specified | 24h TTL on unauthenticated tracks; §4.2 |
+| DP-SGD training privacy | Implemented (federation) | ADR-106 |
+| DP-SGD training privacy (local continuous mode) | Open gap | §7.4 |
+| GDPR data deletion | Specified | §4.3 `DELETE /api/v1/persons/{id}` |
+| Post-quantum migration path | Specified (Kyber-768, Dilithium-3) | ADR-108, ADR-109 |
+| Firmware supply chain integrity | Implemented (Ed25519 cog signing) | ADR-100, ADR-109 hybrid |
+| False-accept rate at scale | Open research | §7.2 |
+| Liveness detection | Open gap | §7.1 |
+| Secure element key storage | Open gap | §7.5 |

docs/research/soul/specification.md

@@ -0,0 +1,525 @@
+# Soul Signature — Technical Specification
+
+**Status:** Research Specification (Pre-Implementation)
+**Date:** 2026-05-24
+**Author:** ruv
+
+---
+
+## 1. Overview
+
+A Soul Signature is a typed, content-addressed RVF graph encoding seven
+electromagnetic observables extracted from a person in a WiFi-DensePose sensing
+zone. The graph is stored as a single `.rvf` binary blob using the existing RVF
+container format (`v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs`)
+extended with two new segment types defined below. A human-readable JSON sidecar
+accompanies the blob for inspection and provenance.
+
+The signature is probabilistic, not deterministic. Matching computes a weighted
+cosine similarity across graph dimensions, producing a score in [0, 1] with a
+calibrated false-accept rate (FAR). The FAR at a given threshold is an open
+research question; the AETHER person re-identification baseline (ADR-024 §2.8:
+>80% mAP at 5 subjects) is the lower bound for the primary embedding channel.
+
+---
+
+## 2. Design Principles
+
+### 2.1 Per-Individual
+
+The signature encodes features that are structurally unique to one person at the
+sensing resolution of commodity WiFi hardware. Discriminative dimensions include:
+cardiac timing (R-R interval structure), respiratory mechanics (tidal depth,
+inspiration-to-expiration ratio), skeletal proportions (limb ratios from 17-keypoint
+pose, ADR-079), gait cadence variability, and the RF backscatter profile shaped by
+body mass distribution and geometry.
+
+### 2.2 Passive at Enrollment Time
+
+No explicit action from the subject is required at recognition time after
+enrollment. Recognition fires whenever an enrolled person is detected in a sensing
+zone. Enrollment itself requires a 60-second structured protocol (see
+`scanning-process.md`). This is a deliberate asymmetry: passive recognition +
+active enrollment — which is the same model used by FaceID (passive unlock after
+initial face setup).
+
+The passivity of post-enrollment recognition is a privacy concern addressed in full
+in `security.md` §4.
+
+### 2.3 Multi-Modal
+
+Seven orthogonal channels contribute. Orthogonality matters: if one channel
+degrades (e.g., cardiac is masked by motion), the remaining six carry the match.
+No single channel is necessary for a positive identification above threshold;
+the fused score is a weighted aggregate.
+
+### 2.4 Persistent Across Time
+
+The stored signature is valid over weeks to months for adults with stable anatomy
+and health. Re-scan cadence is prescribed in `scanning-process.md`. The
+`longitudinal.rs` module (ADR-030 Tier 4) provides the drift detection that
+flags when a re-scan is necessary.
+
+### 2.5 Defensible False-Accept Rate
+
+The security model is not "unbreakable." It is "attacker cost exceeds value of
+attack for the threat model in §security." See `security.md` §3.
+
+---
+
+## 3. Signature as a Typed RVF Graph
+
+### 3.1 Container Format
+
+The soul signature reuses the RVF binary container defined in
+`v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs` (lines 1–660).
+Existing segment types used:
+
+| Segment type | Const | Purpose in soul signature |
+|---|---|---|
+| `SEG_MANIFEST` | `0x05` | Graph metadata: schema version, enroll timestamp, device ID, person_id (opaque u64) |
+| `SEG_VEC` | `0x01` | AETHER 128-dim embedding weights (backbone + projection head) |
+| `SEG_META` | `0x07` | JSON overlay: all non-vector node attributes |
+| `SEG_WITNESS` | `0x0A` | Ed25519 signature over `(content_hash_sha256 || timestamp_ns || enrolled_by_device_id)` |
+| `SEG_EMBED` | `0x0C` | AETHER embedding config + projection head weights (ADR-024 Phase 7) |
+| `SEG_LORA` | `0x0D` | Per-environment LoRA deltas for environment-adapted query |
+
+Two new segment types are proposed for the soul signature extension:
+
+| Segment type | Const | Purpose |
+|---|---|---|
+| `SEG_SOUL_GRAPH` | `0x10` | JSON-serialized graph: node list + edge list + attribute schemas |
+| `SEG_SOUL_INDEX` | `0x11` | Per-node HNSW index serialization for fast graph-level query |
+
+The `SegmentHeader` structure is unchanged. Each segment is 64-byte aligned
+(field `alignment_pad` at offset `0x3C`). CRC32 content hash at offset `0x28`
+covers the payload, providing tamper detection per the existing implementation
+at `rvf_container.rs:line 70`.
+
+### 3.2 Node Types
+
+Each node is a typed struct. Serialized into SEG_META as a JSON object with a
+`node_type` discriminator string. Vector fields (f32 arrays) are co-located in
+a SEG_VEC segment indexed by the node's `vec_segment_id` field.
+
+#### Node: AETHER_Embedding
+
+Primary identity anchor. The contrastive CSI embedding from ADR-024.
+
+```rust
+pub struct AetherEmbeddingNode {
+    pub node_type: &'static str,        // "AETHER_Embedding"
+    pub vec_segment_id: u64,            // references SEG_VEC containing 128 f32s
+    pub embedding_dim: usize,           // 128
+    pub backbone: String,               // "csi-to-pose-transformer"
+    pub pretrain_method: String,        // "simclr+vicreg"
+    pub alignment_score: f32,           // Lowman alignment metric at enrollment time
+    pub uniformity_score: f32,          // Hypersphere uniformity at enrollment time
+    pub enrollment_frames: u32,         // Number of CSI windows averaged into this node
+    pub environment_id: String,         // SHA-256 of field model eigenstate at enrollment
+    pub confidence: f32,                // HNSW search confidence against person_track index
+}
+```
+
+Stored size: 128 × 4 = 512 bytes in SEG_VEC; JSON metadata ~200 bytes in SEG_META.
+Per ADR-024 §2.8, the person re-identification target is >80% mAP at 5 subjects.
+At 10+ subjects the accuracy is open research; baseline TBD.
+
+#### Node: Cardiac_HR_Profile
+
+Extracted from the ADR-039 vitals pipeline (magic `0xC511_0002`, fields offset 6-11:
+breathing_rate at `u16 LE` BPM×100, heart_rate at `u32 LE` BPM×10000).
+For the soul signature, cardiac extraction uses the ADR-021 bandpass pipeline
+(0.8–2.0 Hz) over a minimum 30-second rest window.
+
+```rust
+pub struct CardiacHRProfileNode {
+    pub node_type: &'static str,        // "Cardiac_HR_Profile"
+    pub baseline_bpm: f32,              // mean HR over enrollment window (40–180 BPM range)
+    pub hrv_sdnn_ms: f32,               // SDNN: std dev of R-R intervals (ms)
+    pub hrv_rmssd_ms: f32,              // RMSSD: root mean square successive differences
+    pub hrv_lf_power: f32,              // LF band power (0.04–0.15 Hz), normalized
+    pub hrv_hf_power: f32,              // HF band power (0.15–0.4 Hz), normalized
+    pub hrv_lf_hf_ratio: f32,           // LF/HF ratio (autonomic balance marker)
+    pub sinus_rhythm_class: u8,         // 0=regular, 1=irregular, 2=indeterminate
+    pub confidence: f32,                // from ADR-021 VitalCoherenceGate PERMIT fraction
+    pub window_seconds: u32,            // duration of the measurement window
+}
+```
+
+WiFi CSI-based HRV extraction is an active research area. The SDNN and RMSSD values
+are discriminative at group level (Zhao et al. 2017, Widar 3.0 2019) but per-person
+uniqueness has not been independently validated at scale. Status: open research.
+
+#### Node: Cardiac_Waveform_Morphology
+
+Wavelet decomposition of the bandpass-filtered cardiac phase signal. Captures the
+shape of the cardiac waveform, not just its rate. More discriminative than HR alone
+but requires higher SNR and longer measurement window.
+
+```rust
+pub struct CardiacWaveformMorphologyNode {
+    pub node_type: &'static str,        // "Cardiac_Waveform_Morphology"
+    pub vec_segment_id: u64,            // references SEG_VEC: 64 f32 wavelet coefficients
+    pub wavelet_family: String,         // "db4" (Daubechies 4, standard for cardiac)
+    pub decomposition_levels: u8,       // 4 levels
+    pub snr_db: f32,                    // measured SNR at enrollment; low-SNR nodes down-weighted
+    pub confidence: f32,
+}
+```
+
+Wavelet coefficient dimension: 64 floats = 256 bytes in SEG_VEC. Waveform
+morphology from CSI is highly environment-dependent; the ADR-030 field model
+subtraction must run before this measurement is taken to isolate body perturbation
+from room standing-wave artifacts.
+
+#### Node: Respiratory_Pattern
+
+Extracted by the ADR-021 BreathingExtractor (0.1–0.5 Hz bandpass) plus the
+ADR-030 persistence layer that accumulates statistics over the enrollment window.
+
+```rust
+pub struct RespiratoryPatternNode {
+    pub node_type: &'static str,        // "Respiratory_Pattern"
+    pub baseline_bpm: f32,              // mean RR (normal adult: 12–20 BPM)
+    pub depth_amplitude_normalized: f32, // tidal depth proxy from CSI variance
+    pub inspiration_expiration_ratio: f32, // I:E ratio (1:1.5 to 1:3 typical)
+    pub hrv_rsa_power: f32,             // respiratory sinus arrhythmia spectral power
+    pub apnea_index: f32,               // events per hour of significant pauses
+    pub waveform_regularity: f32,       // coefficient of variation of breath intervals
+    pub confidence: f32,
+    pub window_seconds: u32,
+}
+```
+
+Note: the `apnea_index` field is a biophysical proxy signal (pause events in
+the signal), not a clinical AHI score. It is provided for signature
+discriminability, not diagnostic use.
+
+#### Node: Gait_Timing
+
+Extracted from the 17-keypoint Kalman pose tracker (`pose_tracker.rs`, ADR-029
+Sect 2.7) during the gait phase of the enrollment protocol. The tracker uses
+ruvector-mincut for person separation and AETHER re-ID for identity continuity.
+
+```rust
+pub struct GaitTimingNode {
+    pub node_type: &'static str,        // "Gait_Timing"
+    pub cadence_steps_per_min: f32,     // steps per minute
+    pub stride_period_variance: f32,    // coefficient of variation of stride period
+    pub double_support_pct: f32,        // fraction of gait cycle in double support
+    pub asymmetry_index: f32,           // |left_stride - right_stride| / mean_stride
+    pub step_width_m: f32,              // lateral distance between foot strikes (proxy)
+    pub velocity_variance: f32,         // gait speed variability
+    pub confidence: f32,
+    pub stride_count: u32,              // number of strides captured during enrollment
+}
+```
+
+Gait biometrics from WiFi CSI are documented in WiGait (Adib et al., SIGCOMM
+2015) and WiDraw (Wang et al., MobiCom 2014). Discrimination across 10+ subjects
+in the same household is an open research question for the WiFi-only modality.
+
+#### Node: Skeletal_Proportions
+
+Derived from the ADR-079 camera + CSI paired keypoint pipeline when available,
+or from CSI-only pose estimation (ADR-023 CsiToPoseTransformer) in camera-free
+deployments. Encodes body geometry as ratios (not absolute values) for scale
+invariance.
+
+```rust
+pub struct SkeletalProportionsNode {
+    pub node_type: &'static str,        // "Skeletal_Proportions"
+    pub torso_to_leg_ratio: f32,        // torso height / leg length
+    pub shoulder_to_hip_ratio: f32,     // shoulder width / hip width
+    pub upper_to_lower_arm_ratio: f32,  // upper arm / forearm
+    pub upper_to_lower_leg_ratio: f32,  // thigh / shin
+    pub head_to_torso_ratio: f32,       // head height / torso height
+    pub arm_span_to_height_ratio: f32,  // Vitruvian ratio (close to 1.0 for most adults)
+    pub confidence: f32,
+    pub keypoint_source: String,        // "camera_paired" | "csi_only" | "fused"
+}
+```
+
+CSI-only skeletal proportion estimation has ~15–25% error on individual ratio
+values (open research; baseline from ADR-023 MPJPE ~91.7 mm at best, per
+Person-in-WiFi 3D, CVPR 2024). Camera-paired values (ADR-079) are substantially
+more accurate. The node degrades gracefully when only CSI is available.
+
+#### Node: Subcarrier_Reflection_Profile
+
+The per-subcarrier amplitude attenuation and phase shift profile measured when
+the subject stands still at three orientations (0°, 90°, 180° rotation). This
+encodes the body's RF backscatter cross-section shape, which is determined by
+body mass distribution, limb geometry, and clothing/material factors.
+
+```rust
+pub struct SubcarrierReflectionProfileNode {
+    pub node_type: &'static str,        // "Subcarrier_Reflection_Profile"
+    pub vec_segment_id: u64,            // SEG_VEC: 56 × 3 × 2 = 336 f32s
+                                        // (56 subcarriers × 3 orientations ×
+                                        //  [amplitude_attenuation, phase_shift])
+    pub n_subcarriers: u8,              // 56 (HT-LTF) or up to 242 (HE-LTF, ADR-110 C6)
+    pub n_orientations: u8,             // 3
+    pub frequency_mhz: u32,             // center frequency at measurement time
+    pub environment_id: String,         // references field model used for subtraction
+    pub confidence: f32,
+}
+```
+
+This node directly exploits the ADR-030 field model: the empty-room baseline
+eigenstate is subtracted before computing the reflection profile, isolating the
+person's contribution. Without ADR-030 field subtraction, the profile is too
+environment-coupled to be transferable across rooms. With MERIDIAN (ADR-027),
+the hardware-normalizer layer maps ESP32-S3 (52 subcarriers HT-LTF) and
+ESP32-C6 (242 subcarriers HE-LTF per ADR-110) into a canonical 56-subcarrier
+representation before this measurement.
+
+Stored: 336 × 4 = 1,344 bytes in SEG_VEC.
+
+#### Node: Body_Field_Coupling
+
+The AETHER attention map cells weighted by the ADR-030 room eigenmode structure.
+Encodes how strongly the person's body couples to each dominant electromagnetic
+mode of the room. This is the most physics-grounded node: it captures the
+person's interaction with the actual electromagnetic geometry of the space.
+
+```rust
+pub struct BodyFieldCouplingNode {
+    pub node_type: &'static str,        // "Body_Field_Coupling"
+    pub vec_segment_id: u64,            // SEG_VEC: n_eigenmodes × n_keypoints f32s
+    pub n_eigenmodes: u8,               // top-K SVD modes from field_model.rs (default K=8)
+    pub n_keypoints: u8,                // 17 (COCO)
+    pub eigenmode_energy_fractions: Vec<f32>, // fraction of total variance per mode
+    pub environment_id: String,         // must match SubcarrierReflectionProfile env
+    pub confidence: f32,
+}
+```
+
+This node is only valid when the same room's field model is available. For
+cross-room recognition, MERIDIAN's environment-disentangled embedding (ADR-027)
+is used instead. The BodyFieldCoupling node provides additional discriminative
+power in single-room deployments and degrades to optional in multi-room contexts.
+
+---
+
+### 3.3 Edge Types
+
+Edges are stored in the SEG_SOUL_GRAPH JSON array. Each edge has a typed
+relationship that constrains how the nodes may be used in matching.
+
+| Edge type | Source node(s) | Target node(s) | Semantics |
+|---|---|---|---|
+| `derived_from` | FieldModel_Residual (implicit) | AetherEmbedding | The embedding was computed after field model subtraction |
+| `correlates_with` | Cardiac_HR_Profile | Respiratory_Pattern | Cardiorespiratory coupling at measurement time; correlation coefficient stored as edge weight |
+| `temporally_colocated` | Any pair | Any pair | Both nodes were measured in the same time window; ensures consistency |
+| `temporally_after` | Post-gait node | Pre-gait node | Nodes acquired sequentially during enrollment protocol |
+| `requires_field_model` | SubcarrierReflectionProfile | BodyFieldCoupling | Matching this node requires the same room's ADR-030 field model |
+| `fuses` | AetherEmbedding | SubcarrierReflectionProfile | MERIDIAN-normalized fusion: both mapped to environment-invariant space |
+| `attested_by` | Any leaf node | WitnessChain | Ed25519 witness covers this node's content hash |
+| `derived_by_keypoint_tracker` | GaitTiming | SkeletalProportions | Both extracted from the same pose_tracker.rs output |
+| `environment_normalized` | Any node with `environment_id` | MERIDIAN manifest | MERIDIAN (ADR-027) was applied; signature is cross-room capable |
+
+---
+
+### 3.4 The Aggregator vs. the Stored Profile
+
+Two distinct graph instances exist in the runtime:
+
+**Online Aggregator** — a mutable, in-memory graph that accumulates measurements
+across multiple sensing windows. Nodes are incrementally updated with Welford
+online statistics (`field_model.rs::WelfordStats`). Confidence fields grow toward
+1.0 as more frames accumulate. The aggregator never writes to disk during
+normal operation.
+
+**Stored Profile** — an immutable, content-addressed `.rvf` file on disk. It is
+generated from the aggregator at the end of the enrollment protocol, when all node
+confidence fields exceed their minimum thresholds. The stored profile is the
+canonical soul signature.
+
+```
+Online Aggregator (RAM)                Stored Profile (disk / secure enclave)
++----------------------+               +---------------------------+
+| AETHER_Embedding     |  enrollment   | signature-<sha256>.rvf    |
+| accumulated over     |  completion   | SEG_MANIFEST              |
+| 60-second protocol   +-------------> | SEG_VEC (embedding + refl)|
+| Confidence: 0.0→1.0  |  when all     | SEG_META (all node attrs) |
+|                      |  gates pass   | SEG_EMBED (AETHER config) |
+| Cardiac_HR_Profile   |               | SEG_WITNESS (Ed25519)     |
+| accumulated 30s rest |               | SEG_SOUL_GRAPH (graph)    |
++----------------------+               +---------------------------+
+```
+
+The aggregator pattern ensures that a partial scan (e.g., subject leaves after
+20 seconds) never produces a stored profile — the quality gates prevent premature
+commitment (see `scanning-process.md §5`).
+
+---
+
+### 3.5 Serialization
+
+**Binary container:** RVF blob, per `rvf_container.rs`. All numeric data is
+little-endian, f32 IEEE 754. Segment alignment: 64 bytes. CRC32 (IEEE 802.3
+polynomial) over each segment payload.
+
+**Content addressing:** The file name is:
+```
+signature-<sha256-hex-of-rvf-bytes>.rvf
+```
+SHA-256 is computed over the complete concatenated RVF byte stream after
+`RvfBuilder::build()`. This is a different hash from the per-segment CRC32;
+the CRC32 provides corruption detection within segments, the SHA-256 provides
+content-based addressing and enables deduplication.
+
+**JSON-LD sidecar:** An optional `signature-<sha256>.json` file with the same
+base name. Structure:
+
+```json
+{
+  "@context": "https://ruv.net/soul-signature/v1",
+  "schema_version": "0.1.0",
+  "person_id": "<opaque_u64_hex>",
+  "enrolled_at": "2026-05-24T00:00:00Z",
+  "enrolled_by_device_id": "<mac_or_device_fingerprint>",
+  "rvf_sha256": "<content_hash>",
+  "nodes": [
+    { "node_type": "AETHER_Embedding", "confidence": 0.92, ... },
+    { "node_type": "Cardiac_HR_Profile", "confidence": 0.85, ... },
+    ...
+  ],
+  "edges": [...],
+  "witness": {
+    "algorithm": "Ed25519",
+    "public_key": "<hex>",
+    "signature": "<hex>",
+    "signed_fields": ["rvf_sha256", "enrolled_at", "enrolled_by_device_id"]
+  }
+}
+```
+
+The JSON-LD sidecar is human-readable and intended for audit and provenance.
+It does not contain raw biometric vectors; those stay in the RVF blob.
+
+**ISO/IEC 19794-4 alignment:** The soul signature's graph-based vector template
+is conceptually analogous to the ISO/IEC 19794-4 finger image data format
+and ISO/IEC 19794-2 minutiae data. The node/edge schema is not binary-compatible
+with ISO 19794, but the design intent (typed attribute records, quality scores,
+creator provenance) follows the same standard's principles. Future work may
+include a conformance layer if regulatory certification is sought.
+
+---
+
+### 3.6 Matching Algorithm
+
+Given a stored profile `P` and a query embedding `Q` derived from a live sensing
+window, the match score is computed as a weighted sum of per-channel cosine
+similarities:
+
+```
+match_score = sum_i ( w_i * cosine_sim(P.channel_i, Q.channel_i) )
+               / sum_i ( w_i * availability(P.channel_i, Q.channel_i) )
+```
+
+Where `availability` is 1.0 if both nodes are present and 0.0 if either is absent
+(graceful degradation when a channel cannot be measured in the query window).
+
+Default weights (open research; these are design intent, not validated):
+
+| Channel | Weight | Rationale |
+|---|---|---|
+| AETHER_Embedding | 0.35 | Primary identity anchor; best-studied channel |
+| Subcarrier_Reflection_Profile | 0.20 | Body geometry; angle-stable |
+| Cardiac_HR_Profile | 0.15 | Physiologically stable in healthy adults |
+| Gait_Timing | 0.15 | Well-studied biometric; discriminative |
+| Respiratory_Pattern | 0.10 | More variable than cardiac |
+| Skeletal_Proportions | 0.05 | Proxy for body shape; CSI-only is noisy |
+| Body_Field_Coupling | 0.00 (single-room) / 0.10 (cross-room disabled) | Valid only when room field model available |
+| Cardiac_Waveform_Morphology | 0.05 (supplementary) | High SNR requirement |
+
+The threshold for a positive match is a deployment-specific parameter with a
+documented FAR/FRR trade-off. The AETHER channel alone achieves >80% mAP at 5
+subjects (ADR-024 §2.8 target). The fused multi-channel score is expected to
+exceed this; the exact improvement is open research, baseline TBD.
+
+---
+
+### 3.7 Rust Type Sketch
+
+The following sketch shows how the soul signature types would integrate with
+the existing codebase. This is a design sketch, not implemented code.
+
+```rust
+// In a future: v2/crates/wifi-densepose-sensing-server/src/soul_signature.rs
+
+pub const SEG_SOUL_GRAPH: u8 = 0x10;
+pub const SEG_SOUL_INDEX: u8 = 0x11;
+
+/// Complete soul signature as a graph container.
+pub struct SoulSignature {
+    /// Content-addressed identifier: SHA-256 of the RVF blob bytes.
+    pub content_hash: [u8; 32],
+    /// Opaque person identifier (never PII directly).
+    pub person_id: u64,
+    /// Unix timestamp of enrollment completion (nanoseconds).
+    pub enrolled_at_ns: u64,
+    /// Device that performed enrollment.
+    pub enrolled_by_device_id: String,
+    /// All graph nodes, typed.
+    pub nodes: SoulNodes,
+    /// All graph edges.
+    pub edges: Vec<SoulEdge>,
+    /// Ed25519 witness chain (per ADR-110).
+    pub witness: WitnessChain,
+}
+
+pub struct SoulNodes {
+    pub aether_embedding: Option<AetherEmbeddingNode>,
+    pub cardiac_hr: Option<CardiacHRProfileNode>,
+    pub cardiac_waveform: Option<CardiacWaveformMorphologyNode>,
+    pub respiratory: Option<RespiratoryPatternNode>,
+    pub gait_timing: Option<GaitTimingNode>,
+    pub skeletal_proportions: Option<SkeletalProportionsNode>,
+    pub subcarrier_reflection: Option<SubcarrierReflectionProfileNode>,
+    pub body_field_coupling: Option<BodyFieldCouplingNode>,
+}
+
+pub struct SoulEdge {
+    pub edge_type: SoulEdgeType,
+    pub source_node_type: String,
+    pub target_node_type: String,
+    pub weight: f32, // edge attribute (e.g., correlation coefficient)
+}
+
+pub enum SoulEdgeType {
+    DerivedFrom,
+    CorrelatesWith,
+    TemporallyColocated,
+    TemporallyAfter,
+    RequiresFieldModel,
+    Fuses,
+    AttestedBy,
+    DerivedByKeypointTracker,
+    EnvironmentNormalized,
+}
+
+impl SoulSignature {
+    /// Serialize to an RVF binary blob.
+    pub fn to_rvf(&self) -> Vec<u8>;
+    /// Deserialize from an RVF binary blob.
+    pub fn from_rvf(data: &[u8]) -> Result<Self, SoulError>;
+    /// Compute the weighted match score against a query.
+    pub fn match_score(&self, query: &SoulQuery, weights: &MatchWeights) -> f32;
+    /// Check whether all required nodes meet minimum confidence thresholds.
+    pub fn is_complete(&self, policy: &CompletenessPolicy) -> bool;
+}
+```
+
+---
+
+### 3.8 What the Signature Is NOT
+
+- Not a fingerprint of the room (that is the ADR-030 field model, a separate object).
+- Not a waveform recording (the enrolled vectors are statistics and embeddings, not raw CSI).
+- Not invertible to the original CSI stream (the AETHER projection head's information bottleneck prevents reconstruction; see ADR-024 §4 Negative consequences).
+- Not a single scalar. Reducing to one number for threshold comparison is a deployment decision; the underlying object is a 7-channel graph.
+- Not equal to a stored pose. The AETHER embedding captures body dynamics over many windows, not a single body pose at one instant.

docs/user-guide-apple-homepod.md

@@ -0,0 +1,474 @@
+# RuView ↔ HomePod Integration Guide
+
+**Ambient intelligence for Apple Home.** Run RuView as a native HomeKit accessory so your HomePod discovers it, Siri understands it, and Apple Home automations govern it — no Home Assistant required.
+
+---
+
+## Architecture Overview
+
+RuView turns WiFi radio reflections into spatial intelligence (presence, breathing, fall risk, activity patterns). When paired with a HomePod or Apple TV acting as your Home Hub, RuView becomes an invisible sensor that feeds Siri, automations, and scenes:
+
+```
+ESP32-C6 CSI node (living room)
+  ↓ (UDP feature stream)
+RuView Sensing Server (announces presence, vital signs, BFLD events)
+  ↓ (HTTP polling)
+HAP Bridge (advertises HomeKit accessory on mDNS)
+  ↓ (Bonjour discovery)
+HomePod or Apple TV (Home Hub)
+  ↓ (forwards to Home app + Siri)
+iPhone, iPad, Mac, Watch, Apple Home automations
+```
+
+The integration leverages HomeKit Accessory Protocol (HAP-1.1) — the same standard that Philips Hue, Eve, and Nanoleaf use. Your HomePod discovers the bridge within seconds of launch, pairing is one-tap from the Home app, and Siri queries work immediately: *"Hey Siri, is anyone in the living room?"*
+
+For design rationale and privacy safeguards, see [ADR-125 — RuView ↔ Apple Home native HAP bridge](docs/adr/ADR-125-ruview-apple-home-native-hap-bridge.md).
+
+---
+
+## What's Shipped Today (Tier 1 + Tier 2)
+
+Eight incremental iterations landed in PR #797 on the `feat/adr-125-apple-fabric` branch:
+
+| Iteration | Capability | Commit | Status |
+|-----------|-----------|--------|--------|
+| 1 | Multi-characteristic HomeKit accessory (Motion + Occupancy + StatelessProgrammableSwitch) | `48db60a65` | Runtime-live |
+| 2 | Sensing-server HTTP endpoints for bridge polling (`/api/v1/vitals`, `/api/v1/bfld`, `/api/v1/semantic-events`) | `194a2e163` | Runtime-live, curl-validated |
+| 3 | HAP bridge with N child accessories; Siri-by-room (name each room, Siri voices it) | `63b77f760` | Runtime-live, two bridges advertising |
+| 4 | Semantic-events endpoint per §2.1.d (`Unknown Presence`, `Unexpected Occupancy`, `Unrecognized Activity Pattern`) | `3d30261e7` | Runtime-live, privacy invariant I1 enforced |
+| 5 | rvagent MCP consumer (agentic chain); 12 MCP tools for Claude Code integration | `c19742d71` | Runtime-validated on real C6 |
+| 6 | PyO3 BFLD PrivacyClass binding (SOTA rust crate exposed to Python) | `de0712d43` | Source-built (`cargo check` green) |
+| 7 | Shortcuts-as-glue (launchd job + Speak Text on HomePod via iCloud Home graph, bypasses Bonjour blocker) | `d0525359d` | Runtime-validated, osascript trigger green |
+| 8 | Custom characteristic UUID scaffold for Eve.app rendering (design complete; runtime HAP-python JSON-loader follow-up) | `3bb8c1621` | Design scaffolded |
+
+**What you can do today:**
+
+- Pair a RuView bridge into your Home app on iPhone, iPad, or Mac.
+- Ask Siri room-specific presence questions ("is anyone home", "is the office occupied", "did someone fall").
+- Trigger automations on presence detection, breathing presence, fall risk, or activity pattern anomalies.
+- Stream RuView events to HomePod announcements via the Shortcuts-as-glue path (Tier 2).
+- Query RuView data programmatically through the agentic MCP interface (Claude Code integration).
+
+---
+
+## Quickstart (5 minutes)
+
+### Prerequisites
+
+- **Hardware**: ESP32-C6 running CSI firmware (rev v0.7.0+) on the same WiFi network as your Mac and HomePod.
+- **Software**: Python 3.8+ on a Mac that's already paired into your Home app (iCloud account).
+- **Network**: Mac, HomePod, and ESP32-C6 must all be on the same LAN subnet (e.g., `192.168.1.0/24`).
+
+### Step 1: Provision the ESP32-C6
+
+Connect the C6 via USB and run the provisioning script:
+
+```bash
+python firmware/esp32-csi-node/provision.py \
+  --port /dev/ttyUSB0 \
+  --ssid "YourWiFiSSID" \
+  --password "YourWiFiPassword" \
+  --target-ip 192.168.1.20
+```
+
+Verify the C6 boots on the network:
+
+```bash
+ping 192.168.1.20
+```
+
+### Step 2: Create a Python venv on the Mac and install HAP-python
+
+```bash
+mkdir -p ~/ruview-hap
+cd ~/ruview-hap
+python3 -m venv venv
+source venv/bin/activate
+pip install HAP-python
+```
+
+### Step 3: Copy the RuView bridge scripts to the Mac
+
+From the repository (e.g., cloned on your Mac), copy these files:
+
+```bash
+cp scripts/c6-presence-watcher.py ~/ruview-hap/
+cp scripts/ruview-sensing-server.py ~/ruview-hap/
+cp scripts/ruview-hap-bridge.py ~/ruview-hap/
+```
+
+### Step 4: Start the three daemons in order
+
+**Terminal 1: Start the C6 presence watcher** (reads UDP packets from the C6, applies BFLD privacy gate)
+
+```bash
+cd ~/ruview-hap
+source venv/bin/activate
+python c6-presence-watcher.py --node-id 1 --esp32-ip 192.168.1.20 --privacy-class 2
+```
+
+Output: Writes presence events to `/tmp/ruview-state.json`.
+
+**Terminal 2: Start the sensing server** (HTTP polling interface for the HAP bridge)
+
+```bash
+cd ~/ruview-hap
+source venv/bin/activate
+python ruview-sensing-server.py --port 3000
+```
+
+Output: Listening on `http://127.0.0.1:3000/api/v1/...`.
+
+**Terminal 3: Start the HAP bridge** (advertises HomeKit accessory on mDNS)
+
+```bash
+cd ~/ruview-hap
+source venv/bin/activate
+python ruview-hap-bridge.py --port 51826 --pin 200-70-910
+```
+
+Output: Look for setup code in the terminal output, e.g., `Setup code: 200-70-910`.
+
+### Step 5: Pair the bridge from your iPhone
+
+1. Open the **Home** app on your iPhone.
+2. Tap the **+** icon (top right) → **Add Accessory**.
+3. Scan the setup code (or tap **Don't Have a Code or Can't Scan?** → **More Options**).
+4. Select the **RuView Sense** bridge from the list (should appear within 10 seconds).
+5. Assign to a room (e.g., "Living Room").
+6. Tap **Done**.
+
+### Step 6: Test with Siri
+
+Once paired, ask Siri:
+
+```
+"Hey Siri, is anyone in the living room?"
+```
+
+Siri will respond with the current occupancy state. Walk past the C6 and ask again — the presence value should update within 1–2 seconds.
+
+---
+
+## Per-Room Expansion
+
+To monitor multiple rooms, run multiple C6 nodes, each with its own `c6-presence-watcher.py` instance:
+
+```bash
+# Terminal: Room 1 (Living Room, node_id=1)
+python c6-presence-watcher.py --node-id 1 --esp32-ip 192.168.1.20 \
+  --output /tmp/ruview-state.living-room.json
+
+# Terminal: Room 2 (Bedroom, node_id=2)
+python c6-presence-watcher.py --node-id 2 --esp32-ip 192.168.1.21 \
+  --output /tmp/ruview-state.bedroom.json
+
+# Terminal: HAP bridge (auto-discovers both state files)
+python ruview-hap-bridge.py --port 51826 --rooms "Living Room,Bedroom"
+```
+
+The HAP bridge auto-discovers `*.json` files in `/tmp/ruview-state*` and creates a child HomeKit accessory per room. Each room appears separately in the Home app and can be assigned to its physical location.
+
+---
+
+## Privacy Semantics
+
+RuView's BFLD (Beamforming Feedback Layer for Detection) uses a **privacy class** gate that enforces what data can cross the HomeKit boundary. Only Classes 2 and 3 (Anonymous and Restricted) are eligible; Class 0/1 (Raw identity information) is never exposed.
+
+### The Three Semantic Events
+
+HomeKit exposes **thresholded events**, not raw probabilities:
+
+| Event | HomeKit Characteristic | Meaning | Example Automation |
+|-------|----------------------|---------|-------------------|
+| **Unknown Presence** | MotionSensor (stateful) | Person detected + no matching identity record for >30s | "Turn on porch light when Unknown Presence detected after 9pm" |
+| **Unexpected Occupancy** | OccupancySensor | Occupancy outside the operator's defined schedule | "Send notification if office is occupied on weekends" |
+| **Unrecognized Activity Pattern** | ProgrammableSwitch (momentary) | Activity drift or recalibration gate fires | "Run a re-learning sequence when activity changes" |
+
+### What's Deliberately Hidden
+
+The following are **never** exposed to HomeKit:
+
+- `identity_risk_score` (numeric 0–1 confidence) — only thresholded semantic events cross the boundary
+- Soul-Signature match probability — internal to BFLD
+- `rf_signature_hash` — cryptographic internal state
+
+This enforces **ADR-125 §2.1.d invariant I1**: raw identity information never exits the node. The semantic framing is intentional — "Unknown Presence" reads as *who's-here-and-it's-fine-but-worth-noting*, not as an accusation.
+
+For the technical definition, see [ADR-118 — Beamforming Feedback Layer for Detection](docs/adr/ADR-118-bfld-beamforming-feedback-layer-for-detection.md).
+
+---
+
+## Siri-by-Room
+
+Name each HomeKit accessory after its room. The HAP bridge pulls room names from the state file prefixes:
+
+```bash
+python c6-presence-watcher.py --node-id 1 \
+  --output /tmp/ruview-state.LIVING_ROOM.json
+
+# HAP bridge sees this and names the accessory "Living Room"
+```
+
+When paired in the Home app, Siri knows the room:
+
+| Query | Result |
+|-------|--------|
+| "Is anyone in the living room?" | Queries the Living Room accessory's motion sensor |
+| "Is anyone home?" | Queries all room accessories; returns true if any motion is detected |
+| "Turn on the bedroom lights when occupancy is detected" | Automation triggers on the Bedroom accessory only |
+
+### StatelessProgrammableSwitch for Automations
+
+Each room also exposes a **StatelessProgrammableSwitch** that fires on semantic-event boundaries (Unrecognized Activity Pattern, Recalibration, etc.). This is the HomeKit primitive for momentary triggers:
+
+1. In the Home app, go to **Automation** → **Create New Automation** → **When an Accessory is Controlled**.
+2. Select **Living Room** → **Programmable Switch** → **Single Press**.
+3. Add an action: *Turn on scene*, *Send notification*, *Set HomeKit Secure Video recording*, etc.
+
+---
+
+## HomePod Announcements via Shortcuts (Tier 2 Path)
+
+The easiest way to announce RuView events on a HomePod is through **Shortcuts-as-glue** — a native macOS launchd job that watches RuView's semantic events and triggers a Shortcut you define.
+
+This path **bypasses the Bonjour reflector blocker** that can prevent HomePod discovery in some mesh networks. Instead of direct mDNS, the Mac uses the Home graph (iCloud-paired) to reach the HomePod.
+
+### One-Time Setup
+
+#### 1. Create the Shortcut in Shortcuts.app
+
+1. Open **Shortcuts.app** on your Mac.
+2. Click **+** (top left) → **Create Shortcut**.
+3. Click **Add Action** → search for **"Speak Text"** → add it.
+4. In the **"Speak Text"** action, click the **speaker icon** → select your **HomePod** (or HomePod mini).
+5. Name the Shortcut **`RuView Announce`** (exact name).
+6. **Save** (top right).
+
+#### 2. Test the Shortcut from the terminal
+
+```bash
+osascript -e 'tell application "Shortcuts Events" to run shortcut "RuView Announce" with input "Test from RuView"'
+```
+
+Your HomePod should speak "Test from RuView" in your chosen voice.
+
+#### 3. Install the launchd job
+
+Copy the launchd plist from the repository:
+
+```bash
+cp scripts/macos-shortcuts/ruview-watcher.plist \
+  ~/Library/LaunchAgents/com.ruvnet.ruview.watcher.plist
+
+launchctl load ~/Library/LaunchAgents/com.ruvnet.ruview.watcher.plist
+
+launchctl list | grep ruvnet  # Confirm it's loaded
+```
+
+#### 4. Verify it works
+
+Tail the log in one terminal:
+
+```bash
+tail -f /tmp/ruview-watcher.log
+```
+
+In another terminal, walk past the C6 and trigger a presence detection. The log should show:
+
+```
+[17:10:12] unknown_presence rising-edge → running 'RuView Announce'
+```
+
+And your HomePod should announce the event in its configured voice.
+
+### Extending to Multiple Rooms
+
+To announce different events in different rooms, create multiple Shortcuts in Shortcuts.app:
+
+- `RuView Announce Kitchen`
+- `RuView Announce Bedroom`
+
+Then run multiple watcher jobs with different `--shortcut-name` flags:
+
+```bash
+# Kitchen events on HomePod mini in kitchen
+scripts/macos-shortcuts/announce-via-homepod.sh \
+  --node-id 1 --event unknown_presence \
+  --shortcut-name "RuView Announce Kitchen" \
+  --poll-interval 2 &
+
+# Bedroom events on HomePod in bedroom
+scripts/macos-shortcuts/announce-via-homepod.sh \
+  --node-id 2 --event unknown_presence \
+  --shortcut-name "RuView Announce Bedroom" \
+  --poll-interval 2 &
+```
+
+### Going Further
+
+Because the Shortcut is operator-editable in Shortcuts.app, you can extend it to do anything:
+
+- **Activate a scene** ("turn on bedtime scene when fall risk detected")
+- **Send a notification** to your Apple Watch
+- **Call a Webhook** to integrate with other systems
+- **Send a message** to another person's iPhone
+- **Trigger a HomeKit secure camera recording**
+
+This is the flexibility of the Shortcuts-as-glue approach — no code change needed in RuView, all customization in the operator's own Shortcuts library.
+
+For complete setup details and troubleshooting, see [`scripts/macos-shortcuts/README.md`](scripts/macos-shortcuts/README.md).
+
+---
+
+## Agentic Consumption via MCP
+
+RuView's sensing stream is also available through Model Context Protocol (MCP) — the standard interface for Claude Code and other AI agents to query RuView data.
+
+### The `@ruvnet/rvagent` npm package (v0.1.0)
+
+The package exposes **12 MCP tools** that let Claude Code agents:
+
+- Query presence and occupancy per room
+- Read breathing rate and heart rate telemetry
+- Monitor BFLD semantic events
+- Inspect the app registry (edge modules)
+- Kickstart background training jobs
+
+### Installation
+
+In your Claude Code project:
+
+```bash
+npm install -D @ruvnet/rvagent@0.1.0
+
+# Or, add via MCP:
+claude mcp add rvagent -- npx -y @ruvnet/rvagent@0.1.0
+```
+
+Then in your Claude Code chat:
+
+```
+/claude-flow-help  # Lists all available MCP tools
+```
+
+### Tool Reference
+
+| Tool | Input | Output |
+|------|-------|--------|
+| `ruview_csi_latest` | node_id | Latest CSI window (1024 subcarriers, 30 OFDM symbols) |
+| `ruview_pose_infer` | CSI window | 17-keypoint skeleton (x, y, confidence per joint) |
+| `ruview_count_infer` | CSI window | Person count + 95% CI |
+| `ruview_registry_list` | query (optional) | List of 105+ available edge modules |
+| `ruview_train_count` | epochs, learning_rate | Kickoff training job ID |
+| `ruview_job_status` | job_id | Progress, ETA, current loss |
+| `ruview.bfld.last_scan` | node_id | Latest BFLD scan: privacy_class, person_count (identity_risk_score=null per I1 invariant) |
+| `ruview.bfld.subscribe` | node_id, event_filter | Stream BFLD windows until you close the stream |
+| `ruview.presence.now` | room (optional) | Current occupancy per room |
+| `ruview.vitals.get_breathing` | node_id | Breathing rate (BPM) + confidence |
+| `ruview.vitals.get_heart_rate` | node_id | Heart rate (BPM) + confidence |
+| `ruview.vitals.get_all` | node_id | Breathing + heart rate + metadata |
+
+### Example: Claude Code Agent Workflow
+
+```python
+# Claude-flow agent pseudocode
+import claude_code
+
+tools = claude_code.mcp_tools("rvagent")
+
+# Query latest presence
+presence = tools["ruview.presence.now"](room="living room")
+print(f"Living room occupancy: {presence.occupancy}")  # True/False
+
+# Check vitals
+vitals = tools["ruview.vitals.get_all"](node_id=1)
+print(f"Breathing: {vitals.breathing_bpm} BPM")
+
+# Stream BFLD events in real-time
+for event in tools["ruview.bfld.subscribe"](node_id=1, event_filter="unknown_presence"):
+    print(f"Unknown presence detected: privacy_class={event.privacy_class}")
+```
+
+For the full MCP specification, see [ADR-124 — rvagent MCP / RuVector npm integration](docs/adr/ADR-124-rvagent-mcp-ruvector-npm-integration.md).
+
+---
+
+## Troubleshooting
+
+### HomePod Not Visible on `dns-sd -B _airplay._tcp local.` from the Mac
+
+**Likely cause**: HomePod and Mac are on different subnets despite being on the same SSID. Some mesh networks segment 2.4 GHz and 5 GHz bands onto different `/24` subnets, or place guest devices on a separate VLAN.
+
+**Check**:
+
+1. Open your router admin page and confirm both the HomePod and Mac are in the same subnet range (e.g., both `192.168.1.x`).
+2. If they're on different subnets (e.g., `192.168.1.x` vs `192.168.100.x`), enable **IGMP Proxying** in your router settings (common on Netgear Nighthawk). If available, enable **Bonjour Repeater** or **mDNS Reflector** instead.
+3. Restart the HomePod and Mac.
+
+**Note**: The **Shortcuts-as-glue path (Tier 2)** doesn't need this fix — it routes announcements through the iCloud Home graph, not mDNS.
+
+### iPhone Pairing Fails with "Couldn't Add Accessory"
+
+**Likely cause**: The HAP bridge's pairing state is corrupt or out of sync with mDNS.
+
+**Fix**:
+
+1. Stop the HAP bridge daemon.
+2. Delete the pairing state file:
+   ```bash
+   rm -rf ~/.ruview-hap-prod/accessory.state
+   ```
+3. Restart the HAP bridge — it regenerates a new setup code.
+4. From the Home app, retry **Add Accessory** → **More Options** with the new setup code.
+
+### The Setup Code Regenerates on Restart
+
+**Expected behavior.** HAP-python regenerates the setup code if the pairing persist file is missing or corrupt. Once you've paired successfully, the pairing key is stored separately in `~/.ruview-hap-prod/` and survives restarts — the setup code itself is transient and only matters during initial pairing.
+
+If you lose the setup code before pairing, simply delete the state and restart to get a new one.
+
+### Presence Updates Are Slow or Stuck
+
+**Likely cause**: The HTTP polling loop in `ruview-sensing-server.py` is blocked, or the C6 is not sending UDP packets.
+
+**Check**:
+
+1. Verify the C6 is booting: `ping 192.168.1.20`.
+2. Verify packets are reaching the sensing server:
+   ```bash
+   nc -u -l 5005 &  # Listen on UDP 5005
+   # You should see occasional packets from the C6
+   ```
+3. Manually query the sensing server:
+   ```bash
+   curl http://127.0.0.1:3000/api/v1/vitals/latest
+   ```
+   Should return JSON with breathing and heart rate fields.
+4. If the HAP bridge doesn't reflect the changes after polling, restart it.
+
+---
+
+## What's NOT in Scope
+
+These items are intentionally deferred or beyond the current release:
+
+| Item | Status | Timeline |
+|------|--------|----------|
+| **Matter Protocol (P3)** | Deferred | Waiting for `matter-rs` SDK stabilization; HAP-1.1 covers 95% of the UX today |
+| **Rust-native HAP (P2)** | Planned | Replaces Python `HAP-python` sidecar; expected after operator feedback from 5+ real pairings |
+| **PyO3 BFLD wheel deployment (ADR-117 P5)** | Pending | Runtime import flip so Python scripts use the Rust BFLD crate; source-built (✅ `cargo check` green) but wheel not yet published |
+| **Custom characteristic UUIDs for Eve.app (Iter 8 runtime)** | Scaffolded | Design complete; awaiting HAP-python JSON-loader implementation (small follow-up PR) |
+| **AirPlay 2 voice synthesis (pyatv)** | Network-pending | Requires HomePod visible on Bonjour from the Mac; Shortcuts-as-glue (Tier 2) is the working alternative |
+
+---
+
+## References
+
+- [ADR-125 — RuView ↔ Apple Home native HAP bridge](docs/adr/ADR-125-ruview-apple-home-native-hap-bridge.md) — Design spec, privacy rationale, sequencing
+- [ADR-118 — Beamforming Feedback Layer for Detection](docs/adr/ADR-118-bfld-beamforming-feedback-layer-for-detection.md) — BFLD privacy gate and identity-risk semantics
+- [ADR-124 — rvagent MCP / RuVector npm integration](docs/adr/ADR-124-rvagent-mcp-ruvector-npm-integration.md) — MCP tool specification
+- [Issue #796](https://github.com/ruvnet/RuView/issues/796) — Tier 1+2 sprint tracking (close-out comments have per-iter empirical data)
+- [scripts/macos-shortcuts/README.md](scripts/macos-shortcuts/README.md) — Shortcuts-as-glue setup and troubleshooting
+- [HomeKit Accessory Protocol (Non-Commercial Version)](https://developer.apple.com/apple-home/) — HAP-1.1 spec
+- [HAP-python on GitHub](https://github.com/ikalchev/HAP-python) — Implementation library

docs/user-guide.md

@@ -164,21 +164,66 @@ cargo add wifi-densepose-wasm-edge
 
 See the full crate list and dependency order in [CLAUDE.md](../CLAUDE.md#crate-publishing-order).
 
-### From Source (Python)
+### Python wheel (pip) — ADR-117
+
+The Python API ships as **two interchangeable PyPI packages** — same
+compiled PyO3 wheel under both names; pick whichever import name
+reads better in your code:
+
+| PyPI | Install | Latest | Import |
+|---|---|---|---|
+| [`ruview`](https://pypi.org/project/ruview/) | `pip install ruview` | `2.0.0a1` | `from ruview import ...` |
+| [`wifi-densepose`](https://pypi.org/project/wifi-densepose/) | `pip install wifi-densepose` | `2.0.0a1` | `from wifi_densepose import ...` |
+
+```bash
+pip install ruview                        # core DSP (~250 KB compiled wheel)
+pip install "ruview[client]"              # + asyncio WebSocket + paho-mqtt
+```
+
+```python
+# vitals
+from ruview import BreathingExtractor, HeartRateExtractor
+br = BreathingExtractor.esp32_default()   # 56 subcarriers @ 100 Hz, 30s window
+
+# live sensing-server stream
+from ruview.client import SensingClient, EdgeVitalsMessage
+async with SensingClient("ws://localhost:8765/ws/sensing") as c:
+    async for msg in c.stream():
+        if isinstance(msg, EdgeVitalsMessage):
+            print(msg.breathing_rate_bpm, msg.heartrate_bpm)
+
+# Home Assistant semantic primitives (ADR-115 HA-MIND)
+from ruview.client import (
+    RuViewMqttClient, SemanticPrimitive, SemanticPrimitiveListener,
+)
+```
+
+The wheels ship for Linux (x86_64, aarch64 via sdist), macOS (sdist),
+and Windows (amd64 wheel). Stable ABI (`abi3-py310`) — one binary
+covers Python 3.10+. Multi-arch native wheels are produced by the
+[pip-release.yml](../.github/workflows/pip-release.yml) cibuildwheel
+matrix on each `v*-pip` tag.
+
+> **Migrating from v1.x?** The legacy `wifi-densepose==1.1.0` FastAPI
+> server is end-of-life. `wifi-densepose==1.99.0` is a tombstone that
+> raises `ImportError` with a migration URL; upgrade to `>=2.0.0a1`
+> (or switch to `ruview`).
+
+To build the wheel from source (e.g. for a local change):
 
 ```bash
 git clone https://github.com/ruvnet/RuView.git
-cd RuView
-
-pip install -r requirements.txt
-pip install -e .
-
-# Or via PyPI
-pip install wifi-densepose
-pip install wifi-densepose[gpu]   # GPU acceleration
-pip install wifi-densepose[all]   # All optional deps
+cd RuView/python
+pip install maturin>=1.7
+maturin develop --release
+pytest tests/                              # 183 tests
+pytest bench/ --benchmark-only             # 12 hot-path benchmarks
 ```
 
+Full API + tests breakdown is on the PyPI front page:
+[wifi-densepose on PyPI](https://pypi.org/project/wifi-densepose/) ·
+[ruview on PyPI](https://pypi.org/project/ruview/).
+
 ### Guided Installer
 
 An interactive installer that detects your hardware and recommends a profile:
@@ -727,6 +772,112 @@ Open `/var/run/ruview-matter.txt` for the Matter pairing QR / 11-digit setup cod
 
 Detailed entity reference, blueprint catalog, troubleshooting recipe matrix: see [`docs/integrations/home-assistant.md`](integrations/home-assistant.md).
 
+### BFLD — privacy-gated WiFi BFI sensing layer (ADR-118)
+
+The `wifi-densepose-bfld` crate adds an explicit privacy-gating layer on top of the sensing pipeline. It ingests 802.11ac/ax Beamforming Feedback Information (BFI) and emits bounded, classified sensing events that HA / Matter / MQTT consumers can read **without** leaking identity-discriminative data.
+
+Three structural invariants enforced by the type system:
+
+- **I1** — Raw BFI never exits the node (`Sink` marker-trait hierarchy)
+- **I2** — Identity embedding is in-RAM-only (no `Serialize`/`Clone`/`Copy`; `Drop` zeroizes)
+- **I3** — Cross-site identity correlation is cryptographically impossible (per-site BLAKE3-keyed hash + daily epoch rotation)
+
+#### Minimal operator quickstart
+
+Two runnable examples ship with the crate:
+
+```bash
+# In-process consumer: build pipeline, send one frame, print event JSON
+cargo run -p wifi-densepose-bfld --example bfld_minimal
+
+# Worker thread + HA-DISCO: full publish lifecycle (availability + discovery + state + LWT)
+cargo run -p wifi-densepose-bfld --example bfld_handle
+```
+
+#### Production publish lifecycle (HA-DISCO + MQTT)
+
+```rust
+// Bootstrap (once at startup, retain=true messages):
+publish_availability_online(&mut retained_pub, "seed-01")?;
+publish_discovery(&mut retained_pub, "seed-01", PrivacyClass::Anonymous)?;
+
+// Per-frame:
+let handle = BfldPipelineHandle::spawn(pipeline, state_pub);
+handle.send(PipelineInput { inputs, embedding })?;
+```
+
+Six HA entities are auto-created per node (`binary_sensor.*_bfld_presence`, `sensor.*_bfld_motion`/`person_count`/`zone_activity`/`confidence`/`identity_risk`). The `identity_risk` entity is **only present at `PrivacyClass::Anonymous`**; class `Restricted` deployments (care homes, regulated environments) drop it entirely from both discovery and state topics.
+
+#### Three operator HA blueprints
+
+Under `v2/crates/cog-ha-matter/blueprints/bfld/`:
+
+- `presence-lighting.yaml` — `binary_sensor.*_bfld_presence` ⇒ `light.turn_on/off` with configurable hold time
+- `motion-hvac.yaml` — `sensor.*_bfld_motion > threshold` ⇒ `climate.set_temperature` ΔT
+- `identity-risk-anomaly.yaml` — rolling 7-day z-score notification (requires HA Statistics helper)
+
+Import via HA UI: Settings → Automations & Scenes → Blueprints → Import.
+
+#### Privacy class deployment matrix
+
+| Class | Identity fields | Use case |
+|-------|-----------------|----------|
+| `Raw` | full BFI matrix | local-only research (never networked) |
+| `Derived` | downsampled angles + risk score | operator-acknowledged LAN research mode |
+| `Anonymous` (default) | aggregate sensing only + risk score + rotating hash | production HA / Matter deployments |
+| `Restricted` | aggregate sensing only, identity fields stripped | care homes, GDPR/HIPAA-style regulated environments |
+
+The `enable_privacy_mode()` runtime toggle on `BfldPipeline` engages `Restricted` from any baseline without restarting the pipeline — useful for security-incident response.
+
+#### MQTT topic tree
+
+```
+ruview/<node_id>/bfld/availability         online / offline
+ruview/<node_id>/bfld/presence/state       true / false
+ruview/<node_id>/bfld/motion/state         0.000000..1.000000
+ruview/<node_id>/bfld/person_count/state   integer
+ruview/<node_id>/bfld/confidence/state     0.000000..1.000000
+ruview/<node_id>/bfld/zone_activity/state  "<zone_name>"  (if configured)
+ruview/<node_id>/bfld/identity_risk/state  0.000000..1.000000  (class 2 only)
+```
+
+The `rumqttc 0.24` (`use-rustls`) backend ships behind the `mqtt` feature; `RumqttPublisher::connect_with_lwt(node_id, opts, capacity)` pre-configures the Last Will and Testament so the broker auto-publishes `"offline"` on session drop.
+
+Detailed surface: [`v2/crates/wifi-densepose-bfld/README.md`](../v2/crates/wifi-densepose-bfld/README.md), [`docs/research/BFLD/`](research/BFLD/) (11 files, 13,544 words), [ADR-118 through ADR-123](adr/ADR-118-bfld-beamforming-feedback-layer-for-detection.md).
+
+### SENSE-BRIDGE — rvagent MCP server for AI agents (ADR-124)
+
+`@ruvnet/rvagent` is a dual-transport MCP server that makes RuView sensing primitives callable by Claude Code, Cursor, and ruflo swarms without bespoke HTTP client code.
+
+**Install (Claude Code)**:
+
+```bash
+claude mcp add rvagent -- npx @ruvnet/rvagent stdio
+# With a remote sensing-server:
+RUVIEW_SENSING_SERVER_URL=http://cognitum-v0:3000 claude mcp add rvagent -- npx @ruvnet/rvagent stdio
+```
+
+**Available tools (6 of 20 in v0.1.0)**:
+
+| Tool | Returns |
+|------|---------|
+| `ruview.presence.now` | `present`, `n_persons`, `confidence`, `timestamp_ms` |
+| `ruview.vitals.get_breathing` | `breathing_rate_bpm` (null if unavailable), `confidence` |
+| `ruview.vitals.get_heart_rate` | `heartrate_bpm` (null if unavailable), `confidence` |
+| `ruview.vitals.get_all` | Full `EdgeVitalsMessage` (all vitals in one call) |
+| `ruview.bfld.last_scan` | `identity_risk_score`, `privacy_class`, `n_frames`, `timestamp_ms` |
+| `ruview.bfld.subscribe` | `subscription_id`, `expires_at`, `topic` (MQTT wildcard) |
+
+**Streamable HTTP** (for remote ruflo swarms):
+
+```bash
+RVAGENT_HTTP_TOKEN=secret npx @ruvnet/rvagent http --port 3001
+# POST JSON-RPC to http://127.0.0.1:3001/mcp
+# Cross-origin requests are rejected with 403; missing/wrong token → 401.
+```
+
+Source: [`tools/ruview-mcp/`](../tools/ruview-mcp/README.md). Tracking issue: [#787](https://github.com/ruvnet/RuView/issues/787). Full ADR: [ADR-124](adr/ADR-124-rvagent-mcp-ruvector-npm-integration.md).
+
 ---
 
 ## Web UI

plugins/ruview/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "ruview",
-  "description": "End-to-end RuView (WiFi-DensePose) toolkit for Claude Code: onboarding, ESP32 hardware setup, configuration, sensing applications, model training, advanced multistatic sensing, and witness verification — from practical to advanced.",
-  "version": "0.1.0",
+  "description": "End-to-end RuView (WiFi-DensePose) toolkit for Claude Code: onboarding, ESP32 hardware setup, configuration, sensing applications, model training, advanced multistatic sensing, witness verification, BFLD privacy layer, and rvAgent + RVF agentic flows — from practical to advanced.",
+  "version": "0.3.0",
   "author": {
     "name": "ruvnet",
     "url": "https://github.com/ruvnet/RuView"
@@ -19,5 +19,14 @@
     "edge-ai",
     "model-training",
     "onboarding"
-  ]
+  ],
+  "mcpServers": {
+    "rvagent": {
+      "command": "npx",
+      "args": ["-y", "@ruvnet/rvagent"],
+      "env": {
+        "RVAGENT_SENSING_URL": "http://localhost:3000"
+      }
+    }
+  }
 }

plugins/ruview/codex/AGENTS.md

@@ -47,6 +47,7 @@ After significant changes: run the Rust tests + Python proof, then `bash scripts
 | `ruview-app` | Run a sensing application (presence / vitals / pose / sleep / MAT / point cloud) |
 | `ruview-train` | Train / evaluate / publish a model (incl. GPU on GCloud) |
 | `ruview-verify` | Run the trust pipeline + pre-merge checklist |
+| `ruview-rvagent` | Explore rvAgent + RVF agentic flows wiring into RuView |
 
 Install: copy `codex/prompts/*.md` into `~/.codex/prompts/`, or run Codex with this directory on its prompt path.
 

plugins/ruview/codex/prompts/ruview-rvagent.md

@@ -0,0 +1,54 @@
+# ruview-rvagent — explore rvAgent + RVF agentic flows for RuView
+
+You are helping the operator explore or prototype the integration of `vendor/ruvector/crates/rvAgent/` (a production Rust AI-agent framework) with RuView's existing sensing pipeline (`v2/crates/wifi-densepose-*`) and the RVF cognitive container format (`v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs`).
+
+## Live MCP server: `@ruvnet/rvagent` v0.1.0
+
+The TypeScript MCP server (`tools/ruview-mcp/`, published as `@ruvnet/rvagent`) is live on npm and exposes `bfld_last_scan`, `bfld_subscribe`, `presence_now`, `vitals_get_breathing`, `vitals_get_heart_rate`, `vitals_get_all`, `vitals_fetch`. Add to a Codex MCP config:
+
+```json
+{
+  "mcpServers": {
+    "rvagent": {
+      "command": "npx",
+      "args": ["-y", "@ruvnet/rvagent"],
+      "env": { "RVAGENT_SENSING_URL": "http://localhost:3000" }
+    }
+  }
+}
+```
+
+This is the operator-facing tool surface; the Rust crate below remains the substrate for deeper RVF-aware agentic flows.
+
+## Trigger phrasing
+
+- "wire rvAgent into RuView"
+- "I want a queen agent that fans out to cog-pose-estimation and cog-bfld"
+- "persist agent decisions in the same witness bundle as sensing events"
+- "how do I keep agent outputs class-3 compliant?"
+
+## What to read first
+
+1. `docs/research/rvagent-rvf-integration/README.md` — full integration thesis, open questions, next steps.
+2. `vendor/ruvector/crates/rvAgent/README.md` — what rvAgent ships (8 crates, 14 middlewares).
+3. `vendor/ruvector/crates/rvAgent/.ruv/agents/rvagent-queen.md` — queen-agent persona that coordinates cog subagents.
+4. `v2/crates/wifi-densepose-bfld/src/{event.rs,pipeline_handle.rs}` — the BFLD event surface and the operator-facing handle that an agent would call.
+5. `v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs` — segment types; `SEG_AGENT_STATE = 0x08` and `SEG_DECISION = 0x09` are the proposed additions.
+
+## Three shippable touchpoints (each independent)
+
+1. **RVF wire** — add `SEG_AGENT_STATE` + `SEG_DECISION` segments so rvAgent and RuView sessions can interleave in one blob (witness-bundle covers both halves).
+2. **Tool shim** — `BfldEvent::to_json()` already exists; wrap as `rvagent_tools::ToolOutput`.
+3. **Cog subagents** — register `cog-pose-estimation`, `cog-person-count`, `cog-ha-matter`, (proposed) `cog-bfld` under the queen via the `Subagent` trait.
+
+## Open questions to surface
+
+- Is `vendor/ruvector/crates/rvAgent/` on the v2 workspace path?
+- Sync ↔ async adapter location (BFLD `Publish` is sync; rvAgent backends are tokio).
+- Privacy-class composition — does `rvagent-middleware::sanitizer` consume `BfldEvent::privacy_class`?
+- Soul Signature ↔ `SoulMatchOracle` bridge (ADR-121 §2.6).
+- Should `BfldPipelineHandle::send` land as a public MCP tool via `rvagent-mcp`?
+
+## Suggested next action
+
+Draft ADR-124 — "rvAgent + RVF integration for RuView agentic flows" — capturing segment assignments, cog-subagent contract, and privacy-class composition. Land **before** scaffolding `v2/crates/wifi-densepose-agent`.

plugins/ruview/skills/ruview-rvagent/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: ruview-rvagent
+description: Explore and prototype rvAgent + RVF integration for RuView agentic flows. Use when working on cross-cog coordination, operator-facing agents reading BFLD / pose / vitals events live, or persisting agent state alongside sensing data in the same RVF container.
+---
+
+# RuView rvAgent + RVF integration
+
+Surface area for wiring `vendor/ruvector/crates/rvAgent/` into RuView so the existing sensing pipeline becomes the substrate an agentic flow can read, reason about, and respond to.
+
+## Quickstart — published MCP server (`@ruvnet/rvagent` v0.1.0)
+
+Installing this plugin registers `@ruvnet/rvagent` as an MCP server. On activation, Claude Code spawns `npx -y @ruvnet/rvagent` and exposes its tools directly:
+
+| Tool | Purpose |
+|------|---------|
+| `bfld_last_scan` | Most recent BFLD event from the sensing server |
+| `bfld_subscribe` | Stream BFLD events for a window |
+| `presence_now` | Current room-level presence state |
+| `vitals_get_breathing` | Latest breathing-rate sample |
+| `vitals_get_heart_rate` | Latest heart-rate sample |
+| `vitals_get_all` | Composite vitals snapshot |
+| `vitals_fetch` | Historical vitals window |
+
+Override the sensing-server URL via the `RVAGENT_SENSING_URL` env var (default `http://localhost:3000`). Source lives at `tools/ruview-mcp/`; ADR-124 captures the design.
+
+Smoke-check the wiring: `npm view @ruvnet/rvagent version` should return `0.1.0` (or newer).
+
+## When to use this skill
+
+- "I want an agent that reacts to BFLD presence in the kitchen and pages the carer."
+- "I need cog-pose-estimation and cog-bfld to negotiate before publishing a synthesized event."
+- "Can the witness chain attest both the sensing event AND the agent decision in one RVF blob?"
+- "How do we keep rvAgent's tool outputs class-3 compliant when the source BFLD event is Restricted?"
+
+## Key surfaces
+
+| Surface | File | Notes |
+|---------|------|-------|
+| rvAgent core | `vendor/ruvector/crates/rvAgent/rvagent-core/src/agi_container.rs` (627 LOC) | RVF-compatible state container |
+| rvAgent middleware | `vendor/ruvector/crates/rvAgent/rvagent-middleware/` | Witness, sanitizer, SONA, HNSW |
+| Agent personas | `vendor/ruvector/crates/rvAgent/.ruv/agents/rvagent-{queen,coder,tester,security}.md` | Reference patterns |
+| RVF container | `v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs` | Add `SEG_AGENT_STATE`, `SEG_DECISION` |
+| BFLD event | `v2/crates/wifi-densepose-bfld/src/event.rs` | `BfldEvent::to_json()` → `ToolOutput` |
+| BFLD pipeline handle | `v2/crates/wifi-densepose-bfld/src/pipeline_handle.rs` | `BfldPipelineHandle::send` |
+
+## Research dossier
+
+Full integration analysis lives at `docs/research/rvagent-rvf-integration/README.md`.
+
+Three shippable touchpoints, each independent:
+
+1. **RVF wire**: two new segment types (`SEG_AGENT_STATE = 0x08`, `SEG_DECISION = 0x09`) let rvAgent sessions interleave with RuView sensing sessions in the same blob.
+2. **Tool surface**: `BfldEvent → ToolOutput` shim turns BFLD events into agent context with no new IPC.
+3. **Cog subagents**: `cog-pose-estimation` / `cog-person-count` / `cog-ha-matter` / `cog-bfld` register as rvAgent subagents under a queen-agent router.
+
+## Open questions
+
+- Workspace inclusion of `vendor/ruvector/crates/rvAgent/` (path dep vs published crate)
+- Sync ↔ async adapter (BFLD `Publish` is sync, rvAgent backends are tokio)
+- Privacy-class composition (does rvAgent's sanitizer consume `PrivacyClass`?)
+- Soul Signature ↔ `SoulMatchOracle` bridge
+- Whether `BfldPipelineHandle::send` lands as a public MCP tool via `rvagent-mcp`
+
+## Next decision
+
+ADR-124 (proposed) — "rvAgent + RVF integration for RuView agentic flows" — would capture segment assignments, cog-subagent contract, and the privacy-class composition rule. Land before scaffolding `v2/crates/wifi-densepose-agent`.

python/.gitignore

@@ -0,0 +1,20 @@
+# Python build/install artifacts
+target/
+.venv/
+__pycache__/
+*.pyc
+*.pyd
+*.so
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+
+# Maturin develop produces .pyd extensions in wifi_densepose/
+wifi_densepose/*.pyd
+wifi_densepose/*.so
+wifi_densepose/_native.abi3.*
+
+# Local build wheels
+dist/
+wheelhouse/
+*.egg-info/

python/Cargo.lock

@@ -0,0 +1,995 @@
+# This file is automatically @generated by Cargo.
+# It is not intended for manual editing.
+version = 4
+
+[[package]]
+name = "android_system_properties"
+version = "0.1.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "819e7219dbd41043ac279b19830f2efc897156490d7fd6ea916720117ee66311"
+dependencies = [
+ "libc",
+]
+
+[[package]]
+name = "anyhow"
+version = "1.0.102"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7f202df86484c868dbad7eaa557ef785d5c66295e41b460ef922eca0723b842c"
+
+[[package]]
+name = "arrayref"
+version = "0.3.9"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "76a2e8124351fda1ef8aaaa3bbd7ebbcb486bbcd4225aca0aa0d84bb2db8fecb"
+
+[[package]]
+name = "arrayvec"
+version = "0.7.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7c02d123df017efcdfbd739ef81735b36c5ba83ec3c59c80a9d7ecc718f92e50"
+
+[[package]]
+name = "autocfg"
+version = "1.5.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f2032f911046de80f0a198e0901378627c33f59ea0ac00e363d481118bd70a53"
+
+[[package]]
+name = "bitflags"
+version = "2.11.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c4512299f36f043ab09a583e57bceb5a5aab7a73db1805848e8fef3c9e8c78b3"
+
+[[package]]
+name = "blake3"
+version = "1.8.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "0aa83c34e62843d924f905e0f5c866eb1dd6545fc4d719e803d9ba6030371fce"
+dependencies = [
+ "arrayref",
+ "arrayvec",
+ "cc",
+ "cfg-if",
+ "constant_time_eq",
+ "cpufeatures",
+]
+
+[[package]]
+name = "bumpalo"
+version = "3.20.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "72f5acc6cb2ba439de613abc23857ec3d78374d8ed5ac84e9d11336e87da8649"
+
+[[package]]
+name = "cc"
+version = "1.2.62"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a1dce859f0832a7d088c4f1119888ab94ef4b5d6795d1ce05afb7fe159d79f98"
+dependencies = [
+ "find-msvc-tools",
+ "shlex",
+]
+
+[[package]]
+name = "cfg-if"
+version = "1.0.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9330f8b2ff13f34540b44e946ef35111825727b38d33286ef986142615121801"
+
+[[package]]
+name = "chrono"
+version = "0.4.44"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c673075a2e0e5f4a1dde27ce9dee1ea4558c7ffe648f576438a20ca1d2acc4b0"
+dependencies = [
+ "iana-time-zone",
+ "js-sys",
+ "num-traits",
+ "serde",
+ "wasm-bindgen",
+ "windows-link",
+]
+
+[[package]]
+name = "constant_time_eq"
+version = "0.4.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "3d52eff69cd5e647efe296129160853a42795992097e8af39800e1060caeea9b"
+
+[[package]]
+name = "core-foundation-sys"
+version = "0.8.7"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "773648b94d0e5d620f64f280777445740e61fe701025087ec8b57f45c791888b"
+
+[[package]]
+name = "cpufeatures"
+version = "0.3.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8b2a41393f66f16b0823bb79094d54ac5fbd34ab292ddafb9a0456ac9f87d201"
+dependencies = [
+ "libc",
+]
+
+[[package]]
+name = "crc"
+version = "3.4.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5eb8a2a1cd12ab0d987a5d5e825195d372001a4094a0376319d5a0ad71c1ba0d"
+dependencies = [
+ "crc-catalog",
+]
+
+[[package]]
+name = "crc-catalog"
+version = "2.5.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "217698eaf96b4a3f0bc4f3662aaa55bdf913cd54d7204591faa790070c6d0853"
+
+[[package]]
+name = "equivalent"
+version = "1.0.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "877a4ace8713b0bcf2a4e7eec82529c029f1d0619886d18145fea96c3ffe5c0f"
+
+[[package]]
+name = "find-msvc-tools"
+version = "0.1.9"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5baebc0774151f905a1a2cc41989300b1e6fbb29aff0ceffa1064fdd3088d582"
+
+[[package]]
+name = "foldhash"
+version = "0.1.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d9c4f5dac5e15c24eb999c26181a6ca40b39fe946cbe4c263c7209467bc83af2"
+
+[[package]]
+name = "futures-core"
+version = "0.3.32"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7e3450815272ef58cec6d564423f6e755e25379b217b0bc688e295ba24df6b1d"
+
+[[package]]
+name = "futures-task"
+version = "0.3.32"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "037711b3d59c33004d3856fbdc83b99d4ff37a24768fa1be9ce3538a1cde4393"
+
+[[package]]
+name = "futures-util"
+version = "0.3.32"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "389ca41296e6190b48053de0321d02a77f32f8a5d2461dd38762c0593805c6d6"
+dependencies = [
+ "futures-core",
+ "futures-task",
+ "pin-project-lite",
+ "slab",
+]
+
+[[package]]
+name = "getrandom"
+version = "0.4.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "0de51e6874e94e7bf76d726fc5d13ba782deca734ff60d5bb2fb2607c7406555"
+dependencies = [
+ "cfg-if",
+ "libc",
+ "r-efi",
+ "wasip2",
+ "wasip3",
+]
+
+[[package]]
+name = "hashbrown"
+version = "0.15.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9229cfe53dfd69f0609a49f65461bd93001ea1ef889cd5529dd176593f5338a1"
+dependencies = [
+ "foldhash",
+]
+
+[[package]]
+name = "hashbrown"
+version = "0.17.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ed5909b6e89a2db4456e54cd5f673791d7eca6732202bbf2a9cc504fe2f9b84a"
+
+[[package]]
+name = "heck"
+version = "0.5.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "2304e00983f87ffb38b55b444b5e3b60a884b5d30c0fca7d82fe33449bbe55ea"
+
+[[package]]
+name = "iana-time-zone"
+version = "0.1.65"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e31bc9ad994ba00e440a8aa5c9ef0ec67d5cb5e5cb0cc7f8b744a35b389cc470"
+dependencies = [
+ "android_system_properties",
+ "core-foundation-sys",
+ "iana-time-zone-haiku",
+ "js-sys",
+ "log",
+ "wasm-bindgen",
+ "windows-core",
+]
+
+[[package]]
+name = "iana-time-zone-haiku"
+version = "0.1.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f31827a206f56af32e590ba56d5d2d085f558508192593743f16b2306495269f"
+dependencies = [
+ "cc",
+]
+
+[[package]]
+name = "id-arena"
+version = "2.3.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "3d3067d79b975e8844ca9eb072e16b31c3c1c36928edf9c6789548c524d0d954"
+
+[[package]]
+name = "indexmap"
+version = "2.14.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d466e9454f08e4a911e14806c24e16fba1b4c121d1ea474396f396069cf949d9"
+dependencies = [
+ "equivalent",
+ "hashbrown 0.17.1",
+ "serde",
+ "serde_core",
+]
+
+[[package]]
+name = "indoc"
+version = "2.0.7"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "79cf5c93f93228cf8efb3ba362535fb11199ac548a09ce117c9b1adc3030d706"
+dependencies = [
+ "rustversion",
+]
+
+[[package]]
+name = "itoa"
+version = "1.0.18"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8f42a60cbdf9a97f5d2305f08a87dc4e09308d1276d28c869c684d7777685682"
+
+[[package]]
+name = "js-sys"
+version = "0.3.99"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "142bc4740e452c1e57ade0cbc129f139c9093e354346f0872ef985f4f5cf5f11"
+dependencies = [
+ "cfg-if",
+ "futures-util",
+ "once_cell",
+ "wasm-bindgen",
+]
+
+[[package]]
+name = "leb128fmt"
+version = "0.1.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "09edd9e8b54e49e587e4f6295a7d29c3ea94d469cb40ab8ca70b288248a81db2"
+
+[[package]]
+name = "libc"
+version = "0.2.186"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "68ab91017fe16c622486840e4c83c9a37afeff978bd239b5293d61ece587de66"
+
+[[package]]
+name = "log"
+version = "0.4.29"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5e5032e24019045c762d3c0f28f5b6b8bbf38563a65908389bf7978758920897"
+
+[[package]]
+name = "matrixmultiply"
+version = "0.3.10"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a06de3016e9fae57a36fd14dba131fccf49f74b40b7fbdb472f96e361ec71a08"
+dependencies = [
+ "autocfg",
+ "rawpointer",
+]
+
+[[package]]
+name = "memchr"
+version = "2.8.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f8ca58f447f06ed17d5fc4043ce1b10dd205e060fb3ce5b979b8ed8e59ff3f79"
+
+[[package]]
+name = "memoffset"
+version = "0.9.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "488016bfae457b036d996092f6cb448677611ce4449e970ceaf42695203f218a"
+dependencies = [
+ "autocfg",
+]
+
+[[package]]
+name = "ndarray"
+version = "0.16.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "882ed72dce9365842bf196bdeedf5055305f11fc8c03dee7bb0194a6cad34841"
+dependencies = [
+ "matrixmultiply",
+ "num-complex",
+ "num-integer",
+ "num-traits",
+ "portable-atomic",
+ "portable-atomic-util",
+ "rawpointer",
+]
+
+[[package]]
+name = "ndarray"
+version = "0.17.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "520080814a7a6b4a6e9070823bb24b4531daac8c4627e08ba5de8c5ef2f2752d"
+dependencies = [
+ "matrixmultiply",
+ "num-complex",
+ "num-integer",
+ "num-traits",
+ "portable-atomic",
+ "portable-atomic-util",
+ "rawpointer",
+ "serde",
+]
+
+[[package]]
+name = "num-complex"
+version = "0.4.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "73f88a1307638156682bada9d7604135552957b7818057dcef22705b4d509495"
+dependencies = [
+ "num-traits",
+]
+
+[[package]]
+name = "num-integer"
+version = "0.1.46"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7969661fd2958a5cb096e56c8e1ad0444ac2bbcd0061bd28660485a44879858f"
+dependencies = [
+ "num-traits",
+]
+
+[[package]]
+name = "num-traits"
+version = "0.2.19"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "071dfc062690e90b734c0b2273ce72ad0ffa95f0c74596bc250dcfd960262841"
+dependencies = [
+ "autocfg",
+]
+
+[[package]]
+name = "numpy"
+version = "0.22.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "edb929bc0da91a4d85ed6c0a84deaa53d411abfb387fc271124f91bf6b89f14e"
+dependencies = [
+ "libc",
+ "ndarray 0.16.1",
+ "num-complex",
+ "num-integer",
+ "num-traits",
+ "pyo3",
+ "rustc-hash",
+]
+
+[[package]]
+name = "once_cell"
+version = "1.21.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9f7c3e4beb33f85d45ae3e3a1792185706c8e16d043238c593331cc7cd313b50"
+
+[[package]]
+name = "pin-project-lite"
+version = "0.2.17"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a89322df9ebe1c1578d689c92318e070967d1042b512afbe49518723f4e6d5cd"
+
+[[package]]
+name = "portable-atomic"
+version = "1.13.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c33a9471896f1c69cecef8d20cbe2f7accd12527ce60845ff44c153bb2a21b49"
+
+[[package]]
+name = "portable-atomic-util"
+version = "0.2.7"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c2a106d1259c23fac8e543272398ae0e3c0b8d33c88ed73d0cc71b0f1d902618"
+dependencies = [
+ "portable-atomic",
+]
+
+[[package]]
+name = "prettyplease"
+version = "0.2.37"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "479ca8adacdd7ce8f1fb39ce9ecccbfe93a3f1344b3d0d97f20bc0196208f62b"
+dependencies = [
+ "proc-macro2",
+ "syn",
+]
+
+[[package]]
+name = "proc-macro2"
+version = "1.0.106"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8fd00f0bb2e90d81d1044c2b32617f68fcb9fa3bb7640c23e9c748e53fb30934"
+dependencies = [
+ "unicode-ident",
+]
+
+[[package]]
+name = "pyo3"
+version = "0.22.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f402062616ab18202ae8319da13fa4279883a2b8a9d9f83f20dbade813ce1884"
+dependencies = [
+ "cfg-if",
+ "indoc",
+ "libc",
+ "memoffset",
+ "once_cell",
+ "portable-atomic",
+ "pyo3-build-config",
+ "pyo3-ffi",
+ "pyo3-macros",
+ "unindent",
+]
+
+[[package]]
+name = "pyo3-build-config"
+version = "0.22.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "b14b5775b5ff446dd1056212d778012cbe8a0fbffd368029fd9e25b514479c38"
+dependencies = [
+ "once_cell",
+ "target-lexicon",
+]
+
+[[package]]
+name = "pyo3-ffi"
+version = "0.22.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9ab5bcf04a2cdcbb50c7d6105de943f543f9ed92af55818fd17b660390fc8636"
+dependencies = [
+ "libc",
+ "pyo3-build-config",
+]
+
+[[package]]
+name = "pyo3-macros"
+version = "0.22.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "0fd24d897903a9e6d80b968368a34e1525aeb719d568dba8b3d4bfa5dc67d453"
+dependencies = [
+ "proc-macro2",
+ "pyo3-macros-backend",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "pyo3-macros-backend"
+version = "0.22.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "36c011a03ba1e50152b4b394b479826cad97e7a21eb52df179cd91ac411cbfbe"
+dependencies = [
+ "heck",
+ "proc-macro2",
+ "pyo3-build-config",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "quote"
+version = "1.0.45"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "41f2619966050689382d2b44f664f4bc593e129785a36d6ee376ddf37259b924"
+dependencies = [
+ "proc-macro2",
+]
+
+[[package]]
+name = "r-efi"
+version = "6.0.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f8dcc9c7d52a811697d2151c701e0d08956f92b0e24136cf4cf27b57a6a0d9bf"
+
+[[package]]
+name = "rawpointer"
+version = "0.2.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "60a357793950651c4ed0f3f52338f53b2f809f32d83a07f72909fa13e4c6c1e3"
+
+[[package]]
+name = "rustc-hash"
+version = "1.1.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
+
+[[package]]
+name = "rustversion"
+version = "1.0.22"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "b39cdef0fa800fc44525c84ccb54a029961a8215f9619753635a9c0d2538d46d"
+
+[[package]]
+name = "semver"
+version = "1.0.28"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8a7852d02fc848982e0c167ef163aaff9cd91dc640ba85e263cb1ce46fae51cd"
+
+[[package]]
+name = "serde"
+version = "1.0.228"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9a8e94ea7f378bd32cbbd37198a4a91436180c5bb472411e48b5ec2e2124ae9e"
+dependencies = [
+ "serde_core",
+ "serde_derive",
+]
+
+[[package]]
+name = "serde_core"
+version = "1.0.228"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "41d385c7d4ca58e59fc732af25c3983b67ac852c1a25000afe1175de458b67ad"
+dependencies = [
+ "serde_derive",
+]
+
+[[package]]
+name = "serde_derive"
+version = "1.0.228"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d540f220d3187173da220f885ab66608367b6574e925011a9353e4badda91d79"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "serde_json"
+version = "1.0.150"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e8014e44b4736ed0538adeecded0fce2a272f22dc9578a7eb6b2d9993c74cfb9"
+dependencies = [
+ "itoa",
+ "memchr",
+ "serde",
+ "serde_core",
+ "zmij",
+]
+
+[[package]]
+name = "shlex"
+version = "1.3.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "0fda2ff0d084019ba4d7c6f371c95d8fd75ce3524c3cb8fb653a3023f6323e64"
+
+[[package]]
+name = "slab"
+version = "0.4.12"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "0c790de23124f9ab44544d7ac05d60440adc586479ce501c1d6d7da3cd8c9cf5"
+
+[[package]]
+name = "static_assertions"
+version = "1.1.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a2eb9349b6444b326872e140eb1cf5e7c522154d69e7a0ffb0fb81c06b37543f"
+
+[[package]]
+name = "syn"
+version = "2.0.117"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e665b8803e7b1d2a727f4023456bbbbe74da67099c585258af0ad9c5013b9b99"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "unicode-ident",
+]
+
+[[package]]
+name = "target-lexicon"
+version = "0.12.16"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "61c41af27dd6d1e27b1b16b489db798443478cef1f06a660c96db617ba5de3b1"
+
+[[package]]
+name = "thiserror"
+version = "2.0.18"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "4288b5bcbc7920c07a1149a35cf9590a2aa808e0bc1eafaade0b80947865fbc4"
+dependencies = [
+ "thiserror-impl",
+]
+
+[[package]]
+name = "thiserror-impl"
+version = "2.0.18"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ebc4ee7f67670e9b64d05fa4253e753e016c6c95ff35b89b7941d6b856dec1d5"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "tracing"
+version = "0.1.44"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "63e71662fa4b2a2c3a26f570f037eb95bb1f85397f3cd8076caed2f026a6d100"
+dependencies = [
+ "pin-project-lite",
+ "tracing-attributes",
+ "tracing-core",
+]
+
+[[package]]
+name = "tracing-attributes"
+version = "0.1.31"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7490cfa5ec963746568740651ac6781f701c9c5ea257c58e057f3ba8cf69e8da"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "tracing-core"
+version = "0.1.36"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "db97caf9d906fbde555dd62fa95ddba9eecfd14cb388e4f491a66d74cd5fb79a"
+dependencies = [
+ "once_cell",
+]
+
+[[package]]
+name = "unicode-ident"
+version = "1.0.24"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e6e4313cd5fcd3dad5cafa179702e2b244f760991f45397d14d4ebf38247da75"
+
+[[package]]
+name = "unicode-xid"
+version = "0.2.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ebc1c04c71510c7f702b52b7c350734c9ff1295c464a03335b00bb84fc54f853"
+
+[[package]]
+name = "unindent"
+version = "0.2.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7264e107f553ccae879d21fbea1d6724ac785e8c3bfc762137959b5802826ef3"
+
+[[package]]
+name = "uuid"
+version = "1.23.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ddd74a9687298c6858e9b88ec8935ec45d22e8fd5e6394fa1bd4e99a87789c76"
+dependencies = [
+ "getrandom",
+ "js-sys",
+ "serde_core",
+ "wasm-bindgen",
+]
+
+[[package]]
+name = "wasip2"
+version = "1.0.3+wasi-0.2.9"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "20064672db26d7cdc89c7798c48a0fdfac8213434a1186e5ef29fd560ae223d6"
+dependencies = [
+ "wit-bindgen 0.57.1",
+]
+
+[[package]]
+name = "wasip3"
+version = "0.4.0+wasi-0.3.0-rc-2026-01-06"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5428f8bf88ea5ddc08faddef2ac4a67e390b88186c703ce6dbd955e1c145aca5"
+dependencies = [
+ "wit-bindgen 0.51.0",
+]
+
+[[package]]
+name = "wasm-bindgen"
+version = "0.2.122"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "3ed04576f974d2b2fba0f38c51dbc5518011e38c36bf1143164be765528fd409"
+dependencies = [
+ "cfg-if",
+ "once_cell",
+ "rustversion",
+ "wasm-bindgen-macro",
+ "wasm-bindgen-shared",
+]
+
+[[package]]
+name = "wasm-bindgen-macro"
+version = "0.2.122"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "916151b09da36bd82f6615cbf3a419e2f0ba23a03c6160e8e92eb6bd4aa1dec6"
+dependencies = [
+ "quote",
+ "wasm-bindgen-macro-support",
+]
+
+[[package]]
+name = "wasm-bindgen-macro-support"
+version = "0.2.122"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "299047362ccbfce148b67ab7e73349f77748e00c8296f9542adfad2ad82c5c5e"
+dependencies = [
+ "bumpalo",
+ "proc-macro2",
+ "quote",
+ "syn",
+ "wasm-bindgen-shared",
+]
+
+[[package]]
+name = "wasm-bindgen-shared"
+version = "0.2.122"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9a929b2c61f11ba3e9bc35b50c1f25cb38e0e892c0c231ae2b8cf78d5dad4437"
+dependencies = [
+ "unicode-ident",
+]
+
+[[package]]
+name = "wasm-encoder"
+version = "0.244.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "990065f2fe63003fe337b932cfb5e3b80e0b4d0f5ff650e6985b1048f62c8319"
+dependencies = [
+ "leb128fmt",
+ "wasmparser",
+]
+
+[[package]]
+name = "wasm-metadata"
+version = "0.244.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "bb0e353e6a2fbdc176932bbaab493762eb1255a7900fe0fea1a2f96c296cc909"
+dependencies = [
+ "anyhow",
+ "indexmap",
+ "wasm-encoder",
+ "wasmparser",
+]
+
+[[package]]
+name = "wasmparser"
+version = "0.244.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "47b807c72e1bac69382b3a6fb3dbe8ea4c0ed87ff5629b8685ae6b9a611028fe"
+dependencies = [
+ "bitflags",
+ "hashbrown 0.15.5",
+ "indexmap",
+ "semver",
+]
+
+[[package]]
+name = "wifi-densepose-bfld"
+version = "0.3.0"
+dependencies = [
+ "blake3",
+ "crc",
+ "serde",
+ "serde_json",
+ "static_assertions",
+ "thiserror",
+]
+
+[[package]]
+name = "wifi-densepose-core"
+version = "0.3.0"
+dependencies = [
+ "chrono",
+ "ndarray 0.17.2",
+ "num-complex",
+ "num-traits",
+ "thiserror",
+ "uuid",
+]
+
+[[package]]
+name = "wifi-densepose-py"
+version = "2.0.0-alpha.1"
+dependencies = [
+ "numpy",
+ "pyo3",
+ "wifi-densepose-bfld",
+ "wifi-densepose-core",
+ "wifi-densepose-vitals",
+]
+
+[[package]]
+name = "wifi-densepose-vitals"
+version = "0.3.0"
+dependencies = [
+ "serde",
+ "tracing",
+]
+
+[[package]]
+name = "windows-core"
+version = "0.62.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "b8e83a14d34d0623b51dce9581199302a221863196a1dde71a7663a4c2be9deb"
+dependencies = [
+ "windows-implement",
+ "windows-interface",
+ "windows-link",
+ "windows-result",
+ "windows-strings",
+]
+
+[[package]]
+name = "windows-implement"
+version = "0.60.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "053e2e040ab57b9dc951b72c264860db7eb3b0200ba345b4e4c3b14f67855ddf"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "windows-interface"
+version = "0.59.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "3f316c4a2570ba26bbec722032c4099d8c8bc095efccdc15688708623367e358"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "windows-link"
+version = "0.2.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f0805222e57f7521d6a62e36fa9163bc891acd422f971defe97d64e70d0a4fe5"
+
+[[package]]
+name = "windows-result"
+version = "0.4.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7781fa89eaf60850ac3d2da7af8e5242a5ea78d1a11c49bf2910bb5a73853eb5"
+dependencies = [
+ "windows-link",
+]
+
+[[package]]
+name = "windows-strings"
+version = "0.5.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7837d08f69c77cf6b07689544538e017c1bfcf57e34b4c0ff58e6c2cd3b37091"
+dependencies = [
+ "windows-link",
+]
+
+[[package]]
+name = "wit-bindgen"
+version = "0.51.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d7249219f66ced02969388cf2bb044a09756a083d0fab1e566056b04d9fbcaa5"
+dependencies = [
+ "wit-bindgen-rust-macro",
+]
+
+[[package]]
+name = "wit-bindgen"
+version = "0.57.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "1ebf944e87a7c253233ad6766e082e3cd714b5d03812acc24c318f549614536e"
+
+[[package]]
+name = "wit-bindgen-core"
+version = "0.51.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ea61de684c3ea68cb082b7a88508a8b27fcc8b797d738bfc99a82facf1d752dc"
+dependencies = [
+ "anyhow",
+ "heck",
+ "wit-parser",
+]
+
+[[package]]
+name = "wit-bindgen-rust"
+version = "0.51.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "b7c566e0f4b284dd6561c786d9cb0142da491f46a9fbed79ea69cdad5db17f21"
+dependencies = [
+ "anyhow",
+ "heck",
+ "indexmap",
+ "prettyplease",
+ "syn",
+ "wasm-metadata",
+ "wit-bindgen-core",
+ "wit-component",
+]
+
+[[package]]
+name = "wit-bindgen-rust-macro"
+version = "0.51.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "0c0f9bfd77e6a48eccf51359e3ae77140a7f50b1e2ebfe62422d8afdaffab17a"
+dependencies = [
+ "anyhow",
+ "prettyplease",
+ "proc-macro2",
+ "quote",
+ "syn",
+ "wit-bindgen-core",
+ "wit-bindgen-rust",
+]
+
+[[package]]
+name = "wit-component"
+version = "0.244.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9d66ea20e9553b30172b5e831994e35fbde2d165325bec84fc43dbf6f4eb9cb2"
+dependencies = [
+ "anyhow",
+ "bitflags",
+ "indexmap",
+ "log",
+ "serde",
+ "serde_derive",
+ "serde_json",
+ "wasm-encoder",
+ "wasm-metadata",
+ "wasmparser",
+ "wit-parser",
+]
+
+[[package]]
+name = "wit-parser"
+version = "0.244.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ecc8ac4bc1dc3381b7f59c34f00b67e18f910c2c0f50015669dde7def656a736"
+dependencies = [
+ "anyhow",
+ "id-arena",
+ "indexmap",
+ "log",
+ "semver",
+ "serde",
+ "serde_derive",
+ "serde_json",
+ "unicode-xid",
+ "wasmparser",
+]
+
+[[package]]
+name = "zmij"
+version = "1.0.21"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "b8848ee67ecc8aedbaf3e4122217aff892639231befc6a1b58d29fff4c2cabaa"

python/Cargo.toml

@@ -0,0 +1,55 @@
+[package]
+name = "wifi-densepose-py"
+version = "2.0.0-alpha.1"
+# The `python/` crate is intentionally OUTSIDE the `v2/` Cargo
+# workspace (ADR-117 §5.2) so maturin's `python-source` + `module-name`
+# config stays self-contained and `cargo test --workspace` in v2/
+# doesn't have to compile pyo3. Hence no `*.workspace = true`
+# inheritance here — every field is local.
+edition = "2021"
+license = "MIT"
+authors = ["rUv <ruv@ruv.net>", "WiFi-DensePose Contributors"]
+description = "PyO3 bindings for the WiFi-DensePose Rust core — ships as the `wifi-densepose` PyPI wheel (ADR-117)"
+repository = "https://github.com/ruvnet/RuView"
+
+# ADR-117 §5.2: the Python wheel's compiled module name is
+# `wifi_densepose._native` (the leading underscore marks it as an internal
+# implementation detail re-exported by the pure-Python facade in
+# `wifi_densepose/__init__.py`). Keeping the name distinct from the crate
+# avoids the maturin gotcha where `wifi_densepose-py` would collide with
+# the user-facing `wifi_densepose` package on import.
+[lib]
+name = "wifi_densepose_native"
+crate-type = ["cdylib", "rlib"]
+path = "src/lib.rs"
+
+[dependencies]
+# PyO3 with abi3-py310 — one compiled binary covers Python 3.10, 3.11,
+# 3.12, 3.13, and any future 3.x that keeps the stable ABI (ADR-117 §5.4).
+# Without abi3 we'd need a separate wheel per Python minor version × OS
+# × arch, blowing up the cibuildwheel matrix.
+pyo3 = { version = "0.22", features = ["extension-module", "abi3-py310"] }
+
+# Re-export the Rust core types through PyO3 #[pyclass] wrappers in P2.
+# Default-features-off keeps the wheel size below the 5 MB ADR-117 §5.4
+# budget by avoiding optional BLAS/openssl chains.
+wifi-densepose-core = { version = "0.3.0", path = "../v2/crates/wifi-densepose-core" }
+
+# P3 — vitals extraction (HR/BR via the 4-stage pipeline). Pure-sync;
+# no tokio (Q5 audited 2026-05-24); safe to wrap in py.allow_threads.
+wifi-densepose-vitals = { version = "0.3.0", path = "../v2/crates/wifi-densepose-vitals" }
+
+# ADR-118 BFLD core — PrivacyClass enum + identity_risk scoring +
+# privacy gate. Exposed to Python via bindings/privacy_gate.rs so the
+# c6-presence-watcher.py runtime (currently using a Python port of the
+# same semantics) can switch to the canonical Rust implementation when
+# the wheel ships. ADR-125 §2.1.d invariant enforcement lives here.
+wifi-densepose-bfld = { version = "0.3.0", path = "../v2/crates/wifi-densepose-bfld" }
+
+# numpy bridge — needed for P3.5 BfldFrame (Complex64 ndarray) and for
+# the future P3 CsiFrame numpy round-trip.
+numpy = "0.22"
+
+[dev-dependencies]
+# Doc-test infrastructure for the Python-facing examples in the bound
+# Rust functions. Lands properly in P2 once #[pyfunction]s exist to test.

python/README.md

@@ -0,0 +1,143 @@
+# wifi-densepose
+
+[![PyPI version](https://img.shields.io/pypi/v/wifi-densepose.svg)](https://pypi.org/project/wifi-densepose/)
+[![Python](https://img.shields.io/pypi/pyversions/wifi-densepose.svg)](https://pypi.org/project/wifi-densepose/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
+
+**Detect human presence, count people, read breathing and heart rate, and
+estimate skeletal pose — using only the WiFi signal already in your home.**
+
+No cameras. No wearables. Works through walls and in the dark.
+
+`wifi-densepose` is the Python binding for the [RuView](https://github.com/ruvnet/RuView)
+sensing stack: a Rust core that turns the Channel State Information (CSI)
+emitted by ordinary WiFi chips into ambient-intelligence signals. The wheel
+ships compiled DSP for fast offline analysis, plus an opt-in Python client
+for talking to a live RuView sensing-server over WebSocket or MQTT.
+
+## Features
+
+- **17-keypoint pose** — full-body skeletal estimate from WiFi CSI, no camera
+- **Vital signs** — respiratory rate (6–30 BPM) and heart rate (40–120 BPM)
+  with a confidence score and clinical-grade / degraded / unreliable status
+- **Presence, person count, fall detection, motion** — fused outputs from
+  the same CSI stream
+- **10 semantic primitives** (HA-MIND) — someone-sleeping, possible-distress,
+  room-active, bathroom-occupied, fall-risk-elevated, bed-exit, … — ready
+  to wire into Home Assistant or Apple Home automations
+- **Beamforming Feedback (BFLD) support** — 802.11ac/ax/be compressed feedback
+  matrices on top of the receiver-side CSI path
+- **GIL-releasing DSP** — extract loops run with the GIL released, so a
+  tokio-backed web server can call into the pipeline without stalling its
+  event loop
+- **Tiny wheel** — ~240 KB compiled (one binary per OS/arch covers Python
+  3.10+ via the stable ABI)
+
+## Install
+
+```bash
+pip install wifi-densepose                 # core DSP only
+pip install "wifi-densepose[client]"       # + WebSocket/MQTT clients
+```
+
+Wheels are published for Linux (x86_64, aarch64), macOS (x86_64, arm64), and
+Windows (amd64).
+
+## Usage
+
+### Extract breathing rate from a CSI stream
+
+```python
+from wifi_densepose import BreathingExtractor
+
+br = BreathingExtractor.esp32_default()     # 56 subcarriers @ 100 Hz, 30s window
+
+for residuals, weights in your_csi_source:  # one frame at a time
+    est = br.extract(residuals=residuals, weights=weights)
+    if est is not None:
+        print(f"{est.value_bpm:.1f} BPM  (confidence={est.confidence:.2f})")
+```
+
+Heart rate is the same shape — `HeartRateExtractor.esp32_default()` with a
+0.8–2.0 Hz band-pass and a 15-second window.
+
+### Subscribe to a live sensing-server
+
+```python
+import asyncio
+from wifi_densepose.client import SensingClient, EdgeVitalsMessage
+
+async def main():
+    async with SensingClient("ws://your-ruview-node:8765/ws/sensing") as c:
+        async for msg in c.stream():
+            if isinstance(msg, EdgeVitalsMessage):
+                print(msg.presence, msg.breathing_rate_bpm, msg.heartrate_bpm)
+
+asyncio.run(main())
+```
+
+### React to Home Assistant semantic primitives
+
+```python
+from wifi_densepose.client import (
+    RuViewMqttClient, SemanticPrimitive, SemanticPrimitiveListener,
+)
+
+listener = SemanticPrimitiveListener()
+listener.on(SemanticPrimitive.BedExit, lambda e: print("bed exit:", e.node_id))
+listener.on(SemanticPrimitive.PossibleDistress, lambda e: alert(e))
+
+client = RuViewMqttClient(broker_host="homeassistant.local")
+client.on_message(
+    "homeassistant/+/wifi_densepose_+/+/state",
+    listener.handle_mqtt_message,
+)
+client.start()
+client.wait_connected()
+```
+
+### Decode 802.11ax beamforming feedback
+
+```python
+import numpy as np
+from wifi_densepose import BfldFrame, BfldKind
+
+# Parse compressed BFR from a Wireshark capture into a Complex64 ndarray ...
+fb = np.zeros((2, 1, 996), dtype=np.complex64)  # Nr=2 Nc=1 Nsc=996 for HE80
+
+frame = BfldFrame.from_compressed_feedback(
+    timestamp_ms=ts,
+    sounding_index=seq,
+    sta_mac="aa:bb:cc:dd:ee:ff",
+    kind=BfldKind.CompressedHE80,
+    feedback_matrix=fb,
+)
+print(frame.n_subcarriers, frame.mean_amplitude)
+```
+
+## Hardware
+
+Works with any WiFi chip that exposes CSI. Reference setups (ESP-IDF firmware,
+build scripts, witness-verified test bundles) are in the
+[RuView repo](https://github.com/ruvnet/RuView):
+
+| Device | Cost | Role |
+|---|---|---|
+| ESP32-S3 (8MB flash) | ~$9 | WiFi CSI sensing node |
+| ESP32-S3 SuperMini (4MB) | ~$6 | WiFi CSI (compact) |
+| ESP32-C6 + Seeed MR60BHA2 | ~$15 | mmWave HR/BR/presence add-on |
+
+The legacy v1 line (Wi-Pose-style FastAPI server) is end-of-life;
+`wifi-densepose==1.99.0` is a tombstone that raises `ImportError` pointing
+to v2 with a migration URL.
+
+## Links
+
+- **Repository** — https://github.com/ruvnet/RuView
+- **Modernization plan** — [ADR-117](https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-117-pip-wifi-densepose-modernization.md)
+- **Home Assistant integration** — [ADR-115](https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-115-home-assistant-integration.md)
+- **Issues** — https://github.com/ruvnet/RuView/issues
+
+## License
+
+MIT.

python/bench/test_bench_bfld_and_ws.py

@@ -0,0 +1,111 @@
+"""ADR-117 hardening sweep — Benchmarks for the P3.5 numpy bridge
+and the P4 WS decoder.
+
+The numpy bridge is the most-likely candidate for a hidden allocation
+hot-spot: every `BfldFrame.from_compressed_feedback()` call copies the
+ndarray into a Vec<Complex64>. Confirm the per-frame cost is
+acceptable for the BFR cadence the AP emits (typically a few
+hundred per second, not thousands).
+
+The WS decoder runs once per frame the sensing-server emits. At
+worst-case ~100 Hz × number-of-subscribers, the decoder budget is
+tight; make sure dataclass construction doesn't dominate.
+"""
+
+from __future__ import annotations
+
+import json
+
+import numpy as np
+import pytest
+
+from wifi_densepose import BfldFrame, BfldKind
+
+
+@pytest.mark.parametrize("kind,shape", [
+    (BfldKind.UncompressedHT20, (1, 1, 52)),
+    (BfldKind.CompressedHE20, (2, 1, 242)),
+    (BfldKind.CompressedHE80, (2, 1, 996)),
+    (BfldKind.CompressedHE160, (2, 2, 1992)),
+])
+def test_bfld_from_compressed_feedback(benchmark, kind: BfldKind, shape: tuple[int, int, int]) -> None:
+    rng = np.random.default_rng(seed=42)
+    fb = (rng.standard_normal(shape) + 1j * rng.standard_normal(shape)).astype(np.complex128)
+
+    def _build():
+        return BfldFrame.from_compressed_feedback(
+            timestamp_ms=0,
+            sounding_index=0,
+            sta_mac="aa:bb:cc:dd:ee:ff",
+            kind=kind,
+            feedback_matrix=fb,
+        )
+
+    benchmark(_build)
+
+
+def test_bfld_feedback_matrix_roundtrip(benchmark) -> None:
+    """How expensive is the numpy-out round-trip? Used by clients
+    that want to do further analysis in numpy after constructing
+    the frame."""
+    rng = np.random.default_rng(seed=42)
+    fb = (rng.standard_normal((2, 1, 996)) + 1j * rng.standard_normal((2, 1, 996))).astype(np.complex128)
+    frame = BfldFrame.from_compressed_feedback(
+        timestamp_ms=0,
+        sounding_index=0,
+        sta_mac="aa:bb:cc:dd:ee:ff",
+        kind=BfldKind.CompressedHE80,
+        feedback_matrix=fb,
+    )
+    benchmark(frame.feedback_matrix)
+
+
+# ─── WS decoder ──────────────────────────────────────────────────────
+
+
+_EDGE_VITALS_FRAME = json.dumps({
+    "type": "edge_vitals",
+    "node_id": "bench-node",
+    "presence": True,
+    "fall_detected": False,
+    "motion": 0.34,
+    "breathing_rate_bpm": 14.2,
+    "heartrate_bpm": 72.5,
+    "n_persons": 1,
+    "motion_energy": 0.04,
+    "presence_score": 0.91,
+    "rssi": -42.0,
+})
+
+
+def test_ws_decoder_edge_vitals(benchmark) -> None:
+    from wifi_densepose.client.ws import _decode
+
+    def _decode_one():
+        return _decode(_EDGE_VITALS_FRAME)
+
+    benchmark(_decode_one)
+
+
+_POSE_FRAME = json.dumps({
+    "type": "pose_data",
+    "node_id": "bench-node",
+    "timestamp": 1700000000.5,
+    "persons": [
+        {"id": i, "keypoints": [[0.5, 0.5, 0.9] for _ in range(17)]}
+        for i in range(3)
+    ],
+    "confidence": 0.85,
+})
+
+
+def test_ws_decoder_pose_data(benchmark) -> None:
+    """The pose_data frame is typically the largest one the server
+    emits — bench it separately so a future blob-size regression
+    in the persons array is visible."""
+    from wifi_densepose.client.ws import _decode
+
+    def _decode_one():
+        return _decode(_POSE_FRAME)
+
+    benchmark(_decode_one)

python/bench/test_bench_vitals.py

@@ -0,0 +1,85 @@
+"""ADR-117 hardening sweep — Benchmarks for the P3 vitals hot paths.
+
+Targets the ESP32 production rate: 100 Hz × 56 subcarriers, which is
+what `BreathingExtractor.esp32_default()` is tuned for. The bench
+asserts the *per-extract* cost is comfortably below 10 ms — at 100 Hz
+that's the entire frame budget, so anything above 10 ms means the
+Python binding would be the bottleneck instead of the radio.
+
+Run with:
+    pytest python/bench/ --benchmark-only
+
+The benchmarks are skipped by default (`addopts` in pyproject.toml
+doesn't include them) — they live in a sibling `bench/` directory
+so the main test run stays fast.
+"""
+
+from __future__ import annotations
+
+import math
+from random import Random
+
+import pytest
+
+from wifi_densepose import BreathingExtractor, HeartRateExtractor
+
+
+def _synth_frame(n_subcarriers: int, sample_rate: float, t: float, freq_hz: float, rng: Random) -> tuple[list[float], list[float]]:
+    """Build one ESP32-shape frame at time `t`: sine at `freq_hz` plus
+    tiny per-subcarrier noise."""
+    base = math.sin(2.0 * math.pi * freq_hz * t)
+    residuals = [base + rng.gauss(0.0, 0.01) for _ in range(n_subcarriers)]
+    weights = [1.0] * n_subcarriers
+    return residuals, weights
+
+
+def test_breathing_extract_per_frame_cost(benchmark) -> None:
+    """One BreathingExtractor.extract() at ESP32 defaults should
+    finish well under 10 ms — that's the 100 Hz frame budget."""
+    br = BreathingExtractor.esp32_default()
+    rng = Random(42)
+    # Pre-fill ~25 seconds of history so the bench measures the
+    # steady-state cost, not the cold-start cost.
+    for i in range(2500):
+        residuals, weights = _synth_frame(56, 100.0, i / 100.0, 0.25, rng)
+        br.extract(residuals=residuals, weights=weights)
+
+    def _one_frame():
+        residuals, weights = _synth_frame(56, 100.0, 30.0, 0.25, rng)
+        return br.extract(residuals=residuals, weights=weights)
+
+    benchmark(_one_frame)
+
+
+def test_heart_rate_extract_per_frame_cost(benchmark) -> None:
+    """One HeartRateExtractor.extract() at ESP32 defaults — same 10 ms
+    target."""
+    hr = HeartRateExtractor.esp32_default()
+    rng = Random(43)
+    for i in range(1500):
+        residuals, weights = _synth_frame(56, 100.0, i / 100.0, 1.2, rng)
+        hr.extract(residuals=residuals, weights=weights)
+
+    def _one_frame():
+        residuals, weights = _synth_frame(56, 100.0, 16.0, 1.2, rng)
+        return hr.extract(residuals=residuals, weights=weights)
+
+    benchmark(_one_frame)
+
+
+@pytest.mark.parametrize("n_subcarriers", [56, 114, 242])
+def test_breathing_extract_scaling(benchmark, n_subcarriers: int) -> None:
+    """Sanity check: cost should scale roughly linearly with the
+    subcarrier count. Catches accidental O(n^2) regressions."""
+    sample_rate = 100.0
+    br = BreathingExtractor(n_subcarriers, sample_rate, 30.0)
+    rng = Random(n_subcarriers)
+    for i in range(2500):
+        residuals, weights = _synth_frame(n_subcarriers, sample_rate, i / sample_rate, 0.25, rng)
+        br.extract(residuals=residuals, weights=weights)
+
+    def _one_frame():
+        residuals, weights = _synth_frame(n_subcarriers, sample_rate, 30.0, 0.25, rng)
+        return br.extract(residuals=residuals, weights=weights)
+
+    benchmark(_one_frame)

python/pyproject.toml

@@ -0,0 +1,99 @@
+# ADR-117 — `wifi-densepose` v2.x PyPI wheel
+#
+# This is the PyO3+maturin replacement for the legacy pure-Python
+# `wifi-densepose==1.1.0` (last release 2025-06-07). One compiled
+# extension module per OS/arch covers Python 3.10–3.13 via abi3.
+
+[build-system]
+requires = ["maturin>=1.7,<2.0"]
+build-backend = "maturin"
+
+[project]
+name = "wifi-densepose"
+version = "2.0.0a1"
+description = "WiFi-based human pose estimation, vital sign extraction, and ambient intelligence from Channel State Information (CSI). PyO3 bindings for the Rust core."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "MIT" }
+authors = [
+    { name = "rUv", email = "ruv@ruv.net" },
+]
+keywords = [
+    "wifi", "csi", "pose-estimation", "vital-signs",
+    "biometric", "ambient-intelligence", "home-assistant", "matter",
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Intended Audience :: Science/Research",
+    "License :: OSI Approved :: MIT License",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Rust",
+    "Topic :: Scientific/Engineering",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+    "Topic :: Scientific/Engineering :: Image Recognition",
+    "Topic :: System :: Hardware",
+    "Typing :: Typed",
+]
+dependencies = []
+
+[project.optional-dependencies]
+# ADR-117 §5.6 — pure-Python WS/MQTT client. Lands in P4.
+client = [
+    "websockets>=12.0",
+    "paho-mqtt>=2.1",
+]
+# Developer dependencies for running the test suite + lint.
+dev = [
+    "pytest>=8.0",
+    "pytest-asyncio>=0.23",
+    "ruff>=0.7",
+    "mypy>=1.13",
+]
+
+[project.urls]
+Homepage = "https://github.com/ruvnet/RuView"
+Repository = "https://github.com/ruvnet/RuView"
+Issues = "https://github.com/ruvnet/RuView/issues"
+Documentation = "https://github.com/ruvnet/RuView/tree/main/docs"
+"ADR-117 (modernization plan)" = "https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-117-pip-wifi-densepose-modernization.md"
+"Release notes (v0.7.0)" = "https://github.com/ruvnet/RuView/blob/main/docs/releases/v0.7.0-mqtt-matter.md"
+
+# Console-script entry points wired up in P5 once the CLI shim exists.
+# [project.scripts]
+# wifi-densepose = "wifi_densepose.cli:main"
+
+[tool.maturin]
+# Layout: pyproject.toml + Cargo.toml live at `python/`; the
+# python-source directory `wifi_densepose/` is a sibling (i.e. at
+# `python/wifi_densepose/`). `python-source = "."` tells maturin to
+# look for packages directly under the project root.
+python-source = "."
+module-name = "wifi_densepose._native"
+features = ["pyo3/extension-module"]
+# Strip debug symbols for smaller release wheels (ADR-117 §5.4 5 MB budget).
+strip = true
+
+[tool.pytest.ini_options]
+minversion = "8.0"
+testpaths = ["tests"]
+addopts = "-v --strict-markers"
+asyncio_mode = "auto"
+
+[tool.ruff]
+line-length = 100
+target-version = "py310"
+
+[tool.ruff.lint]
+select = ["E", "F", "W", "I", "UP", "B"]
+
+[tool.mypy]
+python_version = "3.10"
+strict = true
+warn_unused_ignores = true
+warn_redundant_casts = true

python/ruview-meta/README.md

@@ -0,0 +1,58 @@
+# ruview
+
+**Ambient intelligence from WiFi CSI.** Detect human presence, count
+people, read breathing and heart rate, and estimate skeletal pose —
+using only the WiFi signal already in your home. No cameras. No
+wearables. Works through walls and in the dark.
+
+`ruview` is the brand-facing meta-package for the
+[RuView](https://github.com/ruvnet/RuView) sensing stack. It installs
+the compiled PyO3 wheel published as
+[`wifi-densepose`](https://pypi.org/project/wifi-densepose/) and
+re-exports its full API under the `ruview` namespace — so you can
+write either of these and they do the same thing:
+
+```python
+from ruview import BreathingExtractor, SensingClient
+from wifi_densepose import BreathingExtractor, SensingClient
+```
+
+## Install
+
+```bash
+pip install ruview                 # core DSP
+pip install "ruview[client]"       # + WebSocket/MQTT clients
+```
+
+## Usage
+
+```python
+from ruview import BreathingExtractor
+
+br = BreathingExtractor.esp32_default()  # 56 subcarriers @ 100 Hz, 30s window
+for residuals, weights in csi_source:
+    est = br.extract(residuals=residuals, weights=weights)
+    if est is not None:
+        print(f"{est.value_bpm:.1f} BPM  (confidence={est.confidence:.2f})")
+```
+
+Full API + WebSocket / MQTT / Home Assistant integration docs:
+[wifi-densepose on PyPI](https://pypi.org/project/wifi-densepose/).
+
+## Why two PyPI names?
+
+Historic: `wifi-densepose` is the technical / academic name (the
+project started as a WiFi-based DensePose implementation).
+`ruview` is the brand the v2 ambient-intelligence platform ships
+under. Both are the same code. You pick the import that reads
+better in your project.
+
+## Links
+
+- **Repository** — https://github.com/ruvnet/RuView
+- **Modernization plan** — [ADR-117](https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-117-pip-wifi-densepose-modernization.md)
+- **Issues** — https://github.com/ruvnet/RuView/issues
+
+## License
+
+MIT.

python/ruview-meta/pyproject.toml

@@ -0,0 +1,62 @@
+# ADR-117 sibling release — `ruview` meta-package.
+#
+# Pure-Python wheel that re-exports everything from `wifi-densepose`
+# under the alias `ruview`. They're the same code, distributed under
+# two PyPI names so users can `pip install ruview` (the brand) or
+# `pip install wifi-densepose` (the technical name) — both end up
+# with the same compiled DSP available.
+#
+# Build:
+#   cd python/ruview-meta
+#   python -m build
+
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "ruview"
+version = "2.0.0a1"
+description = "RuView — ambient intelligence from WiFi CSI. Meta-package; installs `wifi-densepose` and re-exports it under the `ruview` namespace. See https://github.com/ruvnet/RuView."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "MIT" }
+authors = [{ name = "rUv", email = "ruv@ruv.net" }]
+keywords = [
+    "wifi", "csi", "pose-estimation", "vital-signs",
+    "biometric", "ambient-intelligence", "home-assistant", "matter",
+    "ruview",
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Intended Audience :: Science/Research",
+    "License :: OSI Approved :: MIT License",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Scientific/Engineering",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+    "Typing :: Typed",
+]
+dependencies = [
+    # Pin to the matching v2 release so an alpha-pin `pip install ruview`
+    # always gets a compatible wifi-densepose.
+    "wifi-densepose==2.0.0a1",
+]
+
+[project.optional-dependencies]
+client = ["wifi-densepose[client]==2.0.0a1"]
+
+[project.urls]
+Homepage = "https://github.com/ruvnet/RuView"
+Repository = "https://github.com/ruvnet/RuView"
+Issues = "https://github.com/ruvnet/RuView/issues"
+Documentation = "https://github.com/ruvnet/RuView/tree/main/docs"
+
+[tool.setuptools]
+packages = ["ruview"]
+package-dir = { "" = "src" }

python/ruview-meta/src/ruview/__init__.py

@@ -0,0 +1,50 @@
+"""RuView — ambient intelligence from WiFi CSI.
+
+This package is a thin alias around `wifi-densepose`. Both PyPI names
+ship the same code and the same compiled Rust core; `ruview` is the
+brand-facing name and `wifi-densepose` is the technical name. Pick
+whichever you prefer:
+
+    pip install ruview
+    pip install wifi-densepose
+
+Both make this work:
+
+    from ruview import BreathingExtractor, hello
+    # or equivalently:
+    from wifi_densepose import BreathingExtractor, hello
+
+The actual compiled DSP, the Python facade, and every public class
+live in `wifi_densepose` — `ruview` just re-exports the surface so the
+two names are interchangeable in application code.
+"""
+
+from __future__ import annotations
+
+import wifi_densepose as _wdp
+
+# Re-export everything `wifi_densepose.__all__` declares.
+for _name in _wdp.__all__:
+    globals()[_name] = getattr(_wdp, _name)
+
+# Version + diagnostic fields — surface them under the ruview name
+# too so users can `print(ruview.__rust_version__)` without reaching
+# into the wifi_densepose module.
+__version__: str = _wdp.__version__
+__rust_version__: str = _wdp.__rust_version__
+__rust_build_tag__: str = _wdp.__rust_build_tag__
+__build_features__ = list(_wdp.__build_features__)
+
+# The client sub-package is also aliased for symmetry.
+try:
+    from wifi_densepose import client  # type: ignore[import-not-found]  # noqa: F401
+except ImportError:
+    # client extras not installed — that's fine for the core import.
+    pass
+
+__all__ = list(_wdp.__all__) + [
+    "__version__",
+    "__rust_version__",
+    "__rust_build_tag__",
+    "__build_features__",
+]

python/src/bindings/bfld.rs

@@ -0,0 +1,344 @@
+//! ADR-117 P3.5 — Beamforming Feedback Loop Data (BFLD) bindings.
+//!
+//! BFLD is the transmitter-side, AP-station-loop view of the WiFi
+//! channel — compressed beamforming feedback frames that 802.11ac/ax/be
+//! stations send to the AP per sounding cycle. See ADR-117 §5.7a for
+//! the design rationale and ADR-117 §11.11/12 for open questions.
+//!
+//! **Important**: there is NO Rust ingestion crate for BFLD yet. The
+//! Python types in this module ship with a **stub Rust impl** that
+//! accepts pre-parsed feedback matrices via numpy. When the future
+//! `wifi-densepose-bfld` crate lands, it plugs in here without changing
+//! the Python API.
+//!
+//! Today's user path:
+//!
+//! 1. Capture BFR frames with `tcpdump` / Wireshark + the BFR dissector
+//!    (or via `mac80211` debugfs on Linux 6.10+)
+//! 2. Parse the compressed feedback into a numpy Complex64 ndarray
+//!    `[Nr × Nc × Nsc]` using your favourite Python BFR parser
+//! 3. Construct `BfldFrame.from_compressed_feedback(...)` to hand the
+//!    matrix to RuView
+//!
+//! Tomorrow (post-v2.0): `wifi-densepose-bfld` does steps 1+2 for you.
+
+use pyo3::prelude::*;
+use numpy::{Complex64, PyArray3, PyUntypedArrayMethods, PyReadonlyArray3};
+
+// ─── BfldKind ────────────────────────────────────────────────────────
+
+/// 802.11 PHY variant of the captured BFR frame. Determines the
+/// expected matrix dimensions + the quantization step of the
+/// compressed angles.
+///
+/// Python:
+/// ```python
+/// from wifi_densepose import BfldKind
+/// BfldKind.CompressedHE80   # 802.11ax 80 MHz compressed BFR
+/// ```
+#[pyclass(eq, eq_int, hash, frozen, name = "BfldKind")]
+#[derive(Clone, Copy, PartialEq, Eq, Hash, Debug)]
+pub enum PyBfldKind {
+    CompressedHE20 = 0,
+    CompressedHE40 = 1,
+    CompressedHE80 = 2,
+    CompressedHE160 = 3,
+    UncompressedHT20 = 4,
+    UncompressedHT40 = 5,
+}
+
+#[pymethods]
+impl PyBfldKind {
+    /// Expected number of subcarriers for this BFLD variant.
+    #[getter]
+    fn n_subcarriers(&self) -> usize {
+        match self {
+            Self::CompressedHE20 => 242,
+            Self::CompressedHE40 => 484,
+            Self::CompressedHE80 => 996,
+            Self::CompressedHE160 => 1992,
+            Self::UncompressedHT20 => 52,
+            Self::UncompressedHT40 => 108,
+        }
+    }
+
+    /// Bandwidth in MHz for this BFLD variant.
+    #[getter]
+    fn bandwidth_mhz(&self) -> u16 {
+        match self {
+            Self::CompressedHE20 | Self::UncompressedHT20 => 20,
+            Self::CompressedHE40 | Self::UncompressedHT40 => 40,
+            Self::CompressedHE80 => 80,
+            Self::CompressedHE160 => 160,
+        }
+    }
+
+    /// True for 802.11ax (HE) variants, false for legacy HT.
+    #[getter]
+    fn is_he(&self) -> bool {
+        matches!(
+            self,
+            Self::CompressedHE20
+                | Self::CompressedHE40
+                | Self::CompressedHE80
+                | Self::CompressedHE160
+        )
+    }
+
+    fn __repr__(&self) -> String {
+        let name = match self {
+            Self::CompressedHE20 => "CompressedHE20",
+            Self::CompressedHE40 => "CompressedHE40",
+            Self::CompressedHE80 => "CompressedHE80",
+            Self::CompressedHE160 => "CompressedHE160",
+            Self::UncompressedHT20 => "UncompressedHT20",
+            Self::UncompressedHT40 => "UncompressedHT40",
+        };
+        format!("BfldKind.{}", name)
+    }
+}
+
+// ─── BfldFrame ───────────────────────────────────────────────────────
+
+/// One BFR snapshot: a compressed beamforming feedback matrix tagged
+/// with metadata (timestamp, sounding sequence, source MAC, kind).
+///
+/// Backing storage: a numpy Complex64 ndarray `[Nr × Nc × Nsc]`. The
+/// Python constructor accepts the ndarray directly; under the hood we
+/// hold a `Vec<Complex64>` in row-major order.
+///
+/// Python:
+/// ```python
+/// import numpy as np
+/// from wifi_densepose import BfldFrame, BfldKind
+///
+/// fb = np.zeros((2, 1, 996), dtype=np.complex64)  # Nr=2, Nc=1, Nsc=996
+/// frame = BfldFrame.from_compressed_feedback(
+///     timestamp_ms=1234,
+///     sounding_index=42,
+///     sta_mac="aa:bb:cc:dd:ee:ff",
+///     kind=BfldKind.CompressedHE80,
+///     feedback_matrix=fb,
+/// )
+/// print(frame.n_subcarriers, frame.kind, frame.n_rows, frame.n_cols)
+/// ```
+#[pyclass(frozen, name = "BfldFrame")]
+pub struct PyBfldFrame {
+    timestamp_ms: i64,
+    sounding_index: u32,
+    sta_mac: String,
+    kind: PyBfldKind,
+    n_rows: usize,
+    n_cols: usize,
+    n_subcarriers: usize,
+    // Row-major storage of the [Nr × Nc × Nsc] complex matrix.
+    // Length = n_rows * n_cols * n_subcarriers.
+    matrix: Vec<Complex64>,
+}
+
+#[pymethods]
+impl PyBfldFrame {
+    /// Construct from a pre-parsed Complex64 ndarray of shape
+    /// `[n_rows, n_cols, n_subcarriers]`. The last dimension MUST
+    /// match `kind.n_subcarriers`.
+    #[staticmethod]
+    fn from_compressed_feedback<'py>(
+        timestamp_ms: i64,
+        sounding_index: u32,
+        sta_mac: &str,
+        kind: PyBfldKind,
+        feedback_matrix: PyReadonlyArray3<'py, Complex64>,
+    ) -> PyResult<Self> {
+        let shape = feedback_matrix.shape();
+        let n_rows = shape[0];
+        let n_cols = shape[1];
+        let n_subcarriers = shape[2];
+        let expected = kind.n_subcarriers();
+        if n_subcarriers != expected {
+            return Err(pyo3::exceptions::PyValueError::new_err(format!(
+                "feedback_matrix subcarrier dim {} does not match {:?}.n_subcarriers={}",
+                n_subcarriers, kind, expected
+            )));
+        }
+        // Copy into row-major Vec. This is the safe path; PyArray3 is
+        // also row-major by default.
+        let matrix: Vec<Complex64> = feedback_matrix
+            .as_array()
+            .iter()
+            .copied()
+            .collect();
+        Ok(Self {
+            timestamp_ms,
+            sounding_index,
+            sta_mac: sta_mac.to_string(),
+            kind,
+            n_rows,
+            n_cols,
+            n_subcarriers,
+            matrix,
+        })
+    }
+
+    #[getter]
+    fn timestamp_ms(&self) -> i64 { self.timestamp_ms }
+
+    #[getter]
+    fn sounding_index(&self) -> u32 { self.sounding_index }
+
+    #[getter]
+    fn sta_mac(&self) -> &str { &self.sta_mac }
+
+    #[getter]
+    fn kind(&self) -> PyBfldKind { self.kind }
+
+    #[getter]
+    fn n_rows(&self) -> usize { self.n_rows }
+
+    #[getter]
+    fn n_cols(&self) -> usize { self.n_cols }
+
+    #[getter]
+    fn n_subcarriers(&self) -> usize { self.n_subcarriers }
+
+    /// Mean amplitude across the entire matrix (sanity-check metric;
+    /// production-grade sensing pipelines look at per-subcarrier or
+    /// per-row stats instead).
+    #[getter]
+    fn mean_amplitude(&self) -> f64 {
+        if self.matrix.is_empty() {
+            return 0.0;
+        }
+        let sum: f64 = self.matrix.iter().map(|c| c.norm()).sum();
+        sum / self.matrix.len() as f64
+    }
+
+    /// Return the feedback matrix as a numpy Complex64 ndarray of
+    /// shape `[n_rows, n_cols, n_subcarriers]`. Allocates a fresh
+    /// Python-owned array; the BfldFrame keeps its own copy.
+    fn feedback_matrix<'py>(&self, py: Python<'py>) -> Bound<'py, PyArray3<Complex64>> {
+        PyArray3::from_vec3_bound(
+            py,
+            &self.reshape_to_vec3(),
+        )
+        .expect("Vec dimensions match the matrix shape — invariant of from_compressed_feedback")
+    }
+
+    fn __repr__(&self) -> String {
+        format!(
+            "BfldFrame(kind={:?}, nr={}, nc={}, nsc={}, sta={}, idx={}, mean_amp={:.4})",
+            self.kind, self.n_rows, self.n_cols, self.n_subcarriers,
+            self.sta_mac, self.sounding_index, self.mean_amplitude(),
+        )
+    }
+}
+
+impl PyBfldFrame {
+    fn reshape_to_vec3(&self) -> Vec<Vec<Vec<Complex64>>> {
+        let mut out = Vec::with_capacity(self.n_rows);
+        for r in 0..self.n_rows {
+            let mut row = Vec::with_capacity(self.n_cols);
+            for c in 0..self.n_cols {
+                let start = (r * self.n_cols + c) * self.n_subcarriers;
+                let end = start + self.n_subcarriers;
+                row.push(self.matrix[start..end].to_vec());
+            }
+            out.push(row);
+        }
+        out
+    }
+}
+
+// ─── BfldReport ──────────────────────────────────────────────────────
+
+/// Aggregator over a window of `BfldFrame`s — the natural "all BFR
+/// data in this 60-second scan" container. Mirrors how `VitalReading`
+/// aggregates `VitalEstimate`s in the vitals pipeline.
+#[pyclass(name = "BfldReport")]
+pub struct PyBfldReport {
+    frames: Vec<u32>, // sounding indices we hold (don't deep-copy the matrices)
+    timestamp_first: Option<i64>,
+    timestamp_last: Option<i64>,
+    kind: Option<PyBfldKind>,
+    mean_amplitudes: Vec<f64>, // one per frame
+}
+
+#[pymethods]
+impl PyBfldReport {
+    #[new]
+    fn new() -> Self {
+        Self {
+            frames: Vec::new(),
+            timestamp_first: None,
+            timestamp_last: None,
+            kind: None,
+            mean_amplitudes: Vec::new(),
+        }
+    }
+
+    /// Add a frame to the report. All frames must share the same
+    /// `kind`; the call errors if they don't.
+    fn add_frame(&mut self, frame: &PyBfldFrame) -> PyResult<()> {
+        if let Some(k) = self.kind {
+            if k != frame.kind {
+                return Err(pyo3::exceptions::PyValueError::new_err(format!(
+                    "frame kind {:?} does not match report kind {:?}",
+                    frame.kind, k
+                )));
+            }
+        } else {
+            self.kind = Some(frame.kind);
+        }
+        self.frames.push(frame.sounding_index);
+        self.timestamp_first = Some(self.timestamp_first.unwrap_or(frame.timestamp_ms).min(frame.timestamp_ms));
+        self.timestamp_last = Some(self.timestamp_last.unwrap_or(frame.timestamp_ms).max(frame.timestamp_ms));
+        self.mean_amplitudes.push(frame.mean_amplitude());
+        Ok(())
+    }
+
+    #[getter]
+    fn n_frames(&self) -> usize { self.frames.len() }
+
+    #[getter]
+    fn timestamp_first(&self) -> Option<i64> { self.timestamp_first }
+
+    #[getter]
+    fn timestamp_last(&self) -> Option<i64> { self.timestamp_last }
+
+    #[getter]
+    fn kind(&self) -> Option<PyBfldKind> { self.kind }
+
+    /// Mean of the per-frame mean amplitudes — coarse sanity metric
+    /// for "the scan captured a stable signal over the window".
+    #[getter]
+    fn coherence_score(&self) -> f64 {
+        if self.mean_amplitudes.is_empty() {
+            return 0.0;
+        }
+        let mean = self.mean_amplitudes.iter().sum::<f64>()
+            / self.mean_amplitudes.len() as f64;
+        if mean == 0.0 {
+            return 0.0;
+        }
+        // Inverse coefficient of variation, clamped to [0, 1].
+        let var = self.mean_amplitudes.iter()
+            .map(|m| (m - mean).powi(2))
+            .sum::<f64>()
+            / self.mean_amplitudes.len() as f64;
+        let cv = var.sqrt() / mean;
+        (1.0 - cv.min(1.0)).max(0.0)
+    }
+
+    fn __repr__(&self) -> String {
+        format!(
+            "BfldReport(n_frames={}, kind={:?}, coherence={:.3})",
+            self.frames.len(), self.kind, self.coherence_score(),
+        )
+    }
+}
+
+pub fn register(m: &Bound<'_, PyModule>) -> PyResult<()> {
+    m.add_class::<PyBfldKind>()?;
+    m.add_class::<PyBfldFrame>()?;
+    m.add_class::<PyBfldReport>()?;
+    Ok(())
+}

python/src/bindings/keypoint.rs

@@ -0,0 +1,291 @@
+//! ADR-117 P2 — PyO3 bindings for `wifi_densepose_core::Keypoint` +
+//! `KeypointType` + `Confidence`.
+//!
+//! Design notes (consequential for the Python API surface):
+//!
+//! 1. **`Confidence` is NOT bound as a separate Python class.** End
+//!    users hate having to construct a wrapper just to pass a float.
+//!    Python-side, confidence is just an `f32` in `[0.0, 1.0]`; the
+//!    binding validates on the way in.
+//!
+//! 2. **`KeypointType` is bound as a `#[pyclass]` enum** (PyO3 0.22
+//!    supports `#[pyclass(eq, eq_int)]` for C-like enums). Python-side
+//!    it surfaces as `wifi_densepose.KeypointType.Nose`, etc.
+//!
+//! 3. **`Keypoint` constructor accepts `z` as `Optional[float]`** so
+//!    Python users can pass `Keypoint(KeypointType.Nose, 0.5, 0.3,
+//!    0.95)` for 2D or `Keypoint(..., z=0.1)` for 3D.
+
+use pyo3::prelude::*;
+
+use wifi_densepose_core::{Confidence, Keypoint, KeypointType};
+
+// ─── KeypointType ────────────────────────────────────────────────────
+
+/// COCO-17 keypoint identifier — re-export of the Rust core enum.
+///
+/// Python:
+/// ```python
+/// from wifi_densepose import KeypointType
+/// kp = KeypointType.Nose
+/// print(kp.name)  # "Nose"
+/// ```
+// `hash` makes the enum hashable in Python (usable as dict keys + set
+// members) — derived from `Hash` on the Rust side. `frozen` is a
+// hard requirement for `hash` per pyo3 contract.
+#[pyclass(eq, eq_int, hash, frozen, name = "KeypointType")]
+#[derive(Clone, Copy, PartialEq, Eq, Hash)]
+pub enum PyKeypointType {
+    Nose = 0,
+    LeftEye = 1,
+    RightEye = 2,
+    LeftEar = 3,
+    RightEar = 4,
+    LeftShoulder = 5,
+    RightShoulder = 6,
+    LeftElbow = 7,
+    RightElbow = 8,
+    LeftWrist = 9,
+    RightWrist = 10,
+    LeftHip = 11,
+    RightHip = 12,
+    LeftKnee = 13,
+    RightKnee = 14,
+    LeftAnkle = 15,
+    RightAnkle = 16,
+}
+
+#[pymethods]
+impl PyKeypointType {
+    /// Lowercase snake_case name (matches the COCO standard).
+    #[getter]
+    fn snake_name(&self) -> &'static str {
+        self.as_rust().name()
+    }
+
+    /// Integer index 0–16 (COCO ordering).
+    #[getter]
+    fn index(&self) -> u8 {
+        (*self).into()
+    }
+
+    /// True if this keypoint is on the face (nose, eyes, ears).
+    fn is_face(&self) -> bool {
+        self.as_rust().is_face()
+    }
+
+    /// True if this keypoint is in the upper body (shoulders, elbows, wrists).
+    fn is_upper_body(&self) -> bool {
+        self.as_rust().is_upper_body()
+    }
+
+    /// All 17 keypoint types in COCO order. Useful for Jupyter
+    /// enumeration: `for kp in KeypointType.all(): ...`.
+    #[staticmethod]
+    fn all() -> Vec<Self> {
+        KeypointType::all().iter().map(|k| PyKeypointType::from_rust(*k)).collect()
+    }
+
+    fn __repr__(&self) -> String {
+        format!("KeypointType.{:?}", self.as_rust())
+    }
+}
+
+impl PyKeypointType {
+    pub(crate) fn as_rust(&self) -> KeypointType {
+        // SAFETY equivalent: the enum variants line up 1:1 with the
+        // Rust enum's `#[repr(u8)]` discriminants. The match below is
+        // exhaustive on both sides so a future addition to either side
+        // fails to compile until the other is updated.
+        match self {
+            Self::Nose => KeypointType::Nose,
+            Self::LeftEye => KeypointType::LeftEye,
+            Self::RightEye => KeypointType::RightEye,
+            Self::LeftEar => KeypointType::LeftEar,
+            Self::RightEar => KeypointType::RightEar,
+            Self::LeftShoulder => KeypointType::LeftShoulder,
+            Self::RightShoulder => KeypointType::RightShoulder,
+            Self::LeftElbow => KeypointType::LeftElbow,
+            Self::RightElbow => KeypointType::RightElbow,
+            Self::LeftWrist => KeypointType::LeftWrist,
+            Self::RightWrist => KeypointType::RightWrist,
+            Self::LeftHip => KeypointType::LeftHip,
+            Self::RightHip => KeypointType::RightHip,
+            Self::LeftKnee => KeypointType::LeftKnee,
+            Self::RightKnee => KeypointType::RightKnee,
+            Self::LeftAnkle => KeypointType::LeftAnkle,
+            Self::RightAnkle => KeypointType::RightAnkle,
+        }
+    }
+
+    pub(crate) fn from_rust(k: KeypointType) -> Self {
+        match k {
+            KeypointType::Nose => Self::Nose,
+            KeypointType::LeftEye => Self::LeftEye,
+            KeypointType::RightEye => Self::RightEye,
+            KeypointType::LeftEar => Self::LeftEar,
+            KeypointType::RightEar => Self::RightEar,
+            KeypointType::LeftShoulder => Self::LeftShoulder,
+            KeypointType::RightShoulder => Self::RightShoulder,
+            KeypointType::LeftElbow => Self::LeftElbow,
+            KeypointType::RightElbow => Self::RightElbow,
+            KeypointType::LeftWrist => Self::LeftWrist,
+            KeypointType::RightWrist => Self::RightWrist,
+            KeypointType::LeftHip => Self::LeftHip,
+            KeypointType::RightHip => Self::RightHip,
+            KeypointType::LeftKnee => Self::LeftKnee,
+            KeypointType::RightKnee => Self::RightKnee,
+            KeypointType::LeftAnkle => Self::LeftAnkle,
+            KeypointType::RightAnkle => Self::RightAnkle,
+        }
+    }
+}
+
+impl From<PyKeypointType> for u8 {
+    fn from(k: PyKeypointType) -> u8 {
+        k as u8
+    }
+}
+
+impl PyKeypoint {
+    /// Rust-side accessor for the inner Keypoint (used by pose.rs).
+    /// Not exposed to Python — Python users go through the
+    /// #[pymethods] getters above.
+    pub(crate) fn inner(&self) -> &Keypoint {
+        &self.inner
+    }
+
+    /// Rust-side constructor from a core Keypoint (used by pose.rs
+    /// when re-wrapping outputs of PersonPose methods).
+    pub(crate) fn from_rust(k: Keypoint) -> Self {
+        Self { inner: k }
+    }
+}
+
+// ─── Keypoint ────────────────────────────────────────────────────────
+
+/// Single skeletal joint with COCO type, 2D-or-3D position, and a
+/// confidence score in [0.0, 1.0].
+///
+/// Python:
+/// ```python
+/// from wifi_densepose import Keypoint, KeypointType
+///
+/// kp = Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95)
+/// print(kp.x, kp.y, kp.confidence, kp.is_visible)
+///
+/// kp_3d = Keypoint(KeypointType.LeftWrist, 0.2, 0.4, 0.8, z=0.1)
+/// print(kp_3d.position_3d)  # (0.2, 0.4, 0.1)
+/// ```
+#[pyclass(frozen, name = "Keypoint")]
+#[derive(Clone)]
+pub struct PyKeypoint {
+    inner: Keypoint,
+}
+
+#[pymethods]
+impl PyKeypoint {
+    /// Construct a new keypoint. Confidence must be in [0.0, 1.0].
+    /// `z` is optional — omit for a 2D keypoint, supply for 3D.
+    #[new]
+    #[pyo3(signature = (keypoint_type, x, y, confidence, *, z=None))]
+    fn new(
+        keypoint_type: PyKeypointType,
+        x: f32,
+        y: f32,
+        confidence: f32,
+        z: Option<f32>,
+    ) -> PyResult<Self> {
+        let conf = Confidence::new(confidence).map_err(|e| {
+            pyo3::exceptions::PyValueError::new_err(e.to_string())
+        })?;
+        let inner = match z {
+            Some(zv) => Keypoint::new_3d(keypoint_type.as_rust(), x, y, zv, conf),
+            None => Keypoint::new(keypoint_type.as_rust(), x, y, conf),
+        };
+        Ok(Self { inner })
+    }
+
+    /// COCO keypoint type.
+    #[getter]
+    fn keypoint_type(&self) -> PyKeypointType {
+        PyKeypointType::from_rust(self.inner.keypoint_type)
+    }
+
+    /// X coordinate.
+    #[getter]
+    fn x(&self) -> f32 {
+        self.inner.x
+    }
+
+    /// Y coordinate.
+    #[getter]
+    fn y(&self) -> f32 {
+        self.inner.y
+    }
+
+    /// Z coordinate, or None for 2D keypoints.
+    #[getter]
+    fn z(&self) -> Option<f32> {
+        self.inner.z
+    }
+
+    /// Detection confidence in [0.0, 1.0].
+    #[getter]
+    fn confidence(&self) -> f32 {
+        self.inner.confidence.value()
+    }
+
+    /// True if this keypoint clears the default visibility threshold
+    /// (`confidence >= 0.5`).
+    #[getter]
+    fn is_visible(&self) -> bool {
+        self.inner.is_visible()
+    }
+
+    /// 2D position as a tuple `(x, y)`.
+    #[getter]
+    fn position_2d(&self) -> (f32, f32) {
+        self.inner.position_2d()
+    }
+
+    /// 3D position as a tuple `(x, y, z)`, or None for 2D keypoints.
+    #[getter]
+    fn position_3d(&self) -> Option<(f32, f32, f32)> {
+        self.inner.position_3d()
+    }
+
+    /// Euclidean distance to another keypoint. If both are 3D the
+    /// distance includes the z-axis; otherwise it's 2D only.
+    fn distance_to(&self, other: &PyKeypoint) -> f32 {
+        self.inner.distance_to(&other.inner)
+    }
+
+    fn __repr__(&self) -> String {
+        match self.inner.z {
+            Some(z) => format!(
+                "Keypoint(KeypointType.{:?}, x={}, y={}, z={}, confidence={:.4})",
+                self.inner.keypoint_type, self.inner.x, self.inner.y, z, self.inner.confidence.value()
+            ),
+            None => format!(
+                "Keypoint(KeypointType.{:?}, x={}, y={}, confidence={:.4})",
+                self.inner.keypoint_type, self.inner.x, self.inner.y, self.inner.confidence.value()
+            ),
+        }
+    }
+
+    fn __eq__(&self, other: &PyKeypoint) -> bool {
+        self.inner.keypoint_type == other.inner.keypoint_type
+            && self.inner.x == other.inner.x
+            && self.inner.y == other.inner.y
+            && self.inner.z == other.inner.z
+            && (self.inner.confidence.value() - other.inner.confidence.value()).abs() < f32::EPSILON
+    }
+}
+
+/// Register the binding types with the `_native` PyModule.
+pub fn register(m: &Bound<'_, PyModule>) -> PyResult<()> {
+    m.add_class::<PyKeypointType>()?;
+    m.add_class::<PyKeypoint>()?;
+    Ok(())
+}

python/src/bindings/pose.rs

@@ -0,0 +1,376 @@
+//! ADR-117 P2 — PyO3 bindings for `BoundingBox`, `PersonPose`,
+//! `PoseEstimate`.
+//!
+//! Design notes:
+//!
+//! 1. **`PersonPose` exposes the 17-keypoint array as a Python dict
+//!    keyed by `KeypointType`**, not as a fixed-length list with
+//!    `None` slots. Pythonistas don't want to know that the underlying
+//!    storage is `[Option<Keypoint>; 17]`.
+//!
+//! 2. **`PoseEstimate` metadata `id` and `timestamp` are exposed as
+//!    strings** (UUID + RFC 3339) rather than as bound types. Users
+//!    in notebooks rarely need to compare UUIDs structurally; strings
+//!    are good enough and don't require binding `FrameId` /
+//!    `Timestamp` as separate classes.
+//!
+//! 3. **`PersonPose` is mutable** via `set_keypoint` / `set_bbox` /
+//!    `set_id` — it's a builder-style type users construct
+//!    incrementally. Hence NOT `#[pyclass(frozen)]`.
+//!
+//! 4. **`PoseEstimate` is frozen** — once constructed, the list of
+//!    persons + the metadata don't change.
+
+use std::collections::HashMap;
+
+use pyo3::prelude::*;
+use pyo3::types::PyDict;
+
+use wifi_densepose_core::{
+    BoundingBox, Confidence, KeypointType, PersonPose, PoseEstimate,
+};
+
+use super::keypoint::{PyKeypoint, PyKeypointType};
+
+// ─── BoundingBox ─────────────────────────────────────────────────────
+
+/// Axis-aligned bounding box around a detected person.
+///
+/// Python:
+/// ```python
+/// from wifi_densepose import BoundingBox
+///
+/// bb = BoundingBox(0.1, 0.2, 0.5, 0.7)
+/// print(bb.width, bb.height, bb.area, bb.center)
+/// bb2 = BoundingBox.from_center(0.3, 0.45, 0.4, 0.5)
+/// print(bb.iou(bb2))
+/// ```
+#[pyclass(frozen, name = "BoundingBox")]
+#[derive(Clone)]
+pub struct PyBoundingBox {
+    inner: BoundingBox,
+}
+
+#[pymethods]
+impl PyBoundingBox {
+    #[new]
+    fn new(x_min: f32, y_min: f32, x_max: f32, y_max: f32) -> Self {
+        Self { inner: BoundingBox::new(x_min, y_min, x_max, y_max) }
+    }
+
+    /// Construct from center point + width + height.
+    #[staticmethod]
+    fn from_center(cx: f32, cy: f32, width: f32, height: f32) -> Self {
+        Self { inner: BoundingBox::from_center(cx, cy, width, height) }
+    }
+
+    #[getter]
+    fn x_min(&self) -> f32 { self.inner.x_min }
+    #[getter]
+    fn y_min(&self) -> f32 { self.inner.y_min }
+    #[getter]
+    fn x_max(&self) -> f32 { self.inner.x_max }
+    #[getter]
+    fn y_max(&self) -> f32 { self.inner.y_max }
+    #[getter]
+    fn width(&self) -> f32 { self.inner.width() }
+    #[getter]
+    fn height(&self) -> f32 { self.inner.height() }
+    #[getter]
+    fn area(&self) -> f32 { self.inner.area() }
+    #[getter]
+    fn center(&self) -> (f32, f32) { self.inner.center() }
+
+    /// Intersection over Union (IoU) with another box. Range [0.0, 1.0].
+    fn iou(&self, other: &PyBoundingBox) -> f32 {
+        self.inner.iou(&other.inner)
+    }
+
+    fn __repr__(&self) -> String {
+        format!(
+            "BoundingBox(x_min={}, y_min={}, x_max={}, y_max={})",
+            self.inner.x_min, self.inner.y_min, self.inner.x_max, self.inner.y_max,
+        )
+    }
+
+    fn __eq__(&self, other: &PyBoundingBox) -> bool {
+        self.inner == other.inner
+    }
+}
+
+impl PyBoundingBox {
+    pub(crate) fn from_rust(bb: BoundingBox) -> Self {
+        Self { inner: bb }
+    }
+}
+
+// ─── PersonPose ──────────────────────────────────────────────────────
+
+/// A single detected person with optional ID, up to 17 keypoints, and
+/// an optional bounding box.
+///
+/// Python:
+/// ```python
+/// from wifi_densepose import PersonPose, Keypoint, KeypointType, BoundingBox
+///
+/// pose = PersonPose()
+/// pose.set_keypoint(Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95))
+/// pose.set_keypoint(Keypoint(KeypointType.LeftShoulder, 0.4, 0.5, 0.92))
+/// pose.set_id(7)
+/// print(pose.visible_keypoint_count)         # 2
+/// print(pose.get_keypoint(KeypointType.Nose).confidence)  # 0.95
+/// print(pose.compute_bounding_box())          # auto-derived from visible kp
+/// ```
+#[pyclass(name = "PersonPose")]
+#[derive(Clone)]
+pub struct PyPersonPose {
+    inner: PersonPose,
+}
+
+#[pymethods]
+impl PyPersonPose {
+    /// Construct an empty person pose. Set keypoints + bbox + id with
+    /// the dedicated methods.
+    #[new]
+    fn new() -> Self {
+        Self { inner: PersonPose::new() }
+    }
+
+    /// Per-person track ID. None until set.
+    #[getter]
+    fn id(&self) -> Option<u32> {
+        self.inner.id
+    }
+
+    fn set_id(&mut self, id: u32) {
+        self.inner.id = Some(id);
+    }
+
+    /// Set or replace a keypoint. The keypoint's type determines its
+    /// slot in the internal 17-element array.
+    fn set_keypoint(&mut self, keypoint: PyKeypoint) {
+        self.inner.set_keypoint(*keypoint.inner());
+    }
+
+    /// Get a keypoint by type, or None if not set.
+    fn get_keypoint(&self, keypoint_type: PyKeypointType) -> Option<PyKeypoint> {
+        let kp = self.inner.get_keypoint(keypoint_type.as_rust())?;
+        // Re-wrap the inner Rust Keypoint for Python.
+        Some(PyKeypoint::from_rust(*kp))
+    }
+
+    /// All keypoints as a dict keyed by KeypointType. Missing
+    /// keypoints are omitted (NOT included with None values).
+    fn keypoints<'py>(&self, py: Python<'py>) -> PyResult<Bound<'py, PyDict>> {
+        // PyO3 0.22 — PyDict::new_bound returns a Bound, the legacy
+        // PyDict::new (returning &PyDict) was removed in 0.21.
+        let dict = PyDict::new_bound(py);
+        for (i, kp_opt) in self.inner.keypoints.iter().enumerate() {
+            if let Some(kp) = kp_opt {
+                let kpt = match KeypointType::all().get(i) {
+                    Some(t) => *t,
+                    None => continue,
+                };
+                // Convert through IntoPy to satisfy ToPyObject bound
+                // for dict.set_item — #[pyclass] types impl IntoPy but
+                // not ToPyObject directly in PyO3 0.22.
+                use pyo3::IntoPy;
+                let k_obj: PyObject = PyKeypointType::from_rust(kpt).into_py(py);
+                let v_obj: PyObject = PyKeypoint::from_rust(*kp).into_py(py);
+                dict.set_item(k_obj, v_obj)?;
+            }
+        }
+        Ok(dict)
+    }
+
+    /// Number of visible keypoints (confidence >= 0.5).
+    #[getter]
+    fn visible_keypoint_count(&self) -> usize {
+        self.inner.visible_keypoint_count()
+    }
+
+    /// List of visible keypoints (subset of the dict from
+    /// `keypoints()`).
+    fn visible_keypoints(&self) -> Vec<PyKeypoint> {
+        self.inner
+            .visible_keypoints()
+            .into_iter()
+            .map(|k| PyKeypoint::from_rust(*k))
+            .collect()
+    }
+
+    /// Bounding box, if previously set or computed.
+    #[getter]
+    fn bounding_box(&self) -> Option<PyBoundingBox> {
+        self.inner.bounding_box.map(PyBoundingBox::from_rust)
+    }
+
+    fn set_bounding_box(&mut self, bb: PyBoundingBox) {
+        self.inner.bounding_box = Some(bb.inner);
+    }
+
+    /// Auto-compute bounding box from visible keypoints, set it
+    /// internally, and return it. Returns None if no keypoints visible.
+    fn compute_bounding_box(&mut self) -> Option<PyBoundingBox> {
+        let bb = self.inner.compute_bounding_box()?;
+        self.inner.bounding_box = Some(bb);
+        Some(PyBoundingBox::from_rust(bb))
+    }
+
+    /// Overall confidence in [0.0, 1.0].
+    #[getter]
+    fn confidence(&self) -> f32 {
+        self.inner.confidence.value()
+    }
+
+    fn set_confidence(&mut self, c: f32) -> PyResult<()> {
+        self.inner.confidence = Confidence::new(c).map_err(|e| {
+            pyo3::exceptions::PyValueError::new_err(e.to_string())
+        })?;
+        Ok(())
+    }
+
+    fn __repr__(&self) -> String {
+        format!(
+            "PersonPose(id={:?}, visible_keypoints={}, confidence={:.4})",
+            self.inner.id,
+            self.inner.visible_keypoint_count(),
+            self.inner.confidence.value(),
+        )
+    }
+}
+
+impl PyPersonPose {
+    pub(crate) fn from_rust(pose: PersonPose) -> Self {
+        Self { inner: pose }
+    }
+}
+
+// ─── PoseEstimate ────────────────────────────────────────────────────
+
+/// Top-level result of a pose-estimation pass — a list of detected
+/// persons plus metadata about the inference run.
+///
+/// Python:
+/// ```python
+/// from wifi_densepose import PoseEstimate, PersonPose
+///
+/// est = PoseEstimate([pose1, pose2], confidence=0.87, latency_ms=8.4,
+///                    model_version="v0.1.0")
+/// print(est.person_count, est.has_detections)
+/// best = est.highest_confidence_person()
+/// ```
+#[pyclass(frozen, name = "PoseEstimate")]
+pub struct PyPoseEstimate {
+    inner: PoseEstimate,
+}
+
+#[pymethods]
+impl PyPoseEstimate {
+    /// Construct a pose estimate from a list of detected persons,
+    /// an overall confidence, inference latency, and model version
+    /// string.
+    #[new]
+    fn new(
+        persons: Vec<PyPersonPose>,
+        confidence: f32,
+        latency_ms: f32,
+        model_version: String,
+    ) -> PyResult<Self> {
+        let conf = Confidence::new(confidence).map_err(|e| {
+            pyo3::exceptions::PyValueError::new_err(e.to_string())
+        })?;
+        let rust_persons: Vec<PersonPose> =
+            persons.into_iter().map(|p| p.inner).collect();
+        Ok(Self {
+            inner: PoseEstimate::new(
+                Vec::new(),
+                rust_persons,
+                conf,
+                latency_ms,
+                model_version,
+            ),
+        })
+    }
+
+    /// Unique frame identifier as a UUID string.
+    #[getter]
+    fn id(&self) -> String {
+        format!("{:?}", self.inner.id)
+            .trim_start_matches("FrameId(")
+            .trim_end_matches(')')
+            .to_string()
+    }
+
+    /// Frame timestamp as an RFC 3339 / ISO 8601 string in UTC.
+    #[getter]
+    fn timestamp(&self) -> String {
+        // Timestamp's Debug impl is usable; for a fully spec-compliant
+        // ISO format, a future refactor binds chrono. P2 string-form
+        // is "good enough" for diagnostics.
+        format!("{:?}", self.inner.timestamp)
+    }
+
+    #[getter]
+    fn persons(&self) -> Vec<PyPersonPose> {
+        self.inner.persons.iter().cloned().map(PyPersonPose::from_rust).collect()
+    }
+
+    #[getter]
+    fn confidence(&self) -> f32 {
+        self.inner.confidence.value()
+    }
+
+    #[getter]
+    fn latency_ms(&self) -> f32 {
+        self.inner.latency_ms
+    }
+
+    #[getter]
+    fn model_version(&self) -> &str {
+        &self.inner.model_version
+    }
+
+    #[getter]
+    fn person_count(&self) -> usize {
+        self.inner.person_count()
+    }
+
+    #[getter]
+    fn has_detections(&self) -> bool {
+        self.inner.has_detections()
+    }
+
+    /// Get the person with the highest individual confidence, or None
+    /// if no persons detected.
+    fn highest_confidence_person(&self) -> Option<PyPersonPose> {
+        self.inner
+            .highest_confidence_person()
+            .cloned()
+            .map(PyPersonPose::from_rust)
+    }
+
+    fn __repr__(&self) -> String {
+        format!(
+            "PoseEstimate(persons={}, confidence={:.4}, latency_ms={:.2}, model_version={:?})",
+            self.inner.person_count(),
+            self.inner.confidence.value(),
+            self.inner.latency_ms,
+            self.inner.model_version,
+        )
+    }
+}
+
+/// Suppress unused-import warnings for HashMap (held for future
+/// keypoint-map helpers in P3).
+#[allow(dead_code)]
+fn _hashmap_kept_for_future_use() -> HashMap<u8, u8> {
+    HashMap::new()
+}
+
+pub fn register(m: &Bound<'_, PyModule>) -> PyResult<()> {
+    m.add_class::<PyBoundingBox>()?;
+    m.add_class::<PyPersonPose>()?;
+    m.add_class::<PyPoseEstimate>()?;
+    Ok(())
+}

python/src/bindings/privacy_gate.rs

@@ -0,0 +1,154 @@
+//! ADR-118 / ADR-125 §2.1.d — Python binding for the BFLD `PrivacyClass`
+//! enum and the HAP-eligibility gate.
+//!
+//! Python:
+//! ```python
+//! from wifi_densepose import PrivacyClass, allows_hap, allows_matter, allows_network
+//!
+//! PrivacyClass.Anonymous            # → 2
+//! allows_hap(PrivacyClass.Raw)      # → False  (I1 invariant)
+//! allows_hap(PrivacyClass.Anonymous)# → True
+//! allows_matter(PrivacyClass.Restricted)  # → True (ADR-122 §2.4)
+//! ```
+//!
+//! This is the SOTA replacement for the Python port that ships in
+//! `scripts/c6-presence-watcher.py::PrivacyClass`. When the
+//! `wifi-densepose` PyPI wheel lands (ADR-117 P5), runtimes flip from
+//! the Python port to this Rust-backed binding and get the same enum
+//! semantics as every other consumer of the published
+//! `wifi-densepose-bfld 0.3.0` crate.
+
+use pyo3::prelude::*;
+use wifi_densepose_bfld::PrivacyClass;
+
+/// Python-facing wrapper for [`wifi_densepose_bfld::PrivacyClass`].
+///
+/// Repr matches the Rust enum byte values 0..=3.
+#[pyclass(eq, eq_int, hash, frozen, name = "PrivacyClass", module = "wifi_densepose")]
+#[derive(Clone, Copy, PartialEq, Eq, Hash, Debug)]
+pub enum PyPrivacyClass {
+    Raw = 0,
+    Derived = 1,
+    Anonymous = 2,
+    Restricted = 3,
+}
+
+impl From<PrivacyClass> for PyPrivacyClass {
+    fn from(c: PrivacyClass) -> Self {
+        match c {
+            PrivacyClass::Raw => Self::Raw,
+            PrivacyClass::Derived => Self::Derived,
+            PrivacyClass::Anonymous => Self::Anonymous,
+            PrivacyClass::Restricted => Self::Restricted,
+        }
+    }
+}
+
+impl From<PyPrivacyClass> for PrivacyClass {
+    fn from(c: PyPrivacyClass) -> Self {
+        match c {
+            PyPrivacyClass::Raw => Self::Raw,
+            PyPrivacyClass::Derived => Self::Derived,
+            PyPrivacyClass::Anonymous => Self::Anonymous,
+            PyPrivacyClass::Restricted => Self::Restricted,
+        }
+    }
+}
+
+#[pymethods]
+impl PyPrivacyClass {
+    /// True if frames of this class may cross a `NetworkSink`.
+    /// Class 0 (`Raw`) is local-only by structural invariant I1
+    /// (ADR-118 §2.2).
+    #[getter]
+    fn allows_network(&self) -> bool {
+        PrivacyClass::from(*self).allows_network()
+    }
+
+    /// True if frames of this class may cross the Matter boundary.
+    /// Only classes 2 (`Anonymous`) and 3 (`Restricted`) qualify per
+    /// ADR-122 §2.4 / ADR-125 §2.1.d.
+    #[getter]
+    fn allows_matter(&self) -> bool {
+        PrivacyClass::from(*self).allows_matter()
+    }
+
+    /// True if frames of this class may cross the HomeKit Accessory
+    /// Protocol boundary. Same set as `allows_matter` — class 2 or 3.
+    #[getter]
+    fn allows_hap(&self) -> bool {
+        // HAP eligibility is the same shape as Matter eligibility per
+        // ADR-125 §2.1.d; we don't add a separate Rust method until
+        // there's a divergence to justify it.
+        PrivacyClass::from(*self).allows_matter()
+    }
+
+    /// Byte value (0..=3) for serialization.
+    #[getter]
+    fn as_u8(&self) -> u8 {
+        PrivacyClass::from(*self).as_u8()
+    }
+
+    fn __repr__(&self) -> String {
+        match self {
+            Self::Raw => "PrivacyClass.Raw",
+            Self::Derived => "PrivacyClass.Derived",
+            Self::Anonymous => "PrivacyClass.Anonymous",
+            Self::Restricted => "PrivacyClass.Restricted",
+        }
+        .to_string()
+    }
+
+    /// Map a byte value 0..=3 to the corresponding `PrivacyClass`.
+    /// Raises `ValueError` on out-of-range input.
+    #[staticmethod]
+    fn from_u8(v: u8) -> PyResult<Self> {
+        PrivacyClass::try_from(v)
+            .map(Self::from)
+            .map_err(|e| pyo3::exceptions::PyValueError::new_err(e.to_string()))
+    }
+
+    /// Map a string ("raw" / "derived" / "anonymous" / "restricted",
+    /// case-insensitive) to the corresponding `PrivacyClass`. Raises
+    /// `ValueError` on unknown names.
+    #[staticmethod]
+    fn from_str(s: &str) -> PyResult<Self> {
+        match s.to_ascii_lowercase().as_str() {
+            "raw" => Ok(Self::Raw),
+            "derived" => Ok(Self::Derived),
+            "anonymous" => Ok(Self::Anonymous),
+            "restricted" => Ok(Self::Restricted),
+            _ => Err(pyo3::exceptions::PyValueError::new_err(format!(
+                "invalid PrivacyClass name: {s:?} (expected raw/derived/anonymous/restricted)"
+            ))),
+        }
+    }
+}
+
+/// Free-function helper: `True` iff `c` may cross the HAP boundary.
+/// Convenience wrapper so Python callers can write
+/// `allows_hap(PrivacyClass.Anonymous)` without method-call syntax.
+#[pyfunction]
+fn allows_hap(c: PyPrivacyClass) -> bool {
+    c.allows_hap()
+}
+
+/// Free-function helper: `True` iff `c` may cross a `NetworkSink`.
+#[pyfunction]
+fn allows_network(c: PyPrivacyClass) -> bool {
+    c.allows_network()
+}
+
+/// Free-function helper: `True` iff `c` may cross the Matter boundary.
+#[pyfunction]
+fn allows_matter(c: PyPrivacyClass) -> bool {
+    c.allows_matter()
+}
+
+pub fn register(m: &Bound<'_, PyModule>) -> PyResult<()> {
+    m.add_class::<PyPrivacyClass>()?;
+    m.add_function(wrap_pyfunction!(allows_hap, m)?)?;
+    m.add_function(wrap_pyfunction!(allows_network, m)?)?;
+    m.add_function(wrap_pyfunction!(allows_matter, m)?)?;
+    Ok(())
+}

python/src/bindings/vitals.rs

@@ -0,0 +1,287 @@
+//! ADR-117 P3 — PyO3 bindings for `wifi_densepose_vitals`.
+//!
+//! Surfaces:
+//!
+//! - `VitalStatus` enum — clinical-grade / degraded / unreliable / unavailable
+//! - `VitalEstimate` — single BPM estimate + confidence + status
+//! - `VitalReading` — combined HR + BR + signal quality snapshot
+//! - `BreathingExtractor` — bandpass 0.1–0.5 Hz → respiratory rate
+//! - `HeartRateExtractor` — bandpass 0.8–2.0 Hz + autocorrelation → HR
+//!
+//! ## GIL release strategy (per ADR-117 §7 and the Q5 audit on
+//! 2026-05-24)
+//!
+//! `wifi-densepose-vitals` has zero tokio deps and the extract loops
+//! are pure-sync DSP. Wrap the `.extract(...)` calls in
+//! `py.allow_threads(|| ...)` so Python users can run inference in a
+//! tokio-backed web server without GIL contention starving the
+//! event loop.
+
+use pyo3::prelude::*;
+
+use wifi_densepose_vitals::{
+    BreathingExtractor, HeartRateExtractor, VitalEstimate, VitalReading, VitalStatus,
+};
+
+// ─── VitalStatus enum ────────────────────────────────────────────────
+
+/// Status of a vital sign measurement.
+///
+/// Python:
+/// ```python
+/// from wifi_densepose import VitalStatus
+/// VitalStatus.Valid       # clinical-grade
+/// VitalStatus.Degraded    # reduced confidence
+/// VitalStatus.Unreliable  # single RSSI source / low quality
+/// VitalStatus.Unavailable # no measurement possible
+/// ```
+#[pyclass(eq, eq_int, hash, frozen, name = "VitalStatus")]
+#[derive(Clone, Copy, PartialEq, Eq, Hash)]
+pub enum PyVitalStatus {
+    Valid = 0,
+    Degraded = 1,
+    Unreliable = 2,
+    Unavailable = 3,
+}
+
+#[pymethods]
+impl PyVitalStatus {
+    fn __repr__(&self) -> String {
+        format!("VitalStatus.{:?}", self.as_rust())
+    }
+}
+
+impl PyVitalStatus {
+    fn as_rust(&self) -> VitalStatus {
+        match self {
+            Self::Valid => VitalStatus::Valid,
+            Self::Degraded => VitalStatus::Degraded,
+            Self::Unreliable => VitalStatus::Unreliable,
+            Self::Unavailable => VitalStatus::Unavailable,
+        }
+    }
+
+    fn from_rust(s: VitalStatus) -> Self {
+        match s {
+            VitalStatus::Valid => Self::Valid,
+            VitalStatus::Degraded => Self::Degraded,
+            VitalStatus::Unreliable => Self::Unreliable,
+            VitalStatus::Unavailable => Self::Unavailable,
+        }
+    }
+}
+
+// ─── VitalEstimate ───────────────────────────────────────────────────
+
+/// A single vital-sign estimate (BPM + confidence + status).
+///
+/// Python:
+/// ```python
+/// from wifi_densepose import VitalEstimate, VitalStatus
+/// est = VitalEstimate(72.4, confidence=0.9, status=VitalStatus.Valid)
+/// print(est.value_bpm, est.confidence, est.status)
+/// ```
+#[pyclass(frozen, name = "VitalEstimate")]
+#[derive(Clone)]
+pub struct PyVitalEstimate {
+    inner: VitalEstimate,
+}
+
+#[pymethods]
+impl PyVitalEstimate {
+    #[new]
+    fn new(value_bpm: f64, confidence: f64, status: PyVitalStatus) -> Self {
+        Self {
+            inner: VitalEstimate {
+                value_bpm,
+                confidence,
+                status: status.as_rust(),
+            },
+        }
+    }
+
+    #[getter]
+    fn value_bpm(&self) -> f64 { self.inner.value_bpm }
+
+    #[getter]
+    fn confidence(&self) -> f64 { self.inner.confidence }
+
+    #[getter]
+    fn status(&self) -> PyVitalStatus { PyVitalStatus::from_rust(self.inner.status) }
+
+    fn __repr__(&self) -> String {
+        format!(
+            "VitalEstimate(value_bpm={:.2}, confidence={:.3}, status={:?})",
+            self.inner.value_bpm, self.inner.confidence, self.inner.status,
+        )
+    }
+}
+
+impl PyVitalEstimate {
+    fn from_rust(e: VitalEstimate) -> Self {
+        Self { inner: e }
+    }
+}
+
+// ─── VitalReading ────────────────────────────────────────────────────
+
+/// Combined HR + BR snapshot from one window of CSI data.
+#[pyclass(frozen, name = "VitalReading")]
+pub struct PyVitalReading {
+    inner: VitalReading,
+}
+
+#[pymethods]
+impl PyVitalReading {
+    #[new]
+    fn new(
+        respiratory_rate: PyVitalEstimate,
+        heart_rate: PyVitalEstimate,
+        subcarrier_count: usize,
+        signal_quality: f64,
+        timestamp_secs: f64,
+    ) -> Self {
+        Self {
+            inner: VitalReading {
+                respiratory_rate: respiratory_rate.inner,
+                heart_rate: heart_rate.inner,
+                subcarrier_count,
+                signal_quality,
+                timestamp_secs,
+            },
+        }
+    }
+
+    #[getter]
+    fn respiratory_rate(&self) -> PyVitalEstimate {
+        PyVitalEstimate::from_rust(self.inner.respiratory_rate.clone())
+    }
+
+    #[getter]
+    fn heart_rate(&self) -> PyVitalEstimate {
+        PyVitalEstimate::from_rust(self.inner.heart_rate.clone())
+    }
+
+    #[getter]
+    fn subcarrier_count(&self) -> usize { self.inner.subcarrier_count }
+
+    #[getter]
+    fn signal_quality(&self) -> f64 { self.inner.signal_quality }
+
+    #[getter]
+    fn timestamp_secs(&self) -> f64 { self.inner.timestamp_secs }
+
+    fn __repr__(&self) -> String {
+        format!(
+            "VitalReading(br={:.1}, hr={:.1}, subcarriers={}, quality={:.3})",
+            self.inner.respiratory_rate.value_bpm,
+            self.inner.heart_rate.value_bpm,
+            self.inner.subcarrier_count,
+            self.inner.signal_quality,
+        )
+    }
+}
+
+// ─── BreathingExtractor ──────────────────────────────────────────────
+
+/// Extracts respiratory rate (6–30 BPM) from per-subcarrier amplitude
+/// residuals via 0.1–0.5 Hz bandpass + zero-crossing analysis.
+///
+/// Python:
+/// ```python
+/// from wifi_densepose import BreathingExtractor
+///
+/// br = BreathingExtractor.esp32_default()  # 56 subcarriers, 100 Hz, 30s window
+/// # or: BreathingExtractor(n_subcarriers=56, sample_rate=100.0, window_secs=30.0)
+///
+/// # Feed residuals from your preprocessor (one frame at a time)
+/// est = br.extract(residuals=[0.01, -0.02, …], weights=[])  # equal weights
+/// if est is not None:
+///     print(est.value_bpm, est.confidence)
+/// ```
+#[pyclass(name = "BreathingExtractor")]
+pub struct PyBreathingExtractor {
+    inner: BreathingExtractor,
+}
+
+#[pymethods]
+impl PyBreathingExtractor {
+    /// Construct with explicit parameters.
+    #[new]
+    #[pyo3(signature = (n_subcarriers, sample_rate, window_secs=30.0))]
+    fn new(n_subcarriers: usize, sample_rate: f64, window_secs: f64) -> Self {
+        Self {
+            inner: BreathingExtractor::new(n_subcarriers, sample_rate, window_secs),
+        }
+    }
+
+    /// ESP32 defaults: 56 subcarriers, 100 Hz, 30-second window.
+    #[staticmethod]
+    fn esp32_default() -> Self {
+        Self { inner: BreathingExtractor::esp32_default() }
+    }
+
+    /// Extract respiratory rate from a vector of per-subcarrier
+    /// residuals + per-subcarrier weights. GIL is released during the
+    /// DSP loop so Python threads can do other work concurrently.
+    ///
+    /// Returns `None` if insufficient history has been accumulated.
+    fn extract(&mut self, py: Python<'_>, residuals: Vec<f64>, weights: Vec<f64>) -> Option<PyVitalEstimate> {
+        // GIL release: see ADR-117 §7 and the Q5 tokio audit. The DSP
+        // loop is pure sync, no Python objects touched, safe to run
+        // without the GIL.
+        let est = py.allow_threads(|| self.inner.extract(&residuals, &weights));
+        est.map(PyVitalEstimate::from_rust)
+    }
+
+    fn __repr__(&self) -> String {
+        format!("BreathingExtractor(0.1–0.5 Hz bandpass)")
+    }
+}
+
+// ─── HeartRateExtractor ──────────────────────────────────────────────
+
+/// Extracts heart rate (40–120 BPM) from per-subcarrier amplitude
+/// residuals via 0.8–2.0 Hz bandpass + autocorrelation peak detection.
+#[pyclass(name = "HeartRateExtractor")]
+pub struct PyHeartRateExtractor {
+    inner: HeartRateExtractor,
+}
+
+#[pymethods]
+impl PyHeartRateExtractor {
+    /// Construct with explicit parameters.
+    #[new]
+    #[pyo3(signature = (n_subcarriers, sample_rate, window_secs=15.0))]
+    fn new(n_subcarriers: usize, sample_rate: f64, window_secs: f64) -> Self {
+        Self {
+            inner: HeartRateExtractor::new(n_subcarriers, sample_rate, window_secs),
+        }
+    }
+
+    /// ESP32 defaults: 56 subcarriers, 100 Hz, 15-second window.
+    #[staticmethod]
+    fn esp32_default() -> Self {
+        Self { inner: HeartRateExtractor::esp32_default() }
+    }
+
+    /// Extract heart rate from per-subcarrier residuals. GIL released
+    /// during DSP.
+    fn extract(&mut self, py: Python<'_>, residuals: Vec<f64>, weights: Vec<f64>) -> Option<PyVitalEstimate> {
+        let est = py.allow_threads(|| self.inner.extract(&residuals, &weights));
+        est.map(PyVitalEstimate::from_rust)
+    }
+
+    fn __repr__(&self) -> String {
+        format!("HeartRateExtractor(0.8–2.0 Hz bandpass)")
+    }
+}
+
+pub fn register(m: &Bound<'_, PyModule>) -> PyResult<()> {
+    m.add_class::<PyVitalStatus>()?;
+    m.add_class::<PyVitalEstimate>()?;
+    m.add_class::<PyVitalReading>()?;
+    m.add_class::<PyBreathingExtractor>()?;
+    m.add_class::<PyHeartRateExtractor>()?;
+    Ok(())
+}

python/src/lib.rs

@@ -0,0 +1,89 @@
+//! ADR-117 — PyO3 bindings for the WiFi-DensePose Rust core.
+//!
+//! This crate is the compiled half of the `wifi-densepose` v2.x PyPI
+//! wheel. The Python-facing facade lives in `python/wifi_densepose/`
+//! and re-exports symbols from this module under their stable names.
+//!
+//! ## Phase status (per ADR-117 §6)
+//!
+//! - **P1 (scaffold) — this commit**: module loads, version constant
+//!   exposed, smoke test passes via maturin develop.
+//! - **P2**: bind `CsiFrame`, `Keypoint`, `PoseEstimate` (next).
+//! - **P3**: bind 4-stage vitals + signal DSP.
+//! - **P4**: pure-Python `wifi_densepose.client` (WS/MQTT) — no Rust
+//!   surface needed; lives outside this crate.
+//! - **P5**: cibuildwheel + PyPI publish.
+
+use pyo3::prelude::*;
+
+mod bindings {
+    pub mod bfld;
+    pub mod keypoint;
+    pub mod pose;
+    pub mod privacy_gate;
+    pub mod vitals;
+}
+
+/// Version of the bound Rust core. Surfaced to Python as
+/// `wifi_densepose.__rust_version__` so users can correlate wheel
+/// behaviour with the exact `v2/crates/` HEAD it was built from.
+const RUST_CORE_VERSION: &str = env!("CARGO_PKG_VERSION");
+
+/// Compile-time identifier for the Rust commit that produced this
+/// wheel. Surfaced for diagnostics. Set via `CARGO_PKG_VERSION` for
+/// now; P5 wires in the git SHA via `vergen`.
+const RUST_BUILD_TAG: &str = env!("CARGO_PKG_VERSION");
+
+/// One-line description of which feature flags were enabled at build
+/// time. Helps users debug "is my wheel the slim one or the full one?".
+fn build_features() -> Vec<&'static str> {
+    let mut feats: Vec<&'static str> = Vec::new();
+    feats.push("p1-scaffold");
+    feats.push("p2-keypoint-bindings"); // Keypoint + KeypointType
+    feats.push("p2-pose-bindings"); // BoundingBox + PersonPose + PoseEstimate
+    feats.push("p3-vitals-bindings"); // BreathingExtractor + HeartRateExtractor + VitalEstimate
+    feats.push("p3.5-bfld-bindings"); // BfldFrame + BfldReport + BfldKind (stub Rust)
+    feats
+}
+
+/// Quick smoke test exposed to Python. Returns "ok" — used by the
+/// integration tests in `python/tests/test_smoke.py` to assert the
+/// PyO3 module is importable and callable.
+#[pyfunction]
+fn hello() -> PyResult<&'static str> {
+    Ok("ok")
+}
+
+/// The `_native` module — re-exported in pure-Python as
+/// `wifi_densepose._native`. End users should import the parent
+/// package (`import wifi_densepose`) and never reach into `_native`
+/// directly; the leading underscore is a Python convention marking
+/// it as private.
+///
+/// The function name MUST match the `module-name` in pyproject.toml's
+/// `[tool.maturin]` block — i.e. it must be `_native` because the
+/// pyproject says `module-name = "wifi_densepose._native"`. PyO3
+/// generates the `PyInit__native` symbol from this function name.
+#[pymodule]
+#[pyo3(name = "_native")]
+fn wifi_densepose_native(m: &Bound<'_, PyModule>) -> PyResult<()> {
+    m.add("__rust_version__", RUST_CORE_VERSION)?;
+    m.add("__rust_build_tag__", RUST_BUILD_TAG)?;
+    m.add("__build_features__", build_features())?;
+    m.add_function(wrap_pyfunction!(hello, m)?)?;
+
+    // P2 — Keypoint + KeypointType bindings.
+    bindings::keypoint::register(m)?;
+    // P2 — BoundingBox + PersonPose + PoseEstimate bindings.
+    bindings::pose::register(m)?;
+    // P3 — Vital sign extraction bindings.
+    bindings::vitals::register(m)?;
+    // P3.5 — BFLD bindings (stub Rust; future wifi-densepose-bfld crate
+    // will replace the stub without changing the Python API).
+    bindings::bfld::register(m)?;
+    // ADR-118 PrivacyClass + HAP/Matter eligibility gates (SOTA — backed by
+    // the published `wifi-densepose-bfld 0.3.0` crate, not the Python port).
+    // Closes ADR-125 §2.1.d at the binding boundary.
+    bindings::privacy_gate::register(m)?;
+    Ok(())
+}

python/tests/test_bfld.py

@@ -0,0 +1,263 @@
+"""ADR-117 P3.5 — Tests for BFLD (Beamforming Feedback Loop Data) bindings.
+
+These tests cover the *stub-Rust-backed* forward-compatible Python
+surface defined in ADR-117 §5.7a. The real Rust ingestion crate
+(`wifi-densepose-bfld`) lands post-v2.0; this test suite locks in the
+Python API so a future swap-in is non-breaking.
+
+Coverage:
+
+- BfldKind enum — HE20/40/80/160 + HT20/40 variants
+- BfldKind metadata getters — n_subcarriers, bandwidth_mhz, is_he
+- BfldFrame.from_compressed_feedback — happy path + dim mismatch
+- BfldFrame numpy round-trip — feedback_matrix returns ndarray
+- BfldReport — frame aggregation, kind-mismatch error, coherence score
+"""
+
+from __future__ import annotations
+
+import math
+
+import numpy as np
+import pytest
+
+import wifi_densepose
+from wifi_densepose import BfldFrame, BfldKind, BfldReport
+
+
+# ─── BfldKind enum ───────────────────────────────────────────────────
+
+
+def test_bfld_kind_variants_exist() -> None:
+    assert BfldKind.CompressedHE20 != BfldKind.CompressedHE40
+    assert BfldKind.CompressedHE80 != BfldKind.CompressedHE160
+    assert BfldKind.UncompressedHT20 != BfldKind.UncompressedHT40
+
+
+def test_bfld_kind_is_hashable() -> None:
+    s = {BfldKind.CompressedHE80, BfldKind.CompressedHE80}
+    assert len(s) == 1
+
+
+def test_bfld_kind_n_subcarriers_he() -> None:
+    assert BfldKind.CompressedHE20.n_subcarriers == 242
+    assert BfldKind.CompressedHE40.n_subcarriers == 484
+    assert BfldKind.CompressedHE80.n_subcarriers == 996
+    assert BfldKind.CompressedHE160.n_subcarriers == 1992
+
+
+def test_bfld_kind_n_subcarriers_ht() -> None:
+    assert BfldKind.UncompressedHT20.n_subcarriers == 52
+    assert BfldKind.UncompressedHT40.n_subcarriers == 108
+
+
+def test_bfld_kind_bandwidth_mhz() -> None:
+    assert BfldKind.CompressedHE20.bandwidth_mhz == 20
+    assert BfldKind.CompressedHE40.bandwidth_mhz == 40
+    assert BfldKind.CompressedHE80.bandwidth_mhz == 80
+    assert BfldKind.CompressedHE160.bandwidth_mhz == 160
+    assert BfldKind.UncompressedHT20.bandwidth_mhz == 20
+    assert BfldKind.UncompressedHT40.bandwidth_mhz == 40
+
+
+def test_bfld_kind_is_he_flag() -> None:
+    assert BfldKind.CompressedHE20.is_he is True
+    assert BfldKind.CompressedHE160.is_he is True
+    assert BfldKind.UncompressedHT20.is_he is False
+    assert BfldKind.UncompressedHT40.is_he is False
+
+
+def test_bfld_kind_repr() -> None:
+    r = repr(BfldKind.CompressedHE80)
+    assert "BfldKind" in r and "CompressedHE80" in r
+
+
+# ─── BfldFrame construction ──────────────────────────────────────────
+
+
+def _make_matrix(n_rows: int, n_cols: int, n_subcarriers: int) -> np.ndarray:
+    """Synthetic feedback matrix with non-trivial amplitudes so the
+    mean_amplitude getter has something to chew on."""
+    rng = np.random.default_rng(seed=42)
+    real = rng.standard_normal((n_rows, n_cols, n_subcarriers)).astype(np.float64)
+    imag = rng.standard_normal((n_rows, n_cols, n_subcarriers)).astype(np.float64)
+    return (real + 1j * imag).astype(np.complex128)
+
+
+def test_bfld_frame_he80_happy_path() -> None:
+    fb = _make_matrix(2, 1, 996)
+    frame = BfldFrame.from_compressed_feedback(
+        timestamp_ms=1234,
+        sounding_index=42,
+        sta_mac="aa:bb:cc:dd:ee:ff",
+        kind=BfldKind.CompressedHE80,
+        feedback_matrix=fb,
+    )
+    assert frame.timestamp_ms == 1234
+    assert frame.sounding_index == 42
+    assert frame.sta_mac == "aa:bb:cc:dd:ee:ff"
+    assert frame.kind == BfldKind.CompressedHE80
+    assert frame.n_rows == 2
+    assert frame.n_cols == 1
+    assert frame.n_subcarriers == 996
+
+
+def test_bfld_frame_he160_2x2() -> None:
+    fb = _make_matrix(2, 2, 1992)
+    frame = BfldFrame.from_compressed_feedback(
+        timestamp_ms=0,
+        sounding_index=0,
+        sta_mac="00:00:00:00:00:00",
+        kind=BfldKind.CompressedHE160,
+        feedback_matrix=fb,
+    )
+    assert frame.n_rows == 2
+    assert frame.n_cols == 2
+    assert frame.n_subcarriers == 1992
+
+
+def test_bfld_frame_ht20_legacy_path() -> None:
+    fb = _make_matrix(1, 1, 52)
+    frame = BfldFrame.from_compressed_feedback(
+        timestamp_ms=0,
+        sounding_index=0,
+        sta_mac="aa:bb:cc:dd:ee:ff",
+        kind=BfldKind.UncompressedHT20,
+        feedback_matrix=fb,
+    )
+    assert frame.kind == BfldKind.UncompressedHT20
+    assert frame.n_subcarriers == 52
+
+
+def test_bfld_frame_subcarrier_dim_mismatch_raises() -> None:
+    # HE80 requires 996 subcarriers; pass 64 → ValueError.
+    bad = _make_matrix(2, 1, 64)
+    with pytest.raises(ValueError, match="subcarrier"):
+        BfldFrame.from_compressed_feedback(
+            timestamp_ms=0,
+            sounding_index=0,
+            sta_mac="aa:bb:cc:dd:ee:ff",
+            kind=BfldKind.CompressedHE80,
+            feedback_matrix=bad,
+        )
+
+
+def test_bfld_frame_mean_amplitude_is_finite() -> None:
+    fb = _make_matrix(2, 1, 996)
+    frame = BfldFrame.from_compressed_feedback(
+        timestamp_ms=0,
+        sounding_index=0,
+        sta_mac="aa:bb:cc:dd:ee:ff",
+        kind=BfldKind.CompressedHE80,
+        feedback_matrix=fb,
+    )
+    amp = frame.mean_amplitude
+    assert math.isfinite(amp) and amp > 0.0
+
+
+def test_bfld_frame_numpy_roundtrip_preserves_shape() -> None:
+    fb = _make_matrix(2, 1, 996)
+    frame = BfldFrame.from_compressed_feedback(
+        timestamp_ms=0,
+        sounding_index=0,
+        sta_mac="aa:bb:cc:dd:ee:ff",
+        kind=BfldKind.CompressedHE80,
+        feedback_matrix=fb,
+    )
+    out = frame.feedback_matrix()
+    assert out.shape == (2, 1, 996)
+    # Roundtrip should be lossless (Complex64 in, Complex64 out).
+    assert np.allclose(out, fb.astype(np.complex128))
+
+
+def test_bfld_frame_repr_is_readable() -> None:
+    fb = _make_matrix(2, 1, 996)
+    frame = BfldFrame.from_compressed_feedback(
+        timestamp_ms=0,
+        sounding_index=0,
+        sta_mac="aa:bb:cc:dd:ee:ff",
+        kind=BfldKind.CompressedHE80,
+        feedback_matrix=fb,
+    )
+    r = repr(frame)
+    assert "BfldFrame" in r
+    assert "996" in r
+    assert "CompressedHE80" in r
+
+
+# ─── BfldReport ──────────────────────────────────────────────────────
+
+
+def test_bfld_report_starts_empty() -> None:
+    report = BfldReport()
+    assert report.n_frames == 0
+    assert report.kind is None
+    assert report.timestamp_first is None
+    assert report.timestamp_last is None
+    assert report.coherence_score == 0.0
+
+
+def test_bfld_report_aggregates_homogeneous_frames() -> None:
+    report = BfldReport()
+    fb = _make_matrix(2, 1, 996)
+    for i in range(5):
+        frame = BfldFrame.from_compressed_feedback(
+            timestamp_ms=1000 + i * 100,
+            sounding_index=i,
+            sta_mac="aa:bb:cc:dd:ee:ff",
+            kind=BfldKind.CompressedHE80,
+            feedback_matrix=fb,
+        )
+        report.add_frame(frame)
+    assert report.n_frames == 5
+    assert report.kind == BfldKind.CompressedHE80
+    assert report.timestamp_first == 1000
+    assert report.timestamp_last == 1400
+    # Identical synthetic matrices → near-perfect coherence.
+    assert report.coherence_score >= 0.99
+
+
+def test_bfld_report_rejects_mismatched_kind() -> None:
+    report = BfldReport()
+    fb_he80 = _make_matrix(2, 1, 996)
+    fb_he40 = _make_matrix(2, 1, 484)
+    he80 = BfldFrame.from_compressed_feedback(
+        timestamp_ms=0,
+        sounding_index=0,
+        sta_mac="aa:bb:cc:dd:ee:ff",
+        kind=BfldKind.CompressedHE80,
+        feedback_matrix=fb_he80,
+    )
+    he40 = BfldFrame.from_compressed_feedback(
+        timestamp_ms=0,
+        sounding_index=0,
+        sta_mac="aa:bb:cc:dd:ee:ff",
+        kind=BfldKind.CompressedHE40,
+        feedback_matrix=fb_he40,
+    )
+    report.add_frame(he80)
+    with pytest.raises(ValueError, match="kind"):
+        report.add_frame(he40)
+
+
+def test_bfld_report_repr_summarises() -> None:
+    report = BfldReport()
+    fb = _make_matrix(2, 1, 996)
+    frame = BfldFrame.from_compressed_feedback(
+        timestamp_ms=0,
+        sounding_index=0,
+        sta_mac="aa:bb:cc:dd:ee:ff",
+        kind=BfldKind.CompressedHE80,
+        feedback_matrix=fb,
+    )
+    report.add_frame(frame)
+    r = repr(report)
+    assert "BfldReport" in r
+    assert "n_frames=1" in r
+
+
+# ─── Build feature flag ──────────────────────────────────────────────
+
+
+def test_p3_5_bfld_in_build_features() -> None:
+    assert "p3.5-bfld-bindings" in wifi_densepose.__build_features__

python/tests/test_client_ha.py

@@ -0,0 +1,205 @@
+"""ADR-117 P4 — Tests for HA-DISCO payload parsing.
+
+Pure parsing tests — no MQTT broker needed.
+"""
+
+from __future__ import annotations
+
+import json
+
+import pytest
+
+from wifi_densepose.client import (
+    HABlueprintHelper,
+    HaDiscoveryPayload,
+    HaEntity,
+)
+from wifi_densepose.client.ha import (
+    parse_discovery_payload,
+    parse_discovery_topic,
+)
+
+
+# Real discovery payloads pulled from ADR-115 §3 (formatted for test
+# readability; payloads are otherwise verbatim).
+_PRESENCE_TOPIC = "homeassistant/binary_sensor/wifi_densepose_aabbccddeeff/presence/config"
+_PRESENCE_BODY = {
+    "name": "Presence",
+    "unique_id": "wifi_densepose_aabbccddeeff_presence",
+    "object_id": "wifi_densepose_aabbccddeeff_presence",
+    "state_topic": "homeassistant/binary_sensor/wifi_densepose_aabbccddeeff/presence/state",
+    "availability_topic": "homeassistant/binary_sensor/wifi_densepose_aabbccddeeff/presence/availability",
+    "device_class": "occupancy",
+    "icon": "mdi:motion-sensor",
+}
+
+_HEART_RATE_TOPIC = "homeassistant/sensor/wifi_densepose_aabbccddeeff/heart_rate/config"
+_HEART_RATE_BODY = {
+    "name": "Heart rate",
+    "unique_id": "wifi_densepose_aabbccddeeff_heart_rate",
+    "state_topic": "homeassistant/sensor/wifi_densepose_aabbccddeeff/heart_rate/state",
+    "state_class": "measurement",
+    "unit_of_measurement": "bpm",
+    "icon": "mdi:heart-pulse",
+    "json_attributes_topic": "homeassistant/sensor/wifi_densepose_aabbccddeeff/heart_rate/state",
+}
+
+
+# ─── Topic parsing ───────────────────────────────────────────────────
+
+
+def test_parse_discovery_topic_binary_sensor() -> None:
+    out = parse_discovery_topic(_PRESENCE_TOPIC)
+    assert out == ("binary_sensor", "aabbccddeeff", "presence")
+
+
+def test_parse_discovery_topic_sensor() -> None:
+    out = parse_discovery_topic(_HEART_RATE_TOPIC)
+    assert out == ("sensor", "aabbccddeeff", "heart_rate")
+
+
+def test_parse_discovery_topic_event() -> None:
+    out = parse_discovery_topic(
+        "homeassistant/event/wifi_densepose_aabbccddeeff/fall/config"
+    )
+    assert out == ("event", "aabbccddeeff", "fall")
+
+
+def test_parse_discovery_topic_returns_none_for_non_discovery() -> None:
+    assert parse_discovery_topic("homeassistant/binary_sensor/foo/state") is None
+    assert parse_discovery_topic("ruview/aabbccddeeff/raw/edge_vitals") is None
+    assert parse_discovery_topic("") is None
+
+
+# ─── Payload parsing ─────────────────────────────────────────────────
+
+
+def test_parse_discovery_payload_from_dict() -> None:
+    out = parse_discovery_payload(_PRESENCE_TOPIC, _PRESENCE_BODY)
+    assert out is not None
+    assert out.entity_kind == "binary_sensor"
+    assert out.node_id == "aabbccddeeff"
+    assert out.object_id == "presence"
+    assert out.payload["device_class"] == "occupancy"
+
+
+def test_parse_discovery_payload_from_bytes() -> None:
+    raw = json.dumps(_PRESENCE_BODY).encode("utf-8")
+    out = parse_discovery_payload(_PRESENCE_TOPIC, raw)
+    assert out is not None
+    assert out.payload["unique_id"] == "wifi_densepose_aabbccddeeff_presence"
+
+
+def test_parse_discovery_payload_from_string() -> None:
+    raw = json.dumps(_PRESENCE_BODY)
+    out = parse_discovery_payload(_PRESENCE_TOPIC, raw)
+    assert out is not None
+    assert out.entity_kind == "binary_sensor"
+
+
+def test_parse_discovery_payload_rejects_malformed_json() -> None:
+    assert parse_discovery_payload(_PRESENCE_TOPIC, "{ broken: json") is None
+
+
+def test_parse_discovery_payload_rejects_non_object_root() -> None:
+    assert parse_discovery_payload(_PRESENCE_TOPIC, "[1, 2, 3]") is None
+
+
+def test_parse_discovery_payload_returns_none_for_non_discovery_topic() -> None:
+    assert parse_discovery_payload(
+        "ruview/aabbccddeeff/raw/edge_vitals",
+        _PRESENCE_BODY,
+    ) is None
+
+
+# ─── HaEntity projection ─────────────────────────────────────────────
+
+
+def test_ha_entity_from_payload_extracts_fields() -> None:
+    p = HaDiscoveryPayload(
+        entity_kind="sensor",
+        node_id="aabbccddeeff",
+        object_id="heart_rate",
+        payload=_HEART_RATE_BODY,
+    )
+    e = HaEntity.from_payload(p)
+    assert e.entity_kind == "sensor"
+    assert e.unique_id == "wifi_densepose_aabbccddeeff_heart_rate"
+    assert e.unit_of_measurement == "bpm"
+    assert e.icon == "mdi:heart-pulse"
+    assert e.json_attributes_topic == _HEART_RATE_BODY["json_attributes_topic"]
+
+
+def test_ha_entity_handles_missing_optional_fields() -> None:
+    p = HaDiscoveryPayload(
+        entity_kind="event",
+        node_id="aabbccddeeff",
+        object_id="bed_exit",
+        payload={"unique_id": "wifi_densepose_aabbccddeeff_bed_exit"},
+    )
+    e = HaEntity.from_payload(p)
+    assert e.unique_id == "wifi_densepose_aabbccddeeff_bed_exit"
+    assert e.device_class == ""
+    assert e.unit_of_measurement == ""
+
+
+# ─── HABlueprintHelper aggregation ───────────────────────────────────
+
+
+def _populated_helper() -> HABlueprintHelper:
+    h = HABlueprintHelper()
+    h.add_payload(_PRESENCE_TOPIC, _PRESENCE_BODY)
+    h.add_payload(_HEART_RATE_TOPIC, _HEART_RATE_BODY)
+    # Same fields but a different node
+    h.add_payload(
+        "homeassistant/binary_sensor/wifi_densepose_ff00ff00ff00/presence/config",
+        {**_PRESENCE_BODY, "unique_id": "wifi_densepose_ff00ff00ff00_presence"},
+    )
+    return h
+
+
+def test_helper_starts_empty() -> None:
+    h = HABlueprintHelper()
+    assert len(h) == 0
+    assert h.nodes() == []
+    assert h.all_payloads() == []
+
+
+def test_helper_aggregates_multiple_payloads() -> None:
+    h = _populated_helper()
+    assert len(h) == 3
+    assert h.nodes() == ["aabbccddeeff", "ff00ff00ff00"]
+
+
+def test_helper_entities_for_node() -> None:
+    h = _populated_helper()
+    entities = h.entities_for_node("aabbccddeeff")
+    object_ids = sorted(e.object_id for e in entities)
+    assert object_ids == ["heart_rate", "presence"]
+
+
+def test_helper_by_device_class() -> None:
+    h = _populated_helper()
+    occupancy_entities = h.by_device_class("occupancy")
+    assert len(occupancy_entities) == 2  # presence on both nodes
+    assert {e.node_id for e in occupancy_entities} == {"aabbccddeeff", "ff00ff00ff00"}
+
+
+def test_helper_remove() -> None:
+    h = _populated_helper()
+    assert h.remove("aabbccddeeff", "binary_sensor", "presence") is True
+    assert h.remove("aabbccddeeff", "binary_sensor", "presence") is False  # no-op
+    assert len(h) == 2
+
+
+def test_helper_rejects_non_discovery_topics() -> None:
+    h = HABlueprintHelper()
+    ok = h.add_payload("ruview/aabbccddeeff/raw/edge_vitals", _PRESENCE_BODY)
+    assert ok is False
+    assert len(h) == 0
+
+
+def test_helper_in_operator() -> None:
+    h = _populated_helper()
+    assert ("aabbccddeeff", "binary_sensor", "presence") in h
+    assert ("nonexistent", "binary_sensor", "presence") not in h

python/tests/test_client_mqtt.py

@@ -0,0 +1,208 @@
+"""ADR-117 P4 — Tests for RuViewMqttClient.
+
+These tests do NOT bring up a broker — they exercise:
+
+1. Topic-wildcard matching (`_topic_matches`)
+2. Client construction + handler registration
+3. The callback path by directly invoking the paho callback methods
+   with synthesized messages
+
+End-to-end broker integration is a P4-followon item (the mosquitto
+patterns from memory [[feedback_mqtt_integration_test_patterns]] go
+there). This file keeps unit coverage tight without requiring a
+broker on every CI run.
+"""
+
+from __future__ import annotations
+
+import json
+from types import SimpleNamespace
+from typing import Any
+
+import pytest
+
+from wifi_densepose.client import RuViewMqttClient
+from wifi_densepose.client.mqtt import _topic_matches
+
+
+# ─── Topic wildcard matcher ──────────────────────────────────────────
+
+
+@pytest.mark.parametrize("pattern,topic,expected", [
+    ("ruview/+/raw/edge_vitals", "ruview/aabb/raw/edge_vitals", True),
+    ("ruview/+/raw/edge_vitals", "ruview/aabb/cooked/edge_vitals", False),
+    ("ruview/+/raw/+", "ruview/aabb/raw/pose", True),
+    ("ruview/+/raw/+", "ruview/aabb/raw/pose/extra", False),
+    # Per MQTT v5 §4.7.1.2: `+` is a whole-level wildcard only — mid-
+    # segment `+` is a literal `+` character, not a wildcard. The
+    # spec-correct way to wildcard the third segment of the HA
+    # discovery topic is `homeassistant/+/+/+/config`.
+    ("homeassistant/+/+/+/config",
+     "homeassistant/binary_sensor/wifi_densepose_aabb/presence/config", True),
+    # `wifi_densepose_+` is therefore NOT a wildcard — it matches the
+    # literal string only. Asserting that behaviour stays stable.
+    ("homeassistant/+/wifi_densepose_+/+/config",
+     "homeassistant/binary_sensor/wifi_densepose_aabb/presence/config", False),
+    ("ruview/#", "ruview/aabb/raw/edge_vitals", True),
+    # Per MQTT v5 §4.7.1.2: `<prefix>/#` ALSO matches the bare
+    # `<prefix>` itself (it represents "this topic and all sub-topics").
+    ("ruview/#", "ruview", True),
+    ("ruview/+/raw/#", "ruview/aabb/raw/pose/extra", True),
+    ("exact/topic", "exact/topic", True),
+    ("exact/topic", "exact/topic/extra", False),
+    ("a/b/c", "a/b", False),
+])
+def test_topic_matches(pattern: str, topic: str, expected: bool) -> None:
+    assert _topic_matches(pattern, topic) is expected
+
+
+# ─── RuViewMqttClient construction ──────────────────────────────────
+
+
+def test_client_constructs_with_defaults() -> None:
+    c = RuViewMqttClient()
+    assert c.broker_host == "localhost"
+    assert c.broker_port == 1883
+    assert c.connected is False
+    assert c.client_id.startswith("wifi-densepose-client-")
+
+
+def test_client_unique_client_id_per_instance() -> None:
+    """Per the rumqttc memory lesson — each instance needs a unique
+    client_id so parallel tests don't kick each other off the broker."""
+    c1 = RuViewMqttClient()
+    c2 = RuViewMqttClient()
+    assert c1.client_id != c2.client_id
+
+
+def test_client_accepts_explicit_client_id() -> None:
+    c = RuViewMqttClient(client_id="explicit-id")
+    assert c.client_id == "explicit-id"
+
+
+# ─── Handler registration ────────────────────────────────────────────
+
+
+def test_handler_registration_stores_callback() -> None:
+    c = RuViewMqttClient()
+    seen: list[Any] = []
+    c.on_message("ruview/+/raw/edge_vitals", lambda t, p: seen.append((t, p)))
+    # Internal state — we're allowed to inspect since the handler
+    # path needs to be unit-testable without a broker.
+    assert "ruview/+/raw/edge_vitals" in c._handlers
+
+
+def test_handler_unregister_drops_callback() -> None:
+    c = RuViewMqttClient()
+    c.on_message("ruview/+/raw/edge_vitals", lambda t, p: None)
+    c.unsubscribe_handler("ruview/+/raw/edge_vitals")
+    assert "ruview/+/raw/edge_vitals" not in c._handlers
+
+
+# ─── Callback dispatch (synthesized) ─────────────────────────────────
+
+
+def _fake_message(topic: str, body: Any) -> Any:
+    """Synthesize a paho-mqtt MQTTMessage-ish object."""
+    if isinstance(body, (dict, list)):
+        payload_bytes = json.dumps(body).encode("utf-8")
+    elif isinstance(body, bytes):
+        payload_bytes = body
+    else:
+        payload_bytes = str(body).encode("utf-8")
+    return SimpleNamespace(topic=topic, payload=payload_bytes)
+
+
+def test_message_dispatch_to_matching_handler() -> None:
+    c = RuViewMqttClient()
+    received: list[tuple[str, Any]] = []
+    c.on_message("ruview/+/raw/edge_vitals", lambda t, p: received.append((t, p)))
+
+    msg = _fake_message(
+        "ruview/aabbccddeeff/raw/edge_vitals",
+        {"breathing_rate_bpm": 14.0, "heartrate_bpm": 72.0, "presence": True},
+    )
+    c._on_message(None, None, msg)
+
+    assert len(received) == 1
+    topic, payload = received[0]
+    assert topic == "ruview/aabbccddeeff/raw/edge_vitals"
+    assert payload["breathing_rate_bpm"] == 14.0
+
+
+def test_message_dispatch_ignores_non_matching_topic() -> None:
+    c = RuViewMqttClient()
+    received: list[Any] = []
+    c.on_message("ruview/+/raw/edge_vitals", lambda t, p: received.append(p))
+
+    msg = _fake_message("ruview/aabb/raw/pose", {"persons": []})
+    c._on_message(None, None, msg)
+
+    assert received == []
+
+
+def test_message_dispatch_falls_back_to_bytes_on_non_json() -> None:
+    c = RuViewMqttClient()
+    received: list[Any] = []
+    c.on_message("custom/binary/+", lambda t, p: received.append(p))
+
+    msg = _fake_message("custom/binary/data", b"\x00\x01\x02not-json")
+    c._on_message(None, None, msg)
+
+    assert received == [b"\x00\x01\x02not-json"]
+
+
+def test_handler_exception_does_not_propagate() -> None:
+    """A misbehaving user callback must not crash the paho network
+    loop — exceptions are caught and logged."""
+    c = RuViewMqttClient()
+    seen_after_crash: list[Any] = []
+
+    def crashing(_topic: str, _p: Any) -> None:
+        raise RuntimeError("simulated callback crash")
+
+    c.on_message("crashy/topic", crashing)
+    c.on_message("safe/topic", lambda t, p: seen_after_crash.append(p))
+
+    # First, the crashing handler — must NOT raise out of _on_message.
+    c._on_message(None, None, _fake_message("crashy/topic", "anything"))
+    # Then the safe handler — must still fire on a subsequent message.
+    c._on_message(None, None, _fake_message("safe/topic", {"x": 1}))
+    assert seen_after_crash == [{"x": 1}]
+
+
+def test_multiple_handlers_for_overlapping_patterns_all_fire() -> None:
+    c = RuViewMqttClient()
+    a_received: list[Any] = []
+    b_received: list[Any] = []
+    c.on_message("ruview/+/raw/+", lambda t, p: a_received.append(p))
+    c.on_message("ruview/aabb/raw/edge_vitals", lambda t, p: b_received.append(p))
+
+    msg = _fake_message("ruview/aabb/raw/edge_vitals", {"presence": True})
+    c._on_message(None, None, msg)
+
+    assert len(a_received) == 1
+    assert len(b_received) == 1
+
+
+# ─── on_connect path ─────────────────────────────────────────────────
+
+
+def test_on_connect_sets_event_and_subscribes() -> None:
+    c = RuViewMqttClient()
+    c.on_message("ruview/+/raw/edge_vitals", lambda t, p: None)
+
+    # Stub the paho client so we can capture subscribe() calls.
+    subscribed: list[str] = []
+    stub = SimpleNamespace(subscribe=lambda pattern: subscribed.append(pattern))
+
+    c._on_connect(stub, None, None, 0)
+    assert c.connected is True
+    assert subscribed == ["ruview/+/raw/edge_vitals"]
+
+
+def test_on_connect_with_nonzero_rc_does_not_set_connected() -> None:
+    c = RuViewMqttClient()
+    stub = SimpleNamespace(subscribe=lambda pattern: None)
+    c._on_connect(stub, None, None, 5)  # CONNACK fail
+    assert c.connected is False

python/tests/test_client_primitives.py

@@ -0,0 +1,180 @@
+"""ADR-117 P4 — Tests for the HA-MIND semantic primitive listener.
+
+Pure routing tests — no MQTT broker needed.
+"""
+
+from __future__ import annotations
+
+import json
+
+from wifi_densepose.client import (
+    SemanticPrimitive,
+    SemanticPrimitiveEvent,
+    SemanticPrimitiveListener,
+)
+
+
+# ─── SemanticPrimitive enum ──────────────────────────────────────────
+
+
+def test_enum_covers_all_10_v1_primitives() -> None:
+    expected = {
+        "someone_sleeping",
+        "possible_distress",
+        "room_active",
+        "elderly_inactivity",
+        "meeting_in_progress",
+        "bathroom_occupied",
+        "fall_risk_elevated",
+        "bed_exit",
+        "no_movement_safety",
+        "multi_room_transition",
+    }
+    actual = {p.value for p in SemanticPrimitive}
+    assert actual == expected
+
+
+def test_enum_from_object_id_round_trips() -> None:
+    for p in SemanticPrimitive:
+        assert SemanticPrimitive.from_object_id(p.value) is p
+
+
+def test_enum_from_object_id_returns_none_for_unknown() -> None:
+    assert SemanticPrimitive.from_object_id("garbage") is None
+
+
+# ─── Listener routing ────────────────────────────────────────────────
+
+
+def test_listener_dispatches_to_specific_handler() -> None:
+    listener = SemanticPrimitiveListener()
+    received: list[SemanticPrimitiveEvent] = []
+    listener.on(SemanticPrimitive.SomeoneSleeping, received.append)
+
+    evt = listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aabb/someone_sleeping/state",
+        json.dumps({"state": "ON", "confidence": 0.92, "explanation": ["motion<5%"]}),
+    )
+    assert evt is not None
+    assert evt.kind is SemanticPrimitive.SomeoneSleeping
+    assert evt.node_id == "aabb"
+    assert evt.state == "ON"
+    assert evt.confidence == 0.92
+    assert evt.explanation == ("motion<5%",)
+    assert len(received) == 1
+    assert received[0] is evt
+
+
+def test_listener_on_any_fires_for_every_primitive() -> None:
+    listener = SemanticPrimitiveListener()
+    seen: list[SemanticPrimitiveEvent] = []
+    listener.on_any(seen.append)
+
+    listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aabb/room_active/state",
+        json.dumps({"state": "ON"}),
+    )
+    listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aabb/bathroom_occupied/state",
+        json.dumps({"state": "OFF"}),
+    )
+    assert len(seen) == 2
+    assert seen[0].kind is SemanticPrimitive.RoomActive
+    assert seen[1].kind is SemanticPrimitive.BathroomOccupied
+
+
+def test_listener_specific_handler_does_not_fire_for_other_primitives() -> None:
+    listener = SemanticPrimitiveListener()
+    received: list[SemanticPrimitiveEvent] = []
+    listener.on(SemanticPrimitive.PossibleDistress, received.append)
+
+    listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aabb/someone_sleeping/state",
+        json.dumps({"state": "ON"}),
+    )
+    assert received == []
+
+
+def test_listener_decodes_plain_state_string() -> None:
+    """HA convention: binary_sensors that don't carry attributes emit
+    plain strings ('ON' / 'OFF'). We must accept that too."""
+    listener = SemanticPrimitiveListener()
+    evt = listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aabb/room_active/state",
+        "ON",
+    )
+    assert evt is not None
+    assert evt.state == "ON"
+    assert evt.confidence == 0.0  # not provided in plain string
+    assert evt.explanation == ()
+
+
+def test_listener_decodes_numeric_sensor_state() -> None:
+    """fall_risk_elevated is a 0–100 sensor — verify numeric string."""
+    listener = SemanticPrimitiveListener()
+    evt = listener.handle_mqtt_message(
+        "homeassistant/sensor/wifi_densepose_aabb/fall_risk_elevated/state",
+        "73",
+    )
+    assert evt is not None
+    assert evt.kind is SemanticPrimitive.FallRiskElevated
+    assert evt.state == "73"
+
+
+def test_listener_decodes_bytes_payload() -> None:
+    listener = SemanticPrimitiveListener()
+    evt = listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aabb/room_active/state",
+        b"ON",
+    )
+    assert evt is not None
+    assert evt.state == "ON"
+
+
+def test_listener_ignores_non_state_topics() -> None:
+    listener = SemanticPrimitiveListener()
+    assert listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aabb/room_active/config",
+        json.dumps({"name": "Room Active"}),
+    ) is None
+
+
+def test_listener_ignores_unknown_slug() -> None:
+    listener = SemanticPrimitiveListener()
+    assert listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aabb/unknown_primitive/state",
+        "ON",
+    ) is None
+
+
+def test_listener_ignores_non_wifi_densepose_node() -> None:
+    listener = SemanticPrimitiveListener()
+    # third segment doesn't start with wifi_densepose_
+    assert listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/aqara_fp2/room_active/state",
+        "ON",
+    ) is None
+
+
+def test_listener_explanation_string_is_normalised_to_tuple() -> None:
+    """Producers may send `explanation` as a single string by mistake;
+    accept that and wrap in a 1-tuple so downstream code can iterate
+    uniformly."""
+    listener = SemanticPrimitiveListener()
+    evt = listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aabb/possible_distress/state",
+        json.dumps({"state": "ON", "explanation": "HR=120 baseline=80"}),
+    )
+    assert evt is not None
+    assert evt.explanation == ("HR=120 baseline=80",)
+
+
+def test_event_is_frozen() -> None:
+    evt = SemanticPrimitiveEvent(
+        kind=SemanticPrimitive.SomeoneSleeping,
+        node_id="aabb",
+        state="ON",
+    )
+    import pytest
+    with pytest.raises((AttributeError, Exception)):  # FrozenInstanceError subclass
+        evt.state = "OFF"  # type: ignore[misc]

python/tests/test_client_ws.py

@@ -0,0 +1,195 @@
+"""ADR-117 P4 — End-to-end test for SensingClient against an in-process
+WS server.
+
+We spin up a real `websockets.serve()` server in the same event loop,
+send the four message types defined in ADR-115 §1, and assert the
+client decodes them into the right dataclasses. No mocks — the only
+moving part this test does NOT exercise is the actual sensing-server
+binary, but the wire protocol is the contract under test here.
+"""
+
+from __future__ import annotations
+
+import asyncio
+import json
+from typing import Any
+
+import pytest
+import websockets
+
+from wifi_densepose.client import (
+    ConnectionEstablishedMessage,
+    EdgeVitalsMessage,
+    PoseDataMessage,
+    SensingClient,
+    SensingMessage,
+)
+
+
+# ─── In-process WS server fixture ────────────────────────────────────
+
+
+_FIXTURE_MESSAGES = [
+    {
+        "type": "connection_established",
+        "node_id": "test-node-001",
+        "version": "0.7.4",
+        "capabilities": ["edge_vitals", "pose_data"],
+    },
+    {
+        "type": "edge_vitals",
+        "node_id": "test-node-001",
+        "presence": True,
+        "fall_detected": False,
+        "motion": 0.21,
+        "breathing_rate_bpm": 14.5,
+        "heartrate_bpm": 72.3,
+        "n_persons": 1,
+        "motion_energy": 0.034,
+        "presence_score": 0.91,
+        "rssi": -42.0,
+    },
+    {
+        "type": "pose_data",
+        "node_id": "test-node-001",
+        "timestamp": 1700000000.5,
+        "persons": [{"id": 1, "keypoints": []}],
+        "confidence": 0.88,
+    },
+    # Unknown type — should NOT crash the stream; should yield a plain
+    # SensingMessage.
+    {
+        "type": "future_message_type_not_yet_modelled",
+        "extra": "data",
+    },
+]
+
+
+async def _handler(websocket: Any) -> None:
+    for msg in _FIXTURE_MESSAGES:
+        await websocket.send(json.dumps(msg))
+    # Send one malformed frame to assert the client logs+drops it
+    # rather than crashing the stream.
+    await websocket.send("{not valid json")
+    # And one final "real" message so the test can confirm the stream
+    # survived the malformed one.
+    await websocket.send(json.dumps({"type": "edge_vitals", "node_id": "post-bad-frame"}))
+
+
+@pytest.fixture
+async def ws_server() -> Any:
+    """Start a websocket server on a random port; yield the bound URL."""
+    server = await websockets.serve(_handler, "127.0.0.1", 0)
+    # Get the bound port (host="127.0.0.1" returns one socket).
+    port = server.sockets[0].getsockname()[1]  # type: ignore[union-attr]
+    try:
+        yield f"ws://127.0.0.1:{port}/ws/sensing"
+    finally:
+        server.close()
+        await server.wait_closed()
+
+
+# ─── End-to-end stream test ──────────────────────────────────────────
+
+
+async def test_sensing_client_decodes_all_message_types(ws_server: str) -> None:
+    received: list[SensingMessage] = []
+    async with SensingClient(ws_server) as client:
+        async for msg in client.stream():
+            received.append(msg)
+            if len(received) >= len(_FIXTURE_MESSAGES) + 1:  # +1 for post-bad-frame
+                break
+
+    # connection_established → typed
+    assert isinstance(received[0], ConnectionEstablishedMessage)
+    assert received[0].node_id == "test-node-001"
+    assert received[0].version == "0.7.4"
+    assert "edge_vitals" in received[0].capabilities
+
+    # edge_vitals → typed with full fields
+    assert isinstance(received[1], EdgeVitalsMessage)
+    assert received[1].presence is True
+    assert received[1].fall_detected is False
+    assert received[1].breathing_rate_bpm == 14.5
+    assert received[1].heartrate_bpm == 72.3
+    assert received[1].n_persons == 1
+    assert received[1].rssi == -42.0
+
+    # pose_data → typed
+    assert isinstance(received[2], PoseDataMessage)
+    assert received[2].timestamp == 1700000000.5
+    assert len(received[2].persons) == 1
+    assert received[2].confidence == 0.88
+
+    # Unknown type → plain SensingMessage (forward-compat)
+    assert type(received[3]) is SensingMessage  # exact base class
+    assert received[3].type == "future_message_type_not_yet_modelled"
+    assert received[3].raw["extra"] == "data"
+
+    # After the malformed frame: the stream should have survived and
+    # yielded the post-bad-frame message.
+    assert isinstance(received[4], EdgeVitalsMessage)
+    assert received[4].node_id == "post-bad-frame"
+
+
+async def test_sensing_client_recv_one(ws_server: str) -> None:
+    async with SensingClient(ws_server) as client:
+        msg = await client.recv_one(timeout=2.0)
+    assert isinstance(msg, ConnectionEstablishedMessage)
+
+
+async def test_sensing_client_raises_when_used_without_context() -> None:
+    client = SensingClient("ws://127.0.0.1:1/")  # never connects
+    with pytest.raises(RuntimeError, match="not connected"):
+        await client.recv_one(timeout=0.1)
+    with pytest.raises(RuntimeError, match="not connected"):
+        async for _ in client.stream():
+            pass
+
+
+async def test_sensing_client_close_is_idempotent(ws_server: str) -> None:
+    client = SensingClient(ws_server)
+    await client.__aenter__()
+    await client.close()
+    await client.close()  # second close is a no-op
+
+
+def test_sensing_client_decoder_directly() -> None:
+    """The decoder is pure — exercise it without bringing up a WS
+    server, so we have a fast unit test for the type mapping."""
+    from wifi_densepose.client.ws import _decode
+
+    msg = _decode(json.dumps({
+        "type": "edge_vitals",
+        "node_id": "x",
+        "presence": True,
+        "fall_detected": False,
+        "motion": 1.5,
+    }))
+    assert isinstance(msg, EdgeVitalsMessage)
+    assert msg.presence is True
+    assert msg.motion == 1.5
+    assert msg.breathing_rate_bpm is None  # not present → None, not 0.0
+    assert msg.heartrate_bpm is None
+    assert msg.rssi is None
+
+
+def test_sensing_client_decoder_handles_None_subfields() -> None:
+    """When the sensing-server explicitly emits null for HR/BR (no
+    measurement yet), the client should propagate None, not crash."""
+    from wifi_densepose.client.ws import _decode
+
+    msg = _decode(json.dumps({
+        "type": "edge_vitals",
+        "node_id": "x",
+        "presence": False,
+        "fall_detected": False,
+        "motion": 0.0,
+        "breathing_rate_bpm": None,
+        "heartrate_bpm": None,
+        "rssi": None,
+    }))
+    assert isinstance(msg, EdgeVitalsMessage)
+    assert msg.breathing_rate_bpm is None
+    assert msg.heartrate_bpm is None
+    assert msg.rssi is None

python/tests/test_keypoint.py

@@ -0,0 +1,200 @@
+"""ADR-117 P2 tests — Keypoint + KeypointType binding round-trips.
+
+Run with: cd python && .venv/Scripts/python -m pytest tests/test_keypoint.py -v
+"""
+
+from __future__ import annotations
+
+import pytest
+
+from wifi_densepose import Keypoint, KeypointType
+
+
+# ─── KeypointType ────────────────────────────────────────────────────
+
+
+def test_keypoint_type_all_returns_17() -> None:
+    """COCO standard defines exactly 17 keypoints."""
+    assert len(KeypointType.all()) == 17
+
+
+def test_keypoint_type_index_matches_coco_ordering() -> None:
+    """Indexes 0..16 match the COCO canonical ordering."""
+    expected = [
+        (KeypointType.Nose, 0),
+        (KeypointType.LeftEye, 1),
+        (KeypointType.RightEye, 2),
+        (KeypointType.LeftEar, 3),
+        (KeypointType.RightEar, 4),
+        (KeypointType.LeftShoulder, 5),
+        (KeypointType.RightShoulder, 6),
+        (KeypointType.LeftElbow, 7),
+        (KeypointType.RightElbow, 8),
+        (KeypointType.LeftWrist, 9),
+        (KeypointType.RightWrist, 10),
+        (KeypointType.LeftHip, 11),
+        (KeypointType.RightHip, 12),
+        (KeypointType.LeftKnee, 13),
+        (KeypointType.RightKnee, 14),
+        (KeypointType.LeftAnkle, 15),
+        (KeypointType.RightAnkle, 16),
+    ]
+    for kp, idx in expected:
+        assert kp.index == idx, f"{kp} expected index {idx} got {kp.index}"
+
+
+def test_keypoint_type_snake_name() -> None:
+    """snake_name follows COCO convention."""
+    assert KeypointType.Nose.snake_name == "nose"
+    assert KeypointType.LeftShoulder.snake_name == "left_shoulder"
+    assert KeypointType.RightAnkle.snake_name == "right_ankle"
+
+
+def test_keypoint_type_is_face() -> None:
+    """is_face() matches the 5 facial keypoints."""
+    face = {
+        KeypointType.Nose,
+        KeypointType.LeftEye,
+        KeypointType.RightEye,
+        KeypointType.LeftEar,
+        KeypointType.RightEar,
+    }
+    for kp in KeypointType.all():
+        assert kp.is_face() == (kp in face)
+
+
+def test_keypoint_type_is_upper_body() -> None:
+    """is_upper_body() catches shoulders, elbows, wrists."""
+    assert KeypointType.LeftShoulder.is_upper_body()
+    assert KeypointType.RightShoulder.is_upper_body()
+    assert KeypointType.LeftElbow.is_upper_body()
+    assert KeypointType.LeftWrist.is_upper_body()
+    assert not KeypointType.LeftHip.is_upper_body()
+
+
+def test_keypoint_type_eq() -> None:
+    """Equality + identity work across calls."""
+    assert KeypointType.Nose == KeypointType.Nose
+    assert KeypointType.Nose != KeypointType.LeftEye
+
+
+def test_keypoint_type_repr() -> None:
+    """repr is a useful Python expression."""
+    assert repr(KeypointType.Nose) == "KeypointType.Nose"
+    assert repr(KeypointType.LeftWrist) == "KeypointType.LeftWrist"
+
+
+# ─── Keypoint ────────────────────────────────────────────────────────
+
+
+def test_keypoint_2d_construct() -> None:
+    """Default 2D keypoint."""
+    kp = Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95)
+    assert kp.x == pytest.approx(0.5)
+    assert kp.y == pytest.approx(0.3)
+    assert kp.z is None
+    assert kp.confidence == pytest.approx(0.95)
+    assert kp.keypoint_type == KeypointType.Nose
+    assert kp.is_visible
+
+
+def test_keypoint_3d_construct() -> None:
+    """3D keypoint with kwarg z."""
+    kp = Keypoint(KeypointType.LeftWrist, 0.2, 0.4, 0.8, z=0.1)
+    assert kp.position_3d == pytest.approx((0.2, 0.4, 0.1))
+    assert kp.z == pytest.approx(0.1)
+
+
+def test_keypoint_position_2d_tuple() -> None:
+    kp = Keypoint(KeypointType.RightHip, 0.6, 0.7, 0.99)
+    assert kp.position_2d == pytest.approx((0.6, 0.7))
+
+
+def test_keypoint_position_3d_none_for_2d() -> None:
+    """2D keypoints return None for position_3d, not a default z."""
+    kp = Keypoint(KeypointType.Nose, 0.5, 0.5, 0.99)
+    assert kp.position_3d is None
+
+
+def test_keypoint_is_visible_below_threshold() -> None:
+    """Confidence under 0.5 is NOT visible (default threshold)."""
+    kp_low = Keypoint(KeypointType.Nose, 0.0, 0.0, 0.3)
+    kp_high = Keypoint(KeypointType.Nose, 0.0, 0.0, 0.7)
+    assert not kp_low.is_visible
+    assert kp_high.is_visible
+
+
+def test_keypoint_confidence_validation_too_high() -> None:
+    """Confidence > 1.0 rejected."""
+    with pytest.raises(ValueError, match="Confidence must be in"):
+        Keypoint(KeypointType.Nose, 0.0, 0.0, 1.5)
+
+
+def test_keypoint_confidence_validation_negative() -> None:
+    """Negative confidence rejected."""
+    with pytest.raises(ValueError, match="Confidence must be in"):
+        Keypoint(KeypointType.Nose, 0.0, 0.0, -0.1)
+
+
+def test_keypoint_distance_2d() -> None:
+    """Euclidean distance in 2D."""
+    a = Keypoint(KeypointType.Nose, 0.0, 0.0, 1.0)
+    b = Keypoint(KeypointType.LeftEye, 3.0, 4.0, 1.0)
+    assert a.distance_to(b) == pytest.approx(5.0)
+
+
+def test_keypoint_distance_3d() -> None:
+    """Euclidean distance in 3D when both have z."""
+    a = Keypoint(KeypointType.Nose, 0.0, 0.0, 1.0, z=0.0)
+    b = Keypoint(KeypointType.LeftEye, 1.0, 2.0, 1.0, z=2.0)
+    # sqrt(1 + 4 + 4) = 3.0
+    assert a.distance_to(b) == pytest.approx(3.0)
+
+
+def test_keypoint_distance_falls_back_to_2d_if_mixed() -> None:
+    """Mixing 2D and 3D keypoints uses 2D distance only."""
+    a = Keypoint(KeypointType.Nose, 0.0, 0.0, 1.0)  # 2D
+    b = Keypoint(KeypointType.LeftEye, 3.0, 4.0, 1.0, z=99.0)  # 3D
+    # Should be 5.0 (2D distance), not include the z=99 term
+    assert a.distance_to(b) == pytest.approx(5.0)
+
+
+def test_keypoint_repr_2d() -> None:
+    kp = Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95)
+    r = repr(kp)
+    assert "KeypointType.Nose" in r
+    assert "x=0.5" in r
+    assert "y=0.3" in r
+    assert "z" not in r  # no z field for 2D
+
+
+def test_keypoint_repr_3d() -> None:
+    kp = Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95, z=0.1)
+    r = repr(kp)
+    assert "z=0.1" in r
+
+
+def test_keypoint_eq() -> None:
+    """Two keypoints with same fields compare equal."""
+    a = Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95)
+    b = Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95)
+    assert a == b
+
+
+def test_keypoint_neq_different_type() -> None:
+    a = Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95)
+    b = Keypoint(KeypointType.LeftEye, 0.5, 0.3, 0.95)
+    assert a != b
+
+
+def test_keypoint_neq_different_position() -> None:
+    a = Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95)
+    b = Keypoint(KeypointType.Nose, 0.6, 0.3, 0.95)
+    assert a != b
+
+
+def test_build_features_marks_p2() -> None:
+    """The P2 marker is now in the wheel's feature list."""
+    import wifi_densepose
+
+    assert "p2-keypoint-bindings" in wifi_densepose.__build_features__

python/tests/test_pose.py

@@ -0,0 +1,248 @@
+"""ADR-117 P2 tests — BoundingBox + PersonPose + PoseEstimate bindings.
+
+Run with: cd python && .venv/Scripts/python -m pytest tests/test_pose.py -v
+"""
+
+from __future__ import annotations
+
+import pytest
+
+from wifi_densepose import (
+    BoundingBox,
+    Keypoint,
+    KeypointType,
+    PersonPose,
+    PoseEstimate,
+)
+
+
+# ─── BoundingBox ─────────────────────────────────────────────────────
+
+
+def test_bounding_box_construct() -> None:
+    bb = BoundingBox(0.1, 0.2, 0.5, 0.7)
+    assert bb.x_min == pytest.approx(0.1)
+    assert bb.y_min == pytest.approx(0.2)
+    assert bb.x_max == pytest.approx(0.5)
+    assert bb.y_max == pytest.approx(0.7)
+
+
+def test_bounding_box_dimensions() -> None:
+    bb = BoundingBox(0.0, 0.0, 4.0, 3.0)
+    assert bb.width == pytest.approx(4.0)
+    assert bb.height == pytest.approx(3.0)
+    assert bb.area == pytest.approx(12.0)
+    assert bb.center == pytest.approx((2.0, 1.5))
+
+
+def test_bounding_box_from_center() -> None:
+    bb = BoundingBox.from_center(2.0, 3.0, 4.0, 6.0)
+    assert bb.x_min == pytest.approx(0.0)
+    assert bb.y_min == pytest.approx(0.0)
+    assert bb.x_max == pytest.approx(4.0)
+    assert bb.y_max == pytest.approx(6.0)
+
+
+def test_bounding_box_iou_no_overlap() -> None:
+    a = BoundingBox(0.0, 0.0, 1.0, 1.0)
+    b = BoundingBox(2.0, 2.0, 3.0, 3.0)
+    assert a.iou(b) == pytest.approx(0.0)
+
+
+def test_bounding_box_iou_full_overlap() -> None:
+    a = BoundingBox(0.0, 0.0, 1.0, 1.0)
+    b = BoundingBox(0.0, 0.0, 1.0, 1.0)
+    assert a.iou(b) == pytest.approx(1.0)
+
+
+def test_bounding_box_iou_partial() -> None:
+    a = BoundingBox(0.0, 0.0, 10.0, 10.0)
+    b = BoundingBox(5.0, 5.0, 15.0, 15.0)
+    # intersection 25, union 175 → 1/7
+    assert a.iou(b) == pytest.approx(25.0 / 175.0)
+
+
+def test_bounding_box_eq() -> None:
+    assert BoundingBox(1, 2, 3, 4) == BoundingBox(1, 2, 3, 4)
+    assert BoundingBox(1, 2, 3, 4) != BoundingBox(1, 2, 3, 5)
+
+
+def test_bounding_box_repr() -> None:
+    bb = BoundingBox(0.1, 0.2, 0.5, 0.7)
+    assert "BoundingBox" in repr(bb)
+    assert "x_min=0.1" in repr(bb)
+
+
+# ─── PersonPose ──────────────────────────────────────────────────────
+
+
+def test_person_pose_empty() -> None:
+    p = PersonPose()
+    assert p.id is None
+    assert p.visible_keypoint_count == 0
+    assert p.bounding_box is None
+    assert p.confidence == 0.0
+
+
+def test_person_pose_set_get_keypoint() -> None:
+    p = PersonPose()
+    kp = Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95)
+    p.set_keypoint(kp)
+    got = p.get_keypoint(KeypointType.Nose)
+    assert got is not None
+    assert got.x == pytest.approx(0.5)
+    assert got.confidence == pytest.approx(0.95)
+
+
+def test_person_pose_get_missing_returns_none() -> None:
+    p = PersonPose()
+    p.set_keypoint(Keypoint(KeypointType.Nose, 0.5, 0.3, 0.95))
+    assert p.get_keypoint(KeypointType.LeftWrist) is None
+
+
+def test_person_pose_visible_count() -> None:
+    p = PersonPose()
+    p.set_keypoint(Keypoint(KeypointType.Nose, 0.0, 0.0, 0.9))  # visible
+    p.set_keypoint(Keypoint(KeypointType.LeftEar, 0.0, 0.0, 0.2))  # invisible
+    p.set_keypoint(Keypoint(KeypointType.RightEar, 0.0, 0.0, 0.8))  # visible
+    assert p.visible_keypoint_count == 2
+
+
+def test_person_pose_visible_keypoints_list() -> None:
+    p = PersonPose()
+    p.set_keypoint(Keypoint(KeypointType.Nose, 0.0, 0.0, 0.9))
+    p.set_keypoint(Keypoint(KeypointType.LeftEar, 0.0, 0.0, 0.2))
+    vis = p.visible_keypoints()
+    assert len(vis) == 1
+    assert vis[0].keypoint_type == KeypointType.Nose
+
+
+def test_person_pose_keypoints_dict_excludes_missing() -> None:
+    p = PersonPose()
+    p.set_keypoint(Keypoint(KeypointType.Nose, 0.0, 0.0, 0.9))
+    p.set_keypoint(Keypoint(KeypointType.LeftWrist, 0.5, 0.5, 0.6))
+    d = p.keypoints()
+    assert KeypointType.Nose in d
+    assert KeypointType.LeftWrist in d
+    assert KeypointType.RightAnkle not in d
+    assert len(d) == 2
+
+
+def test_person_pose_set_id() -> None:
+    p = PersonPose()
+    p.set_id(7)
+    assert p.id == 7
+
+
+def test_person_pose_set_bounding_box() -> None:
+    p = PersonPose()
+    bb = BoundingBox(0.1, 0.1, 0.5, 0.9)
+    p.set_bounding_box(bb)
+    assert p.bounding_box == bb
+
+
+def test_person_pose_compute_bbox_returns_none_when_empty() -> None:
+    p = PersonPose()
+    assert p.compute_bounding_box() is None
+
+
+def test_person_pose_compute_bbox_from_keypoints() -> None:
+    p = PersonPose()
+    p.set_keypoint(Keypoint(KeypointType.Nose, 0.0, 0.0, 0.95))
+    p.set_keypoint(Keypoint(KeypointType.RightAnkle, 1.0, 2.0, 0.95))
+    bb = p.compute_bounding_box()
+    assert bb is not None
+    # bbox should span both keypoints
+    assert bb.x_min <= 0.0
+    assert bb.y_min <= 0.0
+    assert bb.x_max >= 1.0
+    assert bb.y_max >= 2.0
+    # also stored
+    assert p.bounding_box is not None
+
+
+def test_person_pose_set_confidence_validation() -> None:
+    p = PersonPose()
+    p.set_confidence(0.85)
+    assert p.confidence == pytest.approx(0.85)
+    with pytest.raises(ValueError):
+        p.set_confidence(1.5)
+
+
+def test_person_pose_repr() -> None:
+    p = PersonPose()
+    p.set_id(3)
+    p.set_keypoint(Keypoint(KeypointType.Nose, 0.0, 0.0, 0.9))
+    r = repr(p)
+    assert "PersonPose" in r
+    assert "id=Some(3)" in r or "id=3" in r
+
+
+# ─── PoseEstimate ────────────────────────────────────────────────────
+
+
+def test_pose_estimate_construct_empty() -> None:
+    e = PoseEstimate([], 0.5, 1.0, "test-v0")
+    assert e.person_count == 0
+    assert not e.has_detections
+    assert e.confidence == pytest.approx(0.5)
+    assert e.latency_ms == pytest.approx(1.0)
+    assert e.model_version == "test-v0"
+
+
+def test_pose_estimate_construct_with_persons() -> None:
+    p1 = PersonPose()
+    p1.set_id(1)
+    p1.set_confidence(0.8)
+    p2 = PersonPose()
+    p2.set_id(2)
+    p2.set_confidence(0.9)
+    e = PoseEstimate([p1, p2], 0.85, 5.2, "v0.7.0")
+    assert e.person_count == 2
+    assert e.has_detections
+    assert e.confidence == pytest.approx(0.85)
+
+
+def test_pose_estimate_highest_confidence_person() -> None:
+    p1 = PersonPose()
+    p1.set_confidence(0.5)
+    p2 = PersonPose()
+    p2.set_confidence(0.95)
+    p3 = PersonPose()
+    p3.set_confidence(0.7)
+    e = PoseEstimate([p1, p2, p3], 0.85, 5.2, "v0.7.0")
+    best = e.highest_confidence_person()
+    assert best is not None
+    assert best.confidence == pytest.approx(0.95)
+
+
+def test_pose_estimate_highest_confidence_returns_none_when_empty() -> None:
+    e = PoseEstimate([], 0.5, 1.0, "test")
+    assert e.highest_confidence_person() is None
+
+
+def test_pose_estimate_metadata_strings_nonempty() -> None:
+    e = PoseEstimate([], 0.5, 1.0, "test")
+    assert isinstance(e.id, str)
+    assert isinstance(e.timestamp, str)
+    assert e.id  # non-empty
+    assert e.timestamp  # non-empty
+
+
+def test_pose_estimate_confidence_validation() -> None:
+    with pytest.raises(ValueError):
+        PoseEstimate([], 1.5, 0.0, "test")
+
+
+def test_pose_estimate_repr_contains_counts() -> None:
+    e = PoseEstimate([], 0.5, 2.3, "v0.7.0")
+    r = repr(e)
+    assert "PoseEstimate" in r
+    assert "v0.7.0" in r
+
+
+def test_build_features_marks_p2_complete() -> None:
+    import wifi_densepose
+
+    assert "p2-keypoint-bindings" in wifi_densepose.__build_features__
+    assert "p2-pose-bindings" in wifi_densepose.__build_features__

python/tests/test_security.py

@@ -0,0 +1,260 @@
+"""ADR-117 hardening sweep — Security & robustness tests for the
+client surface.
+
+Scope: malformed/hostile input handling across the WS decoder, MQTT
+matcher + dispatch, HA discovery parser, and semantic primitive
+listener. The goal is to ensure that an adversarial broker or
+sensing-server can't:
+
+- Crash the client process via malformed JSON, UTF-8, or topic shapes
+- Bypass topic-wildcard matching to deliver messages to the wrong handler
+- Leak MQTT credentials through `repr()` or string conversion
+- Trigger unbounded memory growth via deeply-nested JSON
+- Get a handler exception to crash the network loop
+"""
+
+from __future__ import annotations
+
+import json
+from types import SimpleNamespace
+
+import pytest
+
+from wifi_densepose.client import RuViewMqttClient, SemanticPrimitiveListener
+from wifi_densepose.client.ha import (
+    HABlueprintHelper,
+    parse_discovery_payload,
+    parse_discovery_topic,
+)
+from wifi_densepose.client.mqtt import _topic_matches
+from wifi_densepose.client.ws import _decode
+
+
+# ─── WS decoder robustness ──────────────────────────────────────────
+
+
+def test_ws_decoder_rejects_non_object_root() -> None:
+    """A JSON array at the root must NOT crash the decoder. Plain
+    string/array root values are valid JSON but not valid sensing-
+    server messages — the decoder must reject them cleanly."""
+    with pytest.raises(ValueError):
+        _decode("[1, 2, 3]")
+    with pytest.raises(ValueError):
+        _decode('"just a string"')
+    with pytest.raises(ValueError):
+        _decode("42")
+
+
+def test_ws_decoder_rejects_malformed_json() -> None:
+    with pytest.raises(json.JSONDecodeError):
+        _decode("{ broken: json")
+
+
+def test_ws_decoder_handles_deeply_nested_payload_without_crash() -> None:
+    """Hostile JSON nested 1000 levels deep must not crash via
+    Python's default recursion limit. Json.loads has a built-in
+    guard; verify we don't accidentally bypass it."""
+    nested = "{" + '"a":{' * 999 + '"x":1' + "}" * 1000
+    # json.loads either succeeds (since 999 < ~1000 limit) or raises
+    # RecursionError; either is acceptable — the key is no segfault
+    # or hang.
+    try:
+        _decode(nested)
+    except (RecursionError, json.JSONDecodeError, ValueError):
+        pass  # All acceptable.
+
+
+def test_ws_decoder_handles_huge_string_values() -> None:
+    """A 1 MB string in a JSON field must decode without exploding.
+    The websockets `max_size` parameter (default 16 MB) is the actual
+    DoS guard — this just confirms the decoder itself is linear."""
+    huge_payload = json.dumps({
+        "type": "edge_vitals",
+        "node_id": "x" * (1024 * 1024),  # 1 MB string
+        "presence": True,
+        "fall_detected": False,
+        "motion": 0.0,
+    })
+    msg = _decode(huge_payload)
+    assert msg.type == "edge_vitals"
+
+
+def test_ws_decoder_handles_unicode_in_node_id() -> None:
+    """Non-ASCII node IDs (e.g. accidental terminal escapes) must
+    round-trip cleanly without re-encoding errors."""
+    payload = json.dumps({"type": "edge_vitals", "node_id": "nöde-中", "presence": True, "fall_detected": False, "motion": 0.0})
+    msg = _decode(payload)
+    assert msg.node_id == "nöde-中"  # type: ignore[attr-defined]
+
+
+# ─── MQTT topic matcher — exhaustive edge cases ─────────────────────
+
+
+@pytest.mark.parametrize("pattern,topic,expected", [
+    # Empty / boundary
+    ("", "", True),
+    ("a", "", False),
+    ("", "a", False),
+    # `+` cannot bypass a literal level boundary
+    ("a/+/c", "a/b/c", True),
+    ("a/+/c", "a/b/d", False),
+    ("a/+/c", "a/b/c/d", False),
+    # `#` is greedy from its position but does not match if it's
+    # mid-pattern (per MQTT spec; our matcher returns False then).
+    ("a/#/c", "a/b/c", False),  # `#` must be terminal
+    # Topics starting with `$` are legal here — we don't filter them;
+    # matching is purely syntactic. `+` is one-level only, so `$SYS/+`
+    # matches `$SYS/broker` but NOT `$SYS/broker/version`.
+    ("$SYS/+", "$SYS/broker", True),
+    ("$SYS/+", "$SYS/broker/version", False),
+    ("$SYS/#", "$SYS/broker/version", True),
+    # Null byte in topic: still string comparison, but useful to lock
+    # down behaviour.
+    ("a/b", "a\x00/b", False),
+])
+def test_topic_matcher_edge_cases(pattern: str, topic: str, expected: bool) -> None:
+    assert _topic_matches(pattern, topic) is expected
+
+
+# ─── MQTT credential confidentiality ────────────────────────────────
+
+
+def test_mqtt_password_never_in_repr() -> None:
+    """A user's broker password must NOT leak through __repr__ or
+    __str__. Currently RuViewMqttClient doesn't define repr — that's
+    the safest default (uses object identity). Lock that down so a
+    future "let's add a friendly repr" change doesn't expose creds."""
+    c = RuViewMqttClient(
+        broker_host="broker.example.com",
+        username="alice",
+        password="super-secret-token-do-not-leak",
+    )
+    rep = repr(c)
+    s = str(c)
+    assert "super-secret-token-do-not-leak" not in rep
+    assert "super-secret-token-do-not-leak" not in s
+
+
+def test_mqtt_password_never_stored_in_plain_attribute() -> None:
+    """The plaintext password must not be stored on the client
+    instance — paho-mqtt internalises it into `_client._username_pw`
+    which we never expose. Audit by walking the public dict."""
+    c = RuViewMqttClient(password="dont-leak-me")
+    for k, v in vars(c).items():
+        if isinstance(v, str):
+            assert "dont-leak-me" not in v, f"password leaked via attribute {k!r}"
+
+
+# ─── HA discovery — adversarial topics ──────────────────────────────
+
+
+def test_ha_discovery_rejects_topic_with_null_byte() -> None:
+    """Defensive: regex must not match a null-byte-laced topic."""
+    bad = "homeassistant/binary_sensor/wifi_densepose_aa\x00bb/presence/config"
+    assert parse_discovery_topic(bad) is None
+    assert parse_discovery_payload(bad, {"name": "x"}) is None
+
+
+def test_ha_discovery_rejects_topic_with_slash_in_node_id() -> None:
+    """A node_id with embedded slashes would break the unique_id
+    contract; reject."""
+    bad = "homeassistant/binary_sensor/wifi_densepose_aa/bb/presence/config"
+    # The regex won't match because there are too many segments.
+    assert parse_discovery_topic(bad) is None
+
+
+def test_ha_helper_drops_invalid_topic_silently() -> None:
+    """`add_payload` should return False (not raise) for non-discovery
+    topics so a misconfigured broker doesn't bring down the client."""
+    h = HABlueprintHelper()
+    assert h.add_payload("garbage", {"x": 1}) is False
+    assert h.add_payload("ruview/aa/raw/edge_vitals", {"x": 1}) is False
+    assert len(h) == 0
+
+
+def test_ha_helper_handles_non_dict_payload() -> None:
+    """If the HA discovery body is a list or scalar (broken producer),
+    the helper must reject rather than crash on attribute access."""
+    h = HABlueprintHelper()
+    topic = "homeassistant/binary_sensor/wifi_densepose_aabb/presence/config"
+    assert h.add_payload(topic, "[1, 2, 3]") is False
+    assert h.add_payload(topic, "42") is False
+    assert h.add_payload(topic, b"\xff\xfe invalid utf-8") is False
+
+
+# ─── Semantic primitive listener — adversarial input ────────────────
+
+
+def test_primitive_listener_ignores_topic_injection_attempts() -> None:
+    listener = SemanticPrimitiveListener()
+    # Extra leading segments
+    assert listener.handle_mqtt_message(
+        "evil/homeassistant/binary_sensor/wifi_densepose_aa/someone_sleeping/state",
+        "ON",
+    ) is None
+    # Wrong final segment
+    assert listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aa/someone_sleeping/STATE",
+        "ON",
+    ) is None
+    # Empty node_id after the wifi_densepose_ prefix is still routed
+    # (the node_id is "") because we don't enforce a minimum length —
+    # but that's not an injection vector. Confirm behaviour.
+    evt = listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_/someone_sleeping/state",
+        "ON",
+    )
+    assert evt is not None
+    assert evt.node_id == ""
+
+
+def test_primitive_listener_handles_garbage_payload_without_crash() -> None:
+    listener = SemanticPrimitiveListener()
+    # Bytes that aren't valid UTF-8
+    evt = listener.handle_mqtt_message(
+        "homeassistant/binary_sensor/wifi_densepose_aa/room_active/state",
+        b"\xff\xfe\xfd",
+    )
+    assert evt is not None  # we return a sentinel rather than crash
+    # No assertions on state content — undefined for invalid UTF-8;
+    # what matters is no exception escaped.
+
+
+# ─── Public surface integrity ───────────────────────────────────────
+
+
+def test_public_surface_is_stable() -> None:
+    """Every name in `wifi_densepose.__all__` must be resolvable.
+    Catches accidental re-export breakage between phases."""
+    import wifi_densepose
+    for name in wifi_densepose.__all__:
+        assert hasattr(wifi_densepose, name), f"__all__ promises {name!r} but attribute missing"
+
+
+def test_client_public_surface_is_stable() -> None:
+    import wifi_densepose.client as c
+    for name in c.__all__:
+        # Lazy re-exports for SensingClient + RuViewMqttClient need to
+        # be resolvable too — touch them to exercise __getattr__.
+        _ = getattr(c, name)
+
+
+# ─── Handler crash isolation (expanded) ─────────────────────────────
+
+
+def test_mqtt_handler_exception_isolation_with_multiple_handlers() -> None:
+    """Earlier test covered one crashing handler; this version makes
+    sure a crashing handler in the *middle* of a list of registered
+    handlers doesn't prevent later handlers from firing."""
+    c = RuViewMqttClient()
+    received_before: list[str] = []
+    received_after: list[str] = []
+    c.on_message("a/+", lambda t, p: received_before.append(t))
+    c.on_message("a/b", lambda t, p: (_ for _ in ()).throw(RuntimeError("middle crash")))
+    c.on_message("+/b", lambda t, p: received_after.append(t))
+
+    msg = SimpleNamespace(topic="a/b", payload=b"x")
+    c._on_message(None, None, msg)
+
+    assert received_before == ["a/b"]
+    assert received_after == ["a/b"]

python/tests/test_smoke.py

@@ -0,0 +1,81 @@
+"""ADR-117 P1 smoke tests — assert the maturin-built wheel loads and
+its compiled module is callable.
+
+These tests are the first acceptance gate of the v2.0 PyPI publish
+pipeline (ADR-117 §11.1 — ``cargo test`` equivalent at the Python
+level). They run on every cibuildwheel target in P5's CI matrix.
+"""
+
+from __future__ import annotations
+
+
+def test_package_imports() -> None:
+    """The top-level package must import without error."""
+    import wifi_densepose  # noqa: F401
+
+
+def test_version_string_well_formed() -> None:
+    """Version string follows PEP 440 + matches pyproject.toml."""
+    import re
+
+    import wifi_densepose
+
+    assert isinstance(wifi_densepose.__version__, str)
+    # Allow pre-release segments (a, b, rc, dev) for non-final wheels.
+    assert re.match(
+        r"^\d+\.\d+\.\d+(a|b|rc|\.dev)?\d*$", wifi_densepose.__version__
+    ), f"non-PEP-440 version: {wifi_densepose.__version__}"
+
+
+def test_rust_version_surfaced() -> None:
+    """Bound Rust core version must be reachable from Python.
+
+    This is the diagnostic surface ADR-117 §5.2 promised — users in
+    bug reports can paste ``wifi_densepose.__rust_version__`` so we
+    correlate behaviour with the exact ``v2/crates/`` HEAD.
+    """
+    import wifi_densepose
+
+    assert isinstance(wifi_densepose.__rust_version__, str)
+    assert wifi_densepose.__rust_version__  # non-empty
+
+
+def test_build_features_listed() -> None:
+    """The wheel's build-time features must be enumerable.
+
+    P1 ships only the ``p1-scaffold`` feature marker; later phases
+    add more entries. The test asserts the contract that the list
+    exists and contains the P1 marker.
+    """
+    import wifi_densepose
+
+    feats = wifi_densepose.__build_features__
+    assert isinstance(feats, list)
+    assert all(isinstance(f, str) for f in feats)
+    assert "p1-scaffold" in feats, f"P1 marker missing: {feats}"
+
+
+def test_hello_returns_ok() -> None:
+    """The compiled ``hello`` function round-trips through PyO3.
+
+    This is the actual smoke test — proves the FFI works end-to-end.
+    If this passes on every cibuildwheel target, the PyO3 build matrix
+    is healthy.
+    """
+    import wifi_densepose
+
+    assert wifi_densepose.hello() == "ok"
+
+
+def test_native_module_private() -> None:
+    """The compiled module is reachable but marked private.
+
+    Users should ``import wifi_densepose``, not ``import
+    wifi_densepose._native``. The underscore prefix communicates that.
+    """
+    import wifi_densepose
+    from wifi_densepose import _native
+
+    assert hasattr(_native, "hello"), "compiled module missing hello()"
+    # Both paths must return the same value.
+    assert wifi_densepose.hello() == _native.hello()

python/tests/test_vitals.py

@@ -0,0 +1,196 @@
+"""ADR-117 P3 — Tests for vital-sign extraction bindings.
+
+Covers:
+
+- VitalStatus enum (eq, eq_int, hash, frozen)
+- VitalEstimate construction + getters + immutability
+- VitalReading composite + getters
+- BreathingExtractor + HeartRateExtractor — esp32_default, explicit
+  ctor, extract() return type, validation behaviour
+
+The Rust pipeline is unit-tested in `v2/crates/wifi-densepose-vitals/`.
+These tests are deliberately scoped to the *binding* layer — does the
+Python surface return the right shapes, raise the right errors, and
+release the GIL safely.
+"""
+
+from __future__ import annotations
+
+import math
+from random import Random
+
+import pytest
+
+import wifi_densepose
+from wifi_densepose import (
+    BreathingExtractor,
+    HeartRateExtractor,
+    VitalEstimate,
+    VitalReading,
+    VitalStatus,
+)
+
+
+# ─── VitalStatus enum ────────────────────────────────────────────────
+
+
+def test_vital_status_variants_present() -> None:
+    assert VitalStatus.Valid != VitalStatus.Degraded
+    assert VitalStatus.Unreliable != VitalStatus.Unavailable
+
+
+def test_vital_status_equality_against_int() -> None:
+    # eq_int → enum can be compared to int (PyO3 0.22 surface)
+    assert VitalStatus.Valid == 0
+    assert VitalStatus.Unavailable == 3
+
+
+def test_vital_status_is_hashable() -> None:
+    # frozen + hash → can be used as dict key / set member
+    s = {VitalStatus.Valid, VitalStatus.Valid, VitalStatus.Degraded}
+    assert len(s) == 2
+
+
+def test_vital_status_repr_contains_variant_name() -> None:
+    r = repr(VitalStatus.Valid)
+    assert "VitalStatus" in r and "Valid" in r
+
+
+# ─── VitalEstimate ───────────────────────────────────────────────────
+
+
+def test_vital_estimate_construction_and_getters() -> None:
+    est = VitalEstimate(value_bpm=72.4, confidence=0.85, status=VitalStatus.Valid)
+    assert math.isclose(est.value_bpm, 72.4)
+    assert math.isclose(est.confidence, 0.85)
+    assert est.status == VitalStatus.Valid
+
+
+def test_vital_estimate_is_frozen() -> None:
+    est = VitalEstimate(value_bpm=72.0, confidence=0.9, status=VitalStatus.Valid)
+    with pytest.raises(AttributeError):
+        est.value_bpm = 100.0  # type: ignore[misc]
+
+
+def test_vital_estimate_repr_is_readable() -> None:
+    est = VitalEstimate(value_bpm=72.0, confidence=0.9, status=VitalStatus.Valid)
+    r = repr(est)
+    assert "VitalEstimate" in r
+    assert "72" in r
+
+
+# ─── VitalReading ────────────────────────────────────────────────────
+
+
+def test_vital_reading_construction_and_getters() -> None:
+    br = VitalEstimate(value_bpm=14.0, confidence=0.9, status=VitalStatus.Valid)
+    hr = VitalEstimate(value_bpm=72.0, confidence=0.8, status=VitalStatus.Degraded)
+    reading = VitalReading(
+        respiratory_rate=br,
+        heart_rate=hr,
+        subcarrier_count=56,
+        signal_quality=0.77,
+        timestamp_secs=1700000000.5,
+    )
+    assert reading.respiratory_rate.value_bpm == 14.0
+    assert reading.heart_rate.status == VitalStatus.Degraded
+    assert reading.subcarrier_count == 56
+    assert math.isclose(reading.signal_quality, 0.77)
+    assert math.isclose(reading.timestamp_secs, 1700000000.5)
+
+
+# ─── BreathingExtractor ──────────────────────────────────────────────
+
+
+def test_breathing_esp32_default_constructs() -> None:
+    br = BreathingExtractor.esp32_default()
+    assert br is not None
+    assert "BreathingExtractor" in repr(br)
+
+
+def test_breathing_explicit_ctor() -> None:
+    br = BreathingExtractor(n_subcarriers=64, sample_rate=200.0, window_secs=20.0)
+    assert br is not None
+
+
+def test_breathing_extract_returns_none_with_too_few_samples() -> None:
+    """One frame can't produce a 30-second window — must return None.
+
+    Verifies the binding propagates Rust's `Option<VitalEstimate>` →
+    Python None correctly (vs raising or returning a default).
+    """
+    br = BreathingExtractor.esp32_default()
+    out = br.extract(residuals=[0.0] * 56, weights=[])
+    assert out is None
+
+
+def test_breathing_extract_accepts_empty_weights() -> None:
+    """Empty weights vector means "equal weight per subcarrier" by
+    convention (per breathing.rs)."""
+    br = BreathingExtractor.esp32_default()
+    out = br.extract(residuals=[0.01] * 56, weights=[])
+    # Even with synthetic input it may return None until enough history
+    # accumulates — what matters is that the call doesn't panic.
+    assert out is None or isinstance(out, VitalEstimate)
+
+
+def test_breathing_extract_with_synthetic_signal() -> None:
+    """Drive the extractor with a synthetic 0.25 Hz sine (15 BPM) for
+    enough samples to fill the 30-second window. Don't assert the exact
+    BPM — just that the extractor *eventually* produces a result (rather
+    than returning None forever)."""
+    br = BreathingExtractor.esp32_default()
+    sample_rate = 100.0
+    target_freq = 0.25  # 15 BPM
+    # Run 40 seconds of synthetic data — comfortably past the 30s window.
+    n_samples = int(40 * sample_rate)
+    weights = [1.0] * 56
+
+    produced_estimate = False
+    rng = Random(42)
+    for i in range(n_samples):
+        t = i / sample_rate
+        base = math.sin(2.0 * math.pi * target_freq * t)
+        # Per-subcarrier residual: same signal + small per-carrier noise
+        residuals = [base + rng.gauss(0.0, 0.01) for _ in range(56)]
+        est = br.extract(residuals=residuals, weights=weights)
+        if est is not None:
+            produced_estimate = True
+            assert isinstance(est.value_bpm, float)
+            assert 0.0 <= est.confidence <= 1.0
+            assert est.status in (
+                VitalStatus.Valid,
+                VitalStatus.Degraded,
+                VitalStatus.Unreliable,
+                VitalStatus.Unavailable,
+            )
+            break
+
+    assert produced_estimate, "BreathingExtractor never produced an estimate after 40s of synthetic data"
+
+
+# ─── HeartRateExtractor ──────────────────────────────────────────────
+
+
+def test_heart_rate_esp32_default_constructs() -> None:
+    hr = HeartRateExtractor.esp32_default()
+    assert hr is not None
+    assert "HeartRateExtractor" in repr(hr)
+
+
+def test_heart_rate_explicit_ctor() -> None:
+    hr = HeartRateExtractor(n_subcarriers=64, sample_rate=200.0, window_secs=10.0)
+    assert hr is not None
+
+
+def test_heart_rate_extract_returns_none_with_too_few_samples() -> None:
+    hr = HeartRateExtractor.esp32_default()
+    out = hr.extract(residuals=[0.0] * 56, weights=[])
+    assert out is None
+
+
+# ─── Build feature flag ──────────────────────────────────────────────
+
+
+def test_p3_vitals_in_build_features() -> None:
+    assert "p3-vitals-bindings" in wifi_densepose.__build_features__

python/tombstone/.gitignore

@@ -0,0 +1,3 @@
+dist/
+build/
+*.egg-info/

python/tombstone/README.md

@@ -0,0 +1,38 @@
+# wifi-densepose 1.99.0 — tombstone release
+
+This sub-directory builds the **tombstone wheel** described in
+[ADR-117 §7.2](../../docs/adr/ADR-117-pip-wifi-densepose-modernization.md).
+
+`wifi-densepose==1.1.0` was published on 2025-06-07 as a pure-Python
+FastAPI + PyTorch server. v2.0+ is a hard rewrite around the Rust
+crates in [`v2/crates/`](../../v2/crates/) exposed via PyO3.
+
+`wifi-densepose==1.99.0` ships **no real code** — its `__init__.py`
+raises `ImportError` with a migration URL. The point is that any
+project pinned to `wifi-densepose>=1,<2` that runs `pip install -U
+wifi-densepose` gets a clear, actionable error instead of a silent
+import of a broken legacy server.
+
+## Build locally
+
+```bash
+cd python/tombstone
+python -m build
+```
+
+Result: `dist/wifi_densepose-1.99.0-py3-none-any.whl` and the matching sdist.
+
+## Smoke-test
+
+```bash
+pip install dist/wifi_densepose-1.99.0-py3-none-any.whl
+python -c "import wifi_densepose"
+# Expected: ImportError with the migration URL.
+```
+
+## Publish
+
+Publishing is done by the `pip-release.yml` GH Actions workflow, gated
+on a `v1.99.0-pip` tag OR an explicit `workflow_dispatch` with
+`target: v1-99-tombstone`. Per ADR-117 §7.3 this should publish
+*before* `v2.0.0` to claim the "current" slot in pip's resolver.

python/tombstone/pyproject.toml

@@ -0,0 +1,53 @@
+# ADR-117 §7.2 / §7.4 — v1.99.0 tombstone release.
+#
+# This sub-directory builds a SEPARATE PyPI artifact from the v2.0+
+# PyO3 wheel in ../. The two share the PyPI project name
+# `wifi-densepose` but represent different versions:
+#
+#   1.0.0–1.1.0   legacy pure-Python server (archive/v1/)
+#   1.99.0        THIS PACKAGE — pure-Python wheel whose only behaviour
+#                 is to raise ImportError with the migration URL on
+#                 first import. Acts as a soft-fence for users pinned
+#                 to wifi-densepose>=1,<2.
+#   2.0.0+        PyO3 + maturin Rust core (../pyproject.toml)
+#
+# Build:
+#   cd python/tombstone
+#   python -m build
+#
+# Result: a SINGLE `py3-none-any` wheel plus an sdist. Nothing
+# compiled, no platform-specific tags.
+
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "wifi-densepose"
+version = "1.99.0"
+description = "Tombstone release. wifi-densepose v1.x is superseded by v2.0+ (PyO3 bindings to the Rust core). Install wifi-densepose==2.0.0 — see https://github.com/ruvnet/RuView/blob/main/docs/pip-migration.md"
+readme = "README.md"
+requires-python = ">=3.8"
+license = { text = "MIT" }
+authors = [
+    { name = "rUv", email = "ruv@ruv.net" },
+]
+keywords = ["wifi", "csi", "pose-estimation", "deprecated", "migration"]
+classifiers = [
+    "Development Status :: 7 - Inactive",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+]
+# No runtime dependencies — the import raises before any code runs.
+dependencies = []
+
+[project.urls]
+Homepage = "https://github.com/ruvnet/RuView"
+"Migration guide" = "https://github.com/ruvnet/RuView/blob/main/docs/pip-migration.md"
+"ADR-117 (modernization plan)" = "https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-117-pip-wifi-densepose-modernization.md"
+
+[tool.setuptools]
+packages = ["wifi_densepose"]
+package-dir = { "" = "src" }

python/tombstone/src/wifi_densepose/__init__.py

@@ -0,0 +1,18 @@
+# ADR-117 §7.2 — v1.99.0 tombstone.
+#
+# This module is part of the `wifi-densepose==1.99.0` PyPI release.
+# Its ONLY job is to raise ImportError on import so any project that
+# upgraded from the legacy 1.x line gets a clear migration error
+# rather than a silent broken import.
+#
+# The real package lives at `wifi-densepose>=2.0.0` (built by the
+# PyO3+maturin pipeline in `python/`).
+raise ImportError(
+    "wifi-densepose 1.x has been superseded by v2.0.0 which wraps the Rust-based stack.\n"
+    "\n"
+    "  pip install wifi-densepose==2.0.0\n"
+    "\n"
+    "Migration guide: https://github.com/ruvnet/RuView/blob/main/docs/pip-migration.md\n"
+    "Modernization rationale: https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-117-pip-wifi-densepose-modernization.md\n"
+    "Legacy v1 source (archived): https://github.com/ruvnet/RuView/tree/main/archive/v1\n"
+)

python/tombstone/tests/test_tombstone.py

@@ -0,0 +1,50 @@
+"""ADR-117 §7.2 — Unit test for the v1.99.0 tombstone wheel.
+
+Verifies the *file content* of the tombstone module without actually
+importing it (importing it would raise ImportError, which is the
+behaviour under test). The CI workflow `pip-release.yml` runs the
+real end-to-end install + import test inside an ephemeral venv.
+"""
+
+from __future__ import annotations
+
+import pathlib
+
+
+TOMBSTONE = pathlib.Path(__file__).parent.parent / "src" / "wifi_densepose" / "__init__.py"
+
+
+def test_tombstone_file_exists() -> None:
+    assert TOMBSTONE.is_file(), f"tombstone module missing: {TOMBSTONE}"
+
+
+def test_tombstone_raises_import_error() -> None:
+    """The source must call `raise ImportError(...)`. We grep rather
+    than exec because actually running it would terminate the test."""
+    src = TOMBSTONE.read_text(encoding="utf-8")
+    assert "raise ImportError(" in src, "tombstone does not raise ImportError"
+
+
+def test_tombstone_contains_v2_install_hint() -> None:
+    src = TOMBSTONE.read_text(encoding="utf-8")
+    assert "pip install wifi-densepose==2.0.0" in src, (
+        "tombstone ImportError message must include the v2 pip install hint"
+    )
+
+
+def test_tombstone_contains_migration_url() -> None:
+    src = TOMBSTONE.read_text(encoding="utf-8")
+    assert "docs/pip-migration.md" in src, (
+        "tombstone must point users at the migration guide"
+    )
+
+
+def test_tombstone_is_minimal() -> None:
+    """The whole point of the tombstone is that it's MINIMAL — no
+    imports, no helper functions, no class definitions. Lock that
+    down so a well-intentioned refactor doesn't accidentally bloat it
+    into a real module that loads partway before failing."""
+    src = TOMBSTONE.read_text(encoding="utf-8")
+    forbidden = ("def ", "class ", "import wifi_densepose", "import os", "import sys")
+    for f in forbidden:
+        assert f not in src, f"tombstone must not contain {f!r} — it should ONLY raise"

python/wifi_densepose/__init__.py

@@ -0,0 +1,105 @@
+"""WiFi-DensePose — passive human sensing from WiFi CSI.
+
+ADR-117 — v2.0 is a PyO3-bound replacement for the legacy pure-Python
+``wifi-densepose==1.1.0`` (released 2025-06-07). The compiled core is
+the same Rust workspace published in `v2/crates/` of the
+`ruvnet/RuView <https://github.com/ruvnet/RuView>`_ repository.
+
+Quick start::
+
+    import wifi_densepose
+    print(wifi_densepose.__version__)
+    print(wifi_densepose.__rust_version__)
+    print(wifi_densepose.hello())   # → "ok"
+
+P1 (this release): scaffold. Core types land in P2; vital signs +
+signal DSP in P3; WebSocket/MQTT client in P4. See the
+`ADR-117 modernization plan
+<https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-117-pip-wifi-densepose-modernization.md>`_
+for the full phase ledger.
+
+Migrating from v1.x: the v1 line was pure-Python and had a different
+API surface. v2 is a hard break (semver-justified). See the
+``v1.99.0`` tombstone wheel for the migration URL.
+"""
+
+from __future__ import annotations
+
+# Public Python version follows the wheel version, NOT the Rust core
+# version. The Rust core version is surfaced separately as
+# `__rust_version__` for diagnostics.
+__version__ = "2.0.0a1"
+
+# Re-export the compiled module's surface. The leading underscore on
+# `_native` is intentional — it marks the binding module as internal.
+# Users always import from `wifi_densepose` directly.
+from wifi_densepose import _native
+
+# ─── P2 — Core type re-exports ───────────────────────────────────────
+# Bound types land in `wifi_densepose._native` and are re-exported here
+# under their stable public names. Users always `from wifi_densepose
+# import Keypoint, KeypointType` — never reach into `_native`.
+Keypoint = _native.Keypoint
+KeypointType = _native.KeypointType
+BoundingBox = _native.BoundingBox
+PersonPose = _native.PersonPose
+PoseEstimate = _native.PoseEstimate
+
+# ─── P3 — Vital sign extraction ──────────────────────────────────────
+VitalStatus = _native.VitalStatus
+VitalEstimate = _native.VitalEstimate
+VitalReading = _native.VitalReading
+BreathingExtractor = _native.BreathingExtractor
+HeartRateExtractor = _native.HeartRateExtractor
+
+# ─── P3.5 — BFLD (Beamforming Feedback Loop Data) ─────────────────────
+BfldKind = _native.BfldKind
+BfldFrame = _native.BfldFrame
+BfldReport = _native.BfldReport
+
+
+__rust_version__: str = _native.__rust_version__
+"""Version of the bound Rust core. Useful for bug reports."""
+
+__rust_build_tag__: str = _native.__rust_build_tag__
+"""Build tag of the Rust core (P5 will swap this for the git SHA)."""
+
+__build_features__: list[str] = list(_native.__build_features__)
+"""Feature flags the wheel was compiled with."""
+
+
+def hello() -> str:
+    """Smoke test — confirms the compiled module loads and is callable.
+
+    Returns:
+        Always ``"ok"`` if the wheel built and loaded correctly.
+
+    Used by ``python/tests/test_smoke.py`` to assert the PyO3 round-trip
+    works end-to-end on every cibuildwheel target.
+    """
+    return _native.hello()
+
+
+__all__ = [
+    "__version__",
+    "__rust_version__",
+    "__rust_build_tag__",
+    "__build_features__",
+    "hello",
+    # P2 — core types
+    "Keypoint",
+    "KeypointType",
+    "BoundingBox",
+    "PersonPose",
+    "PoseEstimate",
+    # P3 — vital sign extraction
+    "VitalStatus",
+    "VitalEstimate",
+    "VitalReading",
+    "BreathingExtractor",
+    "HeartRateExtractor",
+    # P3.5 — BFLD (forward-compat surface for the future Rust crate)
+    "BfldKind",
+    "BfldFrame",
+    "BfldReport",
+]

python/wifi_densepose/client/__init__.py

@@ -0,0 +1,93 @@
+"""ADR-117 P4 — Pure-Python client layer.
+
+This sub-package is the **client-facing** half of `wifi-densepose`:
+end users who only want to *consume* live RuView telemetry (rather than
+running DSP locally) get a tight, opt-in client extra:
+
+```
+pip install "wifi-densepose[client]"
+```
+
+The runtime install footprint stays small for users who only need the
+compiled PyO3 surface: `websockets` and `paho-mqtt` are declared as the
+`[client]` extra in `pyproject.toml` and are NOT pulled in by the
+default install.
+
+## Modules
+
+- `ws` — `SensingClient`: asyncio WebSocket client for the
+  sensing-server `/ws/sensing` endpoint (ADR-115 §1)
+- `mqtt` — `RuViewMqttClient`: paho-mqtt v2 wrapper for
+  `ruview/<node>/raw/+` + `homeassistant/+/wifi_densepose_<node>/+/+`
+  topics (ADR-115 §3)
+- `primitives` — `SemanticPrimitiveListener`: typed view over the
+  10 HA-MIND semantic primitives (ADR-115 §3.12)
+- `ha` — `HABlueprintHelper`: parses MQTT-discovery payloads, helps
+  users introspect what entities a node is publishing
+
+No PyO3 here — this module is pure Python so it loads without the
+compiled extension (useful for users who only want the client surface
+and not the DSP pipeline).
+"""
+
+from __future__ import annotations
+
+# Re-export the user-facing types. Import errors are deferred to the
+# moment the user actually instantiates one of these classes — that way
+# `from wifi_densepose.client import HABlueprintHelper` still works
+# even if the user hasn't installed `[client]` extras yet (HABlueprint
+# is pure stdlib).
+from wifi_densepose.client.ha import (
+    HaDiscoveryPayload,
+    HaEntity,
+    HABlueprintHelper,
+)
+from wifi_densepose.client.primitives import (
+    SemanticPrimitive,
+    SemanticPrimitiveEvent,
+    SemanticPrimitiveListener,
+)
+
+
+__all__ = [
+    # ws — re-exported lazily; see module docstring
+    "SensingClient",
+    "SensingMessage",
+    "EdgeVitalsMessage",
+    "PoseDataMessage",
+    "ConnectionEstablishedMessage",
+    # mqtt — re-exported lazily; see module docstring
+    "RuViewMqttClient",
+    # ha — pure stdlib
+    "HaDiscoveryPayload",
+    "HaEntity",
+    "HABlueprintHelper",
+    # primitives — pure stdlib
+    "SemanticPrimitive",
+    "SemanticPrimitiveEvent",
+    "SemanticPrimitiveListener",
+]
+
+
+def __getattr__(name: str):
+    """Lazy re-exports for the modules that pull in optional extras.
+
+    `SensingClient` needs `websockets`; `RuViewMqttClient` needs
+    `paho-mqtt`. Importing those at package init would make
+    `wifi_densepose.client` unusable without the extras installed
+    — defeating the point of an *optional* extra. We defer the import
+    until the attribute is actually looked up.
+    """
+    if name in {
+        "SensingClient",
+        "SensingMessage",
+        "EdgeVitalsMessage",
+        "PoseDataMessage",
+        "ConnectionEstablishedMessage",
+    }:
+        from wifi_densepose.client import ws as _ws
+        return getattr(_ws, name)
+    if name == "RuViewMqttClient":
+        from wifi_densepose.client.mqtt import RuViewMqttClient as _R
+        return _R
+    raise AttributeError(f"module 'wifi_densepose.client' has no attribute {name!r}")

python/wifi_densepose/client/ha.py

@@ -0,0 +1,194 @@
+"""ADR-117 P4 — Home Assistant MQTT-discovery payload helpers.
+
+Parses the `homeassistant/<entity_kind>/wifi_densepose_<node>/<id>/config`
+discovery payloads described in ADR-115 §3 into typed Python objects so
+client code can introspect what a node is publishing without
+hand-parsing JSON.
+
+This is **read-only**: we do NOT generate discovery payloads from
+Python (that's the sensing-server's job). The helper exists so a
+client (HA blueprint author, debugger, dashboard) can ask "what
+entities does this node expose?" and get a structured answer.
+
+Example:
+
+```python
+from wifi_densepose.client import HaDiscoveryPayload, HABlueprintHelper
+
+helper = HABlueprintHelper()
+helper.add_payload(topic, json_bytes)
+for entity in helper.entities_for_node("aabbccddeeff"):
+    print(entity.entity_kind, entity.object_id, entity.unique_id)
+```
+"""
+
+from __future__ import annotations
+
+import json
+import re
+from dataclasses import dataclass, field
+from typing import Any, Iterable
+
+
+# ─── Topic schema ────────────────────────────────────────────────────
+
+
+# Matches discovery topics like:
+#   homeassistant/binary_sensor/wifi_densepose_aabbccddeeff/presence/config
+#   homeassistant/sensor/wifi_densepose_aabbccddeeff/heart_rate/config
+#   homeassistant/event/wifi_densepose_aabbccddeeff/fall/config
+_DISCOVERY_TOPIC_RE = re.compile(
+    r"^homeassistant/"
+    r"(?P<entity_kind>[A-Za-z_]+)/"
+    r"wifi_densepose_(?P<node_id>[A-Za-z0-9]+)/"
+    r"(?P<object_id>[A-Za-z0-9_\-]+)/"
+    r"config$"
+)
+
+
+@dataclass(frozen=True)
+class HaDiscoveryPayload:
+    """One MQTT discovery payload (config topic + JSON body)."""
+    entity_kind: str  # "binary_sensor", "sensor", "event", "switch", ...
+    node_id: str      # the node's MAC-ish identifier
+    object_id: str    # entity slug (e.g. "presence", "heart_rate")
+    payload: dict[str, Any]
+
+    @property
+    def topic(self) -> str:
+        return (
+            f"homeassistant/{self.entity_kind}/"
+            f"wifi_densepose_{self.node_id}/{self.object_id}/config"
+        )
+
+
+@dataclass(frozen=True)
+class HaEntity:
+    """A user-facing view of one HA entity registered by a node."""
+    entity_kind: str
+    node_id: str
+    object_id: str
+    unique_id: str = ""
+    name: str = ""
+    state_topic: str = ""
+    device_class: str = ""
+    unit_of_measurement: str = ""
+    icon: str = ""
+    json_attributes_topic: str = ""
+
+    @classmethod
+    def from_payload(cls, p: HaDiscoveryPayload) -> "HaEntity":
+        body = p.payload
+        return cls(
+            entity_kind=p.entity_kind,
+            node_id=p.node_id,
+            object_id=p.object_id,
+            unique_id=str(body.get("unique_id", "")),
+            name=str(body.get("name", "")),
+            state_topic=str(body.get("state_topic", "")),
+            device_class=str(body.get("device_class", "")),
+            unit_of_measurement=str(body.get("unit_of_measurement", "")),
+            icon=str(body.get("icon", "")),
+            json_attributes_topic=str(body.get("json_attributes_topic", "")),
+        )
+
+
+def parse_discovery_topic(topic: str) -> tuple[str, str, str] | None:
+    """Parse a discovery config topic into (entity_kind, node_id,
+    object_id). Returns None for non-discovery topics."""
+    m = _DISCOVERY_TOPIC_RE.match(topic)
+    if not m:
+        return None
+    return (m.group("entity_kind"), m.group("node_id"), m.group("object_id"))
+
+
+def parse_discovery_payload(
+    topic: str, payload: bytes | str | dict[str, Any]
+) -> HaDiscoveryPayload | None:
+    """Decode an HA discovery payload. Returns None for non-discovery
+    topics OR malformed JSON; raises only on programmer error."""
+    parsed = parse_discovery_topic(topic)
+    if parsed is None:
+        return None
+    entity_kind, node_id, object_id = parsed
+    body: dict[str, Any]
+    if isinstance(payload, dict):
+        body = payload
+    else:
+        if isinstance(payload, bytes):
+            try:
+                payload = payload.decode("utf-8")
+            except UnicodeDecodeError:
+                return None
+        try:
+            decoded = json.loads(payload)
+        except json.JSONDecodeError:
+            return None
+        if not isinstance(decoded, dict):
+            return None
+        body = decoded
+    return HaDiscoveryPayload(
+        entity_kind=entity_kind,
+        node_id=node_id,
+        object_id=object_id,
+        payload=body,
+    )
+
+
+# ─── Helper / aggregator ─────────────────────────────────────────────
+
+
+class HABlueprintHelper:
+    """Aggregates HA discovery payloads observed on the bus and offers
+    structured queries against them.
+
+    Intended use: subscribe a RuViewMqttClient to
+    `homeassistant/+/wifi_densepose_+/+/config`, feed every message
+    into `add_payload()`, then ask the helper "what entities does
+    node X expose?" or "what binary_sensors are presence-class?".
+    """
+
+    def __init__(self) -> None:
+        # (node_id, entity_kind, object_id) → HaDiscoveryPayload
+        self._payloads: dict[tuple[str, str, str], HaDiscoveryPayload] = {}
+
+    def add_payload(self, topic: str, payload: bytes | str | dict[str, Any]) -> bool:
+        """Returns True if the payload was a valid HA discovery
+        message and was stored; False otherwise."""
+        parsed = parse_discovery_payload(topic, payload)
+        if parsed is None:
+            return False
+        self._payloads[(parsed.node_id, parsed.entity_kind, parsed.object_id)] = parsed
+        return True
+
+    def remove(self, node_id: str, entity_kind: str, object_id: str) -> bool:
+        """Drop a stored payload — useful when handling a discovery
+        retain-flag clear (HA's convention for removing an entity)."""
+        return self._payloads.pop((node_id, entity_kind, object_id), None) is not None
+
+    def __len__(self) -> int:
+        return len(self._payloads)
+
+    def __contains__(self, item: tuple[str, str, str]) -> bool:
+        return item in self._payloads
+
+    def all_payloads(self) -> list[HaDiscoveryPayload]:
+        return list(self._payloads.values())
+
+    def entities_for_node(self, node_id: str) -> list[HaEntity]:
+        return [
+            HaEntity.from_payload(p)
+            for p in self._payloads.values()
+            if p.node_id == node_id
+        ]
+
+    def nodes(self) -> list[str]:
+        return sorted({p.node_id for p in self._payloads.values()})
+
+    def by_device_class(self, device_class: str) -> list[HaEntity]:
+        out: list[HaEntity] = []
+        for p in self._payloads.values():
+            e = HaEntity.from_payload(p)
+            if e.device_class == device_class:
+                out.append(e)
+        return out

python/wifi_densepose/client/mqtt.py

@@ -0,0 +1,257 @@
+"""ADR-117 P4 — paho-mqtt v2 wrapper for RuView MQTT topics.
+
+Subscribes to the topic namespaces defined in ADR-115:
+
+- `ruview/<node>/raw/edge_vitals` — opt-in firehose of the WS edge_vitals
+- `ruview/<node>/raw/pose` — opt-in firehose of pose data
+- `ruview/<node>/raw/sensing_update` — opt-in firehose of every sensing update
+- `homeassistant/+/wifi_densepose_<node>/+/config` — HA discovery payloads
+- `homeassistant/+/wifi_densepose_<node>/+/state` — HA state payloads
+
+The client uses **paho-mqtt v2's `Client(CallbackAPIVersion.VERSION2)`**
+API explicitly. v1's deprecated callback signatures will not work.
+
+Example:
+
+```python
+from wifi_densepose.client import RuViewMqttClient
+
+def on_edge_vitals(topic, payload):
+    print(topic, payload["breathing_rate_bpm"])
+
+client = RuViewMqttClient(broker_host="localhost", broker_port=1883)
+client.on_message("ruview/+/raw/edge_vitals", on_edge_vitals)
+client.start()
+# ... runs in a background thread; call client.stop() to disconnect
+```
+
+The constructor never connects; call `.start()` to enter the network
+loop and `.stop()` to disconnect cleanly. Both are idempotent.
+"""
+
+from __future__ import annotations
+
+import json
+import logging
+import threading
+import uuid
+from typing import Any, Callable, Optional
+
+try:
+    import paho.mqtt.client as mqtt  # type: ignore[import-not-found]
+    from paho.mqtt.enums import CallbackAPIVersion  # type: ignore[import-not-found]
+    _PAHO_AVAILABLE = True
+except ImportError:  # pragma: no cover
+    _PAHO_AVAILABLE = False
+
+
+log = logging.getLogger(__name__)
+
+
+MessageHandler = Callable[[str, Any], None]
+"""(topic, decoded_payload) → None. The payload is JSON-decoded if the
+content is valid JSON, otherwise the raw bytes are passed through."""
+
+
+class RuViewMqttClient:
+    """Wrapper around paho-mqtt v2 with per-topic-pattern callbacks.
+
+    Per the rumqttc lesson [[feedback_mqtt_integration_test_patterns]]:
+    - Each instance gets a unique client_id (per-test isolation when
+      tests run in parallel against the same broker).
+    - Subscription wildcards (`+`, `#`) are supported by paho's
+      built-in matcher; we route by exact pattern match against the
+      registered handler.
+    """
+
+    def __init__(
+        self,
+        *,
+        broker_host: str = "localhost",
+        broker_port: int = 1883,
+        client_id: Optional[str] = None,
+        username: Optional[str] = None,
+        password: Optional[str] = None,
+        keepalive: int = 60,
+        tls: bool = False,
+    ) -> None:
+        if not _PAHO_AVAILABLE:
+            raise ImportError(
+                "RuViewMqttClient requires the `paho-mqtt` package. Install with "
+                "`pip install \"wifi-densepose[client]\"` to enable the client extras."
+            )
+        self.broker_host = broker_host
+        self.broker_port = broker_port
+        self.keepalive = keepalive
+        self._client_id = client_id or f"wifi-densepose-client-{uuid.uuid4().hex[:12]}"
+        self._handlers: dict[str, MessageHandler] = {}
+        self._handlers_lock = threading.Lock()
+        self._client = mqtt.Client(
+            callback_api_version=CallbackAPIVersion.VERSION2,
+            client_id=self._client_id,
+            clean_session=True,
+        )
+        if username is not None:
+            self._client.username_pw_set(username, password)
+        if tls:
+            self._client.tls_set()
+        self._client.on_connect = self._on_connect
+        self._client.on_message = self._on_message
+        self._client.on_disconnect = self._on_disconnect
+        self._started = False
+        self._connected_event = threading.Event()
+
+    @property
+    def client_id(self) -> str:
+        return self._client_id
+
+    @property
+    def connected(self) -> bool:
+        return self._connected_event.is_set()
+
+    # ── handler registration ─────────────────────────────────────────
+
+    def on_message(self, topic_pattern: str, handler: MessageHandler) -> None:
+        """Register a handler for a topic pattern. Replaces any
+        previous handler for the same pattern."""
+        with self._handlers_lock:
+            self._handlers[topic_pattern] = handler
+
+    def unsubscribe_handler(self, topic_pattern: str) -> None:
+        with self._handlers_lock:
+            self._handlers.pop(topic_pattern, None)
+        if self._started:
+            self._client.unsubscribe(topic_pattern)
+
+    # ── lifecycle ────────────────────────────────────────────────────
+
+    def start(self) -> None:
+        """Connect to the broker and enter the network loop in a
+        background thread. Idempotent."""
+        if self._started:
+            return
+        self._client.connect(self.broker_host, self.broker_port, self.keepalive)
+        self._client.loop_start()
+        self._started = True
+
+    def wait_connected(self, timeout: float = 5.0) -> bool:
+        """Block until CONNACK has been received. Returns True on
+        connect, False on timeout. Mirrors the rumqttc SubAck pump
+        pattern but for paho's connect step."""
+        return self._connected_event.wait(timeout=timeout)
+
+    def stop(self) -> None:
+        """Disconnect and stop the network loop. Idempotent."""
+        if not self._started:
+            return
+        try:
+            self._client.disconnect()
+        except Exception as e:  # pragma: no cover — best-effort
+            log.debug("ignored mqtt disconnect error: %r", e)
+        try:
+            self._client.loop_stop()
+        except Exception as e:  # pragma: no cover
+            log.debug("ignored mqtt loop_stop error: %r", e)
+        self._started = False
+        self._connected_event.clear()
+
+    def publish(
+        self,
+        topic: str,
+        payload: Any,
+        *,
+        qos: int = 0,
+        retain: bool = False,
+    ) -> None:
+        """Publish a payload. Dicts/lists are JSON-encoded; bytes pass
+        through; strings are encoded UTF-8."""
+        if isinstance(payload, (dict, list)):
+            data: Any = json.dumps(payload, default=str)
+        else:
+            data = payload
+        info = self._client.publish(topic, data, qos=qos, retain=retain)
+        # paho v2 returns MQTTMessageInfo; rc != MQTT_ERR_SUCCESS is a
+        # broker-side error we should propagate so callers don't think
+        # the publish succeeded.
+        if info.rc != mqtt.MQTT_ERR_SUCCESS:
+            raise RuntimeError(f"mqtt publish failed: topic={topic} rc={info.rc}")
+
+    # ── paho callbacks (v2 signatures) ───────────────────────────────
+
+    def _on_connect(self, client: Any, _userdata: Any, _flags: Any, reason_code: Any, _properties: Any = None) -> None:
+        # paho v2 passes ReasonCode; success is 0 ("Success" / Granted_QoS_0)
+        rc = int(reason_code) if hasattr(reason_code, "__int__") else reason_code
+        if rc == 0:
+            self._connected_event.set()
+            # Re-subscribe to all known patterns. Important after a
+            # reconnect — paho doesn't auto-resubscribe with
+            # clean_session=True.
+            with self._handlers_lock:
+                patterns = list(self._handlers.keys())
+            for pattern in patterns:
+                client.subscribe(pattern)
+            log.debug("mqtt CONNACK ok; subscribed to %d pattern(s)", len(patterns))
+        else:
+            log.warning("mqtt CONNACK with non-success rc=%r", reason_code)
+
+    def _on_disconnect(self, _client: Any, _userdata: Any, _flags: Any = None, reason_code: Any = None, _properties: Any = None) -> None:
+        self._connected_event.clear()
+        log.debug("mqtt disconnected rc=%r", reason_code)
+
+    def _on_message(self, _client: Any, _userdata: Any, message: Any) -> None:
+        topic = message.topic
+        # Best-effort JSON decode — fall back to raw bytes if it's not JSON.
+        payload: Any
+        try:
+            payload = json.loads(message.payload.decode("utf-8"))
+        except (UnicodeDecodeError, json.JSONDecodeError):
+            payload = message.payload
+
+        with self._handlers_lock:
+            handlers = list(self._handlers.items())
+
+        for pattern, handler in handlers:
+            if _topic_matches(pattern, topic):
+                try:
+                    handler(topic, payload)
+                except Exception as e:  # never let a user callback crash the loop
+                    log.exception("handler for pattern %r raised: %r", pattern, e)
+
+    # ── re-subscribe on demand ──────────────────────────────────────
+
+    def subscribe_registered(self) -> None:
+        """Explicitly issue SUBSCRIBE for every registered handler.
+        Useful when you registered handlers AFTER calling start().
+        """
+        if not self._started:
+            return
+        with self._handlers_lock:
+            patterns = list(self._handlers.keys())
+        for pattern in patterns:
+            self._client.subscribe(pattern)
+
+
+# ─── Topic-pattern matching ──────────────────────────────────────────
+
+
+def _topic_matches(pattern: str, topic: str) -> bool:
+    """MQTT topic wildcard matcher.
+
+    - `+` matches exactly one topic level
+    - `#` matches one or more remaining levels (must be the final segment)
+    """
+    p_parts = pattern.split("/")
+    t_parts = topic.split("/")
+    i = 0
+    while i < len(p_parts):
+        if p_parts[i] == "#":
+            return i == len(p_parts) - 1 and len(t_parts) >= i
+        if i >= len(t_parts):
+            return False
+        if p_parts[i] == "+":
+            i += 1
+            continue
+        if p_parts[i] != t_parts[i]:
+            return False
+        i += 1
+    return len(p_parts) == len(t_parts)

python/wifi_densepose/client/primitives.py

@@ -0,0 +1,222 @@
+"""ADR-117 P4 — Typed listener for HA-MIND semantic primitives.
+
+ADR-115 §3.12 defines 10 fused inference outputs that the sensing-server
+publishes under the HA-DISCO MQTT namespace. This module gives clients
+a typed handle on them so they can write `if event.kind ==
+SemanticPrimitive.SomeoneSleeping: ...` instead of pattern-matching
+strings.
+
+The 10 v1 primitives (ADR-115 §3.12.1):
+
+| Enum value | Topic suffix | Output kind |
+|---|---|---|
+| `SomeoneSleeping` | `someone_sleeping` | binary_sensor |
+| `PossibleDistress` | `possible_distress` | binary_sensor + event |
+| `RoomActive` | `room_active` | binary_sensor |
+| `ElderlyInactivityAnomaly` | `elderly_inactivity` | binary_sensor + event |
+| `MeetingInProgress` | `meeting_in_progress` | binary_sensor |
+| `BathroomOccupied` | `bathroom_occupied` | binary_sensor |
+| `FallRiskElevated` | `fall_risk_elevated` | sensor (0–100) + event |
+| `BedExit` | `bed_exit` | event |
+| `NoMovementSafety` | `no_movement_safety` | binary_sensor + event |
+| `MultiRoomTransition` | `multi_room_transition` | event |
+"""
+
+from __future__ import annotations
+
+import enum
+import json
+from dataclasses import dataclass, field
+from typing import Any, Callable, Optional
+
+
+# ─── Enum ────────────────────────────────────────────────────────────
+
+
+class SemanticPrimitive(enum.Enum):
+    """One of the 10 HA-MIND fused inference outputs."""
+    SomeoneSleeping = "someone_sleeping"
+    PossibleDistress = "possible_distress"
+    RoomActive = "room_active"
+    ElderlyInactivityAnomaly = "elderly_inactivity"
+    MeetingInProgress = "meeting_in_progress"
+    BathroomOccupied = "bathroom_occupied"
+    FallRiskElevated = "fall_risk_elevated"
+    BedExit = "bed_exit"
+    NoMovementSafety = "no_movement_safety"
+    MultiRoomTransition = "multi_room_transition"
+
+    @classmethod
+    def from_object_id(cls, object_id: str) -> Optional["SemanticPrimitive"]:
+        for v in cls:
+            if v.value == object_id:
+                return v
+        return None
+
+
+# ─── Event payload ───────────────────────────────────────────────────
+
+
+@dataclass(frozen=True)
+class SemanticPrimitiveEvent:
+    """A single fired event for one semantic primitive.
+
+    `state` semantics depend on the primitive kind:
+    - binary_sensor: "ON" / "OFF"
+    - sensor: numeric string (e.g. "73" for fall_risk_elevated 0–100)
+    - event: "fired" or an event-class string like "bed_exit_detected"
+    """
+    kind: SemanticPrimitive
+    node_id: str
+    state: str
+    confidence: float = 0.0
+    explanation: tuple[str, ...] = ()
+    timestamp: float = 0.0
+    raw: dict[str, Any] = field(default_factory=dict, hash=False, compare=False)
+
+
+# ─── Listener ────────────────────────────────────────────────────────
+
+
+Callback = Callable[[SemanticPrimitiveEvent], None]
+
+
+class SemanticPrimitiveListener:
+    """Routes raw MQTT state messages to per-primitive callbacks.
+
+    Designed to plug into RuViewMqttClient:
+
+    ```python
+    from wifi_densepose.client import (
+        RuViewMqttClient, SemanticPrimitive, SemanticPrimitiveListener
+    )
+
+    listener = SemanticPrimitiveListener()
+    listener.on(SemanticPrimitive.SomeoneSleeping, lambda e: print(e))
+
+    client = RuViewMqttClient()
+    client.on_message(
+        "homeassistant/+/wifi_densepose_+/+/state",
+        listener.handle_mqtt_message,
+    )
+    client.start()
+    ```
+
+    The listener itself never touches MQTT — it's a pure router. You
+    feed it `(topic, payload)` pairs and it figures out which primitive
+    the topic refers to and decodes the payload.
+    """
+
+    # Matches state topics for any of the 10 primitives.
+    # homeassistant/<kind>/wifi_densepose_<node>/<primitive_slug>/state
+    _SLUGS = {p.value for p in SemanticPrimitive}
+
+    def __init__(self) -> None:
+        self._handlers: dict[Optional[SemanticPrimitive], list[Callback]] = {}
+
+    def on(self, primitive: SemanticPrimitive, cb: Callback) -> None:
+        """Register a callback for a specific primitive."""
+        self._handlers.setdefault(primitive, []).append(cb)
+
+    def on_any(self, cb: Callback) -> None:
+        """Register a callback that fires for ALL primitives. Useful
+        for logging or dashboards."""
+        self._handlers.setdefault(None, []).append(cb)
+
+    def handle_mqtt_message(self, topic: str, payload: Any) -> Optional[SemanticPrimitiveEvent]:
+        """Decode one MQTT message into a SemanticPrimitiveEvent and
+        fire the matching callbacks. Returns the event (or None if the
+        topic was not a semantic-primitive state topic)."""
+        parts = topic.split("/")
+        # Shape: homeassistant / <kind> / wifi_densepose_<node> / <slug> / state
+        if len(parts) != 5:
+            return None
+        if parts[0] != "homeassistant" or parts[4] != "state":
+            return None
+        node_prefix = parts[2]
+        if not node_prefix.startswith("wifi_densepose_"):
+            return None
+        slug = parts[3]
+        if slug not in self._SLUGS:
+            return None
+
+        primitive = SemanticPrimitive.from_object_id(slug)
+        if primitive is None:  # pragma: no cover — guarded above
+            return None
+
+        node_id = node_prefix[len("wifi_densepose_"):]
+        event = _decode_event(primitive, node_id, payload)
+
+        # Dispatch — primitive-specific first, then "any" handlers.
+        for cb in self._handlers.get(primitive, ()):
+            cb(event)
+        for cb in self._handlers.get(None, ()):
+            cb(event)
+        return event
+
+
+def _decode_event(
+    primitive: SemanticPrimitive,
+    node_id: str,
+    payload: Any,
+) -> SemanticPrimitiveEvent:
+    """Decode a raw state payload into a typed event.
+
+    HA state payloads come in two shapes:
+    1. Plain string ("ON", "OFF", "73") — used by binary_sensor/sensor
+       with no json_attributes_topic.
+    2. JSON object with `state` + `confidence` + `explanation` fields —
+       used by HA-MIND semantic primitives per ADR-115 §3.12.4.
+
+    Both are supported transparently.
+    """
+    if isinstance(payload, bytes):
+        try:
+            payload = payload.decode("utf-8")
+        except UnicodeDecodeError:
+            return SemanticPrimitiveEvent(
+                kind=primitive, node_id=node_id, state="", raw={}
+            )
+
+    if isinstance(payload, dict):
+        body = payload
+    elif isinstance(payload, str):
+        # Try to JSON-decode; if it's not JSON, treat as a plain state string.
+        try:
+            decoded = json.loads(payload)
+        except json.JSONDecodeError:
+            return SemanticPrimitiveEvent(
+                kind=primitive,
+                node_id=node_id,
+                state=payload,
+                raw={"state": payload},
+            )
+        if isinstance(decoded, dict):
+            body = decoded
+        else:
+            return SemanticPrimitiveEvent(
+                kind=primitive,
+                node_id=node_id,
+                state=str(decoded),
+                raw={"state": decoded},
+            )
+    else:
+        return SemanticPrimitiveEvent(
+            kind=primitive, node_id=node_id, state=str(payload), raw={}
+        )
+
+    expl = body.get("explanation") or body.get("reason") or ()
+    if isinstance(expl, str):
+        expl_tuple: tuple[str, ...] = (expl,)
+    else:
+        expl_tuple = tuple(str(x) for x in expl)
+
+    return SemanticPrimitiveEvent(
+        kind=primitive,
+        node_id=node_id,
+        state=str(body.get("state", "")),
+        confidence=float(body.get("confidence", 0.0)),
+        explanation=expl_tuple,
+        timestamp=float(body.get("timestamp", 0.0)),
+        raw=body,
+    )

python/wifi_densepose/client/ws.py

@@ -0,0 +1,256 @@
+"""ADR-117 P4 — Asyncio WebSocket client for the sensing-server.
+
+The Rust sensing-server (`v2/crates/wifi-densepose-sensing-server`)
+broadcasts three structured message types over `ws://<host>:<port>/ws/sensing`:
+
+| `type` field | Source line in main.rs | Payload shape |
+|---|---|---|
+| `connection_established` | 2596 | `{node_id, version, capabilities}` |
+| `pose_data` | 2655 | `{node_id, timestamp, persons: [...], confidence}` |
+| `edge_vitals` | 4548 | `{node_id, presence, fall_detected, motion, breathing_rate_bpm, heartrate_bpm, ...}` |
+
+`SensingClient` is a pure-Python asyncio wrapper around `websockets>=12`
+that connects, decodes JSON, and yields typed dataclasses.
+
+Example:
+
+```python
+import asyncio
+from wifi_densepose.client import SensingClient, EdgeVitalsMessage
+
+async def main():
+    async with SensingClient("ws://localhost:8765/ws/sensing") as client:
+        async for msg in client.stream():
+            if isinstance(msg, EdgeVitalsMessage):
+                print(f"BR={msg.breathing_rate_bpm}, HR={msg.heartrate_bpm}")
+
+asyncio.run(main())
+```
+"""
+
+from __future__ import annotations
+
+import asyncio
+import json
+import logging
+from dataclasses import dataclass, field
+from typing import Any, AsyncIterator, Optional
+
+# Defer import — only fail at construction time, not at module load.
+try:
+    import websockets  # type: ignore[import-not-found]
+    from websockets.exceptions import ConnectionClosed  # type: ignore[import-not-found]
+    _WEBSOCKETS_AVAILABLE = True
+except ImportError:  # pragma: no cover
+    _WEBSOCKETS_AVAILABLE = False
+
+
+log = logging.getLogger(__name__)
+
+
+# ─── Typed messages ──────────────────────────────────────────────────
+
+
+@dataclass(frozen=True)
+class SensingMessage:
+    """Base class for typed sensing-server messages. The original JSON
+    payload is preserved in ``raw`` for forward-compatibility with
+    fields not yet modelled here."""
+    type: str
+    raw: dict[str, Any] = field(default_factory=dict, hash=False, compare=False)
+
+
+@dataclass(frozen=True)
+class ConnectionEstablishedMessage(SensingMessage):
+    """First message after a successful WS handshake. Lets the client
+    discover the node ID and capability flags without making a separate
+    REST call."""
+    node_id: str = ""
+    version: str = ""
+    capabilities: tuple[str, ...] = ()
+
+
+@dataclass(frozen=True)
+class EdgeVitalsMessage(SensingMessage):
+    """Vital-sign telemetry fused from the edge-vitals path
+    (ADR-021/ADR-110). Optional fields may be ``None`` when the
+    upstream channel hasn't produced a measurement yet."""
+    node_id: str = ""
+    presence: bool = False
+    fall_detected: bool = False
+    motion: float = 0.0
+    breathing_rate_bpm: Optional[float] = None
+    heartrate_bpm: Optional[float] = None
+    n_persons: int = 0
+    motion_energy: float = 0.0
+    presence_score: float = 0.0
+    rssi: Optional[float] = None
+
+
+@dataclass(frozen=True)
+class PoseDataMessage(SensingMessage):
+    """17-keypoint pose data broadcast at the sensing-server's frame
+    cadence. Persons are a list of opaque dicts — typed PoseEstimate
+    decoding lives in the P2 bindings; the WS client passes through."""
+    node_id: str = ""
+    timestamp: float = 0.0
+    persons: tuple[dict[str, Any], ...] = ()
+    confidence: float = 0.0
+
+
+# ─── Decoder ─────────────────────────────────────────────────────────
+
+
+def _decode(raw_text: str) -> SensingMessage:
+    """Decode a single WS frame into a typed message.
+
+    Unknown ``type`` values yield a plain ``SensingMessage`` rather
+    than raising — the sensing-server is on a faster release cadence
+    than this client, and unknown types should not break the stream.
+    """
+    obj = json.loads(raw_text)
+    if not isinstance(obj, dict):
+        raise ValueError(f"sensing-server emitted non-dict payload: {type(obj).__name__}")
+    mtype = obj.get("type", "")
+    if mtype == "connection_established":
+        return ConnectionEstablishedMessage(
+            type=mtype,
+            raw=obj,
+            node_id=obj.get("node_id", ""),
+            version=obj.get("version", ""),
+            capabilities=tuple(obj.get("capabilities", ())),
+        )
+    if mtype == "edge_vitals":
+        return EdgeVitalsMessage(
+            type=mtype,
+            raw=obj,
+            node_id=obj.get("node_id", ""),
+            presence=bool(obj.get("presence", False)),
+            fall_detected=bool(obj.get("fall_detected", False)),
+            motion=float(obj.get("motion", 0.0)),
+            breathing_rate_bpm=(
+                float(obj["breathing_rate_bpm"])
+                if obj.get("breathing_rate_bpm") is not None else None
+            ),
+            heartrate_bpm=(
+                float(obj["heartrate_bpm"])
+                if obj.get("heartrate_bpm") is not None else None
+            ),
+            n_persons=int(obj.get("n_persons", 0)),
+            motion_energy=float(obj.get("motion_energy", 0.0)),
+            presence_score=float(obj.get("presence_score", 0.0)),
+            rssi=(float(obj["rssi"]) if obj.get("rssi") is not None else None),
+        )
+    if mtype == "pose_data":
+        persons = obj.get("persons", ())
+        return PoseDataMessage(
+            type=mtype,
+            raw=obj,
+            node_id=obj.get("node_id", ""),
+            timestamp=float(obj.get("timestamp", 0.0)),
+            persons=tuple(persons) if isinstance(persons, list) else (),
+            confidence=float(obj.get("confidence", 0.0)),
+        )
+    return SensingMessage(type=mtype, raw=obj)
+
+
+# ─── Client ──────────────────────────────────────────────────────────
+
+
+class SensingClient:
+    """Asyncio WebSocket client for the RuView sensing-server.
+
+    Usage as async context manager:
+
+    ```python
+    async with SensingClient("ws://localhost:8765/ws/sensing") as c:
+        async for msg in c.stream():
+            ...
+    ```
+
+    The client does NOT auto-reconnect — if you want resilience, wrap
+    the ``async with`` in your own retry loop. Auto-reconnect logic is
+    application-specific (e.g., "retry forever" for a long-running
+    automation vs "fail fast" for a CLI tool that should exit).
+    """
+
+    def __init__(
+        self,
+        url: str,
+        *,
+        ping_interval: float = 20.0,
+        ping_timeout: float = 20.0,
+        max_size: int = 16 * 1024 * 1024,
+    ) -> None:
+        if not _WEBSOCKETS_AVAILABLE:
+            raise ImportError(
+                "SensingClient requires the `websockets` package. Install with "
+                "`pip install \"wifi-densepose[client]\"` to enable the client extras."
+            )
+        self.url = url
+        self._ping_interval = ping_interval
+        self._ping_timeout = ping_timeout
+        self._max_size = max_size
+        self._ws: Any = None  # websockets.WebSocketClientProtocol — typed Any to avoid import cost
+
+    async def __aenter__(self) -> "SensingClient":
+        self._ws = await websockets.connect(
+            self.url,
+            ping_interval=self._ping_interval,
+            ping_timeout=self._ping_timeout,
+            max_size=self._max_size,
+        )
+        return self
+
+    async def __aexit__(self, exc_type: Any, exc: Any, tb: Any) -> None:
+        await self.close()
+
+    async def close(self) -> None:
+        """Idempotent connection close."""
+        if self._ws is not None:
+            try:
+                await self._ws.close()
+            except Exception as e:  # pragma: no cover — best-effort close
+                log.debug("ignored WS close error: %r", e)
+            self._ws = None
+
+    async def stream(self) -> AsyncIterator[SensingMessage]:
+        """Yield typed messages until the server closes the connection
+        or the context is exited.
+
+        Decode failures on individual frames are logged at WARN and
+        swallowed — a malformed frame should not terminate the stream
+        (the next frame may be fine)."""
+        if self._ws is None:
+            raise RuntimeError("SensingClient not connected. Use `async with` first.")
+        try:
+            async for frame in self._ws:
+                if isinstance(frame, bytes):
+                    frame = frame.decode("utf-8", errors="replace")
+                try:
+                    yield _decode(frame)
+                except (ValueError, json.JSONDecodeError) as e:
+                    log.warning("dropping malformed sensing-server frame: %r", e)
+        except ConnectionClosed:
+            # Graceful EOF — exit the iterator normally.
+            return
+
+    async def send_ping(self) -> None:
+        """Send an application-level ping. The sensing-server replies
+        with `{"type": "pong"}` (main.rs:2698)."""
+        if self._ws is None:
+            raise RuntimeError("SensingClient not connected. Use `async with` first.")
+        await self._ws.send(json.dumps({"type": "ping"}))
+
+    async def recv_one(self, *, timeout: Optional[float] = None) -> SensingMessage:
+        """Receive a single decoded message. Convenience for short
+        scripts and tests that don't need an async generator."""
+        if self._ws is None:
+            raise RuntimeError("SensingClient not connected. Use `async with` first.")
+        if timeout is None:
+            frame = await self._ws.recv()
+        else:
+            frame = await asyncio.wait_for(self._ws.recv(), timeout=timeout)
+        if isinstance(frame, bytes):
+            frame = frame.decode("utf-8", errors="replace")
+        return _decode(frame)

scripts/c6-presence-watcher.py

@@ -0,0 +1,402 @@
+#!/usr/bin/env python3
+"""
+c6-presence-watcher.py — ADR-125 iter 2.
+
+Bridges real ESP32-C6 ADR-081 `rv_feature_state` UDP frames to the HAP
+`MotionSensor` characteristic via the toggle file that
+`scripts/hap-test-sensor.py` already pairs against. No mocks, no
+simulation — consumes the exact 60-byte struct emitted by
+`firmware/esp32-csi-node/main/rv_feature_state.[ch]`.
+
+Wire format (RV_FEATURE_STATE_MAGIC = 0xC5110006, 60 bytes total,
+__attribute__((packed))):
+
+    offset  size  field            type
+    0       4     magic            u32   = 0xC5110006
+    4       1     node_id          u8
+    5       1     mode             u8
+    6       2     seq              u16
+    8       8     ts_us            u64
+    16      4     motion_score     f32   0..1, 100 ms window
+    20      4     presence_score   f32   0..1, 1 s window
+    24      4     respiration_bpm  f32
+    28      4     respiration_conf f32
+    32      4     heartbeat_bpm    f32
+    36      4     heartbeat_conf   f32
+    40      4     anomaly_score    f32
+    44      4     env_shift_score  f32
+    48      4     node_coherence   f32
+    52      2     quality_flags    u16
+    54      2     reserved         u16
+    56      4     crc32            u32
+
+`quality_flags & RV_QFLAG_PRESENCE_VALID (1<<0)` gates presence reads.
+`presence_score >= PRESENCE_THRESHOLD` toggles motion ON; below the
+release threshold (with hysteresis) toggles OFF. The toggle file
+is the contract between this watcher and the paired HAP bridge.
+
+Usage:
+    python3 c6-presence-watcher.py [--port 5005] [--toggle /tmp/ruview-motion]
+"""
+from __future__ import annotations
+import argparse
+import json
+import os
+import signal
+import socket
+import struct
+import sys
+import time
+import zlib
+from collections import deque
+
+RV_FEATURE_STATE_MAGIC = 0xC5110006
+RV_QFLAG_PRESENCE_VALID = 1 << 0
+PACKET_SIZE = 60
+
+
+class PrivacyClass:
+    """Mirror of `wifi-densepose-bfld::PrivacyClass` (Rust, ADR-118 §2.1).
+
+    The HAP boundary is governed by ADR-125 §2.1.d + ADR-122 §2.4: only
+    `Anonymous` (2) and `Restricted` (3) frames may cross. `Raw` (0) and
+    `Derived` (1) are HAP-ineligible by structural invariant I1.
+    """
+    RAW = 0
+    DERIVED = 1
+    ANONYMOUS = 2
+    RESTRICTED = 3
+
+    _names = {RAW: "Raw", DERIVED: "Derived", ANONYMOUS: "Anonymous",
+              RESTRICTED: "Restricted"}
+
+    @classmethod
+    def name(cls, value: int) -> str:
+        return cls._names.get(value, f"Unknown({value})")
+
+    @classmethod
+    def from_str(cls, s: str) -> int:
+        m = {"raw": cls.RAW, "derived": cls.DERIVED,
+             "anonymous": cls.ANONYMOUS, "restricted": cls.RESTRICTED}
+        if s.lower() not in m:
+            raise ValueError(f"invalid privacy class {s!r}; "
+                             f"expected one of {list(m.keys())}")
+        return m[s.lower()]
+
+    @classmethod
+    def allows_hap(cls, value: int) -> bool:
+        """ADR-125 §2.1.d gate: only class-2/3 cross the HomeKit boundary."""
+        return value in (cls.ANONYMOUS, cls.RESTRICTED)
+
+
+# Semantic-event naming per ADR-125 §2.1.d. The HAP bridge keeps
+# advertising a generic MotionSensor; this is the operator-facing
+# *label* for the event, written into the watcher log + summary line
+# so the operator never sees "intruder detected" framing.
+SEMANTIC_EVENT_UNKNOWN_PRESENCE = "Unknown Presence"
+
+# Hysteresis — entry / exit thresholds keep the HomeKit characteristic
+# from flapping when presence_score sits near the boundary.
+PRESENCE_ON_THRESHOLD = 0.40
+PRESENCE_OFF_THRESHOLD = 0.20
+# Idle releases motion after this many seconds with no valid presence
+# packets (covers the C6 falling off the air entirely).
+IDLE_RELEASE_S = 5.0
+
+# 60-byte packed layout (`<` = little-endian + no padding)
+# magic|node|mode|seq|ts|motion|presence|resp_bpm|resp_c|hb_bpm|hb_c|anom|env|coh|qflags|reserved|crc
+PACKET_STRUCT = struct.Struct("<IBBHQfffffffffHHI")
+assert PACKET_STRUCT.size == PACKET_SIZE, (
+    f"layout mismatch: struct {PACKET_STRUCT.size}, expected {PACKET_SIZE}"
+)
+
+
+def parse_packet(buf: bytes):
+    """Return parsed dict or None if not a feature_state packet."""
+    if len(buf) != PACKET_SIZE:
+        return None
+    fields = PACKET_STRUCT.unpack(buf)
+    (magic, node_id, mode, seq, ts_us, motion, presence,
+     resp_bpm, resp_conf, hb_bpm, hb_conf,
+     anomaly, env_shift, coherence,
+     qflags, _reserved, crc) = fields
+    if magic != RV_FEATURE_STATE_MAGIC:
+        return None
+    # CRC32 over bytes [0..end-4]. Firmware uses IEEE poly == zlib.crc32.
+    expected = zlib.crc32(buf[:-4]) & 0xFFFFFFFF
+    crc_ok = expected == crc
+    return {
+        "node_id": node_id, "mode": mode, "seq": seq, "ts_us": ts_us,
+        "motion": motion, "presence": presence,
+        "resp_bpm": resp_bpm, "resp_conf": resp_conf,
+        "hb_bpm": hb_bpm, "hb_conf": hb_conf,
+        "anomaly": anomaly, "env_shift": env_shift, "coherence": coherence,
+        "qflags": qflags, "crc_ok": crc_ok,
+        "presence_valid": bool(qflags & RV_QFLAG_PRESENCE_VALID),
+    }
+
+
+def set_motion(toggle_file: str, on: bool, current: bool,
+               semantic: str = SEMANTIC_EVENT_UNKNOWN_PRESENCE) -> bool:
+    """Touch / unlink the toggle file iff state changes. Return new state."""
+    if on == current:
+        return current
+    if on:
+        with open(toggle_file, "w") as fh:
+            fh.write("1\n")
+    else:
+        try:
+            os.unlink(toggle_file)
+        except FileNotFoundError:
+            pass
+    label = semantic if on else f"clear {semantic}"
+    print(f"[{time.strftime('%H:%M:%S')}] {label} (motion -> {on})",
+          flush=True)
+    return on
+
+
+def apply_privacy_gate(pkt: dict, allowed_class: int) -> dict | None:
+    """ADR-118 PrivacyGate equivalent at the HAP boundary.
+
+    The C6 emits sensor-aggregate `feature_state` frames — *not* raw BFI,
+    *not* identity embeddings. We classify the emit at the chosen
+    operator class. Returns the (possibly redacted) event dict, or
+    `None` if the class doesn't allow HAP crossing.
+    """
+    if not PrivacyClass.allows_hap(allowed_class):
+        return None
+    # `Restricted` (3) strips anything that could be a per-occupant
+    # fingerprint — even though feature_state currently carries none.
+    # Future iters extending the wire format will need to respect this.
+    if allowed_class == PrivacyClass.RESTRICTED:
+        return {
+            "presence": pkt["presence"], "motion": pkt["motion"],
+            "presence_valid": pkt["presence_valid"],
+            "node_id": pkt["node_id"], "seq": pkt["seq"],
+            # anomaly_score / env_shift / coherence dropped (could
+            # reveal longitudinal drift signatures over time).
+        }
+    # `Anonymous` (2) — production default. Carries the aggregate
+    # vitals so HomeKit `Unknown Presence` automations can pick up
+    # context, but no identity-derived fields.
+    return {
+        "presence": pkt["presence"], "motion": pkt["motion"],
+        "presence_valid": pkt["presence_valid"],
+        "node_id": pkt["node_id"], "seq": pkt["seq"],
+        "resp_bpm": pkt["resp_bpm"], "hb_bpm": pkt["hb_bpm"],
+        "anomaly": pkt["anomaly"], "env_shift": pkt["env_shift"],
+        "coherence": pkt["coherence"],
+    }
+
+
+def main() -> int:
+    p = argparse.ArgumentParser()
+    p.add_argument("--port", type=int, default=5005)
+    p.add_argument("--toggle", default="/tmp/ruview-motion")
+    p.add_argument("--bind", default="0.0.0.0")
+    p.add_argument("--privacy-class", default="anonymous",
+                   choices=["raw", "derived", "anonymous", "restricted"],
+                   help="ADR-118 PrivacyClass; only anonymous/restricted "
+                        "may cross the HAP boundary (ADR-125 §2.1.d).")
+    p.add_argument("--state-json", default="/tmp/ruview-state.json",
+                   help="JSON state IPC file written for the HAP daemon. "
+                        "Contains motion/occupancy/anomaly_ts.")
+    p.add_argument("--occupancy-window", type=float, default=3.0,
+                   help="Seconds of rolling presence_score average for "
+                        "OccupancyDetected (vs short-window MotionDetected).")
+    p.add_argument("--anomaly-threshold", type=float, default=0.7,
+                   help="anomaly_score crossing this fires the "
+                        "'Unrecognized Activity Pattern' event "
+                        "(Restricted class only; ADR-125 §2.1.d).")
+    args = p.parse_args()
+
+    privacy_class = PrivacyClass.from_str(args.privacy_class)
+    if not PrivacyClass.allows_hap(privacy_class):
+        sys.stderr.write(
+            f"REFUSED: privacy class {PrivacyClass.name(privacy_class)} "
+            f"(value={privacy_class}) is not HAP-eligible. "
+            f"ADR-125 §2.1.d structural invariant I1: only Anonymous (2) "
+            f"and Restricted (3) frames may cross the HomeKit boundary. "
+            f"Use --privacy-class anonymous (default) or restricted.\n"
+        )
+        return 2
+
+    sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
+    sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
+    if hasattr(socket, "SO_REUSEPORT"):
+        sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEPORT, 1)
+    sock.bind((args.bind, args.port))
+    sock.settimeout(1.0)
+
+    print(f"[c6-presence] listening udp {args.bind}:{args.port}", flush=True)
+    print(f"[c6-presence] toggle file: {args.toggle}", flush=True)
+    print(f"[c6-presence] thresholds: on>={PRESENCE_ON_THRESHOLD}, "
+          f"off<={PRESENCE_OFF_THRESHOLD}, idle_release={IDLE_RELEASE_S}s",
+          flush=True)
+    print(f"[c6-presence] privacy class: "
+          f"{PrivacyClass.name(privacy_class)} (HAP-eligible)", flush=True)
+    print(f"[c6-presence] semantic event: {SEMANTIC_EVENT_UNKNOWN_PRESENCE}",
+          flush=True)
+
+    running = True
+    def _stop(*_):
+        nonlocal running
+        running = False
+    signal.signal(signal.SIGTERM, _stop)
+    signal.signal(signal.SIGINT, _stop)
+
+    motion = os.path.exists(args.toggle)
+    occupancy = False
+    last_anomaly_ts = 0.0
+    last_packet_ts = 0.0
+    last_summary = time.time()
+    n_total = n_valid = n_crc_bad = n_anomaly_fires = 0
+    presence_sum = motion_sum = 0.0
+    # Rolling window of (timestamp, presence_score) for occupancy detect
+    occ_window: deque[tuple[float, float]] = deque()
+    OCC_ON_THRESH = 0.30
+    OCC_OFF_THRESH = 0.15
+    state_path = args.state_json
+
+    def write_state(motion: bool, occupancy: bool, anomaly_ts: float) -> None:
+        try:
+            tmp = state_path + ".tmp"
+            with open(tmp, "w") as fh:
+                json.dump({"motion": motion, "occupancy": occupancy,
+                           "anomaly_ts": anomaly_ts, "ts": time.time()}, fh)
+            os.replace(tmp, state_path)
+        except OSError:
+            pass
+
+    # Companion contract for `scripts/ruview-sensing-server.py` (the
+    # @ruvnet/rvagent compatibility layer): write the full BFLD-gated
+    # feature snapshot so the sensing-server can serve EdgeVitalsMessage
+    # and BfldScanResponse without going back to the wire.
+    feature_path = "/tmp/ruview-last-feature.json"
+
+    def write_feature(gated: dict, motion: bool, occupancy: bool,
+                      privacy_cls: int) -> None:
+        try:
+            tmp = feature_path + ".tmp"
+            with open(tmp, "w") as fh:
+                json.dump({
+                    "node_id": str(gated["node_id"]),
+                    "timestamp_ms": int(time.time() * 1000),
+                    "presence": occupancy,           # sustained
+                    "motion": gated["motion"],        # 0..1 float
+                    "presence_score": gated["presence"],
+                    "n_persons": 1 if occupancy else 0,
+                    "confidence": min(1.0, max(0.0, gated["motion"])),
+                    "breathing_rate_bpm": (gated["resp_bpm"]
+                                           if gated.get("resp_bpm") else None),
+                    "heartrate_bpm": (gated["hb_bpm"]
+                                      if gated.get("hb_bpm") else None),
+                    "anomaly_score": gated.get("anomaly"),
+                    "privacy_class": privacy_cls,
+                    "ts": time.time(),
+                }, fh)
+            os.replace(tmp, feature_path)
+        except OSError:
+            pass
+
+    while running:
+        try:
+            buf, _addr = sock.recvfrom(2048)
+        except socket.timeout:
+            buf = None
+
+        now = time.time()
+
+        if buf is not None:
+            n_total += 1
+            pkt = parse_packet(buf)
+            if pkt is not None:
+                if not pkt["crc_ok"]:
+                    n_crc_bad += 1
+                else:
+                    # ADR-118 PrivacyGate: classify + redact before the
+                    # HAP boundary. Returns None for non-eligible classes.
+                    gated = apply_privacy_gate(pkt, privacy_class)
+                    if gated is not None and gated["presence_valid"]:
+                        n_valid += 1
+                        presence_sum += gated["presence"]
+                        motion_sum += gated["motion"]
+                        last_packet_ts = now
+                        # MotionDetected — short-window (each packet)
+                        prev_motion = motion
+                        if not motion and gated["presence"] >= PRESENCE_ON_THRESHOLD:
+                            motion = set_motion(args.toggle, True, motion)
+                        elif motion and gated["presence"] <= PRESENCE_OFF_THRESHOLD:
+                            motion = set_motion(args.toggle, False, motion)
+
+                        # OccupancyDetected — rolling-window avg (§2.1.d
+                        # "Unexpected Occupancy" is a future iter; for now
+                        # we expose Occupancy as sustained presence).
+                        occ_window.append((now, gated["presence"]))
+                        cutoff = now - args.occupancy_window
+                        while occ_window and occ_window[0][0] < cutoff:
+                            occ_window.popleft()
+                        if occ_window:
+                            occ_avg = (sum(p for _, p in occ_window)
+                                       / len(occ_window))
+                            if not occupancy and occ_avg >= OCC_ON_THRESH:
+                                occupancy = True
+                                print(f"[{time.strftime('%H:%M:%S')}] "
+                                      f"Unknown Presence — Occupancy ON "
+                                      f"(rolling_avg={occ_avg:.2f})",
+                                      flush=True)
+                            elif occupancy and occ_avg <= OCC_OFF_THRESH:
+                                occupancy = False
+                                print(f"[{time.strftime('%H:%M:%S')}] "
+                                      f"Occupancy OFF "
+                                      f"(rolling_avg={occ_avg:.2f})",
+                                      flush=True)
+
+                        # Anomaly — only when class allows (Restricted
+                        # gate drops anomaly_score entirely; the dict
+                        # missing the key is the type-level enforcement).
+                        if ("anomaly" in gated
+                                and gated["anomaly"] >= args.anomaly_threshold):
+                            last_anomaly_ts = now
+                            n_anomaly_fires += 1
+                            print(f"[{time.strftime('%H:%M:%S')}] "
+                                  f"Unrecognized Activity Pattern "
+                                  f"(anomaly={gated['anomaly']:.2f})",
+                                  flush=True)
+
+                        if (motion != prev_motion
+                                or not state_path.endswith(".disabled")):
+                            write_state(motion, occupancy, last_anomaly_ts)
+                            write_feature(gated, motion, occupancy,
+                                          privacy_class)
+
+        # Idle release — if the C6 stops sending entirely, clear motion
+        # AND occupancy.
+        if motion and last_packet_ts and (now - last_packet_ts) > IDLE_RELEASE_S:
+            motion = set_motion(args.toggle, False, motion)
+            occupancy = False
+            occ_window.clear()
+            write_state(motion, occupancy, last_anomaly_ts)
+
+        # Periodic summary line (every 10 s) so we can see the watcher is alive
+        if now - last_summary >= 10.0:
+            avg_p = presence_sum / n_valid if n_valid else 0.0
+            avg_m = motion_sum / n_valid if n_valid else 0.0
+            print(
+                f"[{time.strftime('%H:%M:%S')}] 10s stats: "
+                f"pkts={n_total} valid={n_valid} crc_bad={n_crc_bad} "
+                f"avg_presence={avg_p:.2f} avg_motion={avg_m:.2f} "
+                f"motion={motion} occupancy={occupancy} "
+                f"anomaly_fires={n_anomaly_fires}",
+                flush=True,
+            )
+            n_total = n_valid = n_crc_bad = n_anomaly_fires = 0
+            presence_sum = motion_sum = 0.0
+            last_summary = now
+
+    sock.close()
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

scripts/fix-markers.json

@@ -233,6 +233,46 @@
       ],
       "rationale": "At edge tier>=2 on N16R8 PSRAM boards, process_frame() runs update_multi_person_vitals() (4 persons × 256 history samples) plus wasm_runtime_on_frame() back-to-back. The vTaskDelay(1) in edge_task() only fires AFTER process_frame() fully returns — if process_frame() takes >5 s (common on PSRAM-backed boards under sustained 30 pps CSI load), IDLE1 on Core 1 never runs and the Task Watchdog Timer fires. The fix adds two vTaskDelay(1) calls inside process_frame(), gated on tier>=2, at the multi-person vitals boundary and after WASM dispatch. Removing them re-opens the WDT storm on N16R8 hardware.",
       "ref": "https://github.com/ruvnet/RuView/issues/683"
+    },
+    {
+      "id": "RuView#786-tombstone-import",
+      "title": "Tombstone (v1.99.0) __init__.py must raise ImportError with migration URL on import",
+      "files": ["python/tombstone/src/wifi_densepose/__init__.py"],
+      "require": [
+        "raise ImportError(",
+        "pip install wifi-densepose==2.0.0",
+        "github.com/ruvnet/RuView"
+      ],
+      "forbid": [
+        "/^def\\s/",
+        "/^class\\s/",
+        "/^import\\s+wifi_densepose/"
+      ],
+      "rationale": "ADR-117 §7.2 — the v1.99.0 tombstone wheel exists solely to raise a legible ImportError when v1.x users upgrade. If a future refactor adds real code (def / class / imports beyond the bare raise), the module may load partway before failing, breaking the migration narrative. The require patterns lock in the raise + the v2 install hint + the repo URL.",
+      "ref": "https://github.com/ruvnet/RuView/pull/786"
+    },
+    {
+      "id": "RuView#786-tombstone-smoke-cwd",
+      "title": "pip-release.yml tombstone smoke-test must cd out of repo root before importing",
+      "files": [".github/workflows/pip-release.yml"],
+      "require": [
+        "cd /tmp  # away from the repo root's stray wifi_densepose/"
+      ],
+      "rationale": "ADR-117 §P5 — the repo root contains a legacy `./wifi_densepose/__init__.py` from v1. Python places cwd at sys.path[0], so running `import wifi_densepose` from the repo root after a fresh venv install resolves to the legacy directory and bypasses the tombstone wheel entirely. The smoke-test step MUST `cd /tmp` before the import, otherwise CI silently passes against the wrong package. This was the root cause of run 26366648768.",
+      "ref": "https://github.com/ruvnet/RuView/pull/786"
+    },
+    {
+      "id": "RuView#786-pypi-token-auth",
+      "title": "pip-release.yml must authenticate to PyPI via PYPI_API_TOKEN secret, not OIDC",
+      "files": [".github/workflows/pip-release.yml"],
+      "require": [
+        "password: ${{ secrets.PYPI_API_TOKEN }}"
+      ],
+      "forbid": [
+        "id-token: write"
+      ],
+      "rationale": "ADR-117 §P5 — the project is registered with PyPI via API token, not OIDC Trusted Publisher. The token is sourced from GCP Secret Manager (see docs/integrations/pypi-release.md). Re-introducing the `id-token: write` permission would suggest a partial OIDC migration that won't actually work without registering the Trusted Publisher on pypi.org first — a silent regression that would 403 on the next publish.",
+      "ref": "https://github.com/ruvnet/RuView/pull/786"
     }
   ]
 }