Yesterday I wrote about agent sprawl being the new shadow IT. Today is the implementation post. I have five agents in my .NET stack. Triage, ranking, summarization, extraction, daily orchestrator. Each one is well-scoped internally. Microsoft Agent Framework handles the agent interiors just fine. But the handoffs between them? Wide open. The triage agent classifies a work item. The ranking agent reads that classification and scores it. Nothing validates the handoff. If triage hallucinates a category the scoring model has never seen, ranking scores it with full confidence. Both agents complete successfully. The failure is invisible. Someone is going to read this and say "that is just integration middleware." And so, yeah, the pattern is old. Contract, validate, route, log. ESBs did this. RPA orchestration did this. The difference is what crosses the boundary. RPA handoffs are deterministic. Schema validation is enough. Agent handoffs are stochastic. The triage agent can return a structurally valid payload with a hallucinated category. Schema passes. Content is wrong. You need domain validation and confidence gating, not just structural checks. That has no RPA equivalent. I built it with an IBoundaryContract interface, a BoundaryGate middleware, PostgreSQL for the crossing log, and a Vue.js dashboard that shows boundary health rates. The extract-to-triage boundary was failing at 14% and I had no idea until the dashboard lit up. The plumbing is familiar. The threat model is not. Full implementation on the blog. Link in comments.
View On WordPress