ARC-2: Continuous Compliance Through Delta Management

Tord Johan Eide, Einar HoltarXiv 2026 · arXiv

TL;DR

ARC-2 introduces Delta Management, a framework that shifts autonomous system governance from static, deployment-time certification to continuous, real-time monitoring. By measuring the "distance" between a robot's current state and its certified baseline across four dimensions, it provides a structured protocol for handling model drift, environmental shifts, and safety failures throughout a system's entire lifecycle.

What Problem Does This Paper Address?

The traditional approach to safety—validating a system in a lab and then "releasing it into the wild"—is fundamentally broken for autonomous systems. As the authors note, a warehouse robot or a healthcare assistant operates in a world that is constantly changing. Models drift, edge cases accumulate, and the environment the robot was tested in may no longer exist six months later.

The original ARC (Autonomous Robotics Compliance) framework established what needs to be checked (model safety, cognitive capabilities, and operational scope). However, it left a gap: it didn't define how to maintain that compliance once the "on" switch is flipped. ARC-2 tackles the "continuous compliance" requirement mandated by emerging regulations like Article 72(2) of the EU AI Act, providing an operational blueprint for monitoring systems that are never truly "finished."

Methods

The core of the paper is the Delta Management Principle. Instead of viewing certification as a binary pass/fail point, the authors define it as a certified region ($B$). Compliance is then treated as a measurable distance ($\Delta$) between the current system state ($S(t)$) and that region.

The framework introduces four key extensions to the ARC architecture:

  1. Four Dimensions of Delta: Monitoring isn't just about one metric. It tracks Model delta (behavioral fingerprints), Cognitive delta (benchmarked capabilities), Operational delta (task performance), and Environmental delta (changes in the world).
  2. The Outlier Floor Principle: Safety is anchored to the worst verified behavior rather than average performance. To prevent sensor noise from permanently "breaking" a robot's authority, they introduce a quarantine mechanism where outliers must be confirmed before they trigger a governance response.
  3. Layered Trigger Taxonomy: Rather than a simple "kill switch," the paper proposes a four-layer hierarchy:
  4. Layer 1 (Hard Invariants): Immediate safety breaches (e.g., collisions).
  5. Layer 2 (Critical Overrides): Catastrophic failure in a single dimension.
  6. Layer 3 (Spiral Detection): Correlated degradation across multiple subsystems.
  7. Layer 4 (Composite Scores): Gradual drift triggering low-cost responses like increased oversight.
  8. Graduated Safe Transition Protocol: A six-step process that separates "withdrawing authority" from "physical stopping." This ensures that a robot doesn't cause more harm by stopping abruptly in a dangerous position (e.g., mid-patient transfer).

Datasets

Not discussed in the paper. The authors explicitly state that ARC-2 is a "governance architecture proposal, not an empirically validated system." They invite the research community to contribute deployment telemetry and threshold data to help calibrate the framework.

Key Insights and Ideas

  • Compliance as a Vector, Not a Scalar: You cannot reduce the safety of a complex robot to a single number. Delta management treats compliance as a "structured inference problem" operating over a vector of observable proxies.
  • The Environment is a Validity Condition: This is perhaps the most novel insight. If the environment drifts too far from the original Operational Design Domain (ODD), the system hasn't necessarily "failed," but the baseline itself has become invalid. In this case, the correct response is recertification, not just restricting the robot's power.
  • Asymmetric Governance: The authors argue for an intentional bias: it should be easy (and often automatic) to contract a robot's authority when drift is detected, but expanding that authority should always require human-confirmed review.
  • The "Stop" Paradox: Withdrawing a robot's legal/governance authorization to act is a distinct action from cutting its power. In many safety-critical scenarios, an immediate "Category 0" stop is the least safe option.

Key Results

Not discussed in the paper. As a theoretical architecture paper, there are no quantitative performance results (like accuracy or speedup). The "result" is the formalization of the Delta Management equations and the trigger taxonomy.

Limitations and Future Work

The authors are refreshingly transparent about the gaps in this framework:

  • Absence of Empirical Validation: The framework has not yet been tested against real-world operational traces to determine false positive/negative rates for the triggers.
  • Underspecified Distance Metrics: While the paper defines $\Delta(t)$ as a distance-to-set function, it doesn't specify how to normalize heterogeneous data (e.g., how do you weigh a 5% drop in "situational awareness" against a 2% increase in "energy consumption"?).
  • Regulatory Role Mapping: The paper notes that the EU AI Act distinguishes between "providers" and "deployers," but ARC-2 doesn't yet fully map which party is responsible for which part of the delta monitoring stack.
  • Calibration: The thresholds for "spirals" and "overrides" require domain-specific empirical data that the authors currently lack.

In short, ARC-2 provides the "operating system" for continuous AI governance, but it's now up to the robotics community to provide the "drivers" and "data" to make it run.

Summary updated

Abstract

ARC 1 introduced a three-layer governance architecture for autonomous systems comprising model safety validation, cognitive certification (CRAB), and operational authorization (LEA). However, it did not address how compliance should be maintained after deployment. This paper introduces Delta Management, a continuous governance framework that measures deviations between a system's current operational state and its certified baseline, defined as a region rather than a fixed point. Compliance is assessed through continuous monitoring instead of static certification. Four extensions are proposed. First, CRAB evaluation incorporates the worst verified behavioral deviations, with isolated outliers quarantined pending confirmation to prevent unjustified restrictions. Second, a layered trigger taxonomy distinguishes hard safety violations, critical single-dimension failures, correlated multi-system degradation, and risk-weighted composite indicators, each triggering proportionate responses. Third, a graduated safe transition protocol separates withdrawal of operational authorization from physical shutdown, consistent with established safety standards and EU AI Act requirements. Fourth, environmental delta is introduced as a distinct baseline validity condition: environmental drift beyond the certified Operational Design Domain (ODD) triggers recertification or ODD revision rather than automatic authority contraction. Together, these extensions transform ARC from a deployment-time certification architecture into a continuous framework for monitoring, evaluating, and enforcing compliance throughout the operational lifecycle of autonomous systems. The framework addresses the continuous compliance obligations established by EU AI Act Article 72(2).
BibTeX
@misc{eide2026arc,
  author = {Tord Johan Eide and Einar Holt},
  title = {{ARC-2: Continuous Compliance Through Delta Management}},
  year = {2026},
  eprint = {2611.21811},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/2611.21811},
}
Figure