> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.umnai.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.umnai.com/_mcp/server.

# Module dependencies

Use module dependency plots to inspect how a selected module contributes across feature values. Start in **Explanation Lab > Global Explanations** with the intended deployed model selected.

## Before you begin

Select a running deployment and identify a module to investigate. Use [Model structure and decision rules](/ui-guides/explanations/decision-rules) to check which feature or interaction the module represents.

## Inspect module dependencies

1. In **Global Explanations**, select **Module Dependencies**.

2. Choose a module using **Select Module**.

3. Read the **Module Dependency Plot**, including its axis labels and categories.

4. Compare the pattern with the corresponding decision rules.

## Interpret the plot

For the **gender** module, the example plot shows **Female**, **Male** and **Masked** categories against attribution. Female and Masked have negative contributions, while Male has a positive contribution in this model.

This is a useful starting point for investigating how the model treats a feature. It is not, by itself, a fairness assessment. Review the broader model, relevant population, evaluation data, and decision context before drawing conclusions.

## Use Module Explorer

To open the broader plot view, select **Module Explorer** in the navigation. The page title is **Module Dependency Plot Explorer**.

In Module Explorer, select the deployed model and use the search field and module-type controls to choose which plots to display. Select **1 per row**, **2 per row** or **3 per row** to change the layout. Expand a plot to inspect it in more detail.

If the explorer displays a loading or no-match message, check the selected model, clear the search or filters as needed and wait for loading to finish. An empty filtered view does not establish that the model has no modules. The screenshot below shows the loading and filter messages to help identify this state.

![The gender module dependency plot displays Female, Male, and Masked categories.](/_fern-files/_img/6e8e0f9d56eeb547bde144697b81f652ef64b1aae0e80ab548731b79567e5dcc.webp)

![Module Explorer controls with loading and no-match messages.](/_fern-files/_img/285d59ed7b1cd162995f5fc8907d8c987bbc680682223c666b95b3ac74f77be3.webp)

Compare the plot with the module's rule conditions and the observed feature range. Categorical axes represent distinct labels; their positions do not establish an ordered or continuous relationship. For interaction modules, interpret the displayed features together.

## Next steps

Continue to [Dependency graph](/ui-guides/explanations/dependency-graph).