> 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/kill-switch.md).

# Kill switch

1. Set `ARCUS_EXECUTION_KILL_SWITCH=true` in the separate signer/control-plane environment and restart that supervised boundary. Confirm ordinary Arcus order readiness reports `ARCUS_KILL_SWITCH_ACTIVE` before taking any cancellation action.
2. Authenticate the local operator session and inspect the exact configured Arcus owner account. In Safety settings, confirm **Emergency stop** reports `READY`.
3. Select **Review cancel all**. Verify network, account index, current open-order count and market distribution. The ten-second review grants one account-wide cancellation attempt only.
4. Confirm once. Do not repeat the request after an ACK, timeout, disconnect or unknown result. Arcus `202 / CANCEL_ALL_ACKNOWLEDGED` is asynchronous, not proof that orders are gone.
5. Use **Reconcile open orders** until the exact account-wide result is `clear` with `openOrderCount: 0`. Keep the kill switch active while any order remains or state is unknown. Compare the public `orders` stream and a new open-orders snapshot.
6. Reconcile fills, positions, collateral and audit evidence. An order may fill while cancellation is being processed; cancel-all does not close positions.
7. If compromise is suspected, stop the isolated signer, follow Arcus's owner/master-wallet [API-key revocation procedure](https://docs.arcus.xyz/api-reference/onboarding/revoke-api-key), and rotate internal/confirmation/operator credentials. NIGHTSHIFT never revokes an owner key automatically.
8. Do not re-enable order entry until the incident owner, risk owner and security owner approve a documented recovery, a newly reviewed key where applicable, and a new policy version.


---

# 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/kill-switch.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.