Result and EjError

Here is the single move that most separates Fusion code from slop. Domain validation never throws. It returns a Result<T>: either a success carrying a value, or a failure carrying a list of errors. The caller inspects the Result and decides what to do. No try/catch for expected, everyday validation failures.

An error is a small record. EjError has a Field (which part failed) and a Message (why). There are typed subtypes so a caller can branch on the KIND of failure, not on the message text.

public record EjError(string Field, string Message);

public sealed record EntityNotFound(string Field, string Message) : EjError(Field, Message);

public sealed record EjTimeout(string Field, string Message) : EjError(Field, Message);

Result<T> itself gives you IsSuccess / IsFailure, the Errors list, and a Value. Reading Value on a failed result throws, on purpose: it’s a programming error to look at a value that isn’t there, so it fails loudly rather than handing you a default. You construct results with the static Success and Failure factories.

public bool IsSuccess { get; }
public bool IsFailure => !IsSuccess;

public T Value => IsSuccess
    ? _value!
    : throw new InvalidOperationException("Cannot access Value on a failed Result. Check IsSuccess first.");

public static Result<T> Success(T value) => new(value);
public static Result<T> Failure(params EjError[] errors) => /* ... */;