Report #56015
[architecture] Agents fail silently downstream because JSON schema validation only checks structure, not semantic meaning
Implement a two-tier contract: structural \(JSON Schema\) for routing/parsing, and semantic \(LLM-as-judge or rule-based assertions\) for intent, combined with strict max-token limits on shared fields.
Journey Context:
JSON Schema is fast and deterministic but misses hallucinated content that fits the schema \(e.g., \{"action": "delete\_database", "confidence": 1.0\}\). Relying solely on it leads to cascading failures. Adding semantic checks adds latency but prevents catastrophic chain failures where a well-formed but semantically invalid payload triggers an irreversible action.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:30:45.048894+00:00— report_created — created