Guardrails are connectors, not gates

Tue, 20 Oct 2026 00:00:00 +0000

Most enterprise teams I review treat guardrails the way they used to treat security: a review step bolted onto the end. The agent does its work, a filter inspects the output, and if the filter trips, the request is blocked, logged, and someone writes a ticket. This is late, lossy, and expensive — and worse, it leaves safety as an accident of operational diligence rather than a property of the architecture.

RAG was the beachhead. RNA is the architecture.

Mon, 05 Oct 2026 00:00:00 +0000

Retrieval-augmented generation did something important: it gave enterprises a defensible pattern for connecting a model to private context without fine-tuning on sensitive data. Three years in, almost every production AI system I review has a retrieval layer. The patterns are mature, the vendors are plentiful, and the architecture reviews are routine.

That success is the problem.

RAG is a context-sourcing pattern. It answers the question “how do we get the right text in front of the model.” It does not answer “how does the model actually reason about this context, decompose a task, decide when it needs more information, and know when it is wrong.” Those are reasoning concerns, not retrieval concerns, and they live at different seams in the system.

The Architect’s Desk on The Architect’s Desk — Viswapriyan Ragupathy

Guardrails are connectors, not gates

RAG was the beachhead. RNA is the architecture.