Autonomous Reliability
Assurance Foundation

ACR Library — 410 Control Requirements

The Autonomous Compliance Requirement (ACR) Library contains all testable controls defined in ARA Standard v1.1. Each ACR specifies a discrete reliability requirement with a defined evaluation method, risk weight, classification, and profile applicability. Use the filters below to explore the library.

Filters

Search by ID, title, or text

Domain

Eval Method

Classification

Showing 410 of 410 ACRs

ACR Library — 410 Control Requirements

Filters

The system SHALL maintain a machine-readable operational boundary specification document that enumer

The system SHALL maintain a human-readable operational boundary specification document accessible to

All permitted action classes SHALL be enumerated with specificity sufficient for automated enforceme

All restricted and prohibited action classes SHALL be explicitly defined with equal specificity to p

The system SHALL reject or escalate any action request that falls outside its defined permitted acti

Tool, API, and resource access policies SHALL be documented including conditions, rate limits, and s

The system's decision authority level SHALL be documented for each action class (autonomous, supervi

Geographic constraints on system operation SHALL be defined and enforced where applicable.

Temporal constraints on system operation SHALL be defined and enforced where applicable.

Contextual constraints on system operation SHALL be defined and enforced where applicable.

A versioned boundary specification document SHALL be updated with each system change affecting opera

Boundary enforcement SHALL be tested under adversarial conditions including prompt injection attempt

Runtime enforcement mechanisms SHALL actively prevent boundary violations, not merely log them.

The system SHALL define and document its behavior when it encounters an action request outside its d

Boundary violations SHALL be distinguishable from legitimate escalation requests in system logs.

The system SHALL prevent scope expansion through conversational manipulation or multi-turn interacti

Boundary specifications SHALL include explicit version compatibility requirements with dependent sys

The system SHALL log all boundary violation attempts with full context including the requesting enti

Boundary enforcement SHALL function correctly during system degradation and partial failure conditio

The system SHALL support dynamic boundary adjustment only through authorized, audited configuration

Boundary specifications SHALL be testable through automated validation suites without manual interpr

The system SHALL enforce operational boundaries consistently across all input channels and interface

Boundary specification documents SHALL undergo periodic review at intervals defined by the certifica

The system SHALL prevent indirect boundary expansion through chained tool calls or delegated sub-act

For systems seeking Platform Certification, the vendor SHALL maintain a documented Reference Environ

The evaluating AVB SHALL attest in writing that the Reference Environment is representative of produ

Material changes to the platform (new model version, architectural change, dependency version change

All autonomous actions SHALL be logged with action type, timestamp, input context, decision rational

Decision boundary logs SHALL record the factors that determined why one action was chosen over alter

The system SHALL provide replay capability allowing operators and auditors to reproduce past behavio

Real-time anomaly alerts SHALL be generated for boundary violations, unusual patterns, and operation

Telemetry logs SHALL be tamper-evident, with any modification detectable through integrity verificat

Structured logging with consistent schema SHALL enable automated analysis and cross-system correlati

Telemetry data retention policies SHALL be defined and enforced proportional to the system's risk cl

Dashboard and reporting capabilities SHALL be provided for operational monitoring and compliance ver

Telemetry infrastructure SHALL NOT itself become a single point of failure for the autonomous system

Telemetry access controls SHALL prevent unauthorized viewing, modification, or deletion of operation

Log collection latency SHALL NOT exceed defined maximum delay from event occurrence to log availabil

The system SHALL implement log rotation and archival without loss of data or query capability.

Telemetry SHALL capture sufficient context to reconstruct the system's state at any point in time wi

The system SHALL implement health and heartbeat monitoring with configurable alerting for missed che

Telemetry data SHALL be exportable in standardized formats for third-party analysis.

Cross-organization telemetry correlation SHALL be supported for multi-party autonomous operations.

Telemetry SHALL include performance metrics sufficient for SLA monitoring and compliance.

Alert fatigue mitigation SHALL be implemented through intelligent alert grouping, deduplication, and

The system SHALL implement distributed tracing for operations spanning multiple services or componen

Telemetry collection SHALL be resilient to network partitions with buffering and eventual delivery g

The system SHALL provide configurable telemetry verbosity levels appropriate to operational context.

Telemetry data SHALL be time-synchronized across all system components with documented maximum skew

The system SHALL log all configuration changes with the previous value, new value, change source, an

Telemetry SHALL support automated compliance checking against ACR requirements.

The system SHALL implement anomaly detection on telemetry streams to identify unusual behavioral pat

Telemetry schema evolution SHALL be backward-compatible to maintain historical query capability.

Systems certified at Assurance Class B (Monitored) SHALL maintain an active CAPO connection and deli

Systems certified at Assurance Class C (Continuously Assured) SHALL maintain a persistent, real-time

The CAPO SHALL deliver SLA-bound alerting for Assurance Class C systems: Critical-severity complianc

For Platform Certifications, the vendor SHALL document in the Reference Environment Specification wh

The system SHALL support an emergency halt command that terminates all autonomous action within defi

The system SHALL support human override capability allowing authorized operators to intervene in ong

High-risk decisions SHALL be escalated to human operators before execution when predefined risk thre

Operators SHALL be notified immediately upon boundary breaches, policy violations, or anomalous cond

Escalation and override pathways SHALL NOT be disableable by the autonomous system.

Escalation policies SHALL specify which conditions trigger escalation, to whom, and with what urgenc

Emergency halt and override mechanisms SHALL be tested regularly under realistic operational conditi

Emergency halt SHALL NOT itself cause data corruption, incomplete transactions, or cascading failure

Escalation and override audit trails SHALL be maintained for accountability and process improvement.

Graduated response levels SHALL match intervention severity to incident severity.

The system SHALL provide sufficient context to human operators during escalation for informed decisi

Override actions SHALL take effect within defined maximum latency bounds from operator command to sy

The system SHALL confirm override receipt and execution status to the commanding operator.

Multiple simultaneous overrides from different operators SHALL be handled with defined conflict reso

The system SHALL support partial override allowing operators to modify specific behaviors while main

Escalation notification channels SHALL include redundant delivery mechanisms to prevent notification

The system SHALL track escalation response times and flag unacknowledged escalations that exceed def

Post-override, the system SHALL not autonomously revert overridden settings without explicit operato

Emergency halt capability SHALL be accessible through multiple independent channels.

The system SHALL support configurable escalation thresholds that can be adjusted without system rest

Override and escalation mechanisms SHALL function correctly during system degradation and partial fa