Understanding AI Systems

𝗧𝗵𝗲 𝗔𝗜 𝗔𝗴𝗲𝗻𝘁𝘀 𝗦𝘁𝗮𝗶𝗿𝗰𝗮𝘀𝗲 represents the 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝗱 𝗲𝘃𝗼𝗹𝘂𝘁𝗶𝗼𝗻 from passive AI models to fully autonomous systems. Each level builds upon the previous, creating a comprehensive framework for understanding how AI capabilities progress from basic to advanced: BASIC FOUNDATIONS: • 𝗟𝗮𝗿𝗴𝗲 𝗟𝗮𝗻𝗴𝘂𝗮𝗴𝗲 𝗠𝗼𝗱𝗲𝗹𝘀: The foundation of modern AI systems, providing text generation capabilities • 𝗘𝗺𝗯𝗲𝗱𝗱𝗶𝗻𝗴𝘀 & 𝗩𝗲𝗰𝘁𝗼𝗿 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲𝘀: Critical for semantic understanding and knowledge organization • 𝗣𝗿𝗼𝗺𝗽𝘁 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴: Optimization techniques to enhance model responses • 𝗔𝗣𝗜𝘀 & 𝗘𝘅𝘁𝗲𝗿𝗻𝗮𝗹 𝗗𝗮𝘁𝗮 𝗔𝗰𝗰𝗲𝘀𝘀: Connecting AI to external knowledge sources and services INTERMEDIATE CAPABILITIES: • 𝗖𝗼𝗻𝘁𝗲𝘅𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁: Handling complex conversations and maintaining user interaction history • 𝗠𝗲𝗺𝗼𝗿𝘆 & 𝗥𝗲𝘁𝗿𝗶𝗲𝘃𝗮𝗹 𝗠𝗲𝗰𝗵𝗮𝗻𝗶𝘀𝗺𝘀: Short and long-term memory systems enabling persistent knowledge • 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻 𝗖𝗮𝗹𝗹𝗶𝗻𝗴 & 𝗧𝗼𝗼𝗹 𝗨𝘀𝗲: Enabling AI to interface with external tools and perform actions • 𝗠𝘂𝗹𝘁𝗶-𝗦𝘁𝗲𝗽 𝗥𝗲𝗮𝘀𝗼𝗻𝗶𝗻𝗴: Breaking down complex tasks into manageable components • 𝗔𝗴𝗲𝗻𝘁-𝗢𝗿𝗶𝗲𝗻𝘁𝗲𝗱 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸𝘀: Specialized tools for orchestrating multiple AI components ADVANCED AUTONOMY: • 𝗠𝘂𝗹𝘁𝗶-𝗔𝗴𝗲𝗻𝘁 𝗖𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗶𝗼𝗻: AI systems working together with specialized roles to solve complex problems • 𝗔𝗴𝗲𝗻𝘁𝗶𝗰 𝗪𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀: Structured processes allowing autonomous decision-making and action • 𝗔𝘂𝘁𝗼𝗻𝗼𝗺𝗼𝘂𝘀 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴 & 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻-𝗠𝗮𝗸𝗶𝗻𝗴: Independent goal-setting and strategy formulation • 𝗥𝗲𝗶𝗻𝗳𝗼𝗿𝗰𝗲𝗺𝗲𝗻𝘁 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 & 𝗙𝗶𝗻𝗲-𝗧𝘂𝗻𝗶𝗻𝗴: Optimization of behavior through feedback mechanisms • 𝗦𝗲𝗹𝗳-𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗔𝗜: Systems that improve based on experience and adapt to new situations • 𝗙𝘂𝗹𝗹𝘆 𝗔𝘂𝘁𝗼𝗻𝗼𝗺𝗼𝘂𝘀 𝗔𝗜: End-to-end execution of real-world tasks with minimal human intervention The Strategic Implications: • 𝗖𝗼𝗺𝗽𝗲𝘁𝗶𝘁𝗶𝘃𝗲 𝗗𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁𝗶𝗮𝘁𝗶𝗼𝗻: Organizations operating at higher levels gain exponential productivity advantages • 𝗦𝗸𝗶𝗹𝗹 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: Engineers need to master each level before effectively implementing more advanced capabilities • 𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗣𝗼𝘁𝗲𝗻𝘁𝗶𝗮𝗹: Higher levels enable entirely new use cases from autonomous research to complex workflow automation • 𝗥𝗲𝘀𝗼𝘂𝗿𝗰𝗲 𝗥𝗲𝗾𝘂𝗶𝗿𝗲𝗺𝗲𝗻𝘁𝘀: Advanced autonomy typically demands greater computational resources and engineering expertise The gap between organizations implementing advanced agent architectures versus those using basic LLM capabilities will define market leadership in the coming years. This progression isn't merely technical—it represents a fundamental shift in how AI delivers business value. Where does your approach to AI sit on this staircase?

Multi-Head Attention (MHA) is the engine of LLMs. But over the years, we have added several tweaks to make it more efficient for long-context settings, especially when using KV caching during inference. I implemented the most common variants from scratch: 1) Grouped-Query Attention (GQA): Instead of having a unique key and value for each query head, multiple queries share the same key and value. As long as the sharing ratio is not too extreme, this has minimal impact on model quality. It is the most widely used variant today and found in almost every modern LLM including Llama 2-4, GPT-OSS, Gemma 3, Qwen 3, GLM 4.6, and many others. 2) Multi-Head Latent Attention (MLA): This variant introduces a compressed latent representation for the keys and values that are stored in the KV cache. During inference, these latent keys and values are up-projected back to the full dimension. The extra projection adds a small computational cost, but the memory savings make it worth it. This approach is currently used by DeepSeek V3 and Kimi K2. 3) Sliding-Window Attention (SWA): SWA restricts each token’s attention span to a fixed local window, which reduces memory needs by shrinking the KV cache in long-context regimes. It is usually applied selectively, for example every other layer, or in Gemma 3's case, five SWA layers for each full-attention layer. While less common today, it remains an important optimization, notably in Gemma 3. All three variants, GQA, MLA, and SWA, can also be combined freely within the same model. Here's a link to check them out: 1️⃣ GQA: https://lnkd.in/grDPXUUi 2️⃣ MLA: https://lnkd.in/gm4FzE32 3️⃣ SWA: https://lnkd.in/g7x-fdgn

Microsoft just released a 35-page report on medical AI - and it’s a reality check for healthcare. The paper, “The Illusion of Readiness”, tested six of the most popular models (OpenAI, Gemini, etc)… across six multimodal medical benchmarks. And the verdict? The models scored high on medical exams. But they’re not even close to being real-world ready. Here’s what the stress tests revealed: ▶ 1. Shortcut learning Models often answered correctly even when key information, like medical images, was removed. They weren’t reasoning - they were exploiting statistical shortcuts. That means benchmark wins may hide shallow understanding. ▶ 2. Fragile under small changes Making small tweaks caused big swings in predictions. This fragility shows how unreliable model reasoning becomes under stress. In visual substitution tests, accuracy dropped from 83% to 52% when images were swapped - exposing shallow visual–answer pairings. ▶ 3. Fabricated reasoning Models produced confident, step-by-step medical explanations - but many were medically unsound… or entirely fabricated. Convincing to the eye, dangerous in practice. And more importantly, healthcare isn’t a multiple-choice exam. It’s uncertainty, incomplete data, and high stakes. So Microsoft’s team calls for new standards: - Stress tests that expose fragility - Clinician-guided guidelines that profile benchmarks - Evaluation of robustness and trustworthiness - not just leaderboard scores The takeaway is simple: Medical AI may ace tests today. But until it proves reliable under stress, it’s not ready for the clinic. When do you think popular LLMs will be clinic-ready? #entrepreneurship #healthtech #AI

Finally, Amazon’s big move in AI & hardware is here! They just announced their own foundation models, 75% cheaper with better performance. Plus AI chips & supercomputers. Plus their AI ecosystem. The AI race just got more exciting! Here's the breakdown: ◾AWS has launched the 𝐓𝐫𝐚𝐢𝐧𝐢𝐮𝐦 2 𝐀𝐈 𝐜𝐡𝐢𝐩 for large-scale AI supercomputers, some impressive capabilities: - 4x faster training & 30% better performance per dollar - Simplified design with 2 chips per unit and streamlined cooling systems - Partnerships with Anthropic and Databricks, deployment in Ohio data centers ◾It’s not just about chips - Amazon is also introducing a suite of 𝐀𝐈 𝐟𝐨𝐮𝐧𝐝𝐚𝐭𝐢𝐨𝐧 𝐦𝐨𝐝𝐞𝐥𝐬: - Cost-Effective: Up to 75% lower costs for training compared to competitors. - Diverse applications (Nova Micro and Nova Lite for foundational tasks; Nova Pro: A highly capable multimodal model; Nova Canvas for image and Nova Reel for video) These models are modular, scalable, and open-source-friendly, empowering developers with flexibility and innovation. ◾𝐄𝐜𝐨𝐬𝐲𝐬𝐭𝐞𝐦 𝐚𝐫𝐨𝐮𝐧𝐝 𝐓𝐫𝐚𝐢𝐧𝐢𝐮𝐦 2 Amazon is redefining data center efficiency by treating entire centers as a unified “computer”, optimizing AI workloads with partnerships like those with Anthropic and Databricks. Still, there’s a key challenge: software simplicity. NVIDIA’s CUDA ecosystem dominates due to its developer-friendly toolkit, while Amazon’s Neuron SDK is still maturing, which could slow adoption. ◾𝐒𝐚𝐠𝐞𝐌𝐚𝐤𝐞𝐫 𝐔𝐧𝐢𝐟𝐢𝐞𝐝 𝐒𝐭𝐮𝐝𝐢𝐨 It's Amazon's ecosystem extension- integrating data, analytics, and generative AI to streamline workflows: - Integrated Bedrock IDE: Offers tools for RAG, guardrails, and model evaluation. - Lakehouse Integration: Provides seamless access to data lakes and warehouses. ◾𝐎𝐩𝐞𝐧-𝐬𝐨𝐮𝐫𝐜𝐞 𝐌𝐮𝐥𝐭𝐢-𝐀𝐠𝐞𝐧𝐭 𝐬𝐲𝐬𝐭𝐞𝐦𝐬 𝐨𝐧 𝐁𝐞𝐝𝐫𝐨𝐜𝐤 Amazon's Multi-Agent Collaboration on Bedrock facilitates the creation of specialized AI agents for complex workflows. These agents can coordinate tasks like investment analysis and supply chain optimization, aligning with open-source community goals. NVIDIA will not be dethroned overnight, but it will be fascinating to see how the healthy competition among those tech giants could reshape the AI hardware market in the years ahead. Looking forward to seeing AI products that are not just getting smarter, but also more accessible and affordable. (Alexa seems to work better after it upgrades to Claude AI from Anthropic, but also not free anymore) Anyway, hope this will bring a new wave of innovation. How about you, any thoughts on the news? __________________ For more AI news and learning materials, please check my previous posts. I share my learning journey here. Join me and let's grow together. Alex Wang #artificialintelligence #bussiness #technology #innovation

Ever wondered where the future of AI is being built? I just visited the data centre in Finland that's making it happen. Nebius’ data centre is the powerhouse where AI models are trained. Thousands of GPUs working in unison. It’s expanding to host up to 60,000 GPUs dedicated to intensive AI workloads. They’re building a full-stack AI cloud platform. Here’s what I learned: 1. There is a scarcity of GPUs in the US • Clusters are being sold in massive packages • People who need smaller requirements can’t find them 2. Nebius are building a self-serve platform • Cover infrastructure requirements from a single GPU to big GPU clusters • They’re not a GPU reseller—they’re designing the servers and the racks from the ground up 3. Applications • Helped Mistral train their multimodal models • Provide full-stack infrastructure for AI model development Something else that was unique about the visit. Nebius cools the servers in Finland using the outside air. The heat that’s generated from the servers is then shipped back into the grid. This means Nebius not only heats the onsite building, But it also heats homes nearby, benefitting the local community. They’re able to recover 70% of the heat generated. And it’s the first in the world to have this heat reuse application connected to the local municipal grid. They’re now investing over $1B in AI data centres in Europe. I feel the future of AI depends on infrastructure like this that balances performance with sustainability. Follow me Alex Banks for daily AI highlights & insights.

Anthropic 𝗷𝘂𝘀𝘁 𝗿𝗲𝗹𝗲𝗮𝘀𝗲𝗱 𝗮 𝗱𝗲𝗻𝘀𝗲 𝗮𝗻𝗱 𝗵𝗶𝗴𝗵𝗹𝘆 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝗿𝗲𝗽𝗼𝗿𝘁 𝗼𝗻 𝗵𝗼𝘄 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝗲𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀 — 𝗽𝗮𝗰𝗸𝗲𝗱 𝘄𝗶𝘁𝗵 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗶𝗻𝘀𝗶𝗴𝗵𝘁𝘀 𝗳𝗿𝗼𝗺 𝗿𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝗱𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁𝘀: ⬇️ Not just marketing, BUT a real, practical blueprint for developers and teams building AI agents that actually work. It explains how Claude Code (tool for agentic coding) can function as a software developer: writing, reviewing, testing, and even managing Git workflows autonomously. BUT in my view: The principles and patterns described in this document are not Claude-specific. You can apply them to any coding agent — from OpenAI’s Codex to Goose, Aider, or even tools like Cursor and GitHub Copilot Workspace. 𝗛𝗲𝗿𝗲 𝗮𝗿𝗲 7 𝗸𝗲𝘆 𝗶𝗻𝘀𝗶𝗴𝗵𝘁𝘀 𝗳𝗼𝗿 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗯𝗲𝘁𝘁𝗲𝗿 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀 — 𝘁𝗵𝗮𝘁 𝘄𝗼𝗿𝗸 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝘄𝗼𝗿𝗹𝗱: ⬇️ 1. 𝗔𝗴𝗲𝗻𝘁 𝗱𝗲𝘀𝗶𝗴𝗻 ≠ 𝗷𝘂𝘀𝘁 𝗽𝗿𝗼𝗺𝗽𝘁𝗶𝗻𝗴 ➜ It’s not about clever prompts. It’s about building structured workflows — where the agent can reason, act, reflect, retry, and escalate. Think of agents like software components: stateless functions won’t cut it. 2. 𝗠𝗲𝗺𝗼𝗿𝘆 𝗶𝘀 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 ➜ The way you manage and pass context determines how useful your agent becomes. Using summaries, structured files, project overviews, and scoped retrieval beats dumping full files into the prompt window. 3. 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴 𝗶𝘀𝗻’𝘁 𝗼𝗽𝘁𝗶𝗼𝗻𝗮𝗹 ➜ You can’t expect an agent to solve multi-step problems without an explicit process. Patterns like plan > execute > review, tool use when stuck, or structured reflection are necessary. And they apply to all models, not just Claude. 4. 𝗥𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝗮𝗴𝗲𝗻𝘁𝘀 𝗻𝗲𝗲𝗱 𝗿𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝘁𝗼𝗼𝗹𝘀 ➜ Shell access. Git. APIs. Tool plugins. The agents that actually get things done use tools — not just language. Design your agents to execute, not just explain. 5. 𝗥𝗲𝗔𝗰𝘁 𝗮𝗻𝗱 𝗖𝗼𝗧 𝗮𝗿𝗲 𝘀𝘆𝘀𝘁𝗲𝗺 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀, 𝗻𝗼𝘁 𝗺𝗮𝗴𝗶𝗰 𝘁𝗿𝗶𝗰𝗸𝘀 ➜ Don’t just ask the model to “think step by step.” Build systems that enforce that structure: reasoning before action, planning before code, feedback before commits. 6. 𝗗𝗼𝗻’𝘁 𝗰𝗼𝗻𝗳𝘂𝘀𝗲 𝗮𝘂𝘁𝗼𝗻𝗼𝗺𝘆 𝘄𝗶𝘁𝗵 𝗰𝗵𝗮𝗼𝘀 ➜ Autonomous agents can cause damage — fast. Define scopes, boundaries, fallback behaviors. Controlled autonomy > random retries. 7. 𝗧𝗵𝗲 𝗿𝗲𝗮𝗹 𝘃𝗮𝗹𝘂𝗲 𝗶𝘀 𝗶𝗻 𝗼𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻 ➜ A good agent isn’t just a wrapper around an LLM. It’s an orchestrator: of logic, memory, tools, and feedback. And if you’re scaling to multi-agent setups — orchestration is everything. Check the comments for the original material! Enjoy! Save 💾 ➞ React 👍 ➞ Share ♻️ & follow for everything related to AI Agents!

Last week, Chinese AI company DeepSeek shocked the AI industry with the release of R1, their open-sourced reasoning model. Yesterday, the stock market noticed too. To help us understand the significance of this technological and geopolitical moment, I’ve co-authored a piece in The Washington Post about DeepSeek and open-source models. DeepSeek-R1, which matches models like OpenAI’s o1 in logic tasks including math and coding, costs only 2% of what OpenAI charges to run, and was built with far fewer resources. And most importantly, it’s an open-source model, meaning that DeepSeek has published the model’s weights, allowing anyone to use them to create and train their own AI models.   Up until now, closed-source models like those coming out of American tech companies have been winning the AI race. But my co-author Dhaval Adjodah and I argue in our piece that DeepSeek-R1 should make us question our assumption that closed-source models will necessarily remain dominant. Open-source models may become a key component of the AI ecosystem, and the United States should not cede leadership in this space. As we conclude in our article: “America’s competitive edge has long relied on open science and collaboration across industry, academia and government. We should embrace the possibility that open science might once again fuel American dynamism in the age of AI.” It was a pleasure to collaborate on this article with Dhaval, whose company MakerMaker.AI is on the cutting-edge of AI technology, building AI agents that build AI agents. What do you think about the future of open vs. closed-source AI? Read the full op-ed here: https://lnkd.in/eXK5YdWk. 

A Manhattan federal judge has delivered a really important ruling on artificial intelligence and legal practice - can you claim legal privilege over AI generated documents? It’s a potential major blind spot for organisations - and a huge responsibility for in-house lawyers to explain the issue to their non-legal colleagues. On 10 February, U.S. District Judge Jed Rakoff ruled in USA v. Heppner that a criminal defendant could not claim attorney-client privilege over documents he had himself prepared using an AI service and then subsequently sent to his lawyers. Bradley Heppner, former chairman of GWG Holdings, faces fraud charges over an alleged $150 million scheme, with trial set for April. But the privilege ruling carries significance beyond any single case. The reasoning rests on a principle that long predates artificial intelligence. Privilege protects confidential communications between lawyer and client made for the purpose of legal advice. It does not automatically attach to materials a client creates independently simply because those materials are later forwarded to counsel. What matters is how the document came to exist, not its destination. What AI changes is the scale of the problem. Generative AI tools now allow any executive to produce polished case narratives, issue summaries, and chronologies that resemble legal work product, all without a lawyer’s involvement. The natural instinct is to assume that once these materials are emailed to counsel, they enter the protected sphere. Judge Rakoff’s ruling suggests otherwise - the court’s focus is on what the document is and how it came to exist, not on the fact that it was subsequently routed to a lawyer. This matters because AI is rapidly becoming the default tool through which businesspeople process complex situations. An executive facing a regulatory investigation who uses a chatbot to organise the facts and draft a summary for their lawyer may be creating discoverable material that sits entirely outside the privileged relationship. Judge Rakoff also noted that the AI-generated materials could prove “problematic” if used at trial. Even where privilege is not the issue, AI-authored documents create genuine evidential difficulties - questions of authorship, accuracy, hearsay characterisation, and the optics of presenting AI-mediated narratives as though they were direct recollection. If you want AI-assisted materials to have any chance of privilege protection, “Client-produced and then forwarded to counsel” is the weak fact pattern, and after this ruling, in the US at least, it may be no fact pattern at all.

AI Engineering has levels to it: – Level 1: Using AI Start by mastering the fundamentals: -- Prompt engineering (zero-shot, few-shot, chain-of-thought) -- Calling APIs (OpenAI, Anthropic, Cohere, Hugging Face) -- Understanding tokens, context windows, and parameters (temperature, top-p) With just these basics, you can already solve real problems. – Level 2: Integrating AI Move from using AI to building with it: -- Retrieval Augmented Generation (RAG) with vector databases (Pinecone, FAISS, Weaviate, Milvus) -- Embeddings and similarity search (cosine, Euclidean, dot product) -- Caching and batching for cost and latency improvements -- Agents and tool use (safe function calling, API orchestration) This is the foundation of most modern AI products. – Level 3: Engineering AI Systems Level up from prototypes to production-ready systems: -- Fine-tuning vs instruction-tuning vs RLHF (know when each applies) -- Guardrails for safety and compliance (filters, validators, adversarial testing) -- Multi-model architectures (LLMs + smaller specialized models) -- Evaluation frameworks (BLEU, ROUGE, perplexity, win-rates, human evals) Here’s where you shift from “it works” to “it works reliably.” – Level 4: Optimizing AI at Scale Finally, learn how to run AI systems efficiently and responsibly: -- Distributed inference (vLLM, Ray Serve, Hugging Face TGI) -- Managing context length and memory (chunking, summarization, attention strategies) -- Balancing cost vs performance (open-source vs proprietary tradeoffs) -- Privacy, compliance, and governance (PII redaction, SOC2, HIPAA, GDPR) At this stage, you’re not just building AI—you’re designing systems that scale in the real world. What else would you add?

BREAKING! The FDA just released this draft guidance, titled Artificial Intelligence-Enabled Device Software Functions: Lifecycle Management and Marketing Submission Recommendations, that aims to provide industry and FDA staff with a Total Product Life Cycle (TPLC) approach for developing, validating, and maintaining AI-enabled medical devices. The guidance is important even in its draft stage in providing more detailed, AI-specific instructions on what regulators expect in marketing submissions; and how developers can control AI bias. What’s new in it? 1) It requests clear explanations of how and why AI is used within the device. 2) It requires sponsors to provide adequate instructions, warnings, and limitations so that users understand the model’s outputs and scope (e.g., whether further tests or clinical judgment are needed). 3) Encourages sponsors to follow standard risk-management procedures; and stresses that misunderstanding or incorrect interpretation of the AI’s output is a major risk factor. 4) Recommends analyzing performance across subgroups to detect potential AI bias (e.g., different performance in underrepresented demographics). 5) Recommends robust testing (e.g., sensitivity, specificity, AUC, PPV/NPV) on datasets that match the intended clinical conditions. 6) Recognizes that AI performance may drift (e.g., as clinical practice changes), therefore sponsors are advised to maintain ongoing monitoring, identify performance deterioration, and enact timely mitigations. 7) Discusses AI-specific security threats (e.g., data poisoning, model inversion/stealing, adversarial inputs) and encourages sponsors to adopt threat modeling and testing (fuzz testing, penetration testing). 8) And proposed for public-facing FDA summaries (e.g., 510(k) Summaries, De Novo decision summaries) to foster user trust and better understanding of the model’s capabilities and limits.