Files
wehub-resource-sync 9740bc64c9
Continuous Deployment / Deploy to Production (push) Blocked by required conditions
Continuous Deployment / Rollback Deployment (push) Blocked by required conditions
Continuous Deployment / Post-deployment Monitoring (push) Blocked by required conditions
Continuous Deployment / Notify Deployment Status (push) Blocked by required conditions
Firmware QEMU Tests (ADR-061) / QEMU Test (edge-tier1) (push) Has been skipped
Firmware QEMU Tests (ADR-061) / QEMU Test (full-adr060) (push) Has been skipped
Firmware QEMU Tests (ADR-061) / QEMU Test (tdm-3node) (push) Has been skipped
Firmware QEMU Tests (ADR-061) / Swarm Test (ADR-062) (push) Has been skipped
npm packages / tools/ruview-mcp (node 22) (push) Failing after 1s
nvsim-server → ghcr.io / build-and-publish (push) Failing after 1s
ruview-swarm CI guard / tests (full+train) (push) Failing after 2s
Bench Regression Guard / bench compile-verify (--no-run) (push) Failing after 0s
Bench Regression Guard / bench fast-run (informational, non-gating) (push) Has been skipped
Firmware CI / Verify version.txt matches release tag (push) Has been skipped
Dashboard a11y + cross-browser / a11y (push) Failing after 0s
nvsim Dashboard → GitHub Pages / build-and-deploy (push) Failing after 2s
Firmware CI / Build firmware (esp32s3 / 4mb) (push) Failing after 15s
Firmware QEMU Tests (ADR-061) / Build Espressif QEMU (push) Failing after 1s
Firmware QEMU Tests (ADR-061) / Fuzz Testing (ADR-061 Layer 6) (push) Failing after 1s
Continuous Deployment / Pre-deployment Checks (push) Has been skipped
Continuous Deployment / Deploy to Staging (push) Waiting to run
Firmware CI / Build firmware (esp32c6 / c6-4mb) (push) Failing after 15s
Firmware CI / Build firmware (esp32s3 / 8mb) (push) Failing after 15s
Firmware QEMU Tests (ADR-061) / QEMU Test (boundary-max) (push) Has been skipped
Firmware QEMU Tests (ADR-061) / QEMU Test (boundary-min) (push) Has been skipped
Firmware QEMU Tests (ADR-061) / QEMU Test (default) (push) Has been skipped
Firmware QEMU Tests (ADR-061) / QEMU Test (edge-tier0) (push) Has been skipped
Firmware QEMU Tests (ADR-061) / NVS Matrix Generation (push) Failing after 1s
Security Scanning / Security Policy Compliance (push) Failing after 0s
Security Scanning / Security Report (push) Waiting to run
Security Scanning / Dependency Vulnerability Scan (push) Failing after 0s
Security Scanning / Static Application Security Testing (push) Failing after 1s
Security Scanning / Infrastructure Security Scan (push) Failing after 1s
Security Scanning / Secret Scanning (push) Failing after 1s
npm packages / harness/ruview (node 22) (push) Failing after 17s
Security Scanning / License Compliance Scan (push) Failing after 1s
Security Scanning / Container Security Scan (push) Failing after 4s
three.js demos → GitHub Pages / build-and-deploy (push) Failing after 1s
Verify Pipeline Determinism / Verify Pipeline Determinism (3.11) (push) Failing after 1s
Fix-Marker Regression Guard / Verify fix markers (push) Failing after 1s
ADR-115 MQTT integration tests / mqtt-integration (push) Failing after 1s
npm packages / harness/ruview (node 20) (push) Failing after 1s
npm packages / tools/ruview-mcp (node 20) (push) Failing after 1s
npm packages / tools/ruview-cli (node 20) (push) Failing after 1s
npm packages / tools/ruview-cli (node 22) (push) Failing after 1s
BFLD MQTT Integration / cargo test --features mqtt (live mosquitto) (push) Failing after 29s
ruview-swarm CI guard / build train_marl bin (push) Failing after 2s
ruview-swarm CI guard / clippy (-D warnings, --no-deps) (push) Failing after 3s
ruview-swarm CI guard / tests (ruflo) (push) Failing after 1s
ruview-swarm CI guard / tests (train) (push) Failing after 2s
ruview-swarm CI guard / tests (default) (push) Failing after 2s
Point Cloud Viewer → GitHub Pages / build-and-deploy (push) Failing after 8s
ruview-swarm CI guard / ITAR / publish guard (push) Failing after 0s
wifi-densepose sensing-server → Docker Hub + ghcr.io / build · push · smoke-test (push) Failing after 1s
chore: import upstream snapshot with attribution
2026-07-13 11:59:54 +08:00
..

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.