<?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: Sruthi Kumar</title>
    <description>The latest articles on DEV Community by Sruthi Kumar (@sruthi_kumar_c0c809139982).</description>
    <link>https://dev.to/sruthi_kumar_c0c809139982</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%2F3644934%2F6353592c-0828-4267-9838-46a8bd058617.jpg</url>
      <title>DEV Community: Sruthi Kumar</title>
      <link>https://dev.to/sruthi_kumar_c0c809139982</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sruthi_kumar_c0c809139982"/>
    <language>en</language>
    <item>
      <title>"From Financial Overload to Causal Agents: Architecting Autonomy for the Market"</title>
      <dc:creator>Sruthi Kumar</dc:creator>
      <pubDate>Thu, 04 Dec 2025 04:16:18 +0000</pubDate>
      <link>https://dev.to/sruthi_kumar_c0c809139982/from-financial-overload-to-causal-agents-architecting-autonomy-for-the-market-3bc5</link>
      <guid>https://dev.to/sruthi_kumar_c0c809139982/from-financial-overload-to-causal-agents-architecting-autonomy-for-the-market-3bc5</guid>
      <description>&lt;p&gt;*&lt;br&gt;
Hello! I'm Sruthika Kumar, a 3rd-year B.Com student from Madras University and a CA Intermediate candidate. My world is driven by audits, compliance, and razor-sharp financial accuracy. This unique, analytical background is exactly what fueled my enrollment in the AI Agents Intensive: to build systems that automate the highly contextual and high-stakes environment of finance.&lt;/p&gt;

&lt;p&gt;My motivation was to solve a critical, real-world problem for traders: Information Overload in Finance. The Intensive provided the foundational cognitive framework I needed, which culminated in my capstone: the Market Sentiment Monitoring and Alert Agent. You can review the complete execution and code logic in my public notebook: [&lt;a href="https://www.google.com/search?q=https://www.kaggle.com/code/sruthika0817/notebookb88a6dde25" rel="noopener noreferrer"&gt;https://www.google.com/search?q=https://www.kaggle.com/code/sruthika0817/notebookb88a6dde25&lt;/a&gt;].&lt;/p&gt;

&lt;p&gt;The "Aha!" Moment: From Zero-Shot to Causal ReAct&lt;br&gt;
The most resonant concept from the entire course was the transition from passive, Zero-Shot Prompting to the ReAct (Reasoning + Acting) framework. This wasn't just a technical trick; it was the pivotal insight that unlocked true autonomy in my code.&lt;br&gt;
Execution Detail: In my Kaggle notebook, this transition is visible in the structured Agent executor function. I implemented the ReAct loop by defining a clear Thought, followed by a guaranteed Action (calling a tool), which returns an Observation to the model.&lt;br&gt;
This framework was the engine for my Market Sentiment Agent:&lt;br&gt;
Thought: "I need to check the latest news for specific tickers and assess their immediate impact."&lt;br&gt;
Action: Calls a Search Tool and fetches headlines and articles from live financial APIs (e.g., finance or a web scraper), a core concept from Day 3.&lt;br&gt;
Observation: Reads the raw, external data.&lt;br&gt;
Reasoning: "These headlines look bearish, but I must first confirm if the 'loss' refers to competitor data or company profit before calculating the sentiment score."&lt;br&gt;
Final Response: Sends a categorized, scored alert.&lt;br&gt;
This ReAct mechanism, rooted in Day 3's focus on Orchestrating Collaboration, was the critical lever that moved my project from a fragile prototype to a dynamic, goal-driven monitoring system.&lt;br&gt;
The Crucible Moment: Solving Contextual Ambiguity in Finance&lt;br&gt;
Building upon the ReAct loop, my biggest technical hurdle was the Context awareness problem, a challenge directly addressed by Day 2 (Embeddings) and Day 4 (Domain-Specific LLMs). In finance, the Agent needed to distinguish between 'loss' in profits (Bearish) versus 'loss' of a competitor (Bullish) or 'loss' of data (Neutral).&lt;br&gt;
Execution Detail: My solution, directly influenced by Day 5's MLOps focus on Resilience and Observability, was the implementation of a Failure Registry. This is a persistent memory store that tracks explicit examples of contextual misinterpretation. If the Agent's confidence dropped (a key observability metric), it would:&lt;br&gt;
Check the Failure Registry for past, similar errors.&lt;br&gt;
Trigger a Metacognitive Reset, forcing the ReAct loop to generate a new plan that explicitly includes disambiguation constraints in the prompt (e.g., "Only score the sentiment if the term 'loss' refers to a balance sheet item.").&lt;br&gt;
This process of self-correction transformed the Agent into a reliable, domain-aware financial expert, achieving the resilience required for a production-ready system.&lt;br&gt;
Forward Vector: Deploying Agentic Architecture&lt;br&gt;
The AI Agents Intensive has shifted my career trajectory. I plan to take the successful architecture from my Market Sentiment Agent and scale it into a Generative Audit Fabric. This fabric will dynamically spawn and supervise specialized agents to handle compliance checks, financial statement cross-referencing, and continuous anomaly detection—creating intelligent digital collaboration at a scale currently unachievable manually.&lt;br&gt;
The AI Agents Intensive delivered a true masterclass in engineering reliable autonomy. I now possess the confidence, and more importantly, the strategic framework, to tackle real-world automation challenges and actively lead development in the next generation of truly intelligent systems.This is a submission for the &lt;a href="https://dev.to/challenges/googlekagglechallenge"&gt;Google AI Agents Writing Challenge&lt;/a&gt;: Learning Reflections*&lt;/p&gt;

</description>
      <category>googleaichallenge</category>
      <category>ai</category>
      <category>agents</category>
      <category>devchallenge</category>
    </item>
  </channel>
</rss>
