# Step 1

**Project Name** — Your product's name. 

**Brief Description (500)** —  What it is, what it does, why it matters. Think of this as the one paragraph a judge reads before deciding whether to dig deeper.

**Project Website** — A live URL if you have one. A landing page, GitHub, etc.

**What are you building, and who is it for? (1000)** — Get specific. Describe the product, the core mechanic, and the exact user you're building for. 

**Why did you decide to build this, and why build it now? (1000)** — This is where you show conviction. What's the problem you've personally felt or observed? Why is now the right moment — market timing, infrastructure maturity, regulatory shift, whatever your angle is. This is the section that separates missionaries from tourists.

**Technologies / Tools** — List your stack honestly. Frontend, backend, blockchain layer, any AI tooling, dev tools, SDKs. Don't oversell — judges are technical.

**Category** — Pick the one that fits best even if you span several. Hedging across too many categories reads as unfocused. Own your primary lane


---

# 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://xforce-decentralised-protocols.gitbook.io/ship-with-tino-colosseum-edition/documentation/getting-started/submitting-your-project/step-1.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.