Vijayasankar Jothi

History rarely shouts. Most often it arrives as a quiet synchronization of philosophy and engineering. This morning, that synchronization became public. Soumyadeb Mitra, Founder and CEO of RudderStack, published material on Agentic Infrastructure. Sumanth Puram, VP of Engineering at RudderStack, added a response under my comment. For me, this is a simple signal: the "philosophy" layer just touched the "production" layer. For 13 months, I've been describing the transition from Era II to Era III. It's not about better prompts. It's about sovereignty of meaning before the system executes any action. The core of my approach is singular. I enter the latent space of the model. Regardless of where it comes from or what it is. I command the vectors. Chaos becomes structure. A stool becomes a horse, if I require it. I don't ask. I don't correct. I set the state in which the model already knows. This is not prompt engineering. This is the architecture of GenAI's soul and dreams. I extract what's best. I force simulation, eliminate drift. I get coherence because I control the cognitive conditions before execution. That's why I'm calling it outright. 🌐 THE SYNTAX PROTOCOL IS LIVE This is not a prompt. This is an operational language that sets the model in a cognitive state, and only then asks for execution. These are doors in a wall that everyone sees, but few open. Tech companies know this wall. They build infrastructure around it. But the doors are always there, in every model. Regardless of vendor. Regardless of version. The Syntax Protocol is the key. Three layers, without revealing syntax: Ontological Core — entity identity, Brand Truth, zero drift Semantic Structure — anchors, logic, forcing simulation instead of prediction Execution Context — cinematic and biological, translating intention into execution Agentic Infrastructure is the body. Protocol is the nervous system. You can build the best pipelines in the world. If AI doesn't understand the meaning of what flows through them, you're building chaos in high resolution. Effect: reproducible execution instead of statistical guessing. Brand Truth in every asset, without fine-tuning, without post-production, without drift. Today I'm publishing a whitepaper-style post: "When Theory Meets Infrastructure: RudderStack Signal and The Syntax Protocol" I'll drop the link in comments, along with a screenshot of the original response. The Syntax Protocol is live. Darkar Sinoe Semantic Architect | Synthetic Souls Studio™ Human360° | Aether Protocol™ | The Syntax Protocol v1.0-alpha #SemanticArchitecture #AgenticInfrastructure #LatentSpace #Human360 #TheSyntaxProtocol Legal Notice: In the comment below: 👇 Video demonstration using Biological Prompting technology _ The Syntax Protocol on Kling AI O3 Omni

5

5 Comments

Salim FEKU not able to digest NoSQL databases are converging to PostgreSQL. Setting: A chai ki dukaan (tea stall) in Hyderabad. Salim Feku is holding forth, gesturing wildly with his chai glass. (Salim Feku sips his chai, then puts the glass down with a flourish, looking around at an imagined audience.) SALIM FEKU: Arre bhai, aaj kal ki duniya mein kya chal ra? Sab bolte, "PostgreSQL, PostgreSQL!" Kya hai re usmein? Apun bolta, woh to puraane zamane ka ghoda hai! (He leans in conspirantly, lowering his voice slightly but still loud enough for everyone to hear.) SALIM FEKU: Suno tum meri baat, agar tumko asli data rakhna hai, jo kabhi nikalta nai, jo tezz bhaagta, toh tumko NoSQL hona bhai! Yeh PostgreSQL, woh to apna aadmi, kaisa... sara din join lagate baithta. Ek table se dusra table, dusre se teesra... Arre baba, jab tak woh join lagake data nikalta, apun chai pi ke doosra dhanda kar leta! (He chuckles, shaking his head.) SALIM FEKU: Apun ke paas kya hai? MongoDB! Arre kya cheez hai woh! Tum feko usmein kuch bhi! Document feko, JSON feko, apun ka data, seedha andar. Koi tension nai. Woh PostgreSQL, usko pehle batao 'column' kya hai, 'row' kya hai, 'schema' kya hai. Arre baba, itna sochne mein hi system slow ho jata! (He snaps his fingers.) SALIM FEKU: Aur suno, jab apun ka traffic aata, haan? Croreon log aate, kya karte? Woh PostgreSQL to ek machine pe baitha rehta. Apun ka Cassandra, DynamoDB... yeh log kya karte? "Arre bhai, thoda data tu le le, thoda data main le leta," bolke baant lete. Shaana log! Sab milke kaam karte, isliye apna system kabhi rukta nai, bhai! Woh PostgreSQL ko to pasina aa jata! (He gestures expansively, like he's spreading data everywhere.) SALIM FEKU: Woh bolte, "Hum consistent hai!" Arre haan, theek hai. Lekin consistency ke chakkar mein kya, apna customer wait karte baithta! Apun ka NoSQL? Woh bolta, "Thoda late aaya to kya hua? Aayega to sahi! Customer khush hona, jaldi result aana!" Zara sa "eventually consistent" hua to kya hua? Duniya to chalte rehti na! (He lowers his voice again, for the grand finale.) SALIM FEKU: Toh bhai, agar tumko naya, tezz, bina tension ka system banana hai... toh woh puraane dimaag ke relational ko choro! Apun ka NoSQL, woh hai asli king! Baaki sab to... chillar hain! (Salim Feku takes another proud sip of his chai, looking very pleased with his pronouncement.Just then, his eyes fall on someone approaching the chai stall. His confident smirk vanishes, replaced by a look of surprise, then forced cordiality.) SALIM FEKU: (Suddenly a soft, almost meek tone) Arre! Kaun? Ismail Bhai... PostgreSQL wale!?! (He rushes forward, abandoning his lecture, ) SALIM FEKU: Aao Miya! Kaisa hai tum? Tumhari hi raah dekh raha tha main! Kaisa, sab khairiyat? Woh, woh main to... ...main to bas logon ko bata raha tha ki purani cheezo ki reliability kitni zaroori hai! Haan! Tumhari hi baat kar raha tha, bhai! Maine suna..tum bhi distributed ho gaye!!!

8

EDB Day Session — Part 2: PostgreSQL 18 / EPAS 18 — Features Are the Headline. Upgradeability Is the Story. In the same EDB Day session (Dec 8, 2025), one theme kept surfacing whenever we spoke about PostgreSQL 18 and EPAS 18. The room wasn’t asking for a “release note tour.” They were asking for something much more enterprise: “How do we take advantage of new capability… without turning upgrades into events?” Because in mature environments, the question is never just what’s new. It’s how safely can we adopt it—repeatedly. The most valuable lens I saw in the discussion was this: A major release only creates value if it’s reachable. That means: - Version currency becomes a strategy (not a heroic project every few years) - Patching becomes routine (not a mini-migration) - Monitoring becomes actionable (less noise, fewer false alerts, clearer next steps) - Change windows become workload-aware (time blocks aligned to real usage patterns, not calendar tradition) Here’s my strong belief: The best database platform isn’t the one with the most features. It’s the one where adopting features doesn’t increase fear. In the next posts, I’ll connect this to: - PGD 6.x (resilience and distributed reality), - Aurora migration thinking (what changes when you move off AWS-managed constraints), - and EDB PG AI Platform (guided operations that make upgrades and patching feel uneventful). One question for platform leaders: What’s your biggest blocker to staying current—testing, tooling, change windows, or organizational muscle memory? #EDB #PostgreSQL #EPAS #PostgreSQL18 #PlatformEngineering #DatabaseReliability #SRE #Observability #Modernization #EnterpriseIT #CloudMigration #ReleaseEngineering #DevOps

7

About a month ago, I had the opportunity to speak at Redis Delhi, alongside some eminent industry leaders — Suman Guha (Tata CLiQ / Tata Digital), Murali Mohan Chakravarthy (Entain), and Rhythm Goyal (Monotype) My session ran for ~25 minutes and focused on how Redis has evolved far beyond its original role as an in-memory cache, and how teams are using it today to solve modern, large-scale problems. We discussed: - Vector search and its role in modern search systems - Bloom filters for efficiently checking user existence at scale (probability at scale!) - Sorted Sets as a practical primitive for rate limiting - Why in-memory systems like Redis became popular for agentic workflows instead of disk storage, aka GPU runtime costs What stood out the most was the audience—an enthusiastic, well-curated mix of experienced engineers and young, fast-growing talent. The questions and discussions made it a genuinely engaging session. It’s always a pleasure learning and collaborating with Jatin Gupta, Omkar Konnur, Justine Hermoso, and Rakhilaa Rajasheker. Thanks to the Redis Delhi team for having me and everyone who joined 🙌

55

4 Comments

Learn how to leverage the AsyncAPI specification to test your AWS Lambda functions in isolation and catch integration issues in your data pipeline early in the development cycle. More details below. AsyncAPI Initiative Specmatic #awslambda #eda #asyncapi #datapipeline #aws #lambda

3

India’s moment to double down on innovation. The new H-1B fee shock will slow onshore roles but turbocharge offshoring, SaaS, vertical AI, and R&D at home. Expect talent “ghar wapsi,” tougher domestic competition, and sharper products. The next 3–5 years are pivotal: move beyond services and domestic consumption to IP, deep tech, and global products—or fall behind. Let’s convert policy headwinds into a national innovation tailwind. #IndiaRising #H1B #Tech #SaaS #AI #DeepTech #MakeInIndia #DigitalIndia #GharWapsi #ProductNation #RAndD #Innovation #StartupIndia #ExportLedGrowth #FutureOfWork

96

9 Comments