# Project Profile Setup

#### Choosing the right category

Pick the category investors will expect from your product today (DeFi, Infrastructure, Gaming, Consumer, Tools, etc.). If you span multiple areas, choose the one that best reflects your first utility at launch and call out secondary use cases in the description.

#### Writing a clear description

Lead with what the product does, for whom, and why it needs a token. Avoid roadmap promises in the top paragraph; link to the roadmap below.

* Good (clear, factual):\
  “ArcLight is a non-custodial liquidity routing SDK for Mosaic-based DEXs. Our token, ARC, grants fee discounts in integrated apps and is used to prioritize routing in partner pools. MVP live with two DEX integrations.”<br>
* Bad (vague, promotional):\
  “ArcLight is the future of DeFi, revolutionizing everything with unparalleled innovation and massive growth potential.”<br>

Follow with 3–5 bullets that investors can scan: current status (MVP/testnet/mainnet), integrations, audit status, core token utilities, and post-sale listing plan (DEX/CEX symbols and timing). Add links to docs, GitHub, and the verified token contract on Mosaic Chain (or migration instructions, if applicable).

#### Submitting team info & documents

Provide names, roles, and relevant experience for the founding team. Use the same identities as in KYC to avoid confusion. Upload:

* Whitepaper (MiCA-structured ToC)
* Fundraising contract audit attestation
* Token contract address on Mosaic Chain (or migration plan)
* Marketing plan (timing, channels, disclaimers)
* Contact email/PGP (optional) and official links (site, docs, socials)


---

# 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://mosaic-9.gitbook.io/mosaic-launchpad/for-projects-launching-on-mosaic/project-profile-setup.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.