> 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/penal-code/offenses-against-public-order/government-corruption.md).

# Government Corruption

The abuse of power by government officials for personal gain, typically at the expense of the public interest. It involves acts such as bribery, embezzlement, favouritism, fraud, and the manipulation of government processes for private benefit.

Key elements

* Bribery: Offering, receiving, or soliciting payments or favours to influence decisions or actions.
* Embezzlement: Misappropriating public funds or resources for personal use.
* Nepotism or favouritism: Granting government contracts, jobs, or benefits to friends, family, or associates without merit.
* Fraud or manipulation: Engaging in deceitful practices to benefit oneself or a select group, often at the cost of the public.

**Felony**

**Sentence: Hold Until Trail**

**Fine: Hold Until Trail**


---

# 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/penal-code/offenses-against-public-order/government-corruption.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.
