Events & Operations

Define What Happens and What Can Be Done

A domain becomes operational when things happen and actions can be performed.

Operations describe what the system can do.

Events describe what happens within the domain.

Together, they provide a language for executable behavior.

Operations Express Intent

An operation represents an action that can be performed within the domain.

Create an order.

Approve a claim.

Assign a resource.

Sign a contract.

Process a payment.

Schedule a delivery.

The important question is not simply what code executes.

It is what the business means when that operation occurs.

Events Express Change

Events represent meaningful occurrences within the domain.

An order was created.

A payment was received.

A contract was signed.

A claim was approved.

A shipment was delivered.

Events allow the system to recognize that something significant happened and provide a foundation for further behavior.

Behavior Becomes Composable

Operations and events allow different parts of the system to react to meaningful domain activity.

Agents can respond.

Workflows can be triggered.

Integrations can be invoked.

Notifications can be generated.

Audits can be recorded.

Tests can verify expected behavior.

All of these can operate from the same definition of what happened and what can be done.

From Intent to Execution

The domain specification defines the meaning of an operation.

The rules determine whether it is permitted.

The transition defines how the domain changes.

The event records what happened.

The Kernel provides the execution foundation.

This connects business intent directly to executable behavior.

Define what can happen and what can be done, and the domain becomes executable.