Evaluating Revera¶
This directory evaluates Revera against the criteria an engineer weighs when choosing a real-time operating system — determinism, footprint, multicore, isolation, safety, tooling, licensing. It is written for a prospective adopter deciding whether Revera fits a specific project.
How to read each axis. Every file follows the same shape: the generic criterion (what to look for), how Revera answers it (honest prose), a feature → how-to table (each capability, the config knob that turns it on, the exact API symbols to call, and the architectures it works on), and limits & roadmap. The tables answer “I know Revera does X — how do I use it?” with API pointers; follow them to the API reference for full detail. Where Revera is minimal or a feature lives only in the project’s history, the axis says so plainly — that honesty is the point.
The differentiator¶
Memory Protection & Isolation — hardware-enforced per-thread and per-island memory fencing that binds even the kernel. Revera’s headline; start here.
Core kernel¶
Scheduler and Task Management — preemptive fixed-priority, round-robin, optional EDF.
Multi-Core Architecture Support — SMP and AMP on one portable core.
Inter-Task Communication and Synchronization — semaphores, PI mutexes, condition variables (queues/event-flags are roadmap).
Interrupt Handling and Synchronization — deferred processing, priority inheritance.
Memory Management and Footprint — static allocation, no heap, a measured footprint.
Portability, configuration, ergonomics¶
Hardware Abstraction and Portability — 10 arch ports, 14 boards (peripheral breadth is roadmap).
Configuration Flexibility and Modularization — compile-out knobs, profiles, fail-loud.
Standardization and API Ergonomics — a pthread-shaped compatibility subset.
Ecosystem, Tooling, and Observability — trace ring, SystemView, post-mortem, hooks.
Product & assurance¶
Safety, Security, and Compliance — no certs in 0.1.0; a substantial HW-proven security/safety plane in the project’s history.
Connectivity and Protocol Stacks — no networking stack in 0.1.0 (an honest gap).
Commercial and Licensing Lifecycle — dual-licensed (PolyForm Noncommercial + VIACERTO commercial), 100%-owned.
Per-feature, per-architecture maturity (proven-on-hardware vs emulator vs implemented) lives in the readiness dashboard. This evaluation is a work-in-progress adopter’s view; it is reconciled against the shipped 0.1.0 product, not a marketing overlay.