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](https://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. ## 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. 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](https://drayker.org/manifesto/); the [economy page](https://drayker.org/economy/) states plainly what contributing here earns and what it does not. ## What it becomes 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](https://dk.drayker.org) 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. One of the conceptual bases for that pattern is **E.C.H.: Expansion, Complexity and Harmony**. Expansion admits relevant experience, data and knowledge without treating accumulation as the goal. Complexity connects entries to sources, decisions, hypotheses and other relations. Harmony checks coherence and integrity while keeping contradictions visible; it may integrate a new entry, keep alternatives contextualized, or conclude that the previous state must be reconstructed. The cycle repeats at personal, project and global scales. Learning crosses scales in two distinct ways. In **anonymous federated learning**, raw experience stays at its originating instance while patterns or model updates circulate with depersonalized metadata. Global Dknowledge can therefore hold broader context and deeper learned structure without becoming a collection of personal histories; when a pattern is validated independently in other instances, its weight in global learning becomes progressively stronger. In **deliberate contribution**, a person or unit chooses to share knowledge, evidence or narrative under explicit permissions and provenance. Neither route makes private context common property, and the federated route still requires a re-identification threat model before implementation. Dk and Dknowledge remain distinct. Dk coordinates, reasons and proposes actions over the available context. Dknowledge preserves the evolving state, provenance, permissions and decision lines needed to reconstruct what the system knew and why it changed. ## What is here - **[Current orientation](./CURRENT.md)** — what is publicly available now, what remains architecture, and how founding governance works. - **[Papers](./papers)** — organised by main project rather than by date or author: [Dk](./papers/main-projects/dk), [ecosystem](./papers/main-projects/ecosystem), [organization](./papers/main-projects/organization). - **[Historical roadmap](./roadmap)** — older structures and planning documents preserved as context, not a current schedule or commitment. - **[CONTRIBUTING](./CONTRIBUTING.md)** — how to collaborate. - **[Code of conduct](./CODE_OF_CONDUCT.md)**. 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](https://dfmpproject.drayker.org). ## How it fits the whole Dknowledge is the connective tissue: [Dk](https://dk.drayker.org) is the intelligence, [DFM](https://dfmp.drayker.org) is the method, [PAP](https://pap.drayker.org) is the durable environment for projects and applications, and [DAF](https://daf.drayker.org) is a transitional governance experiment — 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](https://dk.drayker.org) intelligence draws on it for architecture and decisions. Papers and resolutions from [DFMP](https://dfmp.drayker.org) are documented here. The [Academy](https://academy.drayker.org) reads from it and feeds learning back. Evidence from [open science](https://science.drayker.org) and projects in transition from [Emergence](https://ei.drayker.org) 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. ## State of this documentation The most complete documentation in the Drayker ecosystem — start with [Current orientation](./CURRENT.md) 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. ## Contributing Open an issue. Issues small enough for one person to finish carry the `open-function` label and appear on the board at [drayker.org](https://drayker.org/fn/). Reading a paper and writing down where it no longer matches reality is a genuinely useful contribution here. Other languages: [Português](./README.PT.md) · [Español](./README.ES.md) — both currently behind this English version. --- [DFMP](https://dfmp.drayker.org) and [DAF](https://daf.drayker.org) describe proposed collaboration and governance architecture. Drayker's current founding-phase governance is documented in [`draykerdk/.github`](https://github.com/draykerdk/.github/blob/master/GOVERNANCE.md), and the work is primarily voluntary.