Daily Digest
Check each tool step before next
Check each step's result so one bad step doesn't spoil the run.
The technique
A bad tool step that continues quietly poisons the rest of the trajectory. After each call, run four checks: does it advance the task, do used args match declared args, was execution valid, and were constraints satisfied. On fail, emit structured feedback and stop for replan instead of always-continuing into cascade.
How it was tested
Offline structural sim (no live model): 8 trajectories. Stop-on-fail matched all 8 expected run lengths; blocked 6 cascades that naive always-continue completed. All four check dimensions fired on a deliberately broken step.