Designing the system around the model: orchestration, memory, context, tools, observability and recovery.
“Internet access” is too broad a permission for an agent. Define destinations, protocols, data-release rules and failure behaviour, then test bypasses against the deployed network path.
Maintenance agents can turn condition signals into coordinated work, but plant safety and control demand bounded action and field verification.
A joint lab should be a governed way to create decision evidence across organisations, with shared methods but explicit ownership of systems, data and conclusions.
Long-running agent work cannot rely on a transcript and hopeful retries. Explicit state makes progress, authority, recovery and completion inspectable across failures.
Agents earn their complexity only when a workflow needs bounded adaptation. A disciplined no-agent test can reveal when rules, search or ordinary software is safer and cheaper.
Least privilege for agents is not a smaller role assigned once. It is authority narrowed by identity, task, resource, action, time and consequence at every tool call.
Deleting a chat is not the same as removing personal data from memory, retrieval, logs, caches, evaluations, backups and learned models.
A passing patch is only the start. Repository evaluation should test understanding, change quality, security, reviewability and recovery.
Protocols make tools and agents interoperable, but they also standardise discovery, delegation and context exchange. Those interfaces need explicit trust and policy controls.
A convincing message can conceal a failed or unauthorised operation. Agent evaluation must inspect tool calls, external state and control decisions.
Keep sensitive data under client control by moving approved methods and people to the environment, exporting only the minimum reviewed evidence needed for collaboration.
An orchestrator should be judged by the workflow it controls: decomposition, routing, state, authority, recovery, verification and stopping—not by a polished final response.
KEEP EXPLORING
Read the method, assumptions and questions to ask.
A little more clarity
Start with the questions that shape a better decision.
The blog examines where agents create business value, how teams define release evidence, how authority and tool access should be bounded, and how engineering, security and governance owners can make a shared decision.
They are written for product, engineering, AI platform, security, governance and transformation leaders responsible for moving an agent workflow from idea or pilot towards accountable operation.
Articles explain the problems and decision methods behind the consultancy’s service direction. They are educational material and do not replace a scoped review of an organisation’s actual system.