Measure whether the two-cluster segmenter works

Translate the claim into assertions or a tiny eval harness. The metric to protect is: silhouette or inertia recorded; centers have finite values. Always record the denominator (how many cases) beside any rate. A percentage without a denominator is marketing, not measurement.

from math import dist
groups=[[(0,0),(.1,.1),(.2,.1)],[(.8,.9),(.9,.9),(1,1)]]
centers=[tuple(sum(v)/len(g) for v in zip(*g)) for g in groups]
wcss=sum(dist(p,c)**2 for g,c in zip(groups,centers) for p in g)
print(round(wcss,3)); assert wcss < .1

Expected output: 0.053, followed by a successful assertion. A passing assertion proves only the behavior it names; broader usefulness still needs the chapter’s full limits.

Be explicit: beating the baseline (random two-group assignment inertia for comparison) on this fixture does not prove behavior under k larger than n, or scaling skipped so one feature dominates. Label observations separately from conclusions so the next page inherits honest evidence about the two-cluster segmenter.

Compute silhouette or inertia recorded; centers have finite values 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 random two-group assignment inertia for comparison before celebrating.

Add one negative case aimed at k larger than n, or scaling skipped so one feature dominates. A suite with only happy cases cannot protect the two-cluster segmenter when the characteristic failure appears in review.

If a check is expensive or flaky, shrink it until it is deterministic on small 2D customer matrix. 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 clustering-basics, the job is narrower than finishing a product demo. You are creating one progressive evidence piece about small 2D customer matrix 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: random two-group assignment inertia for comparison.

For this page specifically, success looks like metrics with explicit denominators and a negative case while still centering the user decision to group customers by spend/visits without pretending clusters are ground-truth labels. If you cannot point to a file, command, or assertion that proves that for the two-cluster segmenter, stay on this page instead of advancing.

Glossary: clustering · Cheatsheet: ML Python starter

Previous · Next

Return to the clustering basics 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 clustering basics 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 clustering basics 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.