When an extraction system attaches one confidence number to a record, it is reporting an average, and an average exists to hide variance. A record can post a strong overall score while one field inside it sits far below the line, and the aggregate erases exactly the fact anyone downstream needs: which value not to trust. The score worth acting on…

A measurement loop looks like rigor. You run the current version of a prompt against a set of cases, score each output, and compare the aggregate to the last version. The number that comes out feels objective in a way a reviewer’s impression never could. That feeling is mostly borrowed. An evaluation does not manufacture its own trustworthiness. It inherits it from…

A prompt is not a document you write once and file away. It is a piece of production behavior. It decides what your system returns, it changes over the life of the system, and every change to it changes the output for every request that flows through it. That makes a prompt an artifact in the same sense that a…

Deterministic validation can only enforce standards you can state as a rule. A schema check, a range check, a check that two fields agree: each one closes a failure you were able to write down in advance. But a large share of what makes an output good cannot be written down that way. Is this summary faithful to what it summarizes? Does…

A language model can hand you an object that is perfectly shaped and entirely false. Every field is present, every type is right, the whole thing parses without complaint, and the value in the field your downstream logic depends on was invented. This is the failure mode that survives structured output. Enforcing a schema settles what shape the answer takes. It settles…

A tool definition is normally understood as a way to make something happen. You declare a function the model can call, it emits the arguments, and something on the other side runs. For pulling structured data out of text, invert that picture entirely. Define the tool, let the model call it, and let nothing on the far side ever run. The call itself is…

A schema attached to an extraction task looks like a description of the output you expect back. It is really a set of instructions the model reads while it generates, and it presses on what comes out. That reframing is the whole subject. A schema is not a passive record of the shape you hope to receive and inspect…

There is a difference between asking a model for JSON and guaranteeing that what comes back conforms to a schema. It looks like a formatting detail. It is actually one of the most consequential architectural decisions you make when you put a language model inside a larger system, because it determines where the risk of malformed output lives, what…