NCWS is a developing route within the Lightpoint Value System.

LumaFonds may support NCWS with structure, language, field setup, templates, field weighing, correction routes and practical guidance.

But LumaFonds does not own NCWS fields.

LumaFonds is not a gatekeeper.

Fields carry their own field.

LumaFonds Facilitates Structure

LumaFonds helps make NCWS understandable, workable and consistent.

It may provide language, page structures, field templates, support options, practical guidance and development frameworks.

The purpose is not to control mobile fields or temporary communities.

The purpose is to help fields make context, carried contribution, field trust and field balance more visible.

LumaFonds facilitates structure.

The field carries the reality.

Fields Carry Their Own Field

NCWS fields are not owned by LumaFonds.

A field may organise its own internal circulation where context, consent, trust and carried weight remain visible.

A field may recognise contribution.

A field may use context notes.

A field may accept circulation carriers.

A field may correct imbalance.

A field may exchange directly with another field when both fields trust each other and voluntarily accept each other’s context weight.

LumaFonds does not need to stand between fields where trust is clear enough.

Direct Field Trust

NCWS allows direct field trust.

If two fields know each other, trust each other and voluntarily accept each other’s context weight, they may exchange directly.

This does not require LumaFonds approval.

Direct trust is possible where context, consent, field trust and visible balance remain present.

But direct trust should not be used to hide pressure, false weight, debt, coercion, unclear source use or legal obligations.

Freedom within the field remains connected to responsibility.

When LumaFonds May Help

LumaFonds may help when a field needs more clarity, structure or support.

This may include:

• NCWS field setup
  
• context note templates
  
• circulation carrier language
  
• partial carrier logic
  
• field balance guidance
  
• field weighing support
  
• field keeper orientation
  
• context witness guidance
  
• correction and restoration routes
  
• field bridge preparation
  
• connection with DKWS where needed

LumaFonds support is meant to make the field clearer, not more dependent.

NCWS Field Setup

An NCWS Field Setup may help a mobile field, temporary community or nomadic circle create a clear starting structure.

It may help define:

• what kind of field is forming
  
• what kind of contribution may be recognised
  
• how context may be noted
  
• how field trust may be protected
  
• how circulation carriers may be used
  
• how field balance may remain visible
  
• how correction may happen
  
• where the field boundaries are

A field setup does not force participation.

It helps a field begin with enough clarity to avoid confusion later.

Field Weighing Review

A Field Weighing Review may help when fields want to cooperate but their carriers, weights or context are not automatically clear.

It may be useful when:

• two NCWS fields want to cooperate
  
• an NCWS field wants to connect with DKWS
  
• a carrier moves outside its original field
  
• context weight is disputed
  
• a field feels under-recognised or overburdened
  
• a bridge between fields creates pressure
  
• source space or responsibility becomes heavier

Field weighing is not an exchange rate.

It is not automatic conversion.

It is a contextual reading between fields.

No Ownership Over Value

LumaFonds does not create value from outside the field.

LumaFonds does not decide the worth of people.

LumaFonds does not own the contribution of a field.

LumaFonds does not turn context weight into money, debt or claim.

Value becomes visible where something has actually been carried.

LumaFonds may help name, structure and protect that visibility.

But the carried context remains with the field.

Earning Through Clarity

LumaFonds may offer paid support.

This may include field setup, structure development, field weighing, templates, guidance, training, review or practical documentation.

But LumaFonds should earn by making fields clearer, not by making them dependent.

LumaFonds should not benefit from confusion, hidden pressure or unnecessary complexity.

Support should help fields become more readable, more balanced and more capable of carrying their own structure.

LumaFonds earns through clarity, not dependency.

Support Without Control

LumaFonds may advise strongly where consistency matters.

For example, fields that want to cooperate with other fields may be advised to use a shared weight language, clear context notes and visible correction routes.

This helps fields remain readable to each other.

But advice is not ownership.

Support is not control.

Guidance is not command.

A field remains responsible for what it carries.

Connection With DKWS

NCWS may sometimes touch DKWS.

This may happen when circulation becomes heavier, more structured, connected to Source Space, connected to entrepreneurs, connected to return movement or connected to practical responsibility.

When this happens, more clarity may be needed.

DKWS may help where Carrying Capacity, Source Space, role division, risk, pre-financing or Return Flow need clearer structure.

NCWS can remain light where the field remains light.

DKWS becomes relevant where carrying responsibility becomes heavier.

Legal and Practical Clarity

LumaFonds support does not replace legal, fiscal or practical responsibility.

NCWS is not intended to avoid tax obligations, contracts, wages, law, liability, permits or ordinary trade.

Where money, contracts, employment, business activity or formal responsibility are involved, the practical world remains relevant.

LumaFonds may help make boundaries clearer.

But each field, person or organisation remains responsible for acting within the real context they are part of.

Core Sentence

LumaFonds facilitates structure.

Fields carry their own field.

Direct trust is allowed where context is clear enough.

Field weighing may help where difference becomes visible.

LumaFonds earns by making fields clearer, not by making them dependent.

Recognition first.

Carrying Capacity where needed.

Circulation where context can carry it.