Open call · contribute
Six roles, and the first task in each is already written.
Day one is the same whichever one you pick: clone the repository, install the daemon, run its test suite, start a node against a throwaway data directory, and curl its status endpoint. Then you take the task at the end of your role's document.
The model runs on your own machine and learns from your own files. What peers are built to exchange is a compact weight-delta — a genome — not the files. No node has yet exchanged one with a node on another machine.
AGPL-3.0 Developer preview One operator
Before you spend time here
The acceptance rule was written before the run. The run did not clear it.
The hypothesis: pooling weight deltas across nodes produces a model better at cross-domain tasks than the best single specialist, and than a generalist trained on the union of the same data. The rule below is pre-registered, the artifact it decided is committed, and the verdict it returned is a negative.
The central claim not confirmed
It has been measured, at a real model size, on a held-out task, and it did not hold. Not a run too small to tell — a clean negative. The numbers and the artifact behind them are held back with the rest of the research until release. That is the open question this project is for, and it is stated here because a person deciding whether to work on it should know what they would be working on.
Where the work is
Every command in these documents was run before it was written down.
One document per role, in the repository under
docs/onboarding/ — on the working branch, not yet
merged to main. The outputs quoted in them are real ones,
and each document ends with a glossary, because the vocabulary is the
real barrier here.
Developers
Backend and systems. The daemon is one Python process: HTTP API, a binary P2P protocol, a local chain, a ledger, an event bus.
- Touches
- The daemon: HTTP API, peer networking, CLI and economics
- First task
- Two filename bugs in cli/, one of them silent data loss
AI / ML engineers
Genomes, merge operators, the evolution engine, the module protocol and distributed inference.
- Touches
- The daemon’s model and module layers, and the experiment harness
- First task
- Measure the evaluation noise floor and publish it
Security
Venom: the dam, the T5 security tributary, antibody genomes, governance. Names in the protocol do not get renamed.
- Touches
- Security, peer networking and the threat model
- First task
- Repair the Test column of the threat model and add the missing regression tests
Researchers
Run experiments, read artifacts, decide what the evidence supports. Prose-only numbers do not count here.
- Touches
- Experiments, result reports and the English documentation
- First task
- Reproduce the committed negative, then close the artifact gap it depends on
Product & UI
Four separate Flutter applications — dashboard, chat, wallet, developer tools — and this website.
- Touches
- The apps, the wallet and this site
- First task
- Fix two stale empirical claims in www/ and surface the honest state in the dashboard
Community & ecosystem
Onboarding, documentation, licensing, the marketplace and how the project talks about itself in public.
- Touches
- Public documentation, this site, the marketplace and licences
- First task
- Make the front door work: a clone URL that 404s, a test count off by 4×, two dead doc links
How to reach us
Not open yet.
There is no public repository, issue tracker or discussion board today, so there is nowhere to point you. The application form is closed while the Participation Terms are rewritten. This page collects no personal data and runs no scripts of its own.
What happens next
Start small.
- We match your interest to open work.
- We agree on scope and time.
- You take one small, verifiable task.
Access is granted gradually, based on need and demonstrated work. We cannot promise when we will reply.