# Use Cases

## What to Expect

This section is dedicated to proposed use-cases with reference to a technical pallet implementation from the [substrate](https://substrate.io/) framework. 

Some are living in the source code, some are only conceptual. Each idea will vary in its development and is expected to grow in depth as contributors work through them.

### How to Contribute Your Ideas

Have more ideas? Join our [Discord](https://discord.com/invite/jJhp58PFA2) to ask about joining the team!

## Legend

You will see the note blocks as you read through the use cases. They each represent the level of development of the idea into the source code. They are defined as:

{% hint style="success" %}
Stable Deployment. 
{% endhint %}

{% hint style="info" %}
Working in Development.
{% endhint %}

{% hint style="warning" %}
Theory-based Idea. This means it can be implemented but hasn't made it into the production pipeline yet.
{% endhint %}

{% hint style="danger" %}
Abstract Idea: Requires high levels of customization or implementation method is unknown.
{% endhint %}

Alright, let's dive in...


---

# 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://www.build3.network/researchers/use-cases.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.