What a service stands on

Dependency mapping is the exercise at the heart of every resilience framework: not what a service is, but what it needs.

In Sudo Bank, 18 elements feed directly into Payment Operations, and 8 into Mortgage Operations. They share four: Backup & Disaster Recovery, Modern Core Banking, Customer Data Operations and Risk Management. Same bank, same exercise, and a visibly different answer.

Maintained by hand, a map like this goes stale between reviews. Here it is read from the model, so it is only as old as the model.

Then the reverse question. The upstream view stands behind a service and asks what could reach it: everything upstream, direct and indirect, ranked by how much of its impact would arrive. For Mortgage Operations it lists 29 elements, 8 direct and 21 indirect.

Downstream is your impact on everyone else. Upstream is where your trouble will arrive from.