IFO4
Loading...The subset of technical debt that arises from system-level design decisions, including monolith decomposition deficits, service ownership ambiguity, and platform fragmentation. Architectural debt is more expensive to remediate than localised technical debt because the remediation requires coordinated change across services, teams, and release cycles. The federation requires architectural debt to be tracked separately from local technical debt with explicit remediation owners and multi-quarter horizons under UFMS-001:2.4(g). Steward tier members publish a federation crosswalk of architectural debt annually.
A specialisation of the Cunningham technical debt metaphor that emerged in the microservices and platform engineering literature of the mid 2010s.
Federation members maintain a separate architectural debt register with multi-quarter horizons. Steward tier accreditation includes a published federation crosswalk under MEV-Annex:3.2. Architectural debt is a quarterly metric in the IFO4 Score calculation.
@misc{ifo4_glossary_architectural_debt,
title = {{Architectural Debt}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{architectural-debt}}},
year = {2026},
url = {https://ifo4.org/glossary/architectural-debt},
note = {Category: Waste; key: ArchitecturalDebt}
}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.