Measure whether the threshold prediction game works

Translate the claim into assertions or a tiny eval harness. The metric to protect is: confusion matrix sums to 5; accuracy matches hand count. Always record the denominator (how many cases) beside any rate. A percentage without a denominator is marketing, not measurement.

counts={'tp':2,'fp':0,'tn':2,'fn':1}
assert sum(counts.values())==5
print('confusion sums to n')

Expected evidence: confusion sums to n. A passing assertion proves only the behavior it names; broader usefulness still needs the chapter’s full limits.

Be explicit: beating the baseline (confusion counts computed by hand at threshold 0.5) on this fixture does not prove behavior under threshold outside 0..1, or reporting accuracy without TP/FP/TN/FN. Label observations separately from conclusions so the next page inherits honest evidence about the threshold prediction game.

Compute confusion matrix sums to 5; accuracy matches hand count with the denominator written beside the rate every time. For this chapter, the evaluation set is intentionally tiny; that is allowed only if you say so in the evidence. Compare against confusion counts computed by hand at threshold 0.5 before celebrating.

Add one negative case aimed at threshold outside 0..1, or reporting accuracy without TP/FP/TN/FN. A suite with only happy cases cannot protect the threshold prediction game when the characteristic failure appears in review.

If a check is expensive or flaky, shrink it until it is deterministic on 5 (truth, score) pairs. Flaky green builds teach the team to ignore gates. Record what this page does not prove so security-ops and mastery-ship inherit honest limits.

At the evaluation stage for prediction-game, the job is narrower than finishing a product demo. You are creating one progressive evidence piece about 5 (truth, score) pairs that later pages inherit without redefining success. Keep that fixture small enough to inspect by hand, keep outputs copy-pasteable as text, and refuse to narrate this baseline as if it were a production SLA: confusion counts computed by hand at threshold 0.5.

For this page specifically, success looks like metrics with explicit denominators and a negative case while still centering the user decision to choose a cutoff that balances errors without claiming generalization from five rows. If you cannot point to a file, command, or assertion that proves that for the threshold prediction game, stay on this page instead of advancing.

Confusion matrix glossary

Previous · Next

Return to the prediction game scenario and restate what this chapter proved on page validation.mdx. Name one metric, one ownership rule, and one regression test you will keep. Explain how this page connects to the previous page without repeating earlier paragraphs. If you cannot name a falsifier, the chapter is still a story rather than a controlled practice. Write the falsifier as an observable event with a threshold.

Return to the prediction game scenario and restate what this chapter proved on page validation.mdx. Name one metric, one ownership rule, and one regression test you will keep. Explain how this page connects to the previous page without repeating earlier paragraphs. If you cannot name a falsifier, the chapter is still a story rather than a controlled practice. Write the falsifier as an observable event with a threshold.

Return to the prediction game scenario and restate what this chapter proved on page validation.mdx. Name one metric, one ownership rule, and one regression test you will keep. Explain how this page connects to the previous page without repeating earlier paragraphs. If you cannot name a falsifier, the chapter is still a story rather than a controlled practice. Write the falsifier as an observable event with a threshold.

For prediction-game, write a transfer example that differs in one constraint from the chapter scenario. Keep the quality bar fixed. Explain which check still applies.