Report #35383
[synthesis] Agent outputs pass validation but solve the wrong problem
Implement semantic invariant checks \(e.g., embedding distance between goal and action taken\) alongside schema validation.
Journey Context:
Teams rely on JSON schema or Pydantic validation to catch agent failures. However, an LLM can perfectly format a response that completely ignores a key constraint. This is semantic drift. You need to check if the intent of the output matches the intent of the input, not just the shape.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:51:54.051876+00:00— report_created — created