What is delivered
One motion for resolution, published in docs/, on a concrete part of the base structure — how a function is described, how modules compose, or how the structure is meant to evolve without discarding what works.
Why it is needed
This repository is described as the place where motions for resolution on the kernel's base structure live. None are published. One worked example would show what a motion looks like here and unblock everyone who would write the second. Drayker holds earlier architectural work on the base structure that has never been published — consolidating it into a motion is a legitimate way to do this.
Where to start
The ground rule is published and binding: only the requirements of Dk and the Drayker platform are final. A motion argues for a solution to those requirements; it does not redefine them.
Prior material
Drayker has earlier work on this subject in its own knowledge base — drafts, mostly in Portuguese, written before the public repositories took their current shape. It is not published yet. If you take this function, say so in the thread and the relevant material will be published alongside it, so you are consolidating and arguing with existing thinking rather than starting from a blank page.
This is an open function: small enough for one person to finish, defined enough that the result composes with the rest. Claim it in this thread before starting so two people do not carry the same function, and deliver through a pull request to master. It appears on the board at https://drayker.org/#org/fn
What is delivered
One motion for resolution, published in
docs/, on a concrete part of the base structure — how a function is described, how modules compose, or how the structure is meant to evolve without discarding what works.Why it is needed
This repository is described as the place where motions for resolution on the kernel's base structure live. None are published. One worked example would show what a motion looks like here and unblock everyone who would write the second. Drayker holds earlier architectural work on the base structure that has never been published — consolidating it into a motion is a legitimate way to do this.
Where to start
The ground rule is published and binding: only the requirements of Dk and the Drayker platform are final. A motion argues for a solution to those requirements; it does not redefine them.
Prior material
Drayker has earlier work on this subject in its own knowledge base — drafts, mostly in Portuguese, written before the public repositories took their current shape. It is not published yet. If you take this function, say so in the thread and the relevant material will be published alongside it, so you are consolidating and arguing with existing thinking rather than starting from a blank page.
This is an open function: small enough for one person to finish, defined enough that the result composes with the rest. Claim it in this thread before starting so two people do not carry the same function, and deliver through a pull request to
master. It appears on the board at https://drayker.org/#org/fn