Technical Debt Inventory and Attributes

The relationship between the Technical Debt Inventory and the Issues Inventory is one of seeding and cross-reference. Issue records may seed Technical Debt candidates when a Defect, Problem, Disruption, or other Issue reveals a continuing technical condition or unresolved obligation. After qualification, the inventories cross-reference one another: the Issues Inventory remains authoritative for the Issue lifecycle and Issue-specific resolution, while the Technical Debt Inventory governs the independently manageable debt condition. A dedicated related inventory is not present in the supplied IF4IT URL inventory. Until one is published, refer to the IF4IT Enterprise Inventory Management Best Practices document for the current Noun Type definition and inventory-governance context.

The relationship is carried through these attributes: Related Issues [Multi-Value]; Candidate Source Record; Record Source; Evidence References [Multi-Value]; Discovery Method; Cause; Technical Debt Condition Statement; Qualification Rationale; Reconsideration Triggers [Multi-Value]. The related inventory’s stable Semantic Identifier or other authoritative identifier should be stored rather than duplicating the full related record. Changes that affect materiality, priority, acceptance, remediation, validation, closure, or reopening should be reconciled across both records while preserving each inventory’s separate audit history.

This relationship allows enterprises to identify recurring or structural debt from operational and engineering evidence without indiscriminately converting every Issue into Technical Debt. It supports root-cause analysis, recurrence detection, impact evidence, prioritization, validation, and post-closure monitoring. Without the relationship, Issues may be closed while the underlying debt persists, or the same condition may be duplicated across systems without clear authority.