# Build The Future

### <mark style="color:purple;">Build the Truth with Zeitgeist</mark> <a href="#benefit-to-zeitgeist" id="benefit-to-zeitgeist"></a>

Build the Future is a community campaign aimed at empowering our community to drive the growth and development of our decentralized, blockchain-based prediction market protocol.

As you know, Zeitgeist is built on a foundation of transparency, collaboration, and community involvement. This new campaign will allow members of our community to propose a project with specific objectives and key results (OKRs), and to receive rewards for the completion of these OKRs.

We believe that this is a unique opportunity for members of our community to demonstrate their passion and commitment to Zeitgeist, while also having a tangible impact on the growth and success of the protocol. Whether you are a developer, marketer, designer, or simply a passionate advocate for blockchain technology, we want to hear from you!

So, if you have a great idea for a project that will help advance Zeitgeist, or if you have a skill that you would like to contribute to a project proposed by someone else, we encourage you to join this campaign today!

To participate, simply follow these steps:

1. Review the guidelines and criteria for project proposals below.
2. Submit your proposal on [<mark style="color:purple;">**Opensquare**</mark>](https://voting.opensquare.io/space/zeitgeist) by filling out the 'Project Proposal Template provided below.
3. Post your Subsquare proposal in the 💸│build-the-future channel, and engage with the community and other participants.
4. If your proposal is selected, work with the community and the Zeitgeist team to bring your project to life!

This is your chance to be a part of the Zeitgeist community, to make a difference, and to be rewarded for your efforts. So, don't wait any longer. Join the campaign today and let's build the future of prediction markets together!

### <mark style="color:purple;">**Project Proposal Template:**</mark>

**Project Title:**

**Introduction:** A brief description of the project, including its purpose, goals, and expected outcomes.

**Project Objectives:**

* A clear and concise list of the specific outcomes you hope to achieve with this project.
* Alignment with Zeitgeist ecosystem objectives.

**Key Results (OKR):**

* Objective:
* Key Result 1: \[Measurable target that supports the objective]
* Key Result 2: \[Measurable target that supports the objective]
* Key Result 3: \[Measurable target that supports the objective]

**Timeline:**

* A timeline that highlights the estimated completion date of Key Results.

**Incentives:**

* Incentive for achieving Key Result 1:
* Incentive for achieving Key Result 2:
* Incentive for achieving Key Result 3:

**Scope of Work:**

* Detailed description of the work to be performed, including any sub-tasks, deliverables, and timelines.
* Any specific requirements or constraints that must be considered.

**Risks and Mitigation Strategies:**

* A list of potential risks that may impact the the proposed project, along with strategies for mitigating those risks.

**Conclusion:**

* A brief summary of the key points covered in the proposal.
* A statement of the overall benefits that will be realized from the project, and why it is important to the organization.

**Appendix (optional):**

* Any additional information, such as references, diagrams, or samples, that may be useful in supporting the proposal.

-


---

# 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://zeitgeist-seer-program.gitbook.io/zeitgeist-seer-program/contribute/building-with-zeitgeist/build-the-future.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.
