Dimitar Kretski

MicroSafe-RL - Adaptive control system for safe engine startup

byโ€ข
Proprietary Edge AI safety engine for Reinforcement Learning. Implements real-time Operational Stability Signatures to prevent hardware failure on microcontrollers (STM32/ESP32) - Kretski/MicroSafe-RL

Add a comment

Replies

Best
Dimitar Kretski
Maker
๐Ÿ“Œ
MicroSafe-RL started from a simple but critical question: **What happens when AI makes a wrong decision in the physical world?** In software, errors are tolerable. In embedded systems โ€” robotics, aerospace, industrial control โ€” they can cause real damage. I wanted a solution that doesnโ€™t rely on heavy models, cloud calls, or probabilistic guarantees. So I built a **deterministic safety layer** that runs directly on hardware. The goal was very specific: * sub-microsecond response * zero dynamic memory * mathematically predictable behavior During development, the approach evolved from a basic statistical filter into a **hybrid safety metric** combining: * real-time signal instability (ฯƒ / entropy) * deviation from learned baseline * dynamic response to sudden changes The result is a minimal, O(1) system that acts as a **shield between AI decisions and physical actuators**. Itโ€™s designed for environments where failure is not an option. Iโ€™m sharing it open for research and experimentation โ€” and Iโ€™m especially interested in feedback from people working in: * embedded systems * robotics * safe reinforcement learning * aerospace / industrial control Curious to hear how others approach safety at the edge.
Dimitar Kretski

AI works in simulation. Hardware doesnโ€™t forgive mistakes."When we launched MicroSafe-RL, we had one goal: to create a deterministic โ€œreflexโ€ for artificial intelligence. In industries like robotic surgery, critical chemistry, and autonomous drones, the latency of software protections is often the difference between success and disaster.๐Ÿ› ๏ธ The Tech Behind the ShieldMicroSafe-RL is not just another wrapper. This is a MISRA-C:2012 compliant interceptor designed for bare-metal systems: Ultra-fast: 1.18 $\mu s$ Worst-Case Execution Time (WCET) on Cortex-M3. Minimalistic: Consumes only 24 bytes of RAM โ€“ less than one TCP packet. Deterministic: $O(1)$ complexity, ensuring safety in every control cycle. ๐Ÿ”ฌ Scientific Validation ("Paper Mode") For this "Launch", we also released our Paper Mode benchmarks, which prove our superiority over industrial PLC systems: 240% greater margin: We achieve an average detection margin of $19.20 \pm 1.54$ steps compared to only $8.14 \pm 0.90$ for traditional threshold systems. Reliability: We maintain an extremely low False Positive Rate (0.05), eliminating unnecessary interruptions to the workflow. Zero overlap: The distribution of our latency shows complete separation from classical methods, ensuring a response window even for the noisiest signals.๐ŸŒ Real-World ImpactWhether it's preventing thermal "runaway" in a chemical reactor or stopping a "hallucinating" robotic limb, MicroSafe-RL provides the time physics needs to stay within safe limits. Check out our GitHub for the full documentation and Paper Mode analyses! We'd love to hear your feedback and technical questions! ๐Ÿ›ก๏ธ๐Ÿš€๐Ÿ†#EdgeAI #Robotics #SafetyFirst #EmbeddedSystems #MicroSafeRL #MISRAC

Dimitar Kretski

Hi everyone ๐Ÿ‘‹

This project started from a simple question:
What if embedded systems could adapt instead of just fail or switch to backup?

We built ORAC โ€” an adaptive fault-tolerant control system.

๐Ÿ”ง What it does:

  • Detects faults (e.g. SEU / drift)

  • Re-routes workload across nodes

  • Recovers automatically

๐Ÿ“Š In our simulation:

  • Node failure injected mid-run

  • System stabilized without collapse

  • No data loss

Would love your feedback โ€” especially from control / embedded engineers.