JSON / semantic review

Separate formatting and semantic JSON changes for review

Classify whitespace and object-key-only differences separately from value, type and array-order changes. Keep a JSON Pointer and review action for every meaningful difference.

Open JSON diff

Use four classifications

Parse both documents first. When only whitespace or object-key order differs and parsed values are equal, the difference is formatting-only. Classify the other changes separately.

Pointer	Observed difference	Classification	Next decision
/	Whitespace and object-key order	Formatting-only	No review for this difference
/version	1 → 2	Value change	Review intent
/enabled	true → "true"	Type change	Review receiver type
/items	b before a	Array order	Confirm the order contract

Separate formatting from meaning

format-before.json and format-after.json differ in whitespace and key order, but their parsed values are equal. The semantic pair gives separate review reasons for value, type and array-order changes.

/version  1 → 2          value
/enabled  true → "true"   type
/items    [a,b] → [b,a]   array-order

Whether array order matters belongs to the receiver's contract. Do not mark a reorder safe automatically.

Review before handoff

Parse both documents and do not confuse whitespace or object-key order with meaning.
Record a JSON Pointer, observed values and classification for each change.
Check intent and receiver schema for value and type changes.
Confirm the array-order contract; hold the change when it is unknown.
Hand off the before/after pair with the decision table; do not auto-apply a patch.

This guide is static browser-local material. Input, files and validation results are not sent to or stored by an external service.

Formatting-only is not a safety proof

No formatting difference does not prove that values and types are correct or that array order matches the receiver's contract. Check intent, schema and execution environment separately before applying a change.