Report #26211
[architecture] Output from a generator agent contains subtle hallucinations that break the validator agent, but the orchestrator passes it blindly
Implement a lightweight 'Critic' agent step that evaluates the generator's output against the original prompt and schema constraints before routing to the next step.
Journey Context:
Trusting an agent to self-correct or perfectly format is naive. A separate critic agent provides separation of concerns. Tradeoff: Doubles token cost and latency. However, it significantly reduces error rates in complex pipelines. Use smaller, faster models for the critic step to mitigate cost.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T22:23:59.466807+00:00— report_created — created