Contribute
This is bigger than one person. There are real ways to help.
Resonant Constructs is a small organization with ambitions larger than its current size. The work needs contributors and maintainers, not just customers. If any of the roles below fit you, the door is open.
Read the philosophy and the ThreadSpace concept first. The position matters more than the implementation. We are looking for people who can hold the position with us over time.
Resonant Constructs is also a corporation. It can pay salaries, accept contracts, and operate as a business. The movement framing and the corporate framing are both honest. We are not asking contributors to pretend otherwise.
Maintainers
Stewardship of the source repositories. Review PRs, triage issues, maintain release discipline, keep docs honest.
What we are asking for
Time and judgment, not just code
Comfort with evidence-first release posture
Willingness to hold the line on scope
Contributors
Anyone shipping code, fixes, integrations, tests, or examples. We are small. Any reliable contributor matters.
What we are asking for
Pick an issue, leave a comment, send a PR
Read the README and architecture decisions before assuming
Prefer small, reviewable changes
Researchers
Investigation in identity portability, transport independence, local inference, neighborhood networks, schema exchange, or related questions.
What we are asking for
Concrete artifacts over position papers
Honest about what is implemented vs. hypothesized
Open to long-term collaboration, not just one-off publications
Node operators
People willing to run a Node in the wild: a Raspberry Pi in a closet, a home server, a phone acting as a relay, a Pi in a neighborhood.
What we are asking for
Comfort with basic Linux
Willingness to share what worked and what broke
Patience with early software
Documentation writers
The strongest contribution to a project like this is making it understandable. Tutorials, examples, translations, comparative pieces.
What we are asking for
Read the code, write in plain language
Find the gap between what is documented and what newcomers actually need
Maintain what you write
Testers
Trying releases, finding rough edges, writing reproducible bug reports. The discipline that keeps a project honest.
What we are asking for
Curiosity about behavior, not just happy-path validation
Specific reproduction steps
Tolerance for early software
Community organizers
Local meetups, study groups, neighborhood pilots. The work that turns a project into a movement.
What we are asking for
Patience with people who arrive skeptical
Willingness to host a local conversation
Read the philosophy before convening others
Supporters
Funding, amplification, introduction to people who can help. Sometimes the most useful thing is opening a door.
What we are asking for
Honest about why you are interested
Comfort with the position, not just the product
Long-term thinking
The simplest path is opening an issue or a discussion on the relevant source repository. If you are not sure where to start, send a brief note describing what you want to contribute and the repository you would be working in. We read everything that arrives; we cannot promise to respond to everything.
For Codexify specifically, the development conversation lives on codexify.space. For Resonant Constructs organizational questions, including ThreadSpace research and stewardship of the public canon, use the GitHub organization that hosts this site.