Report #30560
[architecture] JSON Schema passing but business rules violated
Implement secondary semantic validators \(Pydantic field validators, JSON Logic rules, or LLM-as-judge\) to enforce business rules; validate referential integrity, temporal constraints, and cross-field dependencies separately from structure.
Journey Context:
JSON Schema ensures syntactic correctness but allows semantic nonsense \(e.g., 'end\_date' before 'start\_date', contradictory status fields\). Developers often skip semantic validation assuming 'the LLM will get it right.' Secondary validators catch business rule violations before they propagate downstream. Tradeoff: writing validators is tedious and rules change frequently. Alternative \(LLM-as-judge\) adds latency and cost.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:40:52.377026+00:00— report_created — created