Explainable impact
Reverse dependency traversal identifies potentially affected services and records deterministic shortest paths that explain why each result appears.
ENGINEERING PROJECT / PROJECT DETAILS
ENGINEERING ARTIFACT / PYTHON
The Infrastructure Dependency Analyzer traces a declared service inventory to show potential downstream business impact, dependency paths, circular prerequisites, recovery-target alignment questions, and validation order.
Reverse dependency traversal identifies potentially affected services and records deterministic shortest paths that explain why each result appears.
Detects cycles, highlights RTO alignment questions, and separates declared recovery objectives from demonstrated recovery capability.
25 automated tests cover graph directionality, cycles, duplicate paths, malformed inventories, safe report generation, and CLI behavior. GitHub Actions runs Python 3.10 through 3.13.
Source code, fictional inventories, an interactive offline report, automated tests, and the CI workflow are available on GitHub.
A change can affect services through dependencies that a flat server list hides.
Model resources and directed dependency edges, then inspect the assumptions behind an impact path before using it in a change review.
The linked project source is the implementation record. A dependency path is a hypothesis about impact until checked against the real environment.
Compare a known service dependency with observed configuration and record stale, missing and directional edges.
Open the related experiment or review surface →LET’S BUILD SOMETHING THAT MATTERS
Infrastructure, engineering, technical leadership, and the next challenging problem.