> 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/cross-project-data-hpm.md).

# Cross-Project Data \[HPM]

What this master **publishes down** to every structure project on the corridor.

A structure project pulls it with a **Project Objects** reference, choosing the shared object set by name. The bundle is a live expression rather than a snapshot, so it stays current as the master grows — a structure project that syncs later gets what the master holds then, not what it held when the reference was first made.

Alongside the objects, the bundle can carry the project's **coordinate system and local origin** and its **project parameters**. Both are switches on the shared object itself, and both are on for this workflow: the master is the authority on where the job sits and what it is checked against.


---

# 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/highway-project-master-workflow/cross-project-data-hpm.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.
