A class can make domain decisions explicit by representing each permitted outcome as named data. In this role, it carries a name and attributes but no behavior, so readers can understand meaning without decoding arbitrary state assignments. section 1.3.2
Making retry decisions explicit
A ScheduledTask can store a RetryDecision status and assign concrete classes such as RetryImmediately, ReattemptLater, or Abandon. Scheduler code can then remove abandoned tasks with task.status() instanceof Abandon instead of inferring abandonment from scheduledAt == null.
Use classes to clarify the model when:
- A fixed set of decisions is hidden behind variable assignments. section 1.3.2


























