service-use-case-boundary

name	service-use-case-boundary
description	Keep business use cases in services and keep runtime/UI concerns outside them
metadata	{"type":"Reference","origin":"harness-engineering/ch7","helpful":0,"harmful":0,"status":"active"}

Service Use-Case Boundary

Rules

1. Services express use cases and business decisions.
2. Services can coordinate repositories and providers.
3. Services must not import HTTP framework, UI, or route-handler types.
4. Services return domain results or application errors, not HTTP responses.

Checklist

• Route handlers contain no business-rule branches
• UI never calls repositories directly
• Services are unit-testable without HTTP or browser runtime
• Provider side effects are injected or wrapped by interfaces