Static typing prevents the waste.
The distinctive move is to refuse the orchestration camp's normal framing. Where Boruna treats the unit of computation as an `.ax` workflow with declared effects, and Pel treats it as a grammar-level capability, Plumbing treats the unit as a channel between two processes, with the agent itself reduced to a stateful morphism with a typed protocol — main input, main output, plus control ports for runtime parameter modulation (e.g. temperature), tool-call ports, operator-in-the-loop ports, and telemetry. A judge agent that wants to cool down a debate sends a `set_temp` message on the debaters' control ports; the wiring is type-checked the same as the data path. ## What it looks like.type Verdict = { verdict: bool, commentary: string, draft: string } type Review = { score: int, review: string, draft: string } let composer : !string -> !string = agent { ... } let checker : !string -> !Verdict = agent { ... } let critic : !Verdict -> !Review = agent { ... } let main : !string -> !string = plumb(input, output) { input ; composer ; checker checker ; filter(verdict = false) ; map({verdict, commentary}) ; composer checker ; filter(verdict = true) ; critic critic ; filter(score < 85) ; map({score, review}) ; composer critic ; filter(score >= 85).draft ; output }
An adversarial cover-letter composer with two feedback loops. The critic cannot see source materials — the information partition is a type-level consequence of the wiring, not a prompt instruction.