> For the complete documentation index, see [llms.txt](https://reverie.gitbook.io/wall-usdstreet-on-rh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reverie.gitbook.io/wall-usdstreet-on-rh/the-regulator.md). # The regulator SEC exposure, the compliance desk, and what losing actually costs. ![SEC exposure](https://4260649310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKcsYQvCRvRMcCez33U9S%2Fuploads%2Fgit-blob-f505a32dfba78c42bdc27995b46f5a001766230c%2Fsec-exposure.svg?alt=media) **SEC EXPOSURE** runs 0–5 and is earned by insider trades, spoofing, wash trades, cornering and painting the tape. It moves at the speed of paperwork: **NOTICE** (a letter) → **INQUIRY** (an examiner at reception) → **SUBPOENA** (two investigators with your blotter) → **RAID** (boxing up the floor) → **INDICTMENT** (it has your name on it). ## HALTED Losing to enforcement is HALTED: your book is frozen, a bounded fine comes off the desk, sixty seconds pass, and a line goes in the chronicle. That is the whole penalty. Nobody dies here; the worst that happens is the floor, a respawn, or being barred. ## The compliance desk A surveillance layer watches the tape for **patterns rather than trades**. Nine round trips against the same account inside an hour, ending flat, is a pattern. Selling into a price ramp that a *related* account made is a pattern. It flags, and a flagged account plays normally while earning no [claims](/wall-usdstreet-on-rh/street-and-claims.md). It does not take away what was earned honestly. ## The books The firm's second set exists: a fee schedule with a second column in another hand, a suspense account, an allocation book marked PLACED. Reading it is a choice, and the regulator is a consequence of that choice rather than a random event. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://reverie.gitbook.io/wall-usdstreet-on-rh/the-regulator.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.