Connect needs with the capacity to participate and continue.
Distributed Support is a programme and application for supporting members at multiple levels, locally and globally. It seeks to relate needs to material, social, educational, computational, community and other capacities, including distributed infrastructure as one of its fronts, and connects the computing power of the network to direct support for the members' lives: dedicated hardware, physical infrastructure for laboratories, workshops, connection nodes and mutual material support. This repository proposes how material resources, tools, computing capacity and shared places can support members, projects and communities.
The model connects a stated need to available capacity, a contextual allocation decision and an accountable record of how support is used.
Support is intended to expand human possibilities and common capability, with basic support independent of productive output. In Distributed Support, care as a material condition takes shape: each member's needs are linked to material, social, educational and computational means, locally and globally. This support does not depend on each person's luck, and asking for it is a form of cooperation.
A community project might need workspace and equipment while a research task needs cluster time. Each request should be considered in its own material context. This is an illustration of the proposed design.
The rise of superintelligence breaks wage labor as the primary mechanism for distributing survival. When machines produce intellectual and material goods at near-zero marginal cost, tying human dignity to the sale of commoditized hours becomes a mechanism of artificial scarcity and coercion.
Distributed Support specifies the gradual construction of a common floor of possibility: the basics for living, studying and communicating — food, shelter, health, education, information, communication and basic computing capacity — which the network guarantees to every active member, to the extent the infrastructure can sustain it, so that each can think, learn and create freely. The active member is the one who uses Drayker as their base supersystem; someone who has only created a UID and does not use the network is still a member, but an inactive one, until they use it again, and there is no punishment in this. In health, the floor takes the form of a system of its own, Autonomous Health. Anyone can become a member: all it takes is creating their own UID, the unique identity of each member, based on multi-factor biometrics, verified continuously and certified by people at first enrolment; there is no approval step. While the floor does not reach everyone, access depends on an endorsement that works as a queue weighted by context, such as need and urgency, and the floor grows with abundance.
The durable direction is broader: a person's personal Dk can help relate intentions, dreams, studies, experience and projects; PAP can give those intentions an actionable structure; Dknowledge can preserve the context and consequences; and common resources can be directed toward increasing capacity rather than purchasing consumption or status. No operating benefit or income programme exists today.
The substrate uses capacity that already exists — ordinary devices, idle compute and storage, people who keep them running — rather than hardware bought for one centre. Contribution comes in two tiers: authenticated and supervised nodes on the main network, and lighter, identity-free contribution on the secondary one.
Two points are worth stating early:
- Redundancy instead of trust. The same work is computed at several independent points and the results compared, so a wrong or dishonest answer is detected rather than believed. A node that returns faults is audited, and can be removed.
- Contribution and scarcity (open hypothesis). Whether a contribution should weigh by the local scarcity of what it provides, rather than by its volume, is a hypothesis to examine, not a rule. What you contribute earns the reward, the only transferable reputation, which recognizes the contribution of capacity, such as the computation lent to the network, and gives faster or priority access to resources, with no governance weight.
The ability to contribute depends on practical conditions: time, access, equipment, care and reliable infrastructure. A public invitation alone does not provide them.
The repository publishes the current architectural formulation of Distributed Support and its relation to the personal Dk, PAP, Dknowledge, Dk Network, Stations and the capacity economy. Resources from outside the network enter and leave through the treasury and external interface described in Value Unit. No support allocation, entitlement, node protocol or member programme is operating today.
Reciprocity must never become a rank of persons. Access to the common floor belongs to every active member. While the network cannot sustain it for everyone, above all when resources are scarce, access depends on an endorsement, which works more like a queue weighted by context, such as each person's need and urgency, than like an approval as such; at the beginning of the network, contextual reputation helps protect the organism against abuse and prioritize those who have shown integration, cooperation and responsibility. As capacity grows, what once depended on a queue becomes part of the floor, and reputation weighs only on what remains scarce. Time is not instrumentalized: an artist creates, imagines, thinks, debates, observes and lives, and their personal Dk follows all of it as it follows any other life. History, scarcity and need may inform operational project support, but access to common capacity requires transparent member-defined rules; it is not automatic speculative income, a return, a yield or a commercial payment. Dk may synthesize context and propose, inside systemic safeguards. The global Dk decides and executes allocations within the constitution; a well-justified veto by members obliges review.
The floor does not take the place of power, as bread once did; it comes along with it: those who receive it remain represented by their personal Dk, with the veto, the proposal and the exit. The floor covers what is necessary; what is enough beyond it, each member pursues in their own direction.
Being a member is a relationship of rights and duties, which vary with each person's level. Whoever wants to live with only what is necessary has their place. Whoever wants to enjoy more capacity takes on, in the same measure, more commitments to the whole.
This repository develops the proposal through public documentation and review. The capabilities described here still require specifications, worked examples and implementation.
- Human, project and community support
- Projects of life as a connection among intention, formation, participation and support
- A growing common floor as abundance increases
- Project funds and support contexts
- Physical and virtual support nodes
- Scarcity-aware compute, storage, bandwidth and redundancy
- Relationship with the personal Dk, PAP, Dknowledge, Academy, Stations and Dk Network
- Explainable contextual synthesis and allocation by the global Dk on matters outside the constitution, within the space it grants, open to members' well-justified vetoes, which oblige review
- A deployed support network or a commitment of resources
- Employment, compensation, income, universal basic income or guaranteed benefits today
- A score that determines human worth, membership or fundamental rights
- Automatic entitlement produced by contribution, reputation or a token
- A black-box Dk acting as sovereign owner or allocator of common resources
- Biometric requirements beyond the member's UID, unverified fixed rates or automatic eligibility as requirements
These are concrete and unclaimed. Any of them can be opened as an issue and delivered by one person.
- Separate the human/project support model from the network-substrate model without disconnecting them.
- Specify one small, reviewable project-support experiment using no currency and making every decision reconstructable.
- Define how a project of life relates to the personal Dk, PAP and Dknowledge under consent.
- Model when a scarce resource can move into a common floor.
- Specify a support node and how scarcity, failure, redundancy and maintenance are measured.
Read CONTRIBUTING.md
and GOVERNANCE.md in
draykerdk/.github. In short: open or find an issue, say in the thread that you are taking
it, branch as fn/<issue-number>-<short-name>, and open a pull request against
master. There is no separate review branch.
Participation is voluntary and implies no compensation, employment or future claim.
In the design, ongoing functions receive recognition of cost, responsibility and the conditions to stay: an organism that depends indefinitely on the silent sacrifice of a few people loses part of the capacity it claims to want to widen. Today, nothing of this is operating.
- This repository, for what Distributed support is and is not.
.drayker/component.yml. The machine-readable contract, validated on every pull request.- drayker.org/project/dsupport/. The same record inside the portal, with the live board.
- drayker.com/project/dsupport/. The case for it, in plain terms.
Part of Drayker · content under CC BY 4.0