Module 05 Summary
What this module established
Ask for a shape when the next step is code - it removes the interpretation step, and interpretation is where meaning drifts. Parsing gets you a dict; validation gets you a dict you can rely on.
Carry forward
- Count parse failures rather than defaulting past them. A rising rate is usually truncation from a low
max_tokens, not model quality. - Retry with the specific error attached, cap the attempts, and have a give-up path.
- Widened enums break OLD readers on NEW data. Deploy readers first, and assume both versions run during any rollout.
Before moving on
Move on when your retry feeds back specific errors and gives up cleanly, and you can state which schema changes are safe in which order.
