Connect needs with the capacity to participate and continue.
Distributed Support 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 reputation and productive output.
A practical example
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.
Two connected planes
Members, projects and communities
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 Capacity Floor (Piso Comum de Capacidade): ensuring that every member has unconditional access to the baseline computational cycles, bandwidth, energetic resources, and material support needed to think, learn, and create freely.
The durable direction is broader: a person’s Dk Personal 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.
Network and physical substrate
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 mechanisms shape the design and 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.
- Scarcity-weighted contribution. What you contribute counts for more where it is scarce. The same bandwidth offered where the network is starved is worth more than where it is already plentiful. The incentive follows need, not volume.
The problem it addresses
The ability to contribute depends on practical conditions: time, access, equipment, care and reliable infrastructure. A public invitation alone does not provide them.
Where this stands
The repository publishes the current architectural formulation of Distributed Support and its relation to Dk Personal, PAP, Dknowledge, Dk Network, Stations and the economy of capacity. No support allocation, entitlement, node protocol or member programme is operating today.
Reciprocity must never become a rank of persons. Access to the common capacity floor is an inalienable civilizational baseline, not an earned privilege or reward for obedience. 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; accountable member institutions authorize consequential allocations, inside systemic safeguards.
This repository develops the proposal through public documentation and review. The capabilities described here still require specifications, worked examples and implementation.
Scope
- 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 Dk Personal, PAP, Dknowledge, Academy, Stations and Dk Network
- Explainable contextual synthesis by Dk with accountable member authorization
Not in scope
- 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 intimacy, unverified fixed rates or automatic eligibility as requirements
First functions
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 Dk Personal, 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.
How to contribute
Read CONTRIBUTING.md
and GOVERNANCE.md in
the organization. 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.
Sources of truth
- 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