MiravoArchitecture
Trace the one-way Miravo runtime flow from authoring files to the scheduler, generators, asset graph, event bus, and protocol adapters.
Technical details
Follow the one-way flow
Miravo compiles content once. The runtime evaluates state on each tick. The same graph then feeds adapters, operator surfaces, and persistence.
Keep each subsystem narrow
The live WebSocket stream also carries runtime:tick messages with member deltas, core counters, and adapter metrics.
Adapters never compute member values. They project the graph they receive. Value generation stays in the runtime.
Reference
| Event or metric surface | Notes |
|---|---|
tick:complete | Carries { tick, simulationTime, graph, delta } |
instance:created / instance:removed | Structural lifecycle for runtime instances |
lifecycle:changed | Carries instanceId, stage transition, and operating hours |
fault:triggered / fault:cleared | Fault lifecycle events |
runtime:tick counters | memberValueCount, uptimeMs, actualTicksPerSecond, quarantinedInstanceCount, engineErrorsCount, tickOverrunsCount, circuitBreakerTripsCount |
| Adapter contract | Receives graph snapshots and publishes protocol-specific projections |
Related pages
Concepts
Authoring and runtime terms.
Persistence
Restart boundaries.
CLI ⭢ miravo status
Read live runtime state and metrics.
CLI ⭢ miravo logs
Stream events and runtime output.
Was this page useful?
Last updated on
Miravo AI skill
Turn any agent into a Miravo expert. Describe your use case in plain language, and let the Miravo AI skill turn it into Miravo models and environments.
Persistence
Restore structural runtime state across restarts from snapshots under `$MIRAVO_HOME/state/`, including environment identity and managed runtime data.