Learn UseCase Forge

UseCase Forge coordinates application work that has a lifecycle: it can be admitted or rejected, queued, started, cancelled, failed, completed, observed, and eventually closed. This guide starts with the smallest useful UseCase and then adds policies only when a concrete operational problem requires them.

Recommended path

1. Getting started — install the core package and execute one typed command.
2. Core concepts — understand command, execution, snapshot, result, and group identity.
3. Lifecycle — follow an accepted command from admission to finalization.
4. Policies — choose input and processing behavior deliberately.
5. Architecture — understand the responsibility boundaries behind the public API.

What this documentation does not assume

UseCase Forge is not a dependency injection container, a repository abstraction, or a replacement for domain modeling. It owns execution coordination. Your application continues to own business rules, persistence, navigation, presentation, and service boundaries.