> 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/faq.md). # Questions Written to be read by somebody sceptical, because the ones worth having are. ### What does play actually earn? **Claims**, inside the game. A licensed partner settles the eligible ones. That is the whole mechanism, and no return of any kind is promised — by us or by anybody speaking for us. ### Can I buy my way to the top? No, and it is enforced rather than promised. The wardrobe is appearance, property is space and a bounded safe, a seat is access. Every position on the ladder is production plus a gate, and production is gross commission — which means it comes from trading and nothing else. There is a test in the repository that fails if a purchasable item ever grows a stat. ### Does a whale beat me? Not by being a whale. A round trip costs 50 bp, so making money needs `(2 × win rate − 1) × edge > 50 bp` — at a 54% win rate, better than 625 bp a trade. Somebody with a hundred times your money who churns loses to you if you wait and they do not. A whale who plays *well* will out-earn you, and should. This is a game, not a punishment. ### Is there a season pass? No season pass, no loot box, no gacha, no paid research edge, no paid queue priority, and no insurance against liquidation. The rule the build uses: if a proposal cannot be described without claiming it makes you better at trading, it does not ship. ### What stops two accounts trading with each other to farm claims? A compliance desk that watches the tape for patterns rather than trades. It flags and holds accrual — it never confiscates what was earned honestly. On top of that: a daily cap per account, a 24-hour hold, and a budget that refuses rather than borrows. ### Is there combat? There are contests, and there is a small amount of fighting. A contest runs on COMPOSURE — a tool lands PRESSURE and builds a READ the whole street can see — and losing is a FOLD. Three physical pieces exist and only three: fists, brass knuckles and a bat. A loss to one is a KNOCKOUT rather than a fold. Nobody dies either way, and it is a side activity: the trading case is still the loop. ### Where do two players actually fight? THE CURB, for a stake both sides escrow, on the kerb of whichever quarter you are standing in. Level 3 and up, brackets at 3–7, 8–14 and 15+, minimum stake $50. If the street is empty you can call out the house instead and THE HOUSE MAN comes looking for you. ### Are there factions or classes? No. One character, one floor. The four desk styles are unlocked rather than chosen and anyone can run all four; nothing gates on them and nothing displays them as an identity. ### Are the companies real? No. Every symbol, company and index is invented. No real person, firm name, film or brand appears in the game. ### Do I need a wallet to play? No. A wallet is only needed to move value across the two outward rails, and both ship disarmed. The game never asks for a seed phrase or a private key. ### Where does it run? In a browser, on desktop and mobile. All art and audio are generated in code. *** > Not investment advice. WALL STREET is a game; nothing in it is a solicitation to buy any security or token. --- # 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/faq.md?ask=&goal= ``` `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.