> 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-ladder.md).

# The ladder

Eight positions, earned and granted, never bought.

![The ladder](https://4260649310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKcsYQvCRvRMcCez33U9S%2Fuploads%2Fgit-blob-0efbba294640027c135a142c19bb1b352b097850%2Fthe-ladder.svg?alt=media)

Promotion needs two things: validated **production** over a rolling window, and the gate the position names.

| Position             | Gate                                      | What changes                                         |
| -------------------- | ----------------------------------------- | ---------------------------------------------------- |
| MAIL ROOM            | —                                         | one lead list a day, no book, one specialist's names |
| COLD CALLER          | 20 closes                                 | your own lead list, phone commission only            |
| JUNIOR BROKER        | production + a sponsor                    | your own book, **the whole tape**, 20% payout        |
| BROKER               | production + the **SERIES** exam          | firm creation, bounties, 35%                         |
| SENIOR BROKER        | production + a corner held                | a window desk, 45%, two juniors                      |
| SALES MANAGER        | production + a junior promoted            | five juniors, the push board, 50%                    |
| PARTNER              | production + a corner held through a bell | the corner office, 55%, the book                     |
| THE NAME ON THE DOOR | one player per season, top production     | the boardroom, the bell                              |

## Production, not XP

Production is **gross commission over a rolling 30 market-day window**, and it decays. It is printed on the push board at the front of the room, which means the room can see exactly how you are doing — and you can see them.

Because production is commission, it can only come from trading. There is no purchase, no pass and no grind that substitutes for it.

## The firm

**DUNMORE & CROSS** is a broker-dealer in a converted auto-body shop off the expressway. Blue-chip names in the front of the pitch, chop stock in the back. A founder, **VIC DUNMORE**, who wrote the script everyone still uses. A floor of very young people making more in a month than their parents made in a year, and a compliance officer nobody has ever told the truth.

The firm is the hub, the quest-giver, the shop, the bank, the social space and the scoreboard. Nothing gates on which firm you are in, and no screen displays one as an identity.

## Standing

Two scores, both cosmetic and social — never a combat stat.

* **CREDIBILITY** — the fills you get, the spreads you are quoted.
* **NOTORIETY** — who front-runs you, who copies your trades.

Derived types: NOBODY, DIALER, SIZE, WHALE, LEGEND, BAGHOLDER.


---

# 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://reverie.gitbook.io/wall-usdstreet-on-rh/the-ladder.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.
