> 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-to-neglect.md).

# Passive Pressure to Neglect

How the program handles a specified amount of passive pressure to neglect above the toe.

## How does the program handle the situation where the user specifies some amount of passive pressure to neglect?

When you specify some amount of passive pressure above the toe to neglect, the assumption is that it is because that soil may become frost-disturbed or otherwise insufficiently compacted to generate the specified passive pressure. But the assumption is also that the frost-disturbed soil will still be there as overburden to help the subsoil generate the specified passive pressure. As a result, when you specify some amount of passive pressure above the toe to neglect, the passive pressure distribution becomes trapezoidal. The trapezoid can be constructed by starting with a triangle with its vertex at the top of the soil on the toe side. Then remove a triangle whose vertex is at the top of the soil on the toe side and whose bottom is at the bottom of the layer of passive pressure that is to be neglected. The remaining pressure diagram describes the passive pressure distribution that is considered to be effective.


---

# 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-to-neglect.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.
