arXiv (All)
open access
Reusing Assurance Evidence in AI Pipelines: Validity Conditions, a Fail-Closed Release Gate, and a Replay of 714 Public Data Version Control Pipelines
Rerunning every governance control after every change to an artificial intelligence (AI) pipeline is expensive, so teams reuse earlier results. Reuse is safe only if each control's declared dependencies cover everything that can change its outcome, and only if the release gate checks that reused evi
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- From diagnosis to repair: A model-driven framework for root cause analysis of machine learning pipelines#299189
- OVIG: Optimistic Verification of AI Training Integrity via Gradient Signals#1131584
- How to safely RELEASE-AI models: a lifecycle framework for Trusted Research Environments.#423072
- AI Governance Before Intelligence A Pre-Execution Substrate for Deterministic Refusal, Authority Validation, and Continuity Preservation Version 0.9.6#26427
- Clean Data Can Still Carry Backdoors: Support-Persistent Backdoors for Model Reuse#1356544
Record · ID 1403468
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive