Emergence Initiative

An entry point for ideas whose place is still emerging.

The Emergence Initiative receives questions, studies and proposals that do not yet fit an established component. It helps an unfamiliar contribution find the context in which it can be examined.

An initial discussion can clarify the question, identify related work and establish whether it belongs in an existing proposal path or needs further exploration.

A permeable entry point helps Drayker learn from people and situations outside its current structure.

A practical example

Someone could bring an observation about a local problem, receive help connecting it to existing work and develop a first bounded proposal. This is an illustration of the proposed design.

Why this exists

The Emergence Initiative is the open edge, where someone who has just arrived can start being useful.

The argument in full is on the manifesto. The economy page states plainly what contributing here earns and what it does not.

Why a supersystem needs a permeable border

Not every useful contribution arrives shaped like a core protocol. An idea forced into a category before anyone understands it usually loses whatever made it worth having. So there is one place where “I do not know where this belongs” is a complete and acceptable answer.

Work is documented and discussed here, and routed toward DFM, DAF, Dk or another project once its relation to the ecosystem becomes clear.

What belongs here

• Papers and proposals outside the core models.
• Contributions whose home is not obvious yet.
• Initiatives that follow their own methodology rather than DFM, including campaigns and content made by members. No permission or protocol is needed, only alignment with Drayker’s values, and propagation follows the same rule as everything else: in the open, never by manipulation.
• A place to show an initiative and find people, ideas, help and support for it.
• Suggestions about the initiative itself, including how papers should be published from it.

What does not

Anything that clearly belongs to an existing project. Open it there, so the discussion sits next to the material it concerns.

How it fits the whole

The permeable border of the ecosystem — where work that has not found its home yet can still begin.

Drayker’s main projects are described in Dknowledge and pass through DFMP. Emergence is the counterpart: proposals and contributions outside the core models are welcomed here so that nothing valid is lost for lack of a category. When a contribution finds its real home, it moves to it — a project on the projects platform, a paper into the knowledge base, a discussion into the forum. It is the same principle as the transition layer of the ecosystem: build the real thing with what exists today, on the way to the platform of its own.

A proposal does not have to follow DFM to be heard. Most proposals from outside the method find their place by moving into it, but some reach what the current models do not see, or prove superior and safer than them. Those are tested in parallel as projects, and what is validated is integrated into the system, by the continuous optimization of Dk and by the members’ choice. A mature Drayker has to be able to examine an idea that contradicts its current design.

The route out

A topic is discussed here or on the forum until its place becomes clear. It then gets an owner: the repository it belongs to, found through the routing table of the General Forum, or DFMPProject when it becomes a project of its own. The thread is transferred to the owner with a link, so the discussion that led there stays readable from both sides.

State of this documentation

Minimal, and honestly so: an open edge that over-specifies itself stops being an open edge. The route out above is written in its minimal form.

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.

Drayker is a supersystem in its founding R&D phase, open and primarily volunteer. DAF is an autonomous federation of autonomous units, a basic and primitive form of PAP, implemented now. Current founding governance is documented in draykerdk/.github. Content licensed CC BY 4.0.