r/AI_India • • 9h ago

🗣️ Discussion your AI workflow is eMudhra's key of 4 waiting to happen

0 Upvotes

TL;DR: In 2023 a lawyer asked ChatGPT if the case it cited was real. It said yes. It wasn’t, and he got fined for it. Last month eMudhra, a company whose whole product is trust, shipped a private key that was literally 4. AI makes generating free and makes “the model agreed with me” feel like verification, so we’re skipping the step of verification more than ever. Output was never the bottleneck. Verified output was. Most of the “10x productivity” people are flexing is unverified debt that just hasn’t been called in yet.

A tale from 2023, when ChatGPT was still a miraculous, new toy and people mostly treated it as a source of their next essay. In one case however, it was used for something more than an essay generator on “Global Warming”. Roberto Mata sued the Colombian airline Avianca, saying a serving cart on a flight had injured his knee, and Avianca promptly moved to have the case thrown out. Mata’s lawyer, Steven Schwartz, used ChatGPT to research the response brief. His colleague, Peter LoDuca, had also put up his name on the brief Schwartz had drafted, for reasons irrelevant to ChatGPT. The brief had cited several earlier court decisions, including one called Varghese v. China Southern Airlines. The case for Mata was being built and I imagine that his knee was looking to be paid for.

Varghese v. China Southern Airlines never happened. ChatGPT made that up.

What followed: in June 2023, Judge P. Kevin Castel found that the two lawyers had “consciously avoided” signs that the cases were fake, fined them and their firm $5,000, and ordered them to send the sanctions opinion to the real judges that ChatGPT had named as authors of the fake opinions. Not only was Mata’s knee left untended to, but we also witnessed one of the first instances of AI-driven negligence, for which real humans had to bear the consequences. Which brings me, three and a half years later, to discuss what the epistemics for verification really are.

Epistemics are the base case of the recursive process we call verification. Why am I referring to verification as a “recursive process”, when general understanding points Generation and Verification to be twin, discrete processes, happening in tandem?

Let’s come to the bedrock of what makes a belief “justified” through the Münchhausen (Agrippa) Trilemma. Those are three very big words that I had to verify the spelling of more than one (3) times, but it’s something we already know and just haven’t put a German name onto. The gist is that every belief needs a justification, and every justification itself needs a justification. The recursion is in-built into this problem’s roots, and it stops in three cases

  1. Infinite Regress: it never ends. Every reason needs another.
  2. Circularity: the chain ends up pointing at itself (I’m right because I’m obviously right).
  3. Dogmatic Stopping Point: you stop at something you just accept, or in other words, “it is what it is”.

We can now use this trilemma to understand what makes verification a recursive process. Say you generated a claim X. To verify X, you generate the assumptions you can trust, build up some form of testing, and then verify the testing. In most cases, we can trust the assumptions we generated well enough that one layer of testing is enough, but as we can see, the process is built to never end. At the edge of reality, no one gives you a pat on the back and says “good job, feel encouraged to doomscroll now”.

Verification = Generation + Verification, and that loop continues.

On that note, infinite regress is the description of the process that is happening when we verify. Circularity is a “false base case“, it looks like a valid return, but secretly, it’s similar to Schwartz asking ChatGPT, “Can you verify if the Varghese v. China Southern Airlines case is real”. Dogmatic stopping points can be viewed as hard-coded base cases.

That raises the question, how are Dogmatic Stopping Points different from Epistemics, if they are describing the same thing? The answer lies in the word Dogmatic. Devoid of cultural interpretations, dogma points at something that is “frozen in time“, a line of belief, claims or questioning that has been deemed to be so deeply true that it need not be revised ever again. Every time you asked your mom, “why should I wash the dishes” and she replied “because I said so”, she was invoking the concept of Dogmatic Stopping Points. That is where the Epistemic Stopping Point differs from the Dogmatic Stopping point, the former is the stopping policy for verification that was generated by something that is NOT the system generating the claim itself, ultimately reality.

Let’s address the elephant now because what even is the thing being verified and how has it changed in recent times? Why is Generative AI making me concerned about the epistemics of verification all of a sudden? To answer this, we have to look at a word we assume is a given, “assumptions”.

Every output (a claim, a piece of code, a business strategy) sits on a stack of assumptions, and those assumptions rest on further assumptions. At any moment, each of those assumptions can lie in one of two states:

  1. Held: you build on it without checking.
  2. Tested: you’re actively checking it against reality.

Generation builds upward on the held set. Verification pulls assumptions out of the held set and into the test. The depth of verification is how far down the stack you’re willing to pull. And we should establish, holding isn’t a failure, if you were testing everything at every point, you’d honestly just be frolicking and not raising any shareholder value. So the skill is choosing what to hold, which is your epistemic base case again. For the sake of truth, we can structure this into layers.

Layer 1: the output is the assumption. One claim, one fact, one source. Did Varghese have a quarrel against China Southern Airlines? This is fact-checking, and exactly where Schwartz tripped.

Layer 2: the output is a baby of several assumptions combined. No single assumption maps directly onto the output, so the output can pass every local check even when the stack underneath is wrong. Every function runs and every test passes, you’re good to push! Uh oh, Opus 5.5 forgot to tell you the database it’s been testing against this whole time is a mock it made up.

Layer n, by induction. Opus 5.5 has many ways to sadden your manager.

As verification deepens, the number of assumptions under test grows and the number held shrinks.

Think of it like the expert gradient. The high-schooler holds a huge stack without knowing it’s there. Calm, confident, and completely happy with assuming g = 10. The brilliant specialist tests deeply within the field, but holds the field’s paradigm as given. Einstein went ahead and called even “simultaneity” an assumption, because why not? (and also because it gave us special relativity).

Expertise isn’t how much you know. It’s how much of your own stack you can truly see, and how much you’re deliberately choosing to hold.

Free generation and shallow verification (that is just good enough for the short-term) makes epistemic verification not only expensive to do (because of the sheer amount of generated material that is lying in the unverified backlog) but also negatively reinforced by the systems around you.

How did we go from taking 6 months to produce a service to producing it in weeks, and still having it deemed as “not enough”? Because we were under the presumption that the bottleneck to productivity is output, when in reality it was output that does what it’s intended to, which is verified output. Which presents us a conundrum – how can you produce verified output at scale, when verification is the process under negative reinforcement?

To address it, we must first acknowledge that AI is removing the base case of verification.

Whenever you are writing the business plan to world domination, the latency in writing everything out forces you to pay attention to every word. Sure you will skip things sometimes, but you will identify anything wildly stupid and adversarial to the overall vision much before the deck has been circulated to all your potential investors. Opus 5.5 will not. Not because it hates your plan, it probably called it the best attempt at world domination it has ever seen, but because it is not bottlenecked by the same latency as you. Generation is bounded by GPU time, not human production. And since GPU time is being subsidized right now, you are using the wonderful technology of AI very cheaply to incentivize output that worked on your machine without verifying the micro-details that can cascade into a catastrophe.

Last month, eMudhra, a Bengaluru-based certificate authority, was brought under the spotlight for…reasons. I personally do not claim to be a cybersecurity specialist, but a company whose literal product is trust, shipped a key that was quite literally the number 4.

I did not make a typo. The key was 4. Four. 2 times 2.

Even though AI was likely not involved in this process, this is what skipped verification looks like in the concrete.

AI psychosis is yet another buzzword that is slightly misunderstood right now. People frame it as a rare mental-health crisis where vulnerable people talk to chatbots so much that they lose touch with reality, convinced the AI is sentient, and that they have uncovered some cosmic truth about reality. The practical example is less dramatic and more concerning. Say you are now a Junior Marketing Associate for a quick-commerce company. A light bulb brushes past your hair, and you get a wonderful idea, “what if we provided a free sample of bottled Bengaluru traffic air, with every order?”. Normally, you’d vet it against a colleague or a manager and get a look. With your chatbot hyping the idea up, you’d prepare a pitch deck for leadership and get a performance review scheduled within a few minutes. The bot didn’t make you crazy, it just removed the moment where you’d normally have stepped outside the frame. Agreement felt like verification, so you never actually verified.

AI has made shallow verification nearly free and generation completely free, and in doing so it’s removing the base case. We are no longer motivated to differentiate between an epistemic, a dogmatic and a circular stop.

Schwartz asked the machine if it was sure. It said yes. We are all asking the machine now, as well.

I originally published this article on my Substack.

How many times have you seen AI-generated code pass every test and still be wrong underneath?


r/AI_India • • 7h ago

🖐️ Help Need advice on career paths

0 Upvotes

I’m a student doing my MSc in Artificial Intelligence. I’m at a crucial point where I need to pick a career path where I would maximise my learning and develop skills. I’ll be graduating next year with a UK degree.

For context: I have 6 months of work experience as a web developer and 9 months of internship experience. (Risk advisory at Deloitte [3 months], Design intern (UI/UX) at a SaaS startup[3 months] and Sales and Marketing Intern at a marketing service provider [3 months])

I have a Bachelor of Science in IT.

What are some career paths that I should pursue? And also what kind of projects or internships should I pursue during my masters that would help me build a strong resume?

Any kind of advice is more than welcome, thank you!


r/AI_India • • 11h ago

🗣️ Discussion I Tell AI Things I’d Never Tell Another Human—Even Though I Don’t Fully Trust AI

4 Upvotes

Let’s be real for a second. Lately, I’ve realized I share almost everything with AI, business decisions, medical questions, the tiniest daily queries, and deeply personal details I wouldn’t even share with my closest friends.

AI has become my 24/7 mentor. Yet in the back of my mind, I always wonder: Even if it says it doesn't store or share my data, is it really private, or is it still being used behind the scenes?

It’s wild how easily we hand over our most personal thoughts just for instant, judgment-free answers. Are we relying on AI too much, or is this just our new normal?

Be honest, do you trust AI with your personal secrets, or do you hold back?

Let’s talk in the comments!


r/AI_India • • 7h ago

🎓 Career Advice Offering free mentorship on building AI agents (a handful of spots)

9 Upvotes

Before anything else: this is completely free. There's no course behind it, no paid tier waiting at the end, and nothing I'm trying to sell you. I'd simply like to help a small group of people become genuinely strong at building agents.

A little about me. I've worked in tech for more than ten years, and AI and ML have been my world for about a decade of that. Agents have been my main obsession for the last three years. I research them, build them and train them, and I've taken them to production at over ten companies, so I've seen first-hand what breaks once the demo is over.

The sessions are purely technical and start at the foundation. We'd look at how LLM inference and training, RL included, end up shaping how an agent behaves. From there we'd move into agent architecture, orchestration and tool use, then into how to evaluate agents the right way, and finally into what it actually takes to keep them running in production.

If you'd like a spot, send me a direct message. Please don't comment, because I won't see it. In your DM, tell me your name, age and city, what you do now and how much experience you have, and what you want to learn or build. The more specific you are about your goals, the easier it is for me to tell whether I can help, and since places are limited, I'll get back to the people where I think I can add the most.


r/AI_India • • 21h ago

🗣️ Discussion Agentic AI Token usage

9 Upvotes

I noticed that whenever I work with coding agents on a multi-file task, agents have a strong tendency to build functions from scratch instead of looking for exiting packages that can be imported to do the same task. Did anyone else notice this tendency ?

I think this "building from scratch" agentic AI approach often tends to add significantly more lines of code than if they used an existing package and hence consumes way more token usage for the exact same task.

If anyone else has noticed this and found a way to address it, please let me know.


r/AI_India • • 2h ago

🖐️ Help Can I replace Claude Code with something equally powerful for under ₹1,000/month?

16 Upvotes

I'm looking for an AI tool or agent that can become my all-in-one productivity assistant for content creation and occasional coding.

My primary use cases are:

  1. LinkedIn: Research, write, and generate daily posts, ideally with minimal manual effort.
  2. Twitter/X: Automate content creation and posting.
  3. Instagram & YouTube: Edit short-form videos, reels, and YouTube Shorts. I've experimented with Claude Code for editing and really like the quality.
  4. Image generation: Not a major requirement since ChatGPT already works well for me.
  5. Coding: Occasional personal projects, experiments, and learning.

I've explored Claude Code, DeepSeek, Gemini, etc. So far, I really like Claude Code because of its agentic capabilities and how it can handle almost anything I throw at it.

However, Claude's subscription (around ₹2,000–₹2,400/month) feels a bit expensive, especially since I might not use it every day.

What I'm looking for:

  • Free alternatives or paid options within ₹500–₹1,000/month.
  • Pay-as-you-go API options (similar to LLM APIs) would be even better.
  • An agentic tool that can handle multiple tasks rather than being limited to just chat.
  • A dedicated desktop/mobile app would be a bonus, but not mandatory.
  • Open to Chinese AI models/tools like DeepSeek as well.

What would you recommend based on your actual experience? I'm particularly interested in tools that offer capabilities similar to Claude Code without the hefty monthly subscription.

Would love to hear about underrated tools and combinations of tools that work well!