> For the complete documentation index, see [llms.txt](https://docs.awenetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.awenetwork.ai/governance/governance-process/wlp-and-wtp-overview.md).

# WLP & WTP Overview

**World Launch Proposals (WLP)** and **World Tokenization Proposals (WTP)** are the two governance processes that determine how new Worlds and their tokens are approved within the World.fun ecosystem.

***

#### World Launch Proposal (WLP)

A **World Launch Proposal** is a formal request to approve a new World for launch on World.fun.

Approval of an WLP:

* Grants the project a **"Coming Soon"** listing on World.fun
* Coordinates launch support from AWE contributors
* Makes the World eligible for further promotion, incubation, and partnership opportunities

***

#### World Tokenization Proposal (WTP)

A **World Tokenization Proposal** is a governance request to create and deploy a token for an approved World.

Approval of a WTP:

* Authorizes the deployment of the token contract
* Enables on-chain fundraising or distribution through World.fun
* Marks the transition from **concept validation** (via WLP) to **full tokenized operation**

***

#### Relationship Between WLP & WTP

1. **Step 1 – WLP:** Validate the idea and approve the World for launch.
2. **Step 2 – WTP:** Approve the creation of the token and its on-chain mechanics.

This two-step process ensures that projects entering the ecosystem have both **concept validation** and **token design** reviewed by the community before going live.\
\
Both WLP/ WTP goes through a Snapshot vote.


---

# 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://docs.awenetwork.ai/governance/governance-process/wlp-and-wtp-overview.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.