Kjell Tore Guttormsen
4c4457f6e9
The brief pre-registers "median forbedring >= 30 % pa (a) eller (b) -> adopt. < 15 % -> decline." decideVerdict() required BOTH metrics to clear the adopt bar and BOTH to fall under the decline bar, a rule introduced at execution time (plan Step 11 restated the brief's wording unchanged). The divergence is behavioural, not cosmetic: sources +90% / dimensions +10% is adopt under the brief and was inconclusive in code; sources +2% / dimensions +20% is decline under the brief and was inconclusive in code. Adopt is evaluated before decline, so the OR bars do not conflict where they overlap. docs/storm-measurement.md §2 and the test pins follow the same rule. The stricter AND rule may well be the better decision procedure — but changing it after the fact is exactly what pre-registration exists to prevent. Review finding c37bf50d. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011vPSXe88qp5aqWUqbDNWoF |
||
|---|---|---|
| .. | ||
| annotate.mjs | ||
| bakeoff-armA-merge.mjs | ||
| bakeoff-fidelity.mjs | ||
| gen-expected-prom.mjs | ||
| q3-cache-prefix-experiment.mjs | ||
| storm-measure.mjs | ||
| synthesis-measure.mjs | ||
| trekreview-armB.workflow.mjs | ||