Orbit is my multi-agent content system. A planner directs each run, and a Bash orchestrator runs the agents in sequence or in parallel. Most of the interesting problems in it are about what the agents write. This one was about what an agent returned.
The failure
On 24 March 2026 the analytics agent returned placeholder code instead of data. Nothing crashed. The output file existed, the next agent read it, and the system carried on for five cycles.
That is the failure I now design for first. An agent that errors is easy to see: something exits with a failure and the run stops. An agent that returns something plausible but wrong is quiet, and every step after it treats the wrong thing as input.
Check the shape after every run
The fix was output validation after every agent run, in the orchestrator itself. It asks three questions of each output:
Is it valid JSON?
Does it look like code instead of data?
Is it an error object?
None of these are clever.…