Value Origin Documentation Module (VODM)
Value Origin Documentation Module (VODM)
Architecture Ecosystem: Structured Reality Standards™
Architecture Family: VFM® — Value Flow Mechanism
Parent Standard: Value Origin Standard (VOS)
Module: VODM — Value Origin Documentation Module
Operational Layer: Value Origin Documentation Layer
Category: Governance & Enforcement
Subcategory: Value Lifecycle Governance
Type: Core Module
Governed Space: Value Origin Documentation
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 Documentation Module (VODM) is the fifth Core Module of the Value Origin Standard (VOS).
VODM governs the structured documentation of the complete governed basis through which the origin of a defined value can be identified, understood, reconstructed, compared, reviewed, and transferred into subsequent value lifecycle governance.
The Module consolidates the outputs of:
VSOIM — Value Source Identification Module VSBM — Value Source Basis Module VORM — Value Origin Relationship Module VOCM — Value Origin Conditions Module
into a coherent Value Origin Record.
VODM does not determine that value has emerged.
It establishes the documented origin basis required to understand:
where the governed value can originate, what within the source can contribute to it, how that contribution occurs, and under which conditions the value-origin pathway can operate.
The distinction is fundamental:
Documented Value Origin ≠ Existing Value
Architectural Position
VODM is the fifth and final Core Module of the Value Origin Standard.
It follows:
VOCM — Value Origin Conditions Module
and completes the internal Value Origin governance sequence:
Value Source Identification → Value Source Basis → Value Origin Relationship → Value Origin Conditions → Value Origin Documentation
VODM therefore creates the final governed record before the architecture proceeds from:
Value Origin
to:
Value Emergence.
Operational Purpose
The existence of a Value Source, Value Source Basis, Value Origin Relationship, and Value Origin Conditions is insufficient if those elements cannot be connected and reconstructed as one governed origin pathway.
VODM prevents Value Origin governance from becoming fragmented across:
isolated records; organizational departments; technical systems; financial models; contracts; operational databases; undocumented assumptions; institutional knowledge; individual expert knowledge; disconnected analytical outputs.
Its purpose is to create one reconstructable methodological chain:
Governed Value → Value Source → Value Source Basis → Value Origin Relationship → Value Origin Conditions → Origin Readiness → Value Origin Record
Operational Space
VODM governs documentation relating specifically to the origin of value.
This may include:
governed value reference; Value Source identity; Value Source description; Value Source Basis; source-to-value relationship; origin pathway; necessary Origin Conditions;
enabling Origin Conditions; critical Origin Conditions; alternative Origin Conditions; condition dependencies; condition thresholds; Origin Readiness; material limitations; temporal applicability; unresolved origin questions; changes affecting the origin basis; supporting references; Value Origin Record status.
VODM governs how these elements are assembled into a coherent value-origin record.
The Value Origin Record
The principal governance object produced by VODM is the:
Value Origin Record (VOR).
A Value Origin Record is the structured representation of the governed basis through which a defined value may originate.
At minimum, the record should answer:
What value is being governed?
What is the Value Source?
What within that source provides the basis for value?
How is that basis related to the governed value?
What conditions must exist for the relationship to operate?
What is the current Origin Readiness state?
What material dependencies or limitations affect the origin pathway?
This transforms Value Origin from a general statement into a reconstructable governance object.
Documentation Principle
VODM follows a simple rule:
A value-origin claim should be reconstructable from its documented basis.
A statement such as:
“This technology creates value.”
is insufficient as a governed Value Origin record.
VODM requires the statement to be decomposed.
For example:
Governed Value: reduced operational energy cost
Value Source: intelligent energy-management system
Value Source Basis: capability to optimize energy consumption
Value Origin Relationship: optimization of consumption can reduce unnecessary energy use, creating potential cost reduction
Origin Conditions: measurable consumption, controllable loads, usable optimization decisions, operational implementation, relevant energy-cost structure
Origin Readiness: Ready
The resulting record explains the origin pathway rather than merely asserting value.
Documentation ≠ Evidence Validation
VODM requires the basis of Value Origin to be documented.
It does not automatically determine that every statement contained within the record has been independently validated.
Where formal validation is required:
VALIDOS® may govern validation.
Where integrity must be governed:
INTEGROS® may govern integrity.
Where evidence and auditability are required:
ADIT® may govern audit and evidence.
VODM owns the Value Origin documentation structure.
This boundary prevents documentation from being mistaken for proof.
Source Documentation
The Value Origin Record should identify the relevant Value Source sufficiently for the governed value to remain connected to its origin.
Source documentation may include:
source name; source type; source reference; source configuration; source location where relevant; source version; source state; relevant capability; temporal applicability.
VODM does not replace identity governance.
Where formal identity, ownership, authority, provenance, or continuity is required, the relevant external architecture may govern those questions.
Value Source Basis Documentation
The record should identify what within the Value Source provides the basis from which value may originate.
Examples include:
Capability
Resource
Knowledge
Function
Relationship
Access
Capacity
Position
Process
Property
Opportunity
Infrastructure
The basis should be specific enough that the origin relationship can be understood independently of the general existence of the source.
Origin Relationship Documentation
VODM requires the relationship between:
Value Source Basis
and
Governed Value
to remain explicit.
The relationship should explain the pathway through which the source basis may contribute to the governed value.
For example:
Predictive Maintenance Capability
→ identifies developing equipment failure earlier → enables intervention before catastrophic failure → may reduce downtime and repair requirements → creates a pathway toward avoided-loss and continuity value.
The documentation should preserve the pathway rather than reducing it to:
“Predictive maintenance has value.”
Origin Conditions Documentation
Material conditions established through VOCM should remain connected to the relevant origin relationship.
The record may distinguish:
Necessary Conditions
Enabling Conditions
Supporting Conditions
Critical Conditions
Alternative Conditions
Threshold Conditions
Temporal Conditions
External Conditions
Internal Conditions
This makes it possible to determine why an origin pathway is:
Ready
or
Not Ready.
Dependency Documentation
Where Value Origin depends upon several interacting conditions, VODM should preserve the material dependency structure.
Example:
Manufacturing Value
depends upon:
Production Capability
Material Availability Energy Availability Qualified Personnel Operational Demand
Material Availability may itself depend upon:
Supplier Capability → Logistics → Delivery Access.
The Value Origin Record should make material dependencies visible where their failure can interrupt the origin pathway.
Alternative Origin Pathways
The same governed value may originate through multiple pathways.
VODM therefore supports documentation such as:
Governed Value
↙ Origin Pathway A ↘ Origin Pathway B ↘ Origin Pathway C
For example, operational cost reduction may originate through:
energy efficiency
or
automation
or
waste reduction
or
maintenance optimization.
These pathways should not be silently combined.
Each may have different:
Value Sources; Value Source Bases; relationships; conditions; dependencies; readiness states.
Multiple Sources of One Value
One governed value may depend upon multiple Value Sources.
Example:
Reduced Hospital Treatment Delay
may depend upon:
diagnostic capability
staff availability information availability coordination capability treatment capacity.
VODM may therefore represent a multi-source Value Origin Record.
This allows organizations to identify situations where no single asset or actor can legitimately be described as the sole origin of the governed value.
One Source, Multiple Values
A single Value Source may also support several different values.
For example, an industrial robot may contribute to:
production value
safety value
quality value
time value
cost value
capacity value.
VODM requires those values to remain separately identifiable where their origin relationships differ.
This prevents one broad statement such as:
“The robot creates value”
from obscuring multiple distinct value pathways.
Origin Record Status
A Value Origin Record may carry a governance status.
A practical minimum model may include:
1. Draft
The Value Origin basis is being documented.
2. Incomplete
Material elements required to reconstruct the origin pathway are missing.
3. Documented
The material Value Origin structure has been sufficiently recorded.
4. Conditionally Documented
The record is usable subject to explicitly identified unresolved conditions or limitations.
5. Superseded
A newer Value Origin Record has replaced the current record.
6. Archived
The record is retained for historical, comparative, or reconstruction purposes.
These statuses concern documentation.
They do not establish whether value exists.
Temporal Documentation
Value Origin is not necessarily static.
Sources may change.
Capabilities may change.
Relationships may change.
Conditions may change.
Dependencies may change.
The Value Origin Record should therefore identify its relevant temporal basis.
Where materially required, VODM may support:
Effective From
Effective Until
Review Date
Last Material Change
Superseding Record
This allows the architecture to distinguish historical Value Origin from current Value Origin.
Change Documentation
A material change to the origin basis should remain visible.
Examples include:
Value Source replacement; capability change; source degradation; new dependency; removed dependency; changed relationship; changed threshold; condition failure; condition restoration; new alternative pathway; change in beneficiary or context affecting the origin pathway.
The purpose is not to create unnecessary administrative history.
It is to preserve the ability to understand why the Value Origin pathway changed.
Unresolved Origin Questions
VODM should allow unresolved questions to remain explicit.
Examples:
Source basis not fully established
Dependency uncertain
Condition threshold unknown
Alternative source under assessment
Relationship partly understood
Origin Readiness indeterminate
An unresolved issue should not be hidden merely to create a complete-looking record.
A documented uncertainty is methodologically stronger than an undocumented assumption.
Documentation Granularity
VODM does not require every Value Origin Record to contain the same level of detail.
Documentation should be proportionate to:
complexity of the value; materiality; number of sources; number of beneficiaries; number of dependencies; operational significance; decision significance; lifecycle significance; expected downstream reliance.
A simple value pathway may require a compact record.
A national infrastructure project may require a complex multi-source Value Origin model.
Machine-Readable Value Origin
VODM should support machine-readable representation of Value Origin.
A machine-readable Value Origin Record may contain structured fields for:
Value Context ID
Value Source ID
Value Source Basis
Value Origin Relationship
Origin Condition IDs
Condition States
Origin Readiness State
Dependency Links
Temporal State
Record Version
Supporting References
This enables Value Origin governance to become usable by:
AI systems; financial systems; enterprise platforms; accounting systems; public administration; asset-management systems; digital twins; economic models; automated decision systems.
Value Origin Graph
For complex environments, VODM may represent Value Origin as a graph:
Value Source ↓ Value Source Basis ↓ Value Origin Relationship ↓ Origin Conditions ↓ Governed Value
Multiple sources and pathways can then be connected.
This enables organizations to analyze:
Where does this value originate?
Which sources contribute to it?
Which conditions are critical?
Which dependencies threaten it?
Which alternative origin pathways exist?
What happens if one source disappears?
The Value Origin Record therefore becomes more than documentation.
It becomes a navigable representation of value origin.
Transition to Value Emergence
VODM completes the governance of potential Value Origin.
The next architectural question is fundamentally different.
Value Origin asks:
Where can the governed value come from?
Value Emergence asks:
Has the governed value actually come into existence?
The transition is:
Documented Value Origin → Origin Readiness → Value-Producing Event / Condition / Interaction → Value Emergence Assessment
The existence of a complete Value Origin Record does not permit the architecture to skip this transition.
Therefore:
Documented Origin ≠ Emerged Value
Minimum Implementation Framework
A practical VODM implementation should establish:
1. Governed Value Reference
Connect the record to the Value Context established under VCXS.
2. Value Source Record
Document the identified Value Source or Sources.
3. Value Source Basis Record
Document the relevant capability, resource, relationship, condition, or other basis.
4. Value Origin Relationship Record
Document how the source basis may contribute to the governed value.
5. Value Origin Conditions Record
Document material conditions required for the origin pathway.
6. Dependency Record
Document material dependencies and alternative pathways.
7. Origin Readiness Record
Preserve the current readiness state established through VOCM.
8. Limitation and Uncertainty Record
Identify material limitations, unresolved questions, and uncertainty.
9. Temporal and Version Record
Identify the applicable time, version, and material changes.
10. Value Origin Record
Consolidate the complete governed origin basis into one reconstructable record.
Governance Outputs
VODM may produce:
Value Origin Record Value Origin Source Record Value Source Basis Record Value Origin Relationship Record Value Origin Conditions Record Value Origin Dependency Record Value Origin Pathway Map Alternative Value Origin Pathway Record Multi-Source Value Origin Record Origin Readiness Record Value Origin Limitation Record Value Origin Uncertainty Record Value Origin Change Record Value Origin Version Record Machine-Readable Value Origin Record
Value Origin Graph
These outputs complete the Value Origin Standard and provide the governed input for the next Parent Standard in the VFM® lifecycle.
Use Case 1 — Banking: Origin of Fraud-
Prevention Value
A bank deploys several capabilities intended to reduce fraud losses:
transaction monitoring
AI fraud detection
customer authentication
behavioral analytics
human investigation
payment intervention.
Without structured Value Origin documentation, the organization may record a general conclusion:
“The fraud platform creates CHF X in value.”
VODM decomposes that claim.
For avoided fraud-loss value, the Value Origin Record may establish:
Value Sources: detection models, transaction data, investigation capability, intervention mechanisms
Value Source Bases: anomaly detection, pattern recognition, human judgment, transaction blocking
Value Origin Relationships: earlier detection and intervention may prevent otherwise realizable fraud losses
Origin Conditions: relevant data, sufficiently early detection, operational alerts, investigation availability, intervention authority, actionable transaction state
Dependencies: payment infrastructure, data availability, model operation, staff response
Origin Readiness: Ready / Partially Ready / Interrupted depending upon the current condition state.
This allows the bank to distinguish between:
money spent on fraud capability
and
the actual governed pathway through which fraud-prevention value can originate.
The record can subsequently be compared with Value Emergence and later Value State information to determine whether the expected value actually came into existence.
Use Case 2 — Space Mission: Documenting the
Origin of Cost-Reduction Value
A space organization develops a reusable launch architecture intended to reduce mission costs.
The organization may have multiple potential Value Sources:
reusable launch vehicle
recoverable propulsion components
automated inspection
predictive maintenance
rapid refurbishment
operational learning from repeated missions.
VODM creates a structured origin model for the governed:
lifecycle cost-reduction value.
The record may show:
Reusable Vehicle → repeated component utilization
→ reduced replacement requirement
Automated Inspection → faster condition assessment → reduced inspection resource requirement
Predictive Maintenance → earlier intervention → reduced failure and repair exposure
Operational Learning → improved turnaround processes → reduced resource consumption per mission.
Each pathway receives its own conditions and dependencies.
The organization can therefore determine that the same cost-reduction value may originate from several interacting mechanisms rather than one asset.
If one pathway fails—for example, refurbishment becomes excessively expensive—the Value Origin Record still shows whether alternative pathways continue to support the governed value.
This gives mission planners a structured answer to a question that ordinary asset accounting does not fully answer:
Where does the expected lifecycle value actually come from?
Foundational Principles
Value Origin should be documented as a reconstructable pathway, not merely asserted.
A Value Source is not sufficient documentation of Value Origin.
The basis, relationship, conditions, and dependencies of value origin must remain distinguishable.
One source may originate multiple forms of value.
One value may originate from multiple sources.
Alternative Value Origin pathways should remain separately identifiable.
Documentation does not establish validation.
A complete Value Origin Record does not establish that value has emerged.
Material uncertainty should remain documented rather than hidden.
Value Origin documentation should remain proportionate to the complexity and significance of the governed value.
Machine-readable Value Origin can transform value from an assumed economic concept into a governable lifecycle object.
Canonical Closing Statement
Value Origin Documentation Module completes the Value Origin Standard by transforming the identified Value Source, Value Source Basis, Value Origin Relationship, Value Origin Conditions, dependencies, readiness state, limitations, uncertainty, temporal applicability, and material changes into a coherent and reconstructable Value Origin Record. By preserving the complete pathway through which a defined value may originate, VODM prevents value-origin claims from being reduced to unsupported assertions that an asset, technology, organization, activity, or capability simply “creates value.” The Module enables Value Origin to be represented as a documented, reviewable, comparable, and machine-readable governance object while preserving the critical distinction between potential origin and actual Value Emergence. VODM therefore closes the governance of where value can come from and creates the documented foundation required for VFM® to proceed to the next question in the value lifecycle: whether that value has actually come into existence.