A failure ladder for retrieval-augmented agents
A wrong answer is the final symptom of failures that may begin with source coverage, access control, parsing, retrieval, context assembly, generation or action.
Softlander blog perspectives published in August 2026.
A wrong answer is the final symptom of failures that may begin with source coverage, access control, parsing, retrieval, context assembly, generation or action.
Review should follow material changes in purpose, authority, data, users, dependencies, evidence or incidents—not an arbitrary calendar alone.
An AI inventory becomes useful when it identifies deployed systems, their context, owners, dependencies and review triggers—not merely a list of model vendors.
Specify the workflow, evidence, responsibility and exit conditions suppliers must meet, then evaluate them through representative scenarios.
Agent credentials should be shorter-lived than the assumptions that justify them. Bind them to a workload, audience, task and action, then prove renewal and revocation work.
A centre can concentrate scarce expertise and reusable controls, or become an approval queue detached from real work. Choose the mandate before the structure.
Smaller models are not merely budget substitutes. Used behind explicit routing and escalation rules, they can improve latency, locality and architectural control.
A reference trace can explain one acceptable journey. Treating it as the only correct path can punish valid behaviour and conceal unsafe alternatives.
A useful quarterly watchlist tracks changes that could alter real decisions: system authority, evidence, incidents, standards, providers and organisational readiness.
Investigators need more than chat transcripts. Preserve identity, instructions, retrieved context, model and tool versions, policy decisions, credentials, network events and actual state changes.
Do not divide work into “human” and “AI” columns. Redesign tasks, decisions, authority, handoffs and learning so each role remains operable and accountable.
A successful demonstration does not create a live service. Pilots stall when they test capability without resolving ownership, integration, economics and operating evidence.
KEEP EXPLORING
Read the method, assumptions and questions to ask.