<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: zeeshan khan</title>
    <description>The latest articles on DEV Community by zeeshan khan (@zeeshan9958).</description>
    <link>https://dev.to/zeeshan9958</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4207378%2Fbc37824c-1dc1-4b8e-bea1-591c2bbb1da2.jpg</url>
      <title>DEV Community: zeeshan khan</title>
      <link>https://dev.to/zeeshan9958</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zeeshan9958"/>
    <language>en</language>
    <item>
      <title>Webhook-only 'paid': wiring Google sign-in and Razorpay for a one-time Rs 3,999 product</title>
      <dc:creator>zeeshan khan</dc:creator>
      <pubDate>Sat, 31 Oct 2026 06:14:57 +0000</pubDate>
      <link>https://dev.to/zeeshan9958/webhook-only-paid-wiring-google-sign-in-and-razorpay-for-a-one-time-rs-3999-product-1npe</link>
      <guid>https://dev.to/zeeshan9958/webhook-only-paid-wiring-google-sign-in-and-razorpay-for-a-one-time-rs-3999-product-1npe</guid>
      <description>&lt;p&gt;Content365 sells one thing: a year of branded social media posts for one business, for Rs 3,999 including GST, paid once. I built it, and the payment path is small enough to describe in one post. The design goal was boring on purpose: exactly one way for an order to become paid, and nothing the browser says can change that.&lt;/p&gt;

&lt;p&gt;Here is the flow and the reasoning behind each piece. No keys and no secrets, just the shape.&lt;/p&gt;

&lt;p&gt;Sign-in stores as little as possible. Customers sign in with Google. We keep four things: Google's stable account id, the email, the name and the profile picture. We do not keep Google access or refresh tokens, because we never call Google on the user's behalf. The session is an HttpOnly cookie that lasts 30 days. Fewer stored credentials means fewer things to leak and fewer things to rotate.&lt;/p&gt;

&lt;p&gt;The order comes first, payment second. After sign-in, the customer creates a brand. The only required field is the business name; the logo and details can come later. Creating the brand creates an order, and that order starts on the free plan: every account gets 2 free posts for its brand every 48 hours. If the customer later pays, the same order continues to the full 365 days and keeps the free posts already made. A customer who clicks 'Buy now' gets an order marked as a purchase, which skips the free previews and goes straight to checkout.&lt;/p&gt;

&lt;p&gt;The point of one order for both paths is that nothing has to be migrated at the moment of payment. Paying only changes the order's state.&lt;/p&gt;

&lt;p&gt;The server sets the price. The browser never sends an amount. When checkout opens, the server creates the Razorpay order for 399900 paise. Money is stored as integer paise, which avoids floating-point drift, and the GST split is fixed in code: Rs 3,388.98 plus Rs 610.02 at 18%. If someone edits the page's JavaScript, the worst they can do is break their own checkout.&lt;/p&gt;

&lt;p&gt;Only the signed webhook means 'paid'. Razorpay Checkout runs in the browser and calls a success handler when the customer completes payment. It is tempting to mark the order paid right there. We don't. The browser callback only updates the screen to say the payment is being confirmed. The order is marked paid when Razorpay's server calls our webhook endpoint with a signed payload and the signature checks out. Then, and only then, the order is queued for its full year.&lt;/p&gt;

&lt;p&gt;Why be this strict? Because the browser is the one party in the transaction we cannot trust. It can be closed mid-flow, replayed or edited. The webhook comes from Razorpay, signed, server to server. A single source of truth also keeps support simple. If a customer says they paid and the order is not paid, the question is always 'did the webhook arrive?', never 'which of three code paths ran?'.&lt;/p&gt;

&lt;p&gt;Two practical notes if you build this yourself. Webhooks can arrive more than once and out of order, so make the transition to paid idempotent. And keep checkout behind a server-side switch, as we do, so you can turn buying off without a deploy if something upstream misbehaves.&lt;/p&gt;

&lt;p&gt;Analytics follow the same rule. Our Meta Conversions API events are built on the server, and the Meta pixel never loads on signed-in pages. The server reports a Purchase only for a real Razorpay payment reference. Demo orders and orders our team marks as paid by hand never count as purchases, and those server events carry only a hashed email and a user id. A test can't inflate the purchase numbers.&lt;/p&gt;

&lt;p&gt;On refunds and changes, we keep it simple and honest while the written policy is finalised: they are agreed case by case before work begins, and we ask buyers to ask us before paying what can be changed.&lt;/p&gt;

&lt;p&gt;What I would tell anyone building a one-time product in India: keep the price on the server, store paise rather than rupees, let exactly one signed message decide 'paid', and tie purchase events to real payment references. None of it is clever. All of it saves you a bad day.&lt;/p&gt;

&lt;p&gt;If you want to see the flow from the customer side, &lt;a href="https://content365.si" rel="noopener noreferrer"&gt;https://content365.si&lt;/a&gt; lets you make 2 free posts every 48 hours with no payment, and &lt;a href="https://content365.si/offer" rel="noopener noreferrer"&gt;https://content365.si/offer&lt;/a&gt; is the full year at Rs 3,999 including GST per brand, one time. We don't post for you, and Reels are not included yet. Questions about the wiring are welcome in the comments.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>architecture</category>
      <category>startup</category>
      <category>backend</category>
    </item>
    <item>
      <title>Building things that ask before they act: My journey with GodEngine and AskShiva</title>
      <dc:creator>zeeshan khan</dc:creator>
      <pubDate>Wed, 28 Oct 2026 04:11:50 +0000</pubDate>
      <link>https://dev.to/zeeshan9958/building-things-that-ask-before-they-act-my-journey-with-godengine-and-askshiva-18c2</link>
      <guid>https://dev.to/zeeshan9958/building-things-that-ask-before-they-act-my-journey-with-godengine-and-askshiva-18c2</guid>
      <description>&lt;p&gt;I am a builder. Not the kind who spends months perfecting a landing page just to show a "Coming Soon" button that never changes. I build in Greater Noida, India, and I build with a very specific philosophy: AI should ask before it acts.&lt;/p&gt;

&lt;p&gt;Most people see AI as a magic black box. You type a prompt, and a machine spits out an answer. But in the real world—in business, in accounting, in school administration—blindly following an output is how expensive mistakes happen. You don't want an AI that just "does things"; you want an AI that understands the cause, assesses the effect, and checks with you before it jumps.&lt;/p&gt;

&lt;p&gt;That is the core of everything my co-founder Divyaprakash Jha and I are building at GodEngine.ai and AskShiva.ai. We aren't interested in hype. We are interested in decision intelligence and getting real work done.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Ecosystem: From Decision Intelligence to Daily Work
&lt;/h2&gt;

&lt;p&gt;We split our focus between two main pillars. GodEngine.ai is our "brain" for decision intelligence. AskShiva.ai is our "hands" for getting work done. &lt;/p&gt;

&lt;p&gt;If you look at what we have actually shipped and what is currently in progress, it looks like a roadmap of reality, not a collection of promises:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The GodEngine Suite (Live Alpha)&lt;/strong&gt;&lt;br&gt;
We are currently in the Alpha stage with several tools designed for people who actually need to think through complex problems:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;GodEngine:&lt;/strong&gt; A tool for causal analysis and scenario planning. You ask a decision question, and it breaks it down into causes and effects to show you the reasoning.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Startup Intelligence:&lt;/strong&gt; For founders who want to stop guessing. It reads your startup idea and writes a de-risking report—highlighting load-bearing assumptions and the cheapest experiments to run first.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;World 360:&lt;/strong&gt; A news reader that goes beyond the headline to explain &lt;em&gt;why&lt;/em&gt; things happened and what might come next.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The AskShiva Suite (In Development &amp;amp; Pilot)&lt;/strong&gt;&lt;br&gt;
While GodEngine helps you think, AskShiva helps you run your business and school:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;Falcon (Live Alpha):&lt;/strong&gt; Double-entry accounting for Indian SMBs. It handles GST working papers, invoices, and bank reconciliation. It's a browser-based tool with a Windows desktop app currently in development.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Campus One (In Pilot/Building):&lt;/strong&gt; We are testing this with schools. It is a complete education suite—admissions, fees via UPI, attendance, and exam report cards—meant to replace the chaos of manual registers and fragmented WhatsApp groups.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What We Are Doing Right Now: Content 365
&lt;/h2&gt;

&lt;p&gt;While we build these heavy-duty decision engines and management systems, we have also been working on something much more practical for the small business owner in India—someone who knows they need to be on social media but simply doesn't have the time or the budget for a massive agency.&lt;/p&gt;

&lt;p&gt;We have built and are currently using &lt;strong&gt;Content 365&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Problem:&lt;/strong&gt;&lt;br&gt;
Most local shops, professionals, and creators know they should post regularly to stay relevant. But then life happens. You miss a week, then a month, and suddenly your social media is a ghost town. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Solution:&lt;/strong&gt;&lt;br&gt;
Content 365 turns your business details and logo into 365 days of branded social media posts. It covers an entire year of content, including images and captions, planned around the specific festivals and the Indian financial year.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Reality of Content 365:&lt;/strong&gt;&lt;br&gt;
I want to be honest about where this stands. This is not a "do it yourself" mass-market bot. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;What is Live:&lt;/strong&gt; Brand set-up, year-long content plans, branded images, and a delivery folder.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;How it works:&lt;/strong&gt; The studio runs on our own machines. Our team runs each order from start to finish to ensure the quality is actually useful for a real business.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;The Cost:&lt;/strong&gt; A one-time fee of ₹3,999 (GST included) for the whole year.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is for the person who wants to say, "I have my content sorted for the next 12 months," so they can get back to actually running their business. &lt;/p&gt;

&lt;h2&gt;
  
  
  Building in Public
&lt;/h2&gt;

&lt;p&gt;I don't believe in corporate fluff. There is no "revolutionary" AI magic here. There is just a developer in India building tools that provide reasoning, structure, and automation where it is actually needed.&lt;/p&gt;

&lt;p&gt;Whether it is a founder trying to de-risk a startup with Startup Intelligence, an accountant using Falcon to reconcile a bank statement, or a small business owner using Content 365 to stay visible, the goal is the same: building intelligence that works &lt;em&gt;with&lt;/em&gt; you, not instead of you.&lt;/p&gt;

&lt;p&gt;If you are a founder, a developer, or a business owner who wants to see what we are building, or if you want to try Content 365 for your own brand, let's talk.&lt;/p&gt;

&lt;p&gt;Do you have a specific problem in your workflow that you wish an AI could handle—but only if it explained its reasoning first? Reply to this or reach out at GodEngine.ai.&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>buildinpublic</category>
      <category>startup</category>
    </item>
    <item>
      <title>Why our AI never writes text on images: a deterministic compositor for 365 branded posts</title>
      <dc:creator>zeeshan khan</dc:creator>
      <pubDate>Wed, 28 Oct 2026 04:09:13 +0000</pubDate>
      <link>https://dev.to/zeeshan9958/why-our-ai-never-writes-text-on-images-a-deterministic-compositor-for-365-branded-posts-3g78</link>
      <guid>https://dev.to/zeeshan9958/why-our-ai-never-writes-text-on-images-a-deterministic-compositor-for-365-branded-posts-3g78</guid>
      <description>&lt;p&gt;Ask an image model for a poster that says 'Mehta Sweets, Main Market' and you will usually get something close. Close is the problem. For a small business, a post that says 'Mehta Sweats' is worse than no post at all. And when you generate 365 posts for one shop, 'usually right' means a misspelling somewhere in the year, almost certainly.&lt;/p&gt;

&lt;p&gt;I build Content365, which makes a whole year of branded social media posts for one Indian small business in one go. Early on we made one rule that shaped everything else: the image model never draws text. Not the name, not the phone number, not the price, not the call to action. This post explains how that works and what it costs us in flexibility.&lt;/p&gt;

&lt;p&gt;We split the job in two. Each post is built in layers. The first layer is a scene painted by the image model: a product on a table, a shopfront, a festive setting. The prompt asks for a picture with no lettering and with room where copy will go. Everything after that is deterministic code. A decoration layer adds frames and accents. A copy layer sets the headline and selling text in one of ten layouts. A final layer places the brand's real logo, using a treatment that does not repeat within the year.&lt;/p&gt;

&lt;p&gt;Because code sets every word, spelling and prices are exact by construction. If the shop's name is stored correctly, it is on the post correctly. The model never gets a chance to be creative with a phone number.&lt;/p&gt;

&lt;p&gt;A few scheduling rules keep a year of this from looking mechanical. No layout runs two days in a row. The logo never sits in the same corner two days running. Posts are 1080x1350 with a square-safe centre, so a 1:1 crop for a grid or a WhatsApp share still keeps the important parts.&lt;/p&gt;

&lt;p&gt;Indian scripts need real shaping. Hindi in Devanagari is not a row of independent letters. Conjuncts join consonants, and vowel signs attach before or after the consonant they belong to. Naive rendering produces text that is technically present and visibly wrong, and any Hindi reader spots it instantly. We shape Indic text with HarfBuzz, the open-source shaping engine used by major browsers and Android, before drawing it, so what lands on the image is what a native reader expects.&lt;/p&gt;

&lt;p&gt;Privacy comes before any model sees anything. Business details often include a phone number, an email address or a WhatsApp number. We strip those from the text before any model reads it, and the compositor adds them back at the very end from the brand's own record. The model never needs them to paint a scene, so it never gets them.&lt;/p&gt;

&lt;p&gt;Claims are gated too. Some post angles naturally want a claim: a rating, an award, a guarantee, a statistic. Those angles run only if the brand has verified that fact; otherwise the post is made without the claim. We also removed default template labels like 'BESTSELLER', because a label is a claim as well. More on that in a separate write-up.&lt;/p&gt;

&lt;p&gt;QA is something the customer can see. Every render gets a vision check and a perceptual-hash check. The vision check reviews the finished image. The hash check compares it with the brand's other renders, so near-duplicates are rejected. A failed render is retried, up to three tries. If a day still fails after that, it ships with a visible warning in the customer's gallery instead of being quietly hidden. I would rather a customer see 'this one needs a look' than find a bad post after publishing it.&lt;/p&gt;

&lt;p&gt;What does this cost us? The obvious trade-off is that we give up expressive lettering, the hand-painted signboard look that image models are getting good at. Our typography is only as good as our layouts, so layout design became a real part of the product, not an afterthought. We also maintain font coverage for every script we render, which is unglamorous work. For small businesses, where correctness beats flair, I think it is the right trade.&lt;/p&gt;

&lt;p&gt;If you are building anything that puts generated images in front of customers with names, prices or legal text on them, my advice is the same rule: let the model paint, let code write.&lt;/p&gt;

&lt;p&gt;For context on the product: Content365 is Rs 3,999 including GST per brand, one time, for 365 posts with captions and Indian festival days pinned in the calendar. We don't post for you, and Reels are not included yet. The cover image is a sample design for a made-up business. You can make 2 free posts every 48 hours with no payment at &lt;a href="https://content365.si" rel="noopener noreferrer"&gt;https://content365.si&lt;/a&gt;, and the full offer is at &lt;a href="https://content365.si/offer" rel="noopener noreferrer"&gt;https://content365.si/offer&lt;/a&gt;. I built it, and I am happy to answer questions about the pipeline in the comments.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>architecture</category>
      <category>machinelearning</category>
      <category>softwaredevelopment</category>
    </item>
    <item>
      <title>Building AI that asks before it acts: A look at what we are shipping</title>
      <dc:creator>zeeshan khan</dc:creator>
      <pubDate>Tue, 27 Oct 2026 06:43:10 +0000</pubDate>
      <link>https://dev.to/zeeshan9958/building-ai-that-asks-before-it-acts-a-look-at-what-we-are-shipping-2big</link>
      <guid>https://dev.to/zeeshan9958/building-ai-that-asks-before-it-acts-a-look-at-what-we-are-shipping-2big</guid>
      <description>&lt;p&gt;I am a builder. &lt;/p&gt;

&lt;p&gt;I don’t believe in AI that just hallucinates confidently or gives you a generic paragraph that no one actually reads. I believe in AI that understands the &lt;em&gt;why&lt;/em&gt; before it gives you the &lt;em&gt;what&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;From my desk in Greater Noida, me and my co-founder Divyaprakash Jha are building. We aren’t just playing with LLM wrappers; we are building products designed to solve actual problems. We call this "decision intelligence." Whether it is helping a founder de-risk a startup idea or helping an accountant close their books, the goal is the same: tools that actually work.&lt;/p&gt;

&lt;p&gt;I wanted to pull back the curtain on what we are actually building at GodEngine.ai and AskShiva.ai, and what stage these projects are in right now. No hype, just the truth.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision Intelligence: The GodEngine Suite
&lt;/h2&gt;

&lt;p&gt;Most AI tools are "input-output" machines. You ask a question, it gives a response. But real decisions are messy. They have causes and effects. They have variables that change.&lt;/p&gt;

&lt;p&gt;This is why we are building the GodEngine ecosystem. We want AI to act like a smart partner who says, "Wait, before we do that, let’s look at the consequences."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Here is what is live in our Alpha right now:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;GodEngine (Live Alpha):&lt;/strong&gt; This is for the operators and researchers. You ask a decision question, and it breaks the problem down into a cause-and-effect breakdown. It builds scenarios and writes a report showing the reasoning. It’s meant to help you think through a move before you make it. &lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Startup Intelligence (Live Alpha):&lt;/strong&gt; For the founders. Before you burn your seed round or your savings on an idea, run it through this. It reads your startup idea and identifies the load-bearing assumptions. It gives you a "no number without a source" grade, tells you the points at which you should stop, and suggests the cheapest experiments to run first. It is designed to tell you the truth, even if that truth is: "Stop here."&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;World 365 (Live Alpha):&lt;/strong&gt; A news reader that moves past headlines. It groups reports into stories and explains the "why" and the "what next," running on our own newsroom engine.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Accounting and Education: Real World Work
&lt;/h2&gt;

&lt;p&gt;We aren't just building for Silicon Valley-style tech companies. We are building for the backbone of India.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Falcon (Live Alpha)&lt;/strong&gt;&lt;br&gt;
Small business owners and accountants in India deal with a specific kind of complexity: GST, TDS, and manual reconciliation. Falcon is a double-entry accounting system built for this. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;Status:&lt;/strong&gt; We have the double-entry ledger, reports, invoices, estimates, and bank reconciliation working. We also have an AI assistant that drafts and answers questions based on your own figures.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;What’s coming:&lt;/strong&gt; A Windows desktop app is currently in development.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Campus One (In Pilot / Building for 2026)&lt;/strong&gt;&lt;br&gt;
Most schools in India are still running on a mess of registers, spreadsheets, and WhatsApp groups. It’s chaotic. Campus One is a single system to bring everything together.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;What is available now:&lt;/strong&gt; Admissions, student records, and fee collection (with UPI).&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;In Pilot:&lt;/strong&gt; We are currently testing modules like attendance and parent communication with schools.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;The Road to 2026:&lt;/strong&gt; We are building out everything from exam paper generators to live bus tracking. We are working with founding schools to get this right.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Shipping Now: Content 365
&lt;/h2&gt;

&lt;p&gt;While we work on these larger systems, I wanted to build something that solves a massive problem for the small business owner I talk to every day: &lt;strong&gt;Visibility.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Every shopkeeper, professional, and creator knows they &lt;em&gt;should&lt;/em&gt; be posting on social media, but they don't have the time or the agency to do it every single day. They end up posting once every three months, then going silent.&lt;/p&gt;

&lt;p&gt;We built &lt;strong&gt;Content 365&lt;/strong&gt; to solve this.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Product:&lt;/strong&gt;&lt;br&gt;
Content 365 turns one business's details and logo into 365 branded posts—a whole year’s worth of content. It includes an image and a caption for every single day. It is planned around Indian festivals and the financial year so the content actually feels relevant to your customers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Logistics (Being honest here):&lt;/strong&gt;&lt;br&gt;
This isn't a fully automated "click-and-forget" SaaS tool yet. Currently, the studio runs on our own machines, and our team runs each order from start to finish to ensure quality. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;Status:&lt;/strong&gt; Live and in use.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;What you get:&lt;/strong&gt; A full year-long content plan, branded images, and a delivery folder.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Price:&lt;/strong&gt; ₹3,999 for the whole year (including GST). One-time payment.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It is the simplest way for a local business to stay present online without hiring a social media team.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building in Public
&lt;/h2&gt;

&lt;p&gt;I am sharing this because I want to be honest about the journey. We aren't a massive corporation with thousands of employees. We are a team of builders—myself and Divyaprakash Jha—working to make AI useful for the people who move the economy.&lt;/p&gt;

&lt;p&gt;We are building "AI that asks before it acts." It is a difficult problem to solve, but it is the only way to build tools that people actually trust.&lt;/p&gt;

&lt;p&gt;Whether you are a developer looking to collaborate, a founder who needs to de-risk an idea, or a small business owner who needs 365 days of content, I’d love to hear from you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you want to see what we are working on or grab a Content 365 plan, reach out or check the links below. Let's build something real.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://content365.si/offer" rel="noopener noreferrer"&gt;Try Content 365 here&lt;/a&gt; | &lt;a href="https://godengine.ai" rel="noopener noreferrer"&gt;Explore GodEngine&lt;/a&gt; | &lt;a href="https://askshiva.ai" rel="noopener noreferrer"&gt;Visit AskShiva&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you have feedback on our Alpha products, just hit reply. I read every single one.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>product</category>
      <category>startup</category>
    </item>
    <item>
      <title>Building AI Agents That Ask Before They Act</title>
      <dc:creator>zeeshan khan</dc:creator>
      <pubDate>Mon, 26 Oct 2026 23:47:11 +0000</pubDate>
      <link>https://dev.to/zeeshan9958/building-ai-agents-that-ask-before-they-act-3b22</link>
      <guid>https://dev.to/zeeshan9958/building-ai-agents-that-ask-before-they-act-3b22</guid>
      <description>&lt;p&gt;I am tired of seeing "autonomous" AI agents that are anything but.&lt;/p&gt;

&lt;p&gt;If you have spent much time building with LLMs lately, you have seen the same pattern. A developer gives an agent a tool, a goal, and a loop. The agent starts executing. Then, it hallucinates. It tries to call an API it wasn't supposed to touch, or it executes a sequence of actions that fundamentally breaks the user's workflow. &lt;/p&gt;

&lt;p&gt;In the rush to build "agentic" workflows, we are creating systems that act with too much confidence and not enough supervision. We are building digital employees that act before they check if they have permission to touch the steering wheel.&lt;/p&gt;

&lt;p&gt;At GodEngine.ai and AskShiva.ai, we decided to take a different path. Our philosophy is simple: AI agents must ask before they act.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem with Total Autonomy
&lt;/h2&gt;

&lt;p&gt;The industry is currently obsessed with the "loop." We want the agent to loop until the task is done. &lt;/p&gt;

&lt;p&gt;But in a real-world production environment, a "loop" can quickly become a "financial drain" or a "data nightmare." If an agent is tasked with managing a database or executing marketing workflows, the cost of an error isn't just a bad chat response. It is an incorrect entry in a production database or a botched email campaign sent to a client list.&lt;/p&gt;

&lt;p&gt;When I sit down to architect a system for a startup or a developer, I look at the "action boundary." Every time an agent hits a point where it moves from &lt;em&gt;thinking&lt;/em&gt; to &lt;em&gt;doing&lt;/em&gt;, there must be a checkpoint.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Human-in-the-Loop Framework
&lt;/h2&gt;

&lt;p&gt;We aren't building assistants that just talk; we are building agents that work. But "working" requires accountability.&lt;/p&gt;

&lt;p&gt;To achieve what we are building at GodEngine, we focus on three specific layers of verification:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Intent Verification:&lt;/strong&gt; Before an agent triggers a complex sequence, it must present the "Plan" to the user. Not just a vague summary, but a concrete list of steps: "I will do A, then B, then C. Do you agree?"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Parameter Validation:&lt;/strong&gt; If the agent is about to execute a function, it should present the arguments it intends to use. If it is about to send an email, it should show the recipient and the body.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Post-Action Review:&lt;/strong&gt; The agent reports back on what it did and asks if the result matches the user's expectation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We call this "Permission-Driven Agency." It is the difference between a chaotic intern and a professional colleague.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why This Matters for Indian Founders
&lt;/h2&gt;

&lt;p&gt;The AI landscape in India is moving fast. We have the talent, we have the scale, and we are building for a global market. But to win globally, our products must be reliable.&lt;/p&gt;

&lt;p&gt;Founders building with AI shouldn't be afraid of the "Agent" label. You shouldn't have to build "guardrails" that are actually just massive, expensive prompt-engineering walls that fail 20% of the time. Instead, you build systems where the agent is designed to realize its own limitations.&lt;/p&gt;

&lt;p&gt;When we build at AskShiva.ai, we prioritize this transparency. Users shouldn't have to wonder, "What is the AI doing in the background?" They should feel in control because the agent is constantly checking in.&lt;/p&gt;

&lt;h2&gt;
  
  
  Engineering for Control
&lt;/h2&gt;

&lt;p&gt;Building this isn't just about changing a prompt. It is about how you structure the integration between the LLM and the tool-calling mechanism.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The "Pause" State:&lt;/strong&gt; You have to architect your backend to handle a "pending approval" state. The agent isn't just running a script; it is waiting for an external signal to resume.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Contextual Confirmation:&lt;/strong&gt; You don't want to ask for permission for every single irrelevant step. That is annoying. You want the agent to be smart enough to know &lt;em&gt;when&lt;/em&gt; an action is high-stakes. &lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Granular Tool Access:&lt;/strong&gt; We treat tools as precious resources. An agent shouldn't have "Write" access by default. It should have "Draft" access, and only through human intervention does it gain "Commit" access.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Real Progress Over Hype
&lt;/h2&gt;

&lt;p&gt;I am not interested in discussing what AI might do in 2030. I care about what we are shipping today in Greater Noida and beyond.&lt;/p&gt;

&lt;p&gt;We are building agents that people can actually trust with real tasks. Real workflows. Real consequences. It is much harder to build an agent that asks for permission than one that just runs wild. It requires more logic, more structured state management, and a better understanding of user psychology.&lt;/p&gt;

&lt;p&gt;But the "wild" agents? They will fail the moment they encounter a professional environment with high stakes. The agents that survive—the ones that become part of the daily stack for developers and marketers—will be the ones that know when to stop and ask, "Is this what you wanted?"&lt;/p&gt;

&lt;p&gt;We are building the engines of the future, but we are building them with a hand on the brake.&lt;/p&gt;

&lt;p&gt;Are you building agents that act, or agents that ask? Let me know what you are working on in the replies.&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>architecture</category>
      <category>llm</category>
    </item>
  </channel>
</rss>
