Follow the relationships in the interactive agent map: app → harness → LLM → approved tools, with optional RAG and separate observability.
You ask, “Why is payments slow?” A chatbot can write an answer. An agent can also ask a permitted tool for evidence, read the result and decide what to do next. It repeats a small loop until it can answer or a rule tells it to stop.
The model is the part that proposes words or a tool call. The harness is the surrounding program: it gives context, checks permissions, runs an allowed tool, remembers the conversation and records the result. A model cannot add a new permission just by asking for it.
OpsDesk gives an operator a ticket inbox and one useful AI action. First the inbox works by itself. Later, Analyze safely asks the runtime investigator to collect synthetic service/release evidence. A convincing answer is not proof: we will look for the actual tool call and its trace.
The diagram teaches the loop. It does not run a model or send a trace.