Part 1: The Mental Shift · Module 3
Structured Output: Getting Data Back, Not Text
Ready. Lessons, visuals, quiz, harness and check script are complete and were run on a current model.
Work through it in order
- 1 The run that did not breakThe untyped router returned a clean queue name on every ticket, so the failure this module was planned around never showed up, and the typed router chose the same queue on every ticket. 1 interactive
- 2 What the schema costsTyping the router multiplied input tokens several times over for the same one-word decision, while output tokens moved much less. 2 interactives
- 3 Three ways a typed call ends badlyA typed call that was cut off raised a validation error and returned nothing, a reply of the wrong shape raised too, and a reply with no text block returned None without raising. 2 interactives
- 4 Typed is not correctA typed call returned a value that passed every check and was not the value in the prompt, and both routers agreed with each other while disagreeing with the answer key on one ticket. 2 interactives
- Q QuizEvery option explained, scored as you go.
- T Hands-on testThe check script passes on your run file and your prediction: all ten tickets ran both ways, every typed call returned one of the four queues, the truncation call did not return a queue and is in the file, the header recomputes from the records, and the prediction is dated before the first call.