Yes — this is the first genuinely interesting control result, and Outcome A clearly happened. The unrelated Viking pairs do not behave like Zana–Khwit: at depth 8+, ZK is down to 1 OH per 223,119 sites, while the unrelated pairs sit around 1 per 12k–21k, and the depth-2 values were nearly identical across all four comparisons. That is exactly the qualitative pattern we wanted. fileciteturn7file0L104-L124
I would not quite let Claude close Phase 2 with the “siblings excluded at p ≈ 6×10⁻⁶” sentence yet, though. That p-value is more model-dependent than the rest of the result. He estimated a sibling expectation as roughly one quarter of the unrelated OH rate, but our unrelated controls are cross-population and share individuals across comparisons. Population differentiation raises the unrelated OH floor, so using that floor to derive a sibling expectation can make the sibling test look stronger than it really is. Claude already acknowledges the cross-population caveat, but the p-value headline outruns that caveat. fileciteturn7file0L126-L147
So I’d say the correct conclusion right now is:
Our custom depth-stratified OH test successfully distinguished Zana–Khwit from three documented-unrelated ancient-human comparisons under the same analysis pipeline. The Zana–Khwit pattern is strongly consistent with parent–offspring and agrees with the published R0 result by an independent route.
That is already a big win. No need to squeeze an overprecise significance claim out of it.
And this is exactly why we identified the harder same-site control earlier. Since Outcome A happened, I would now run one matched same-population test before unlocking Phase 3. Best choice remains the Hofstaðir trio:
- VK110 + VK230 = documented first-degree
- VK102 + VK230 = no documented relationship
- same site, same period, same pipeline
- shared VK230 controls a lot of nuisance variation
If that matched negative retains an OH floor while the known first-degree pair collapses toward zero, then I’d consider the relatedness calibration properly nailed down.
So my recommendation to Claude would be:
Do write the Outcome A result into the README/DISCARDED record, but phrase sibling exclusion as provisional and do not open Phase 3 yet. Run the Hofstaðir matched control next. If it reproduces the relationship-dependent behavior, close Phase 2 and open Phase 3.
Also, the download/repair side is now legitimately done: all three BAMs are ~8.5–9.4 GiB, MD5-matched, full-decoded, read counts exactly match the archive, and all are indexed. fileciteturn7file0L68-L94
So we’re very close. The core null test passed. One tougher matched control is the clean way to finish this.
