> 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/statute-of-limitations-and-license-removal/statue-of-limitations-and-license-removal.md).

# Statue of Limitations & License Removal

Warrants

* Arrest Warrants: A Warrant is valid for 30 days after the date of the crime(s) underlying the warrant, NOT from the time a Judge signs said Warrant. A judge may approve a Warrant for a shorter period of time depending on the Warrant that has been requested. Law Enforcement may also request that a warrant to be extended.
* Search and Seizure Warrant: is valid for 30 days after the date of the crime(s) underlying the warrant, NOT from the time a Judge signs said Warrant. A judge may approve a Warrant for a shorter period of time depending on the Warrant that has been requested. Law Enforcement may also request that a warrant to be extended.

License Removal:

Hunting/Fishing License

* Must wait 14 days to request a hunting/fishing license after it is revoked before reapplying

Weapons License

* Must wait 30 days after revoked and an informal hearing in front of a Judge is required.

Driver License

* Must wait 7 days after it is revoked before reapplying.

Bike License

* TBC

Pilot License

* TBC

Implementation

Timeline for Enactment: Effective immediately.


---

# 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/statute-of-limitations-and-license-removal/statue-of-limitations-and-license-removal.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.
