Poison Valleys

Code-repair trajectories

Where did a code repair go wrong?

A final test can tell us that a patch failed. Poison Valleys follows the path backward—from violated software obligations to the earlier misconception that shaped the repair.

Try the demo Code and data
Poison Valley trajectory Five stages trace a repair from observation through dependency context, hypothesis, plan, and code.
  1. 00ObservationWhat the agent sees
  2. 01Dependency ContextWhat informs the repair
  3. 02HypothesisWhat the agent believes
  4. 03PlanWhat it commits to doing
  5. 04CodeWhat the patch implements

Package version 0.2.4

Download reviewer artifact

SHA-256 54b3ad458cffd329f93d21e4f48326fec0ccd74cb5b04870bc005e63dc855e7d