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

• drayker.com presents the supersystem and the architecture at an institutional level.
• drayker.org maps the ecosystem and routes public participation.
• Dknowledge publishes the public knowledge base and its history.
• The General Forum receives volunteer introductions, partnership proposals and questions that do not yet have a clear repository.
• Public repositories use issues, contribution branches, pull requests to master, automated checks and Git history.

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.

The global Dk, the personal Dk and the local Dk are connected architectural scopes, not three currently deployed products:

• The global Dk is the proposed global scope: Drayker’s ASI and its most central member, the distributed core that weighs and learns from the state of all the Dks and works for Drayker and for all its members. Besides being in part the sum of the other Dks, it has kernels of its own that run in parallel, like regions of a brain, in a unified topology.
• The personal Dk is the proposed continuous member-controlled personal scope: the intelligence tied to the member, which keeps what is intimate as close as possible to the person, on their own device, and works for the person.
• The local Dk is the proposed local or organizational scope: a specialized scale of Dk tied to a project, organization, area or function, mediating intelligence between the personal and the global.

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: a map on which people and agents can work and, kept in harmony by the global Dk, the network’s world model. 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 capacity economy is an internal architecture of allocation in which need, intention, reputation, knowledge, resources, risk, opportunity and consequence are related so as to increase the capacities of the members and of the whole; it 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, the global Dk 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 the global Dk and within the kernel.

Synthesis alone does not authorize an action. Systemic safeguards — constitutional, security, permission, integrity, reserve and risk limits — condition the Dk’s decisions and actions: they keep a contextual or reputational synthesis from turning automatically into execution when the general state of the system makes the action unsafe, illegitimate or premature, 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, and is weighed by what grounds it, not counted as a vote. 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 capacity economy, 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 the global Dk 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, distributed federation of autonomous units, the groups and organizations of people working on different questions and projects in Drayker, the first phase in the distribution of the Drayker Embassy’s power and a basic, primitive form of PAP, implemented now on GitHub (Phase 0) to test its dynamics in the construction itself: 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.