> For the complete documentation index, see [llms.txt](https://arborswap.gitbook.io/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arborswap.gitbook.io/product-docs/curated-ido/curator-guidelines.md).

# Curator Guidelines

## Project Maturity

The project must exhibit a minimum of two months of active development and community engagement endeavors. During this period, the project should have made tangible progress in its development milestones and actively interacted with its community to foster engagement and build relationships. 

### Social Media Presence

The project's social media presence should demonstrate consistent activity for a minimum of two months. This entails regular posting of relevant content, engaging with followers, responding to inquiries, and fostering meaningful interactions within the community. 

### Team Composition

Team composition is essential for the success and sustainability of the project, requiring a minimum of two members. Having a team with diverse skills, expertise, and perspectives enables effective project management, development, and decision-making processes.

<br>


---

# 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://arborswap.gitbook.io/product-docs/curated-ido/curator-guidelines.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.