docs/adr/ADR-091-stand-off-radar-tier-research.md
| Field | Value |
|---|---|
| Status | Proposed — Research only. No production hardware integration. Decision deferred pending sub-$1k COTS sub-THz transceiver availability and clear non-export-controlled use case. |
| Date | 2026-04-26 |
| Authors | ruv |
| Refines | ADR-021 (60 GHz / mmWave vital-signs pipeline) |
| Companion | docs/research/quantum-sensing/16-ghost-murmur-ruview-spec.md §6.3, ADR-029 (RuvSense multistatic), ADR-089 (nvsim simulator), ADR-090 (Lindblad extension) |
On Good Friday 3 April 2026 the press reported a CIA system called "Ghost Murmur"
— a Lockheed Skunk Works NV-diamond + AI sensor reportedly used in the recovery
of an F-15E pilot in southern Iran. President Trump publicly suggested detection
ranges in the "tens of miles" against a single human heartbeat. RuView shipped
a research spec (16-ghost-murmur-ruview-spec.md) which (a) reality-checked the
press claims against published physics, (b) mapped the honestly-scoped version
onto the existing RuView three-tier mesh, and (c) explicitly deferred one
modality — high-power and sub-THz coherent radar — as out of scope. From §6.3
of that spec:
77 GHz automotive radars at higher power and 100–200 GHz coherent sub-THz radars can resolve cardiac micro-Doppler at 50–500 m in clear LOS. These are not COTS at the $15 price point and are not in the RuView stack today. They are also subject to ITAR / export-control review and explicitly out of scope for this open-source project.
That sentence is the trigger for this ADR. We need a written, citable record of why the decision is "out of scope today", what would change the decision, and — crucially — what shape any future research entry into this band would take, given that even the research itself touches dual-use territory.
RuView's existing modality coverage (per the CLAUDE.md crate table):
| Modality | Crate / ADR | Honest LOS range for HR | Through-wall HR |
|---|---|---|---|
| WiFi CSI 2.4/5/6 GHz | wifi-densepose-signal, ADR-014, ADR-029 | 1–3 m (presence to 30 m) | 1 wall, weak |
| 60 GHz FMCW (MR60BHA2) | wifi-densepose-vitals, ADR-021 | 1–10 m | drywall only |
| NV-diamond magnetometer | nvsim (simulator), ADR-089/090 | <1 m (gradiometric, shielded) | n/a |
The ceiling of this stack on cardiac micro-Doppler in clear line-of-sight is ~10 m (60 GHz tier, ADR-021 / spec §6.1). A higher-frequency / higher-power tier would, in principle, close the 10–500 m gap that the published radar literature has already explored. The two candidate bands:
This ADR examines both bands — the SOTA, the COTS reality, the regulatory envelope, the physics ceiling, the export-control posture, and the open-source ethics — and lands at a build / research / skip recommendation per row.
The 76–81 GHz band is now densely populated with single-chip CMOS / SiGe transceivers. Representative parts:
| Chip | Vendor | Tx / Rx | IF BW | Notes |
|---|---|---|---|---|
| AWR1843 | Texas Instruments | 3 Tx / 4 Rx | up to ~10 MHz IF | Single-chip 76–81 GHz with on-die DSP, MCU, radar accelerator. Long-range automotive ACC, AEB. (TI AWR1843) |
| AWR2243 | Texas Instruments | 3 Tx / 4 Rx | up to ~20 MHz IF | Cascadable for higher angular resolution (up to 12 Tx / 16 Rx with multi-chip cascade). (TI AWR2243) |
| BGT60 family | Infineon | 1–3 Tx / 1–4 Rx | Several MHz IF | 60 GHz primarily; BGT24 family at 24 GHz. Smaller, lower power, gesture / presence focus. |
| TEF82xx | NXP | up to 4 Tx / 4 Rx | several MHz IF | Automotive-grade 76–81 GHz. |
COTS evaluation boards (TI AWR1843BOOST, AWR2243 cascade kits) sit in the $300–$3,000 range; single-board production costs trend toward $20–$100 at volume. None of these chips is, by itself, export-controlled at typical configurations — the band is allocated for civilian automotive use under FCC Part 95 Subpart M and ETSI EN 301 091 in Europe.
EIRP envelope: 47 CFR §95.M (and the historical §15.253 it replaced) caps the 76–81 GHz band at 50 dBm average / 55 dBm peak EIRP measured in 1 MHz RBW (Federal Register notice 2017, eCFR 47 CFR Part 95 Subpart M). That is roughly 100 W EIRP average, 316 W peak. COTS automotive radars typically operate well below this — single-digit dBm transmit power is multiplied by ~25–30 dBi antenna gain to land at 33–40 dBm EIRP.
Three regulatory paths exist for an open-source project that wants to push beyond typical commercial deployment power:
For an open-source mesh node shipping to anonymous users worldwide, only path (1) is defensible. Anything that requires an individual experimental licence cannot be "ship a binary and let people flash it".
The 77 GHz cardiac literature is dominated by short-range work (0.3–2 m), e.g.:
The most cited long-range radar cardiac measurement is at 24 GHz, not 77 GHz:
We could not find an equivalent peer-reviewed cardiac measurement at 77 GHz beyond ~5 m with a verifiable antenna gain × power × integration-time budget. The work that exists at 77 GHz is overwhelmingly bench-scale (≤ 2 m). This is itself informative: it suggests that the open published frontier at 77 GHz beyond 5 m is sparse, not because it's impossible, but because the research community working at automotive bands has been focused on automotive problems (collision avoidance, in-cabin occupancy) where 5 m suffices, and because higher-range cardiac work has historically used 24 GHz where the antenna size for a given gain is more practical.
The radar equation for chest-wall displacement detection scales roughly as:
SNR ∝ (P_t · G_t · G_r · σ_chest) / (R^4 · k T B · NF) · √(t_int / T_coh)
where σ_chest ≈ 10⁻³–10⁻² m² for the cardiac scatterer at 77 GHz, NF ≈ 10–15 dB on COTS chips, and integration time t_int is bounded by T_coh ≈ 0.5–1 s (physiological coherence — the heart period itself).
Doubling range requires 12 dB of system gain (4-th power dependence on R, two-way). At the part-95 §95.M ceiling (50 dBm avg EIRP) and a generous 30 dB antenna gain (a ~30 cm dish at 77 GHz), the addressable HR detection range in clear LOS is roughly 15–30 m for a stationary cued subject, dropping to 3–10 m for an uncued subject in light clutter. Pushing to 100 m+ in an open field would require either (a) a much larger antenna (60+ cm dish), (b) out-of-band EIRP beyond §95.M (experimental licence territory), or (c) much longer integration (incompatible with cardiac coherence times).
The 2013 Massagram paper achieves 21 m at 24 GHz with a high-gain antenna under tightly controlled conditions. Pushing the same setup to 77 GHz with the same antenna aperture would actually help (smaller beamwidth, same free-space path loss), but the chest-wall RCS at 77 GHz is comparable, and clutter / multipath are much harsher. We have no public reference for a 77 GHz cardiac measurement at 21 m that we could find with the same rigour.
An open-source mesh node spec implies "ships in a kit, does not require individual licensing, fits the existing PoE / mini-PC edge model". That implies:
The chip cost is already met by COTS. The antenna and host are met. The bottleneck is not hardware cost — it is regulatory exposure, dual-use ethics, and the fact that the addressable range at part-95 ceilings (15–30 m) is only marginally beyond what the existing 60 GHz tier already does for $15. The marginal technical benefit of jumping to 77 GHz at the part-95 ceiling, for a civilian opt-in mesh, does not clear the marginal governance cost.
At 140 GHz, λ ≈ 2.14 mm. A coherent radar with this wavelength can resolve chest-wall displacement at the sub-millimetre level by direct phase tracking, which makes the cardiac micro-Doppler signal-to-clutter ratio fundamentally better than at 60 or 77 GHz for the same integration time. Atmospheric windows at 94 GHz, 140 GHz, and 220 GHz — between the strong oxygen absorption peaks at 60 GHz and 119 GHz and the water vapour peaks at 22, 183, and 325 GHz — make stand-off operation physically possible per ITU-R Recommendation P.676 (ITU-R P.676-11, ITU-R P.676-9).
Order-of-magnitude values for one-way attenuation through standard atmosphere at sea level, taken from ITU-R P.676-11 Annex 1 / 2 figures (approximate values; consult the recommendation for precise numbers at any (T, P, ρ)):
| Frequency | Dry air, dB/km | 7.5 g/m³ humid, dB/km | Notes |
|---|---|---|---|
| 60 GHz | ~14 | ~14.5 | O₂ absorption peak — terrible for stand-off |
| 77 GHz | ~0.4 | ~0.5 | Allocated for automotive radar |
| 94 GHz | ~0.4 | ~0.7 | First major window above 60 GHz |
| 119 GHz | ~2.5 | ~3 | O₂ subsidiary peak |
| 140 GHz | ~0.5 | ~1.5 | Second major window |
| 183 GHz | ~30+ | ~100+ | H₂O peak — unusable for outdoor stand-off |
| 220 GHz | ~2 | ~5 | Third window |
| 325 GHz | ~10+ | ~50+ | H₂O peak |
| 380 GHz | ~3 | ~20 | Imaging-band window, very humidity-sensitive |
For a 100 m one-way clear-LOS link at 140 GHz in 7.5 g/m³ humidity, atmospheric attenuation alone is ~0.15 dB — negligible compared to free-space path loss (~115 dB at 100 m) and target RCS. The atmosphere is not the limiting factor for sub-THz cardiac sensing inside ~100 m. Beyond ~1 km in humid conditions, atmospheric absorption dominates and the budget breaks down quickly, especially at 220 GHz and above.
The sub-THz commercial landscape in 2026 is sparse and expensive:
A coherent sub-THz radar maintains phase reference between Tx and Rx (and ideally across multiple Tx / Rx channels for MIMO or multistatic operation). Coherent processing buys:
It costs:
For a single-aperture monostatic radar (one Tx, one Rx, one chip), coherence is nearly free (the LO is shared on-die). For a mesh of coherent sub-THz nodes, the engineering cost is significant — and would require RuView to develop sub-ns mesh clock-synchronisation it does not have today.
The published peer-reviewed cardiac literature at 100–300 GHz is sparse but not empty:
Honest assessment: published primary work on cardiac micro-Doppler at beyond a few meters in the 100–300 GHz band is limited. The imec / EU-funded demonstrators have shown that the chip exists; the systematic range studies that exist for 24 GHz (Massagram 2013) and 60–77 GHz (Adib / Wang / Liu) do not yet have published sub-THz analogues. Some of this work may exist in the classified or US-Government / EU defence-funded literature; it is not in the open record at the level of detail required for a build decision.
For a stationary, cued, line-of-sight subject with chest-wall displacement ~0.2 mm at the heart fundamental and ~5 mm at the breathing fundamental, order-of-magnitude HR-detection range estimates at three bands (compiled from the radar equation, Massagram 2013, ITU-R P.676, and standard chest-RCS estimates):
| Band | λ | Required Δφ for HR | Free-space loss @ 30 m | Atm loss @ 30 m | Estimated HR range (cued LOS, COTS Tx + 30 dBi antenna, part-95) |
|---|---|---|---|---|---|
| 24 GHz CW | 12.5 mm | 0.36° | 89 dB | <0.01 dB | 21 m measured (Massagram 2013) |
| 60 GHz FMCW | 5.0 mm | 0.9° | 97 dB | 0.4 dB | 5–10 m (ADR-021 / spec §6.1) |
| 77 GHz FMCW | 3.9 mm | 1.2° | 99 dB | 0.01 dB | ~15–30 m (estimated, no rigorous public ref beyond 5 m) |
| 140 GHz FMCW | 2.1 mm | 2.2° | 105 dB | 0.04 dB | ~30–100 m (estimated, sparse open lit) |
| 220 GHz FMCW | 1.4 mm | 3.3° | 109 dB | 0.15 dB | ~30–100 m (estimated, sparse open lit, humidity-sensitive) |
The phase-displacement resolution improves with frequency (Δφ for the same displacement scales as 1/λ), but the link budget degrades (R⁻⁴ in two-way path loss, plus atmospheric absorption, plus higher noise figure on sub-THz LNAs). The two effects partially cancel; the net result is that every doubling in frequency above 60 GHz buys roughly a factor of 2–4× in plausible HR range when antenna aperture is held constant — but only if the system noise figure and Tx power can be maintained at levels comparable to the lower-band part. Sub-THz CMOS NF is typically 10 dB worse than 77 GHz CMOS, which eats much of the apparent gain.
| Range | 77 GHz total loss | 140 GHz total loss | 220 GHz total loss |
|---|---|---|---|
| 1 m | 70 dB + 0 | 76 dB + 0 | 80 dB + 0 |
| 10 m | 90 dB + 0.01 | 96 dB + 0.03 | 100 dB + 0.1 |
| 100 m | 110 dB + 0.1 | 116 dB + 0.3 | 120 dB + 1 |
| 1 km | 130 dB + 1 | 136 dB + 3 | 140 dB + 10 |
| 10 km | 150 dB + 10 | 156 dB + 30 | 160 dB + 100 |
| 65 km (40 mi) | 168 dB + 65 | 174 dB + 200+ | 178 dB + impossible |
Observations:
Holding integration time at 0.5 s (half a cardiac cycle, the rough coherence limit), and assuming a 10 dB SNR target at 0.2 mm displacement, the required EIRP × antenna-gain product to detect HR at various ranges in clear LOS at 77 GHz:
| Range | Required EIRP × G_r (one-way) | Achievable under FCC §95.M? |
|---|---|---|
| 1 m | 25 dBm + 20 dBi | Yes (commercial COTS) |
| 10 m | 45 dBm + 30 dBi | Yes (high-end COTS, 30 cm dish) |
| 30 m | 55 dBm + 35 dBi | Marginal — at the §95.M peak ceiling |
| 100 m | 70 dBm + 45 dBi | No — above §95.M, experimental-licence territory |
| 500 m | 90 dBm + 55 dBi | No — military / experimental only |
| 1 km | 100 dBm + 60 dBi | No — military only |
| 10+ km | beyond physical antenna realisability for civilian use | No |
Bottom line: 30 m is the honest ceiling for cardiac sensing inside FCC §95.M power limits with a 30 cm dish at 77 GHz. Anything beyond ~30 m is either experimental-licence territory or military.
The press claim of HR detection at "40 miles" (65 km) corresponds to a one-way path loss at 77 GHz of roughly 168 dB (free space) plus ~65 dB of atmospheric absorption (humid). Closing this link to detect a 0.2 mm chest-wall displacement would require:
The honest reading: HR detection at "tens of miles" against a single heartbeat is not consistent with any physically realisable open-air radar system at any band the laws of physics allow. The claim either refers to cued detection (i.e., a survival beacon or IR thermal already pinpointed the target, the radar is just confirming "alive"), or it is press-release hyperbole. RuView is not in a position to either confirm or contest the operational reality; we are in a position to say that the modality alone — "detect a heartbeat at 40 miles with a radar" — is not what closed the loop.
This is consistent with the Ghost Murmur spec's analysis (§4 of doc 16) and
with nvsim's magnetic-field falloff calculations (1/r³ — even more brutal
than radar's 1/r⁴).
| Use | FCC path | Practical for open source? |
|---|---|---|
| 60 GHz unlicensed (existing tier) | Part 15.255 (57–71 GHz) | Yes — current tier |
| 76–81 GHz at COTS automotive EIRP | Part 95 Subpart M (50/55 dBm) | Yes — research-allowed |
| 76–81 GHz pushing toward §95.M ceiling | Part 95 Subpart M | Yes — single-installation |
| 76–81 GHz beyond §95.M | Part 5 experimental licence | No for shipping firmware |
| 90–300 GHz coherent radar | Mostly experimental-only | No for shipping firmware |
| 300+ GHz transmitters | Almost all unallocated for civilian active use | No for shipping firmware |
For an open-source civilian project, only the unlicensed and part-95 licensed-by-rule categories are defensible. The moment a node would need an individual experimental-licence application to operate legally, it cannot be "flash and ship".
The correct posture for RuView is: assume the worst case. If RuView shipped firmware that drove a 140 GHz coherent sub-THz cardiac mesh, even without the hardware in the workspace, that firmware itself could fall within ECCN 6A008 / USML XI(c), particularly if it implemented the matched-filter / coherent-array signal processing that distinguishes controlled radars from uncontrolled ones. We do not ship that firmware.
The Ghost Murmur spec (§9) is explicit about RuView's civilian-only ethics framing:
Stand-off radar at 77 GHz with §95.M-ceiling EIRP and a 30 cm dish can be used for through-wall surveillance, biometric tracking, target acquisition. Sub-THz coherent radar can do the same with finer resolution. Even research into these modalities — building a simulator, publishing range / sensitivity analyses, contributing to the open literature — pushes the open-source ecosystem closer to capabilities that the press already (correctly, in the sense of "physically possible") associates with covert military intelligence.
Two specific dual-use risks if RuView research were to ship anything beyond this ADR:
| Tier | Build now | Research only | Skip permanently | Notes |
|---|---|---|---|---|
| 77 GHz commercial COTS (already shipping at low EIRP via the 60 GHz tier; mentioned for completeness) | — | — | — | Already covered by 60 GHz tier ADR-021. No action. |
| 77 GHz higher-power experimental (≤ §95.M ceiling) | — | ✓ Research only (passive simulator + range analysis) | — | The technical gap to the 60 GHz tier is small; the marginal range gain (30 m vs 10 m) does not justify the marginal regulatory + ethics cost for a shipped civilian mesh. Research / simulation only. |
| 77 GHz beyond §95.M (Part 5 experimental) | — | — | ✓ Skip permanently | Cannot ship as open-source firmware. Individual experimental licences are not delegatable. |
| 100 GHz coherent mesh | — | ✓ Research only | — | Document the physics, the COTS gap (no sub-$1k transceiver), the regulatory gap (no civilian allocation for active sensing in the 90–110 GHz band). Build only if all three conditions in §7.4 below trigger. |
| 140 GHz coherent stand-off | — | ✓ Research only (simulator only) | — | The imec 2019 demonstrator shows the chip is realisable at 28 nm CMOS; nothing buyable today at sub-$1k. ECCN 6A008 risk is real. Simulator OK; firmware no. |
| 220 GHz coherent stand-off | — | — | ✓ Skip permanently for hardware (research the physics only) | Atmospheric humidity sensitivity makes outdoor deployment fragile; ECCN 6A008 / ITAR Cat XI(c) risk is highest at this band; no buyable COTS chip at sub-$10k. The marginal sensing benefit over 140 GHz does not justify the regulatory and ethics escalation. |
| 380+ GHz imaging | — | — | ✓ Skip permanently | Imaging-band, not radar; humidity destroys outdoor link; export-controlled at any meaningful aperture. Not RuView's modality at any plausible build. |
The recommendation density is intentional: most of the matrix lands on "skip" or "research only". Only one row (77 GHz at the §95.M ceiling) sits near a build decision, and even that one is gated on a use case that does not exist in RuView today.
nvsim patternADR-089 / 090 established the precedent: when a sensing modality is physically interesting but not buildable today, RuView ships a deterministic forward simulator, not hardware. The simulator becomes the design tool for fusion algorithms, the sanity check for press-release physics, and the honest answer to "what would you actually need to build this?"
Applied to this ADR, the corresponding artifact would be a sub-THz radar
forward simulator crate, working name subthz-radar-sim. Scope:
rand_chacha for byte-identical outputs across
runs.RadarFrame-shaped output with magic distinct from
0xC51A_6E70 (nvsim's MagFrame) and 0xC511_0001 (CSI frames).nvsim::Pipeline::run_with_witness.ruvector/viewpoint/; it must not be wired to the sub-THz
radar simulator's output.The same questions nvsim answers for NV-diamond, the sub-THz simulator
would answer for radar:
These are pre-build sanity checks. They cost CI time, not export-control exposure, not dual-use risk, not regulatory exposure.
Promotion of any "research only" row in §6 to "build" requires all three of:
If any one of those three is missing, this ADR remains Proposed indefinitely and the modality stays in the simulator-only tier.
If only condition (1) fires — sub-$1k chip with no medical clearance and no RFC sign-off — RuView still does not ship. The simulator might be expanded; no firmware ships.
ruvector/viewpoint/.nvsim NV-diamond pipeline simulator. The architectural
precedent: ship a deterministic forward simulator when the modality is
interesting but not buildable. Same proof / witness pattern applies here.nvsim Lindblad / Hamiltonian extension. Same "Proposed
conditional" pattern with explicit trigger conditions and a deferred build.
This ADR follows the same shape.docs/research/quantum-sensing/16-ghost-murmur-ruview-spec.md — the
Ghost Murmur reality-check spec. §6.3 is the explicit boundary that
triggered this ADR. §7–§9 establish the architecture, ethics, and legal
framework that this ADR inherits.These are the questions that, if answered differently, could move a row of the §6 decision matrix:
This ADR is Proposed — Research only. The decision matrix in §6 lands on:
If RuView builds anything in this space, it builds a sub-THz forward
simulator (subthz-radar-sim) following the nvsim pattern: deterministic,
host-side, witness-verified, with explicit "what this is not for" framing
and no firmware. The simulator does not ship until conditions §7.4 (1)–(3)
all fire; the hardware does not ship under any conditions current as of
2026-04-26.
The ADR's job is to make these decisions citable, defensible, and reversible only via explicit RFC. It is not a build commitment.