{{ heroTitle }}
{{ heroBody }}
One protocol, one kernel, one ecosystem.
Model a problem, break it into small functions, distribute them worldwide through decentralized peer review.
A unified intelligence, organization and computing system: DFM architecture, BSDK coordination, LCrypt security.
A parallel network, a universal identity, a federation without an owner — and everything the volunteers build on top.
Humanity has immense latent capacity. We exist to create the conditions — of organization and action — that unlock it.
This site explains the system. The other one is where you build it.
drayker.org is the volunteers portal: every project and what it is for, the functions open right now, the contribution process, and a guided way in that ends with a track and a first step. Nothing here is a prerequisite for going there.
We can solve problems we believe are impossible.
Drayker starts from a conviction: we can do more with less, evolve faster, and solve problems we have given up on.
None of that is a question of talent or capital. It is a question of conditions — the conditions of organization and of action. Most human effort is lost in coordination: in hierarchies that filter information, in work that is never documented, in decisions nobody can trace, in problems too large for any single team to hold.
Drayker exists to create those conditions — so civilization can build infrastructure, scale up, and act at a level it never could before.
So we started with the method instead of the product. First a specification for collaboration — DFM — which breaks any issue into small individual functions, so that thousands of strangers can work on one thing without a manager in the middle.
Then the systems that method makes possible: a distributed kernel, a parallel network, a universal identity, a federation that manages resources without an owner.
We develop human, collective and artificial intelligence to reach further and see further. We do this for people — for each person. The boundless evolution of humanity is the end; intelligence is the means.
A problem, cut small enough for the world to solve.
Distributed function modularization is the collaboration paradigm behind every Drayker project. It adapts to different domains, but the logic is always the same: model, fragment, distribute, review.
{{ dfmBody }}
{{ dfmNote }}
Self-assessed, validated, re-evaluated.
The protocol ensures that every paper is self-assessed, validated and re-evaluated. Validation walks alongside development — ideas are discussed with communities and councils, then shaped into a detailed, widely revised paper that passes through the DAOs and councils before adoption.
All ideas, goals and purposes must be in line with Drayker.
A paper enters the DFMP process only after being presented, discussed and validated in the community issue threads. Once legitimated, it moves through the community review branch to master. Updates follow the paper's own validation branch — every decision is traceable.
Intelligence, distributed.
Dk is a unified system of intelligence, organization and computing — built from the ground up to be distributed, secure, fail-safe and self-improving.
The same kernel, at three distances from you.
Dk is not one intelligence in one place. It is designed as a personal agent, specialised local agents, and the collective intelligence that federated learning from both is meant to add up to. Learning travels upward; personal context does not.
The collective intelligence: the layer that concentrates the federated learning of every local and personal Dk. Nobody logs into it — it is what the others amount to together, and the reason a lesson learned once does not have to be learned again everywhere.
Each member's own agent, bound to their UID. It works in personal context — what someone is doing, what they are trying to understand about themselves, what to give the day to. It contributes learning upward without handing over the context that produced it.
Agents specialised in a specific project, area or function — the non-deterministic work that cannot be written as a fixed procedure. A local Dk knows its domain deeply and nothing else, and sends what it learns up the same way a personal one does.
All three stand on the same parts: BSDK as the base structure, UID as the identity a personal Dk belongs to, LCrypt as the tunnel between them, Dk Network as the ground they run on, and DFM as the method by which any of it gets proposed and reviewed. None of the three is implemented yet — the architecture is what is open for argument.
A general intelligence is the goal, not the claim: BSDK and DFM are the architecture it is being designed on.
When machines carry the repetitive load, humans are free to do what matters. There will be no shortage of things to do.
Everything that makes it run.
The projects, protocols and structures that carry Drayker forward — and the people building them.
Governance without an owner.
Drayker is organized by the DFMP process; resources are governed by the non-profit DAF. Today we work on GitHub and third-party tools — building the foundation and experience to create our own collaboration platform at scale.
Appearance
Choose how the portal renders for you. The choice is stored on this device and applies to drayker.org and drayker.com alike.
Start your own DAO.
Anyone — a person, a team, a project or an initiative — can create their own DAO and link it to the federation. Over time, DAOs accumulate federative weight and voting power over federation resources and decisions.
Support requests are made only where there is no other alternative: resource efficiency matters here, and the main projects are the priority.
Everything you need to start today.
One portal for the whole collaboration: what each project is for, what is open right now on GitHub, which track fits you, and exactly how work travels from an issue thread to a legitimated paper on master.
Three steps, in any order.
You do not need to know the whole system to contribute to it — that is the entire point of the protocol.
The people currently building it.
Read live from the commit history. Nothing here is anonymous by default: your work stays attributed, reviewable and permanent, in the repository and in the paper it belongs to.
How work travels here.
Issue thread → claim → fork and branch → pull request to the community review branch → peer and council review → legitimated on master. Six steps, written out with the exact commands.
Seven ways in.
Code is one of them. Research, review and translation carry the same weight — a paper nobody reviewed is not legitimated, and a paper nobody translated does not reach the people it was written for.
Every project, and what it is for.
{{ projNote }}
Named in the architecture, no repository yet.
These are parts the system is designed around and nobody has written down. There is nothing to fork — which is exactly why the first page, the first model or the first honest objection counts as much here as code does anywhere else.
Nothing here answers to {{ missingKey }}.
The project may have been renamed, or the page for it has not been written yet — writing one is itself an open function. Every project that does have a page is one click away.
{{ pd.name }}
{{ pd.tagline }}
{{ pd.vision }}
{{ pd.problem }}
{{ pd.state }}
No open issue is listed for this repository right now. Open one: a well-modelled issue is a contribution in itself, and it is how every function on the board started.
Take a function. Any size.
Every issue is fragmented into functions small enough for one person to finish. Pick one, claim it in the thread, deliver it through the community review branch.
From issue thread to master.
The same six steps for every function, in every repository, whatever your track. Nobody assigns work and nobody merges to master directly.
Reading the board.
Labels are the whole coordination layer. If an issue is unlabelled, labelling it correctly is already a contribution.
Still not sure where you fit?
Tell us what you are good at and what you care about. We will point you at functions that match — and nothing stops you from claiming one today anyway.
Everything is written down.
All proposed resolutions presented here are solutions to the requirements of Dk and the Drayker platform — only those requirements are final. These motions illustrate what should be done; the definitive architecture will be structured around optimal solutions developed with metaprogramming intelligent algorithms and research organized through DFMP.
This work is licensed under a Creative Commons Attribution 4.0 International License. Every site is open source.
{{ jLt }}
{{ jLb }}
{{ resTrackTitle }}.
{{ resTrackDesc }}
Each one names, on its own page, exactly what is missing from it. That is where a first contribution lands easiest.
Nothing is open in this track at this exact moment — which is itself an opening. Take one of the gaps above and open the issue yourself; a well-modelled issue is how every function on the board started.
Five layers, seventeen repositories. What you picked is lit; everything else stays visible, because nothing here is closed to you — you can cross layers whenever you want.
Want someone to walk you in?
Optional — everything above is already yours to take. But if you leave a way to reach you, the volunteers council will cut a first function with you and point you at the people already in that track.
Your track went with it. Nothing stops you from claiming a function today — the board does not wait for an answer.