> For the complete documentation index, see [llms.txt](https://nytshift.gitbook.io/nytshift-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nytshift.gitbook.io/nytshift-docs/policy-control-and-incident-response/aegis-risk-policy.md).

# AEGIS risk policy

## Interpret a rejection

The execution review returns a deterministic `decision.reason`, fixed message, policy version and numeric metrics. For the position-safe rules:

* `SYMBOL_NOTIONAL_LIMIT` with **Reduce-only intent does not close an existing position** means the fresh account was flat, or the order side would add to the position.
* `SYMBOL_NOTIONAL_LIMIT` with **Reduce-only quantity exceeds the open position** means the venue-normalized quantity could cross through zero.
* `GROSS_EXPOSURE_LIMIT` with **Projected correlated exposure exceeds policy** means the applicable correlation group breached its equity-relative cap before signer I/O.
* `RISK_POLICY_INVALID` is a configuration defect, not a tradable rejection. Keep execution disabled and repair the reviewed policy source.

Do not retry by clearing `reduceOnly`, changing account evidence, weakening the policy or splitting one intended position flip into smaller calls. Re-read the live position, correct the closing side and cap the quantity to the currently open amount. A later review must fetch fresh book, account, position and policy evidence again.

## Verify the default envelope

```powershell
pnpm --filter @terminal/risk test
pnpm --filter @terminal/web test -- app/api/execution/server.test.ts
pnpm typecheck
```

The default `crypto-beta` group contains BTC, ETH, SOL and HYPE with a 20% equity cap. The ordinary symbol cap remains 10% and gross cap remains 35%. Any policy change requires a new reviewed version, bounded deterministic tests and a complete release gate; changing a number in local state is not authorization.

## Incident response

If a confirmed order is nevertheless canceled or rejected as reduce-only by Hyperliquid, do not resubmit automatically. Preserve the CLOID and normalized lifecycle evidence, reconcile through the signer, and compare the account position observed at review time with venue state at execution time. Position movement between review and fill can legitimately make a once-valid reduction no longer reducing. The venue result remains authoritative.


---

# 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, and the optional `goal` query parameter:

```
GET https://nytshift.gitbook.io/nytshift-docs/policy-control-and-incident-response/aegis-risk-policy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
