The AI Laws : A Constitutional Framework

Hello everyone, I'm a CS student in a mid college and I want to go and build my career towards AI safety/security.

But, i am quite skeptical, because i dont see much jobs or internships in this part of field, and all the opportunities available seems to be for international people, mostly not flexible for indian students.

So, i would like to hear your thoughts on this- will it worth to explore this field as i dont want to waste my time on a domiain, which will remain out of reach?

Please let me know what do you think

Hello everyone, I'm a CS student in a mid college and I want to go and build my career towards AI safety/security.

But, i am quite skeptical, because i dont see much jobs or internships in this part of field, and all the opportunities available seems to be for international people, mostly not flexible for indian students.

So, i would like to hear your thoughts on this- will it worth to explore this field as i dont want to waste my time on a domiain, which will remain out of reach?

Please let me know what do you think

The Vercel Ship 26 event in New York City this past Tuesday was genuinely one of the most useful technology events I have attended, but for more than just networking purposes, as it revealed something important to me...

As AI infrastructure shifts from supporting basic chatbots toward enabling increasingly autonomous work, the focus can no longer remain entirely on making underlying models more intelligent. Just as important to this are the systems that allow agents to execute tasks, operate with in controlled environments, show users what they are doing, and act accountable to the humans using them.

_____

The event brought together founders, developers, investors, and product teams, with sessions involving companies such as Anthropic, Slack, Notion, Stripe, Supabase and countless others. Although the networking, venue (The Glasshouse, Manhattan), workshops, and demonstrations were all great, what interested me most was the repeated focus on the infrastructure required to make AI agents useful in practice: sandboxed code execution, controlled environments, real-time visibility, and human oversight prior to consequential actions being taken.

_____

My biggest takeaway from these sessions was how effective products that utilize AI can truly become when sandboxes are leveraged. The systems behind them are quite complex, but I was given this simple analogy when I was first introduced to the concept that made it much easier to grasp.

“Cleaning your house manually with a broom is like not using AI at all. It is the most manual, but least efficient process.

Cleaning your house with a vacuum is like using AI chatbots. The task becomes quicker and more effective, but it still requires a manual operator.

Cleaning your house with a Roomba is like using an AI agent with a sandbox. Not only does it have the full power of a vacuum, but it can also understand your home’s layout, move autonomously, and recharge when needed.”

This understanding makes it clear why so many companies are constantly adopting AI systems, as they can reduce the amount of time spent on repetitive tasks and allow employees to focus on tasks of greater importance.

_____

However, it goes without saying that this also presents countless risks. I think many of those risks will create new jobs for humans in oversight, law, compliance, technical architecture, security, and product design, which inherently combats the commonly presented issue of AI taking away jobs.

You could have thousands of AI agents constantly cross-checking one another, but the core problem persists as none of them actually “understand” concepts in the same way a human does. Having them verify one another can be like taking an exam while a room full of your own clones checks your answers, because every clone may still be limited by the same studying, assumptions, and gaps in understanding.

That limitation is critical in high-stakes use cases where people’s finances, legal representation, medical treatment, and other serious decisions are involved, which I could personally attest to having legitimate experience in such myself. Despite the shared consensus that AI is ruining the job marke (which I agree with to some degree) I think we will eventually come to accept where things are going and how many tasks are becoming more efficient. The focus will begin shifting toward ensuring that this efficiency is not achieved at the cost of accuracy, security, or accountability.

_____

I understand that the analogies above are oversimplifications and that output-validation agents already exist, but my counter to that would be:

at what point does it become more cost-effective to have countless agents checking one another compared with having one human review the output of an AI?

Runtimes continues to be one of the biggest bottlenecks in AI advancement, as capability is beginning to outpace scalability because of compute costs. Adding more agents to verify the work of other agents may improve reliability, but it also increases the amount of infrastructure, time, and compute required to complete what may have originally been a relatively simple task.

_____

You may be wondering how any of this connects back to Vercel beyond the opening paragraphs, but that was exactly what made the event so interesting.

Vercel was not simply discussing what agents could theoretically become. A major focus was eve, its new open-source frame work for building / operating production AI agents. Eve packages together an agent’s instructions, tools, workflows, sandboxed execution, subagents, evaluations, and approval requirements into a single space, providing the infrastructure needed for agents to execute code, work autonomously inside controlled environments, and most importantly, remain visible to the humans overseeing them. In the simplest way possible; it does all of the work but prior to acting it presents its exact plan to the human operator so as to avoid drifting into harm's way or out of scope.

The human-in-the-loop (aka. HITL) approach that eve is built around addresses one of my biggest concerns with agentic systems. Rather than blindly assigning an agent a goal and hoping the final result matches what you intended, approval steps allow users to understand what the agent is planning to do before consequential actions are taken. I still believe drift can occur once the agent begins implementing that plan, but keeping the human on the same page as the system creates a much stronger balance between autonomy and accountability.

______

TL;DR: The most important thing I took away from Vercel Ship 2026 was not simply what individual companies are building, but how AI infrastructure is changing as the industry moves from chat-based assistance toward increasingly autonomous work.

The next stage of AI development is not just about making models more intelligent, it's about building the infrastructure that allows agents to execute code, operate inside controlled sandboxes, stream their work in real time, and pause for human approval before taking consequential actions.

My biggest takeaway was that human oversight may not be a temporary limitation that disappears as agents improve. In high-stakes use cases involving finances, law, healthcare, security, and other serious decisions, a human-in-the-loop (aka. HITL) approach may be what allows greater autonomy to remain practical, secure, and accountable in the first place.

The event gave me a much clearer understanding of how companies such as Vercel, Anthropic, and others are approaching the balance between capability, scalability, security, and human control.

Beyond the formal sessions, being in NYC made the experience even more valuable because I had the opportunity to speak with founders, venture capital professionals, developers, and people working across several areas of technology. Those conversations gave me new perspectives on building products, raising capital, managing risk, and understanding where the industry may be heading next.

___

❓ QUESTION ❓

With that said, I’m curious to hear the opinions of others in this subreddit and where they think AI is headed.

What issues do you foresee becoming the biggest blockers?

Whether it is compute costs, RAM shortages, a plateau in its capability progression , the security and accountability risks discussed above, or an entirely different concern, I’d be interested to hear what you think.

--

*[*p.s. no this was not made with AI, I took a lot of time in writing as much detail as possible to get my actual opinion and thoughts on this topic across instead of making a slop post]

I kept running into the same problem: AI coding agents (Cursor, Claude Code, etc.) would confidently rewrite a function without knowing what else in the codebase depended on it. One "simple fix" would silently break three other modules downstream.

So I built a tool that gives agents a structural map of the codebase before they touch anything — call graphs, blast radius analysis, and architecture boundaries, computed locally with no cloud calls.

A few technical details that might be interesting to this crowd:

• Delta sync via SHA-256: instead of re-indexing the whole repo on every change, it hashes each file and only re-parses what actually changed. Makes it usable on large repos without a multi-minute wait every time.
• Hybrid graph model: combines a structural graph (tree-sitter based, across Python/JS/TS/Java/C++/Go) with semantic embeddings, so queries can be answered by structure ("what calls this function") or by meaning ("where's the auth logic").
• Blast radius: before an edit lands, it traces downstream callers/dependents so you (or the agent) know what's at risk.
• MCP integration: exposes this as context directly inside Cursor/Windsurf/Claude Code, so the agent gets the graph without you manually pasting file contents.

It runs fully offline — no API keys, no data leaving your machine, works air-gapped with a local LLM if you want it fully isolated.Wanted to share it here since blast-radius-aware tooling for AI agents seems like a gap in the current OSS landscape.

Code's here if you want to poke at the architecture or the parsing layer: Github

Happy to answer questions about the graph construction, the delta-sync design, or tradeoffs I hit along the way.