
Sounds like science fiction. But on June 24, 2026, the Reserve Bank of India (RBI) turned it into policy.
The RBI released a draft circular “Guidance on Regulatory Principles for Model Risk Management, 2026” which mandates an instant kill switch for every AI system running inside an Indian bank, NBFC, or financial institution. If an AI hallucinates, discriminates, or starts making erratic decisions, human supervisors must be able to shut it down immediately. No waiting or rebooting. Just a complete, immediate freeze.

Banks have been sprinting to integrate AI into everything. It approves your loans. It scores your credit risk. It hunts for fraud. It powers the chatbot you use to complain about a failed UPI transaction.
But AI has a chaotic side. It hallucinates - making things up with full confidence. It develops bias, quietly discriminating against certain applicants based on flawed training data.

That 72% number is not from India alone: it’s a global survey. But India’s banks face the same reality. The RBI isn’t creating a new problem. It’s making an existing one visible.
Convenience cannot come at the cost of control. The RBI is preventing a scenario where an out-of-control algorithm causes market panic before humans even realize what went wrong.
Every single category of RBI-regulated entity must have this in scope - no exceptions, no minimum size threshold.
But the clock isn't ticking equally for everyone. If you are a large bank running AI in credit, fraud, and customer service at scale, your Board Risk Committee will be fielding questions about this within weeks. If you are a digital-first NBFC or fintech that built AI-heavy underwriting without formal model governance, you have the biggest gap to close and the least time to close it. If you are a payments bank with AI in KYC and onboarding, the customer disclosure and human handoff requirements hit your core product. And if you're a credit bureau, your models don't just affect one institution, they underpin decisions across the entire sector. Expect the RBI to start here.
The common thread: if AI touches a decision that affects a customer, a loan, or a risk score - it's in scope. And the Board is now personally accountable for it.
Before the final circular lands, every CTO, CRO, and CDO at a regulated entity should be asking three questions about every AI platform in production:
If the answer to all three is yes, that vendor is your compliance partner. If the answer to any one is no, FI’s are carrying a regulatory risk that lands on your Board.
The RBI has made one thing non-negotiable: the bank owns the outcome, regardless of who built the AI. Your vendor list is now your compliance checklist.
The RBI has opened the floor for public comments until July 24, 2026. The final circular is expected in Q3/Q4 2026. That gives institutions a narrow window — weeks, not quarters — to assess where they stand.
The institutions that move now will shape how AI governance works in Indian banking. The ones that wait for the final circular will be playing catch-up under a deadline.
The machines can do the heavy lifting. But the humans will always keep their hands on the plug.
Official RBI Press Release: Read here

Convogent, Aivar's multi-channel conversational intelligence platform, runs voice interactions at sub-500 millisecond latency when a turn needs no backend call and under 1.2 seconds when it does, while holding more than 1,000 concurrent sessions in validated deployments. AWS Marketplace lists Convogent as an implementation service that designs and deploys "AI voice bots powered by Amazon Bedrock" directly inside a customer's own AWS account, across more than 100 languages. That deployment model, one AWS account per customer with data that never crosses into Aivar's infrastructure, is the constraint that shaped how we built Convogent's agent graph on top of Bedrock rather than around it.



Naive RAG pipelines, embed a document, store the vector, retrieve top-k by cosine similarity, generate, fail at retrieval roughly 40% of the time in production, according to a 2026 production guide covering deployments across enterprise knowledge bases. The failure mode is not a crash. It is a fluent, well-structured answer grounded in the wrong passage, which is worse than an outright error because customers trust it. On AWS, three decisions determine whether a retrieval-augmented generation system crosses that 40% line or stays on the safe side of it: how documents get chunked, which vector store holds the embeddings, and whether retrieval runs single-pass or hybrid-plus-rerank.

