Urgent.News

What's breaking now, across thousands of outlets.

AI

The More Powerful the AI, the More the Architecture Matters

The boundaries I designed, the gaps I haven't solved, and why the difference matters Part 14 findings of an experiment: building an LLM-powered support agent with deterministic boundaries. The companion repo contains the full code. If someone asked me over a coffee what I've been building, the short version is this. A support agent that can work out whether you're owed a refund, and cannot give…

The architecture of AI systems plays a crucial role in determining their effectiveness, according to a recent experiment building an LLM-powered support agent with deterministic boundaries. The experiment involved creating a support agent that could determine whether a customer was owed a refund without actually providing one. The AI system read the customer's message and found relevant documents.

The software then decided eligibility, owned risk tiers, scoped lookups to the logged-in user, and placed expensive tasks in a queue for human intervention. The entire system ran without any API key.

The key takeaway from the experiment is that the boundaries set for the AI system were crucial to its success. These boundaries included the gaps the experiment hadn't solved, the reasons why the difference mattered, and a set of tests that would fail if the system stopped being true. One of the most important boundaries was an allowlist that prevented the business rules from referencing any packages other than itself and the JDK.

This allowed the system to maintain its deterministic behavior and prevented any unexpected dependencies from creeping in.

Another important aspect of the architecture was the gate that determined whether the AI or a human would handle a particular task. The gate was designed to only allow tasks with a low risk tier to be handled by the AI, while medium to high risk tasks required human approval, and very high risk tasks were only proposed and required a person to execute them. This gate helped ensure that the system remained under human supervision and did not become too autonomous.

The experiment also highlighted the importance of having a well-defined architecture that prevents the system from slowly decaying into something that no longer meets business requirements. By having an allowlist and a deterministic gate, the system was able to maintain its focus on business questions and avoid becoming overwhelmed by technical debt. The experiment did not include a full implementation with real customers, but it did provide a framework for building a more robust and reliable AI system in the future.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

Stage 3 of enterprise AI adoption: agents that can read

This is part 3 of a series that started with the full reference diagram in part 0 , covered identity and the gateway in part 1 , and covered data and retrieval in part 2 .

  • Stage 3 of enterprise AI adoption introduces autonomous agents
  • Agent runtime enables independent task execution with containment
  • Read connectors grant role-specific access to internal systems

Build and Test an AI Agent Skill with SKILL.md and Python

AI agents are good at interpreting intent, but they are not a reliable place to hide every rule in a workflow. If an agent must count characters, parse a file, or refuse to overwrite an existing…

  • Create skill structure with SKILL.md and scripts directory
  • Implement deterministic script to validate Conventional Commit messages
  • Test script thoroughly covering various message scenarios

More from Saturday 19 September →