> 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/csp-violation.md).

# Browser CSP violation

1. Keep execution disabled and capture the directive, blocked URI class, page and release commit. Do not paste query strings, tokens or wallet data into tickets.
2. Confirm the response has a fresh nonce and every framework `<script>` carries the same value. A reused or missing nonce is a release failure.
3. Classify the resource: same-origin application asset, official Arcus/Hyperliquid connection, computed style attribute, or unexpected injection.
4. For expected same-origin assets, reproduce in the production build and fix nonce propagation or asset packaging. Do not add `unsafe-inline` to `script-src`.
5. For a new external origin, require an architecture/security review and exact production evidence before changing `connect-src`; wildcards are prohibited.
6. Treat unexpected script, frame, object, font or media attempts as hostile until disproved. Preserve browser/network evidence, restart the clean committed build and rotate any potentially exposed operator credential outside NIGHTSHIFT.


---

# 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/csp-violation.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.