Mobile energy must behave like infrastructure.
Dispatchable charging is useful only when the network can discover demand, qualify sites and equipment, reserve capacity, support the asset, reconcile measured delivery and preserve an accountable record. FE-OS coordinates those responsibilities without pretending to own every vehicle, charger, site or provider.
Proposal before execution.
NormalizeTranslate consented inputs into a versioned snapshot.
ProjectEstimate depletion, timing and common need; reject stale inputs.
MatchEvaluate capability, corridor, ETA, authority and site constraints.
ExplainReturn a deterministic proposal or no-dispatch reason.
ApproveRequire fleet, operator, site, equipment and commercial gates.
RecordPersist evidence and corrections without silent overwrite.
The core does not directly command machinery.
The current architecture cannot issue governor, CAN/Modbus, charging, rerouting, reservation, billing or payment commands. Provider adapters remain separately authorized, scoped, revocable and observable.
One transaction identity across operations.
| Layer | Responsibility | Evidence |
|---|---|---|
| Demand | Fleet need and energy objective | Consented request |
| Supply | Asset capability and reserve | Operator record + fresh telemetry |
| Place | Authority, circulation and safety | Verified-site policy |
| Execution | Mission and state transitions | Signed events + audit |
| Commerce | Delivery, tax and settlement | Commercial meter + ledger |
| Uptime | Technician, parts and support | Repair order + evidence |