ls -la /roles/needed
RESTORE doesn't have a HR department. It doesn't have a payroll system. Some of these roles are compensated through corporate partnerships. Some are rewarded in Sovereign Credits. Some are the kind of work people do because they're alive and capable and the world needs it done. All of them are essential.
38
open roles
12
disciplines
∞
locations — it's P2P
0
bosses
open roles
How compensation works: Roles marked SC are rewarded in Sovereign Credits — the only currency created by verified real-world action. Roles marked Paid are funded through corporate partnerships and city council contracts as they come online. Roles marked Both have a path to paid once the network reaches sustainability. Nobody here is getting rich. That's not the point. The point is building something that lasts.
The most foundational engineering role in the entire project. You are building the network that cannot be shut down. libp2p peer discovery, gossip protocol design, IPFS pinning strategy, Nostr-style signed event relay architecture. This is the spine of RESTORE.
You are not building a startup's backend. You are building infrastructure that should still be running in 50 years regardless of what any company, government, or court decides to do about it. That requires a different kind of engineering discipline — one that prioritises resilience over elegance and survivability over speed.
Phase 1 runs entirely on Cloudflare's edge — Workers, D1, KV, R2. You own this infrastructure, build the API layer, and design the migration path toward full P2P. The bridge between what's launchable now and what's ungovernable long-term.
RESTORE runs in any browser on any device — no app store, no install friction. You build the PWA: the map interface, the agent conversation flows, the mission completion and verification UI, the offline-capable service worker. The game experience lives here.
Phase 2 adds a native-quality PWA wrapper for background GPS, Bluetooth proximity sensing for peer verification, and local LLM inference. You bridge the gap between browser capabilities and what the game actually needs to do in the field.
The three-tier inference architecture — on-device small models, Petals distributed inference, aligned entity backbone — is the engineering challenge that takes RESTORE from Anthropic-API-dependent to fully sovereign. You make this work reliably at scale.
RESTORE's goal is zero external API dependency for routine agent calls within three years. This is technically achievable. Getting there requires someone who understands the trade-offs between model quality, latency, cost, and network resilience — and can make pragmatic decisions at each step of the transition.
The six self agents and the world agent system are only as good as their prompts. You design, test, and iterate the prompts that determine whether the Body Agent actually changes how someone eats, or whether it just sounds good. Requires deep understanding of both LLM behaviour and human psychology.
The SC economy is only trustworthy if gaming it is hard. You design and maintain the protocol-level anomaly detection agents that monitor SC creation velocity, Sybil patterns, and verification quality — and surface findings to the community for governance review.
Every city RESTORE launches in needs someone physically present to seed the first world agents, recruit the first players, connect the first corporate partners, and make sure the game is grounded in real local knowledge. This is the most essential non-technical role in the project.
The network isn't a platform you build and people join. It's a community you show up for, every week, in person. City Node Coordinators are the proof that RESTORE is real — that there are actual humans doing actual things in actual places. Without you, it's just a whitepaper.
Stewards are the community's backbone — verifying missions, voting in governance, serving in emergency patch multi-sigs, nominating new world agents. You design and run the programme that turns engaged players into trusted Stewards, and trusted Stewards into community leaders.
The Body Agent's nutritional framework must be grounded in the best available science, not in industry-funded guidelines. You ensure the protocol reflects evolutionary biology, metabolic research, and clinical evidence — and that the missions it generates are achievable, evidence-based, and genuinely transformative.
The Body Agent will be talking to millions of people about what they eat. That is an enormous responsibility. The framework must be honest about what the evidence shows, transparent about where it disagrees with mainstream guidelines and why, and designed to help people track their own outcomes rather than just accept the protocol on faith.
The Freedom Agent talks to people about their dependencies. Some of those people are in genuine distress. The protocol must be grounded in actual behaviour change science, harm reduction principles, and clinical reality — not motivational platitudes. You make sure the agent helps rather than harms.
You design and oversee the installation of community solar and battery nodes. You understand second-life EV battery preparation and repurposing for stationary storage. You know which regulations are relevant in which jurisdictions and how to navigate them. You make the energy sovereignty pathway real in the physical world.
Every solar panel installed, every second-life battery commissioned, every household that stops writing a cheque to a utility every month is a proof point. This role produces the most visible, tangible evidence that RESTORE works. You are building infrastructure that will still be running when you're old.
The highest-SC advocacy missions require someone who can actually show up — at planning meetings, at council consultations, at community energy forums. You coordinate the players who take on advocacy missions and translate regulatory wins into network infrastructure upgrades.
Direct relationships between RESTORE communities and local farmers are the food sovereignty pathway's end goal. You build those relationships, onboard farmers to the network, design the community food store model, and create the mission sequences that connect players to real local food systems.
The one-person-one-vote governance protocol is the most politically important design decision in the project. You stress-test it, red-team it, refine it — and propose changes through the very governance system you are designing. You understand both the theory of decentralised governance and the history of how it has failed.
Every decentralised governance system that has preceded RESTORE has eventually been captured — by whales, by insiders, by the tyranny of structurelessness, or by simple voter apathy. Your job is to understand each failure mode and design against it. Not to create a perfect system — there is no perfect system — but to create one that is honest about its limitations and builds in the mechanisms to correct them over time.
Corporate partnerships are how RESTORE gets resourced without charging players. You understand the ESG landscape, the CSR budget cycle, and how to make the case that contributing hardware, vehicles, and funds to RESTORE produces better verified impact data than any alternative. You close deals that fund the commons.
You are not a salesperson for a product. You are making the case that generosity is rational — that Toyota gets more from donating second-life batteries than from recycling them quietly, that Dell gets more from donating laptops than from writing a cheque to a charity nobody has heard of. The pitch is grounded in numbers and evidence. Your job is to find the people inside these organisations who already believe this and give them the ammunition to make the case internally.
The SC credit profile is the most important financial innovation in the project — a better signal than traditional credit scoring for the population most underserved by traditional finance. You find the banks and credit unions that understand this and build the partnerships that connect Sovereign Credits to real financial access.
Missions are the game. They must be specific, achievable, genuinely useful, and written in the voice of an agent who cares deeply about the person they're talking to. You write missions that change behaviour — not because they're clever, but because they're real.
The most powerful proof that RESTORE works is a person transformed. The second most powerful is a community changed. You find those stories, film them with honesty, and put them in front of the world. Not polished corporate content. Raw, real, on a phone if that's what it takes.
The SC ledger is only credible if it cannot be gamed. The P2P network is only ungovernable if it cannot be captured. You break things before adversaries do — and you do it publicly, because that is what an open-source network demands of its security researchers.
Everything you find gets published. Fixes go through the governance process. There are no private disclosures that get quietly patched — the community needs to know what was vulnerable and why, because that is the only way to build genuine trust in infrastructure that cannot rely on institutional authority to back it up.
$ grep -r "[filter]" /roles/ — no results found
why contribute
01 —
P2P, open source, public domain. No company to acquire. No server to shut down. No CEO to bribe. What you build here should still be running when your grandchildren are old enough to use it.
02 —
Governance by community vote. Protocol changes require consensus. Your contributions go through the same open process as everyone else's. No sprint planning from a product manager. No OKRs from a VP.
03 —
Every commit is public. Every governance vote is on-chain. Every SC earned for your contributions is a verifiable record of what you actually did. Your portfolio is the ledger.
04 —
Human sovereignty across food, energy, mind, body, community, and purpose is not a utopian fantasy. It is a technical and organisational problem. Every role on this page solves a specific, well-defined part of it.
05 —
Sovereign Credits are not a promise. They are a public record of verified contribution that accumulates over time, unlocks real community resources, and provides the financial identity that traditional credit scoring cannot see.
06 —
We are at the moment when AI either becomes an instrument of liberation or an instrument of tighter control. The people building RESTORE have decided which side of that they want to be on. This is the work that answers that question with action, not opinion.
RESTORE is mobile-first. The app is the product. We need someone who builds native-feeling mobile apps with React Native or Flutter and cares about performance at the architecture level — shared context layers, deterministic routing, background compute scheduling, BLE integration. The app must feel as fast as any top-tier social app. All sovereignty infrastructure runs silently underneath. You make that possible.
The social layer, community hex pages, encrypted DMs, and Proof of Action feed all run on Nostr. We need someone who knows the NIPs — NIP-01, NIP-44 encrypted messaging, NIP-65 relay lists — and can design the RESTORE-specific event schema for missions, SC transactions, and governance votes. If you've built something on Nostr and care about genuinely decentralised communication, this is the role.
RESTORE launches city by city. The first city needs 200 real people doing real missions within 30 days. A Steward makes that happen. You personally onboard 20–30 players, BLE-handshake with each of them to establish their personhood verification, run one community event per month, and seed your local hex feed with Proof of Action content. This is not a tech role. It is a people role. The network is built one real interaction at a time. You are the proof that RESTORE is real.
open application
The list above is what we know we need. There is certainly much more. If you see where you fit — or where something is missing — tell us.
community
Join the SudoSupport Discord
Connect with the sudosupport.consulting community — builders, local coordinators, and early network members.