> 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/construction-ex1-cug/superstructure-construction-ex1-cug/superstructure-attachment-construction-ex1-cug.md).

# Superstructure Attachment Construction

This section assigns superstructure attachments (barriers) to construction stages.

{% hint style="info" %}
**Navigation:** Construction > Superstructure Construction > Superstructure Attachment Construction

For detailed parameter explanations, see the [Superstructure Attachment Construction Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/construction-cug/superstructure-construction-cug/superstructure-attachment-construction-cug).
{% endhint %}

## Steps

### Step 1: Navigate to Superstructure Attachment Construction

Navigate to **Construction > Superstructure Construction > Superstructure Attachment Construction** in the tree view.

### Step 2: Assign Barriers to Stages

Associate barriers with the construction stage when they are installed (typically after deck curing).

### Step 3: Verify Sequence

Ensure attachments are assigned to stages after the deck is constructed.

## Verification

{% hint style="success" %}
After completing these steps, superstructure attachments are assigned to construction stages.
{% endhint %}


---

# 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/construction-ex1-cug/superstructure-construction-ex1-cug/superstructure-attachment-construction-ex1-cug.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.