Core Concepts
Philosophy
Kenate is built on one core belief: robotics code should be modular, not monolithic. We replace scripts with specialist behaviors.
The Atomic State Paradigm
Kenate represents a paradigm shift. It is the first framework to treat robotic behavior as a set of isolated, high-performance modules. By replacing "scripts" with "Atomic States," Kenate allows for the creation of autonomous systems that are modular by design and impossible to break by accident.
Definition: Atomic State
A behavioral module that performs exactly one task perfectly. Never build a State that does two major jobs. If a robot needs to move and clean, build two states.
Why Kenate?
Traditional robotic software relies on monolithic control loops. As systems evolve, these become "Spaghetti Logic"—endless chains of if-else statements. Kenate enforces a disciplined lifecycle: Init, Run, Analyze.
Core Principles
Modularity
Each behavior is a self-contained State class. You can add, remove, or modify states without affecting others. It's like Lego, but for robot brains.
Hybrid Performance
Write in easy Python; execute in high-speed C++. The 1000Hz Kernel ensures precise timing for smooth robot motion.
Determinism
The Heartbeat guarantees your code runs at exact intervals. No more 'jitter' or missed sensor readings. Predictable is professional.
The Watchdog Pattern
For production-grade autonomy, Euretix Labs recommends the Watchdog pattern.
# The Watchdog constantly monitors system health
class ThermalWatchdog(kenate.ThresholdState):
def on_update(self):
if self.get_system_temperature() > 85.0:
# Overrides ANY active mission state
self.engine.set_state("Safety")Always include a background state that monitors system vitals (heat, battery, signal).