ALL-ARCH0005 · evidence
This page continues ALL-ARCH0005 directly from its source docstring. Read its implementation.
Evidence
Section titled “Evidence”Each finding names the module, how many of its types are contracts, and that nothing in the repository imports it. The value is whether this module is an abstraction with no dependents.
Exceptions
Section titled “Exceptions”A library publishes abstractions for callers outside its own repository, and a plugin contract a framework loads by name is reached in a way no static graph sees, so both are legitimately unreferenced here and belong in the exclusion set rather than in the code that gets deleted. A module the tests alone implement is genuinely unused by the shipped code, which is worth knowing rather than worth hiding. A repository whose whole graph is unresolved reports every module this way, so an empty afferent count across the board is a reason to check the graph before acting on any single finding.
References
Section titled “References”- Cites “Agile Software Development”, the zone of uselessness
- Cites “Clean Architecture”, chapter 14, component coupling
- Cites “Design Principles and Design Patterns”. Open reference
- Cites “Extreme Programming Explained”, you are not going to need it