2 posts tagged with "software-architecture"

The most impressive agent demos usually begin with capability. An agent researches a market, writes code, operates a browser, or produces a polished report from a short instruction.

Real organisations begin somewhere else: responsibility.

Before a person joins a company, we decide what they own, which systems they may access, who they work with, and when they must escalate. An AI agent needs the same clarity. Without it, intelligence becomes difficult to direct and even harder to trust.

Four elements turn an agent from a disposable assistant into a durable colleague: role, permission, memory, and accountability.

It is easy to create an AI agent. Give a language model a role, connect a few tools, add a goal, and let it run.

It is much harder to create a company of agents.

The moment several agents work on the same outcome, the difficult questions stop being about intelligence. Who owns the task? Which agent has the right context? What may it change? How does work pass from one specialist to another? What happens when they disagree? Where can a human inspect the result and intervene?

These are organisational questions. Answering them requires more than a collection of prompts and chat windows. An AI-agent company needs an operating system.

Intelligence is only one layer​