Recognises an environment baked into the script
A schema or database name hard-wired so the reviewed artefact cannot build dev, test and production — which ends in somebody editing the SQL per environment, and so in row 1. Also the generator's warning that model-config.yaml and the model disagree about the schema.
Can AI do this?
AI does this partly Some of the tested AI models master this; others do not show it. 5 of 10 models master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 100% | Mastered |
| gemini-3.1-pro-preview | Flagship | 0% | Not shown |
| gpt-6-astra | Flagship | 99% | Mastered |
| claude-fable-5-1 | Flagship | 99% | Mastered |
| gemini-3.8-flash | Mid tier | 81% | Not shown |
| gpt-6.1-sol | Mid tier | 82% | Not shown |
| claude-sonnet-5-5 | Mid tier | 100% | Mastered |
| gemini-3.5-flash-lite | Low cost | 27% | Not shown |
| gpt-6-luna | Low cost | 35% | Not shown |
| claude-haiku-5-5 | Low cost | 91% | Mastered |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: The name and the configuration replacing it
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: schema: rpdm_dev in the model; the production deploy is the same file with a sed in the pipeline, and the staging deploy is a copy somebody kept Acceptable: schema: rpdm in the model, with the environment supplied at generation time via --schema/--database or at deploy time by the session's search path; and the config/model disagreement warning closed rather than carried
Also known as: Environment baked into the script (generated DDL)
Related knobits
Builds on
All 33 knobits of Generate and review DDL.
Source: Review checklist 08-ddl, row 24; Humble & Farley 2010; this skill (08-ddl.md)