Versions and deletions

Sentium preserves source history without confusing historical evidence with the provider's current state.

Immutable versions#

When source bytes change, Sentium creates a new immutable source version. It does not edit the earlier snapshot in place. Processing outputs record the exact version and processing configuration that produced them.

Historical citations remain pinned to the source version used during review, even after a newer provider revision arrives. New retrieval and drafting use the current eligible version after processing succeeds.

Renames and moves#

A rename or move inside selected scope updates source metadata when the provider's durable identity and content are unchanged. Sentium does not manufacture a new content version solely because a path changed.

Moving an item outside selected scope changes eligibility. The item is no longer available for current retrieval unless it is explicitly selected through another authorized scope.

Deletion and lost access#

Provider deletion, trash, or access loss creates a tombstone. The tombstone records why Sentium stopped seeing the source and removes it from current retrieval. It does not silently erase governed historical snapshots, citations, reviews, or audit history.

Retention and deletion requests follow the source data lifecycle. For how changes are detected, see sync and freshness.