Models as Governed Interfaces for AI-Native MBSE: Read-Side Adequacy and Write-Side Admissibility
Not on the map. Why?
Abstract (arXiv)
Machine-readable models such as SysML v2 are now programmatically accessible, and a growing body of work treats that access as the enabling condition for AI participation in systems engineering. Access is necessary, but not sufficient. The remaining work lies not in the modelling language but in the data architecture around it. An AI reader that queries a structurally complete model for a derivation still runs into absent derivation chains, untagged epistemic status, missing provenance, and evidence that the model cannot resolve. Faced with these gaps, it does not abstain; it fills them from training data, a source that is neither verifiable nor governed. To make the case on a model that is exemplary by current practice rather than deficient, we probe the public Apollo 11 SysML v2 reconstruction. We name the missing property epistemic adequacy and offer it as a candidate data-architecture pattern in two halves. Read-side adequacy lets derivation, status, and provenance answer a query rather than invite a guess; write-side admissibility gates an AI contribution before it enters the record. The property is broken down into five criteria. Four sit on the read side, evidenced by the case and convergent literature; the fifth sits on the participation side, advanced as a hypothesis this paper does not yet test. The architecture space runs from an inline metadata extension up to a substrate-native multi-model store, and over it, we propose the Governed-Query Architecture Framework, which governs agent participation through the viewpoint conventions that engineers already use. We commit the reframing to falsification: the epistemic layer counts as refuted if it cannot beat a retrieval-augmented baseline on the same model, tested first on the Apollo chain and then in an industrial pilot.
Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 10 of its 45 references that are in the map. First posted on arXiv 30 Jul 2026.
Builds on
10 of 45 references.
References · 10
- 2018Know What You Don't Know: Unanswerable Questions for SQuADcited by 1,554
- 2023Ragas: Automated Evaluation of Retrieval Augmented Generationcited by 418
- 2020Selective Question Answering under Domain Shiftcited by 238
- 2024Hallucination-Free? Assessing the Reliability of Leading AI Legal Research Toolscited by 176
- 2024On the use of Large Language Models in Model-Driven Engineeringcited by 13
- 2026Automotive Engineering-Centric Agentic AI Workflow Frameworkcited by 2
- 2026The Provenance Gap in Clinical AI: Evidence-Traceable Temporal Knowledge Graphs for Rare Disease Reasoningcited by 2
- 2025Survey: On the Landscape of Graph Databasescited by 1
- 2026Engineering Decisions in MBSE: Insights for a Decision Capture Framework Developmentcited by 1
- 2026AI as Consumer and Participant: A Co-Design Agenda for MBSE Substrates and Methodologycited by 1
Built on by
Not cited yet.
Similar, not cited
Close in wording, no citation either way
- 2026AI Space Physics: Constitutive boundary semantics for open AI institutions
- 2026VISA: A Structured Description Protocol for Agent-Based Simulation Models Towards Machine Reproducibility
- 2026Agent-Native Telemetry: Verifiable State-Delta Evidence for Autonomous Operations
- 2026Reasoning Provenance for Autonomous AI Agents: Structured Behavioral Analytics Beyond State Checkpoints and Execution Traces
- 2026Semantic Laundering in AI Agent Architectures: Why Tool Boundaries Do Not Confer Epistemic Warrant
- 2026Beyond the Binary: A nuanced path for open-weight advanced AI ↗
- 2026Harness as an Asset: Enforcing Determinism via the Convergent AI Agent Framework (CAAF)
- 2026AGL-1: The Enterprise AI Governance Layer as a Control Plane for Trusted Enterprise Intelligence