This analysis was produced by an AI financial research system. All data is sourced exclusively from publicly available filings, earnings transcripts, government data, and free financial aggregators — no proprietary data, paid research, or institutional tools are used. Every figure cited can be independently verified by the reader using the sources listed at the end...
The post Walmart Inc. (WMT) — AI Equity Research | April 2026 appeared first on 1redDrop.
In the latest in our series of interviews meeting the AAAI/SIGAI Doctoral Consortium participants, we caught up with Aniket Roy to find out more about his research on generative models for computer vision tasks.
I recently completed my PhD in Computer Science at Johns Hopkins University, where I worked under the supervision of Bloomberg Distinguished Professor Rama Chellappa. My research primarily focused on developing methods for resource-constrained image generation and visual understanding. In particular, I explored how modern generative models can be adapted to operate efficiently while maintaining strong performance.
During my PhD, I worked broadly at the intersection of generative AI, multimodal learning, and few-shot learning. Much of my work involved designing techniques that enable models to learn new concepts or perform complex visual tasks with limited data or computational resources. This included research on diffusion models, personalized image generation, and multimodal representation learning. Overall, my work aims to make advanced vision and generative AI systems more adaptable, efficient, and practical for real-world applications.
During my PhD, my research broadly focused on improving the adaptability, efficiency, and quality of modern generative models for computer vision tasks. The rapid progress in generative AI–particularly diffusion models and vision–language models–has created new opportunities to address long-standing challenges such as data scarcity, controllable generation, and personalized image synthesis. My work aimed to develop methods that allow these large models to adapt effectively with limited data and computational resources while maintaining high visual fidelity.
One line of my research addressed learning in data-constrained settings. For example, I proposed FeLMi, a few-shot learning framework that leverages uncertainty-guided hard mixup strategies to improve robustness and generalization when only a small number of labeled samples are available. Building on this idea of improving training data quality, I also developed Cap2Aug, which introduces caption-guided multimodal augmentation. This approach uses textual descriptions to guide synthetic image generation, improving visual diversity while reducing the domain gap between real and generated data.
Overview of Cap2Aug.
Another aspect of my research focused on improving the perceptual quality of images generated by diffusion models. In this direction, I proposed DiffNat, a plug-and-play regularization method based on the kurtosis-concentration property observed in natural images. By incorporating this principle into diffusion models through a KC loss, the generated images exhibit more natural texture statistics and improved perceptual realism, which also benefits downstream vision tasks.
A major part of my work explored personalization and efficient adaptation of large generative models. I introduced DuoLoRA, a parameter-efficient framework for composing low-rank adapters that enables fine-grained control over content and style without requiring full retraining of the base model. I further extended personalization to zero-shot settings using a training-free textual inversion approach that allows arbitrary objects to be customized directly during generation. Finally, I proposed MultiLFG, a frequency-guided multi-LoRA composition framework that uses wavelet-domain representations and timestep-aware weighting to enable accurate and training-free fusion of multiple concepts in diffusion models.
Overview of DuoLoRA.
Overall, my research contributes toward building generative systems that are more efficient, adaptable, and controllable, enabling high-quality image generation and understanding even in data-limited or resource-constrained scenarios.
One project that I found particularly interesting during my PhD is DiffNat, which was published in TMLR 2025. Diffusion models have become the backbone of many modern generative AI systems and have achieved impressive results in generating and editing realistic images. However, improving the perceptual quality and naturalness of generated images remains an important challenge.
Overview of DiffNat.
In this work, we introduced a simple but effective regularization technique called the kurtosis concentration (KC) loss, which can be integrated into standard diffusion model pipelines as a plug-and-play component. The idea was inspired by a statistical property of natural images: when an image is decomposed into different band-pass filtered versions–for example using the Discrete Wavelet Transform–the kurtosis values across these frequency bands tend to be relatively consistent. In contrast, generated images often show large discrepancies across these bands. Our method reduces the gap between the highest and lowest kurtosis values across the frequency components, encouraging the generated images to follow more natural image statistics.
In addition, we introduced a condition-agnostic perceptual guidance strategy during inference that further improves image fidelity without requiring additional training signals. We evaluated the approach across several diverse tasks, including personalized few-shot finetuning with text guidance, unconditional image generation, image super-resolution, and blind face restoration. Across these tasks, incorporating the KC loss and perceptual guidance consistently improved perceptual quality, measured through metrics such as FID and MUSIQ, as well as through human evaluation.
What I particularly liked about this project is that it connects classical image statistics with modern diffusion models. It shows that relatively simple statistical insights about natural images can still play a powerful role in improving large generative models.
During my PhD, I discovered that I genuinely enjoy the process of research–especially the moment when an intuition or idea turns out to work in practice. That process of exploring new ideas and pushing the boundaries of what we know is something I find very motivating.
To continue pursuing this, I will be joining NEC Laboratories America as a Research Scientist. In this role, I hope to build on my PhD work by developing new methods for generative models and exploring how these models can interact with broader multimodal systems. In particular, I am interested in advancing research at the intersection of generative models, vision–language–action models, and embodied AI. More broadly, my goal is to contribute to the development of intelligent systems that can understand, generate, and interact with the visual world more effectively, while also continuing to push forward the scientific understanding of these models.
My interest in computer vision and machine learning started during my undergraduate studies, when I took courses in signal processing and image processing. I found those subjects particularly fascinating because they allowed you to experiment with algorithms and immediately see their effects on images. That visual and intuitive aspect made the field very engaging, and it helped me appreciate how mathematical concepts can directly translate into meaningful visual results.
At the same time, I was also curious about how the human brain processes visual information—how we are able to recognize objects, understand scenes, and interpret complex visual signals so effortlessly. That curiosity led me to wonder whether we could design computational models that mimic aspects of human perception and enable machines to understand visual data in a similar way.
A major influence during this time was my professor, Dr. Kuntal Ghosh, who encouraged me to think more deeply about these problems and approach them with a scientific mindset. His mentorship played an important role in shaping my interest in research. Since then, that curiosity about visual perception and intelligent systems has continued to drive my work in computer vision and machine learning.
Unfortunately, I was not able to attend the AAAI Doctoral Consortium in person due to visa-related issues. However, a colleague kindly helped present my poster on my behalf during the event. Even though I could not be there physically, I was very encouraged by the response my work received. Several researchers reached out to me after seeing the poster, and we had some very insightful discussions about the ideas and potential future directions of the research. In that sense, I still found the experience quite rewarding. The Doctoral Consortium is a great platform for sharing early-stage ideas, receiving feedback from the community, and connecting with other researchers working on related problems. I appreciated the opportunity to engage with people who were interested in the work, and those interactions helped spark new perspectives and collaborations.
Outside of research, I’m a big fan of music and stand-up comedy, and I really enjoy traveling whenever I get the chance. Exploring new places, cultures, and perspectives is something I find refreshing—it’s a great way to recharge and stay curious about the world beyond work. I also enjoy writing poetic satire from time to time, and I occasionally perform it. It’s a fun creative outlet that allows me to mix humor and storytelling, which is quite different from the analytical nature of the research work I usually do.
|
Aniket is currently a Research Scientist at NEC Labs America. He obtained his PhD from the Computer Science dept at Johns Hopkins University under the guidance of Bloomberg Distinguished Professor Prof. Rama Chellappa. Prior to that, he did a Master’s from Indian Institute of Technology Kharagpur. He was recognized with the Best Paper Award at IWDW 2016 and the Markose Thomas Memorial Award for the best research paper at the Master’s level. During PhD, he explored domains of few-shot learning, multimodal learning, diffusion models, LLMs, LoRA merging with publications in leading venues such as NeurIPS, ICCV, TMLR, WACV, CVPR and also 3 US patents filed. During his PhD, he also gained industrial experience through multiple internships in Amazon, Qualcomm, MERL, and SRI International. He was awarded as an Amazon Fellow (2023-24) at JHU and selected to participate in ICCV’25 and AAAI’26 doctoral consortium. |
When your website goes down, you know it immediately. Alerts fire, users complain, revenue may stop. When your AI agents fail, none of that happens. They keep responding. They just respond wrong.
Agents can appear fully operational while hallucinating policy details, losing conversation context mid-session, or burning through token budgets until rate limits shut them down.
Zero-downtime for AI agents isn’t the same as infrastructure uptime. It means preserving behavioral continuity, controlling costs, and maintaining decision quality through every deployment, update, and scaling event. This post is for the teams responsible for making that happen.
Key takeaways
Your web services either respond or they don’t. Databases either accept queries or they fail. But your AI agents don’t work that way. They remember context across a conversation, produce different outputs for identical inputs, make multi-step decisions where latency compounds, and consume real budget with every token processed.
“Working” and “failing” aren’t binary for agents. That’s what makes them hard to monitor and harder to deploy safely.
System uptime is binary: Infrastructure responds, endpoints return 200s, and logs show activity.
Functional uptime is what matters. Your agent produces accurate, timely, and cost-effective outputs that users can trust.
The difference plays out like this:
“Up and running” is not the same as “working as intended.” For enterprise AI, only the latter counts.
Traditional software throws errors. AI agents don’t — they produce confidently wrong answers instead. Because large language models (LLMs) are non-deterministic, failures surface as subtly degraded outputs, not 500 errors. Users can’t tell the difference between a model limitation and a deployment problem, which means trust erodes before anyone on your team knows something is wrong.
Deployment strategies for agents must detect behavioral degradation, not just error rates. Traditional DevOps wasn’t built for systems that degrade instead of crash.
Real zero-downtime for enterprise AI agents requires managing three distinct tiers — each entering the lifecycle at a different stage, each with different owners:
Most teams have tier one covered. The gaps that break production agents live in tiers two and three.
Infrastructure availability is necessary, but insufficient for agent reliability. This tier belongs to your platform, cloud, and infrastructure teams: the people keeping compute, networking, and storage operational.
Perfect infrastructure uptime guarantees only one thing: the possibility of agent success.
Traditional SLAs matter, but they stop short for agent workloads.
CPU utilization, network throughput, and disk I/O tell you nothing about whether your agent is hallucinating, exceeding token budgets, or returning incomplete responses.
Infrastructure health and agent health are not the same metric.
Kubernetes, scheduling, and resource isolation carry more weight for AI workloads than traditional applications. GPU contention degrades response quality. Cold starts interrupt conversation flow. Inconsistent runtime environments introduce subtle behavioral changes that users experience as unreliability.
When your sales assistant suddenly changes its tone or reasoning approach because of underlying infrastructure changes, that’s functional downtime, despite what your uptime dashboard may say.
This tier moves beyond machines running to models and orchestration functioning correctly together. It belongs to the ML platform, AgentOps, and MLOps teams. Latency, throughput, and orchestration integrity are the availability metrics that matter here.
Enterprise AI agents rarely rely on a single model. Orchestration chains route requests, apply reasoning, select tools, and blend responses, often across multiple specialized models per request.
Updating any single component risks breaking the entire chain. Your deployment strategy must treat multi-model updates as a unit, not independent versioning. If your reasoning model updates but your routing model doesn’t, the behavioral inconsistencies that follow won’t surface in traditional monitoring until users are already affected.
Budget overruns create hidden downtime. When an agent hits token caps mid-month, it’s functionally unavailable, regardless of what infrastructure metrics show.
Latency compounds the same way. A 500 ms slowdown across five sequential reasoning calls produces a 2.5-second user-visible delay — enough to degrade the experience, not enough to trigger an alert. Traditional availability metrics don’t account for this stacking effect. Yours need to.
Standard deployment approaches assume clean version separation, deterministic outputs, and reliable rollback to known-good states. None of those assumptions hold for enterprise AI agents.
Blue-green, canary, and rolling updates weren’t designed for stateful, non-deterministic systems with token-based economics. Each requires meaningful adaptation before it’s safe for agent deployments.
This tier is what users actually experience. It’s owned by AI product teams and agent developers, and measured through task completion, accuracy, cost per interaction, and user trust. It’s where the business value of your AI investment is realized or lost.
Losing context qualifies as functional downtime.
When a customer explains their problem to your support agent, and it then loses that context mid-conversation during a deployment rollout, that’s functional downtime — regardless of what system metrics report. Session affinity, memory persistence, and handoff continuity are availability requirements, not nice-to-haves.
Agents must survive updates mid-conversation. That demands session management that traditional applications simply don’t require.
Enterprise agents depend on external APIs, databases, and internal tools. Schema or contract changes can break agent functionality without triggering any alerts.
A minor update to your product catalog API structure can render your sales agent useless without touching a line of agent code. Versioned tool contracts and graceful degradation aren’t optional. They’re availability requirements.
Subtle prompt changes, token usage shifts, or orchestration tweaks can alter agent behavior in ways that don’t show up in metrics but are immediately apparent to users.
Deployment processes must validate behavioral consistency, not just code execution. Agent correctness requires continuous monitoring, not a one-time check at release.
Traditional deployment patterns aren’t wrong. They’re just incomplete without agent-specific adaptations.
Blue-green deployments for agents require session migration, sticky routing, and warm-up procedures that account for model loading time and cold-start penalties. Running parallel environments doubles token consumption during transition periods — a meaningful cost at enterprise scale.
Most importantly, behavioral validation must happen before cutover. Does the new environment produce equivalent responses? Does it maintain conversation context? Does it respect the same token budget constraints? These checks matter more than traditional health checks.
Even small canary traffic percentages — 1% to 5% — incur significant token costs at enterprise scale. A problematic canary stuck in reasoning loops can consume disproportionate resources before anyone notices.
Effective canary strategies for agents require output comparison and token tracking alongside traditional error rate monitoring. Success metrics must include correctness and cost efficiency, not just error rates.
Rolling updates are incompatible with most stateful enterprise agents. They create mixed-version environments that produce inconsistent behavior across multi-turn conversations.
When a user starts a conversation with version A and continues with the new version B mid-rollout, reasoning shifts — even subtly. Context handling differences between versions cause repeated questions, missing information, and broken conversation flow. That’s functional downtime, even if the service never technically went offline.
For most enterprise agents, full environment swaps with careful session handling are the only safe option.
For AI agents, observability is about agent behavior: what the agent is doing, why, and whether it’s doing it correctly. It’s the foundation of deployment safety and zero-downtime operations.
No single metric captures agent health. You need correlated visibility across correctness, cost, and latency — because each can move independently in ways that matter.
When accuracy improves but token consumption doubles, that’s a deployment decision. When latency stays flat but correctness degrades, that’s a regression. Individual metrics won’t surface either. Correlated observability will.
By the time users report agent issues, trust is already eroding. Proactive observability is what prevents that.
Effective observability tracks semantic drift in responses, flags changes in reasoning paths, and detects when agents access tools or data sources outside defined boundaries. These signals let you catch regressions before they reach users, not after.
Agent failures aren’t just technical problems — they erode trust, create compliance exposure, and put your AI strategy at risk.
Fixing that means treating deployment as an agent-first discipline: tiered monitoring across infrastructure, orchestration, and behavior; deployment strategies built for statefulness and token economics; and observability that catches drift before users do.
The DataRobot Agent Workforce Platform addresses these challenges in one place — with agent-specific observability, governance across every layer, and the operational controls enterprises need to deploy and update agents safely at scale.
Learn whyAI leaders turn to DataRobot’s Agent Workforce Platform to keep agents reliable in production.
Traditional uptime only tells you whether infrastructure responds. AI agents can appear healthy while producing incorrect answers, losing conversation state, or failing mid-workflow due to cost or latency issues, all of which are functional downtime for users.
System uptime measures whether services are reachable. Functional uptime measures whether agents behave correctly, maintain context, respond within acceptable latency, and operate within budget. Enterprise AI success depends on the latter.
LLMs are non-deterministic and degrade gradually. Instead of throwing errors, agents produce subtly worse outputs, inconsistent reasoning, or incomplete responses, making failures harder to detect and more damaging to trust.
Traditional rolling updates often break stateful agents. Blue-green and canary deployments can work, but only when adapted for session continuity, behavioral validation, token economics, and multi-model orchestration dependencies.
Teams need agent-specific observability, behavioral validation during deployments, cost-aware health signals, and governance across infrastructure, orchestration, and application layers. DataRobot’s Agent Workforce Platform provides these capabilities in one control plane, keeping agents reliable through updates, scaling, and change.
The post How to achieve zero-downtime updates in large-scale AI agent deployments appeared first on DataRobot.
For years, the technology industry has operated under the shadow of a single, green-tinted giant. NVIDIA, through a combination of visionary leadership and the early realization that GPUs were the secret sauce for parallel processing, effectively “owned” the AI market […]
The post The Sleeping Giant Wakes: Why AMD’s MLPerf Breakthrough Signals the Beginning of the End for NVIDIA’s AI Monopoly appeared first on TechSpective.
Easily the most prominent trend that emerged in AI writing in Q1 2026 is that major businesses are all-in when it comes to bringing the tech on-board.
The only problem: Rank and file employees haven’t gotten the memo.
A new study from Boston Consulting Group, for example, found that 94% of CEOs surveyed are committed to staying invested in AI — no matter how long it takes to metastasize in their organizations.
And a survey from AI consulting firm Section found that 41% of execs say AI is saving them eight hours-a-week on routine tasks.
But a new poll from Gallup simultaneously found that for all its glories, AI is only being used by 12% of workers on a daily basis.
Given that most of that 12% probably represents creative pros who are using AI writing daily to handle marketing, reports or legal work, that leaves maybe 2% of the everyday workforce that has actually embraced AI in a meaningful way.
Alarmed, some employers , like Bausch + Lomb, have resorted to bullying staff into adopting AI, threatening to withhold bonuses — or worse, indicating that without AI chops, employees’ days are numbered.
But the real solution may lie in businesses redoubling their efforts to offer highly effective training programs, which ensure workers deeply grasp how to use the new tech.
Observes Wall Street Journal writer Christopher Mims: “There is a huge gap between what AI can already do today and what most people are actually doing with it.”
Here’s detail on the key stories in Q1 2026 that revealed the AI adoption challenge – along with other significant developments in AI’s ongoing evolution:
*ChatGPT Now Clocking 900 Million Weekly Users: It’s official: 900 million people are now flocking to ChatGPT each week for AI-powered writing, answers, thinking and more.
Most of those people use the free version of ChatGPT, while about 50 million users access the AI via a paid subscription, according to writer Aisha Malik.
Adds Malik: “The new weekly active user figure marks a jump of 100 million users from the 800 million that OpenAI reported in October 2025.”
*94% of CEOs All-In on AI: A new study finds that nearly all CEOs surveyed are working to integrate AI into their businesses in 2026 – even if return-on-investment takes a while.
Even more encouraging for AI advocates: On average, those same CEOs plan to invest more than twice as much in AI during 2026 as they did the previous year.
Firms leading the way in AI are using the tech to up-skill and retrain their workforces, according to writer Cliff Saran.
*41% Execs: ‘AI Saves Me Eight Hours-a-Week:’ A new survey finds that 41% of execs using AI are saving at least eight hours a week with the tech.
Even more eye-opening: An additional 33% of execs say they’re saving at least four-to-eight hours a week with AI.
That makes 74% of execs total who say they’re reaping significant productivity gains with AI.
One downside finding of the survey: Employees tend to be less enthused about AI — which many believe can be easily solved with highly targeted training.
*AI as Journalist: At Fortune Magazine, It’s De Rigueur: As many fiction and nonfiction media outlets express outrage over AI-generated content, others are embracing it unabashedly.
Case-in-point: Fortune Magazine, where nearly 20% of all articles are generated in part by AI, according to writer Isabella Simonetti.
Most of those articles are penned – with the help of AI – by journalist Nick Lichtenberg, who has “produced more stories in six months than any of his colleagues at Fortune delivered in a year,” according to Simonetti.
*Only 12% of Workers Use AI Daily: More than three years after the release of the AI that changed the world – ChatGPT– only 12% of workers are using AI on a daily basis.
Observes writer Brandon Vigliarolo: “Frequent AI users are still a tiny minority of overall workers.”
The greatest irony here is that a $20/month ChatGPT subscription, for example, will pay for itself in the workspace, simply with its ability to significantly reduce the amount of time writing emails each day – while elevating that writing to the world-class level.
*Learn AI — Or Forget About that Bonus: Bausch + Lomb’s CEO Brent Saunders has issued a simple ultimatum to employees: Get a clue when it comes to AI, or kiss your bonus goodbye.
Observes writer Francisco Velasquez: “By tying bonuses to (AI) education, Saunders is essentially legislating the end of resistance.
“He also noted that employees risk becoming ‘irrelevant’ should they fall short of implementing AI in their career pursuits.”
*AI Training Now the Chokepoint: Wall Street Journal writer Christopher Mims reports that while AI is plenty smart across a wide spectrum of tasks, too few people know how to use AI well.
Observes Mims: “There is a huge gap between what AI can already do today and what most people are actually doing with it.”
*Slash and Burn: Elon Musk Rebuilding ChatGPT-Competitor xAI from the Ground Up: Completely disenchanted with the performance of xAI – which makes Grok, a key competitor to ChatGPT – CEO Elon Musk has decided to rip it up and start over.
Observes writer Victor Tangermann: “Musk reportedly ordered higher-ups from Tesla and SpaceX — the latter of which xAI was folded into earlier this year — to conduct audits and weed out anybody deemed to be underperforming.”
*Gemini Gets Tighter Integration with Google Workspace Suite: Google is out with a new upgrade to Gemini designed to ensure the ChatGPT competitor is more tightly integrated with Google Docs, Sheets, Slides and Drive.
Observes Yulie Kwon Kim, VP product/workspace: “Today we are re-imagining how people create content.”
Click here for the blow-by-blow that backs-up Kim’s statement.
*China’s Open-Source AI Could Upend U.S. Market: MIT Technology Review is out with a new, in-depth article warning that the rising popularity of AI created by Chinese researchers and companies could scramble U.S. hopes to continue to dominate in AI.
China’s open-source AI software is incredibly attractive to many companies, given that it can be downloaded for free – and custom-tailored or improved by anyone.
Observes writer Caiwei Chen: “If these open-source AI models keep getting better, they will not just offer the cheapest options for people who want access to frontier AI capabilities — they will change where innovation happens and who sets the standards.”
Share a Link: Please consider sharing a link to https://RobotWritersAI.com from your blog, social media post, publication or emails. More links leading to RobotWritersAI.com helps everyone interested in AI-generated writing.
–Joe Dysart is editor of RobotWritersAI.com and a tech journalist with 20+ years experience. His work has appeared in 150+ publications, including The New York Times and the Financial Times of London.
The post Top Ten Stories in AI Writing, Q1 2026 appeared first on Robot Writers AI.
Buying a high-performance engine doesn’t make you a racing team. You still need the pit crew, the logistics, the telemetry, and the discipline to run it at full speed without it blowing up on lap three.
Agentic AI is the same. The technology is no longer the hard part. What breaks enterprises is everything the AI depends on: data pipelines that weren’t built for real-time agent access, governance frameworks designed for humans making decisions (not machines making thousands of them), and legacy systems that were never meant to coordinate with an autonomous digital workforce.
Most scaling efforts stall not because the pilot failed, but because the organization behind it wasn’t built for what production actually demands: the infrastructure investment, the integration debt, the governance gaps, and the hard conversations that don’t show up in a demo.
Key takeaways
Scaling traditional software is largely a capacity problem. Add compute, optimize code, increase throughput. Scaling agentic AI introduces something different: You’re extending decision-making authority to systems operating with varying degrees of human oversight. The technical challenges are real, but the organizational ones are harder.
True scalability spans four dimensions: horizontal (expanding across departments), vertical (handling more complex, higher-stakes tasks), data (supporting volumes your current infrastructure wasn’t designed for), and integration (connecting agents to the systems they need to act on, not just read from).
The readiness questions that actually matter: Can your data infrastructure handle 100x the current volume? Does your governance model account for thousands of autonomous decisions per day, or just the ones humans review? Are your core systems accessible to agents in real time, or are you still running batch processes?
Most enterprises can answer one of these confidently. Few can answer all four.
Scaling agentic AI isn’t a milestone. It’s a progression, and where your organization sits on that curve determines what AI can realistically deliver right now.
Most enterprises move through four stages. Agents start isolated, supervised, and scoped to low-risk tasks. They graduate into specialized systems that own specific, high-value workflows. From there, coordination becomes possible, with agents working across functions to optimize entire processes. At full maturity, autonomous systems operate continuously, adapting to new information faster than manual processes can.
Each stage requires more: more governance, deeper integration, sharper measurement. Organizations that stall almost always underestimate this. They try to jump stages without evolving the controls underneath, and momentum collapses.
The measurement problem compounds this. Most enterprises can’t clearly define what scaled agentic AI looks like in their business, let alone how to measure it. Without that definition, scaling decisions get made on enthusiasm rather than evidence. And when leadership asks for proof of ROI, there’s nothing concrete to point to.
When agents coordinate across functions, the organization starts acting like a system rather than a collection of siloed teams. That’s when compounding value becomes real. But it only holds if governance scales alongside the agents themselves. Without it, the same coordination that creates value also amplifies risk.
Scale amplifies everything, including what goes wrong.
Data quality is the most underestimated vulnerability. At scale, a single corrupted data source doesn’t create one bad decision. It poisons thousands of automated decisions before anyone notices. Managing that risk requires semantic layers, automated validation, and unambiguous ownership of every data element — before, not after, agents are deployed.
Security and compliance don’t get simpler at scale either:
| Category | Without governed scaling | With governed scaling | Implementation priority |
|---|---|---|---|
| Data quality | Inconsistent, unreliable | Validated, trustworthy | Critical: Day one |
| Decision transparency | Black-box operations | Explainable AI | High: Month one |
| Security | Vulnerable endpoints | Enterprise-grade protection | Critical: Day one |
| Compliance | Ad hoc checks | Automated monitoring | High: Month two |
| Performance | Degradation at scale | Consistent SLAs | Medium: Month three |
The answer isn’t to slow down. It’s to build governance that scales at the same rate as your agent capabilities. Organizations that treat governance as a constraint find that it becomes one. Those that build it into their foundation find that it becomes a competitive advantage — the thing that lets them move faster with more confidence than competitors who are patching risk controls in after the fact.
The path from pilot to enterprise-wide deployment is where most organizations lose momentum. These steps don’t eliminate that difficulty, but they make it navigable.
Your data infrastructure will need to handle more volume, velocity, and variety than it does today. Can your systems handle a 10X to 100x increase in data processing? Identify data silos that need integration before scaling. Disconnected data doesn’t just limit AI effectiveness — it creates the kind of inconsistency that erodes trust fast.
Establish clear quality benchmarks before you scale: accuracy above 95%, completeness above 90%, and timeliness measured in seconds, not hours.
If the answer to any of these is no, fix your data foundation first.
Governance makes scaling possible. Design role-based access control for AI agents with the same rigor you apply to human users. Create audit mechanisms that show not just what happened, but why.
Bias detection and correction protocols should be proactive, not reactive. Your governance framework needs three things:
AI that can’t connect with your core systems will always be limited in impact. Map out your existing architecture, identify integration points, prioritize API development for legacy system connections, and design an orchestration layer that coordinates across all of your systems.
The integration sequence matters:
Centralized orchestration handles deployment, monitoring, and coordination across your agent workforce. Without it, agents operate in isolation, and the compounding value of coordination never materializes.
Establish KPIs that measure business impact alongside technical performance, and build feedback loops from real-world outcomes into your improvement cycle. Monitor in real time:
Define ROI in business terms before scaling begins, and let data, not enthusiasm, inform your scaling decisions. The metrics that matter most aren’t always the ones that are easiest to track.
Three performance dimensions break first at scale:
If you can’t answer these confidently at your current scale, you’re not ready to expand.
Left unmanaged, agentic AI loses relevance faster than most organizations expect. Agent models drift. Training data goes stale. Governance that was sufficient at pilot scale develops gaps at production scale.
Sustaining momentum requires focus. Target use cases that move real numbers, then reinvest those wins into broader capability. Financial returns matter, but track decision accuracy, resilience, and risk exposure too. These signals often surface problems before the balance sheet does.
Build improvement into your operating rhythm: review performance weekly, optimize monthly, expand quarterly, rethink annually.
One-time breakthroughs are exactly that. Progress comes from discipline, not momentum.
The gap between AI ambition and AI results almost never comes down to the technology. It comes down to whether orchestration, governance, and integration were built for production from the start, or assembled after the gaps became impossible to ignore.
Enterprises that close that gap don’t do it by moving faster. They do it by building the right foundation before scaling begins.
Ready to go deeper? The agentic AI enterprise playbook covers what enterprise-scale deployment actually requires in practice.
Pilots demonstrate potential but don’t reveal real operational constraints. Only scaled deployment shows whether AI can handle enterprise data volumes, governance requirements, and the complexity of coordinating across systems and functions.
Agentic AI systems make decisions autonomously, learn from outcomes, and coordinate across workflows. This introduces new requirements — semantic layers, guardrails, audit trails, and observability — that traditional software scaling doesn’t require.
At scale, agents coordinate across departments, eliminate bottlenecks, and compound improvements over time. These effects create efficiency gains and cost reductions that isolated pilots cannot produce.
Data quality issues, unmonitored decisions, biased outputs, and integration gaps can escalate quickly across thousands of autonomous actions. Governance and monitoring frameworks are essential to manage that risk.
Data readiness, unified governance standards, integration infrastructure, and executive alignment. Without these foundations, scaling increases cost, complexity, and operational risk.
The post What it takes to scale agentic AI in the enterprise appeared first on DataRobot.
This analysis was produced by an AI financial research system. All data is sourced exclusively from publicly available filings, earnings transcripts, government data, and free financial aggregators — no proprietary data, paid research, or institutional tools are used. Every figure cited can be independently verified by the reader using the sources listed at the end...
The post Berkshire Hathaway Inc. (BRK-B) — AI Equity Research | April 2026 appeared first on 1redDrop.
Proof-of-concept AI agents look great in scripted demos, but most never make it to production. According to Gartner, over 40% of agentic AI projects will be canceled by the end of 2027, due to escalating costs, unclear business value, or inadequate risk controls.
This failure pattern is predictable. It rarely comes down to talent, budget, or vendor selection. It comes down to discipline. Building an agent that behaves in a sandbox is straightforward. Building one that holds up under real workloads, inside messy enterprise systems, under real regulatory pressure is not.
The risk is already on the books, whether leadership admits it or not. Ungoverned agents run in production today. Marketing teams deploy AI wrappers. Sales deploys Slack bots. Operations embeds lightweight agents inside SaaS tools. Decisions get made, actions get triggered, and sensitive data gets touched without shared visibility, a clear owner, or enforceable controls.
The agentic AI development lifecycle exists to end that chaos, bringing every agent into a governed, observable framework and treating them as extensions of the workforce, not clever experiments.
Key takeaways
Traditional software lifecycles assume deterministic systems, but agentic AI breaks that assumption. These systems take actions, adapt to context, and coordinate across domains, which means reliability must be built in from the start and reinforced continuously.
This lifecycle is unified by design. Builders, operators, and governors aren’t treated as separate phases or separate handoffs. Development, deployment, and governance move together because separation is how fragile agents slip into production.
Every phase exists to absorb risk early. Skip one (or rush one), and the cost returns later through rework, outages, compliance exposure, and integration failures.
Effective agent development starts with humans defining clear objectives through data analysis and stakeholder input — along with explicit boundaries:
KPIs must map to measurable business outcomes, not vanity metrics. Think cost reduction, process efficiency, customer satisfaction — not just the agent’s accuracy. Accuracy without impact is noise. An agent can classify a request correctly and still fail the business if it routes work incorrectly, escalates too late, or triggers the wrong downstream action.
Clear requirements establish the governance logic that constrains agent behavior at scale — and prevent the scope drift that derails most initiatives before they reach production.
Poor data discipline is more costly in agentic AI than in any other context. These are systems making decisions that directly affect real business processes and customer experiences.
AI agents require multi-modal and real-time data. Structured records alone are insufficient. Your agents need access to structured databases, unstructured documents, real-time feeds, and contextual information from your other systems to understand:
Diverse data exposure expands behavioral coverage. Agents trained across varied scenarios encounter edge cases before production does, making them more adaptive and reliable under dynamic conditions.
Your Day 1 architecture choices determine whether agents can scale cleanly or collapse under their own complexity.
Modular architecture with reasoning, planning, and action layers is non-negotiable. Agents need to evolve without full rebuilds. Open standards and emerging interoperability protocols like Model Context Protocol (MCP) and A2A reinforce modularity, improve interoperability, reduce integration friction, and help enterprises avoid vendor lock-in while keeping optionality.
API-first design is equally critical. Agents need to be orchestrated programmatically, not confined to limited proprietary interfaces. If agents can’t be controlled through APIs, they can’t be governed at scale.
Event-driven architecture closes the loop. Agents should respond to business events in real time, not poll systems or wait for manual triggers. This keeps agent behavior aligned with operational reality instead of drifting into side workflows no one owns.
Governance must live in the architecture. Observability, logging, explainability, and oversight belong in the control plane from the start. Standardized, open architecture is how agentic AI stays an asset instead of becoming long-term technical debt.
The architecture decisions made here directly determine what’s testable in Phase 5 and what’s governable in Phase 7.
A “functionally complete” agent is not the same as a “production-ready” agent. Many teams reach a point where an agent works once, or even a hundred times in controlled environments. The real challenge is reliability at 100x scale, under unpredictable conditions and sustained load. That gap is where most initiatives stall, and why so few pilots survive contact with production.
Iterative training using reinforcement and transfer learning helps, but simulation environments and human feedback loops are necessary for validating decision quality and business impact. You’re testing for accuracy and confirming that the agent makes sound business decisions under pressure.
Testing agentic systems is fundamentally different from traditional QA. You’re not testing static behavior; you’re testing decision-making, multi-agent collaboration, and context-dependent boundaries.
Three testing disciplines define production readiness:
Traditional software either works or doesn’t. Agents operate in shades of gray, making decisions with varying degrees of confidence and accuracy. Your testing framework needs to account for that. Metrics like decision reliability, escalation appropriateness, and coordination accuracy matter as much as task completion.
Multi-agent interactions demand scrutiny because weak handoffs, resource contention, or information leakage can undermine workflows fast.
When your sales agent hands off to your fulfillment agent, does critical information transfer with it, or does it get lost in translation, or (perhaps worse) is it publicly exposed?
Testing needs to be continuous and aligned with real-world use. Evaluation pipelines should feed directly into observability and governance so failures surface immediately, land with the right teams, and trigger corrective action before the business gets caught in the blast radius.
Production environments will surface scenarios no test suite anticipated. Build systems that detect and respond to unexpected situations gracefully, escalating to human teams when needed.
Deployment is where architectural decisions either pay off or expose what was never properly resolved. Agents need to operate across hybrid or on-prem environments, integrate with legacy systems, and scale without surprise costs or performance degradation.
CI/CD pipelines, rollback procedures, and performance baselines are essential in this phase. Agent compute patterns are more demanding and less predictable than traditional applications, so resource allocation, cost controls, and capacity planning must account for agents making autonomous decisions at scale.
Performance baselines establish what “normal” looks like for your agents. When performance eventually degrades (and it will), you need to detect it quickly and identify whether the issue is data, model, or infrastructure.
The uncomfortable truth: most enterprises already have ungoverned agents in production. Wrappers, bots, and embedded tools operate outside centralized visibility. Traditional monitoring tools can’t even detect many of them, which creates compliance risk, reliability risk, and security blind spots.
Continuous discovery and inventory capabilities identify every agent deployment, whether sanctioned or not. Real-time drift detection catches agents the moment they exceed their intended scope.
Anomaly detection also surfaces performance issues and security gaps before they escalate into full-blown incidents.
Most platforms fragment responsibility. Development lives in one tool, operations in another, governance in a third. That fragmentation creates blind spots, delays accountability, and forces teams to argue over whose dashboard is “right.”
Agentic AI only works when builders, operators, and governors share the same context, the same telemetry, the same controls, and the same inventory. Unification eliminates the gaps where failures hide and projects die.
That means:
When these roles operate from a shared foundation, failures surface faster, accountability is clearer, and scale becomes manageable.
When business users and stakeholders trust that agents operate within defined boundaries, they’re more willing to expand agent capabilities and autonomy.
That’s what governance ultimately gets you. Added as an afterthought, every new use case becomes a compliance review that slows deployment.
Traceability and accountability don’t happen by accident. They require audit logging, responsible AI standards, and documentation that holds up under regulatory scrutiny — built in from the start, not assembled under pressure.
Approval workflows, access controls, and performance audits create the structure that moves toward more controlled autonomy. Role-based permissions separate development, deployment, and oversight responsibilities without creating silos that slow progress.
Centralized agent registries provide visibility into what agents exist, what they do, and how they’re performing. This visibility reduces duplicate effort and surfaces opportunities for agent collaboration.
Security for agentic AI goes beyond traditional cybersecurity. The decision-making process itself must be secured — not just the data and infrastructure around it. Zero-trust principles, encryption, role-based access, and anomaly detection need to work together to protect both agent decision logic and the data agents operate on.
Explainable decision-making and bias detection maintain compliance with regulations requiring algorithmic transparency. When agents make decisions that affect customers, employees, or business outcomes, the ability to explain and justify those decisions isn’t optional.
Transparency also provides board-level confidence. When leadership understands how agents make decisions and what safeguards are in place, expanding agent capabilities becomes a strategic conversation rather than a governance hurdle.
Scaling multiplies complexity fast. Managing a handful of agents is straightforward. Coordinating dozens to operate like members of your workforce is not.
This is the shift from “project AI” to “production AI,” where you’re moving from proving agents can work to proving they can work reliably at enterprise scale.
The coordination challenges are concrete:
Early coordination decisions determine whether scale creates leverage, creates conflict, or creates risk. Get the orchestration architecture right before the complexity multiplies.
Post-deployment learning separates good agents from great ones. But the feedback loop needs to be systematic, not accidental.
The cycle is straightforward:
Observe → Diagnose → Validate → Deploy
Automated feedback captures performance metrics and black-and-white outcome data, while human-in-the-loop feedback provides the context and qualitative assessment that automated systems can’t generate on their own. Together, they create a continuous improvement mechanism that gets smarter as the agent workforce grows.
Resource allocation and capacity planning must account for how differently agents consume infrastructure compared to traditional applications. A conventional app has predictable load curves. Agents can sit idle for hours, then process thousands of requests the moment a business event triggers them.
That unpredictability turns infrastructure planning into a business risk if it’s not managed deliberately. As agent portfolios grow, cost doesn’t increase linearly. It jumps, sometimes without warning, unless guardrails are already in place.
The difference at scale is significant:
The goal is infrastructure controls that prevent cost surprises without constraining the scaling that drives business value. That means automated scaling policies, cost alerts, and resource optimization that learns from agent behavior patterns over time.
Agentic AI works best when it enhances human teams, freeing people to focus on what human judgment does best: strategy, creativity, and relationship-building.
The most successful implementations create new roles rather than eliminate existing ones:
These roles reflect a broader shift: as agents take on more execution, humans move toward oversight, design, and accountability.
Moving agentic AI from pilot to production requires more than capable technology. It takes executive sponsorship, honest audits of existing AI initiatives and legacy systems, carefully selected use cases, and governance that scales with organizational ambition.
The connections between components matter as much as the components themselves. Development, deployment, and governance that operate in silos produce fragile agents. Unified, they produce an AI workforce that can carry real enterprise responsibility.
The difference between organizations that scale agentic AI and those stuck in pilot purgatory rarely comes down to the sophistication of individual tools. It comes down to whether the entire lifecycle is treated as a system, not a checklist.
Learn how DataRobot’s Agent Workforce Platform helps enterprise teams move from proof of concept to production-grade agentic AI.
Traditional SDLC and MLOps lifecycles were designed for deterministic systems that follow fixed code paths or single model predictions. The agentic AI lifecycle accounts for autonomous decision making, multi-agent coordination, and continuous learning in production. It adds phases and practices focused on autonomy boundaries, behavioral testing, ongoing discovery of new agents, and governance that covers every action an agent takes, not just its model output.
Most projects do not fail in early prototyping. They fail at the point where teams try to move from a successful proof of concept into production. At that point gaps in architecture, testing, observability, and governance show up. Agents that behaved well in a controlled environment start to drift, break integrations, or create compliance risk at scale. The lifecycle in this article is designed to close that “functionally complete versus production-ready” gap.
The first step is discovery, not shutdown. You need an accurate inventory of every agent, wrapper, and bot that touches critical systems before you can govern them. From there, you can apply standardization: define autonomy boundaries, introduce monitoring and drift detection, and bring those agents under a central governance model. DataRobot gives you a single place to register, observe, and control both new and existing agents.
The lifecycle is designed to be tool-agnostic and standards-friendly. Developers can keep building with their preferred frameworks and IDEs while targeting an API-first, event-driven architecture that uses standards and emerging interoperability protocols like MCP and A2A. DataRobot complements this by providing CLI, SDKs, notebooks, and codespaces that plug into existing workflows, while centralizing observability and governance across teams.
Many enterprises have solid pieces of the stack, but they live in silos. One team owns infra monitoring, another owns model tracking, a third manages policy and audits. DataRobot’s Agent Workforce Platform is designed to sit across these efforts and unify them around the agent lifecycle. It provides cross-environment observability, governance that covers predictive, generative, and agentic workflows, and shared views for builders, operators, and governors so you can scale agents without stitching together a new toolchain for every project.
The post The agentic AI development lifecycle appeared first on DataRobot.