Under the five-state document lifecycle model for enterprise corpus governance, what is the mandatory operational behavior for documents marked as SUPERSEDED?
Day 2: Audit and Govern the Source Corpus
Audit and Govern the Source Corpus
Loading lesson content...
The PolicyDesk ingestion audit harness validates incoming document envelopes with the function above. Why does the audit rule strictly require a superseded_by pointer whenever lifecycle_state is SUPERSEDED?
FieldDesk is indexing 25 years of technical manuals. The repository contains identical manual uploads across different site directories, as well as scanned PDF copies of the same manual that have minor OCR variances and different PDF metadata headers. Why is cryptographic SHA-256 deduplication alone insufficient for cleaning this legacy repository?