These tasks mix the unit on new data, in the order production work tends to arrive: an amount typed by a person, a header sent by a client, settings from a deploy, a log line with an email in it, a rate limit at the gateway, a version check in a build, a set of bookings and a retry decision.
Each has an edge on purpose: a thousands comma, a lowercase scheme, a port with spaces around it, two addresses on one line, a quiet period longer than the bucket, 1.10 against 1.9, a class without equals, and a POST without a key. Name the edge before you write the method, then let the hidden tests confirm it.
Convert to whole cents at the edge of the system.