# Product Flow

The complete OneWorld Launchpad flow can be divided into three main tracks:

1. Project owner launch and execution
2. User subscription and exit
3. Platform review and next-round qualification

These three tracks interact in every fundraising round. Project owners submit information, claim funds, and move the project forward. Users participate or exit according to the rules. The platform reviews project creation applications and stage proofs for the next round.

### Full Lifecycle

A project usually goes through the following lifecycle from creation to final trading:

1. The project owner prepares materials
2. The project owner submits a project creation application
3. The platform reviews project materials
4. The project is approved and displayed publicly
5. The current round enters upcoming or live status
6. Users subscribe in the current round
7. Eligible previous-round users may submit exit applications
8. The current round ends and is settled
9. Users claim Tokens, refunds, exit payments, or returned Tokens
10. The project owner claims successful fundraising
11. The project owner continues publishing Updates
12. If a next round is needed, the project owner submits a stage proof
13. The platform reviews the stage proof
14. After approval, the next round opens
15. After final launch, the project switches to trading status

### How Project Owners Use OneWorld Launchpad

The project owner flow is:

1. Use the official project account to launch the project
2. Submit project information, Token information, current-round fundraising parameters, and related explanations
3. Wait for platform review
4. After approval, the project enters public fundraising status
5. Publish Updates during fundraising
6. After the current round succeeds, claim the fundraising result
7. If a next round is needed, submit a stage proof
8. After the stage proof is approved, open the next fundraising round

Project owners should note that a successful round allows them to claim the funds from that round, but it does not automatically open the next round. If the project owner wants to continue fundraising, the stage proof must explain the value created by the previous-round funds and pass platform review.

### How Users Participate in OneWorld Launchpad

The user flow is:

1. Connect a wallet
2. Browse the project and current-round rules
3. Subscribe
4. If eligible, submit an exit application in later rounds
5. Wait for current-round settlement
6. After the result is finalized, claim Tokens, refund, or exit payment on-chain

Users should focus on:

1. Current-round price and sale amount
2. Current-round start time and end time
3. Whether the round still has subscribable allocation
4. Whether the project has published enough progress updates
5. Claim rules after current-round success or failure
6. Whether later rounds may allow exit applications

### The Role of Platform Review

The platform mainly reviews two types of submissions:

1. Project creation applications
2. Stage proof applications

Different reviews lead to different results:

1. After the project creation application is approved, the project can be displayed publicly
2. After the stage proof application is approved, the project can open the next fundraising round
3. After the final launch application is approved, the project can enter trading status

A rejection does not mean the project can never participate. The project owner can supplement materials, correct parameters, or clarify the roadmap according to the rejection reason, then submit again.

### What Happens Inside Each Round

Each round can be divided into four stages:

#### Configuration Stage

The project owner configures the sale amount, price, fundraising target, start time, end time, and next-step condition.

#### Participation Stage

Users subscribe. If this is a later round, eligible previous-round holders may also submit exit applications.

#### Settlement Stage

The system determines whether the round succeeds or fails based on subscription, exit applications, and the fundraising target, then generates the claimable result for users.

#### Execution Stage

The project owner claims the current-round funds and continues publishing Updates. If the project owner wants to open the next round, a stage proof must be submitted. After approval, the next round can open.

### Platform Flow Rule

OneWorld Launchpad project execution follows this flow:

Launch -> Review -> Fundraising -> Settlement -> Fund Claim -> Progress Updates -> Next-Round Application -> Proof Submission -> Review -> Next Round Opens

Project owners must complete each required step. Users can use the current status to understand whether the project is still fundraising, waiting for settlement, preparing the next round, or already in trading status.

### Common Status Change Example

A project may move as follows:

1. Submitted project enters pending review
2. Approved project enters upcoming status
3. At the start time, the project enters live status
4. After reaching the round target, the project enters successful status
5. Project owner claims the current-round funds
6. If preparing the next round, project owner submits a stage proof
7. After platform approval, the next round opens
8. After the final round is completed, the project enters live / tradable status

If a round does not meet the success condition, the project enters failed status. Users can claim refunds or returned assets according to the settlement rules, and the project owner cannot directly open the next round.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.oneworld.xyz/oneworld-launchpad/getting-started/product-flow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
