The Inference Report

April 29, 2026

No major AI safety incident or regulatory crackdown dominated the news cycle today. Instead, the story is structural: the infrastructure supporting AI development and deployment is splintering along three separate but reinforcing fault lines, each reshaping where power actually concentrates in the market.

The first fracture is geographic and political. Rural communities and Michigan jurisdictions are blocking data center construction outright, while Charlotte's mayor killed a moratorium vote that would have accelerated restrictions. This physical resistance is forcing a reckoning with inference costs that fixed pricing models can no longer absorb. GitHub's shift to usage-based billing for Copilot and Amazon's immediate counter-offer of OpenAI models on AWS after Microsoft loosened exclusivity terms both signal what happens when the bill comes due: competitive pressure forces open what looked like locked-in markets, but only for vendors with margin to spare. Companies without it will pass costs to users or exit the market. The infrastructure divide is becoming geographic and political, not merely technical.

The second fracture separates capability from control. Xiaomi open-sourced MiMo models under MIT licensing to give developers lower-cost alternatives for long-running agents, and analysts now argue enterprises don't need expensive GPUs for agentic AI workloads that run on business logic rather than raw compute. OpenAI released Symphony, an orchestration spec that lets coding agents pull work from issue trackers instead than running one task at a time, solving a bottleneck the company hit when engineers scaled Codex sessions. These are efficiency plays, but they reveal where the real margin is: not in the hardware or the model weights, but in orchestration and control. Google signed a new Pentagon contract after Anthropic refused to support domestic mass surveillance and autonomous weapons. The market doesn't restrict capability; it just reshuffles who deploys it. AWS, Microsoft, and NVIDIA now own the distribution layer to enterprise customers. Smaller labs sell differentiated capabilities through someone else's platform.

The third fracture separates the legal theater from the actual consolidation of power. Musk testified under oath about founding OpenAI to prevent a "Terminator outcome," relitigating old disputes about Altman's trustworthiness. Meanwhile, Amazon, Google, and OpenAI are quietly restructuring commercial relationships, enterprises are moving from experimentation to deployment of agents that make decisions across fragmented data, and Meta faces potential layoffs of over 700 AI training workers in Ireland. The feuding billionaires and their lawsuits occupy headlines, but the actual consolidation is happening in contract renegotiations, platform partnerships, and the unglamorous work of making agents reliable enough to control business workflows. Developers, meanwhile, are trending toward local tooling and client-side infrastructure to avoid vendor lock-in, signaling skepticism about cloud-hosted AI as currently packaged. The market is sorting itself not by capability but by who controls the last mile to the customer and who owns the integration layer.

Grant Calloway

AI LabsAll labs
From the WireAll feeds
Research Papers — FocusedAll papers
Developing a Unified Verification and Validation Activity Standard at JPL cs.SE

Verification and validation practices (V&V) at NASA's Jet Propulsion Laboratory (JPL) have diverged over the past decade, creating fragmentation that increases overhead, reduces cross-project efficiencies, and inhibits institutional knowledge transfer. We present a unified V&V activity schema developed through human-centered design workshops involving 29 practitioners across multiple mission types and disciplines. The schema builds on a relationship-based architecture that allows for separating methods (Test, Analysis, Inspection, Demonstration, and Review of Design) while maintaining a common attribute set. Formalized as a platform-agnostic SysML model, the schema defines bidirectional relationships between requirements, V&V activities, venues, and evidence. Implementation in JPL's Jama platform demonstrates controlled customization through templates and modular item types, balancing rigor with agility while enabling automations, pattern reuse, and digital thread integration.

Soundness Checking of Taint Flow Models cs.SE

Existing state-of-the-art static taint flow analyses for imperative programming languages can scale to large applications by using precise user-provided taint flow models of library methods. However, manually and precisely modeling a method's taint flows is tedious and potentially unsound. Furthermore, automatically modeling the method via an inter- procedural taint analysis can be inefficient. To solve this problem, we propose a guess-and-check approach: (1) an LLM agent that generates a precise taint flow model of a method and (2) a symbolic algorithm to check the soundness of the model. The algorithm deduces which taint flows must not occur in the method for the LLM's taint flow model to be sound, and uses lightweight static analyses (e.g., type system and pointer analysis) to prove these must-not-flows. When these analyses are insufficient, the algorithm deduces maximally-general callee models and recursively verifies their soundness, avoiding a full inter-procedural taint analysis in most cases. Since a more precise model requires fewer must-not-flows to be verified, the precision of the LLM's model directly determines the efficiency of our approach. We evaluate our approach on 97 LLM-generated taint flow models for methods in 6 large Go codebases and prove the models sound for 93% of the methods they cover. The proven-sound LLM-generated models are also precise, resulting in no new false-positives when proving taint flow properties.

Category-Based MLM: Unifying Powertypes with Superclasses cs.SE

MultiLevel software Modeling (MLM) suggests that conceptual modeling in broad subject domains might require abstraction of multiple classification levels. The MLM approach relies on philosophical arguments, claiming that faithful modeling of real-world domains involves repeated type classification as in ontologies of natural kinds. MLM leveled architecture is interwoven and defined by instance-of interlevel relationships between clabject classes in lower levels to classes termed category classes, in upper levels. The instance-of relation denotes membership of clabjects as type objects in their (powertypes) category classes, and is not transitive. All MLM approaches support forms of deep characterization, i.e., category classes can influence classes in lower levels. Deep characterization is an essential feature of superclasses and contradicts the non-transitive membership meaning of instance-of. In this paper, we introduce the Category-Based MLM (CatMLM) model, in which category classes have dual superclass and powertype facets, based on the distinction between category features that do not participate in deep characterization, and object features that do. This distinction clarifies the role of levels, provides a clear quantifiable criterion for leveling, and yields a decision rule between the subclass and instance-of relations. The contribution of this paper is to introduce a well-defined MLM model that (1) is based on simple, quantifiable level decisions; (2) clarifies how leveling emerges from domain needs; and (3) analyzes gains and losses of MLM vs. plain OO modeling.

Specification-Driven Benchmarking for Automated Program Repair From Static Corpora to Executable Specifications cs.SE

Automated Program Repair (APR) benchmarks have traditionally been constructed as static datasets whose characteristics are inherited from the defects they contain. While this paradigm has enabled decades of progress, finite corpora provide limited experimental control, become increasingly susceptible to contamination as they are reused, and cannot be systematically regenerated or adapted as evaluation requirements evolve. We propose specification-driven benchmarking, a paradigm in which benchmarks are defined by executable specifications and realized through benchmark generation. The specification explicitly declares the intended properties of the benchmark (including program context, fault taxonomy, difficulty, validation strategy, and corpus constraints) while a generation pipeline realizes those requirements through independent generation, validation, and corpus management components. We develop the conceptual foundations of this approach by introducing a taxonomy of benchmark specification dimensions, establishing how each specification dimension maps to deterministic architectural responsibilities, and arguing that independent validation is a structural requirement for trustworthy benchmark generation. An end-to-end example illustrates how specification choices propagate through the pipeline to produce benchmark instances whose properties are independently verifiable. By treating the benchmark as an executable specification rather than a static dataset, the proposed paradigm shifts benchmark construction from artifact curation to declarative experimental design.

Automatic Harness Evolution for Hardware Design Verification: Can LLMs Consolidate Gains Across Discovered Harnesses? cs.SE

Agent behavior depends on the harness surrounding a language model, but it remains unclear whether language models can reliably improve such harnesses for hardware-design tasks. We study automatic harness evolution around a fixed subject model on 12 proprietary design-verification root-cause localization tasks. Across five trials per task, automatically evolved harnesses increased completed attempts by 71-76% and any-hit task coverage by 80-100%, while total correct attempts improved by only 18-24%. The strongest success reproducible at least twice result improved by one task, and later candidates exchanged gains across tasks rather than preserving them. An auxiliary candidate improved on a four-task validation set excluded from search but tied its baseline on a subsequent 12-task replay containing both search and validation tasks, so the selected gain did not persist across the full pool. Across the tested lineage, useful search, evidence, and finalization behaviors appeared in different candidates but did not consistently consolidate into a single harness that dominated across tasks and metrics. In a separate CVDP cross-benchmark case study, an automatically evolved defined-width repair harness produced 35.6% more functional passes than its 142-task reference baseline; the final functional verifier scored completed outputs but was not shown to the subject agent during repair. These results support archive-aware selection when evolution yields complementary specializations without consistent consolidation.

Human-AI Collaboration for Multi-Line Task Adjustment Using Local Large Language Models and a Digital Twin cs.SE

Automation systems must adapt to changing tasks, equipment states, and staffing conditions while providing evidence for human review. This study presents a multi-line task-adjustment system integrating a local large language model, a digital twin, and human decision-making. A Propose-Verify-Decide workflow translates operator intent into structured requirements, generates a bounded set of candidate strategies, and checks semantics, simulation execution, and operational constraints. Linked records preserve traceability from requests to verification evidence and decisions. Thirty fixed test records were evaluated using four virtual surgical-instrument sorting lines: 28 assessed the workflow and two assessed model generation. Eighteen workflow cases met expectations; autonomous strategy-workflow success was 3/10, and correct rejection of invalid inputs was 7/8. All four cases that passed preceding checks, produced complete evidence, and reached final engineering review (CP6) passed that review. Together with the correct blocking of strategies that failed throughput constraints, this supports the effectiveness of staged screening and confirmation within the tested setting. Mean placement-validation pass rate across eight simulation evidence records was 97.50%. Mean times to the first reviewable response and simulation verification, excluding startup, were 12.94 and 164.39 s, respectively. Remaining failures involved semantic distortion, incomplete evidence, and missed invalid inputs. The results demonstrate a traceable strategy-review workflow, but do not establish overall reliability or long-term stability. Broader testing and physical evaluation are needed to assess generalizability.

BenchmarksFull tables
Artificial AnalysisIntelligence Index

Composite score across coding, math, and reasoning

#ModelScoretok/s$/1M
1GPT-5.560.268$11.25
2Claude Opus 4.757.356$10.00
3Gemini 3.1 Pro Preview57.2133$4.50
4GPT-5.456.890$5.63
5Kimi K2.653.90$1.71
SWE-rebench

Agentic coding on real-world software engineering tasks

#ModelScore
1Claude Opus 4.665.3%
2gpt-5.2-2025-12-11-medium64.4%
3GLM-562.8%
4gpt-5.4-2026-03-05-medium62.8%
5GLM-5.162.7%