← Latest papers
🤖 AI

Evidence Over Plans: Online Trajectory Verification for Skill Distillation

This paper introduces SPARK, a framework that utilizes the Posterior Distillation Index (PDI) to verify and distill agent skills directly from environment-grounded trajectory evidence rather than prior plans, resulting in efficient, transferable skills that outperform human-written baselines across diverse tasks.

Original authors: Yang Zhou, Zihan Dong, Zhenting Wang, Can Jin, Shiyu Zhao, Bangwei Guo, Difei Gu, Linjun Zhang, Mu Zhou, Dimitris N. Metaxas

Published 2026-05-12
📖 4 min read☕ Coffee break read

Original authors: Yang Zhou, Zihan Dong, Zhenting Wang, Can Jin, Shiyu Zhao, Bangwei Guo, Difei Gu, Linjun Zhang, Mu Zhou, Dimitris N. Metaxas

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 you are trying to teach a new apprentice (the "Student" AI) how to fix a complex machine. You have two ways to write the instruction manual:

  1. The "Plan" Approach: You sit down and write a manual based on what you think should happen. You guess the steps, the tools needed, and the order of operations. This is like writing a recipe for a cake you've never actually baked.
  2. The "Evidence" Approach: You watch an expert (the "Teacher" AI) actually try to fix the machine. They might fail three times, break a part, realize their mistake, and finally succeed on the fourth try. You then write the manual based only on the specific actions that worked and the specific mistakes they avoided.

This paper argues that Approach #2 is vastly superior, but only if you can tell the difference between a "good" manual and a "bad" one.

The Problem: Guessing vs. Knowing

The authors noticed that most AI systems today try to create "skills" (instruction manuals) by guessing what the solution should be before they even touch the machine. They rely on "prior plans."

The problem? These plans often fail because they don't account for the messy reality of the environment. The manual says "turn the red knob," but in the real machine, the red knob is stuck, and you actually need to wiggle the blue lever first. If the manual is just a guess, the apprentice will fail.

The Solution: SPARK and the "Posterior Distillation Index" (PDI)

The researchers built a system called SPARK (Structured Pipelines for Autonomous Runnable tasKs and sKill generation). Think of SPARK as a high-tech film crew that records the expert's entire journey, including all the failures.

But recording isn't enough. You need a way to judge if the resulting manual is actually good. That's where PDI comes in.

PDI is like a "Truth Detector" for instruction manuals. It asks three simple questions:

  1. Did they actually do it? (Execution Grounding): Does the manual describe actions that were verified to work in the real world?
  2. Did they just copy their own bad guesses? (Plan Copying): Does the manual just repeat the expert's initial, unproven ideas? (PDI wants this to be low).
  3. Did they get stuck in a loop? (Memo Ossification): Did the expert keep trying the same failed strategy over and over, or did they learn and adapt? (PDI wants this to be low).

If a manual scores high on PDI, it means it's built on hard evidence (what actually worked) rather than soft guesses (what they hoped would work).

The "Aha!" Moment: Online Intervention

Here is the clever part. Usually, you only check if a manual is good after it's written. But SPARK uses PDI as a live monitor.

Imagine the expert is trying to fix the machine. SPARK is watching their "thought process" (their notes). If the system sees the expert starting to repeat the same mistake or sticking to a plan that isn't working (a low PDI score), it intervenes immediately. It whispers to the expert: "Hey, that strategy isn't working. Try a completely different angle."

This ensures that the final manual is distilled from a successful, adaptive journey, not a stubborn failure.

The Results: Small Students, Big Wins

The researchers tested this by having a "Teacher" AI (a very smart, expensive model) explore tasks and generate these PDI-verified manuals. Then, they gave these manuals to "Student" AIs (smaller, cheaper, less powerful models).

The results were surprising:

  • The Students beat the Teachers: In many cases, the small Student AI, armed with the PDI-verified manual, performed better than the powerful Teacher AI did without any manual at all.
  • Cheaper is Better: The Teacher AI is expensive to run (like hiring a senior engineer for a week). The Student AI is cheap (like hiring a junior intern for an hour). SPARK lets you pay the senior engineer once to figure out the evidence, then let the cheap intern do the work a thousand times.
  • Better than Human Manuals: The SPARK-generated manuals actually outperformed manuals written by human experts. Why? Because humans often write based on general knowledge (prior plans), while SPARK writes based on specific, verified trial-and-error (posterior evidence).

The Bottom Line

This paper proves that for AI to learn truly useful skills, it shouldn't just "think" about how to solve a problem. It must do the problem, fail, learn, and succeed. The resulting "skill" must be a distillation of that real-world evidence, not a theoretical plan.

By using the PDI score to filter out bad plans and guide the learning process in real-time, SPARK creates a library of skills that allows even small, cheap AI models to perform complex tasks with the reliability of a much larger, smarter system.

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 →