DFMP

DFM is the paradigm Drayker’s projects and motions for resolution are built with. It exists to answer one question: how do thousands of people who have never met work on the same problem without a manager standing between them?

The answer is to stop distributing tasks and start distributing functions. Pieces small enough that one person can finish one, and defined enough that the result composes with the rest.

Why this exists

Drayker is a way of working where people keep creating, discovering and learning while intelligence carries the rest, and what results reaches the work that produced it. DFM is the method half: how a problem becomes functions that people who have never met can each finish a piece of.

The argument in full is on the manifesto. The economy page states plainly what contributing here earns and what it does not.

The method

1. Model. The issue is modelled and modularized, with the initial strategy expressed as a Bayesian model. Before any code, what is known, what is assumed, and what would change the strategy are written down.
2. Fragment. The problem is partitioned into small functions.
3. Distribute. Functions are distributed among collaborators through decentralized peer review. Nobody is assigned work. Contributors claim what matches their skill.
4. Review. Ideas are discussed with communities and councils and turned into a comprehensive, widely revised paper. Validation runs alongside development, not after it.
5. Integrate. A contribution is proposed in an issue, developed on its own branch and submitted as a pull request to master. Automated checks and public discussion preserve traceability. During the founding phase, Hyadhuad may also integrate directly under the organization governance policy.

The protocol adapts to different kinds of project, but the logic does not change.

Principles

• Simplicity and cleanliness
• Automation
• Relation and documentation
• Agile development is evolutionary
• Worldwide collaboration
• International community, local emergence

DFMP · the proposal process

DFMP is the path a proposal takes from an idea to a legitimated paper. The protocol has to ensure that papers created from it are self-assessed, validated and re-evaluated. Before entering the approval process, a paper must have been presented to the community through the issues and widely discussed. All goals and purposes must be in line with Drayker.

dfmpp/ holds the proposals themselves.

How it fits the whole

The method is the first layer of the ecosystem, and every other layer runs on it.

Drayker is designed so that thousands of strangers can work on one thing without a manager in the middle: any issue is broken into functions small enough for one person — or one agent — to finish, and the Dk distributes them by profile. The same vocabulary of functions and modules is the language the BSDK base structure is proposed in. Meta DFM formalizes the method itself and the notation its papers use. Validation runs through the councils; the Academy shapes formation to the functions; Dknowledge keeps the papers traceable; and DAF is the governance that the same proposals feed into. The method is the one part genuinely in use today — which is the whole point of starting there.

State of this documentation

The method and the proposal path are written down. DFMP-000, the paper that should specify the proposal process itself, is currently a title and nothing more. Writing it is the most useful thing anyone could contribute here, and it does not require permission. Open an issue with the draft.

Contributing

Open an issue in this repository. Issues small enough for one person to finish carry the open-function label and appear on the board at drayker.org.

Related: dfmpproject (proposing a project through DFM) · metadfmp (modeling the method itself) · dknowledge (papers and roadmap).

Other languages: Português · Español. Both currently behind this English version.

DFMP and DAF describe proposed collaboration and governance architecture. Drayker’s current founding-phase governance is documented in draykerdk/.github, and the work is primarily voluntary. Content licensed CC BY 4.0.