arXiv (All)
open access
Audit-First Rollback Semantics for Safety-Critical Deployment Pipelines
Distributed deployment runtimes carry a coherence obligation that classical fault-tolerance frameworks do not name directly: the live state a component is configured to run and the audit chain that records how it got there must agree at every terminal configuration. Prior works mainly focus on indiv
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
- Audit-First Rollback Semantics for Safety-Critical Deployment Pipelines#809858
- Uncovering Logit Suppression Vulnerabilities in LLM Safety Alignment#152988
- Pirateship: Append-Only Ledgers for (Mostly) Trusted Execution Environments#1084127
- Bounded Loops: Pre-Run Spend Bounds, Proved Termination, and Verified Completion for Agent Harnesses#1064415
- Making Deployments Safe at Meta: Health Checks for Continuous Change-Safety#659079
Record · ID 819854
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