Cross-Domain Scope

Purpose

This note describes how the same record lifecycle gap appears across multiple infrastructure domains. In each case, a governance function is addressed while the lifecycle of the records those systems create remains undefined. ARCS applies at the record lifecycle layer beneath all of these systems.

The structural condition

Governance for agent behavior is advancing more quickly than governance for the records those systems create. Runtime systems govern connection, permissions, orchestration, and execution. ARCS governs a different layer: the lifecycle of the records those workflows produce. It addresses persistence, movement, custody, and later review or production.

Compute sovereignty

Inference runs on infrastructure controlled by the operator. Vendor-side retention is removed by removing the vendor from the inference path. The lifecycle of records created by the operator's own application is not defined.

Contractual non-retention

The vendor commits to not retaining interaction content. The vendor's retention surface is addressed. The operator's independent retention surface is not governed.

Privacy and encryption

Data is protected from unauthorized access in transit and at rest. Access to records is governed. Whether records exist, how long they persist, or what follows when authorized legal process compels production is not determined.

Interoperability protocols

Agents connect to tools and services through standardized protocols. Connection and execution semantics are governed. The lifecycle of the records those connections generate is not defined.

Runtime governance controls

Agent interactions are validated, transformed, and logged to enforce compliance policies. Real-time enforcement is governed. The records created by those controls during ordinary operation have independent lifecycle, custody, and production consequences.

Payment protocols

Agents pay for data, compute, and services. Value exchange is governed. The records generated by those payments, including settlement records, authorization traces, and received-data records, are not governed by payment protocol specifications at the lifecycle layer.

Practical reading

In each case, the governance function is real, the resulting records exist, and lifecycle governance is absent. ARCS applies at the record-lifecycle layer beneath these systems and governs the records they create, retain, or fail to destroy.