Protocol mathematics
How a lived moment becomes a value claim
A story-first guide to how The Internet of Value separates observation, human-state movement, commons value, chronology and evidence.
With the vocabulary set
Next, move to variables and symbols.
Select VC, W or Vcom to see its meaning and open the protocol tools behind it.
Where W begins
Before W can change, it needs a starting state.
Identity + consent6 baseline statest₀
The Identity workshop establishes the observer and consent context; it does not score identity. A separate evidence review establishes Physiology, Emotion, Feeling, Thought, Habit and Performance at a declared starting boundary—called Genesis in the implementation.
Any composite is a secondary policy projection. The component state remains visible.
Then follow a moment
Now the variables can move through lived time.
Imagine a facilitated learning session. It took time. It may have helped someone learn. It may have exhausted the facilitator. It may or may not have an authorised economic value. Those are different questions.
01
What happened?
A bounded time slice records activity, context and provenance.
02
What changed for the person?
A separate review may record movement, no transition or pending.
03
What value was constituted?
A commons route may produce typed value when its required inputs exist.
One moment · two possible routes
Keep economic value and human change separate.
The model preserves different units, decisions and privacy boundaries instead of collapsing them into one score reveal.
Private human-state route
- Wellbecoming nodes
- ~~Physiology, ~~Emotion, ~~Feeling, ~~Thought or ~~Habit
- Commons route
- Not automatically activated
- Possible output
- Wafter and deltaW in WellbeingScore units
- Economic value
- Not automatically produced
- Human boundary
- A state update, never a price for personal life
Conditional Performance route
- Wellbecoming node
- ~~Performance
- Commons route
- May open through ~~Learning, ~~Earning or ~~OrgBuilding
- Vcom_event
- Requires declared, validated valuation inputs
- Missing valuation
- Vcom_event and VCperformance_event remain null
- Human movement
- Applied, no transition or pending under a separate decision
- Time boundary
- ~~~StartTime to ~~~EndTime
Synthetic fixture · not observed data
One explicitly valued Performance hour
The purpose is dimensional clarity: show where each input enters and keep the person distinct from the event output.
Wbefore / 1000= 800 / 1000 = 0.8
Vcomevent= 1,000 hypothetical credits
Duration= 1 validated hour
VCperformanceevent= 0.8 × 1,000 = 800 hypothetical credits
Read it aloud: the event begins from a represented Wbefore of 800/1000 and has a constituted Vcom of 1,000 hypothetical credits. The typed event output is therefore 800 hypothetical credits.
A different decision still determines whether represented wellbeing moves, remains unchanged or stays pending.
The unit is deliberately hypothetical. This example does not publish a live rate, observed author event or private score.
Follow the complete story-led caseTime boundary
Time belongs to the captured slice.
~~~StartTime~~~EndTime
~ValueCaptureProtocol/~~TimeSlice supplies the observation boundary. Several non-overlapping slices may describe one occurrence, but splitting the clock must not silently multiply the human transition.