Overview
Lexum runtime is a deterministic execution engine responsible for:
- executing compiled bytecode
- scheduling domain transitions
- maintaining persistent state
- ensuring reproducibility
Design Principles
The runtime is built around:
- determinism
- isolation
- bounded execution
- replayability
High-Level Components
Lexum runtime consists of:
- Scheduler
- Interpreter
- Mailbox System
- State Store
- Journal
- Snapshot Manager
Component Diagram
text
+-------------------+
| Scheduler |
+---------+---------+
|
v
+-------------------+
| Interpreter |
+---------+---------+
|
+-------+-------+
| |
v v
+----------+ +-------------+
| Mailbox | | State Store |
+----------+ +------+------+
|
v
+-------------+
| Journal |
+------+------+
|
v
+-------------+
| Snapshot Mgr|
+-------------+
Execution Flow
- Scheduler selects message
- Interpreter executes transition
- State is updated
- Messages/effects are emitted
- Journal records execution
- Snapshot may be updated
Determinism Enforcement
Determinism is enforced at:
- scheduling layer
- interpreter execution
- state mutation
- persistence layer