JSON Patch / review handoff
Review JSON Patch targets without misreading the pointer
Check add, replace and remove beside their JSON Pointer target. A valid patch remains a review proposal until the target document and intent are confirmed.
Put operation, target and decision together
Split each patch row into operation, path, before/after values and next decision. Resolve the pointer against the expected target document.
| Operation | Pointer | Before → after | Decision |
|---|---|---|---|
| add | /profile/role | missing → reviewer | Review add intent |
| replace | /profile/name | A → Alice | Review replace intent |
| remove | /obsolete | remove-me → missing | Review remove intent |
| replace | /profile/unknown | target missing | Stop on mismatch |
Read a patch as a proposal
The three operations in patch.json describe the intended move from before.json to after.json. mismatch.json points to a missing path, so it is not applied even though its syntax is valid.
op: replace
path: /profile/unknown
result: target mismatch
decision: block-target-mismatch
Hold the patch until the target document, schema, intent and receiver contract are confirmed.
Review before applying
- Freeze the expected before document and keep it beside the proposal.
- Resolve every path as a JSON Pointer against that document.
- Confirm the intent and before/after values for add, replace and remove.
- Stop on a pointer mismatch or unexpected value; do not apply the patch.
- Record the reviewer, target document and receiver schema before handoff.
This guide is static browser-local material. Input, files and validation results are not sent to or stored by an external service.
Valid syntax is not success
A JSON Patch can parse correctly while its pointer targets another document, its expected value is wrong, or its intent is unclear. Treat a target mismatch as a review failure.