ModelForgeLocal only
JSON → IR → deterministic code

JSON to Spring Boot models

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

VERIFIED 4.1.1Spring Boot 4.1.x · Java 21
Awaiting generationInspect the model, choose a target, then commit the route.
JSONIRCODE
Hover a field to inspect its route
COMPILER NOTES

Spring output tied to verified profiles

Spring compatibility is not a label pasted onto generic Java. Version profiles own Java ranges and verification metadata, while the adapter adds Jakarta Persistence and Spring Data semantics after core Java generation.

Common questions

Will a field named id automatically become @Id?

No. Arbitrary JSON cannot prove a database primary key, so identifier selection is explicit.

What does verified mean?

The recorded profile’s Maven fixture compiled successfully against the exact Spring Boot patch.