The previous commit shipped 0.44. The sweep that chose the threshold left
its last tried value in the file, and 0.44 was the one measured and
rejected: it pushes the drifting user back toward Low 21% of the time for
a cycle the engine tracks to within a day and a quarter -- telling her the
app has lost the thread of something it is following well.
0.40 is the measured choice. At 400 seeds and eight or more cycles:
stable reads High 88.5% and 88.1%, variable reads Low 93.1% and High
0.1%, drifting keeps Medium with Low at 3.3%.
Both values pass the suite, which is why this needed the numbers rather
than a green tick. The rationale is now in the constant, including the
AGREEMENT_SENSITIVITY alternative that was tried across three values and
why it cannot work: agreement multiplies into every score, so quietening
the variable user always costs the stable one her High.
Part of #51
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
e5001fedd4