> 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/contract-law-act.md).

# Contract Law Act

The purpose of this act is to outline and clearly define what is required within a contract to be considered valid by the San Andreas Department Of Justice.

**Section 1: Contract Requirements**

1. An offer, The offer must be a clear and intentional proposal made by one party to another. The offer must contain essential terms such as timeframes and prices. Vague or open ended statements do **NOT** constitute a valid offer.
2. Acceptance, Unconditional agreement to the terms of the offer. Any attempt to change the terms during acceptance is considered a "Counter offer" and is not treated as acceptance.
3. Consideration, Referring to something of value exchanged between the parties entering into the contract. This may take the form of money, goods or services. Consideration is required, without it the contract is unenforceable. Consideration must be of reasonably equivalent value to the obligations involved in the contract. Nominal or token consideration (e.g. $1 for a house) may render a contract void; unless justified by context and witnessed by the appropriate legal counsel
4. Capacity, All parties entering the contract must be legally competent and authorized to do so. This means they must; Be at least the age of majority, Not be under the influence of drugs or alcohol at the time of the agreement, Be of healthy state of mind (No recent head trauma) The "qualified authority" may use their own discretion to reject either parties signature if they have a reasonable belief that the person is not in a competent state of mind.
5. Legality, The subject matter must be legal. Contracts involving any illegal activities are void and unenforceable, regardless of whether other elements are met.
6. Signature and Witnessing, All contracts must be signed and dated by all parties involved and witnessed by at least one qualified authority, which may include

* City Clerk
* Legal Aid
* Lawyer
* FIB Agent
* Judge
* Justice
* Or any other recognized higher authority within San Andreas Department Of Justice

**Ambiguity Clause**

In the event that a contract term is "Ambiguous" the ambiguity shall be construed in favor of the party that did not draft the contract.

**Writing, Retention and Logging**

All contracts must;

* Be "in writing", either physical or digital
* A copy must be retained by each party involved
* An additional copy must be filed by a lawyer to the San Andreas Department Of Justice

**Section 2: Definitions**

"Counter offer" - A counter offer is defined as when a party accepts the contract, but with specific conditions. A counter offer is not considered an unconditional acceptance.

"Ambiguous" - Is defined as when a term or a statement could have multiple reasonable interpretations.

"Qualified Authority" - Refer to section 1 point 6

"In Writing" - Refers to any recorded form of text that can be preserved and shown in court

**Implementation** 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/contract-law-act.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.