How One AI Pipeline Learned to Catch Valid but Wrong-Shaped JSON Responses

On March 3, 2026, a content automation pipeline built by an IT analyst failed not because an AI model returned invalid JSON, but because it returned a bare array instead of the expected envelope object. The error passed JSON parsing cleanly but was caught only later by Zod schema validation, highlighting a lesser-known second layer of structured-output failure. To fix the issue, the developer embedded the exact JSON schema directly into the prompt and added a deterministic code fallback to wrap bare arrays automatically. The approach was later codified as a standing rule across two levels of project configuration to ensure it applied to all future work. The lesson proved broadly relevant when the same pipeline was extended to support three interchangeable AI backends, confirming that prompt-plus-code defenses are necessary regardless of the underlying model.