reference
SupportOS governed data lifecycle
Retention, legal holds, and cross-owner subject erasure.
Retention policy, legal holds, and erasure requests derive scope from authenticated server authority. Erasure and subject-level holds begin from a revision-fenced case; the server derives the requester closure and never accepts an arbitrary subject target. Subject references are protected immediately; portable projections expose only a scoped digest. Active holds fail closed and remain visible.
Erasure is durable, idempotent, and evidence-bound across SupportOS, CommunicationOS, Forms, Knowledge, and CompanyOS. Each owner remains authoritative for its data. Completion requires terminal evidence from every owner, removal of the protected orchestration subject, and an immutable tombstone that prevents provider resurrection.