A dependency rule checked in CI beats a diagram

An architecture diagram describes an intention and a dependency check describes what is true, and the two diverge from the first week.

$ vendor/bin/deptrac analyse --report-uncovered

  Orders → Catalogue
    app/Modules/Orders/PriceLookup.php:41

 Violations: 1
 Uncovered:  3        ← files in no layer at all

# the uncovered count is the underused signal: a new
# directory nobody assigned to a module is a boundary
# decision that was never made.

--report-uncovered is the flag worth turning on, because a file in no layer is exempt from every rule and accumulates silently. Generating the diagram from the same configuration means the picture in the documentation cannot disagree with the build.