> 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/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/substructure-code-checks-ex1-stg.md).

# Substructure Code Checks

This section defines code checks for all substructure components according to AASHTO specifications.

{% hint style="info" %}
**Navigation:** Substructure Code Checks
{% endhint %}

## Overview

Substructure code checks verify structural adequacy for:

* Pier caps
* Pier columns
* Footings
* Piles

Code checks are performed according to AASHTO LRFD Bridge Design Specifications.

## Sections

| Section       | Description                                    |
| ------------- | ---------------------------------------------- |
| Pier Cap      | Verify pier cap flexure and shear capacity     |
| Pier Column   | Check column axial and flexural capacity       |
| Pier Footing  | Verify footing bearing and structural capacity |
| Pile Capacity | Check individual pile capacity                 |

{% hint style="success" %}
Complete code checks after defining all load combinations and templates.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrim.org/examples/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/substructure-code-checks-ex1-stg.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.