`value_destroyed` is already `P(destroyed) x Location::value()`. Weighting criticals by the same function gives the two columns a shared basis on top of a shared driver, which aligns them rather than separating them. The orthogonal half is the through-armour term, and by construction: four LB-X firing cluster into whole armour score 0.393, all of it the natural 2, while `value_destroyed` is exactly 0.00000 - a critical through intact armour destroys nothing, so no weighting lets the other column see it. The 0.77 comes from the stripped regime, where the two measure the same event from two sides. Recorded with two cautions: a corpus predating the through-armour term carries only the collinear half, and the recording bot never priced the column, so no decision in it was taken to fish for criticals. If decorrelation is wanted, the column splits along a seam that is already in the arithmetic.