When the service objects from ~a dozen developer articles are measured against the combined 'service ruler' (stateless; named for an activity; represents a business operation; coordinates domain objects; controls transactions; SRP-compliant; has side effects; no application logic), almost none satisfy all criteria. Book creators, discount-code validators, tweet creators and trip updaters fail the activity-name test, SRP, or stateless criteria. Even an authentication service with clear 'single purpose' wording violates SRP because SRP is about a single reason to change, not a single topic. Therefore the same bucket — 'service object' — is used for many unrelated kinds of code.