> For the complete documentation index, see [llms.txt](https://arbridge-network.gitbook.io/arbridge-network-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arbridge-network.gitbook.io/arbridge-network-docs/arbridge-network-lab/strategic-relations-unit.md).

# Arbridge Strategic Relations Unit

The Strategic Relations Unit manages the relationships that sit outside the Pulse execution graph but are essential to Arbridge's ability to operate — partners, venues, infrastructure providers, institutional allocators, and ecosystem counterparties.

## Remit

* **Venue and protocol relationships** — maintaining direct channels with the decentralized exchanges, bridges, and liquidity providers Arbridge interacts with
* **Infrastructure partnerships** — node providers, custody technology vendors, and data providers whose services underpin Arbridge operations
* **Institutional counterparties** — allocators, aggregators, and professional users operating inside Arbridge's compliance perimeter
* **Ecosystem contribution** — Arbridge's participation in industry working groups, research forums, and open standards

## Operating principles

* **Commercial terms do not influence execution.** The Pulse engine's venue registry is controlled by the Risk Desk on technical and compliance grounds. A partnership does not buy routing priority.
* **Disclosure is mandatory.** Any material commercial arrangement with a venue or counterparty that Pulse interacts with is disclosed to the Compliance and Governance Unit and reviewed for conflicts.
* **Reciprocity is expected.** Counterparties that fail to meet the transparency, technical, or compliance standards Arbridge holds itself to are removed from the relationship set — regardless of commercial value.

## Outcome

The unit's work is successful when the infrastructure Pulse depends on is more resilient, more liquid, and more transparent than it would be without Arbridge's participation.


---

# 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:

```
GET https://arbridge-network.gitbook.io/arbridge-network-docs/arbridge-network-lab/strategic-relations-unit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.