> 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/department-of-justice-public-legislation/san-andreas-constitution/article-2-judicial-congress/writ-of-habeas-corpus.md).

# Writ of Habeas Corpus

San Andreas Law recognizes Writ of Habeas Corpus as a code under the Constitution which grants all free persons protection against illegal imprisonment.

This does not include approved investigative Hold by Judicial Power, Federal Agents or Police Department (PD) Command Members.

Federal Agents are able to do their own investigative detainment up to 72 hours.

PD Command are able to do their own investigative detainment of up to 24 hours anything beyond that is to be approved by Judicial Power and is not to exceed 72 hours total.

To hold an individual Upton investigation, the state must have reasonable suspicion upon the individual that they were involved in a crime. Writ of Habeas Corpus does not include the 72 hours holds of “Held Until Trial” charges that have sufficient probable cause as evidence. As well as 5150’s that have been approved.


---

# 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/department-of-justice-public-legislation/san-andreas-constitution/article-2-judicial-congress/writ-of-habeas-corpus.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.