Value Origin Standard (VOS)
2. Value Origin Standard (VOS)
Architecture Ecosystem: Structured Reality Standards™
Architecture Family: VFM® — Value Flow Mechanism
Parent Standard: Value Origin Standard (VOS)
Operational Layer: Value Origin Governance Layer
Category: Governance & Enforcement
Subcategory: Value Lifecycle Governance
Type: Parent Standard
Governed Space: Value Origin
Origin ID: VFM-VOS-002
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 23 August 2026
Compatibility: OOF® Methodology OS™ · GOA™ · ORA™ · AGA™ · INTEGROS® · CLA™ · ADIT® · VALIDOS® · OBIDENITY®
AI-Readable: Yes
Authority: OOF®
Protection: MIP® — Methodology Intellectual Property Protection
Canonical Language: English
Canonical Definition
Value Origin Standard (VOS) is the second Parent Standard within VFM® — Value Flow Mechanism and governs the identification, definition, relationship, conditions, and documentation of the origin from which governed value can emerge.
VOS establishes the methodological distinction between the source capable of producing value and value that has actually come into existence.
The Standard recognizes that value does not appear without a basis. It may originate from an object, capability, resource, activity, relationship, information, knowledge, right, condition, process, infrastructure, system, opportunity, natural resource, human capability, technological capability, or another identifiable source.
VOS does not determine whether value has already emerged, how much value exists, what its current state is, how it changes, or whether it will ultimately be realized.
Its purpose is foundational:
to establish where the governed value can originate and the basis connecting that potential value to its source.
Core Question
From what identifiable source, capability, condition, activity, relationship, object, or other basis can the governed value originate?
Architectural Position
VOS occupies the second governed space of the VFM® value lifecycle.
It follows:
Value Context Standard (VCXS)
and precedes:
Value Emergence Standard (VES).
The preceding standard establishes:
What value is being governed?
VOS then establishes:
Where can that value come from?
The next standard determines:
Has value actually emerged?
The sequence is therefore:
Value Context → Value Origin → Value Emergence
This distinction prevents a potential source of value from being treated automatically as existing value.
Governance Flow Position
Governed Value Context → Value Source Identification → Value Source Basis → Value Origin Relationship → Value Origin Conditions → Value Origin Documentation → Governed Value Origin → Value Emergence
Operational Space
VOS governs the space between:
identified value context
and
actual emergence of value.
Its governed space includes:
value source identification; value-source differentiation;
source basis; source capability; origin relationships; origin dependencies; origin conditions; latent value potential; multiple-source value origin; composite value origin; conditional value origin; temporal origin; origin continuity; origin change; origin documentation.
The Standard asks whether a sufficiently identifiable basis exists from which the governed value can arise.
It does not presume that value already exists.
Value Source Principle
A Value Source is an identifiable basis from which a defined form of value may potentially emerge.
A Value Source may include:
physical assets; natural resources; intellectual property; knowledge; data; infrastructure; technology; human capability; organizational capability; production capability; relationships; networks; contractual rights; access rights; operational capacity; energy resources; financial resources; land; biological resources; algorithms; software; inventions; scientific discoveries; market access; time; location; information; combinations of multiple sources.
A source becomes relevant to VOS only in relation to the governed value context established by VCXS.
Value Source ≠ Value
The central distinction of VOS is:
Value Source ≠ Existing Value
An object, capability, resource, or relationship may possess the capacity to generate value without that value having yet emerged.
For example:
A mineral deposit may exist without economically recoverable value having emerged.
A patent may exist without generating licensing value.
A manufacturing machine may exist without producing operational value.
A dataset may exist without creating informational or economic value.
A technology may exist without creating cost-saving value.
A scientific discovery may exist before commercial or operational value emerges.
VOS therefore prevents potential from being silently treated as realized value.
Origin Asset™
Origin Asset™ has its natural architectural home within Value Origin governance.
An Origin Asset™ represents an identifiable asset, capability, resource, relationship, condition, or other governed basis capable of functioning as an origin from which value may emerge.
The concept does not itself establish:
existing value; monetary value; ownership; legality; validation; market recognition; accounting recognition; taxable value; asset identity; value realization.
Its function within VFM® is narrower:
Origin Asset™ identifies a potential value-origin basis.
Therefore:
Origin Asset™ ≠ Value Asset™
An Origin Asset™ may become associated with a Value Asset™ only after the relevant value has legitimately emerged and entered an applicable value state.
Source Basis
Identifying a source is insufficient unless the basis through which that source may produce value is understood.
VOS therefore distinguishes:
Value Source
from
Value Source Basis.
For example:
Factory → source.
Capability to manufacture a required product → source basis.
Dataset → source.
Capability to reduce decision uncertainty → source basis.
Satellite → source.
Capability to generate Earth-observation information → source basis.
Patent → source.
Exclusive technological capability capable of enabling commercial exploitation → source basis.
The source identifies where value may originate.
The basis explains why that source is capable of producing the governed value.
Value Origin Relationship
Value may originate through a relationship rather than through an isolated object.
VOS therefore governs the relationship between:
Value Source → Governed Value
The relationship may be:
direct; indirect; enabling; dependent; conditional; composite; sequential; network-based; temporal; reciprocal.
A source should not be attributed as the origin of value merely because it is associated with the value-bearing object.
There must be a methodologically intelligible relationship between the source and the value capable of emerging from it.
Multiple Value Sources
One form of value may originate from multiple sources.
For example:
AI service value
may originate from a combination of:
model capability + data + computing infrastructure + software + human expertise + distribution network.
No single source may independently explain the value.
VOS therefore supports:
Composite Value Origin
where multiple sources jointly establish the basis from which value may emerge.
One Source, Multiple Values
The reverse is also possible.
One source may generate several distinct forms of value.
A satellite may generate:
scientific value commercial data value strategic value navigation value security value environmental monitoring value
These values must remain distinguishable according to the Value Context established under VCXS.
Therefore:
One Value Source ≠ One Value
Latent Value Origin
Some sources contain a value-generating capability that has not yet produced actual value.
VOS recognizes this as:
Latent Value Origin
Examples may include:
unused intellectual property; undeveloped land; unexploited mineral resources; dormant datasets; unused production capacity; uncommercialized scientific discoveries; unused spectrum; inactive infrastructure; unused technological capabilities.
Latent origin is not equivalent to zero value.
Nor is it equivalent to positive value.
It identifies a potential value-origin condition prior to value emergence.
Value Origin Conditions
A Value Source may require particular conditions before value can emerge.
These conditions may include:
access; demand; technological capability; infrastructure; complementary resources; operational readiness; environmental conditions; human capability; network participation;
timing; scarcity; usability; interoperability; availability; deployment; combination with another source.
The existence of a source therefore does not imply that the conditions necessary for value emergence are present.
Conditional Value Origin
Where value can originate only under specified conditions, VOS recognizes:
Conditional Value Origin
For example:
A renewable-energy installation may become a source of grid value only where grid connection exists.
A dataset may become a source of analytical value only where sufficient processing capability exists.
A manufacturing capability may become a source of commercial value only where demand exists.
A technology may become a source of cost-saving value only when integrated into an operational process.
The source exists.
Its ability to produce the governed value remains conditional.
Origin Dependency
Some value origins depend upon other origins.
For example:
Software Service Value
may depend upon:
Software → Compute Infrastructure → Energy → Network Access
VOS may therefore document Origin Dependencies where the ability of one source to produce value depends materially upon another source.
This enables later lifecycle governance to distinguish between:
loss of value
and
loss of a condition enabling the source to produce value.
Value Origin Change
A Value Source may change over time.
Its capability may:
increase; decrease; become inaccessible;
become obsolete; combine with another source; split into multiple sources; become substituted; disappear.
VOS therefore permits a governed Value Origin to be versioned or reassessed where material source conditions change.
However:
Value Origin Change ≠ Value Change
A change in the source may eventually cause a change in value, but VFM® must preserve these as distinct lifecycle events.
Origin Extinction ≠ Value Extinction
A source may disappear while previously generated value continues to exist.
Likewise, a source may continue to exist after the value associated with it has disappeared.
Therefore:
Value Source Extinction ≠ Value Extinction
This distinction becomes important later in the VFM® lifecycle.
Parent Standard Modules
1. VSOIM — Value Source Identification Module
Governs identification and differentiation of the source, capability, resource, activity, relationship, condition, object, or other basis from which the governed value may originate.
It establishes the identifiable Value Source.
2. VSBM — Value Source Basis Module
Governs the basis explaining how and why the identified Value Source is capable of producing the governed value.
It distinguishes simple association from an intelligible value-origin basis.
3. VORM — Value Origin Relationship Module
Governs the relationship connecting the Value Source to the governed value.
It supports direct, indirect, composite, enabling, conditional, sequential, and multi-source origin relationships.
4. VOCM — Value Origin Conditions Module
Governs the conditions, dependencies, circumstances, thresholds, capabilities, or environmental states required for the identified source to function as an origin of the governed value.
5. VODM — Value Origin Documentation Module
Governs the structured documentation, traceability, versioning, dependencies, conditions, and reconstruction of the governed Value Origin.
Internal Module Flow
Governed Value Context → VSOIM — Value Source Identification → VSBM — Value Source Basis → VORM — Value Origin Relationship → VOCM — Value Origin Conditions → VODM — Value Origin Documentation → Governed Value Origin → Value Emergence Standard
The logic is:
Where could the value originate? → Why can this source produce it? → How is the source connected to the value? → Under what conditions can that relationship operate? → How is the complete origin basis preserved?
Cross-Architecture Boundaries
VOS governs value origin, not general identity, validation, integrity, audit, authority, classification, or operational execution.
OBIDENITY® may establish the identity, origin-bound identity, ownership, authority, provenance, or continuity of an underlying entity.
VALIDOS® may determine whether a claim concerning a Value Source or origin relationship is sufficiently validated.
INTEGROS® may govern integrity of the source, records, conditions, or supporting information.
ADIT® may govern audit and evidence concerning how the origin determination was established.
GOA™ may govern authority and responsibility for the process.
VFM® retains the narrower question:
From where can this governed value originate?
Minimum Implementation Framework
A minimum VOS implementation should establish:
1. Governed Value Context
Identify the value context inherited from VCXS.
2. Value Source
Identify the source or sources from which the value may originate.
3. Source Basis
Define why the source is capable of producing the governed value.
4. Origin Relationship
Define how the source relates to the value.
5. Origin Conditions
Identify conditions required for the value-origin relationship to operate.
6. Dependencies
Identify material dependencies affecting the source's ability to produce value.
7. Multi-Source Structure
Where necessary, identify composite or interacting sources.
8. Temporal Basis
Identify material timing or lifecycle conditions affecting origin.
9. Origin Status
Establish whether the origin is active, latent, conditional, changed, unavailable, or otherwise appropriately governed.
10. Value Origin Record
Document the complete governed origin basis for transfer into Value Emergence governance.
Governance Outputs
VOS may produce:
Value Source Record Value Source Identifier Value Source Basis Record Value Origin Relationship Record Composite Value Origin Map Value Origin Dependency Record Value Origin Condition Record Latent Value Origin Record Conditional Value Origin Record Value Origin Change Record Value Origin Status Value Origin Record
These outputs establish the basis required by the next lifecycle stage:
Value Emergence Standard (VES).
Enterprise Application
VOS allows an organization to distinguish between:
what exists
and
what actually creates the possibility of value.
This is particularly useful in banking, investment, public finance, industrial systems, intellectual property, digital assets, AI, infrastructure, energy, natural resources, scientific research, and technology portfolios.
Instead of beginning with an assumed monetary value, an organization can trace the governed value backward to the source or combination of sources capable of producing it.
This creates a stronger methodological basis for later determining whether value has actually emerged, what state it occupies, and how it subsequently changes.
Use Case 1 — Banking: Identifying the Real
Source of Credit Value
A financial institution evaluates a manufacturing company seeking financing.
Traditional analysis may begin with assets, financial statements, collateral, and expected cash flows.
VOS permits a different question:
From what sources does the company's ability to generate the relevant value actually originate?
The analysis may identify:
manufacturing equipment + skilled workforce + production knowledge + customer relationships + intellectual property + supply-chain access
as a composite Value Origin.
This distinction matters because the physical equipment alone may not explain the value-generating capability.
If critical customer relationships disappear or specialized production knowledge is lost, the underlying Value Origin may weaken even though the accounting assets remain physically present.
VOS therefore provides a structured method for understanding the origin architecture behind value-generating capability before later VFM® stages govern actual value emergence and change.
Use Case 2 — Space Mission: Locating the
Source of Cost-Avoidance Value
A space organization introduces a high-fidelity simulation capability intended to reduce expensive physical testing.
The governed value context established under VCXS is:
Cost-Avoidance Value → Mission Program → Mission Development Reference Framework.
VOS then identifies where that value can originate.
The source may not simply be:
simulation software.
The actual Value Origin may be composite:
simulation model + computing infrastructure + validated engineering knowledge + scenario capability + mission data + engineering expertise.
The source basis is the capability to detect design problems before expensive physical construction or testing occurs.
The value has not necessarily emerged yet.
VOS establishes only the governed origin from which that cost-avoidance value can emerge.
When the simulation subsequently identifies a design defect and prevents a CHF 20 million physical-test failure, the architectural question moves from:
Value Origin
to:
Value Emergence.
This clean separation allows VFM® to trace the value lifecycle from its source rather than recognizing value only after financial consequences appear.
Foundational Principles
Value must not be assumed merely because a potential source of value exists.
Value Source ≠ Existing Value.
Origin Asset™ ≠ Value Asset™.
One source may originate multiple forms of value.
One form of value may originate from multiple sources.
Value origin may be latent, active, conditional, composite, dependent, or changing.
The source of value and the conditions enabling value emergence must remain distinguishable.
A change in Value Origin does not automatically constitute a change in value.
The disappearance of a Value Source does not automatically constitute Value Extinction.
Canonical Closing Statement
Value Origin Standard establishes the governed origin layer of the VFM® value lifecycle by identifying the sources, capabilities, resources, activities, relationships, objects, conditions, and composite structures from which a defined form of value may emerge. Through governance of Value Sources, source bases, origin relationships, enabling conditions, dependencies, latent origins, conditional origins, multi-source structures, temporal changes, and origin documentation, VOS prevents potential value from being confused with existing value and establishes the methodological distinction between the capability to produce value and the actual emergence of value. By positioning Origin Asset™ as a value-origin concept rather than an automatic declaration of value, VOS provides the traceable foundation required for the next lifecycle question: not merely where value could come from, but whether value has actually come into existence.
Nahlad
Value Origin Standard (VOS)
Architecture: VFM® — Value Flow Mechanism
Category: Governance & Enforcement
Subcategory: Value Lifecycle Governance
Canonical Definition: Value Origin Standard governs the identification, basis, relationships, conditions, and documentation of the sources from which a defined form of value may emerge, while preserving the fundamental distinction between a potential source of value and value that has actually come into existence.
Governed Space: Value Origin
A source may possess the capability to generate value without that value having yet emerged. Value Source ≠ Existing Value.
→ View Standard
About standard