{"path":"/guide/how-it-works/wf-store/retirement","content":{"title":"Retirement, preservation and recovery","summary":"Remove an asset from normal interpretation without destroying its source.","breadcrumbs":"[Everything guide](/guide) / [How Everything works](/guide/how-it-works) / [wf-store](/guide/how-it-works/wf-store)","body":"wf-store keeps immutable source assets even when they are no longer part of ordinary public results. This separates **logical retirement** from physical deletion.\n\nAn asset can carry the reserved `wf:deleted` tag. Ordinary reads and selections exclude retired assets. Removing that tag may restore eligibility if all other required metadata is still valid.\n\nUnpublishing is narrower than retirement: it makes a page revision unavailable to public readers while retaining its source and history. This is one reason a published page and a stored asset are different concepts.\n\nKeeping source separate from its public interpretation supports eventual consistency, ordinary repair and historical preservation. The durable identity of a page is independent of the physical layout or retrieval generation used to store it.\n\nSee [The tag model](/guide/how-it-works/tag-model), [How public visibility works](/guide/reading/visibility) and [Repair over prevention](/guide/how-it-works/repair-philosophy).","navigation":"[Everything guide](/guide) · Section: [wf-store](/guide/how-it-works/wf-store) · Previous: [Search families and their tradeoffs](/guide/how-it-works/wf-store/search-families) · Next: [Security and ownership](/guide/how-it-works/security)","related":[{"title":"Repair over prevention","url":"/guide/how-it-works/repair-philosophy"},{"title":"How public visibility works","url":"/guide/reading/visibility"}]}}