> 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/governance-and-compliance-framework/compliance-principles.md).

# Compliance Principles

Arbridge Network's compliance posture is anchored in a short list of operating principles. They are stated plainly so that members, personnel, and counterparties can measure Arbridge's conduct against them.

## The principles

**1. Compliance is architectural.** Controls are built into the system, not bolted on after the fact. If a control cannot be enforced by the architecture, the architecture is reworked until it can.

**2. Evidence over assertion.** Every compliance claim Arbridge makes is supported by a record that can be produced on request — onboarding verifications, sanctions screenings, execution logs, policy versions, review approvals.

**3. Independence is non-negotiable.** The Compliance and Governance Unit, the Risk Desk, and internal audit functions operate outside commercial and engineering reporting lines. Their authority to intervene cannot be overridden by revenue considerations.

**4. Member interests over operational convenience.** Where a choice exists between a more convenient operational path and a better-protected member outcome, Arbridge chooses the member outcome. This includes choosing friction over speed when friction is protective.

**5. Disclosure is the default.** When something changes, members are told. When something goes wrong, members are told. Silence is not a compliance strategy.

**6. Regulation is a floor, not a ceiling.** Legal requirements define the minimum. Arbridge's standards — on identity, on execution transparency, on counterparty review — are intended to sit materially above that minimum.

**7. No member is above the framework.** Size of balance, seniority of relationship, and commercial value do not create exceptions to policy. The framework applies uniformly, or it does not apply at all.

**8. Continuous review.** Principles are re-examined on a fixed cadence and after every material incident. Where a principle is found to be insufficient, it is revised — publicly, with version history retained.

These principles govern how Arbridge conducts itself. They are the standard against which members are invited to judge us.


---

# 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/governance-and-compliance-framework/compliance-principles.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.