Dknowledger· drayker.org
drayker.org ↗

PUBLIC KNOWLEDGE LAYER · SOURCE-FIRST

Knowledge that
keeps its source.

Dknowledger connects Drayker's current orientation, architecture, papers, decisions and evidence. The public site is operational today; the wider distributed knowledge system remains a direction under development.

PUBLIC REPOSITORY CC0 KNOWLEDGE FOUNDING PHASE
PUBLIC MEMORYREASONING → SOURCE

A wiki stores pages. Dknowledger is designed as a network: requirements → motions → decisions → evidence, with every claim linked back to where it came from.

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.

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.

LOADING SOURCE TREE

Reading data/catalog.json

03 · DESIGNED NEXT

From documents
to connected knowledge.

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.

01REQUIREMENT

A property the system must preserve.

02MOTION

A proposed answer argued in public.

03DECISION

The issue, review or merge that changed it.

04EVIDENCE

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.

Dknowledger 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.