Browse documentation
Actors, workflows and effects
How actors own state, workflows save progress and effects describe operations.
An actor owns state and handles messages. A workflow saves progress through an operation. Effects describe interactions; scoped grants and runtime checks determine which operations are allowed.
Concurrency, actors and async Rust explains scheduling, actor state during waits and integration with native async code.
Actors own domain state
Inventory can own stock and reservations. Checkout owns order progress and asks Inventory to reserve an item. It does not write Inventory’s state directly.
Checkout ── reserve request ──▶ Inventory
◀─ typed outcome ───
│
├── wait for approval
└── payment request ──────▶ Native adapter ──▶ Provider
Each arrow represents an interaction with a typed contract and permission checks.
An actor has an identity, mailbox and handlers. Its saved state can survive supported restarts. Several actors can run within one node; you do not need a separate service for each actor.
Workflows save progress
A workflow records the steps of an operation: submit, wait for approval, request payment. It resumes at supported points using saved state and history. An actor usually continues receiving messages; a workflow usually represents one operation.
Effects expose interactions
Calculating a price from supplied values runs in the core. Reading the clock or requesting payment uses an effect. The runtime can check and record that operation. Declaring it grants no permission; the runtime checks permission separately.
Code identities and test results
Source and dependency identities identify the selected code. Test evidence records the tested inputs and can be checked against later revisions.
Communication views show what code declares it may do, what it is permitted to do in a given context and what was observed during execution. A declared or permitted operation may never run. Read effects and authority for details.