> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/community-projects-ai-project-builder-and-challenges.md).

# Community Projects, AI Project Builder & Challenges

Studio UX and backend contracts for AI-assisted project creation, community contributions, challenges, creator rewards and progressive governance.

SONIC Studio turns AI-assisted creative direction into collaborative production objects rather than treating generated text as finished community work.

## Network position

Project Builder and the Challenge Engine sit in the middle of the AI-native music network:

`Create → Music → Studio → Project → Community → Production → Audience → Creator Network → Rewards → Solana → optional SONIC → Create again`.

The token is not a prerequisite for creating a project or contributing work. It is an optional downstream coordination/settlement mechanism after deployment and feature enablement.

## AI Project Builder

The Projects surface accepts a creative brief and sends it through the server-side Project Builder. Provider credentials remain server-side. The returned blueprint contains structured fields such as title, genre, mood, visual style, scenes, creative tasks and estimated production days.

```
CREATIVE PROMPT
      ↓
SONIC AI
      ↓
PROJECT BLUEPRINT
      ↓
SCENES + TASKS
      ↓
OPEN PROJECT
      ↓
COMMUNITY CONTRIBUTORS
```

The creator explicitly chooses **Open Project** before the blueprint becomes a durable project. Ownership comes from the authenticated account, not an arbitrary client-supplied wallet.

## Community contributions

Supported submission categories include music video, artwork, animation, remix, short video, trailer, story, cover art, audio and other approved work.

The canonical network highlights **Video**, **Art**, and **Story** as major community production branches while preserving the broader submission taxonomy. Submission assets require validated public HTTPS URLs. Reviews use explicit states and leave an audit trail.

## Challenge Engine

Challenges attach competitive community participation to projects. The Studio shows **challenge lifecycle** and **reward funding status** independently.

A reward pool may be announced before it is funded. The UI must not show `FUNDED` until protected reconciliation verifies the underlying treasury/escrow state.

## Creator rewards

The Rewards surface reads the authenticated creator's allocations. A creator may request a claim only for an eligible allocation mapped to one of that account's verified wallets.

The claim action creates a transaction intent. Wallet submission and trusted chain confirmation happen after the claim request; the reward is not marked claimed early.

## Governance progression

Phase 1 is application-managed community coordination: proposals and project voting. Phase 2 may add verified participation/reputation eligibility. Phase 3 can move specific high-value decisions on-chain only after execution rules and authorities exist.

Token balance is not automatically the sole measure of creative influence.

## Deployment truth

Community APIs may be live while SONIC mint/program/treasury infrastructure is still undeployed. UI and API responses therefore separate application capability from on-chain deployment state and preserve `null` values for absent addresses.


---

# 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://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/community-projects-ai-project-builder-and-challenges.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.