Patched JSON to Selected-Path Support Copy

Apply a caller-authored merge patch and replace named values before reviewing a stable JSON support copy.

Processing stays in your browser; code and assets download as needed. Original and checkpoint downloads retain source content, including omitted values. Reset and Exit stop this session’s owned work; they do not establish secure erasure or anonymity.

This flow needs JavaScript. If it does not load, refresh the page and try again.

About this flow

Choose a UTF-8 JSON file, supply compact one-line RFC 7396 patch text, replace exact JSON Pointer targets in the patched result, and sort keys. This produces a patched support copy rather than a dotenv parse or a difference checklist.

Limitations

Each merge input5 MiB;40 levels/200,000 values; result20 MiB, each next input5 MiB. A larger completed intermediate remains only a checkpoint and final success refuses.
RFC7396 null object members delete keys; root nonobject patches replace the document. Redactor replacement, including null, sets values rather than deleting them.
1–1000 exact pointers;4096 units each/256 KiB total; existing canonical array indexes only; duplicate/ancestor-overlapping or missing paths refuse.
Numbers retain exact spelling; key sort uses UTF-16 code units and arrays keep order. No schema validation, wildcards, secret detection or security certification.
Only the latest checkpoint is exposed. The unchanged standalone redaction-report.json is supplementary and deliberately omitted from the connected primary artifact.