DAF is the alliance basis between Drayker's DAOs and DACs: a transitional federation scaffold for testing coordination, governance and shared-resource rules while the broader member constitution and PAP mature.
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. DAF is an early organizational experiment inside that direction: a way to make decisions and resource rules inspectable before the durable environment exists.
DAF is not Drayker's final constitution and is not the permanent reason the system has no head office. Functions that prove useful here are expected to migrate into PAP, member governance and specialized councils. DAF may therefore become progressively thinner or functionally dissolve rather than survive for its own sake.
If DAF reaches a phase with a token economy, ICP is only a probable provisional substrate, not a final dependency or the destination of Drayker's infrastructure. That phase is meant to help build and test Drayker's own infrastructure and system inside DAF. When PAP exists at the required maturity, DAF's useful functions and that transitional infrastructure are expected to be absorbed into PAP; DAF dissolves into the durable environment rather than remaining a parallel institution.
The argument in full is on the manifesto. The economy page states plainly what contributing here earns and what it does not.
Anyone, a person, a team, a project or an initiative, can link their own unit to the federation. During this experiment, units may accumulate federative points and voting weight over decisions inside DAF's bounded scope.
The federation's shared interface and public record are maintained in English so every assembly has one auditable reference. A unit may organize around a particular language, region or nationality, and may work internally in that language. It only needs to submit its unit record, claims, requests and assembly evidence to the federation in English. Language or nationality never changes how points are earned or how a vote is weighted.
Weight follows delivered work. It is not appointed, and it cannot be bought. A point records one delivered function, it is non-transferable, and it does not decay. These points are a ledger for the federation experiment: they are not the member's general reputation, do not measure human value and do not automatically determine support, access or resource allocation elsewhere in Drayker.
The mechanics are specified in DAF-000.
The initial DAO is funded by grants and side projects. All support requests must be made in situations where there are no other alternatives. Resource efficiency matters here, and the major projects are the priority.
That rule is published on purpose. A federation that treats its shared resources as a first resort stops being able to fund anything that matters.
It is also enforceable rather than decorative: a request that does not say what was tried first is returned unjudged, and funding is granted one function at a time, each grant evaluated against the evidence of the last.
DAF is an early place where autonomous units can test cooperation without being absorbed into one organization. Projects, councils, initiatives and the volunteers portal can connect through it while its useful functions are learned and transferred to more durable layers.
Contribution is attributable through UID, while federative points remain separate from the broader, contextual reputation model. Dktron and the value-unit family are distinct resource and economic instruments, not another name for those points. Councils can validate proposals; DAF can test limited shared-resource decisions and, provisionally, the infrastructure for a token-economy phase. Drayker has no head office because intelligence, projects, knowledge and member governance are designed to be distributed — not because one transitional federation owns that role forever.
dafp/ holds the proposals that specify the federation.
- DAF-000. The minimal constitution, independent of any platform: participants and units, how a point is earned, how points become voting weight, quorum and majority, how a resource request is judged, penalties and exit.
- DAF-001. Phase 0, the initial version: the federation designed to run on this repository, with no chain and no token, and an explicit account of what is deferred to later phases.
The record itself lives in federation/: unit records, assembly reports, resource requests and the ledger, in plain text under version control, so that any claim about who delivered what can be checked by reading.
The point mechanics and the voting procedure are now specified, as drafts open to argument, and the structure that would hold the record exists. Nothing is running in it: no unit is recorded, no points have been issued, no assembly has been held, and there is no deployed contract. Phase 0 begins at the first assembly that records a real delivery, not at the commit that created the folders.
Several things are still unspecified on purpose. The substrate beyond Phase 0 was identified as ICP (Internet Computer Protocol), but no migration has occurred. The authority of councils, the migration of useful DAF functions into PAP and member governance, and the limits of federative points remain open. Federative points should not be converted wholesale into uid reputation; at most, verified DAF history may become one contextual input among several. These questions are listed in DAF-000 §9.
Open an issue. Issues small enough for one person to finish carry the open-function label and appear on the board at drayker.org.
Run node tools/render-check.js before opening a site change. It exercises the empty, snapshot, malformed-snapshot and offline states without sending any external action.
Related: dfmp (how proposals are validated) · uid (identity and contribution) · advices (councils)
Drayker is a volunteer, non-profit organization. Content licensed CC BY 4.0.