> 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-and-operational-architecture.md).

# Compliance and Operational Architecture

The Arbridge compliance program is not a department that reviews work after the fact — it is an architectural layer woven through every operational surface.

## Architectural layers

**Layer 1 — Member perimeter.** Identity verification, sanctions screening, and source-of-funds review form the entry boundary. Nothing reaches the Pulse engine without clearing this layer.

**Layer 2 — Execution perimeter.** The Risk Desk's approved venue and token registry defines the operational surface Pulse is allowed to touch. The engine refuses to route outside this perimeter — not as policy, but as code.

**Layer 3 — Telemetric perimeter.** Every execution, settlement, and disbursement is written to an immutable log that both members and internal control functions reconcile against independently.

**Layer 4 — Governance perimeter.** Material changes to any of the above — new venues, new tokens, new strategies, new jurisdictions — require review through the Compliance and Governance Unit and, where relevant, the Risk Desk before they go live.

## Why layered architecture matters

A single point of compliance is a single point of failure. By distributing compliance enforcement across entry, execution, observation, and change-management, Arbridge ensures that a failure at any one layer is contained by the others.

## Review cadence

The architecture itself is subject to periodic review. Independent assessors evaluate both the controls as designed and the controls as operating. Findings drive architectural change — compliance posture at Arbridge is a living property of the system, not a frozen artifact.


---

# 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-and-operational-architecture.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.