| DL-001 | 2026-07-11 | PL-101 Project Loom Ontology | Added Implementation Debt | Existing concepts couldn’t explain pre-existing structural weaknesses | Technical Debt, Institutional Debt | Case #002 |
| DL-002 | 2026-07-11 | PL-101 Project Loom Ontology | Added Governance Fragility | No concept explained external vulnerability | None | Case #001 |
| DL-003 | 2026-07-11 | PL-101 Project Loom Ontology | Added Fragility subtypes | Two distinct fragility mechanisms; conflating reduced precision | Single fragility concept | Cases #001, #002 |
| DL-004 | 2026-07-11 | PL-101 Project Loom Ontology | Added Dependency Concentration | Chains alone couldn’t explain cascading failure | None | Case #002 |
| DL-005 | 2026-07-11 | PL-101 Project Loom Ontology | Added Formal vs. Effective Authority | Divergence between legal empowerment and practical control | None | Cases #001, #002 |
| DL-006 | 2026-07-11 | PL-101 Project Loom Ontology | Added Capacity Domains | Aggregated ratings misleading | Single capacity rating | Case #002 |
| DL-007 | 2026-07-11 | PL-201 Loom Analysis Protocol | Added Level of Analysis | Protocol risked conflating analytical levels | No level specification | Case #003 |
| DL-008 | 2026-07-11 | PL-201 Loom Analysis Protocol | Added Evidence Standards | Improve transparency and consistency | No evidence ratings | Cross-case review |
| DL-009 | 2026-07-11 | PL-201 Loom Analysis Protocol | Added Stage 10 | Create formal feedback loop | Framework unchanged by cases | Cross-case review |
| DL-010 | 2026-07-11 | PL-201 Loom Analysis Protocol | Added Design Adequacy classification | Protocol implied all disappointing outcomes are governance failures | No design classification | Case #003 |
| DL-011 | 2026-07-11 | PL-901 Artifact Registry | Established Artifact Registry | Project needed canonical structure | Ad hoc management | Project maturation |