Moss Travel, a fictional scheduling service, is reviewing small functions that keep state and read external text. One function owns a private counter; another must use a receiver supplied later. A third validates a whole route code rather than accepting a matching substring. These tasks revisit the unit without adding a new language feature. Trace separate instances separately, identify which object supplies this, and validate parsed data before returning it. Empty labels and repeated seeds are deliberate cases, because they expose assumptions hidden by ordinary examples. The finished utilities should return the requested values without depending on a specific fictional team name.