> For the complete documentation index, see [llms.txt](https://docs.bawsaq.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bawsaq.org/playing/hud.md).
# The screen, explained
The heads-up display
1. **The tape.** Live prices of the listed companies, ticking across the top, straight from Robinhood Chain. Green is up, red is down over the last window.
2. **Controls hint.** A one-line reminder of the keys. It stays until you know them.
3. **Health.** Five green bars at the top right. Each landed kick takes one; they grow back after four seconds without damage.
4. **Radar.** The minimap rotates with your camera. The triangle is you. White dots are other players, coloured dots are NPCs. District names show where you are.
5. **Who is online.** Everyone in your room, with the all-time rank of anyone who has fought.
6. **The feed.** Joins, knockouts, round bells, chat. The last few lines only.
7. **Chain status and the clock.** Block height, BAWSAQ burned, and the in-game time. The city stays at 22:00.
8. **Progress.** Lore boards read and dossiers found. Press Tab for the full checklist.
## The arena panel
During rounds a **BAWSAQ Arena** panel sits at the side: the round timer, the pot, who is in, and the **Wallet & claims** drawer with the **Approve + Enter** and **Redeem claim** buttons. It is explained in [Enter the arena](/start-here/enter-the-arena.md).
## Dossier cards
Walk up to any company logo and its dossier slides in at the bottom left: name, sector, description, live price, contract address. See [Lore and dossiers](/the-city/lore-and-dossiers.md).
A dossier card, opened by walking up to a shopfront logo
---
# 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://docs.bawsaq.org/playing/hud.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.