> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/retaining-wall-workflow/construction-rw/retaining-wall-construction-complete-rw.md).

# Retaining Wall Construction (Complete) \[RW]

Activates the retaining wall and everything it carries at a chosen construction stage. All selected objects are placed in a single step, so their self-weight and stiffness enter the analysis from that stage onward.

## General

**Stage:** Choose the stage at which the selected objects are constructed.

**Wall Segments:** Wall segments constructed in this stage.

**Footing Steps:** Footing Step objects constructed in this stage.

**Barriers:** Barrier objects constructed in this stage.

**Sound Walls:** Sound Wall objects constructed in this stage.

**Self Weight Factor:** Controls the scaling of self-weight during finite element analysis (default: 1.0).


---

# 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://docs.openbrim.org/templates/retaining-wall-workflow/construction-rw/retaining-wall-construction-complete-rw.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.