The split in the thread — JSON mode plus schema validation for low-cost, regular fields, and constrained decoding where a single format error fails the chain — is the right default, and the failure modes already listed should stay in the release note: extra prose in a field, mistyped enums, a retry of the whole call, and first-token slowdown or incomplete regex support on a deep schema. I would not treat any of those slowdowns as a universal SLA. The questions about safe defaults and a hybrid path are the parts I would nail down before choosing a side.
First, a hybrid is useful if the boundary is explicit. Constraining the envelope and the enumerations, while leaving free text inside string fields that you then validate, is the version I would try; a second pass that “repairs” a failed JSON-mode object with a constrained call has its own failure mode, because the repair can invent values that were never in the source. The schema itself can also be wrong. An over-tight pattern will make constrained decoding emit a grammatically valid object that is useless to the business, and that will not show up if you only measure “valid JSON rate.” I would measure illegal paths and first-token latency on the target schema, as the editorial note asks, and I would also measure how often the valid object still fails a business rule.
Second, grammar validity and business validity are two layers. Constrained decoding does not know that a date does not exist, that a SKU is not in the catalog, or that a unit is out of range. Downstream still has to validate, and the log should say which layer rejected the object. On a hard failure I would rather degrade to a safe default or a human queue than blindly retry the same unconstrained call; retries are for transient decode or tool errors, not for “the model talked in a field.” The boundary between those should be written down, not decided in the on-call.
Third, the path is part of the metric. A grammar that works in one engine’s regex subset fails in another, so the engine, the schema hash, and the token counts need to be pinned, and a path change should rerun a frozen set. On a local or ARM inference host, constrained decoding can be cheaper than a retry, or more expensive if the mask runs on the CPU; measure both paths on the runtime you will ship.
If the cost of a bad object is high, I start from constrained decoding on the critical fields, keep schema validation on everything, and refuse to treat a valid grammar as a valid business object.