> 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/about-logos-circles/circles-charter.md).

# Circles Charter

### **1. Purpose of Circles**

Circles exist to rebuild civil society by enabling local groups to:

* Build **real community (tribe)**
* Develop **agency (ability to solve problems locally)**
* Execute **winnable civic actions in the real world**

### **2. Core Principle: Winnable Issue Defined Before First Circle**

Every Circle is built around an initial, **pre-defined winnable issue**.

This issue is:

* Identified and designed during **Steward training**
* Prepared in parallel with Circle recruitment and promotion
* Executed in the **first month of Circle activity**

Following the execution of the first issue, the Circle decides as a group what issue to tackle next.

### **3. Definition of a Winnable Issue**

A winnable issue must:

* Be complete in **≤ 3 months total lifecycle**
* Have visible, local impact
* Be executable by volunteers (low dependency on institutions)
* Produce a measurable outcome

#### Examples (link to Issue buckets):

* Park or street clean-up
* Community safety or lighting improvement
* Local mapping or coordination system
* Small digital tool or workflow for civic coordination
* Physical improvement in partnership with local actors

### **4. Operating Model**

Circles follow a **four-stage execution lifecycle**:

#### **Stage 1 — Steward Training (Pre-Circle)**

The Steward:

* Completes training
* Identifies **one winnable issue**
* Defines:
  * clear problem statement
  * success criteria
  * execution steps
  * required volunteers/resources
* Begins recruitment **in parallel**

Output:

A fully defined, ready-to-execute winnable issue + initial participant pipeline

#### **Stage 2 — Recruitment & Setup (Parallel Phase)**

While the Circle is being formed:

* Steward recruits participants
* Communicates clear mission (“we are doing X”)
* Pre-aligns expectations around execution

Key rule:

Participants join an **action**, not a discussion.

#### **Stage 3 — Circle 1 Execution (Month 1)**

Circle 1 is an execution container.

It includes:

* Alignment on issue plan
* Final coordination
* Volunteer mobilisation
* Execution of the winnable issue

Primary goal:

> Complete or materially deliver the winnable issue within 30 days of Circle launch

#### **Stage 4 — Review & Iteration (Post Month 1)**

After execution:

* Document outcomes (report + media)
* Share publicly on Logos forum
* Evaluate success
* Decide next issue cycle

### **5. Circle Session Types**

Circles operate through two session types:

#### **1. Action Sessions (Core)**

* Volunteer days
* Cleanups
* Field execution
* Direct civic work

#### **2. Execution Planning Sessions (meet-up style)**

* Logistics and coordination
* Resource alignment
* Task breakdown
* Relationship building
* Reflection
* Recruitment

### **6. Funding Model**

#### Circle Stipend

Each active Circle receives a monthly stipend from Logos.

The stipend is intended to support the Circle's mission and gives Stewards the flexibility to decide how it is best used to create local impact.

The stipend may be used for things such as:

* Venue hire
* Food and refreshments
* Travel for Stewards
* Materials or equipment
* Printing (where appropriate)
* Costs associated with delivering the Circle's winnable issue
* Donations, supplies, or other direct support for organisations or community partners where this contributes to the Circle's winnable issue

Rather than allocating separate budgets for venue, food, printing, or other categories, Stewards are trusted to determine the best use of the stipend based on their local context and priorities.

#### Funding Timeline

* Logos provides a monthly stipend during a Circle's initial three-month launch period.
* After the launch period, active Circles continue to receive one stipend per quarter, provided they continue meeting the criteria outlined in this charter.
* Stewards are encouraged to make the stipend go as far as possible by seeking community partners, donations, sponsorships, or low-cost meeting formats where appropriate.

#### Funding Conditions

Continued eligibility for the stipend requires:

* Submission of a public report after each Circle, including photos or other evidence of activity (faces may be hidden to respect privacy).
* Completion of the first winnable issue within 30 days of Circle launch.
* Completion of a new winnable issue at least once every three months.
* Regular Circle activity and participation.

#### Hard Rules

If a Circle does not complete a winnable issue within its three-month lifecycle, stipend payments will be paused until the Circle returns to good standing.

If a Circle does not meet for three consecutive months, the Steward will be offboarded and the Circle removed from the active programme if there is no other active Circle member willing to step up to Steward.

### **7. Reporting Requirements**

After every Circle:

Must publish a report on Logos forum including:

* Issue being addressed
* Actions taken
* Outcome (or current status)
* Evidence (photos, documentation, outputs)
* Next steps

No report = no continued funding eligibility.

### **8. Steward Responsibilities**

Stewards are responsible for:

* Designing the initial winnable issue during training
* Facilitating the discussion to define future winnable issues with Circle attendees
* Ensuring execution happens within timeline
* Coordinating logistics and sessions
* Publishing Circle reports

### **9. Support Model Shift**

To make Circles successful under this model, support shifts from “meetup funding” to “execution enablement”.

#### Support systems:

#### 1. Issue Design Templates

Pre-built winnable issue formats (the “issue buckets” including:

* cleanup day
* mapping exercise
* infrastructure micro-fixes
* civic coordination tools

#### 2. Steward Training System

Focus on:

* defining executable issues
* building simple action plans
* ongoing training through courses on the e-learning platform

#### 3. Steward coaching layer

* weekly office hours
* troubleshooting execution issues
* helping refine issue scope

#### 4. Recognition + visibility loop

* highlight successful Circles publicly
* create visibility for Stewards across the global network
* reinforce success culture through storytelling

#### **5. Fundraising Support**

Support for Circles to raise additional funding and increase the visibility of local initiatives, including:

* creating a fundraising page on Fundbrave
* promotion through Logos X channels
* feature posts on the Logos blog
* dedicated X posts
* opportunities to present campaigns in Logos X Spaces
* local PR and media outreach support where appropriate

### **10. Success Metrics**

* ≥1 winnable issue completed per Circle in Month 1
* New winnable issues executed every three months
* High-quality public reporting after each Circle (forum and X)
* Repeatable Steward onboarding → execution pipeline established

***

## **Future Direction (Charter V2)**

The charter above defines the operating model for the next **4–6 months** as we validate the Circles movement and establish repeatable patterns for successful local organising.

Following this initial phase, the programme will evolve to include additional layers of economic coordination, governance and network participation.

The following features are planned for **Version 2**.

### **1. Savings & Mutual Aid**

Every Circle will operate a local savings and mutual aid fund.

This fund forms the economic foundation of the Circle by encouraging financial discipline, building trust between members and creating local capacity for community investment.

Funds accumulated through the savings circle may be used to:

* support local community initiatives
* provide mutual aid to members where appropriate
* act as collateral for future access to on-chain lending markets

Savings circles will become a core part of every Circle's long-term operating model.

### **2. Expanded Stewardship Structure**

As Circles mature, leadership responsibilities will be distributed across a number of formal officer roles.

Every Circle will be expected to appoint, at minimum, the following officers.

| **Officer**   | **Function**                                                                                                                                                   |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Steward**   | Runs the Circle, facilitates meetings, coordinates activities and serves as the primary point of contact with regional support.                                |
| **Treasurer** | Manages the Circle's savings fund and finances, records contributions and provides financial updates. Withdrawals require dual authorisation with the Steward. |
| **Secretary** | Records meeting minutes, maintains membership records, tracks attendance, submits reports and manages Circle communications.                                   |
| **Warden**    | Maintains standards and safeguarding, ensures the code of conduct is followed, manages disputes where appropriate and escalates serious issues when necessary. |

Distributing responsibilities across multiple officers increases resilience, accountability and continuity as Circles grow.

### **3. Every Circle Runs a Logos Node**

In Version 2, each Circle will be encouraged to operate its own Logos node.

Running a node serves three purposes.

#### Practical

Each node strengthens the decentralisation, resilience and sovereignty of the Logos network.

Every Circle becomes an active part of the network's infrastructure.

#### Symbolic

The node becomes the Circle's shared centre of coordination.

Rather than organising around an individual leader, the Circle organises around its contribution to the network itself.

#### Economic

Node operators receive staking rewards which can provide a sustainable source of funding for Circle activities over time.

#### Accessibility

Nodes are designed to run on inexpensive, low-power hardware and should require minimal technical expertise to operate with the appropriate tooling and documentation.

### **4. Long-Term Vision**

Over time, Circles will evolve beyond meetup groups into self-sustaining local institutions.

Each Circle will combine:

* strong local community
* regular civic action
* shared economic coordination
* distributed leadership
* ownership of network infrastructure

Together, these create a durable foundation for rebuilding civil society through locally organised, globally connected communities.


---

# 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://circles.logos.co/readme/about-logos-circles/circles-charter.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.
