Backend
Keeping Shielded Data-Driven Controllers Safe Under System Evolution via Model Consistency
arXiv cs.SY0 views
arXiv:2611.24428v1 Announce Type: new Abstract: Cyber-physical systems (CPS) increasingly contain data-driven controllers, which raise safety concerns given their black-box nature. A common mitigation is to enforce system safety via a shield around the controller, which restricts the inputs based on assumptions about the physical system. However, these assumptions are usually fixed and may become invalid as the system evolves (during development or due to component degradation), possibly leading to unsafe behavior. We address this limitation in a model-driven approach that treats both the data-driven controller and safety shield as first-class models that are integrated into a virtual single underlying model (V-SUM) alongside system models. We describe system evolution as changes in the associated models, such that consistency checking yields a continuous assessment of safety guarantees. In case of inconsistencies, consistency-preservation rules automatically update the models and restore a valid safety shield. We evaluate our approach on a reach-avoid task for a unicycle system. The results show that consistency-driven evolution effectively maintains safety guarantees under system changes and provides a principled basis for evaluating and restoring performance.
Source:https://arxiv.org/abs/2611.24428PreviousLaguerre-MPPINextN-1 Security constrained Hosting Capacity Assessment for Ultra Large-scale Data Center with Workload Flexibility
Related posts

Signal is blocking Gemini and Siri AI from reading your screen
0The Verge
12 Paid Calls, 0 Answers: A Contract That Says Every Field Is Optional
0dev.to
Auditing a WooCommerce checkout from the shell before Black Friday
0dev.to

Fix Kubernetes CrashLoopBackOff in k3s: A Debug Guide
0dev.to
Four columns that stop a size-ambiguous furniture inquiry from being priced wrong
0dev.to
Wi-Fi Calling where there is no cellular signal: what the phone, ePDG and IMS do on the call path
0dev.to