ModelForgeLocal only
JSON → IR → deterministic code

JSON model generation you can inspect

Target
01

Source

VALID JSON
Local processing. Your JSON stays in this browser.
370 B
02

Model

4 MODELS
6 fields
SourceTarget
TypeEvidence
id
email_address
email
created_at
datetime
profile
tags
projects
4 fields
SourceTarget
TypeEvidence
display_name
active
phone
address
2 fields
SourceTarget
TypeEvidence
city
country
2 fields
SourceTarget
TypeEvidence
name
active
4 diagnosticsThe property name was normalized for the target. "email_address" → "emailAddress"
  • infoThe property name was normalized for the target. "email_address" → "emailAddress"PROPERTY_NAME_NORMALIZED
  • infoThe property name was normalized for the target. "created_at" → "createdAt"PROPERTY_NAME_NORMALIZED
  • infoThe property name was normalized for the target. "display_name" → "displayName"PROPERTY_NAME_NORMALIZED
  • warningOnly null was observed, so a concrete type cannot be inferred. "phone"NULL_ONLY_UNKNOWN_TYPE
03

Output

Awaiting generationInspect the model, choose a target, then commit the route.
JSONIRCODE
Hover a field to inspect its route
COMPILER NOTES

How ModelForge compiles JSON

ModelForge parses JSON into a universal intermediate model first. You can inspect names, types, optionality, null evidence, and semantic hints before any target generator runs.

Common questions

Does my JSON leave the browser?

No. Parsing, inference, editing, and code generation run locally in the browser.

Can I review uncertain inference?

Yes. Empty arrays, null-only fields, mixed evidence, and normalized names remain visible as diagnostics.