Influence, Weight and Boundaries
DKWS does not deny that influence can differ.
In practical systems, some people, entrepreneurs, organisations or carrying sources may carry more cost, more risk, more responsibility, more continuity, more Source Space or more operational pressure.
That reality should not be hidden.
It should be made visible.
DKWS exists to make practical weight discussable before it turns into unclear power.
A heavier role may carry more Context Weight.
It does not create higher human value.
Influence may follow responsibility, but it must remain connected to what is actually carried, where it is carried, and under which boundaries.
Greater Weight Does Not Mean Control
Greater contribution, greater risk or greater responsibility may justify more weight in certain practical areas.
But greater weight does not automatically mean control over the whole field.
Influence must remain visible, discussable, explainable and bounded.
No person, company, organisation or party should be able to turn practical contribution into unlimited control.
What is carried should be recognised.
But what is carried should not become a claim over everything.
Context Weight may shape a specific agreement, project, Source Space or Return Flow.
It may not become general authority over LPWS, DKWS or the wider field.
LumaFonds® and Practical Carrying
LumaFonds® may build, pay, initiate, organise or help carry parts of the practical field.
That can create responsibility and practical weight.
It may also give LumaFonds® a stronger role in areas where it carries real cost, risk, infrastructure, continuity, stock, operational responsibility, Source Space or reserve.
But this does not make LumaFonds® the owner of the entire structure.
LumaFonds® may carry important parts of the field without turning the whole field into possession.
Where LumaFonds® carries risk, reserve, Source Space or continuity, that role should remain visible, bounded and explainable.
LumaFonds® should not be treated as the automatic source of the field.
It may carry where real Carrying Capacity is present, visible and bounded.
Its influence should follow what it actually carries.
It should not silently expand into control over people, participants, entrepreneurs, Source Holders or the wider field.
More Influence, Not Unlimited Influence
Large contributors or operational parties may receive more influence in the areas they actually carry.
But not unlimited influence.
And not over everything.
Influence should remain connected to the area of actual carrying.
If a party carries stock, it may have more say over that stock.
If a party carries risk, it may need clearer boundaries around that risk.
If a party carries infrastructure, it may have a stronger role in how that infrastructure is used.
If a party opens Source Space, it may define the Source Boundaries connected to that Source Space.
But influence should not silently expand beyond what is actually carried.
Influence remains healthy when it stays connected to contribution, Carrying Capacity, Source Space, responsibility and Return Flow.
Context Weight, Not Field Control
Context Weight is rooted in the Dutch term Contextgewicht.
Carrying more may create recognition and Context Weight.
But it does not create authority over the whole field.
A person, entrepreneur, Source Holder or organisation may have more weight within a specific source, pilot, responsibility or agreement because they actually carry more.
That weight must remain connected to the concrete context where the carrying happens.
It should not silently become general control over LPWS, DKWS or the wider field.
Influence may follow responsibility, but it must remain bound to context, contribution, Source Space and agreed limits.
Context Weight can help explain why Return Flow or influence may differ in one agreement.
It should not become a permanent claim.
Source Holder Influence
A Source Holder may carry specific influence over the Source Space they open.
This is not domination.
It is source responsibility.
A Source Holder may define what can be made available, under which conditions, and up to which Source Boundary.
DKWS may ask, clarify, signal or advise.
It may not claim Source Space.
When a Source Holder opens stock, space, service capacity, funding, tools, infrastructure, food flow or operational capacity, that opening must remain voluntary, bounded and connected to Return Flow.
Source Holder influence becomes unhealthy when it turns into control over the whole field.
Field influence must stay connected to what is actually being carried.
Behaviour, Pressure and Boundaries
DKWS does not judge inner intention.
The field does not claim to know someone’s soul, motivation or inner state.
What can be observed is behaviour, pressure, responsibility, dependency, Source Space use, Return Flow and the way influence affects others.
A carrying party may become a concern when contribution is used to create pressure, claim authority, force dependency, demand exception, push Lumen movement too quickly or pull the field toward private interest.
The question is not whether someone is “good” or “bad”.
The question is whether the influence remains clear, bounded, explainable and connected to what is actually carried.
Where pressure begins to steer, movement should slow down.
Where influence becomes unclear, the agreement should be reviewed.
Where Source Space is claimed rather than opened, DKWS should protect the source.
Boundaries Keep Contribution Clean
A boundary helps show:
- what someone carries
- where their influence is legitimate
- where their influence stops
- what Source Space is involved
- where the Source Boundary sits
- what Return Flow may be fitting
- what must be agreed before influence expands
- how cooperation can remain fair without becoming vague
This keeps practical exchange from turning into silent ownership, hidden pressure or unclear dependency.
Boundaries do not reject contribution.
They protect contribution from becoming control.
Practical Weight and Return Flow
Where practical weight is greater, Return Flow may also differ.
Someone who carries more cost, risk, continuity, infrastructure, reserve, Source Space or operational pressure may need a different share, role or Return Flow.
That is not automatically unfair.
But it must remain explainable.
Return Flow should follow what is actually carried, not what is only claimed.
DKWS does not deny different weight.
It asks that different weight remains visible enough to be discussed before it becomes tension.
A heavier contribution may justify a different Return Flow within a specific context.
It does not justify unlimited control outside that context.
Field Trust and Influence
Field Trust is rooted in the Dutch term Veldvertrouwen.
Field Trust grows when influence remains visible, explainable and bounded.
It becomes weaker when influence is hidden, when Source Space is claimed, when Return Flow is demanded without real carrying, or when practical weight becomes a reason for control.
Field Trust also becomes weaker when Lumen are pushed without Carrying Capacity, or when Context Weight becomes a permanent claim.
DKWS protects Field Trust by keeping influence connected to real responsibility, real Source Space, real Carrying Capacity and agreed boundaries.
Where Field Trust becomes weak, Source Space may naturally become less available.
What DKWS Should Prevent in Influence
DKWS should help prevent:
- greater carrying becoming ownership
- Context Weight becoming field control
- Source Space being claimed without consent
- LumaFonds® or any other party being treated as automatic owner of the field
- influence expanding beyond what is actually carried
- practical weight becoming hidden power
- Return Flow being demanded without real carrying
- Lumen movement being pushed without Carrying Capacity
- boundaries being treated as disloyalty
- one person or party becoming the invisible authority
- Air Value
- Source Depletion
- Essence Extraction
Influence should remain practical, visible and bounded.
It should not become a hidden ownership layer.
In Essence
DKWS recognises that influence can differ.
But influence must stay connected to what is actually carried.
Greater carrying may justify greater influence in a specific area.
It does not justify unlimited control over the whole field.
Carrying more may create recognition and Context Weight, but it does not create authority over LPWS, DKWS or the wider field.
A Source Holder may carry influence over the Source Space they open.
That influence must remain bounded by Source Boundaries, Carrying Capacity and Return Flow.
The field does not judge inner intention.
It observes behaviour, responsibility, pressure, Source Space use, Return Flow and boundaries.
Boundaries protect contribution from becoming hidden ownership, silent pressure or field control.
DKWS keeps influence clean by making it visible, explainable and bounded.