← Latest papers
🤖 AI

Safe and Adaptive Cloud Healing: Verifying LLM-Generated Recovery Plans with a Neural-Symbolic World Model

This paper introduces PASE, a neuro-symbolic self-healing framework that unifies LLM-based plan synthesis, neural-symbolic world model verification, and DRL-driven prompt optimization to significantly reduce cloud system recovery time and improve fault detection accuracy compared to existing methods.

Original authors: Junyan Tan, Haoran Lin, Siyuan Guo, Yichen Fang, Xinyue Luo, Tianyu Shen, Zeyu Qiao

Published 2026-07-03
📖 4 min read☕ Coffee break read

Original authors: Junyan Tan, Haoran Lin, Siyuan Guo, Yichen Fang, Xinyue Luo, Tianyu Shen, Zeyu Qiao

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a massive, bustling city made entirely of digital services (like cloud servers). Sometimes, parts of this city break down—a traffic light fails, a power line snaps, or a building catches fire. In the past, fixing these problems was like having a team of firefighters who only knew a few specific moves: "If the fire is here, spray water there." If the fire was in a weird new spot, they were stuck.

This paper introduces a new system called PASE (Planning-Aware Semantic self-hEaling engine). Think of PASE not as a firefighter with a single hose, but as a super-smart city planner, a safety inspector, and a coach all rolled into one.

Here is how PASE works, broken down into three simple roles:

1. The Super-Planner (The LLM)

In old systems, the computer just looked at a broken part and picked the next move from a short list of pre-written options.
PASE is different. It uses a Large Language Model (LLM)—basically a very advanced AI that reads and understands language like a human. When something breaks, PASE doesn't just pick a move; it writes a whole story on how to fix it.

  • The Analogy: Instead of just saying "Turn left," the planner says, "First, isolate the broken street, then send a backup crew to the next block, and finally reroute the traffic." It can invent new, multi-step plans for problems it has never seen before.

2. The Safety Inspector (The Neural-Symbolic World Model)

Here is the tricky part: Sometimes, even a super-smart planner can get things wrong. It might suggest a plan that sounds good but would actually cause a bigger disaster (like trying to fix a power outage by turning off the backup generator).
PASE has a built-in safety inspector. Before the plan is actually executed in the real city, this inspector runs a simulation.

  • The Analogy: Imagine the planner draws a blueprint for a new bridge. Before they pour any concrete, the inspector runs a computer simulation to see: "Will this bridge hold? Will it collapse in a storm?" If the simulation says "No, this is risky," the plan is thrown out. This stops the system from making dangerous mistakes.

3. The Coach (The Meta-Prompt Optimizer)

Even the best planners can get stuck or write confusing instructions.
PASE has a coach that watches how well the planner is doing. If the planner keeps making bad plans, the coach doesn't rewrite the whole planner (which takes too long). Instead, the coach gives the planner a better set of instructions (a "prompt") to help it think more clearly.

  • The Analogy: Think of a chess player. If they keep losing, you don't replace their brain. You give them a new tip: "Remember to protect your king first." The coach learns these tips automatically through trial and error, helping the planner get smarter and faster at fixing new types of problems.

How They Work Together

The paper describes a tight loop:

  1. Reason: The system looks at the mess (logs, errors, alarms) and describes the problem.
  2. Plan: The Super-Planner writes a step-by-step fix.
  3. Verify: The Safety Inspector simulates the fix to make sure it's safe.
  4. Adapt: The Coach tweaks the instructions for next time to make the planner even better.

The Results

The authors tested this on a real-world cloud system that they intentionally broke (fault injection).

  • Speed: PASE fixed problems 40% faster than the best existing methods.
  • Smarts: It was much better at figuring out why things broke and creating custom solutions for weird, new types of failures that old systems couldn't handle.
  • Safety: Because of the Safety Inspector, it rarely tried dangerous fixes.

In short, PASE moves cloud repair from a rigid "press button A if light B blinks" approach to a flexible, thinking approach where the system plans, checks, and learns its way out of trouble, just like a human expert would.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →