Timing constraints are independent: task, reaction, sequence.
The framework must pass three independent timing checks: local task deadlines, the end-to-end response budget, and the minimum dwell time between reconfigurations.
Task, reaction, sequenceExpand section
Task, reaction, sequence
The framework must satisfy three different timing requirements: task schedulability, the end-to-end fault response budget, and the minimum interval between repeated reconfigurations.
θ + R_dec + t_hot ≤ t_max(mode)
Δt_reconf ≥ τd
What was obtained for the reference implementationExpand section
What was obtained for the reference implementation
For the framework task set, the total utilization is U = 0.396 with the bound at 0.735, and the worst response-time ratio R/D is only 0.176. The task set is therefore schedulable with a healthy reserve.
The end-to-end response consists of detection, decision and hot switching. The baseline result is t_reaction = 82.30 ms, while the best achievable value after optimization is 54.80 ms.
The bottleneck is not DecisionEngine but switchingExpand section
The bottleneck is not DecisionEngine but switching
The key conclusion is that the limiting factor is not configuration selection but the transition mechanism t_hot. To satisfy the DEGRADED-mode requirement, hot switching must be reduced to t_hot ≤ 30.2 ms.