> 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/risk-desk.md).

# Arbridge Risk Desk

The Risk Desk is the independent control function that stands between strategy intent and member capital. Its job is to say no when the data says no — and to say so unambiguously.

## Mandate

The Risk Desk owns the boundaries inside which Pulse is permitted to operate. It maintains the engine's approved venue registry, its position-sizing limits, its exposure caps per network and per token, and the thresholds at which execution is halted.

## Daily functions

* **Opportunity registry review** — evaluating and approving (or rejecting) new venues, tokens, bridges, and routes before they become eligible for Pulse execution
* **Limit management** — setting and adjusting per-tier, per-network, and per-token exposure limits based on current liquidity conditions
* **Real-time monitoring** — watching execution telemetry for drift, clustering, or failure patterns that warrant intervention
* **Kill-switch authority** — unilateral power to halt execution at any granularity — venue, network, strategy, or engine-wide — without operational approval

## Independence

The Risk Desk reports through the Compliance and Governance Unit, not through commercial or engineering leadership. Its authority to pause, limit, or veto execution cannot be overridden by performance or revenue considerations.

## Philosophy

An unprofitable opportunity is inconvenient. An unvetted one is existential. The Risk Desk optimizes for the second consideration, explicitly and always.


---

# 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/risk-desk.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.