Report #30886
[architecture] Downstream agent receives logically invalid or context-drifting output from an upstream agent because there is no verification gate
Implement a 'LLM-as-a-judge' verifier agent or deterministic assertion checks \(e.g., unit tests, linters\) at the boundary. The orchestrator should only pass the output to the next agent if the verifier confirms success.
Journey Context:
Trusting an LLM's self-assessment \('I have completed the task'\) is a common anti-pattern. An agent might output syntactically correct but semantically useless text. By inserting a lightweight, specialized verifier agent \(or deterministic script\) between steps, the orchestrator can catch hallucinations or task drift early. If verification fails, the orchestrator can loop back with the error context, creating a robust feedback loop rather than propagating garbage downstream.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T06:13:28.520642+00:00— report_created — created