Framework semantic default
deeply nested inputs Functional Model Keras 3
A model using nested dictionaries/lists fails construction after migration.
Agent Quick Fix
Repair against the current Keras 3 contract, then keep the change narrow and source-backed.
Product: Keras 3
Current-contract area: Keras 3 deeply nested Functional inputs rejected
Likely root cause: A model using nested dictionaries/lists fails construction after migration.
Repair direction: Verifier checks behavior across multiple requests/build modes, not merely compilation. Check model outputs and save/load behavior, not only construction.Symptom
A model using nested dictionaries/lists fails construction after migration.
Why This Happens
Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
site:keras.io/guides/migrating_to_keras_3 deeply nested inputs Functional Model Keras 3
https://keras.io/guides/migrating_to_keras_3/