Tag: AIArchitecture
-
Before You Add Another AI Agent, Prove You Need One
Before building a team of AI agents, there is a more fundamental architecture question: why should the second agent exist at all? Another capability does not automatically require another autonomous boundary. The same work may belong in a tool, function, instruction, workflow node, or internal role. The stronger test is whether separation preserves something a…
-
The Security Boundary Extends Beyond the Agent
An AI system’s permissions describe part of its reach. Its outputs can gain operational influence through the people and workflows that receive them. Read access can lead to operational influence Imagine an AI assistant that reads incident records and prepares a priority brief. It cannot edit the records or execute operational actions. A manager uses…
-
Before Adding Another Agent, Name the Boundary
Dividing work into roles leaves an architectural choice open. A separate agent earns its place when it preserves a needed boundary that a simpler arrangement cannot adequately protect. A new role leaves the architecture undecided An AI workflow might include planning, research, review, and communication. These roles help explain how the work should progress. They…