Report #53262
[architecture] Downstream agent crashes on invalid syntax from upstream agent
Insert a deterministic validation function \(e.g., AST parser, linter, JSON schema validator\) between the generating agent and the consuming agent. Do not use an LLM to validate syntax.
Journey Context:
A common mistake is using an LLM to check another LLM's output for structural or syntactic correctness. This is slow, expensive, and unreliable. Traditional parsers \(like pylint for Python or ajv for JSON\) are 100% reliable for syntax. The orchestrator should catch the validation error and route it back to the upstream agent with the exact compiler/parser error message for a self-correction retry. Tradeoff: Adds an extra step and latency to the pipeline, but dramatically reduces error cascades and token waste compared to LLM-based validation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:53:43.556532+00:00— report_created — created