Dknowledge is the public knowledge layer of Drayker and Dk: the place where current orientation, papers, architecture, decisions, evidence and historical roadmaps remain connected to their sources instead of scattered across repositories.
Single official public site: dknowledge.drayker.org. The main Drayker sites link here instead of maintaining a second public copy of this material.
Its first versions exist to get volunteers and stakeholders into the ecosystem. Over time it is meant to become a structured base for all of Dk's data, sensors, files, oracles, processes and ontologies, across public, federated and private layers — that part is a stated direction, not a running system.
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. Dknowledge is the memory of it: what has been decided, tried, learned and discarded, still attached to its sources.
The argument in full is on the manifesto; the economy page states plainly what contributing here earns and what it does not.
The systemic final form of Dknowledge is described as evolutionary knowledge graphs — a version of the knowledge layer that is more than a graph of linked documents, and more complex than a wiki can be. Requirements, decisions and evidence stay connected by trust derived from evidence rather than from position; the graph evolves with the system, so the memory of the network is not a snapshot but a living structure — the same fractal logic Dk is designed around, applied to knowledge itself. Today Dknowledge is pages, papers and roadmaps connected to their sources. What it becomes is a structure that only exists as the whole.
Each scale of the intelligence carries its own knowledge: Dk Personal is connected to the person's personal Dknowledge, Dk Global to global Dknowledge, and every organization and project has its own Dknowledge in connection with a specialized Dk. Dknowledge is not one repository of everything — it is the pattern repeated at every scale, and the global Dknowledge is the junction of them all.
- Current orientation — what is publicly available now, what remains architecture, and how founding governance works.
- Papers — organised by main project rather than by date or author: Dk, ecosystem, organization.
- Historical roadmap — older structures and planning documents preserved as context, not a current schedule or commitment.
- CONTRIBUTING — how to collaborate.
- Code of conduct.
Main projects sit in priority and time queues; effort and resources treat them as the priority. Projects outside that set can be opened and proposed by any contributor through DFMPProject.
Dknowledge is the connective tissue: Dk is the intelligence, DFM is the method, DAF is the organization — and this is where what they mean, what is being designed and what was decided stay traceable to their sources.
A complex system needs memory that can be followed, not just information that can be stored. That is the whole reason this repository exists.
It is the memory the rest of the ecosystem reads from and writes to. The Dk intelligence draws on it for architecture and decisions. Papers and resolutions from DFMP are documented here. The Academy reads from it and feeds learning back. Evidence from open science and projects in transition from Emergence land here. Even the historical roadmaps are kept — dated, and separated from current work — because the reasoning is worth reading even when the phase has passed.
The most complete documentation in the Drayker ecosystem — start with Current orientation if you are new. It is also the oldest: parts of the roadmap and several papers predate the current shape of the projects, so read dates before treating anything as current.
Open an issue. Issues small enough for one person to finish carry the open-function label and appear on the board at drayker.org. Reading a paper and writing down where it no longer matches reality is a genuinely useful contribution here.
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.