Review and apply proposed changes
Inspect a Lemon Code proposal against its Harness Draft and your intended behavioral change.
Prerequisites
A Harness conversation with a proposed file change and the context that motivated it.
Steps
- Read the proposed diff and rationale alongside the current Draft.
- Check which files and behavior change, and which requirements the intervention needs to preserve.
- Continue the conversation to refine the proposal. Apply only the changes you choose to accept into the Draft.
- Validate the revised Draft as needed, then publish an exact Version. Select that saved Version for any debug run, and evaluate it against the intended Benchmark Version.
Object and state changes
Applying changes edits the Draft. Publishing and benchmark execution create separate saved records; your engineers decide what to integrate into their application.
Success criteria
The saved candidate contains the reviewed changes and its assessment addresses the original objective and protected behavior.
Common failure modes
Applying a proposal without inspecting its file scope; treating a plausible explanation as measured improvement.