> 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/trading-oversight-and-strategy-governance.md).

# Trading Oversight and Strategy Governance

Every strategy Pulse executes against is a governed artifact. Governance begins before a strategy is live and continues for as long as it remains in production.

## Strategy lifecycle

1. **Proposal** — a candidate strategy is documented by Core Labs with its thesis, expected performance surface, risk indicators, and failure modes.
2. **Simulation** — the strategy is run in an isolated environment using historical and live-shadow data. Pulse evaluates it under the same probabilistic validator that will govern it in production.
3. **Risk Desk review** — the Risk Desk evaluates exposure characteristics, worst-case behavior, and the venues the strategy touches. Approval is formal and written.
4. **Staged rollout** — the strategy goes live under tight exposure limits, closely observed, with the ability to halt immediately.
5. **Full activation** — limits are expanded as evidence accumulates that real-world behavior matches expectation.
6. **Continuous oversight** — the strategy's live telemetry is monitored against its approved envelope. Drift triggers review.
7. **Retirement** — when a strategy no longer clears the validator's threshold — whether because markets have changed or venues have shifted — it is taken out of production and archived.

## Oversight principles

* **No silent changes.** Any modification to an approved strategy re-enters governance at the appropriate stage.
* **No override for performance.** Strong performance does not relax oversight. If anything, it invites additional scrutiny to verify the outcome is structural rather than incidental.
* **Failure is information.** When a strategy produces an outcome outside its approved envelope, Core Labs is responsible for explaining why, and the Risk Desk is responsible for deciding what changes as a result.

## Member-visible effect

Members experience strategy governance as consistency: the Pulse engine behaves predictably, execution matches telemetry, and the surface of what Arbridge does is documented and stable — even as the specific strategies behind the surface evolve.


---

# 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/trading-oversight-and-strategy-governance.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.