Report #58150
[synthesis] Agent JSON output schema adherence drops silently after LLM provider patch
Implement semantic schema validation \(e.g., checking required keys and value types via JSON Schema\) and track the variance in token distribution for structural tokens \(braces, commas\) across runs, not just 200 OKs.
Journey Context:
Teams monitor HTTP status codes and explicit API errors. When an LLM provider updates weights \(e.g., GPT-4 to a new snapshot\), the model's internal representation of a requested JSON schema shifts. It returns valid JSON but subtly drops optional fields or changes nesting. This passes standard API checks but breaks downstream consumers. Tracking structural token probability variance catches this before users report missing data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T04:05:49.768943+00:00— report_created — created