DKWS in Short

DKWS refers to the Draagkrachtwaardestelsel.

In English, DKWS can be understood as The Capacity Layer.

DKWS is the practical capacity layer within the wider field.

Where LPWS helps recognition become visible, DKWS helps clarify what can actually be carried in practice.

DKWS is for situations where contribution, responsibility, Source Space, cost, risk, continuity, Return Flow, Lumen or cooperation need clearer structure.

DKWS does not replace LPWS.

It does not turn every contribution into money.

It does not make Lightpoints into purchasing power.

It does not turn every form of Carrying Value into Lumen.

It does not allow Lumen to move without Carrying Capacity.

DKWS asks first:

What is actually being carried?

What DKWS Helps Clarify

DKWS helps ask simple but important questions:

• What is being contributed?
• Who carries the work?
• Who carries the cost?
• Who carries the risk?
• Who carries responsibility?
• Is there Draagwaarde / Carrying Value?
• What Source Space is involved?
• Who is the Source Holder?
• What Carrying Capacity supports the movement?
• What Context Weight is present?
• What Return Flow may be fair?
• Where are the Source Boundaries?
• Is there enough Field Trust?
• Can this be explained clearly?
• Can Lumen move without becoming Air Value?

The goal is not to make cooperation heavy.

The goal is to prevent hidden pressure, vague expectations, unfair claims, Source Depletion and unsupported movement.

For Entrepreneurs and Practical Carriers

DKWS may be useful for entrepreneurs, suppliers, makers, organisers, service providers, local producers, hubs, project teams or supporting partners.

It can help make visible:

• real costs
• real contribution
• stock or material input
• preparation
• risk
• continuity
• customer relation
• operational pressure
• Source Space
• fair Return Flow
• available Carrying Capacity

This helps prevent one side from silently carrying too much.

A supplier should not be drained.

A participant should not be misled.

A field should not release value it cannot carry.

For a more practical business route, see DKWS for Entrepreneurs.

Carrying Capacity Plan

A Carrying Capacity Plan is a practical planning tool rooted in the Dutch term Draagkrachtplan.

It can help make contribution, cost, risk, Carrying Capacity, Source Space, role division, pre-financing, Return Flow, Context Weight, Field Trust, attention points, boundaries and review moments visible before work begins.

A Carrying Capacity Plan does not assume ideal conditions, unlimited growth or perfect cooperation.

It starts with what is actually present, what can realistically be carried, and what should not be silently absorbed.

A plan can stand on its own.

It does not create an obligation to purchase other services from LumaFonds® or use Luma Protective Services.

Where Lumen Fit

Lumen belongs to the DKWS layer.

Lumen are not money, not euros, not legal tender and not a general claim.

Lumen should not move only by balance.

Lumen move by context.

They may only move where practical exchange is supported by context, Field Trust, Source Space, Carrying Capacity, voluntary acceptance and Return Flow.

Carrying Capacity may come through real work, available stock, pre-financing, a confirmed assignment, a clear guarantee, operational capacity, a visible reserve, Source Space or a Carrying Capacity Reserve.

Lumen do not arise from wish, claim or intention alone.

They arise where value can be carried.

For the deeper structure, see Lumen and Value in Circulation.

What Makes DKWS Different

DKWS does not try to make everything cheaper by hiding costs.

It also does not accept every existing cost as unavoidable.

It helps make hidden costs and unnecessary costs visible.

The purpose is to understand what should truly be carried, what can become lighter, and where value can move more fairly.

DKWS looks for balance between:

• the person contributing
• the source carrying the cost
• the project or field receiving value
• the Return Flow needed to keep movement healthy
• the Source Space that can safely be opened
• the Carrying Capacity that can actually support movement

Money may support value.

It may not replace value.

Value remains connected to contribution, context, responsibility and what can actually be carried.

Source Space and Source Boundaries

Source Space is rooted in the Dutch term Bronruimte.

Source Space means the available room within a source to support movement without becoming depleted, overloaded or unclear.

A source may be stock, money, time, service capacity, tools, space, infrastructure, trust, responsibility or operational availability.

The Source Holder determines what Source Space can safely be opened, under which conditions, and up to which Source Boundary.

This helps DKWS ask whether practical exchange can really be carried before movement grows.

It protects suppliers, entrepreneurs, participants and the wider field from hidden pressure, Source Depletion or unsupported circulation.

Source Space may be asked, offered or opened.

It may not be claimed.

Field Trust and Context Weight

Field Trust is rooted in the Dutch term Veldvertrouwen.

Field Trust grows when contribution, Source Space, Carrying Capacity, Return Flow and limits remain readable.

Without Field Trust, Carrying Value may still be recognised, but it may not yet be safe enough for wider Lumen movement.

Context Weight is rooted in the Dutch term Contextgewicht.

Context Weight helps DKWS understand that not every contribution carries the same practical weight.

A contribution may carry more weight because of risk, responsibility, skill, preparation, continuity, pressure, Source Space or recovery importance.

Lumen remain Lumen.

Context determines the weight.

How LumaFonds May Support

LumaFonds® may help structure pilots, plans, practical agreements and Carrying Capacity questions where it actually carries responsibility.

This may include role clarity, risk visibility, Source Space logic, reserve logic, supplier protection, Return Flow structure or practical planning.

Where LumaFonds® carries risk, reserve, recovery, stock, planning or Source Space, that role must remain visible, bounded and supported by real Carrying Capacity.

LumaFonds® should not become the invisible rescuer of every imbalance.

LumaFonds® should not be treated as the automatic source of the field.

It may support where real Carrying Capacity is present, visible and bounded.

For concrete project support, see DKWS for Entrepreneurs.

What DKWS Should Prevent

DKWS should help prevent:

• contribution being claimed without carrying
• Source Space being used without consent
• Carrying Value becoming automatic Lumen
• Lumen movement without Carrying Capacity
• Return Flow being demanded without real carrying
• Context Weight becoming permanent claim
• one person or source becoming the invisible buffer
• LumaFonds® becoming the invisible rescuer of every imbalance
• Air Value
• Source Depletion
• Essence Extraction

DKWS keeps practical exchange readable by asking what is actually carried before movement grows.

In Essence

DKWS helps practical exchange become clear, fair, explainable and grounded.

It makes visible who carries what.

It protects contribution from being claimed without carrying.

It protects suppliers and Source Holders from being drained.

It protects participants from unclear value.

It protects Source Space from being overloaded.

It protects the field from Lumen without grounding.

DKWS does not turn every recognition into circulation.

It does not turn every form of Carrying Value into Lumen.

Lumen may only move where context, Field Trust, Source Space, Carrying Capacity, voluntary acceptance and Return Flow are sufficiently clear.

DKWS exists so practical cooperation can move without becoming vague, extractive or unfair.