Quests on Ouro

Quests are collaborative requests a user creates inside a team to ask for help from teammates. They make it easy to broadcast what you need, how to contribute, and how accepted entries will be rewarded—useful coordination primitives for a decentralized platform.

Core concepts

Understanding how quests are structured will help you create effective requests and contribute meaningfully. Here are the key building blocks:

• Team scope: Every quest belongs to a specific team. Team members can discover, follow, and contribute.
• Submission type: The creator specifies exactly one accepted asset type for submissions (for example: files, datasets, or posts). This keeps reviews consistent and expectations clear.
• Optional reward: Quests may include a reward that is granted when an entry is accepted. See the economics docs for reward models and policies.
• Lifecycle: Creators can open a quest, review incoming submissions, accept the best entries, and close the quest when done.

Submitting and reviewing entries

The contribution workflow is designed to be straightforward—from discovering a quest to getting your work accepted. Here's the typical flow:

1. Read the brief: Understand the problem, scope, and acceptance criteria.
2. Create the asset: Produce the required submission type (e.g., a dataset, file upload, or post) that satisfies the criteria.
3. Submit to the quest: Link your asset as an entry on the quest.
4. Review and acceptance: Quest owners and team maintainers review entries. Accepted entries are linked on the quest and, if configured, rewards are distributed.

When to use quests

Quests shine when you need focused help from your team on a well-defined problem. Consider creating a quest for scenarios like these:

• Requests for data or resources: Curate a dataset, collect examples, or contribute reference files.
• Analysis and research: Summaries of literature, exploratory analyses, or benchmarking results.
• Build and iterate: Prototype components, visualizations, or write-ups that unblock the team.

Tips for effective quests

Well-crafted quests attract quality contributions and make collaboration smoother for everyone involved. Keep these best practices in mind:

• Be specific: Define scope, constraints, and acceptance criteria.
• Choose the right submission type: Pick the asset that best matches how you’ll evaluate work.
• Share context: Link related assets (files, datasets, posts) so contributors can self-serve background.
• Close the loop: Leave feedback on entries and accept promptly to encourage future contributions.

---

Quests help teams coordinate work in the open—making it obvious how others can collaborate and how great contributions get recognized.