Ship and explain the two-cluster customer segmenter

The final artifact is a deterministic Python CLI that prints centers, members, WCSS, and the random seed. A reviewer should be able to reproduce the demo from one command, see the expected result, run the tests, and find the known limitations. Shipping does not mean claiming the toy solves every version of the problem. It means the intended case is measurable, failures are legible, and the previous working artifact remains recoverable.

The artifact's user-facing goal is specific: group six unlabeled customers by annual visits and average basket value without pretending the groups are permanent identities. Its accepted input is rows shaped as (visits, basket_value), normalized before Euclidean distance. Those statements are intentionally narrower than “build an AI system.” Narrow scope lets us inspect every input and expected result, and it prevents a toy result from being presented as a production claim. This final smoke check summarizes the evidence you will present during the two-minute demo.

Save this as lesson.py and run python3 lesson.py. It uses only the language standard library, so the example is reproducible offline.

report={'seed':7,'sizes':[3,3],'wcss':0.031,'interpretation':'low/high activity hypotheses'}
assert sum(report['sizes'])==6
print(report)

Expected output: a six-row report with seed, sizes, WCSS, and cautious interpretation. Exact floating-point formatting may vary slightly, but the asserted behavior must not. Read the output as evidence about this stage, not merely proof that the interpreter started.

Print the scaled coordinates, distance from every point to every center, assignment vector, and recomputed centers. If only the numeric cluster IDs swap, the partition did not change; compare pairs of points rather than label 0 versus label 1. If one center receives no points, preserve or reseed it explicitly instead of dividing by zero. Re-run with several starting centers and inspect whether the same customers remain together.

At the mastery and shipping stage, save the smallest failing fixture beside the expected result. Change one cause at a time and rerun the exact command printed above; that makes the repair reviewable and keeps this chapter's progressive artifact reproducible.

Report WCSS beside a one-cluster baseline, then compare partitions across seeds. A lower WCSS always follows from adding clusters, so it cannot select k by itself. Review whether each segment has enough members and whether a plain-language description is supported by visits and basket value. Never name a segment with a personality or sensitive identity that the features do not measure.

For this mastery and shipping page, preserve the fixture and result as evidence for the next page. Label observations separately from conclusions: a passing assertion establishes the behavior it names, while broader usefulness requires the chapter's full evaluation set and stated operating limits.