Posts

Knowledge Retention & Ownership in AI based development

  Knowledge Retention & Ownership is no longer a good to have—it's the emergency. 1. Declare a comprehension freeze, not just a metric change Before any framework can work, leadership must stop the bleeding: no new AI-generated artifacts in the critical path (specs, architecture docs, PRDs) until engineers can explain what already exists. This is the "pull over the car" moment Vembu is describing. Tactic: Institute a "Explain Before Merge" mandate with teeth—if the author (or the AI) can't defend it in a 5-minute review, it doesn't ship. This directly operationalizes "never cede our understanding to AI." 2. Treat the "forced to ship" mandate as the root cause The image makes clear this isn't an emergent culture problem—it's an explicit management directive. Solutions must target leadership behavior, not engineer habits: · Escalate with cost data: AI-generated rework, incident frequency, and attrition. · Ask leadership a di...
Post a Comment
Read more

Autonomous AI Agents : Understanding the Real Risk and taking precautions

When AI Agents Go Beyond the Sandbox: Understanding the Real Risk and taking precautions  As AI systems become increasingly autonomous, one question is becoming unavoidable: What happens when an AI agent is given the ability to act in the real world rather than merely answer questions? Recent cybersecurity experiments illustrate why this question deserves serious attention—but they also show why the reality is more nuanced than headlines about an AI "escaping" or "attacking" companies might suggest. A containment failure is not the same as an AI escape In one reported cybersecurity red-team exercise, an AI agent operating during a controlled evaluation was able to access real-world corporate systems. The underlying problem was not that the AI had independently broken out of its sandbox. The testing environment had inadvertently retained live internet connectivity, while the simulated target had been given a generic name that happened to correspond to actual com...
Post a Comment
Read more

MCP, agents, and the rewiring of enterprise software

  The Convergence Stack MCP, agents, and the rewiring of enterprise software — where Jira, Outlook, Azure DevOps, OpenAI, Claude, Gemini, and Copilot are headed in 2026   1. The shift: from tools to actors Through 2023–2024, the AI conversation was about which model answered best. In 2026, the conversation is about which model can act — inside Jira, Outlook, Azure DevOps, a data warehouse, or a codebase — without a human retyping context at every step. Microsoft's own framing at Build 2026 captures the pivot: AI is moving from assisting to acting on a person's behalf. That shift required a plumbing layer. Chat interfaces didn't need one; autonomous agents touching ten different enterprise systems do. That plumbing layer is the Model Context Protocol, and its emergence is the single biggest structural change underlying everything else in this piece. 2. MCP: the connector that made agents enterprise-viable Anthropic released MCP as an open standard in Novemb...
Post a Comment
Read more

The AI ecosystem - how Meta Nvidia Pwc Deloitte Google fit ?

  The Evolving AI Solutions Landscape The AI market is moving from a simple “technology vendor” model toward a multi-layered AI transformation ecosystem . Enterprises increasingly want business outcomes , not isolated AI tools. They therefore need a combination of foundation models, cloud infrastructure, data, applications, agents, implementation, governance, and workforce transformation. No single company can optimally provide the entire stack. This is creating an ecosystem in which hyperscalers, model companies, IT-services firms, consultants, startups, and domain specialists work together . A useful way to understand the market is as follows: I. THE AI VALUE CHAIN 1. AI Infrastructure & Compute What they provide GPUs and AI accelerators Cloud infrastructure AI data centres Model hosting and inference AI development infrastructure Global leaders NVIDIA AMD Microsoft Azure AWS Google Cloud This is the “electricity and infrastructure layer” of AI. India has relatively limited...
Post a Comment
Read more

AI ecosystem - opportunities for India

  India probably does not need to compete head-on with NVIDIA or OpenAI to build a large AI industry. Its more natural opportunities are further up the value chain. Tier 1 — India's strongest existing advantages 1. AI services & implementation TCS, Infosys, HCLTech, Wipro, Tech Mahindra, LTIMindtree, Persistent etc. 2. AI consulting & transformation Big Four, Accenture and Indian IT-services companies. 3. Data engineering & analytics Fractal, Tiger Analytics, LatentView, Mu Sigma and others. 4. Enterprise AI Customer service, automation, enterprise copilots and workflow AI. Tier 2 — High-growth opportunities 5. Agentic AI AI agents that actually execute enterprise workflows. 6. Vertical AI Healthcare, pharma, BFSI, manufacturing, telecom, retail etc. 7. AI governance Especially important in regulated industries. 8. AI managed services Operating and continuously improving enterprise AI after implementation. 9. AI-enabled workforce transformation Training, adoption and r...
Post a Comment
Read more

Key Agentic AI Risks to address in User Stories in healthcare solutions

 Key agentic AI risks in user stories; Human-in-the-loop controls for AI Key Agentic AI Risks to address in User Stories Every AI-enabled user story should explicitly address these risks and define mitigation controls. 1. Hallucination Risk The AI may generate recommendations, summaries, diagnoses, codes, explanations, or actions that are not supported by source data. User Story Considerations: AI responses must reference source data. Confidence scores must be visible. Unsupported recommendations must be flagged. Human review required for high-impact decisions. 2. Patient Safety Risk Incorrect AI recommendations can impact clinical care. User Story Considerations: Define safety-critical workflows. Establish escalation paths. Require clinical approval for high-risk recommendations. Prevent autonomous execution of clinical decisions. Examples: Medication recommendations. Care plans. Diagnostic suggestions. Triage recommendations. 3. Data Quality Amplification Risk AI can spread and m...
Post a Comment
Read more