Distribution & Alignment

Distribution within DKWS is not treated as a fixed formula that automatically gives everyone the same share.

Fair distribution does not always mean equal distribution.

It means that payment, recognition, Lumen, responsibility, Source Space and Return Flow are aligned with what each person actually brings, carries, risks, opens and continues to support.

DKWS helps make that visible before tension arises.

The purpose is not to calculate fairness from above.

The purpose is to make what is carried clear enough that people can align before imbalance grows.

Fair Distribution Through Visible Carrying

Within DKWS, fair distribution begins with visible carrying.

A person, entrepreneur or organisation may bring work, risk, cost, client relation, stock, infrastructure, Source Space, preparation, responsibility or continuity.

These forms of carrying are not always equal.

They may carry different Context Weight.

DKWS does not hide those differences.

It helps make them visible, discussable, explainable and bounded.

Distribution becomes healthier when Return Flow follows what has actually been carried.

Where distribution ignores real carrying, Air Value, hidden pressure or unfair extraction may appear.

Equal Is Not Always Fair

In some situations, an equal division may be simple and appropriate.

But in other situations, equal division can hide imbalance.

One entrepreneur may bring in the client.

Another may carry most of the execution.

Another may invest materials, space, preparation, Source Space or transport.

Another may carry financial risk, administrative responsibility or aftercare.

When these differences are real, they should not be ignored.

DKWS does not assume that every contribution is the same.

It asks what is actually being carried.

Equal human worth does not mean equal practical weight in every exchange.

What May Be Included in Distribution

Distribution within DKWS may relate to:

money
Lumen where Carrying Capacity is present
commission
referral value
project contribution
time spent
preparation
materials
transport
storage
administration
risk
responsibility
client contact
aftercare
future work
visibility or recognition
available reserve
infrastructure
tools, space or stock
Source Space
Context Weight
Return Flow

Not every contribution needs to be converted into money or Lumen immediately.

Not every Carrying Value becomes Lumen.

But every meaningful contribution should be visible enough to be considered.

Distribution should remain connected to what is actually carried, not to status, pressure or assumption.

Alignment Before Agreement

Before a distribution is agreed, DKWS encourages participants to clarify:

Who brought the opportunity in?
Who performs which part of the work?
Who carries direct costs?
Who carries risk if something goes wrong?
Who is responsible toward the client?
Who handles payment, communication and follow-up?
Who carries continuity after the first project?
Who provides infrastructure, tools, stock, space or preparation?
Is Source Space being opened?
Who is the Source Holder?
Where are the Source Boundaries?
What Return Flow is fair in this situation?
Is Lumen involved, and if so, what Carrying Capacity supports it?
What happens if the project grows, changes or stops?

These questions prevent assumptions from becoming disappointment.

They also help protect the cooperation from hidden pressure, Air Value and Source Depletion.

Context Weight, Not Permanent Claim

Context Weight is rooted in the Dutch term Contextgewicht.

Within DKWS, some contributions may carry more Context Weight than others.

This may happen when someone carries more risk, cost, responsibility, infrastructure, stock, client relation, preparation, Source Space, continuity or recovery pressure.

That weight may influence distribution within a specific project, source, cooperation or agreement.

But Context Weight is not a permanent claim.

It does not automatically create ownership over future projects, client lines, Lumen movement, Source Space or the wider field.

A heavier contribution may justify a different Return Flow.

But the Return Flow must remain connected to what is actually carried, within the context where it is carried.

DKWS uses alignment to prevent both extremes:

equal sharing where carrying is not equal

and dominant control where one party uses carrying as a reason to take over more than the context justifies.

Percentages Are Tools, Not Truth

Percentages can help make agreements clearer.

But within DKWS, a percentage is not automatically proof of fairness.

A 50/50 split may be fair in one situation and unfair in another.

A small commission may be enough in one case and too little in another.

A larger share may be justified when someone carries more risk, cost, responsibility, infrastructure, Source Space or continuity.

DKWS does not calculate fairness on behalf of people.

It helps people look more honestly at what they are asking from each other.

A percentage should serve clarity.

It should not hide pressure, Air Value or unfair extraction.

Return Flow

Return Flow is rooted in the Dutch term Terugstroom.

Return Flow is broader than direct payment.

It may include money, Lumen where Carrying Capacity is present, future access, continued cooperation, client recognition, shared visibility, materials, support, referrals or another agreed form of value.

The important question is not only:

Who receives what?

But also:

Does the Return Flow match what was carried?

Return Flow is not interest.

It is not automatic entitlement.

It should remain connected to real contribution, responsibility, Source Space, risk, availability or Carrying Capacity.

Where Return Flow is unclear, tension often appears later.

That is why DKWS brings it into the conversation early.

No Hidden Advantage

DKWS is designed to reduce hidden advantage.

Hidden advantage can arise when someone benefits from another person’s client, work, time, network, reputation, infrastructure, Source Space, availability or risk without clear recognition or Return Flow.

This does not always happen through bad intention.

Sometimes it happens because people want to stay friendly and avoid difficult conversations.

DKWS protects cooperation by making these conversations normal.

The purpose is not to make cooperation suspicious.

The purpose is to keep cooperation readable before imbalance becomes conflict.

Field Trust and Distribution

Field Trust is rooted in the Dutch term Veldvertrouwen.

Distribution affects Field Trust.

When contribution, Source Space, risk, responsibility and Return Flow remain visible, Field Trust becomes stronger.

When distribution hides who actually carried what, Field Trust becomes weaker.

Field Trust also weakens when Lumen are distributed without Carrying Capacity, or when Source Space is treated as if it can be claimed.

Distribution should therefore remain readable enough for the people involved to understand why movement takes place.

Where Field Trust becomes weak, Source Space may naturally become less available.

Adjustment When Reality Changes

A fair agreement at the start may become unbalanced later.

A project may grow.

A client may ask for more.

One person may carry more than expected.

Costs may increase.

Risk may shift.

A role may become heavier than first agreed.

A reserve may need to be used or adjusted.

Source Space may become more pressured than expected.

Lumen or Return Flow may need clearer grounding.

Within DKWS, agreements may be reviewed when reality changes.

This does not mean every feeling requires a new deal.

It means that real changes in carrying, risk, cost, responsibility, Source Space, reserve or circulation may justify renewed alignment.

Adjustment should protect clarity.

It should not become a tool for constant pressure.

Lumen in Distribution

Lumen belong to the DKWS layer.

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

Lumen may be part of distribution only where context, Field Trust, Source Space, Carrying Capacity and Return Flow are sufficiently clear.

Lumen should not move by balance alone.

Lumen move by context.

This means that the number alone is not enough.

The contribution context, Context Weight, Source Space, voluntary acceptance, Carrying Capacity and Return Flow must remain readable.

Not all Carrying Value becomes Lumen.

Where Lumen are distributed without enough Carrying Capacity, Air Value may enter the field.

Core principle

Fair distribution does not always mean equal distribution.

It means aligned distribution.

DKWS does not promise perfect fairness through numbers.

It offers a structure for honest alignment.

Money, Lumen, time, clients, risk, responsibility, Source Space, reserve and recognition should not disappear into vague cooperation language.

When people carry differently, distribution may need to differ too.

The goal is not to make everyone the same.

The goal is to make what is carried visible enough that the agreement can remain fair, practical, responsible and bounded.

Distribution begins with one question:

Who is carrying what?

It continues with another:

Does the Return Flow still match what is actually being carried?

What DKWS Should Prevent in Distribution

DKWS should help prevent:

equal sharing where carrying is not equal
dominant control where one party carries more
hidden advantage
vague commission expectations
Return Flow disconnected from real carrying
Source Space being used without consent
Lumen distribution without Carrying Capacity
Context Weight becoming permanent claim
client lines being absorbed without agreement
one party becoming the invisible buffer for others
Air Value
Source Depletion
Essence Extraction

Distribution should remain practical, explainable and correctable.

It should not become a hidden power layer.

It should not turn cooperation into ownership over people, clients, sources or future movement.

In Essence

DKWS helps distribution follow what is actually carried.

It does not make every share equal by default.

It does not let client lines, risk, costs, preparation, infrastructure, stock, Source Space, continuity or responsibility disappear into vague cooperation.

Lumen may only be part of distribution where context, Field Trust, Source Space, Carrying Capacity and Return Flow support them.

Context Weight may justify a different Return Flow, but it does not create permanent claim or field control.

Fair distribution begins by asking: