Section navigation

Paired Record Environments

Purpose

This note describes a class of systems that create paired record environments where one component is anchored by infrastructure-level guarantees and the paired component remains subject to operator retention decisions. ARCS governs the mutable, operator-governed components of these environments.

The structural condition

Some systems create records in which one component is permanent and tamper-resistant by infrastructure design, while the paired component depends on operator retention decisions for its continued existence. Blockchain settlement records, append-only consensus ledgers, and cryptographic attestation chains can produce permanent anchors. The explanatory records paired with those anchors, including what was purchased, why, under whose authority, and what followed, remain operator-governed and lifecycle-sensitive.

Scope

ARCS governs the mutable, operator-governed components of these environments. Infrastructure-guaranteed immutable anchors are outside the standard's retention and deletion governance. Mutable records paired with those anchors require defined retention, documented custody, preservation capability, and producibility assessment.

Evidentiary coherence

Where an immutable anchor remains available but the explanatory record layer drifts, degrades, or disappears, an evidentiary gap results. Proof that an event occurred remains available, while the records needed to explain or defend that event do not. ARCS addresses this by requiring disclosure of the retention posture of mutable components in paired record environments and assessment of the consequences of any gap between anchor permanence and explanatory-record retention.

Practical reading

The immutable anchor proves that something happened. The mutable records explain what happened and why. ARCS governs the second half of that pair.

This document is informative. It is not part of the normative ARCS standard.