Evaluation & assurance6 MIN READ
Continuous evaluation without alert theatre
Run evaluations often, but interrupt people only when a signal maps to user consequence, a decision owner and a tested response.
THE SOFTLANDER BLOG
Architecture & engineering
Designing the system around the model: orchestration, memory, context, tools, observability and recovery.
In Architecture & engineering
47 articlesAgent security6 MIN READ
A practical security review for an MCP server
Review an MCP server as a privileged protocol adapter: verify tool semantics, OAuth boundaries, token audience, downstream delegation, input handling, isolation, logging and consent.
Agent security6 MIN READ
How to map an AI agent’s attack surface
A useful agent threat model follows data, instructions, identity, tools and state across trust boundaries. This method turns the map into test cases and control decisions.
Agent security6 MIN READ
The dangerous combination of private data, untrusted content and external actions
An agent becomes especially risky when it can read secrets, ingest attacker-controlled material and communicate or act outside the boundary. Design the workflow to break that combination.
Architecture & engineering6 MIN READ
Context is not memory: why the distinction matters
Context is the information available for one inference. Memory is a governed process for retaining, changing and recalling information across time. Confusing them creates silent risk.
Agent security6 MIN READ
What CISOs need to know about tool-using AI agents
Tool-using agents join untrusted input, probabilistic decisions and privileged action. CISOs should govern that path as a security system, not a chatbot feature.
Evaluation & assurance6 MIN READ
Evaluating a customer-support agent from answer to action
A support agent should be judged on whether it resolves the right problem safely, not on whether its first answer sounds convincing.
Architecture & engineering6 MIN READ
Agent observability should answer questions, not produce dashboards
Useful observability reconstructs a decision and its effects. Begin with incident, release and governance questions; then collect the smallest safe evidence that answers them.
Governance & privacy7 MIN READ
A useful autonomy classification starts with consequences
Classify an AI agent by what it can affect, the authority it can exercise and how quickly people can recover—not by how autonomous a demo appears.
Architecture & engineering6 MIN READ
The anatomy of a tool-using AI agent
A tool-using agent is a controlled system around a model, not a model with an API key. Map its runtime layers before deciding what to test, trust or release.
Architecture & engineering6 MIN READ
How to evaluate model-routing decisions
A model router is a policy for allocating quality, cost, latency, privacy and failure risk. Evaluate whether each route serves the workflow—not whether routing is fashionable.
Architecture & engineering6 MIN READ
What can go wrong in a multi-agent handoff?
Multi-agent systems fail between workers when goals, evidence, state, authority and completion semantics do not survive the transfer. Test the protocol, not just each agent.
KEEP EXPLORING
Take the thinking
into your next discussion.
Read the method, assumptions and questions to ask.
A little more clarity
Questions worth asking.
Start with the questions that shape a better decision.
Which enterprise agent questions does the Softlander blog examine?
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.
Who are the articles written for?
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.
How do the articles relate to Softlander’s services?
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.