Goal
Keep AI code changes inspectable through context, previews, diffs, and restoration.
Step-by-step
- State the edit scope.
- show proposed changes.
- separate apply from execute.
- verify and retain a recovery point.
Worked scenario
Review an edit diff before applying a suggested refactor.
Write down the current behavior, the intended change, and the evidence you would need before deciding it worked. Use synthetic or anonymized material for exploration.
Acceptance check
A generated patch does not run unreviewed commands or erase unrelated code.
Common failure
A convincing artifact can hide untested assumptions. Keep an explicit list of unknowns and test the highest-consequence transition before expanding the work.
Next step
Apply the guide to one bounded task, review the evidence, and adjust the approach. The linked reference is a separate publication; this guide is Knoveya's independent treatment of the topic.