<?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: Krish D Shah</title>
    <description>The latest articles on DEV Community by Krish D Shah (@thekrishdshah).</description>
    <link>https://dev.to/thekrishdshah</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2968958%2Fd5e8628a-58ff-4ce1-a4de-66ff9daad772.jpg</url>
      <title>DEV Community: Krish D Shah</title>
      <link>https://dev.to/thekrishdshah</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/thekrishdshah"/>
    <language>en</language>
    <item>
      <title>Building KAVACH — An AI-Powered Income Protection System for Gig Workers</title>
      <dc:creator>Krish D Shah</dc:creator>
      <pubDate>Fri, 03 Apr 2026 11:43:48 +0000</pubDate>
      <link>https://dev.to/thekrishdshah/building-kavach-an-ai-powered-income-protection-system-for-gig-workers-1bbf</link>
      <guid>https://dev.to/thekrishdshah/building-kavach-an-ai-powered-income-protection-system-for-gig-workers-1bbf</guid>
      <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;&lt;u&gt;Guidewire DEVTrails Hackathon Devlog&lt;/u&gt;&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;What if insurance didn’t ask you to file a claim…&lt;br&gt;
and just paid you when something went wrong?&lt;/p&gt;

&lt;p&gt;That idea became the starting point for KAVACH (कवच) — a parametric, AI-powered income protection system designed for India’s gig workers. This post documents what we built, why we built it, and how the system actually works under the hood.&lt;/p&gt;




&lt;p&gt;**&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The Problem&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Gig workers operate in highly volatile conditions. A delivery partner’s income depends on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Weather disruptions (rain, storms)&lt;/li&gt;
&lt;li&gt;Air quality spikes (AQI)&lt;/li&gt;
&lt;li&gt;Flooding and road blockages&lt;/li&gt;
&lt;li&gt;Localized disasters&lt;/li&gt;
&lt;li&gt;Platform demand fluctuations&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A single bad day can wipe out ₹500–₹2000 of expected income.&lt;/p&gt;

&lt;p&gt;Traditional insurance doesn’t work here:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Claims require manual filing&lt;/li&gt;
&lt;li&gt;Verification takes days or weeks&lt;/li&gt;
&lt;li&gt;Payouts arrive too late&lt;/li&gt;
&lt;li&gt;Small income losses aren’t covered&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So the real question became:&lt;/p&gt;

&lt;p&gt;Can we detect income disruption automatically and trigger payouts instantly?&lt;/p&gt;

&lt;p&gt;That’s the foundation of parametric protection.&lt;/p&gt;




&lt;p&gt;**&lt;/p&gt;

&lt;p&gt;The Idea: Parametric Income Protection&lt;/p&gt;

&lt;p&gt;Instead of asking:&lt;/p&gt;

&lt;p&gt;«"Did the user file a claim?"»&lt;/p&gt;

&lt;p&gt;We ask:&lt;/p&gt;

&lt;p&gt;«"Did the worker’s earning environment degrade?"»&lt;/p&gt;

&lt;p&gt;If yes → trigger payout automatically.&lt;/p&gt;

&lt;p&gt;No claims. No paperwork. No waiting.&lt;/p&gt;

&lt;p&gt;This is what KAVACH attempts to solve.&lt;/p&gt;




&lt;p&gt;System Overview&lt;/p&gt;

&lt;p&gt;KAVACH combines three main components:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Real-time disruption detection&lt;/li&gt;
&lt;li&gt;ML-based earnings prediction&lt;/li&gt;
&lt;li&gt;Automated payout engine&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The flow looks like this:&lt;/p&gt;

&lt;p&gt;External Data → Disruption Detection → Income Prediction → Loss Calculation → Auto Payout&lt;/p&gt;




&lt;p&gt;Real-Time Disruption Detection&lt;/p&gt;

&lt;p&gt;We aggregate multiple data sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Weather APIs (rainfall, alerts)&lt;/li&gt;
&lt;li&gt;AQI feeds&lt;/li&gt;
&lt;li&gt;Disaster indicators&lt;/li&gt;
&lt;li&gt;Geo-based environmental signals&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These inputs are normalized and converted into disruption scores per location.&lt;/p&gt;

&lt;p&gt;Example:&lt;/p&gt;

&lt;p&gt;Heavy rain + AQI spike + low visibility&lt;br&gt;
→ High disruption score&lt;br&gt;
→ Trigger evaluation&lt;/p&gt;

&lt;p&gt;The system runs continuously and flags abnormal conditions.&lt;/p&gt;




&lt;p&gt;Earnings Prediction Model&lt;/p&gt;

&lt;p&gt;This is where ML comes in.&lt;/p&gt;

&lt;p&gt;We estimate expected earnings for a worker using:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Historical earnings&lt;/li&gt;
&lt;li&gt;Time of day&lt;/li&gt;
&lt;li&gt;Day of week&lt;/li&gt;
&lt;li&gt;Location demand patterns&lt;/li&gt;
&lt;li&gt;Weather sensitivity&lt;/li&gt;
&lt;li&gt;Behavioral trends&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We used:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;XGBoost regression model&lt;/li&gt;
&lt;li&gt;Feature engineering for time series signals&lt;/li&gt;
&lt;li&gt;Rolling baseline computation&lt;/li&gt;
&lt;li&gt;Dynamic adjustment windows&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Output:&lt;/p&gt;

&lt;p&gt;Expected earnings today: ₹1200&lt;br&gt;
Actual earnings detected: ₹540&lt;br&gt;
Loss detected: ₹660&lt;/p&gt;

&lt;p&gt;This becomes the payout base.&lt;/p&gt;




&lt;p&gt;Automated Payout Engine&lt;/p&gt;

&lt;p&gt;Once disruption + income drop is confirmed:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Risk score is computed&lt;/li&gt;
&lt;li&gt;Fraud checks are applied&lt;/li&gt;
&lt;li&gt;Loss amount validated&lt;/li&gt;
&lt;li&gt;Payout triggered&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Payout happens via:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;UPI transfer&lt;/li&gt;
&lt;li&gt;Instant disbursement logic&lt;/li&gt;
&lt;li&gt;Rule-based caps&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal is:&lt;/p&gt;

&lt;p&gt;Minutes, not days.&lt;/p&gt;




&lt;p&gt;Fraud &amp;amp; Abuse Prevention&lt;/p&gt;

&lt;p&gt;Parametric systems are vulnerable without safeguards.&lt;/p&gt;

&lt;p&gt;We added:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Anomaly detection on earnings&lt;/li&gt;
&lt;li&gt;Location spoofing checks&lt;/li&gt;
&lt;li&gt;Sudden behavioral deviation filters&lt;/li&gt;
&lt;li&gt;Multi-factor validation scoring&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Only validated losses trigger payouts.&lt;/p&gt;




&lt;p&gt;Why This Matters&lt;/p&gt;

&lt;p&gt;This isn’t just about insurance.&lt;/p&gt;

&lt;p&gt;It’s about:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Financial resilience&lt;/li&gt;
&lt;li&gt;Predictable income&lt;/li&gt;
&lt;li&gt;Gig worker stability&lt;/li&gt;
&lt;li&gt;Instant safety nets&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For millions of workers, a single disrupted day matters.&lt;/p&gt;

&lt;p&gt;KAVACH tries to make that risk invisible.&lt;/p&gt;




&lt;p&gt;What We Built During the Hackathon&lt;/p&gt;

&lt;p&gt;In the hackathon timeframe, we implemented:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Disruption detection pipeline&lt;/li&gt;
&lt;li&gt;ML income baseline model&lt;/li&gt;
&lt;li&gt;Loss calculation engine&lt;/li&gt;
&lt;li&gt;Decision trigger logic&lt;/li&gt;
&lt;li&gt;Simulated payout flow&lt;/li&gt;
&lt;li&gt;Dashboard for monitoring&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Still rough. Still evolving. But functional.&lt;/p&gt;




&lt;p&gt;Tech Stack&lt;/p&gt;

&lt;p&gt;Backend&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Python&lt;/li&gt;
&lt;li&gt;FastAPI&lt;/li&gt;
&lt;li&gt;Real-time ingestion&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;ML&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;XGBoost&lt;/li&gt;
&lt;li&gt;Pandas&lt;/li&gt;
&lt;li&gt;Feature engineering pipeline&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Data&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Weather APIs&lt;/li&gt;
&lt;li&gt;AQI feeds&lt;/li&gt;
&lt;li&gt;Synthetic earnings dataset&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;System&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Decision engine&lt;/li&gt;
&lt;li&gt;Rule evaluator&lt;/li&gt;
&lt;li&gt;Risk scoring module&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;Challenges We Faced&lt;/p&gt;

&lt;p&gt;Data scarcity&lt;br&gt;
Real gig-worker earnings data is not easily available.&lt;/p&gt;

&lt;p&gt;Dynamic environments&lt;br&gt;
Weather impact varies across cities.&lt;/p&gt;

&lt;p&gt;False positives&lt;br&gt;
Not every income drop is disruption-based.&lt;/p&gt;

&lt;p&gt;Payout fairness&lt;br&gt;
Avoiding over-compensation.&lt;/p&gt;

&lt;p&gt;Each of these required iterative tuning.&lt;/p&gt;




&lt;p&gt;What’s Next&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Better earnings prediction models&lt;/li&gt;
&lt;li&gt;Real gig platform integration&lt;/li&gt;
&lt;li&gt;Geo-level risk calibration&lt;/li&gt;
&lt;li&gt;Live payout simulation&lt;/li&gt;
&lt;li&gt;Mobile interface&lt;/li&gt;
&lt;li&gt;Policy engine tuning&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is still early — but the direction is clear.&lt;/p&gt;




&lt;p&gt;Team&lt;/p&gt;

&lt;p&gt;Built during Guidewire DEVTrails by:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Anisha&lt;/li&gt;
&lt;li&gt;Compilation&lt;/li&gt;
&lt;li&gt;Flux&lt;/li&gt;
&lt;li&gt;Fresh&lt;/li&gt;
&lt;li&gt;Priyanshu&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Different roles, shared goal — build something meaningful.&lt;/p&gt;




&lt;p&gt;Final Thoughts&lt;/p&gt;

&lt;p&gt;Hackathons usually produce demos.&lt;br&gt;
We tried building something closer to a product.&lt;/p&gt;

&lt;p&gt;KAVACH explores a simple idea:&lt;/p&gt;

&lt;p&gt;If risk can be detected automatically, protection should be automatic too.&lt;/p&gt;

&lt;p&gt;Still early. Still imperfect.&lt;br&gt;
But worth building.&lt;/p&gt;

&lt;p&gt;Seed Phase 2 is coming. Let’s go.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>guidewirechallenge</category>
    </item>
    <item>
      <title>Hackathon Doubts</title>
      <dc:creator>Krish D Shah</dc:creator>
      <pubDate>Fri, 11 Apr 2025 18:57:55 +0000</pubDate>
      <link>https://dev.to/thekrishdshah/hackathon-doubts-27m7</link>
      <guid>https://dev.to/thekrishdshah/hackathon-doubts-27m7</guid>
      <description>&lt;p&gt;Hello everyone this is my first post on this platform &lt;br&gt;
I wish to get some cool hackathon ideas in AIML field.&lt;/p&gt;

</description>
      <category>hackathon</category>
      <category>ai</category>
      <category>programming</category>
      <category>ideas</category>
    </item>
  </channel>
</rss>
