![[Collective knowledge problems#^ownership-clarity]] ## Resolution > The property of a knowledge artefact having unambiguous answers to who creates it, who reviews it, and who retires it. ^definition Knowledge without ownership rots - no one updates it, no one is on the hook when it goes stale, and no one feels qualified to retire it. Ownership clarity closes that gap. It depends on the system carrying ownership as a first-class field (not folklore) and on the organisation having norms for handing over ownership when a person leaves. Without it, audit trails and attribution become impossible regardless of how rigorous the rest of the system is. ## In practice ```yaml owner: alice@org reviewer: bob@org review-cadence: 90d last-reviewed: 2026-02-15 ``` The artefact carries its ownership as frontmatter. When Alice leaves, the handover is one commit; when the review is overdue, an agent can surface it.