Browse documentation
From Elixir or Erlang
Map state owners, messages and workflows to the Septa runtime.
Septa actors own state and receive messages through typed handlers. Their identity and saved state can outlive the process executing them. The source is Rust within a supported profile.
Familiar concepts
| Concept | Septa meaning |
|---|---|
| State owner | A durable actor with identity, mailbox and handlers |
| Cast | A message without a typed reply |
| Call | A request with a typed reply |
| Workflow | An operation with retained progress and supported resume points |
| Inspection | State and execution views tied to source and retained history |
Run the counter. Every CLI command starts a fresh process; the state directory connects them.
Authority is explicit
A valid message type does not grant permission to send it. Scoped grants and runtime admission govern the caller, operation and target. A typed capability handle alone supplies no authority.
Replies belong to their request. A reply does not authorize the responder to initiate unrelated operations on the caller. See effects and authority.
Check each runtime contract
Actor vocabulary does not imply BEAM compatibility. Supervision, distribution, selective receive, reentrancy and shutdown each need their own supported contract. Local actor boundaries also do not require separate deployments.
Durability follows the storage and recovery contract. External services retain their own retry and idempotency rules. Start with durable execution, then design a boundary for one stateful responsibility.