4arXiv cs.AI (Artificial Intelligence)·
Industry study at Daimler Truck reveals gaps in Requirements Engineering practices for AI explainability
A qualitative study with eight practitioners at Daimler Truck investigates how existing Requirements Engineering (RE) techniques handle explainability requirements across elicitation, specification, and validation phases. The study finds recurring challenges including conceptual ambiguity, limited testability, and fragmented validation due to vague criteria and regulatory uncertainty. The authors propose a research vision toward an empirically grounded RE framework for explainable AI systems in safety-critical industrial contexts.
Related guides (2)
Related events (8)
Anthropic details red teaming methods and calls for standardized AI testing practices
Anthropic published a detailed overview of red teaming approaches used to test Claude and other AI systems, covering domain-specific expert testing, automated red teaming, multilingual/multicultural testing, and multimodal red teaming. The post documents empirical findings about when each method is appropriate, highlights partnerships with organizations like Thorn, Institute for Strategic Dialogue, and Singapore's IMDA, and closes with policy recommendations for building a standardized AI testing ecosystem. The piece is notable for its operational specificity and its explicit call for industry-wide standards to enable cross-system safety comparisons.
Improving Verifiability in AI Development: Multi-Stakeholder Report
OpenAI contributed to a multi-stakeholder report co-authored by 58 researchers across 30 organizations, including Mila, CSET, and the Schwartz Reisman Institute. The report identifies 10 mechanisms for improving the verifiability of claims about AI systems. These tools are intended to help developers demonstrate safety, security, fairness, and privacy properties, while enabling policymakers and civil society to evaluate AI development processes.
Benchmark gap paper: EU AI Act requires doctrinal legal reasoning evals that don't yet exist
A new arXiv preprint identifies a critical measurement gap in legal AI evaluation: existing benchmarks test paralegal and ancillary tasks rather than doctrinal legal reasoning, which is the interpretive core of legal work. The authors argue this gap is not merely methodological but legally significant, because the EU AI Act's 'appropriate accuracy' requirement for high-risk AI in the judicial domain cannot be operationalized without a doctrinal-reasoning benchmark. The paper proposes a benchmark framework aimed at filling this gap under EU AI Act compliance requirements.
Retrospective analysis of multimodal VQA systems for clinical GI endoscopy reveals evaluation gaps
A new arXiv paper analyzes nine documented systems from the MediaEval Medico 2025 challenge for GI endoscopy visual question answering, examining design choices around parameter-efficient adaptation, structured reasoning, and explanation quality. The authors find that leaderboard performance gains do not reliably translate to faithful clinical reasoning, while methods enforcing structured reasoning and explicit grounding show more consistent behavior. The paper argues for evaluation frameworks that go beyond lexical overlap, incorporating evidence-linked explanations, leakage-aware data governance, and calibration checks for trustworthy healthcare AI.
AIEWF Daily Dispatch: Autoresearch and the tension between AI and human agency
A conference dispatch from AI Engineer World's Fair 2026 covers debate between proponents of fully automated 'software factory' and 'autoresearch' visions versus speakers defending human understanding and control. The piece captures live tension at a major practitioner conference around how much autonomy AI systems should have in research and software development workflows. The framing surfaces a recurring fault line in the agent-tool ecosystem between automation maximalism and human-in-the-loop approaches.
Study finds AI disclosure designs in newsrooms fail readers, proposes user-agency-centered alternatives
A paper from arXiv examines how newsrooms disclose AI involvement in news content, finding that neither brief labels nor detailed disclosures achieve the goal of building reader trust. A controlled experiment with 34 readers shows detailed disclosures trigger a 'transparency dilemma' that can reduce trust, while one-line labels create an information gap requiring cognitive effort to fill. Readers instead preferred disclosure designs centered on user agency, including detail-on-demand interactions, proportional AI-ratio visualizations, and explicit 'no AI' labels. The author frames this as a design problem for the HCI community rather than a journalism ethics problem alone.
Reversa: A Multi-Agent Framework for Reverse Engineering Legacy Software into AI-Readable Operational Specifications
Reversa is a multi-agent pipeline framework that converts legacy software systems into traceable operational specifications suitable for use by AI coding agents. The framework employs specialized agents for surface mapping, module analysis, implicit rule extraction, architecture synthesis, and specification review, with mechanisms for traceability, confidence marking, and gap preservation. An exploratory case study on migrating an ATM system from COBOL to Go produced 517 confidence-indexed claims, 53 Gherkin parity scenarios, and a partial reconstruction plan, though final validation was not completed. The system is distributed as a Node.js CLI and is positioned relative to literature on reverse engineering, LLM-based documentation, and software agents.
Data Readiness for Agentic AI in Financial Services
This MIT Technology Review commentary examines the specific requirements for deploying agentic AI in financial services, arguing that success depends more on data readiness than on model sophistication. The piece highlights the dual challenge of operating under heavy regulatory constraints while processing real-time market data. It frames data infrastructure as the critical bottleneck for agentic AI adoption in the sector.