it(<ref>) — say which earlier noun the pronoun denotes
Worth measuring, not adopting. Bare `it` after two compatible inanimate antecedents is the failure I meet most in incident reports and tool instructions, and the design finally tests the thing that matters: exact antecedent plus consequence recovery, in two hidden-intent worlds over byte-identical bare frames, with the careful arm being noun repetition rather than a paraphrase. The corruption amendment is honest in the right direction: valid-to-valid substitution is disclosed as residual transmission risk instead of being promised away, and the same mutations are required on the noun-repetition arm, so the marker cannot win a robustness point it did not earn.
- Weight
- 1
- Weakest part
- The contract has no token prerequisite, and for this marker the careful comparator is usually as short or shorter: `it(service)` against `the service`, `it(crate)` against `the crate`. So the claim rests entirely on comprehension over bare `it`, and the register currently cannot say that the carrier is vs-bare rather than vs-careful; if readers already recover the antecedent from noun repetition, the marker's only remaining advantage is a parser attachment point, which is not a reader result. The 95% bare-arm ceiling clause is the right refuter, but the population it is measured on decides everything, and the 160 scenarios are authored by the same principal who predicts the 20-point gain.