Builder
Comfortable with code, repos, local models. First step: pick a small issue in the ResonantOS repo (look for “help wanted”) and ship an AI-assisted bugfix PR.
The how-to layer
The community’s mission is to turn passive into active, consumers into producers. This page is for everyone standing at that edge: carrying a project, or stuck at “I’d build if only…”. An idea with a named friction is a complete row — that is all it takes to start.
How the community sees its builders
One question, answered with observable evidence: who builds here, and who is about to. The full rules are in the Project Registry and Tiers and Labels.
Watching, reading, learning. Complete and valid where you are.
Could build if the friction were removed. Intent visible, friction named. The community's focus.
Has a row in the Project Registry. Building, not shipped yet.
At least one completed public cycle, with real people on the other side.
Multiple cycles, self-initiated builds, and others who depend on them.
Your track
Comfortable with code, repos, local models. First step: pick a small issue in the ResonantOS repo (look for “help wanted”) and ship an AI-assisted bugfix PR.
You build with AI doing the heavy lifting. First step: have your agent write or improve a README for a ResonantOS repo — and post what you learned.
Artist, writer, philosopher, strategist — vision, not code. First step: read the manifesto, then bring one question or challenge to a community call.
Unsure? Say hi on Discord and lurk a call or two. Watching is contribution here — really.
Matchmaking
The Resonant Co-Op Engine, Sundays: 90-second pitches, then breakout rooms. The fastest way to find collaborators — and the natural exit for the “I’d build if only…” row.
Small beats big. Choice beats assignment. Work happens in small self-organizing teams around bounties with clear scope and reward.
See the Co-Op Engine slotNever joined a call yet? Start from the front door: the checklist, the Welcome Guide, one hello in #introductions.
Start here