Edit reviews and add notes
Correct proposal fields while preserving the difference between changes and commentary.
Use the review's editable fields to correct a saved proposal. An App can expose text, boolean, and date leaves, including selected fields within arrays. Other payload fields remain preserved, so inspect the full saved content before making a final decision.
Edit a proposal
Check the current revision and source basis. Change the relevant field, save, and inspect the recorded result. An edit returns the review to pending even if it was previously approved. The changed proposal needs a new decision.
Unsaved edits are not the same as a saved event. They can also clear a displayed dated projection because the on-screen draft no longer matches the saved basis used for that projection. Save deliberately, then refresh the relevant view.
Change source links
Relinking a source changes the review basis and returns the review to pending. Capture the selected source set again as required before approval. Reusing a familiar filename does not prove the file has the same contents as the earlier source.
Add a note
A note records commentary without replacing the proposal or changing its decision status. Use it to explain a review choice, record a question, or describe follow-up work. A note is not a way to change the approved value without resetting approval.
If a supposed “note” materially changes the conclusion, edit the proposal instead and require renewed review. Keep the history readable for the next person inspecting it.
Stale or uncertain saves
A conflicting revision means your view is no longer current. Reload, compare the saved payload and history, then make a new deliberate edit. If a save's outcome is uncertain, use the original retry path or inspect the persisted event before issuing a different change.