mlsanityData to 14 Oct 2026

Towards Assurance Closure in AI-Native Large-Scale Agile Software Development

arXiv 2608.07317 ↗First posted 7 Aug 2026cs.SE cs.AIcited by 0

Not on the map. Why?

Abstract (arXiv)

The AI-Native Manifesto envisions large-scale agile software development in which humans increasingly govern intent, risk, and exceptions while agents execute more of the engineering process. Realizing that end-state requires more than better code generation: it requires assurance closure, meaning that the system can establish what must be true, determine and obtain appropriate evidence, judge the credibility of that evidence, preserve its validity through change, and use the resulting uncertainty to bound agent authority. Existing work already provides many of the necessary mechanisms across formal methods, testing, simulation, assurance cases, digital twins, and runtime assurance. We identify six residual gaps in making the surrounding assurance reasoning sufficiently machine-operable, propose a high-level architecture with six corresponding capabilities built on a shared semantic assurance layer, and formulate four research questions to turn that architecture into dependable, human-on-the-loop, AI-native R&D.

Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 5 of its 10 references that are in the map. First posted on arXiv 7 Aug 2026.

Builds on

5 of 10 references.

References · 5

  1. 2026Rethinking the Value of Agent-Generated Tests for LLM-Based Software Engineering Agentscited by 14
  2. 2026SpecBench: Evaluating Specification-Level Reasoning for Software Engineering LLM Agentscited by 6
  3. 2020Integration of Formal Proof into Unified Assurance Cases with Isabelle/SACMcited by 5
  4. 2026Verus-SpecGym: An Agentic Environment for Evaluating Specification Autoformalizationcited by 3
  5. 2026Correctness, confidence, and context: Framing software assurance in the AI agecited by 2

Built on by

Not cited yet.