How would you design a useful JSON schema for model output?

I separate transport validation from domain validation. Provider-constrained decoding can enforce shape, while application code checks allowed transitions, cross-field consistency, current identifiers, and source evidence. I account for schema compilation latency and token overhead when deciding how much structure belongs in one response. The contract is versioned, and refusals or incomplete generations are represented outside the normal success payload rather than forced into domain fields.