> For the complete documentation index, see [llms.txt](https://circles.logos.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circles.logos.co/readme/for-hacktivists/technical-builds-eligibility-and-review-guide.md).

# Technical Builds: Eligibility & Review Guide

*Companion to the* [*Logos Circles Charter*](https://circles.logos.co/readme/about-logos-circles/circles-charter.md) *focusing on Hacktivists.*

### 1. What This Guide Is For

Logos encourages [Hacktivists](https://circles.logos.co/readme/for-hacktivists/what-is-a-hacktivist.md) to experiment, build tools and develop parallel infrastructure that serves communities.

The Circle stipend supports regular Circle activities and collaboration, whether in person or online. It is not intended to pay developers for building software. To remain eligible, Circles must meet regularly, report their activities and demonstrate progress against agreed outcomes.

Hacktivists can also build independently without applying for Circle funding.

### 2. What Qualifies?

Technical builds must follow one of two routes:

**A. Address shared Circle needs**

Build a solution that at least **three active Circles** confirm they need and intend to use. This can include your own Circle.

* Validate demand through conversations or documented requests.
* Build something reusable and adaptable to different local needs.

*Example: An open-source event registration tool that three Circles want to use.*

**B. Build long-term parallel infrastructure**

Develop broadly reusable infrastructure that can serve communities beyond individual Circles.

* The solution must be designed to run on **Logos Basecamp**.
* If not initially built on Logos, include a plan for how it could use Logos Storage, Messaging and/or Blockchain.
* Focus on shared infrastructure rather than a solution limited to one local use case.

*Example: A Basecamp civic reporting module that communities can adapt for emergencies, infrastructure issues or other local needs.*

Both routes require open-source solutions that others can use and maintain independently.

### 3. What Do We Expect?

**Within 30 days of Circle launch:**

* Submit a short roadmap describing what you're building, why, and the first milestones.
* Include basic technical specifications and evidence of the chosen eligibility route.
* Review the proposal with Logos.

**Every three months:**

* Demonstrate progress against agreed milestones.
* Share a working technical output, such as a prototype, implemented feature or tested component.
* Review progress and next steps with Logos.

Research and planning are part of development, but the first three months should also produce something functional. It doesn't need to be a finished application.

Stewards must also publish a report after every Circle meetup, as outlined in the [Charter](https://circles.logos.co/readme/about-logos-circles/circles-charter.md).

Circles may pursue other projects alongside their funded work. Only the agreed work determines stipend eligibility.

### 4. How Are Projects Evaluated?

Reviews are kept simple and focus on five questions:

1. **Relevance:** Does it address validated Circle needs or contribute meaningful parallel infrastructure?
2. **Reusability:** Can others use or adapt the solution?
3. **Logos alignment:** Does long-term infrastructure have a credible path to Basecamp and the Logos stack?
4. **Feasibility:** Can the team realistically deliver its first milestones?
5. **Progress:** Is there tangible work to demonstrate after three months?

The Movement team at Logos reviews relevance and community needs. The EcoDev team at Logos reviews technical feasibility, architecture and milestones.

Where similar projects already exist, we encourage Hacktivists to collaborate rather than duplicate efforts.

Projects involving sensitive information or vulnerable users may require additional technical and safety review.

### 5. Larger Projects: λ Prizes & RFPs

Some projects require more resources or development time than volunteers can reasonably contribute.

These may be suitable for additional funding through Logos:

* **λ Prizes:** For user-facing applications, where success is demonstrated through adoption.
* **RFPs:** For defined technical work, such as reusable infrastructure or integrations, with agreed deliverables and milestone-based funding.

Hacktivists can help identify these opportunities, define requirements and shape proposals based on real community needs.

Circle funding does not guarantee additional funding through either programme.

[Start here](https://logos.co/get-started) for current opportunities and technical resources.

### 6. Working Together

Hacktivists can work within a local Circle or form a Circle with contributors across different cities. Each funded Circle needs one designated Steward and receives one stipend.

Stewards and Hacktivists are encouraged to share needs, exchange ideas and collaborate across Circles.

**The goal is simple: identify real problems, build useful solutions and share what works.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://circles.logos.co/readme/for-hacktivists/technical-builds-eligibility-and-review-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
