A property the system must preserve.
PUBLIC KNOWLEDGE LAYER · SOURCE-FIRST
Knowledge that
keeps its source.
Dknowledge is Drayker's distributed memory. This repository is its single official public surface today; the systemic design repeats at personal, project, local and global scales, each connected to the corresponding scale of Dk.
What has been decided, tried, learned and discarded remains attached to its sources. Personal context stays personal; projects keep their own memory; global Dknowledge is the junction of shared learning rather than one repository that absorbs everything. The wider evolutionary knowledge system remains a direction under development.
PUBLIC REPOSITORY
CC0 KNOWLEDGE
FOUNDING PHASE
PUBLIC MEMORYREASONING → SOURCE
A wiki stores pages. Dknowledge is a memory pattern repeated at every scale: personal → project and local → global junction. Within each scale, requirements → motions → decisions → evidence keep every claim linked to where it came from. This public repository is the visible global source, not a claim to contain every member's context.
01 · ORIENTATION
Read in the right order.
The repository contains current guidance, design proposals and historical material. They stay public for different reasons and should never be read as one status.
01CURRENT
Current orientation
What exists now, what remains architecture and how the founding-phase Git flow works.
Read first → 02PROPOSALSPapers
Requirements and motions grouped by the part of the system they address.
Explore papers → 03HISTORICALRoadmap archive
Older structures kept so the development of the reasoning remains traceable.
Read with dates → 04OPENContribute
Correct a claim, connect a source, fill an empty paper or improve a translation.
Choose an entry point →02 · THE REPOSITORY, VISIBLE
Not a brochure.
A readable source tree.
This inventory is generated from the files committed to the repository. Network data can enrich it, but the page remains useful offline and under API limits.
Reading data/catalog.json…
03 · DESIGNED NEXT
From public documents
to distributed memory.
This model is a public engineering direction, not a deployed graph or governance mechanism. The repository remains the source of truth while the structure is specified and tested.
A proposed answer argued in public.
The issue, review or merge that changed it.
A document, test, deployment or usage record.
IDENTITY
Stable nodes
Requirements, motions, contracts, decisions, terms and records receive durable identities instead of becoming isolated pages.
RELATION
Typed links
answers, depends on, supersedes, evidenced by and translation of make the reasoning traversable.
EVIDENCE
Derived confidence
Confidence should follow verifiable facts — source, review, discussion and replacement — rather than a badge assigned by authority.
PUBLIC / PRIVATE BOUNDARY
The public base is not the private workspace.
Dknowledge publishes material intentionally committed to draykerdk/dknowledge. Private vault content, personal context and agent memory are not copied into this site.
The long-term architecture may span public, federated and private knowledge. Today, only this public repository surface is claimed as operational.
04 · CONTRIBUTE
Improve the map,
and keep the source attached.
The simplest useful contribution is often editorial: identify a historical claim presented as current, connect a paper to evidence, fill one empty document or bring a translation back in sync.