LV2 · Toolooo Standard
Data Contract Drift Doctor
Compare JSON release samples for consumer-breaking changes, date/value-set drift and possible path movement.
Compare release samples through consumer impact, date/value-set changes and possible path movement. Shape inference reuses Schema Drift Doctor. For schema-only JSON/CSV inspection use that tool; for expected-versus-actual API validation use API Payload Doctor.
Up to 500 KB per sample, 30 levels and 2,000 paths. Inspect up to 50 items per array. Local memory only; nothing is saved, shared or exported.What this tool does and why
Before you start
What
Compare JSON release samples for consumer-breaking changes, date/value-set drift and possible path movement.
Why
A payload can remain valid JSON while breaking consumer parsing, branching or field access. Compare release evidence before changing a contract.
Your Result and Action update in the tool as you change its inputs.
Model note
This browser-side model explains the inputs you choose. Check an important decision against the real system, brief, or production constraints.
Next
How this tool stays honest
How it works
Review before and after JSON snapshots with bounded shared schema inference. Inspect observed type, shape, presence and nullability changes alongside uncertain date, value-set, rename and nesting evidence, then plan consumer validation and a backward-compatible migration.
Assumptions
The tool runs in your browser and models the information you provide. It does not know facts outside that model.
Limitations
Samples are not schemas. BREAKING labels indicate potential incompatibility; enum, rename and movement findings are inferences. Arrays are sampled and empty arrays cannot establish item contracts.
Understand Data Contract Drift Doctor
What this tool helps you understand
Review before and after JSON snapshots with bounded shared schema inference. Inspect observed type, shape, presence and nullability changes alongside uncertain date, value-set, rename and nesting evidence, then plan consumer validation and a backward-compatible migration.
When to use it
Before releasing a changed JSON response to existing consumers.
Try a scenario
Compare an old sample with a new sample where a nullable timestamp becomes a number. Check affected parsing assumptions; samples alone do not establish a schema.
How to read the result
Review BREAKING observations first, confirm RISKY value/date assumptions, and collect evidence for UNKNOWN findings. Preserve aliases or version contracts where consumers require migration.
Assumptions and limits
Samples are not schemas. BREAKING labels indicate potential incompatibility; enum, rename and movement findings are inferences. Arrays are sampled and empty arrays cannot establish item contracts.
Toolooo is part of Khizooology, created byKhizar Imtiaz (khizooo).