> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-faq/using-the-software/calculation-modules/retaining-walls/cantilevered-retaining-wall/passive-pressure-does-not-resi.md).

# Passive Pressure does not resist stem flexure

Why passive pressure is used only for sliding resistance and not as resistance to retaining wall stem flexure.

## Why doesn't the module consider passive pressure as resistance to stem flexure?

Passive pressure is only considered when evaluating sliding. It is not used as resistance to stem flexure. The amount of movement required to mobilize typical passive pressures is so significant that most walls would be considered to have failed by the time that pressure had been mobilized.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/sel-faq/using-the-software/calculation-modules/retaining-walls/cantilevered-retaining-wall/passive-pressure-does-not-resi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
