A provisioned asset whose parent or controlling resource has been deleted, leaving the asset disconnected from its original purpose but still incurring charges. Orphan assets are typical of attached storage volumes, public IP addresses, snapshots, and load balancer artefacts whose owning compute has been terminated. The federation requires orphan asset detection on every weekly cycle, with a remediation SLA of fourteen days unless the asset is reassigned to a new parent or formally retained for compliance. UFMS-001:2.4(c) governs the detection and remediation cadence.
From the Greek orphanos, parentless; the metaphor entered IT vocabulary via filesystem nomenclature for files without parent directories.
Federation members run orphan asset detection weekly. Orphan storage and snapshots are auto-deleted after the retention SLA unless held for compliance, in which case the rationale is documented under MEV-Annex:3.2. The detection coverage is reviewed annually.
@misc{ifo4_glossary_orphan_asset,
title = {{Orphan Asset}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{orphan-asset}}},
year = {2026},
url = {https://ifo4.org/glossary/orphan-asset},
note = {Category: Waste; key: OrphanAsset}
}Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.