The AI landscape doesn't move in one direction — it lurches. Some techniques leap from experiment to table stakes in a single quarter; others stall against regulatory walls, technical ceilings, or organisational inertia that no amount of hype can dislodge. Knowing which is which is the hard part. The State of Play cuts through the noise with a rigorously maintained index of AI techniques across every major business domain — classified by maturity, evidenced by real-world adoption, and updated daily so you always know where you stand relative to the field. Stop guessing. Start knowing.
A daily newsletter distilling the past two weeks of movement in a domain or two — delivered to your inbox while the index updates in the background.
Each dot marks the weighted maturity of practices within a domain — hover for a brief summary, click for more detail
Comprehensive management of AI model inventories including documentation, model cards, versioning, and lifecycle tracking from development to retirement. Includes automated model card generation and deprecation workflows; distinct from model evaluation which assesses performance rather than managing metadata.
Model inventory, documentation, and lifecycle management is a leading-edge practice defined by an acute and widening gap between vendor tooling maturity and organizational adoption. The discipline covers maintaining authoritative registries of models in production, documenting capabilities and lineage via model cards, tracking versions, and governing the full lifecycle from development through retirement. By June 2026, every major cloud provider ships production-grade registries (AWS SageMaker, Databricks/MLflow, Microsoft Azure Databricks, Google Vertex AI) with formalized lifecycle governance including automated deprecation timelines. The EU AI Act enforcement deadline (August 2, 2026) has elevated model documentation and inventory from optional practice to regulatory requirement: technical documentation, model cards, and centralized AI catalogs are now baseline audit expectations across jurisdictions (EU, UK FCA/PRA, US federal guidance, state laws). Yet organizational implementation remains incomplete—the binding constraint is not tooling maturity but organizational adoption effectiveness and sustained post-deployment governance. Regulatory examinations reveal critical gaps: most US banks have only partial inventory coverage (43% cannot update live models), shadow AI (unregistered business-unit tools, vendor-embedded models, proof-of-concept systems) dominates inventory gaps, and post-deployment governance fails systematically (documentation decay, ownership dissolution, vendor updates bypassing reassessment). This is a practice where leading practitioners (Salesforce, Uber, Cisco, Databricks enterprise customers) maintain disciplined model registries with automated governance and versioned lifecycle tracking, while organizational governance remains fragmented—driven by regulatory urgency but limited by adoption barriers around documentation automation, cross-platform integration, and post-deployment accountability.
Vendor ecosystem maturity has consolidated around integrated model registry, governance, and lifecycle management platforms as table-stakes features. AWS SageMaker ML Governance suite (April 2026) automates model card generation from training metadata, integrates with DataZone for cross-org discovery, and enforces role-based access control with Model Dashboard monitoring; production customers include Cisco, Perplexity, and Salesforce (19 documented models spanning Data Cloud, Agentforce, Einstein, Marketing Cloud with versioned lifecycle tracking). Databricks MLflow on Databricks (June 2026) integrates centralized model registry with Unity Catalog, providing cross-workspace access control, lineage tracking, and automated model discovery alongside approval-gated deployment jobs with auditable activity logs. Microsoft Azure Databricks MLflow 3 (June 2026) introduces LoggedModels capturing training metrics and parameters across dev/staging/production environments with unified performance visibility when promoted to Unity Catalog. Microsoft Azure AI Foundry (September 2025) formalized model lifecycle retirement with four explicit phases (Preview, GA, Legacy, Deprecated, Retired) and concrete transition timelines (30-day legacy minimum, 90-day deprecated minimum). UiPath (May 2026) documents LLM model deprecation with four-stage lifecycle (Announced, Migration open, Action required, Deprecated) and automated fallback for bring-your-own deployments. Uber published production case study (April 2026) of centralized Model Catalog with auto-populated Model Cards integrating feature attribution (SHAP, TreeSHAP) directly into governance workflows. MLflow maintains ecosystem prominence with 30 million monthly downloads and adoption by 1000+ organizations including Databricks, Azure ML, SageMaker, and Vertex AI.
Regulatory drivers have reached enforcement stage across multiple jurisdictions. The April 17, 2026 revised federal Model Risk Management guidance from Federal Reserve, FDIC, and OCC establishes principles-based framework requiring model inventory, validation, monitoring, and vendor governance for all US banks >$30B; regulatory examinations show 43% of banks cannot update live models and 38% struggle sustaining governance across growing inventories, with self-learning models and agent orchestration layers systematically missing from inventories. UK FCA and PRA (May 2026) mandate model identification, classification, and governance under Supervisory Statement SS1/23, with explicit language that unregistered AI use is a direct control gap. EU AI Act (effective August 2, 2026) requires technical documentation and model cards for high-risk AI systems with penalties reaching €35M or 7% global turnover. Consultancies explicitly map model documentation to regulatory frameworks (NIST AI RMF, ISO/IEC 42001), establishing centralized AI catalogs with versioning and risk documentation as baseline audit expectations.
Critical adoption barriers persist despite vendor maturity and regulatory urgency. Post-deployment governance represents the binding constraint: documentation decays after launch, classification drift is missed when use cases expand, ownership dissolves when project teams disband, and vendor model updates often bypass reassessment workflows. Hawk/Chartis survey of 125 financial leaders (April 2026) found 70% report model performance degradation unaddressed. Documentation automation, despite NVIDIA MCG toolkit achieving 91% field completion and 76% accuracy, remains incomplete on foundational capabilities: Stanford 2026 AI Index documents Foundation Model Transparency Index collapse (58→40/100 year-over-year) with 80 of 95 foundation models released in 2025 lacking training code disclosure. Multi-sourced 2026 surveys reveal governance-adoption velocity mismatch: agent adoption projected to grow from 23% to 74% in two years but only 21% of organizations have mature governance; 96% report agent sprawl but only 12% implement centralized platforms. Independent platform reviews document steep learning curves, opaque pricing, and cross-platform integration friction (MLflow Model Registry limitations in Microsoft Fabric, API gaps around aliases and metrics). Model deprecation creates operational burden: six-month vendor transition windows demand prompt re-tuning, regression testing across distributions, downstream schema repair, and team coordination—driving enterprise need for model versioning and lifecycle management as architectural requirements.
— Industry analyst establishes that model cards, data lineage, and centralized AI catalogs are now regulatory baseline expectations with materialized compliance gaps for audit-unprepared organizations.
— Official Databricks production documentation of MLflow Model Registry in Unity Catalog with centralized access control, lineage, model discovery, and cross-workspace governance for model inventory management.
— Practitioner-authored deprecation protocol treating model IDs as versioned dependencies with regression gate and atomic PR-based migrations — operational pattern for managing distributed model lifecycle complexity.
— Official Azure Databricks ML lifecycle documentation with model registration, staging, testing, and promotion governance via MLflow Model Registry in Unity Catalog with versioned lineage.
— Salesforce published 19 model cards covering production AI/ML models across product portfolio (Data Cloud, Agentforce, Einstein Platform, Marketing Cloud) with versioned lifecycle tracking — evidence of at-scale enterprise adoption of model documentation as a governance artifact.
— IDC analyst report recognizing Databricks as Leader in unified AI governance; validates ecosystem maturity for integrated model inventory, governance, and lifecycle management at scale.
— MLflow 3 lifecycle management with LoggedModels capturing metrics/parameters across dev/staging/production with Unity Catalog governance and unified performance visibility across workspaces.
— PRA Supervisory Statement SS1/23 establishes model inventory, classification, and governance as enforceable expectations for material AI systems; unregistered AI use is a direct control gap per UK regulators.
2020: Major vendors (AWS, Databricks, SAS) released model registry and lifecycle management products, signaling early ecosystem maturity; open-source implementations showed technical maturity gaps with documented integration failures and UI limitations.
2021: Academic standardization efforts emerged (HuggingFace, GEM, Model Card Toolkit) indicating consensus on documentation templates; vendor tooling continued to mature with documentation updates. However, industry survey data revealed critical adoption barriers: financial services organizations with 270+ models in production rated inventory processes as only 25% effective. MLflow and open-source tools struggled with platform compatibility (Windows performance issues) and integration reliability, limiting adoption beyond cloud-native environments.
2022-H1: Vendor ecosystem consolidated with AWS, Microsoft, and Databricks all shipping production-grade model registry and lifecycle management features; Vanguard deployed SageMaker Model Registry at Fortune 500 scale with 100% automated deployment. However, adoption barriers intensified on the organizational side: HuggingFace documentation study showed only 40% of models have any documentation despite years of tooling availability; industry surveys found 85-90% of ML models never reach production, with lifecycle management delays and organizational bottlenecks cited as primary causes. Tooling had matured; adoption had not.
2022-H2: Vendor expansion accelerated with Azure ML Registries entering public preview and Google Vertex AI Model Registry growing to named production deployments (ZOZO). AWS reported tens of thousands of SageMaker customers managing millions of models and generating hundreds of billions of predictions. Documentation standards continued to advance (NVIDIA Model Card++). However, organizational adoption barriers persisted: talent shortages (29% of decision-makers cited lack of talent as key challenge) and organizational complexity remained the binding constraints, not tooling maturity.
2023-H1: AWS launched SageMaker Collections for hierarchical model organization; Microsoft and Google expanded model registry capabilities with tutorials and production case studies. However, documentation quality deteriorated: HuggingFace analysis found 80% of models lack sufficient docs (vs. 40% in 2022), 88% of model cards inflated performance claims, 96% omitted bias/limitations. Only 1 in 10 ML models operationalized; 64% of organizations require 1+ months for deployment. Research pivoted toward automated model card generation to address documentation labor bottleneck. Vendor feature expansion continued while organizational adoption stagnated.
2023-H2: Vendor ecosystem continued expanding with AWS SageMaker deployment approval workflows (November) and Databricks MLflow lifecycle examples. Research on automated model card generation (arXiv 2309.12616) advanced documentation automation with 500-example QA datasets, though findings revealed LMs struggling to understand documentation requirements. RMA survey showed two-thirds of 53 financial institutions using lifecycle management IT applications, signaling sustained adoption in regulated sectors despite tool complexity. However, Kubeflow user survey (July) found model registry remained a top gap (44%) across open-source platforms, and Azure ML integration issues surfaced real-world deployment complexities. Vendor tooling matured incrementally while organizational barriers—documentation quality, tool interoperability, and platform compatibility—persisted as binding constraints on broader adoption.
2024-Q1: Vendors continued operationalizing governance features: AWS SageMaker model registry automated approval and promotion workflows (with Merck pharma as production case study), and Azure Databricks launched wind farm forecasting examples for lifecycle management. Research community advanced automated model card generation with LLM-based approaches and large datasets (NAACL-HLT 2024, CardBench with 4.8k model cards). Open-source ecosystem expanded with Kubeflow Model Registry entering alpha. However, platform reliability remained a blocker: MLflow integration failures with Azure ML and model registration bugs surfaced in production deployments, indicating that despite vendor maturity, organizations still face real-world obstacles to seamless inventory management. Documentation incompleteness persisted as a structural challenge requiring automation.
2024-Q2: New vendor expansion accelerated: Snowflake announced GA of its Model Registry (May), and Valohai released centralized registry features for its MLOps platform. Research on automated model card generation published in NAACL 2024 (CardGen paper) demonstrated LLM-based generation of model and data cards from cardBench dataset of 4.8k examples, addressing documentation labor bottleneck. Regulatory perspectives strengthened: OSFI (Canadian financial regulator) research paper advocated adoption of model ownership, documentation, and challenge principles from financial model risk management to AI systems. However, integration maturity gaps persisted: MLflow registry integration failures in Ultralytics YOLO and Vertex AI SDK deployment issues for BigQuery ML models revealed ongoing real-world adoption barriers despite vendor tooling expansion.
2024-Q3: Vendor feature consolidation accelerated: AWS advanced SageMaker Model Registry with automated approval workflows incorporating governance checks (quality, bias, feature importance) for multi-account organizations; Azure ML confirmed GA MLflow integration for workspace-level lifecycle management; Valohai released Model Hub with versioning, lineage, and automated approval. Critical ecosystem shift emerged: Databricks deprecated its workspace model registry in favor of Unity Catalog, signaling major platform reorganization toward centralized cross-workspace governance. However, real-world deployment barriers persisted: practitioner analysis documented fundamental misalignment between idealized lifecycle models and organizational chaos in implementation, with hidden dependencies and provisioning failures in Azure ML ecosystem undermining platform reliability. Documentation automation research advanced but organizational adoption gaps remained structural.
2024-Q4: Platform consolidation continued: AWS released GA of cross-account model sharing via SageMaker Model Registry with AWS Resource Access Manager (November), enabling enterprise governance at scale. SAS and open-source projects (model-card-generator) advanced automated model card generation to reduce documentation labor. Databricks workspace model registry formally moved to legacy status with migration to Unity Catalog, completing the platform reorganization toward centralized governance. However, ecosystem voices remained critical: vendors acknowledged documentation complexity (SAS plea for simpler cards) and real-world deployment barriers persisted despite expanded feature sets. Tooling reached clear maturity—cross-account governance, automated documentation, deep audit trails—but organizational adoption and documentation quality remained below leading-edge expectations, with talent, process complexity, and interoperability gaps persisting as binding constraints.
2025-Q1: Vendor tooling maturation continued: AWS unified SageMaker Model Cards directly with Model Registry to streamline governance workflows; empirical research showed MLflow adoption driving significant improvements in development cycle times, reproducibility, and deployment efficiency across organizations. Sectoral adoption accelerated in healthcare with Coalition for Health AI (CHAI) launching a model card registry with Providence, Cleveland Clinic, and Kaiser Permanente participation, standardizing documentation for healthcare AI procurement. However, real-world deployment barriers persisted acutely: Kubeflow Model Registry UI defects and Azure Databricks/MLflow authorization failures in production deployments revealed ongoing integration maturity gaps; critical assessments documented persistent governance and lifecycle management deficiencies in custom AI solutions despite vendor tooling maturity. Open-source and commercial ecosystems continued divergence: while Tier 1 vendors achieved technical maturity and sectoral adoption signals, organizational barriers—integration failures, documentation quality, and production reliability gaps—remained binding constraints on broader industry adoption.
2025-Q2: Documentation crisis intensified alongside continued vendor tooling maturity. IEEE Requirements Engineering Conference research (June 2025) analyzed 26 ethics guidelines and 10 model cards, finding developers overwhelmingly emphasize capabilities and reliability while systematically overlooking fairness, explainability, and user autonomy—negative signal on model card comprehensiveness despite vendor automation efforts. Major vendor transparency failure emerged: Google released Gemini 2.5 Pro (March 2025) without safety report or model card, violating public commitments to US government and international AI safety summits; similar gaps reported at OpenAI and Meta. Vendor tooling continued maturity trajectory but deployment-first practices demonstrated that regulatory and transparency commitments remained subordinate to rapid release cycles. The practice remained technically advanced but organizationally fractured: Tier 1 vendors provided mature, feature-rich registries and governance automation; yet deployment practices and documentation completeness continued deteriorating as model volume and urgency accelerated.
2025-Q3: Vendor tooling expanded unified lifecycle capabilities while organizational adoption barriers persisted. AWS SageMaker HyperPod launched model deployment (July 2025) enabling unified training-to-inference on same infrastructure with named customers (Perplexity, Hippocratic, Salesforce, Articul8) demonstrating real-world adoption across foundation model development. Microsoft formalized lifecycle retirement governance in Azure AI Foundry (September 2025) with explicit phases and concrete timelines for model deprecation and replacement. Regulatory compliance requirements emerged: EU AI Act mapping accelerated with consultancies (2B Advice September 2025) explicitly linking model cards to compliance, identifying governance elements (approvals, validity periods, re-audit intervals) needed for regulatory alignment. However, open-source tooling quality regressed: MLflow 3.0 introduced UI regressions (Source run link disappearance in Model Registry, July 2025) signaling quality control gaps despite continued development. Documentation incompleteness and organizational implementation barriers remained binding constraints despite leading-edge vendor feature maturity. The practice embodied persistent technical maturity alongside organizational stagnation: sophisticated registries coexisting with systematic documentation gaps, transparency failures, and deployment velocity outpacing governance infrastructure.
2025-Q4: Vendor ecosystem consolidated continued investment in model lifecycle tooling while documentation quality research revealed persistent comprehensiveness gaps. Microsoft Azure AI Foundry and Azure ML continued MLflow integration (November 2025), confirming platform commitment to lifecycle management though with explicit limitations documented (no model renaming, no organizational registries, no cross-workspace operations). Academic research emerged with mixed signals: Patra Model Card framework (November 2025) advanced documentation beyond static reports with dynamic, runtime-aware systems for edge AI environments, yet peer-reviewed analysis of 90 model cards (WEBIST 2025) found pervasive structural variance, missing ethical reporting, and inconsistent transparency—documenting that documentation practice quality remained far below vendor tooling capability. Industry analysis (December 2025) reported 87% of data science projects never reach production with poor data lifecycle management as primary culprit, underscoring that organizational adoption barriers and lifecycle practices themselves—not vendor tooling—remained the binding constraint. By year-end 2025, the practice had reached a plateau: registries achieved leading-edge technical maturity with formalized retirement governance and expanded cloud platform integration, yet documentation completeness, organizational implementation effectiveness, and deployment velocity management remained unresolved structural challenges limiting broader adoption despite years of vendor investment.
2026-Jan: Vendor tooling advancement continued with AWS S3-based SageMaker AI Project templates (January 2026) enabling version-controlled, decentralized project management, and research reframed model cards using system safety methodologies at ICSE 2026. Empirical MLOps tool evaluation (arxiv January 2026) independently assessed Metaflow, Airflow, and Kubeflow alongside MLflow, measuring installation complexity and ML scenario implementation barriers. Critical research emerged: ADAS framework (January 2026) explicitly critiqued model cards as providing only descriptive information without binding deployment decisions, calling for machine-readable authorization standards. Real-world Cisco deployment showcased SageMaker Model Registry efficiency gains with programmatic lifecycle management. Market adoption signals remained positive: Grand View Research projected MLOps market at $16.6B by 2030 (+40.5% CAGR), with MLflow 3.x governance evolution and enterprise adoption of comprehensive lifecycle practices. However, the structural tensions identified in 2025 intensified: tooling maturity continued advancing at vendor level, yet the documentation crisis and organizational adoption barriers remained unresolved despite three years of research, automation attempts, and regulatory pressure. Model inventory registration tooling had become a commodity feature across Tier 1 vendors—the binding constraint shifted toward integrated governance, documentation completeness, and organizational implementation effectiveness.
2026-Feb: AWS released continued enhancements to SageMaker in 2025 review post, emphasizing improved observability with granular metrics and serverless MLflow integration (February 2026). MLflow maintained ecosystem prominence with 30 million monthly downloads across 1000+ organizations. However, critical adoption barriers persisted: independent platform review (TrueFoundry February 2026) documented opaque pricing, steep learning curves, and vendor lock-in penalties for multi-cloud strategies in SageMaker ecosystem. Platform integration challenges emerged: Microsoft Fabric integration of MLflow Model Registry revealed API limitations (alias support, metrics accessibility), indicating maturity gaps in cross-platform lifecycle management. By February 2026, the practice maintained leading-edge technical capability in vendor tooling but faced unresolved organizational adoption barriers, platform integration friction, and pricing/complexity burdens limiting deployment velocity among practitioners.
2026-Mar: Regulatory drivers intensified with OCC examinations explicitly requiring model inventory compliance under SR 11-7, extending financial model risk management to AI systems. Examinations revealed most US banks have only partial governance coverage: 43% cannot update live models, 38% struggle sustaining governance across growing inventories, and self-learning models/agent orchestration layers often missing entirely. Post-deployment governance emerged as a critical lifecycle gap: documentation decay, classification drift misses, ownership dissolution when teams disband, and vendor model updates bypassing reassessment workflows. ServerWorks deployed production model lifecycle management on SageMaker MLflow, demonstrating end-to-end operationalization. Model lineage formalized as a foundational EU AI Act compliance requirement, with datasets, code, hyperparameters, training conditions, and deployment targets forming an auditable provenance chain.
2026-Apr: Regulatory drivers reached critical mass with revised federal Model Risk Management guidance (April 17, Federal Reserve/FDIC/OCC) replacing 2011 guidance, establishing principles-based governance requiring model inventory, validation, monitoring, and vendor management across all US banks. AWS unified ML Governance suite matured with Model Cards autopopulation, DataZone integration, and integrated Model Dashboard monitoring. Databricks MLflow on Databricks formalized lifecycle management with Unity Catalog integration and approval-gated deployment jobs. Uber published production case study of Model Catalog (centralized inventory with auto-populated Model Cards and feature attribution integrated into Michelangelo ML platform), demonstrating enterprise-scale operationalization. Stanford 2026 AI Index documented critical transparency gap: Foundation Model Transparency Index dropped 58→40/100 year-over-year, with 80 of 95 2025 model releases lacking training code disclosure. Multi-sourced 2026 surveys revealed governance-adoption paradox: 23% companies moderately using agents projected to reach 74% in two years, but only 21% have mature governance models; 96% of organizations using agents report sprawl, yet only 12% implement centralized control platforms. Hawk/Chartis survey of 125 financial leaders found 70% report model performance degradation unaddressed, with shadow AI (business-unit tools, vendor-embedded models, PoCs) as primary inventory gap in regulatory examinations. By April 2026, vendor tooling maturity is unambiguous and multi-sourced (AWS, Databricks, Microsoft, Uber), but organizational adoption barriers remain acute: documentation comprehensiveness declining despite governance framework adoption, post-deployment lifecycle gaps (ownership dissolution, classification drift), and governance-velocity mismatch driving shadow AI proliferation.
2026-May: Vendor ecosystem continued formalizing model lifecycle and retirement governance with explicit, machine-readable policies. Databricks published comprehensive Foundation Model API maintenance policy with three retirement tracks (3-6 month transitions), automated model card notifications, and partner model fallback procedures. UiPath formalized LLM model deprecation timeline tracking across all products with four-stage lifecycle definitions (Announced→Migration open→Action required→Deprecated) and automated fallback for bring-your-own deployments. Anthropic and Databricks expanded cross-platform model inventory documentation on Vertex AI and Azure with platform-specific lifecycle status tracking and explicit retirement dates differing from managed API schedules. MLflow 3.12.0 released (May 2026) with multimodal tracing, artifact attachments, and coding agent integration for enhanced lifecycle observability. However, critical vulnerabilities emerged: MLflow CVE-2026-2651 exposed artifact authorization gaps enabling unauthorized cross-user writes and model supply chain poisoning—highlighting that security and integrity verification remain unresolved governance gaps even in mature registry tooling. Horizon Scan research confirmed governance maturity gaps in regulated industries persist despite vendor tooling maturity, with deployment velocity outpacing accountability infrastructure for agents and autonomous systems. By May 2026, vendor governance frameworks have achieved operational maturity—explicit retirement policies, cross-platform inventory tracking, automated governance workflows—but institutional adoption, lifecycle security, and implementation barriers remain unresolved.
2026-Jun: Regulatory deadlines crystallized model documentation as an enforced compliance requirement: EU AI Act (effective August 2, 2026) mandated technical documentation and centralized AI catalogs as audit baseline, with UK FCA/PRA SS1/23 treating unregistered AI as a direct control gap and US OCC/Federal Reserve guidance requiring model inventory for all banks. Vendor tooling continued maturing with Databricks MLflow on Unity Catalog, Azure Databricks MLflow 3 LoggedModels, and Salesforce publishing 19 production model cards across Agentforce, Data Cloud, and Einstein—demonstrating at-scale enterprise adoption of documentation as a governance artifact. NVIDIA MCG toolkit achieved 91% field completion and 76% accuracy on automated model card generation in under one minute, addressing the documentation labor bottleneck; IDC named Databricks a Leader in unified AI governance platforms. Operational deprecation burden intensified as a recognized lifecycle cost: practitioners documented six-month vendor transition windows demanding prompt re-tuning, regression testing, schema repair, and team coordination, with "model-ID-as-dependency" protocols emerging as an operational pattern for managing distributed model lifecycle complexity.