A command such as `void handle(SomeCommand)` promises no return data, but says nothing about failure. When exceptions are its only failure channel, expected outcomes remain invisible to callers. section 4.0 section 4.2
Reserve exceptions for faults the application cannot reasonably model or recover from, such as programming errors or infrastructure failures. Put expected contingencies in the use-case contract as typed outcomes, such as `Either<Error, R>`. section 4.0 section 4.2.1
Contingencies and faults
A duplicate email, missing article, or rejected authorization is an expected outcome a caller can react to. Corrupted state or an unrecoverable runtime problem may remain exceptional. section 4.2.1




























