network-is-central-dependency
IN premise
`network.py` is imported by essentially every other module — api, storage, import, export, compact, check_stale, and all test files — making it the central data structure of the project.
Summary
The entire codebase revolves around network.py as its foundational module, since every major component depends on it for core data structures. Any change to network.py has the potential to ripple across the whole project, so it requires extra care and testing when modified.
Dependents
These beliefs depend on this one:
- central-dependency-is-safely-contained — Despite `network.py` being imported by virtually every module in the codebase, the three-layer architecture with clean boundaries ensures this central coupling does not create cross-cutting mutation paths — layer separation contains the dependency's blast radius so that the hub topology does not compromise architectural integrity.
Details
| Source | entries/2026/04/23/scan-ftl-reasons.md |