JSON schema patterns for LLM output

Choosing and using JSON schemas for LLM output

• Field Order as a Contract: Testing the First Keys
• JSON Schema Patterns for LLM Outputs
• JSON Schema Patterns That Stream Well
• Schema Tests for Approval Requests: Fixtures That Catch Edits
• A Confidence Schema for Support Answers: Score and Source
• Choosing Nullable, Enum or Union by First-Failure Rate
• Field-Level Extraction Before Merging
• Incremental JSON Parsers Compared: Which Field Arrives First
• All of JSON schema patterns for LLM output

Repairing broken LLM JSON

Repairing and validating broken JSON

• A Repair Prompt Template That Names the Failing Field
• A Validator Wrapper That Names the First Failing Field
• Naming the First Failing Field: A Validator Wrapper
• Repairing Invalid JSON from LLM Responses
• Routing a Failed Repair to a Human Queue: Codes, Ownership
• What to Do When a Model Ignores the Schema: Diagnostic Playbook
• When a Model Ignores the Schema: Diagnostic Playbook
• When to Repair a Failed Response and When to Start Over
• All of Repairing broken LLM JSON

Structured output vs function calling

Structured output vs function calling

• Structured Output from LLMs: Schemas and Validation
• When to Use Structured Output vs Function Calling
• An Extractive Answer Contract: Fields and a Fallback
• Cost and Latency of JSON Mode Across Providers

Schema compliance across models

Schema compliance and testing across models

• A Compliance Scorecard for Two Candidate Models
• A Weekly Rollup of Schema Misses by Field and Prompt Version
• Counting Schema Misses by Field, Model and Prompt Version
• Measuring Schema Compliance per Model and Prompt
• Schema Compliance Across Three Providers: A Repeatable Harness
• Schema Compliance by Model: A Comparison Test You Can Run
• Storing LLM Outputs in Postgres: JSONB and Queries
• Testing Structured Outputs at Scale: Fixtures and Real Calls
• All of Schema compliance across models

Generating schemas from code

Generating and syncing schemas from code

• From JSON Schema to Pydantic: One Source of Truth
• A Schema Registry for Agent Contracts: Who Owns Which Field
• Generating Tool Schemas from Code
• Keeping a Schema and Its Prompt in Sync: A Lint Rule
• Keeping an Approval Schema in Sync With the Agent's Tool Output
• Keeping API Contracts in Sync With a Lint Rule
• Versioning an Event Schema Without Stopping the Publisher
• What to Log When an Approval Is Rendered and Decided
• All of Generating schemas from code