> For the complete documentation index, see [llms.txt](https://whitepaper.getpaid.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.getpaid.family/roadmap/phase-0-concept.md).

# Phase 0: Concept

Defines the September 2026 concept foundation, including research, protocol direction, economic design, and explicit validation criteria.

### Timeline

**September 2026**

Phase 0 is GetPaid's current concept stage. It establishes the foundation for a proposed fee-routing protocol before testnet implementation.

| Foundation area        | Scope                                                                              |
| ---------------------- | ---------------------------------------------------------------------------------- |
| Protocol thesis        | The core case for generalized launchpad fee routing.                               |
| Market research        | The market context and conditions the protocol is intended to address.             |
| Predecessor analysis   | Lessons and constraints drawn from related fee-routing and launchpad models.       |
| Architecture direction | The initial direction for routing, payout, economic, and governance components.    |
| Economic model         | Proposed fee distribution, protocol revenue, treasury, and token mechanisms.       |
| Initial roadmap        | A sequential path from concept through testnet, review, deployment, and expansion. |
| Invalidation criteria  | Explicit conditions that can challenge or retire the project thesis.               |

### Conviction-Build result

F9 Conviction-Build passed at **0.55**. This represents moderate conviction in the current thesis, not product-market fit or production validation.

The protocol remains pre-testnet. Its architecture, economics, and roadmap require implementation, testing, and review before later phases.


---

# 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 dynamically by asking a question.

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

```
GET https://whitepaper.getpaid.family/roadmap/phase-0-concept.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.