> 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/compliance-and-governance-unit.md). # Arbridge Compliance and Governance Unit The Compliance and Governance Unit is the custodian of the rules Arbridge operates under — both the regulatory requirements imposed externally and the ethical commitments Arbridge imposes on itself. ## Responsibilities * **Regulatory engagement** — maintaining licences, registrations, and reporting obligations in the jurisdictions where Arbridge operates * **AML program ownership** — administering, auditing, and continuously improving the [AML Compliance Policy](/arbridge-network-docs/learning-and-resources/aml-compliance-policy.md) * **Policy authority** — authoring, versioning, and enforcing the internal policies that bind members, personnel, and counterparties * **Oversight of the Risk Desk** — providing the reporting line and independence guarantee for risk control * **Member due diligence** — onboarding verification, ongoing monitoring, and periodic review * **Investigations** — reviewing alerts, escalations, and reports raised through any channel ## Independence The unit operates with a reporting path that does not run through commercial or engineering leadership. Its findings cannot be commercially overridden. Disagreements between compliance and business leadership are escalated to the highest governance layer for resolution — not resolved inside the commercial chain. ## Transparency Material changes to Arbridge's compliance posture are reflected in these docs. When a policy updates, the version history is retained, and members continue to have a reliable, current reference. --- # 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/compliance-and-governance-unit.md?ask= ``` 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.