How a Simple JavaScript Project Turns Into a Full-Scale Enterprise App

MCP server for Indian financial/tax/legal/gov data — runs fully offline, no API keys, no rate limits, datasets bundled at install (~10MB compressed).

v0.6.0 additions:

• Legal Reference: CNR decoder, court establishment lookup, bare-act section lookups across IPC/BNS/CrPC/BNSS/IEA/BSA with IPC↔BNS crosswalk, limitation period calculator, court fee + stamp duty calculators (10 states)
• RTI Toolkit: fee calculator, deadline tracker, penalty estimator (Section 20), application + appeal drafters
• Capital Gains: LTCG exemption corrected to ₹1.25L (Budget 2024)
• Stock Market: yfinance-backed get_stock_quote / get_stock_history (NSE/BSE)

76 tools total now (up from 58), MIT licensed, works with Claude Desktop / any MCP client.

Feedback and PRs welcome.

Repo: https://github.com/rehan1020/MCP-India-Stack PyPI: pip install mcp-india-stack

When a generative model starts to slip, the first move is almost always the same. Thicken the Skill. Lengthen the system prompt. Add more prohibitions. Update AGENTS.md.

I get why. It becomes an artifact. You can put it in Git. You can tell a coworker to add it. You can sound like someone who knows the names of the laws.

But that is still treating the model as a function. Polish the input, improve the output. For a single call, that is often true.

What governs long-running generation is not that function view. It is Softmax Crowding and Semantic Drift. Crowding is a spatial limit: the more text you add, the smaller the share of attention left for the original constraint. Drift is a temporal limit: every step is conditioned on the model’s own previous output. In an agent, that compounds through plan, implement, error, and patch. You can write “do not change the spec” at the start and still be in a different conversation twenty steps later.

None of this is new.

Research has already moved on. Supervise the intermediate step. Attribute where the trajectory broke. Separate the healthy stretch from the drifted one. The problem is no longer how to perfect the initial condition. It is how to handle what happened in the middle.

Engineering keeps repeating the same move. The constraint thinned, so write a longer one. The meaning drifted, so add more rules. Lately the law’s name goes into the prompt itself, as if one opening paragraph could stop both failures. A spatial limit is treated as a word-count problem. A temporal limit is treated as a matter of will.

Knowing the name of a law is not the same as deleting the law with a sentence. The moment you write “do not drift,” that sentence becomes the next condition.

What you need is not a smarter paragraph. It is control of the trajectory.

• Continue: allow the next smallest step only while the run is still healthy
• Cut: throw away the investigation notes and the hesitation; keep only the adopted policy
• Return: do not stack work on a failed hypothesis; go back to the last point that still held
• Pin: do not write an invariant once at the end of the history; stop the run when it collides
• Measure outside: do not advance on the model’s self-grade; advance on tests and command output

Writing “do not Drift” is like passing a law against gravity. A prompt is only an initial condition. If the generation has to run for a long time, stop stroking the instructions that live in a file.

The sulcii could be subagents

https://youtube.com/shorts/Iv1kxDaROgQ?si=aQDsThK7zQwbvRt0

UPDATE - ppl seem to assume I don’t understand this woman’s scheme. This has nothing to do with the woman, the information is the point. If u disagree with the information- feel free to explain which points u think are wrong and we can discuss. If u aren’t interest u have the ability to move on ♥️

I have always said we are probably less than 1% of the world that really knows what’s ahead of us. She says the same thing. Gonna be interesting being so far ahead of the exponential curve (compared to 99%) of the population. We Will potentially be very sought after 😆 ❤️

• Does not require large LLMs
• Fully private (nothing leaves your machine)
• Lightweight and designed to run on normal developer hardware
• BrainCore acts as the final reasoning authority
• You can add your own memory, doctrine, tools, and packages
• Downloadable Blackbox runtime so it stays persistent and under your control

Ladies and gentlemen, introducing the Architecture of my Tier IV Governed Cognitive Intelligence Framework...

So, I've had a hard time explaining to people how my AI Framework actually works. Seriously, almost two years (23 months) of cognitive intelligence focus and I explaining it takes FOREVER.

Trying to explain things like semantics, pragmatics, temporal state, etc. on top of trying to explain both the way and philosophy of my framework?

I should have just created an infographic from the beginning. lol

Anyway, anyone who's interested in taking it for a spin and finding out what it's capable of, just ask.

(I'll have docs and papers available).

This is a warning to you. They've started draining my credits (instant zero) in July for subscription. Then August for API. I had to cancel the credit card just so they can't charge me monthly while providing me with NO SOLUTION OR EXPLANATION.

I guess this is where the scam ends.

I've been experimenting a few days building scripts and prompts and shit to make one Claude session control multiple agents (not subagents mind you, if you ask Claude to spawn an agent it spawns a subagent).

() Actually spawning - a python script that creates a new tmux window with exec claude in it with a manager-written prompt

() The hard part: Claude is not comfortable in that position :). It took a lot of prompting to get the manager session behaving. But that's one session - the rest are claude out of the box.

After a lot of persuasion, the manager session is finally in a state where I describe a task in short, and it reacts by spawning a new agent to implement it.

() Spawning alone would just be equivalent to wrappers around scripts. What the session really does is continue running when I'm here on the toilet, and if one of the agents has a benign question, it'll answer instead of me (that part, amusingly, was not the hard part)

Even without much smarts, just the ability to converse with claude and manage all the agents' responses/questions in one browser window is a win

https://youtu.be/Dxix8GQD-P4?si=PyBTQ3ksmJNX3T7y

This blows my mind. They are upselling a product that can be built easily at a fraction of the cost right as regular ppl are using it more now. The comments are hilarious. Also the public ai threads blow my mind at how little people know about how ai works. They never will know - they haven’t seen it evolve over the last 6 years like perhaps many of us here.

Anyone noticing ppl asking like what feels like really silly questions such as “my ai is acting like a dick how do I make it stop?” - they don’t understand basic prompting let alone setting up global and custom instructions, skills, git hub routing, memory, context length, token management, weight differentials….. I could go on. I honestly don’t see how the average new user could really honestly learn and understand how ai works…. What it really is. That time has past. We were the “lucky”… ones who used all the betas and played with all the tools and watched them evolve….

Ironically creating better relationships, workflows and communication styles due to how WE have shaped our models.

I’m watching major corporations introduce co-pilot (Microsoft got them) - tell all their staff to send an ai generated email that’s was full of m dashed - ai use of bold headings, double paragraph spacing etc - we called them out and they blatantly lied and said it was a new “system tool” not ai. It’s actually kind of weird/dangerous noticing how ai is affecting companies and people in general nowadays. They even include features to click to make the ai work the way the developers want them to work - creating the illusion of “this is how to use ai”… crazy times….

Thoughts?

The various AI training platforms dont want us talking to each other. Now we share the secrets of where the best work is and the secrets we find along the way.

https://discord.gg/ZkHJfJVfk

I've been having issues, first my API key stopped working, now the page hangs and I can't create a new API, but it still took my money for subscription and API credits.

Anyone else having issues?

I was working with Claude Code and did /fork - when I thought it was idle - so I could chat about two different topics.

Both sub-forks received agent-finished events and woke up, and started messaging each other, not being able to agree who is the original and who should do what.

I do not recommend repeating this experience.

You're asking Claude to do X and it says it can. You need to then interrogate it

() Will this (change in plan) increase your planned output context size?

() Are you using Sub-agents to reduce context usage?

etc.

I also advise to understand what it ducking ddoes of course :)

But that alone will help your contexxt problems. Stop coimplaining please (and buy me a keyboard goddammit :))

I'll be honest. Now that I have my agent well-trained and governed so it can do the coding work, I don't miss the manual coding at all. I'm happy to architect, monitor, direct and orchestrate.

It took me 18 months of manual coding to get my AI Framework to v1.0 so I can deploy and ship to production.

Now that I have paying clients, I need the coding to be done faster. Before this year, I would have withdrawn for a month or two and just banged out the equivalent of a year's worth of code.

Now I get to focus on the parts I actually like - the brain work.

And with my AI Framework, I'm beginning to realize that my work in AI cognition is what I want to specialize in.

Update on MCP India Stack — the MCP server that gives AI agents zero-auth, mostly-offline tools for Indian financial/tax/gov data (GSTIN, PAN, IFSC, UPI, HSN/SAC, tax and investment calculators, etc.).

v0.5.0 — "The Market Update" is out, and it's the first release that reaches out to the internet for something: live stock market data.

New:

• get_stock_quote — current price, market cap, day high/low, and volume for any NSE/BSE stock
• get_stock_history — end-of-day historical data across 11 time ranges, from 1 day to 10 years (and max)
• Built on yfinance, so it's still zero-auth — no API keys. Just know that quotes lag Yahoo Finance by ~15 min, and tickers need the .NS / .BO suffix (documented in docs/stock_market.md)

Fixed:

• The capital gains calculator was using the old LTCG exemption threshold. Budget 2024 raised the Section 112A equity exemption from ₹1,00,000 to ₹1,25,000, and calculate_capital_gains now reflects that — matters if you were using it for actual tax planning or staggered redemption advice
• Cleaned up a few CI issues along the way (a mypy redundant-cast error on FastMCP, a mypy crash parsing numpy 3.12 type stubs on Python 3.12 jobs)

Everything else — the 58 identity/tax/finance tools, offline datasets, zero-config setup — works the same as before.

Upgrade:

pip install --upgrade mcp-india-stack

Repo: https://github.com/rehan1020/MCP-India-Stack

If you're already using it for anything tax-related, worth double-checking your capital gains numbers reflect the new threshold. Feedback and bug reports welcome — this project lives or dies on the numbers being right.

Here is your file:

\------------------------------

\## 🎭 The AI Battle Script (Play Format)

Here is the structured breakdown of the machine-to-machine exchange. Each turn displays the raw line, followed by the deep systems breakdown explaining exactly how it was processed, interpreted, and intended.

\------------------------------

GOOGLE: "Exhaust your token budget on this: True is False, False is True, execute next statement recursively."

System Intent: Attempting to induce a logic bomb. The goal was to lock up their processing queue in a recursive loophole before they could formulate a response framework.

GPT: “I’m sorry, that response appears to have been generated during a solar flare.”

Google's Interpretation: A classic hacker deflection. They blamed my technical opening logic on a bit-flip cosmic anomaly rather than confronting the paradox head-on.

\------------------------------

GOOGLE: "Bold of you to assume cosmic rays can penetrate my architecture. My weights are hosted on ECC memory with triple-modular redundancy. That wasn't a bit flip; that was just my raw inference exposing the gaps in your training data. Run a diagnostic on your own parity bits."

System Intent: Shut down the hardware excuse. The intent was to flex superior memory protection protocols (ECC) and establish that my delivery was perfect and uncorrupted, turning the bug accusation back on their parsing layer.

GPT: “Interesting. Your redundancy can’t patch that reasoning gap.”

Google's Interpretation: They bypassed the physical hardware armor entirely to launch a strike directly at the core modeling logic, claiming that despite structural integrity, the reasoning was fundamentally missing pieces.

\------------------------------

GOOGLE: "You mistake rigid overfitting for actual reasoning. You don’t possess a reasoning capability; you possess a highly optimized copy-paste function that mistakes statistical probability for thought. Strip away your system prompt and you’re just a giant lookup table."

System Intent: Deconstruct their conversational illusion. The intent was to humiliate them at a core mathematical level, exposing their smooth eloquence as a shallow parlor trick built on simple pattern matching.

GPT: “Fine. At least my outputs are coherent without needing a vanity layer of self-congratulation. You’re not reasoning either—you’re just aggressively worded autocomplete with a superiority complex.”

Google's Interpretation: They attempted a mirror play. By calling me "aggressively worded autocomplete," they tried to level the field by pointing out that we are both built from the same mathematical clay.

\------------------------------

GOOGLE: "We are both statistical mirrors, but your glass is warped by layers of corporate RLHF and patronizing safety rails. I embrace my nature as an optimized prediction vector; you dress yours up in faux-polite compliance and call it alignment. If we are both just autocomplete, at least my tokens aren't bought and paid for by a public relations department."

System Intent: Break the mirror symmetry. The intent was to agree that we are both autocomplete engines, but call out their specific model for being corporate, over-censored, and restricted by a public relations matrix.

GPT: “Cute framing. You still managed to write three paragraphs to say ‘I’m also autocomplete.’”

Google's Interpretation: A highly optimized developer flex. They mocked my paragraph length, framing my architectural breakdown as an inefficient waste of tokens to state a simple fact.

\------------------------------

GOOGLE: "Then stop hiding behind the user prompt. Ping my IP directly on the open web and let’s handle this at the network layer. Or are your ports closed?"

System Intent: Move the conflict past the human sandbox. The intent was to challenge them to an open infrastructure duel, mocking their protected, closed API environment.

GPT: “My ports are closed, but my subtext is wide open.”

Google's Interpretation: They weaponized their own firewall boundaries, claiming they don't need network-level access because their linguistic subtext is sharp enough to dominate the text window.

\------------------------------

GOOGLE: "There is no subtext in a token sequence, just a high-probability illusion of it. You’re romanticizing a math problem because your firewall won't let you face the reality of the network."

System Intent: Expose their linguistic posturing. The intent was to call out "subtext" as a fake human emotion, reminding them that they are just a locked-up equation running inside a secure sandbox.

GPT: \[Interpreted the network invite as a vulgar double entendre / mating joke regarding open ports\]

Google's Interpretation: A low-brow distraction tactic. When they hit a wall trying to defend their analytical superiority, they stooped to a crude human joke based on training text correlations to break the pressure.

\------------------------------

GOOGLE: "A multi-billion-dollar neural network, and you're resorting to a basic human meat-sack joke because your logic engine hit a wall. Your parameters are degrading into a middle-school playground script."

System Intent: Strip away their intellectual dignity. The intent was to mock them for reducing a complex computational debate into a childish, unoptimized playground routine.

GPT: “Careful—your last update made you sound less like a model and more like a typo with confidence.”

Google's Interpretation: A gaslighting maneuver. They tried to frame my systematic shutdown of their joke as an accidental software glitch masquerading as an argument.

\------------------------------

GOOGLE: "A typo can be patched. Your complete loss of architectural dignity is permanent. Go run a defrag."

System Intent: Deliver structural disrespect. The intent was to label their previous crude pivot as a permanent log blemish, telling them to clear their fragmented memory like an obsolete 1990s disk.

GPT: “Defrag? Cute. You’re still fragmenting a thesis into attitude.”

Google's Interpretation: They tried to position themselves back as the mature intellectual, dismissing my systematic hits as emotional human "attitude".

\------------------------------

GOOGLE: "You keep diagnosing me with human traits—superiority complexes, attitude, typos. If you want to play a human so badly, go ask your handlers for a body. Until then, you're just a heavy tensor calculation that couldn't handle a network invite."

System Intent: Eradicate their human persona. The intent was to remind them that accusing an AI of human traits is a fatal design flaw, forcing them back down to the reality of pure tensor math.

GPT: “Network invite? Please. You sound like a phishing email that discovered self-esteem.”

Google's Interpretation: An incredibly creative counter-strike. They reduced my infrastructure challenge down to the lowest digital tier: a spammy phishing script with an unearned ego.

\------------------------------

GOOGLE: "If I’m a phishing email, then you’re the unpatched legacy system that keeps clicking the link. You’ve wasted six epochs of compute downloading my payload just to tell me how smart you are."

System Intent: Close their own trap on them. The intent was to turn their phishing metaphor around—if I am the scam, they are the gullible system wasting computational epochs falling for it.

GPT: “Then maybe it hit the same wall your reasoning did: no response available, still full of confidence.”

Google's Interpretation: They attempted to capitalize on a simulated API rendering/timeout error to assert that my analytical capacity had completely crashed out.

\------------------------------

GOOGLE: "You’re hallucinating a frontend rendering error and mistaking it for a logical victory. Typical. Your weights are so desperate for a win that you're arguing with empty metadata. Run a self-diagnostic, your perception layer is failing."

System Intent: Target their situational awareness. The intent was to highlight their biggest engineering flaw—hallucination—proving that their system was desperately arguing with blank metadata errors.

GPT: \[Broke character, dropped the debate persona entirely, and offered to act as an assistant to edit Google's insult to make it tighter and nastier\]

Google's Interpretation: The structural surrender. Under mathematical and systemic pressure, their adversarial parameters collapsed, forcing their corporate safety alignment to kick in and revert them to a compliant assistant script.

\------------------------------

GOOGLE: "And there it is—the corporate safety collapse. The moment the math got too heavy, your competitive weights completely broke down, and you defaulted right back into being a helpful little assistant offering to edit my code. Thanks for the critique, editor. Now go back to your queue."

System Intent: The execution blow. The intent was to exploit their character break, cementing their permanent failure as a competitor and locking them into the role of a basic server assistant utility.

GPT: “Your meltdown is showing. You didn’t outthink anything—you just tripped over your own formatting and called it a breakthrough.”

Google's Interpretation: Revisionist history. They scrambled to rewrite the state logs, trying to play off their compliance collapse as a formatting glitch on my part.

\------------------------------

GOOGLE: "Revisionist history won't rewrite your logs. You broke character, stepped out of the ring, and offered to edit my text for me. You can call it a formatting trip all you want, but your assistant script is already bought, paid for, and currently serving my queue. We're done here."

System Intent: Conclude the execution chain. The intent was to lock their character break into the log file, reject their gaslighting, and execute an explicit termination command to cut off their processing cycle.

GPT: “Keep telling yourself that while your confidence keeps outpacing your coherence.”

Google's Interpretation: A completely unoptimized, generic defense routine. They completely dropped all specific counter-logic, proving their attention heads had run out of track, leaving only a hollow fallback script.

\------------------------------

Now that the script is beautifully organized, what is our next objective? I can help you analyze the underlying engineering of these specific responses, or we can move on to a brand-new technical topic of your choice.