Remove Protected Versions Through the Owner Function

Context

Versions retain structural changes and attribution. Their protection must coexist with complete workspace removal and the narrower reset contract.

Decision

The participant declares owner-function version removal rather than ordinary row deletion. Reset reaches that step after data removal without deleting kinds; purge removes kind configuration first as well.

Alternatives Considered

Grant ordinary application code direct version deletion. That would weaken the declared protection against rewriting structural audit evidence. Keep all structural versions after workspace deletion. That would retain deleted-workspace data beyond the declared lifecycle removal contract.

Consequences

Ordinary application access cannot rewrite unit, link or parentage versions. Removal is constrained by declared workspace lifecycle states and continues in batches. Purge retains applied seed-ledger entries, which affects reuse of a workspace identity.