docs(rfc): define retention, erasure, and lifecycle policies - #1447
Open
Ethan-Xingyue wants to merge 2 commits into
Open
docs(rfc): define retention, erasure, and lifecycle policies#1447Ethan-Xingyue wants to merge 2 commits into
Ethan-Xingyue wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue or RFC does this PR close?
Closes #1425.
Rationale for this change
Existing lifecycle mechanisms (Memory
forget(), Artifact head governance, protected Source observations) stop short of retention and erasure. Several stores grow without any policy, and every schema reference isRESTRICT, so deleting referenced rows would break lineage and exact citations. RFC 1447 defines retention, archival, purge, and erasure without rewriting immutable history.What changes are included in this PR?
Documentation only, no code or schema changes.
docs/en/rfcs/1447_retention_erasure_lifecycle.mdand its Chinese translation underdocs/zh/rfcs/.zensical.tomlnavigation entries for both locales.The RFC defines five distinct operations (forget, governance, Scope archival, purge, erase), record classes, a versioned Lifecycle Policy, precedence with Legal Hold on top, a preview/plan-digest/apply run protocol with crash recovery and content-free receipts, in-place tombstones, derived-Artifact policy for Source erasure, stable erased citation states, projection and copy cleanup, a redacted audit, and an acceptance plan mapped to the issue.
Are there any user-facing changes?
No. Proposed API additions are design intent and do not ship here.
How was this change tested?
make docs-test: no issues.uv run prek run --files ...: all hooks passed.