> For the complete documentation index, see [llms.txt](https://doj.secondliferp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doj.secondliferp.com/legislation/doj-legislation.md).

# Department of Justice Public Legislation

Second Life Roleplay Legislation Overview

The Judicial Bodies of San Andreas, including San Andreas Government and the San Andreas Department of Justice, are responsible for creating and maintaining all Government Legislation within the State of San Andreas.

Legislation can be proposed by the City Council, the San Andreas Medical Authority and any People’s Petition that has over 30 Signatures. The San Andreas Department of Justice reviews the legislation for its constitutional justification and alignment.

All legal changes, including changes to the legislation and penal code will be made public.

Each piece of legislation is available to read in Second Life Roleplay Public Documents. (there are plans to have a civilian MDT at the City Hall in the future to have this all available in county)

Second Life Roleplay County Guidelines - <https://secondliferp.com/rules>

Second Life Roleplay - <https://discord.gg/SecondLifeRP>

Second Life RP DOJ - <https://discord.gg/>


---

# 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://doj.secondliferp.com/legislation/doj-legislation.md?ask=<question>&goal=<user_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.
