Processes

Processes describe how semantic processes are arranged across time, observers, entities, and external systems.

A process may be a domain process, saga, process manager, durable workflow, orchestration, choreography, operational procedure, transaction, runtime operation, scheduler-managed logical process, or resumable maintenance procedure. The model treats it as structure when it gives coherence to a series of related observations, commands, events, transitions, decisions, effects, and artifacts. This describes coordination shape and participant roles, not the workflow engine, scheduler, transaction manager, application host, or operating-system mechanism that realizes it.

Business Transactions are domain-level process structures whose progress, acceptance, rejection, compensation, or completion matters to the business. They may use one process or several cooperating processes.

Processes may maintain their own process state and may coordinate several participants without making every participant part of one transaction.

A process may be modeled as a special kind of entity and observer when it has its own identity, durable state or history, and rules for interpreting incoming events, signals, or commands over time.

Processes have flows. A flow describes how process inputs, outputs, signals, observations, commands, events, effects, or artifacts move between participants. Flow is therefore a useful view of process movement, but it is not the whole process. The process also includes subject identity, participant roles, state, decisions, policies, transitions, recovery, compensation, and completion meanings.

Process concerns include:

The subject or correlation identity.
Participant observers and entities.
Current process state.
Steps, decisions, and transitions.
Inputs, outputs, effects, artifacts, and movement paths.
Compensation or recovery behavior.
Delivery and retry expectations.

Examples include:

OS processes and OS threads executing work across one or more scheduling units.
Logical processes spanning fibers, green threads, coroutines, or runtime tasks.
ASP.NET operations that perform multiple steps, possibly wrapped by durable execution.
Driver onboarding, coordinated across entity state transitions, runtime listeners, effect emitters, concurrency control, UI activity, and durable step advancement.
Index rebuilds, backfills, data repairs, and migrations that must resume after a crash.
Sagas whose selected steps have compensating actions.
RDBMS transactions that attach ACID commit and rollback semantics to database operations.
ML workflows that normalize training examples, generate or project datasets, run models, transform and persist model artifacts, evaluate outcomes, and promote selected models.

Processes compose when outputs of one process feed another process as observations, commands, events, artifacts, or decisions. Such compositions may be pipelines, nested sub-processes, concurrent processes, or feedback loops.