> 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/highway-project-master-workflow/project-parameters-hpm.md). # Project Parameters \[HPM] The project-wide values every structure on the corridor is designed and checked against — design code, design temperature, owner criteria, load factors. They are ordinary global parameters, so any expression in any project can read them by name. What makes them project-wide is that the master publishes them: when a structure project pulls the shared bundle, these are merged into that project's own parameter set, together with their units, categories and validation rules. The master wins for anything it defines, and reports what it replaced. Parameters the master does not define are left alone, so a structure project keeps its own working values. --- # 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/templates/highway-project-master-workflow/project-parameters-hpm.md?ask=&goal= ``` `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.