When a dependency is unavailable, return a reduced result or skip optional work only if the use case can still preserve its domain invariants. Keep availability handling at the boundary: the domain receives a validated value, a refusal, or DependencyUnavailable without changing its rules. section 11.5
Choose the failure behavior according to what the use case requires:
- For optional information, use a cached value, omit it, or move the work off the synchronous request path. section 11.5
- For information that gates a domain decision, do not guess or bypass the check; return DependencyUnavailable and let the caller retry. section 11.5
- Bound required synchronous calls with chosen timeouts, safe retries, and fast failure; a circuit breaker can stop repeated calls and allow a probe after cooldown. section 11.5


