Retention and Immutability
Retention and Immutability
Document verified data lifecycle and mutation rules.
Status: Partial implementation reference — Code-confirmed; operational validation pending
Last reviewed: 2026-10-19
Scope
Retention, deletion, mutation controls, exceptions and evidence for any immutability claims. The source-confirmed baseline below covers part of this scope; remaining operational details are unknown.
Current implementation baseline
Normal Corpus APIs append messages and attributed relationship assertions/retractions. Retraction withdraws an assertion; it does not erase original message bytes. SQL immutability triggers protect ordinary mutation paths, not arbitrary privileged administration.
Public archive objects/manifests require retention without mutation or expiry for replay. This is an operator obligation; repository code does not attest live bucket lifecycle or backup lock settings. Restoration or incompatible history replacement requires fresh lineage and fenced traffic.
Evidence: schema triggers, lineage runbook and the retained moderation/redaction design issue. No implemented moderation contract or universal retention duration is established here.
