Configuration Validator and Semantic Diff Studio
A strict, versioned parser and semantic comparison workspace for high-consequence configuration changes. It validates JSON or YAML syntax, detects duplicate keys, optionally applies JSON Schema 2020-12 and reports semantic changes as JSON Pointer paths.
Who this Lab is for
Designed for
- Platform, security and release engineers
- Principal engineers reviewing infrastructure changes
- Teams authoring schema-governed configuration
Use it when
- Reviewing a generated or hand-edited configuration change
- Detecting duplicate YAML or JSON keys before deployment
- Validating a document against an organisation-owned schema
- Separating semantic changes from formatting noise
A complete run, step by step
Choose the syntax contract
Use strict JSON, YAML 1.2 or documented auto-detection.
Paste the current document
The parser reports syntax and duplicate-key problems without attempting repair.
Add schema and comparison inputs
Optionally supply a strict JSON Schema and a proposed document using the same syntax.
Review semantic paths
Inspect semantic paths, the verified patch and canonical fingerprint rather than relying on line-oriented diff alone.
What you will need
Prepare the following information before starting. Use measured evidence where possible; defaults are examples and should not be treated as recommendations.
Document syntax
Auto detects JSON by its first token; otherwise uses strict YAML 1.2.
Choices: Auto detect · Strict JSON · YAML 1.2
Current document
Configuration to parse and optionally validate.
Proposed document
Optional document parsed with the same syntax and compared semantically.
JSON Schema 2020-12
Optional strict JSON Schema. Schema and format errors are reported separately from syntax errors.
Offline schema pack
Optional version-pinned schema evaluated without network access. Leave custom schema empty when a pack is selected.
Choices: None / custom schema · RFC 6902 JSON Patch (2013) · Kubernetes ConfigMap v1 envelope (KBY 2026.07) · Terraform plan JSON 1.x envelope (KBY 2026.07)
What the result tells you
Your report includes
- Strict syntax and duplicate-key findings with locations
- Optional JSON Schema 2020-12 validation
- Canonical JSON projection
- Added, removed, changed and type-changed JSON Pointer paths
- Round-trip verified RFC 6902 patch and RFC 8785 SHA-256 fingerprint
- Version-labelled offline schema packs for bounded contracts
How it is determined
JSON is parsed with comments and trailing commas disabled; YAML uses strict YAML 1.2 with unique-key enforcement. Optional schemas use JSON Schema Draft 2020-12 with strict compilation and format validation. Parsed values are recursively compared in sorted object-key order, preserving array order.
Syntax is evaluated by strict JSON or YAML 1.2 parsers, schemas by JSON Schema 2020-12, and semantic differences by deterministic JSON Pointer traversal.
Model assumptions
- • Both documents intentionally use the selected syntax.
- • Schema validity only means conformance to the supplied schema, not production safety.
- • Array order is semantically significant and changes are capped at 500 displayed paths.
ConfigMap policy mode change
Situation
A proposed YAML document changes data.mode and adds data.audit while retaining identical metadata.
Result
Formatting is ignored and the studio reports two semantic paths: /data/mode changed and /data/audit added.
Use the result with engineering judgement
- Schema conformance is not proof that a configuration is safe for production.
- Provider admission controllers and runtime defaults are outside the parser contract.
- Arrays are ordered values; set-like array semantics require a domain-specific schema or comparison tool.
- Displayed changes are capped at 500 paths.
Questions before you begin
Will it fix invalid configuration automatically?
No. Automatic repair can change intent. It reports exact parser or schema findings for an engineer to resolve.
Does valid YAML mean valid Kubernetes?
No. YAML validity covers syntax only. Kubernetes validation requires the correct API schema and admission behaviour.
Are secrets sent to an AI model?
No AI participates in parsing, validation or diff calculation. Avoid pasting production secrets into any browser tool.
Ready to run Configuration Studio?
Log in to open the full interactive workspace. Your completed result can be saved, revisited and exported as a private report.
Log in and start