> 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/the-city/grove-street.md).
# Grove Street and Ganton
Where it starts. The alley, the cul-de-sac, the Johnson house, and the car.
The Ganton alley, first thing you see
You spawn in the alley from the meme: high walls, spray tags, a BAWSAQ poster, palms over the fence. This is Ganton. Follow it north and the walls open onto **Grove Street**, the cul-de-sac with the Johnson house at the end and the overpass behind it.
Grove Street cul-de-sac
## What is here
* **The Green Sabre**, parked in the street. Press E. See [The Sabre](/playing/the-sabre.md).
* **Grove Street Families** walking their block. They will not start anything, but you can.
* **Lore boards** for chapter one: the return, Sweet, Ryder, Big Smoke, and the line that gave the game its name.
* The **GROVE ST 4 LIFE** and **FAMILIES** tags. Free Roam fights tend to happen right here, because everyone spawns nearby.
{% hint style="info" %}
Free Roam knockouts count on the all-time leaderboard, and this is where most of them happen.
{% endhint %}
---
# 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://docs.bawsaq.org/the-city/grove-street.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.
