Permission-aware retrieval: the control most RAG diagrams omit
A retrieval system should establish the active principal and filter authorised resources before similarity ranking or model context assembly.
Evidence, privacy and oversight practices for keeping agentic systems accountable as they change.
A retrieval system should establish the active principal and filter authorised resources before similarity ranking or model context assembly.
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.
Deleting a chat is not the same as removing personal data from memory, retrieval, logs, caches, evaluations, backups and learned models.
Effective oversight gives a prepared person the signal, authority, time and interface needed to prevent or limit a defined AI failure.
A technical review can trace data and test controls, but it cannot alone determine lawful basis, resolve policy choices or certify compliance.
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.
An evidence register should connect each claim and requirement to versioned artefacts, review decisions, known gaps and the conditions under which evidence expires.
Better agent context is not the largest possible context. It is the smallest authorised, relevant and timely data set that supports the task.
A principle becomes operational only when it is translated into requirements, control owners, enforcement points, evidence and responses to failure.
KEEP EXPLORING
Read the method, assumptions and questions to ask.