Crate Index

EnerOS consists of 56 Rust crates divided into 10 functional categories. All crates share the unified types and error model provided by eneros-core, ensuring cross-module type consistency and zero-copy transfer. The entire project is organized as a Cargo workspace with a single version number (currently 0.47.0) released in unison, avoiding submodule version drift.

Design Principles

EnerOS’s crate partitioning follows these principles:

• Single Responsibility: Each crate handles only one clear domain, facilitating independent testing and replacement
• Unidirectional Dependencies: Dependencies flow only from upper to lower layers; circular dependencies are forbidden, and compilation order is deterministic
• Zero-Copy Transfer: Cross-crate data transfer uses Arc<T> / &T, avoiding serialization overhead
• Feature Granularity: Each crate exposes optional capabilities through Cargo features, enabled on demand to reduce binary size
• Tiered Stability: Core layer APIs are marked stable, power kernel marked beta, application layer marked experimental

Category Overview

A total of 56 crates, with category counts matching the release manifest.

Dependency Graph Overview

┌─────────────────────────────────────────────────────────────┐
│  Application Layer                                           │
│  eneros-dashboard  eneros-api  eneros-edge  eneros-3d        │
└─────────────────────────────────────────────────────────────┘
                          ↓
┌─────────────────────────────────────────────────────────────┐
│  Agent Runtime                                               │
│  eneros-agent → memory / tool / reasoning / ai               │
└─────────────────────────────────────────────────────────────┘
                          ↓
┌─────────────────────────────────────────────────────────────┐
│  Power-Native Kernel                                         │
│  topology → powerflow → constraint → equipment → timeseries  │
│                          eventbus                            │
└─────────────────────────────────────────────────────────────┘
                          ↓
┌─────────────────────────────────────────────────────────────┐
│  Core Layer                                                  │
│  eneros-core (unified types)    eneros-linalg (sparse matrix)│
└─────────────────────────────────────────────────────────────┘
                          ↓
┌─────────────────────────────────────────────────────────────┐
│  Infrastructure                                              │
│  eneros-os  eneros-gateway  eneros-device  eneros-scada      │
│  eneros-trust  eneros-audit  eneros-ids  eneros-compliance   │
└─────────────────────────────────────────────────────────────┘

Dependencies flow strictly top-down; lower layers are unaware of upper layers. For the detailed dependency matrix, see the Crate Dependencies page.

Core Crate Details

The table below lists the 10 most critical crates of EnerOS, corresponding to the 10 documents that follow in this chapter:

Complete Crate List

Core Layer (2)

Power Kernel (7)

Agent Runtime (5)

Infrastructure (8)

Protocol Adapters (8)

Analytics (4)

Security (4)

Operations (5)

Visualization (4)

i18n & Plugins (9)

Cargo Workspace Organization

EnerOS uses a single Cargo workspace to manage all 56 crates. The root Cargo.toml excerpt is as follows:

[workspace]
resolver = "2"
members = [
    "crates/core",
    "crates/linalg",
    "crates/topology",
    "crates/powerflow",
    "crates/constraint",
    "crates/equipment",
    "crates/cnpower",
    "crates/timeseries",
    "crates/eventbus",
    "crates/agent",
    "crates/memory",
    "crates/tool",
    "crates/reasoning",
    "crates/ai",
    "crates/os",
    "crates/gateway",
    "crates/device",
    "crates/scada",
    "crates/network",
    "crates/bridge",
    "crates/runtime",
    "crates/perf",
    "crates/protocol-cdt",
    "crates/protocol-coap",
    "crates/protocol-dlt698",
    "crates/protocol-iccp",
    "crates/protocol-iec103",
    "crates/protocol-lwm2m",
    "crates/protocol-mqtt",
    "crates/protocol-pmu",
    "crates/analysis",
    "crates/emtp",
    "crates/twin",
    "crates/simulator",
    "crates/trust",
    "crates/ids",
    "crates/audit",
    "crates/compliance",
    "crates/slo",
    "crates/aiops",
    "crates/ops",
    "crates/multiregion",
    "crates/tenant",
    "crates/dashboard",
    "crates/3d",
    "crates/nl",
    "crates/report",
    "crates/i18n",
    "crates/plugin",
    "crates/plugin-macros",
    "crates/sdk",
    "crates/edge",
    "crates/iot-hub",
    "crates/graphql",
    "crates/api",
    "crates/test-utils",
]

[workspace.package]
version = "0.47.0"
edition = "2021"
license = "Apache-2.0"
repository = "https://github.com/Gawg-AI/EnerOS"

[workspace.dependencies]
eneros-core = { path = "crates/core", version = "0.47.0" }
eneros-linalg = { path = "crates/linalg", version = "0.47.0" }
eneros-topology = { path = "crates/topology", version = "0.47.0" }
serde = { version = "1.0", features = ["derive"] }
tokio = { version = "1", features = ["full"] }
tracing = "0.1"
thiserror = "1.0"

Crate Selection Guide

Version and Compatibility

All EnerOS crates share the 0.47.0 version number, following semantic versioning:

• 0.x.0: Minor versions released quarterly, allowing API breaking changes; migration guides provided with release notes
• 0.47.x: Patch versions released weekly, containing only bugfixes and non-breaking new APIs
• LTS versions: Released annually, providing 3 years of security updates

Compatibility matrix:

Performance Overview

EnerOS end-to-end performance under standard test environment (4 cores / 8GB / Ubuntu 22.04):

Related Documentation

• Crate Dependencies — Dependency hierarchy details
• Project Structure — Directory layout
• Layered Architecture — Architecture layering design
• eneros-core — Start with the root crate to understand the type system