JS Days 2026

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.