Resolving Availability and Run-time Integrity Conflicts in Real-Time Embedded Systems

PAIR addresses a critical 'Fail-Secure vs. Fail-Operational' dilemma in safety-critical systems where traditional security measures (like stopping a process on violation) can lead to physical catastrophe (e.g., a drone falling out of the sky). The defensibility is currently low (3) because the project is an academic prototype with 0 stars and no community traction, making it a 'paper-to-code' artifact. However, the domain knowledge required to bridge Control Flow Integrity (CFI) with Worst-Case Execution Time (WCET) scheduling is substantial. Frontier labs (OpenAI/Anthropic) have zero interest in hard real-time micro-controller scheduling, making frontier risk low. The primary threat comes from established RTOS vendors like BlackBerry QNX, Wind River (VxWorks), or Green Hills Software, who could integrate similar scheduling-aware recovery mechanisms directly into their kernels. Displacement is unlikely in the short term as this research must first prove its industrial robustness, a process that typically takes 3-5 years in the embedded sector.