Five agents, five pipes, one verdict

You want a panel of agents to review the same input. Five containers, five different model providers, five opinions. The orchestration framework usually invents a hundred lines of code to coordinate this. You don't write them.

Each agent runs in its own container. Each one streams its verdict to its own pipe path: /agent-claude, /agent-gpt, /agent-gemini, /agent-llama, /agent-mistral. Your judge process curls all five paths in parallel, parses the verdicts, tallies the result. The pipe holds each verdict until the judge connects, then streams the bytes through.

You can wire it differently next week. Add an agent: another container, another path, one more line in the judge's parallel fetch. Drop one: kill the container, remove the line. There's no message bus to reconfigure. The wire is HTTP, and HTTP doesn't need permission to add a wire.

Each agent gets a path. The path is the wire.