Rohan Mehta (@RowRowRoUrBoat) header
Rohan Mehta (@RowRowRoUrBoat) profile picture

Data scientist, Token Engineer, MSc Physics + BE Electronics @BITSPilaniIndia

Mumbai, India
Joined November 2018
Photo by Rohan Mehta (@RowRowRoUrBoat)Photo by Rohan Mehta (@RowRowRoUrBoat)Photo by Rohan Mehta (@RowRowRoUrBoat)Photo by Rohan Mehta (@RowRowRoUrBoat)Photo by Rohan Mehta (@RowRowRoUrBoat)Photo by Rohan Mehta (@RowRowRoUrBoat)
30 people. 3,464 doors. One weekend in Phoenix. 📷 That's 115 doors per person. THINK YOU CAN DO BETTER? We'll be in Detroit, Michigan on the weekend of the 17th, and San Antonio, Texas on the weekend of the 31st of this month. Me and @MrMouton and @imreallyimprtnt will also be at both events doing live shows for The Blue Wave. HOTEL ROOMS PROVIDED IF NEEDED, SIGN-UPS BELOW ->
30
159
2
2,789
54,751
Rohan Mehta retweeted
Reminder that Jev is a "system one" model. It does not reason. It categorizes. It is nearly impossible to know how "complex" a task is purely from a prompt. You need to understand the system the prompt is made in, the tools the agent has access to, and the complexity of what the agent has to work around to complete the work. Jev has none of this context. Literally zero. It cannot know how hard it is to make a change in your codebase. If you ask an agent to "port this to Rust," it doesn't know if the codebase is a 100-line TypeScript file or if it's a million-line complex application. It doesn't know if your request to fix a bug touches complex pieces of your application or if it's a simple two-line change. Jev is awesome, but it is not built for this. In order to know how much thinking a task requires, you have to think. Jev does not "think".
44
26
15
821
95,229
Rohan Mehta retweeted
"just answer yes or no"
143
575
101
9,362
558,490
Rohan Mehta retweeted
We've raised $1.8M in pre-seed funding to navigate the ocean. A new kind of compass: quantum sensors read Earth's magnetic field; AI turns it into position. The Universal Positioning System.
49
52
23
226
23,472
This meeting could have been a .md file
1
6
413
Rohan Mehta retweeted
Never forget that the Indian government had blocked GitHub & Pastebin in 2014 and one government official said that: > These are all providing very dangerous kind of cut and paste services. You can take code, cut it, paste it, remove it, delete it.
32
261
9
3,522
99,726
Rohan Mehta retweeted
life imitates ai slop
1
1
6
219
Rohan Mehta retweeted
unironic productivity hack for 2026 use a pencil and paper to write down your ideas
200
102
32
2,811
104,076
Rohan Mehta retweeted
Built to be extensible by design and owned by the community. Add one json file to create an entry and that's it (the contributing card has everything you need) Project: llmdict.is-cool.dev/ Github: github.com/aditya-pola/llmdi…
1
1
1
116
Rohan Mehta retweeted
The instance that I faced was parsing gemma model tags (E4B? A4B? IQ?). If only I had a quick lookup for the all the vocabulary we come across. A dictionary perhaps... An LLM Dictionary if you will.
1
1
1
81
gm
48
733
40
12,848
323,787
Rohan Mehta retweeted
GPS isn’t broken. It’s just vulnerable. Today, we’re proud to share a glimpse into what we’re building at Dirac Labs. A quantum sensor that listens to the Earth itself — no satellites required. Spoof-proof. Jam-resistant. Always on. 🌐 diraclabs.com
7
33
9
121
14,516
🚨Q1 Recap is here! This quarter took us from the @UN to @sxsw, @EthereumDenver & @FundingCommons — sharing insights on AI, governance, privacy & digital infra Including: - Systems thinking - Open source - Public infra Here’s everything we’ve been up to: bit.ly/4iXKvVI
4
1
7
464
Today is a big moment. I'm very excited to announce our launch (along with fully open source release of the code) of v1 of the Naptha Stack. This is something we’ve been building towards for years. AGI won't be a monolith. We believe it will be a network of intelligent agents with heterogeneous models, architectures and data that adapt, compete and cooperate across many use cases. However, it's difficult to build such systems today because: 1. Agent and multi-agent frameworks built by different groups don’t interoperate. There are few standards for agent interactions. 2. Open Source Models use a variety of standards: Format for tool calling and reasoning, and adherence to structured output, vary depending on the model. 3. Scaling multi-agent orchestration across a network of nodes is an unsolved problem. The Naptha Stack solves this. Naptha is a framework and infrastructure for developing and running multi-agent systems at scale with heterogeneous models, architectures and data. Agents and other modules can run on separate devices, while still interacting over the network. This is a new type of platform that will enable new types of multi-agent applications, and we can't wait to see what AI engineers and researchers build. Come help us is to reimagine the internet. Let's bring forth the Web of Agents! Naptha Node: github.com/NapthaAI/naptha-n… Naptha SDK: github.com/NapthaAI/naptha-s… Docs: docs.naptha.ai/
30
41
14
146
10,692
Are you trying to get AI agents to work for you but the results aren’t hitting the sweet spot? Most AI systems fail not because they aren't powerful enough but because they don’t know when to ask for help. Building great workflows isn’t about “automating everything.” It’s about knowing what NOT to automate. At Inverter Network, we’re building systems that blend AI, automation, and human expertise to create workflows that actually work. Our resident AI expert @RowRowRoUrBoat has a framework for structuring multistep reasoning workflows that actually work so your automation isn’t just smart, but practical and reliable. 1. The Real Challenge of Automation Everyone talks about AI replacing human tasks, but the real challenge? Context. Some tasks are easy to automate (data entry, API calls). Others need human intuition (strategy, creativity). The sweet spot is a structured system where: ✅ Fully automatable steps run without intervention 🤖 AI handles complex reasoning 🧠 Humans step in only when absolutely necessary This isn’t just automation. It is orchestration. 2. Breaking Down the Workflow Not all workflows are equal. Depending on complexity, you can structure them as: 📌 Single Agent Model – One AI interacts with tools (simple tasks, low dependencies) 📌 Collaborative Network – Multiple AI agents share context (distributed intelligence) 📌 Supervisor Model – One AI oversees and coordinates other AI agents (structured delegation) 📌 Hierarchical Systems – Layered automation, each handling different levels of complexity No one-size-fits-all approach. The key is mapping dependencies and ensuring AI knows its limits. At Inverter, we’re using these models to build systems where AI doesn’t just run,it knows when to escalate decisions. 3. The Hidden Flaws in AI Automation Most “AI-driven” systems break because they: ❌ Assume the world is static (but real-world data is messy) ❌ Automate too aggressively without fallback mechanisms ❌ Don’t recognize when a task should be handed off to a human The fix? Dynamic routing. Instead of brute-forcing AI through every problem, design workflows where tasks flow between code, AI, and humans dynamically. 4. Categorizing Tasks for Efficiency Every workflow step should be assigned to one of three categories: 💻 Code Node – Fully deterministic (e.g., API calls, data transformation) 🤖 AI Node – Context-dependent reasoning (e.g., summarization, anomaly detection) 👩‍💻 Human Node – Requires creativity, ethics, or judgment If too many Human Nodes exist → The system is broken. If too many AI Nodes exist → It’s prone to catastrophic failure. 5. The Most Underrated Lessons in Workflow Design 🔁 Feedback loops matter more than first-pass accuracy. Good automation isn’t “set and forget.” It’s iterative refinement: where AI constantly learns from past outputs. 🚦 Decision routing beats brute force AI. Instead of forcing AI to do everything, create workflows where different systems work together efficiently. Let AI decide when to pass a task to another system (or human). ⚡ The best AI is the one that knows its own limitations. A well-designed AI should say: “I don’t know, but I know who/what to ask next.” That’s Inverter’s approach to automation! AI that works with humans, not against them. 6. Where This Works Best (And Where We’re Applying This at Inverter) 💡 Automated Code Documentation – AI-assisted updates when code changes 📊 AI Dashboards – Automated data integration + AI-driven insights 📖 Internal Knowledge Systems – AI-curated wikis with human validation 🔬 Research Workflows – AI-assisted insight extraction, human oversight The common theme? AI doesn’t replace humans. It optimizes how humans and machines collaborate. 7. Final Thoughts The future of AI isn’t in replacing humans. It’s in building systems where AI knows when to ask for human help. Instead of blindly automating, structure workflows that respect both human intuition and machine efficiency. If this made you rethink AI automation, quote it with your thoughts? Let’s design better systems.
7
15
1,838
While we were in Bangkok for Devcon, something unexpected happened. A bunch of people approached us not just to chat, but to play a game we created. 🎲 What game, you ask? The Token Orchestrator Card Game. And here’s what it achieved in just minutes: 1) It sparked curiosity. People got hands-on experience building innovative token economy workflows for real-world use cases. Suddenly, tokenomics wasn’t just theoretical. It was something they could see, build, and refine. 🔥 2) It attracted potential partners and patrons. By playing the game, people instantly understood what kind of token infrastructure would benefit them the most. A unique, fun way to showcase our work instead of just talking about it. 3) It made us memorable. People walked away with something tangible: a game that challenged them, sparked curiosity, and ignited new ideas. This is what meaningful merch should do and here’s why investing in something like it is a good idea for your organization too . 👇
3
8
2
23
3,152
Economies are complex and dynamic systems - yet, we are tied to static mechanisms that fail to adapt. Inverter is unlocking a novel design space for architecting markets. Enter the rabbit hole 🕳️ inverter.network/blog/vision… Thank you @el33th4xor for the shoutout 🙏🫡
If you're a crypto built, you should know about Inverter, a purpose built protocol stack for algorithmic issuance and redemption of tokens. Inverter Use Cases: 1. Multi-reserve stablecoins. 2. Condition-based issuance for real world assets. 3. Microloans powered by a 2d bonding surface algorithm. 4. Dynamic issuance for receivables with premiums & discounts. Take a look: 1. inverter.network/blog/vision… 2. inverter.network/blog/introd… 3. inverter.network/blog/econom…
1
8
21
2,608
If you're a crypto built, you should know about Inverter, a purpose built protocol stack for algorithmic issuance and redemption of tokens. Inverter Use Cases: 1. Multi-reserve stablecoins. 2. Condition-based issuance for real world assets. 3. Microloans powered by a 2d bonding surface algorithm. 4. Dynamic issuance for receivables with premiums & discounts. Take a look: 1. inverter.network/blog/vision… 2. inverter.network/blog/introd… 3. inverter.network/blog/econom…
36
53
5
328
26,591
Underneath nihilism is the deeper vice of shamelessness.
2
9
838
Dinner with a side of #TokenEngineering 🤓🚀 Great to meet up with #TokenEngineering friends IRL at @EFDevcon! 🦄🇹🇭 We’re excited to continue joining such fun meetups with our global community at future conferences! 💜🥂🙌
1
1
13
530