Logos Circles solve winnable local problems: pop-up health clinics, financial literacy, community gardens, cleanups, civic-tech. Each Circle is run by a volunteer Steward. The Movement team supplies training, tools, and 1:1 support so those Circles compound into a network of mutual aid. The regional lead is the operating layer that makes that scale: mentor Stewards, standardise briefs and reporting, and give the movement one clean view of what is working across cities. Below: what Logos is, what a Circle does, where it sits among civic-organising models, the JD mapped to a plan, and the operating model I would run.
A Circle lives or dies on one thing: whether its volunteer Steward has a clear next action and feels supported. The Movement already supplies the mission, the tools, and the training. What breaks at scale is the middle layer: briefs that vary Circle to Circle, reporting that arrives late or not at all, and new Stewards who stall in their first month. The regional lead owns that middle layer. My plan is to give every Steward the same repeatable scoping-to-report loop, run a light-touch mentoring cadence so no new Circle goes dark in week one, and roll regional metrics up into one view the movement can act on. The rest of this page reads the landscape, then lays out that loop.
Logos is the movement building what it calls the Parallel: a decentralised, privacy-preserving stack for civil society. It has two halves. The technology half is the free, censorship-resistant infrastructure of the wider IFT ecosystem: Waku for messaging, Codex for storage, Nomos for consensus, and Status as the flagship app. The movement half is Circles: local groups taking direct action on problems that existing institutions have overlooked. This role sits on the movement half. The through-line between them is parallel organising: build the alternative rather than wait for the incumbent to fix itself.
Read the movement in Logos's own words: logos.co/movement and Circles: tackling winnable issues with grassroots action.
A Circle is a small local group and a Steward who runs it. It picks a winnable issue, scopes a project, delivers it, and reports the outcome. The regional lead sits alongside that loop and makes it repeatable across every Circle in the region.
Circles borrow from several existing models and combine them in a way none does alone: the local-chapter structure of service clubs, the direct action of mutual-aid networks, and the sovereignty thesis of network-state projects. Reading those neighbours is how the regional lead knows which playbooks to borrow and which failure modes to avoid.
| Model | How they organise | What Circles borrow | Where Circles differ |
|---|---|---|---|
| Service clubs Rotary, Kiwanis, Lions | Chartered local chapters, a member cadence, a global body that sets format and reporting. | The chapter model and the standard brief. Proof that a light global format lets thousands of local groups run themselves. | Circles pick issues bottom-up and lean on shared digital tools rather than a fixed rulebook and dues. |
| Mutual-aid networks post-2020 neighbourhood pods | Fast, leaderless, hyper-local. Spreadsheets and group chats, direct help with no gatekeeper. | Speed and the winnable-issue instinct: solve the concrete thing in front of you now. | Circles add continuity and reporting so wins compound instead of fading when the crisis passes. |
| Network-state projects Praxis, Cabin, Zuzalu-style | Start from shared values and crowdfunded physical nodes, aiming at eventual sovereignty. | The Parallel Society thesis and the privacy-preserving tech stack underneath it. | Circles start from doing useful local work first, so credibility is earned on the ground before the bigger claim. |
| Web3 public-goods Gitcoin, Giveth grants | Fund impact through quadratic funding and grant rounds, mostly online and capital-first. | Civic-tech for local fundraising and a crypto-native way to move money to Circles. | Circles are people-first and in-person; funding serves the fieldwork rather than being the product. |
Service clubs and mutual-aid pods are the closest operational analogues; the JD itself names Kiwanis and community gardens. Network-state framing is from Logos's own Build the Parallel thesis.
Grassroots movements rarely die from lack of energy. They die from friction in the middle: a new Steward who cannot find the brief, a great project nobody outside the city ever hears about, reporting that is a different shape from every other Circle so the movement cannot tell what is working. Left alone, each Circle reinvents the wheel and the network never compounds.
One scoping-to-report loop every Steward uses. A mentoring cadence light enough that a part-time lead can keep every new Circle moving in its first month. One monthly regional view the movement can act on. The measure of the job is simple: fewer stalled Circles, faster time from idea to first project, and reports that arrive on time in a shape you can compare across cities.
This is the same shape as running a community-health ambassador programme and mentoring a team of local advocates: a shared format, a light cadence that keeps volunteers active, and clean reporting rolled up for the people funding the work. The specific mechanics and track record are in my application materials rather than on this homework page.
| JD duty | How I would run it | First move |
|---|---|---|
| Help organisers scope and execute community-impact projects | Give every Steward one project-scoping brief: issue, outcome, people, resources, date, and the single metric that proves it worked. Same template region-wide so I can help fast and compare later. | Week 1 |
| Mentor new local Circle Stewards using provided formats | A 30-minute onboarding 1:1 in a new Steward's first week, then a weekly open office hour. The goal is that no new Circle goes dark before its first project ships. | Week 1 |
| Manage documentation, briefs, and reporting for promotion | Keep one living folder of briefs and outcomes per Circle, written so comms can lift a story straight into a post without chasing the Steward for details. | Week 2 |
| Aggregate regional reporting and metrics to improve coordination | One monthly regional roll-up from a fixed template: active Circles, projects shipped, people reached, and at-risk Circles flagged early so support arrives before they stall. | Month 1 |
| Serve as the primary liaison for logistical support | Be the single, predictable point of contact for Stewards: one channel, a clear response window, and recurring blockers turned into shared playbooks so the same question is not answered twice. | Week 1 |
| Attend local events to promote Circles and connect participants | Show up, capture contacts, and route each newcomer to the nearest Circle or help them start one. Every event should end with named follow-ups, not a stack of business cards. | Ongoing |
| Produce standardised regular reports on regional progress | Same report, same day each month, same shape. Predictable cadence is what lets the movement trust the numbers and plan against them. | Month 1 |
Treat every new Steward as moving through a simple pipeline, the same way a good onboarding funnel treats a new user. The regional lead's job is to reduce the drop-off between each stage.
A 30-minute welcome 1:1 within the first week: what a Circle is, the winnable-issue idea, the scoping brief, and where to reach me. Drop-off here means someone signed up on impulse and never started.
Help them pick one winnable issue and fill the brief. The bar is deliberately low: something local they can ship in weeks, not a grand plan that never starts.
Unblock logistics, share a playbook from a Circle that has done something similar, and check in once before the date. First win is what makes a Steward stay.
Capture the outcome in the shared format while it is fresh: what happened, who it reached, one photo, one number. This is the raw material for promotion and the monthly roll-up.
A Circle that has shipped and reported once can now recruit from the people it reached and pick its next issue. At this point the Steward needs less of my time, which frees me for the next new Circle.
A part-time lead cannot watch every Circle by hand, so I would run a lightweight health signal off the reporting that already exists. It answers one question for the movement: which Circles are healthy, which are at risk, and where should support go this month.
| Signal | What it tells me | Healthy | At risk |
|---|---|---|---|
| Time to first project | Whether onboarding and scoping are working for new Stewards. | < 30 days | stalled |
| Projects shipped / quarter | Whether a Circle is actually active rather than nominal. | 1+ | 0 |
| Reporting on time | Whether I can trust the roll-up and comms can promote the work. | on cadence | silent |
| People reached | The real-world impact number, and the recruiting pool for next time. | growing | flat |
| Steward responsiveness | Early warning of burnout or a Circle about to go quiet. | replies | gone dark |
The monthly regional report is one page from a fixed template: active Circles, projects shipped, people reached, new Stewards onboarded, and a short list of at-risk Circles with the specific support each needs. Same shape every month so the movement can compare across regions and act.
This is an independent homework page I built for my application. It is not affiliated with, endorsed by, or operated by Logos. All figures and framing are from public sources as of mid-2026.