Drayker dknowledge.drayker.org
Knowledge base

Dknowledge

Knowledge with sources, context and a path to correction. Dknowledge connects the papers, architecture, decisions and evidence of Drayker. Its longer-term design links public, project and personal knowledge under distinct access and provenance rules.

Current orientation

This page separates Drayker’s current public operating surfaces from its longer-term architecture and historical plans. It is intentionally not an internal roadmap, backlog or assignment board.

Available now

Architecture under development

Dk, BSDK, Dk Network, Living Cryptography, OSDK, UID, PAP, Dk Academy, Stations, Value Unit, Distributed Support, Open Science, DFM/DFMP, Meta DFM, DAF, Advices, DFMPProject and the Emergence Initiative remain at different levels of documentation and specification. Their repository contracts in .drayker/component.yml state the evidence and limits for each component.

Dk Global, Dk Personal and Dk Local are connected architectural scopes, not three currently deployed products:

The precise interfaces and operational implementations among them are still to be specified and tested.

Global Dknowledge is intended to be an operational ontology, not merely a document archive: entities, events, concepts, projects, decisions, capabilities, resources and their relations remain connected to provenance. Permissions remain contextual. Auditability requires that an authorized decision path can be reconstructed; it does not require every underlying fact to be public. The record of a decision keeps the data and rules used, the versions of the components involved, the proposals considered, the authorizations given and the actions executed. Agents’ justifications are checked against these records, without having to reconstruct the model. Permissions fall into five classes: personal context, private projects, sensitive research, critical infrastructure and open knowledge.

Current economic interpretation

Drayker’s proposed internal economy circulates capacity rather than selling it among members. Money, contracts and markets belong to the external interface. Internally, Dk may synthesize need, intention, contextual reputation, trust, project quality, risk, impact and available resources; Dknowledge preserves the reasons and consequences. Inside the space the members’ constitution gives it, Dk Global decides and executes allocations autonomously. Allocations stay open to representation and proposals, and members can make a well-justified veto, which obliges review. The rules themselves are constitutional, changed with Dk Global and within the kernel.

Synthesis alone does not authorize an action. Systemic safeguards — constitutional constraints, security, permissions, integrity, reserves and risk — condition what Dk decides, so the executable decision is the one inside a permitted and safe space. Decisions do not end the loop: effects, refusals and consequences return through members’ personal Dks as new evidence. A well-justified veto obliges review. Every veto carries its grounds, even when its author stays anonymous. It passes through triage and stays in the signed veto chain. A decision can then be maintained, adapted, excepted, suspended or reversed.

The ecosystem papers now contain the current canonical formulations of Distributed Support, Dktron, the economy of capacity, Will to Potential and Autonomous Health. They replace the former one-line placeholders.

The Dk papers now contain Constitutional alignment, the current synthesis of how Dk Global is meant to stay aligned with members as it improves itself, and Supersystems and the choice of intelligence, the forecast and the position Drayker starts from.

Governance now

Drayker is in a founding phase. Public contribution is open, while the GitHub account Hyadhuad holds the explicit bootstrap authority to edit or integrate directly. DAF is an autonomous federation of autonomous units and a basic and primitive form of PAP, implemented now on GitHub (Phase 0): its rules, instruments and public record exist. No unit has been recorded and no assembly has been held yet. Member councils remain proposed architecture.

The versioned governance source is draykerdk/.github.

Reading historical material

The current direction, with the condition each phase must meet, is Direction. Roadmaps and older papers remain public because they preserve the development of the ideas. They are not automatically current commitments, schedules, implementation evidence or promises of funding. Follow links to component repositories and inspect their current evidence contract before making an operational claim.