The Internet of Value
Curated IoV legacy terms
A current-language glossary for IoV-specific terms that appeared in early Internet of Value public materials.
This page translates useful early Internet of Value vocabulary into the current Foundation website language.
The old public site used terms like OpenProtocolStack, DAOcommons, Wellbeing Protocol, and Value Capture Protocol while the system was still being named. The current public model is the four-protocol stack: ~ValueCaptureProtocol, ~WellbecomingProtocol, ~SAOcommons, and ~WellbeingIdentity.
Use this page as a migration glossary, not as a protocol specification.
OpenProtocolStack
Early public phrase for the coordinated IoV protocol system.
Current usage: use Internet of Value protocol stack when speaking publicly, and refer to the four Level 1 protocols by their canonical names.
Value Capture Protocol
Early public phrase for making value creation visible before extraction or pricing.
Current usage: use ~ValueCaptureProtocol. It concerns bounded time, activity, proof, and context so contribution can become legible before it is flattened into output metrics.
Wellbeing Protocol
Early public phrase for making wellbeing part of the value system.
Current usage: use ~WellbecomingProtocol when describing the protocol logic that brings human state into the system. Use ~WellbeingIdentity when describing the living state that updates from validated protocol flows.
DAOcommons
Early public phrase for community and DAO-oriented coordination.
Current usage: use ~SAOcommons. The public macro lanes are ~~Learning, ~~Earning, and ~~OrgBuilding. Validation, attestation, valuation, pricing, and disputes are lifecycle facets inside those lanes, not standalone public macro nodes.
Wellbeing Identity
The current protocol term for a living state built and updated by validated flows from the other three protocols.
Current usage: use Wellbeing Identity in prose and ~WellbeingIdentity when referring to the canonical protocol. Do not describe it as a standalone profile.
Aura View
Current UI metaphor for a person-facing view of wellbeing identity state.
Current usage: use Aura View for product or experience language only. Protocol-grounded copy should still say Wellbeing Identity.
Value Capture
The shift from invisible human input to visible contribution.
Current usage: value capture should be explained through time, activity, proof, and context. It should not be reduced to monetization.
Value Creation
Human, community, and institutional activity that produces value before that value is priced, extracted, or counted by existing systems.
Current usage: pair value creation with contribution, learning, care, skill, coordination, and community validation.
Value Extraction
The capture of output, attention, revenue, reputation, or price without adequately recognizing the human input beneath it.
Current usage: useful as a critique, but avoid treating it as the whole story. The current Foundation framing is constructive: make time, wellbeing, contribution, and validation legible.
Time
The common human input beneath labor, learning, care, rest, recovery, coordination, and performance.
Current usage: time is not just duration. In IoV public language, time becomes meaningful when bounded by activity, state, proof, and context.
State
The condition a person carries through time.
Current usage: state can include wellbeing-relevant context, but public copy should avoid implying full surveillance or forced disclosure. Consent and privacy boundaries matter.
Contribution
Work, care, learning, coordination, or other meaningful activity that may not be visible in conventional economic measures.
Current usage: contribution becomes more durable when connected to bounded time, proof, community context, and validation.
Community Validation
The process by which a community recognizes, attests, or disputes contribution and value.
Current usage: connect this to ~SAOcommons, especially the ~~Learning, ~~Earning, and ~~OrgBuilding lanes.
Value Exchange
The movement of value between people, communities, institutions, and systems.
Current usage: value exchange can include money, but IoV copy should not limit exchange to payments or crypto transfer. The broader question is what became legible before exchange happened.
Protocol
A repeatable structure for naming, validating, and coordinating value across contexts.
Current usage: use protocol language carefully. The Foundation website can explain protocols, but canonical protocol definitions come from the IoV Spec API and source repositories.