A robot hasone battery,one CPU, andone chanceto get home.
CORES decides which cognitive modules run, in what order, and under what constraints. Every cycle. Deterministically.
It is not the robot's brain. It is the infrastructure that keeps the brain from burning out.
Read the architecture decisionsRuntime Status
LiveMission Utility
LexicographicThe stack is the interface.
Modules compose vertically. Each layer adds intelligence without breaking determinism. The runtime never knows which modules are loaded.
Lexicographic Scheduler
Multi-objective dispatch across safety, mission, and energy dimensions. Produces the one Pareto-optimal execution plan for each cycle.
Risk-Aware Knapsack
Energy-budgeted task selection modeled as a knapsack problem. Maximizes mission value within the available energy envelope.
Criticality Scheduling
Safety-critical modules receive bounded, non-preemptible execution slots with SIL-4 equivalent fault containment.
Runtime Foundation
Deterministic priority scheduler with O(1) dispatch and zero-allocation hot paths. Fixed-priority preemptive scheduling.
One robot. Four policies. Four outcomes.
Each policy implements the same trait. Swap it at construction. The runtime never knows the difference.
Priority
Criticality
Knapsack
Lexicographic
Failure is the input.
Twenty scenario families. Deterministic seeds. Every cycle is a new failure mode vector.
Hand-picked scenarios do not generalize. This generator spans every subsystem, then combines them. The same code drives 1000+ trial Monte Carlo workloads.
Monte Carlo Mode
The same ScenarioGenerator feeds 1000+ trial Monte Carlo workloads. Seeded RNG guarantees exact reproducibility.
Every cycle, measured.
Deterministic execution produces deterministic traces. Every tick is logged, measured, and accountable.