1. Tickless idle
The current EoS scheduler uses a 1 ms tick interrupt. This prevents the CPU from entering deep sleep for more than 1 ms, wasting power on battery devices. The 2026 tickless scheduler programs the RTC to wake the CPU only when the next task deadline arrives. On a typical IoT workload (1 Hz sensor read, 10 Hz display update), this reduces idle power from 8 mA to 0.4 mA — a 20× improvement.
2. RT-IPC across security domains
Today, eIPC uses copy-based message passing across MPU domain boundaries. For high-bandwidth use cases (neural data, video), copy overhead is prohibitive. RT-IPC introduces a shared-memory window with hardware-enforced read/write permissions: the producer domain has write access, the consumer domain has read access, and neither can access the other's private memory. This enables zero-copy neural data transfer at 61 MB/s.
3. Formal verification of the context switch
The context switch is the most security-critical code in any RTOS. A bug here can corrupt task state, leak secrets across security domains, or enable privilege escalation. We are using TLA+ to specify the context-switch state machine and Coq to prove that the implementation matches the spec. The verified context switch will ship in EoS 2.0.
What's not on the list
We are explicitly not adding a POSIX compatibility layer, a dynamic linker, or a general-purpose memory allocator in 2026. These features would increase the kernel's attack surface and binary size. EoS remains a purpose-built embedded RTOS, not a general-purpose OS.