Systems that take a sequence of actions rather than answering once.
The model is handed a typed catalogue of callable functions — look up an order, check stock in a warehouse, raise a ticket — and chooses which one to invoke and with what arguments. A separate layer decides whether that invocation is permitted: reads run unattended, anything that writes waits behind an allow-list or a human confirmation.
A request arrives — a refund, an address change, a duplicate invoice, a licence renewal — and the system reads the policy, plans the steps, calls whichever systems hold the records and closes the case without a person opening it. What gets checked afterwards is the state the records ended in, not the reasoning the system wrote on its way there.
Rather than one long prompt doing everything, the work is cut into parts — one agent retrieves, one drafts, one checks the draft against the retrieved material — each with its own instructions and its own tools, and a coordinator passes results between them. Each part becomes separately testable; the handoffs between them become the system.
The last mile of an Indian back office is often a screen with nothing behind it you can call — a filing portal, a bank's corporate console, a state department form. A model reads the rendered page or the desktop, decides where to click and what to type, and performs the steps a clerk would, recording the run so somebody can replay what it actually did.