Value Origin Relationship Module (VORM)
Value Origin Relationship Module (VORM)
Architecture Ecosystem: Structured Reality Standards™
Architecture Family: VFM® — Value Flow Mechanism
Parent Standard: Value Origin Standard (VOS)
Module: VORM — Value Origin Relationship Module
Operational Layer: Value Origin Relationship Layer
Category: Governance & Enforcement
Subcategory: Value Lifecycle Governance
Type: Core Module
Governed Space: Value Origin Relationship
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 23 August 2026
AI-Readable: Yes
Authority: OOF®
Protection: MIP® — Methodology Intellectual Property Protection
Canonical Language: English
Canonical Definition
Value Origin Relationship Module (VORM) is the third Core Module of the Value Origin Standard (VOS).
VORM governs the explicit relationship between an identified Value Source, its established Value Source Basis, and the governed value to which that source may contribute.
The Module determines how the source and its value-relevant basis are connected to the potential origin of the governed value.
VORM operates after:
VSOIM — Value Source Identification Module
and
VSBM — Value Source Basis Module.
The distinction is fundamental:
VSOIM identifies the source.
VSBM identifies what about the source can contribute to value.
VORM establishes how that basis is related to the origin of the specific governed value.
VORM does not establish that value has already emerged.
It establishes the origin relationship capable of supporting subsequent Value Emergence.
Architectural Position
VORM is the third module within the Value Origin Standard.
It follows:
VSBM — Value Source Basis Module
and precedes:
VOCM — Value Origin Conditions Module.
The internal sequence is:
Identified Value Source → Established Value Source Basis → Value Origin Relationship Identification → Relationship Type → Relationship Structure → Contribution Pathway → Dependency Identification → Value Origin Relationship Record → VOCM — Value Origin Conditions Module
VORM therefore moves Value Origin governance from:
Why can this source matter?
to:
How can this source contribute to the origin of this specific value?
Operational Space
VORM governs relationships connecting:
Value Source
to:
Governed Value
through an established:
Value Source Basis.
These relationships may be:
direct; indirect; enabling; dependent; conditional; complementary; cumulative; sequential; substitutive; synergistic; network-based; multi-source; multi-stage; temporal; latent.
The Module does not assume that one source produces one value through one simple causal pathway.
Complex value may originate through networks of relationships.
Source Basis ≠ Origin Relationship
VORM establishes the distinction:
Value Source Basis ≠ Value Origin Relationship
A basis describes what the source possesses, enables, provides, or can do.
An origin relationship describes how that basis connects to the origin of the governed value.
Example:
Industrial Robot
Value Source Basis:
automation capability
Value Origin Relationship:
automation capability → reduction of repetitive manual production effort → potential production-cost value
The capability exists independently.
The relationship explains why that capability matters to the particular governed value.
Relationship to the Governed Value Context
Every Value Origin Relationship must remain connected to the Value Context established under the Value Context Standard (VCXS).
The same source and the same capability may create different Value Origin Relationships depending upon:
value being governed; Value Object; beneficiary; purpose; reference framework; operational context.
For example:
Battery Storage System
may have the basis:
energy-storage capability
but different Value Origin Relationships:
energy storage → peak-demand reduction → cost value
energy storage → backup availability → resilience value
energy storage → renewable balancing → system-efficiency value
energy storage → reduced grid dependency → strategic value
The source is the same.
The basis may be the same.
The relationship to value is different.
Direct Value Origin Relationship
A Direct Value Origin Relationship exists where the established source basis contributes directly to the governed value pathway without requiring another independent value-producing mechanism between the source and the value.
Example:
Solar installation
→ electricity-generation capability → usable electricity generation → energy-production value.
Direct does not mean unconditional.
Conditions may still determine whether value actually emerges.
Indirect Value Origin Relationship
An Indirect Value Origin Relationship exists where the source contributes through one or more intermediate capabilities, processes, states, or outcomes.
Example:
Predictive maintenance system
→ failure-prediction capability → earlier maintenance intervention → reduced unplanned downtime → increased productive availability → operational value.
The source does not directly produce the final value.
It contributes through a governed value-origin pathway.
Enabling Value Origin Relationship
Some sources do not independently originate the governed value but enable another source to do so.
Example:
Charging infrastructure
→ access to energy replenishment → enables electric vehicle operation → supports transportation value.
The charging infrastructure may therefore hold an enabling relationship to transportation value even though it does not itself perform transportation.
Complementary Relationship
Value may require two or more sources whose bases complement one another.
Example:
AI Model
Operational Data Computational Infrastructure
may collectively support:
decision-support capability
which may contribute to:
faster or more accurate operational decisions.
None of the three sources may independently establish the complete value-origin pathway.
VORM therefore supports:
Multiple Sources → Complementary Origin Relationship → Governed Value
Dependent Relationship
A Value Origin Relationship may depend upon another source, capability, infrastructure, condition, or relationship.
Example:
High-speed manufacturing equipment
may possess substantial productive capability.
But its relationship to production value may depend upon:
electricity; trained operators; raw materials; software; maintenance; logistics; downstream demand.
VORM identifies material dependencies affecting the origin relationship.
VOCM subsequently governs the conditions under which that relationship can become operationally effective.
Sequential Relationship
Value may originate through a sequence.
For example:
Scientific Knowledge → engineering method → manufacturing capability → product performance → customer utility.
VORM allows the value-origin pathway to preserve intermediate stages rather than incorrectly attributing all value directly to the final visible source.
This is particularly important where organizations need to understand where value actually originates across complex systems.
Cumulative Relationship
Multiple small contributions may collectively support value even when no individual contribution is sufficient.
Example:
1% energy reduction
2% material reduction shorter production cycle lower maintenance requirement
may collectively produce substantial lifecycle cost value.
VORM can represent:
Multiple Value-Origin Contributions → Cumulative Value-Origin Relationship
without requiring each contribution to be treated as a separate final value.
Synergistic Relationship
Some combinations produce a value-origin capability greater than the contribution available from the sources independently.
For example:
high-quality data + AI model + domain expertise
may produce an analytical capability unavailable from any one component alone.
VORM may therefore identify a:
Synergistic Value Origin Relationship
where the relevant origin pathway depends upon the interaction between multiple sources.
VORM identifies the relationship.
It does not automatically quantify the resulting value.
Substitutive Relationship
Different Value Sources may provide alternative pathways toward the same governed value.
For example:
human inspection
and
machine-vision inspection
may both contribute to defect-detection value.
VORM may therefore represent:
Source A → Value Origin Pathway
and
Source B → Alternative Value Origin Pathway
This enables later comparison without assuming that the sources, costs, risks, or resulting value are identical.
Network Value Origin Relationship
In complex ecosystems, value may originate through a network rather than a linear chain.
Examples include:
payment networks; supply chains; telecommunications networks; digital platforms; logistics ecosystems; healthcare networks; financial markets; distributed energy systems; blockchain ecosystems; AI agent ecosystems.
VORM may map:
Source Network → Interdependent Bases → Relationship Network → Governed Value
This makes distributed value origin governable without forcing artificial attribution to one source.
Multi-Beneficiary Relationship
The same Value Source may contribute to different values for different beneficiaries.
Example:
A digital payment infrastructure may create:
for the customer:
transaction convenience
for the merchant:
payment acceptance capability
for the bank:
transaction-service capability
for the wider network:
interoperability and settlement efficiency.
VORM therefore preserves the beneficiary established in the Value Context.
Same Source ≠ Same Value Relationship for Every Beneficiary.
Positive and Protective Value-Origin
Relationships
A Value Origin Relationship does not need to produce additional output.
It may originate value by preserving an existing desirable state or preventing an undesirable state.
Examples include:
Cybersecurity capability → reduced probability of disruption → preservation of operational value.
Backup infrastructure → recovery capability → reduction of expected continuity loss.
Preventive maintenance → reduced failure exposure → preservation of productive capability.
This allows VFM® to recognize value originating through:
creation
and through:
preservation / avoided loss
without treating them as identical mechanisms.
Cost-Reduction Relationship
Cost reduction represents an important value-origin pathway.
VORM may establish relationships such as:
Reusable component → repeated-use capability → reduced replacement requirement → potential lifecycle cost value.
Automation system → automated execution capability → reduced manual processing requirement → potential process-cost value.
Energy optimization system → consumption optimization capability → reduced energy requirement → potential operating-cost value.
The Module identifies the relationship.
It does not yet declare that the savings have actually occurred.
Temporal Relationship
A source may contribute to value at different times.
A relationship may therefore be:
Immediate
Delayed
Recurring
Periodic
Long-Term
Dormant
Time-Bounded
Event-Triggered
For example, emergency infrastructure may remain unused for years while retaining a legitimate relationship to resilience value.
VORM must therefore avoid equating:
lack of current utilization
with
absence of Value Origin Relationship.
Latent Origin Relationship
A Value Origin Relationship may exist before the conditions necessary for value emergence are satisfied.
Example:
A patented technology possesses a technological basis and a defined relationship to potential manufacturing efficiency.
However:
production infrastructure may not yet exist; implementation cost may remain too high; complementary technology may be missing.
The relationship can therefore be classified as:
Latent Value Origin Relationship.
This preserves the distinction:
Origin Relationship Exists ≠ Value Has Emerged.
Relationship Strength
Where useful, organizations may characterize how strongly the identified source basis is connected to the governed value.
Possible governance states may include:
Primary
Material
Supporting
Enabling
Conditional
Marginal
Unresolved
These states do not represent universal monetary valuation.
They describe the role of the source within the value-origin structure.
Relationship Dependency
VORM requires material dependencies to remain visible where they affect the origin relationship.
A relationship may depend upon:
another Value Source; complementary capability; infrastructure; access; timing; knowledge; demand; resource availability; interoperability; external event; operational process.
Dependency must not be mistaken for Value Origin Condition.
VORM identifies what the relationship depends upon structurally.
VOCM determines which conditions must be satisfied for the origin pathway to operate.
Relationship Evidence
A claimed Value Origin Relationship should be supportable where materially relevant.
Support may include:
operational observation; technical evidence; historical performance; comparative analysis; financial records; scientific evidence; simulation; controlled testing; production data; empirical relationships; documented capability pathways.
VORM does not own general validation or evidence integrity.
Where required:
VALIDOS® may govern validation.
ADIT® may govern audit and evidence.
INTEGROS® may govern integrity.
VORM governs the value-origin relationship being asserted.
Relationship Change
A Value Origin Relationship may change even when the Value Source itself remains unchanged.
For example:
A technology may remain technically identical while:
a complementary infrastructure appears; market conditions change; another technology replaces part of its role; a new use is discovered; regulation changes access; operating costs change; interoperability improves.
The underlying source remains.
Its relationship to governed value may strengthen, weaken, disappear, or transform.
VORM therefore requires material relationship changes to remain identifiable.
Relationship Map
For complex value systems, VORM may produce a Value Origin Relationship Map.
A simplified structure may be:
Value Source A → Basis A → Contribution A
Value Source B → Basis B → Contribution B
Value Source C → Basis C → Enabling Contribution
↓
Combined Value Origin Relationship
↓
Governed Value
This allows VFM® to map where value may originate before later lifecycle stages determine whether that value actually emerges, changes, develops, degrades, reaches zero, is restored, or becomes extinct.
Minimum Implementation Framework
A practical VORM implementation should establish:
1. Value Source Input
Receive the identified Value Source from VSOIM.
2. Value Source Basis Input
Receive the established Value Source Basis from VSBM.
3. Governed Value Context
Identify the specific governed value, Value Object, beneficiary, purpose, and reference context.
4. Relationship Identification
Determine how the source basis connects to the potential origin of the governed value.
5. Relationship Type
Identify whether the relationship is direct, indirect, enabling, complementary, dependent, cumulative, sequential, synergistic, substitutive, network-based, or another relevant type.
6. Contribution Pathway
Document the pathway through which the source may contribute to the governed value.
7. Dependency Identification
Identify material structural dependencies affecting the relationship.
8. Relationship State
Determine whether the relationship is active, latent, conditional, weakened, interrupted, or unresolved.
9. Relationship Support
Identify the basis supporting the asserted relationship where required.
10. Value Origin Relationship Record
Create the governed relationship record for downstream Value Origin governance.
Governance Outputs
VORM may produce:
Value Origin Relationship Record Value Origin Relationship Type Value Contribution Pathway Direct Value Origin Relationship Record Indirect Value Origin Relationship Record Enabling Value Origin Relationship Record Complementary Value Origin Relationship Record Dependent Value Origin Relationship Record Sequential Value Origin Relationship Record Cumulative Value Origin Relationship Record Synergistic Value Origin Relationship Record Substitutive Value Origin Relationship Record Network Value Origin Relationship Map
Value Origin Dependency Record Value Origin Relationship State Value Origin Relationship Change Record
These outputs provide the governed input for:
VOCM — Value Origin Conditions Module.
Use Case 1 — Banking: From Data Capability to
Fraud-Loss Reduction
A bank identifies its transaction-data environment as a Value Source.
VSBM establishes:
transaction information and analytical capability
as relevant Value Source Bases.
VORM then establishes the relationship:
transaction data → pattern-analysis capability → earlier identification of suspicious activity → potential prevention or reduction of fraudulent transactions → potential avoided-loss value for the bank and affected customers.
This matters because the dataset itself is not the value.
Nor is analytical capability automatically value.
The value-origin relationship explains how those capabilities may contribute to an economically meaningful outcome.
If fraud detection does not actually prevent loss, the relationship may still exist while the expected value fails to emerge.
That distinction becomes critical when organizations assess investments in AI, analytics, cybersecurity, or financial infrastructure. Use Case 2 — Space Mission: Mapping the Origin of Reusability Value
A launch organization identifies a reusable launch system as a Value Source.
VSBM identifies multiple bases:
reusable propulsion
reusable structures rapid inspection capability operational learning refurbishment capability.
VORM maps how those bases relate to the governed value:
reusable hardware → reduced replacement requirement
rapid inspection → shorter turnaround
operational learning → improved repeat-mission execution
refurbishment capability → extended component utilization
Together:
multiple Value Source Bases → combined Value Origin Relationship → potential reduction in lifecycle mission resource requirements and cost.
The architecture therefore avoids the simplistic conclusion:
“Reusability = value.”
Instead, it identifies the actual pathways through which reusability may originate value.
VOCM can then determine whether the conditions necessary for those pathways to function are actually present.
Foundational Principles
A Value Source Basis must be connected to the governed value through an identifiable Value Origin Relationship.
Value Source Basis is not Value Origin Relationship.
Value Origin Relationship is not Value Emergence.
The same source may have multiple relationships to different forms of value.
The same source may create different value relationships for different beneficiaries.
Multiple sources may jointly support one Value Origin Relationship.
A Value Origin Relationship may be direct, indirect, enabling, dependent, cumulative, sequential, synergistic, substitutive, or network-based.
Avoided cost and avoided loss may form legitimate value-origin pathways.
A latent relationship may exist before value emerges.
Complex value should remain traceable to the sources, bases, relationships, and dependencies from which it can originate.
Canonical Closing Statement
Value Origin Relationship Module establishes the relational layer of Value Origin governance by defining how an identified Value Source and its established Value Source Basis connect to the potential origin of a specific governed value. Through governance of direct, indirect, enabling, complementary, dependent, cumulative, sequential, synergistic, substitutive, network-based, temporal, and latent relationships, VORM makes complex value-origin pathways explicit without prematurely declaring that value has emerged. By separating the existence of a source, the capability contained within that source, the relationship of that capability to value, and the later conditions under which value can actually emerge, VORM creates the governed relational structure necessary for determining where value comes from across financial, industrial, digital, scientific, infrastructure, and other complex systems.
Modul4