> For the complete documentation index, see [llms.txt](https://annarbor.worldiaday.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://annarbor.worldiaday.org/people/paul-dannels.md).
# Paul Dannels
In his role as principal at SDI Structures, Paul conceives innovative structural solutions for buildings on behalf of both aspiring and accomplished architects. His many clients value his ability to quickly grasp complex architectural intentions and effectively render them in structural form. His designs have earned three IDEAS2 Awards from the American Institute of Steel Construction, the industry's highest engineering honor for buildings constructed with steel. his projects have received numerous other national and regional recognitions and have been published widely. Paul is the 2013 Vice President/President Elect of AIA Michigan, and has served the organizations in numerous capacities. He is an adjunct faculty member at Lawrence Technological University where he teaches engineering principals in the College of Architecture and Design. Paul grew up in western New York, where as a teenager grand buildings like the Buffalo City Hall and Buffalo State Hospital captured his imagination. He studied engineering and architecture at the University of Michigan, and worked as a construction engineer in remote northern Michigan before forming SDI-Structures.
---
# 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://annarbor.worldiaday.org/people/paul-dannels.md?ask=&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.