RCMM — Resource Consumption Measurement Module
Architecture: RSGA™ — Resource Sustainability Governance Architecture
Parent Standard: Resource Consumption & Utilization Standard (RCUS)
Category: Governance & Enforcement
Subcategory: Resource Governance
Type: Core Module
Governed Space: Resource Consumption Measurement Governance
Module ID: RSGA-RCUS-RCMM-01
Origin ID: OOF-RSGA-RCUS-RCMM
Version: 1.0
Status: Draft Module
Effective Date: 7 October 2026
Compatibility: Methodology OS — Modular Compatibility
GIE-Compatible: Yes
AI-Readable: Yes
Authority: OOF® — OriginOpen® Foundation
Protection: Protected Methodological Work
Canonical Language: English
1. Canonical Definition
RCMM — Resource Consumption Measurement Module governs how the actual Consumption of a defined Resource is identified, bounded, measured, calculated or estimated where necessary, temporally and spatially contextualized, evidenced, validated, and represented as a governed Resource Consumption state.
RCMM establishes the measurement foundation required to distinguish what was actually consumed from what was merely:
available; accessible; allocated; reserved; withdrawn; occupied; transferred;
estimated; or expected to be consumed.
Its foundational distinction is:
Allocated Resource ≠ Consumed Resource.
Its measurement principle is:
Resource Quantity Without Measurement Boundary ≠ Governed Consumption Evidence.
2. Operational Role
RCUS requires operational evidence of actual Resource use.
RCMM establishes that evidence for Resource Consumption.
Its role is to determine:
what Resource is being measured; what constitutes Consumption for that Resource; which Resource boundary applies; which native measurement unit applies; when Consumption occurred; where Consumption occurred; from which Resource Source it occurred; how Consumption was measured; whether the measurement is direct or estimated; whether gross and net Consumption differ; what uncertainty exists; whether the evidence is sufficient; what governed Consumption state can be established.
RCMM therefore creates the measurement foundation upon which the wider Consumption & Utilization governance layer depends.
3. Operational Question
What quantity or capacity of the relevant Resource was actually consumed within the defined Resource, measurement, Source, location, purpose, and temporal boundary, using what measurement method and evidence, with what uncertainty, and with what resulting Resource Consumption state?
4. Position in RCUS Governance
Canonical progression:
Governed Resource Allocation → Actual Resource Use → Consumption Measurement → Utilization Determination → Resource-Use Attribution → Allocation-to-Use Comparison → Resource-Use State → Residual / Released Resource State → Reassessment
RCMM governs:
Actual Resource Use → Governed Resource Consumption Measurement
5. Governed Space
RCMM governs:
Resource Consumption Measurement Governance
This governed space concerns the determination of actual Resource Consumption through defined measurement boundaries, units, methods, evidence, uncertainty, and validation.
6. Governed Object
The primary Governed Object is:
A Resource Consumption Measurement associated with a defined Resource, measurement boundary, Resource Source, location, time interval, operational context, and evidence basis.
Canonical relationship:
**Resource
Measurement Boundary Consumption Definition Native Measurement Unit Measurement Method Operational Evidence Context → Resource Consumption Measurement → Resource Consumption State**
7. Scope
RCMM governs:
Consumption identification; Consumption definition; measurement boundaries; measurement points; native Resource units; gross Consumption; net Consumption; withdrawal measurement; return-flow measurement; Resource depletion; Resource transformation; Resource expenditure; Resource throughput where relevant; direct measurement; metered Consumption; telemetry-based measurement; inventory-based measurement; calculated Consumption; estimated Consumption; model-based estimation; measurement interval; temporal aggregation; spatial measurement; Source-specific measurement; measurement calibration evidence; measurement completeness; measurement uncertainty; measurement confidence; measurement conflict;
measurement gaps; evidence sufficiency; Consumption states; measurement reassessment; versioning; traceability.
RCMM does not independently:
determine Resource Utilization; determine whether Consumption was productive; determine Resource-use purpose legitimacy; determine Resource Allocation; determine Resource Priority; authorize Resource Access; determine Resource Scarcity; govern Resource Recovery; determine Resource Sustainability; determine Value; determine Harm; determine Liability.
8. Consumption Definition
Before Resource Consumption can be measured, the Resource-specific meaning of Consumption must be sufficiently defined.
Consumption may represent:
physical depletion; energy expenditure; material transformation; net withdrawal; capacity-time expenditure; irreversible use; other Resource-specific operational reduction or commitment.
9. Consumption Definition Boundary
Resource Use ≠ Resource Consumption by definition.
Different Resources may require different Consumption definitions.
10. Resource Identity
Every Consumption Measurement should identify the Resource to which the measurement applies.
11. Resource Type
The Resource type may determine:
measurement unit; measurement method; Consumption definition; measurement boundary; relevant uncertainty.
12. Resource Source
Where materially relevant, the Resource Source from which Consumption occurs should remain identifiable.
13. Source Boundary
Consumption of Resource Type X ≠ Consumption from Every Source of Resource Type X.
14. Measurement Boundary
Every governed Consumption Measurement should establish the boundary within which Resource Consumption is being determined.
The boundary may be:
physical; systemic; facility-level; process-level; device-level; organizational; geographic; temporal; Source-specific; other domain-appropriate boundary.
15. Boundary Principle
Resource Quantity Without Measurement Boundary ≠ Governed Consumption Evidence.
A quantity alone cannot establish what was consumed unless the included and excluded Resource flows are sufficiently understood.
16. Boundary Inclusion
RCMM should identify materially relevant Resource flows included in the measurement.
17. Boundary Exclusion
Material exclusions should remain explicit where they could affect interpretation.
18. Boundary Change
A material change in measurement boundary should remain visible.
19. Boundary Comparability
Consumption measurements using materially different boundaries should not be treated automatically as directly comparable.
20. Native Resource Unit
Consumption should be represented first in the applicable native Resource unit where sufficiently measurable.
Examples include:
kWh; MWh; litres; m³; kg; tonnes; litres of fuel; GPU-hours; CPU-hours; storage-byte-time; other Resource-specific units.
21. Native Measurement Principle
Native Resource Measurement ≠ Normalized Resource Significance.
Normalization may occur elsewhere where methodologically justified.
RCMM preserves the native measurement foundation.
22. Unit Definition
The applicable measurement unit should be sufficiently defined to prevent ambiguous interpretation.
23. Unit Consistency
Comparative Consumption measurements should use compatible units or governed conversions.
24. Unit Conversion
Where unit conversion occurs, the conversion basis should remain identifiable.
25. Conversion Boundary
Converted Quantity ≠ Original Measurement.
Both should remain distinguishable where traceability requires it.
26. Measurement Point
RCMM should identify where Resource Consumption is measured when the measurement point materially affects the result.
Examples may include:
Resource Source; facility inlet; system inlet; device input; process boundary; output boundary; return flow.
27. Measurement-Point Boundary
Same Resource Flow Measured at Different Points ≠ Necessarily Same Consumption Value.
Losses, transformations, returns, and intermediate use may occur between measurement points.
28. Gross Consumption
Gross Consumption may represent total Resource entering or being expended within the defined measurement boundary before applicable returns or adjustments.
29. Net Consumption
Net Consumption may represent Resource Consumption after defined:
returns; exports; releases; recovery-adjusted flows where methodologically appropriate; other valid Resource-specific adjustments.
30. Gross–Net Distinction
Gross Consumption ≠ Net Consumption.
The applicable measurement must state which quantity is being represented.
31. Withdrawal
For some Resources, Resource withdrawal is measurable independently of Resource Consumption.
32. Withdrawal Boundary
Resource Withdrawal ≠ Resource Consumption by definition.
Water provides a clear example.
Water may be withdrawn, used, partially consumed, and partially returned.
33. Return Flow
Where Resource returns materially affect net Consumption, RCMM should preserve the return flow.
34. Return-Flow Boundary
Returned Resource ≠ Automatically Equivalent to Original Resource State.
Quality, location, timing, temperature, contamination, or other conditions may differ.
35. Resource Depletion
Where Consumption reduces a Resource stock, RCMM should measure or estimate the depleted quantity where feasible.
36. Resource Transformation
Where Resource use transforms rather than destroys the Resource, the measurement should preserve the relevant transformation boundary.
37. Transformation Principle
Transformation ≠ Disappearance.
The resulting Resource state may remain relevant to downstream governance.
38. Energy Consumption
For energy Resources, Consumption may be measured as energy expended within the defined boundary.
39. Material Consumption
For material Resources, Consumption may involve:
incorporation into products; physical transformation; depletion; loss; discard; other Resource-specific pathways.
40. Capacity-Time Consumption
For some capacity Resources, Consumption may be represented through capacity-time.
Examples include:
GPU-hours; CPU-hours; machine-hours; storage-byte-time.
41. Capacity-Time Boundary
Capacity-Time Consumption ≠ Physical Resource Depletion.
The underlying physical asset may remain available after the Consumption interval.
42. Throughput Measurement
Where throughput is materially relevant, RCMM may measure Resource passing through the governed system.
43. Throughput Boundary
Throughput ≠ Net Consumption by definition.
44. Direct Measurement
Direct Measurement obtains Resource Consumption evidence directly from a measurement instrument or system designed to observe the relevant Resource quantity.
45. Metered Consumption
Metered Consumption is a form of Direct Measurement where a meter records Resource flow or expenditure.
46. Telemetry-Based Measurement
Operational telemetry may provide direct or near-direct Resource Consumption evidence depending upon the Resource and instrumentation.
47. Direct Measurement Boundary
Instrument Output ≠ Automatically Valid Consumption Evidence.
The instrument, measurement point, calibration, boundary, unit, and operational context remain relevant.
48. Calculated Consumption
Consumption may be calculated from measured variables where direct Consumption measurement is unavailable or unnecessary.
49. Calculation Basis
A calculated Consumption value should preserve:
input variables; formula or method; units; assumptions; time interval; applicable Resource context.
50. Estimated Consumption
Where direct measurement or sufficiently complete calculation is unavailable, Resource Consumption may be estimated.
51. Estimation Boundary
Estimated Consumption ≠ Directly Measured Consumption.
The distinction should remain visible in the governed state.
52. Estimation Method
The estimation method should be explicit.
Possible methods may include:
engineering estimate; statistical estimate; sampling; proxy measurement; model-based inference; historical extrapolation; other validated method.
53. Proxy Measurement
A proxy may be used where it has a sufficiently supported relationship to Resource Consumption.
54. Proxy Boundary
Correlated Signal ≠ Resource Consumption Measurement by itself.
The proxy relationship must be established.
55. Model-Based Estimation
A computational model may estimate Resource Consumption where the methodology and inputs are sufficiently governed.
56. Model Boundary
Model Output ≠ Measured Consumption.
57. Historical Estimation
Historical Resource-use patterns may support estimation where current direct measurement is unavailable.
58. Historical Boundary
Historical Consumption Pattern ≠ Current Consumption Fact.
59. Measurement Method Hierarchy
RCMM may preserve a hierarchy of evidence quality where appropriate.
For example:
direct measurement; validated calculation; validated estimation; proxy inference; unknown.
The hierarchy should reflect the Resource context rather than being treated as universally fixed.
60. Measurement Interval
Every Consumption Measurement should preserve the relevant time interval.
61. Instantaneous Measurement
Some Resource variables may be measured instantaneously but require integration over time to establish Consumption.
62. Interval Consumption
Consumption may be determined over:
seconds; minutes; hours; days; months; years; other operational intervals.
63. Temporal Aggregation
Consumption measurements may be aggregated across time where the underlying evidence permits.
64. Temporal Aggregation Boundary
Equal Total Consumption ≠ Equal Consumption Pattern.
Two systems may consume the same annual Resource quantity while producing radically different peak or temporal conditions.
65. Peak Consumption
RCMM should preserve peak Consumption where materially relevant.
66. Average Consumption
Average Consumption may support analysis but should not replace materially relevant peak evidence.
67. Average Boundary
Average Consumption ≠ Peak Consumption.
68. Temporal Granularity
The measurement interval should be sufficiently granular for the Resource governance question.
69. Temporal Granularity Boundary
Annual Measurement ≠ Sufficient Evidence for Hourly Constraint by definition.
70. Spatial Measurement
Resource Consumption may be measured at:
device; facility; site; district; region; network; other geographic level.
71. Spatial Aggregation
Consumption may be aggregated across locations where governance permits.
72. Spatial Boundary
Aggregate Consumption ≠ Local Consumption State.
Local Resource conditions may remain materially different.
73. Source-Specific Measurement
Where multiple Resource Sources supply the same operational system, Source-specific Consumption should remain identifiable where materially relevant.
74. Source Aggregation Boundary
Aggregate Resource Consumption ≠ Source-Neutral Consumption.
Source characteristics may matter to downstream governance.
75. Measurement Completeness
RCMM should determine whether the relevant Resource flows are sufficiently captured by the measurement system.
76. Partial Measurement
A measurement may represent only part of total Consumption.
Such evidence should not be silently represented as complete.
77. Measurement Coverage
Where useful:
Measurement Coverage = Measured Relevant Resource Scope / Defined Relevant Resource Scope
The exact implementation depends upon the Resource context.
78. Coverage Boundary
High Measurement Precision ≠ Complete Measurement Coverage.
A highly precise meter may measure only one part of the relevant Resource system.
79. Measurement Accuracy
Where evidence permits, RCMM should preserve information relevant to measurement accuracy.
80. Measurement Precision
Precision should remain distinguishable from accuracy.
81. Accuracy–Precision Boundary
High Precision ≠ High Accuracy.
82. Calibration
Where measurement devices require calibration, relevant calibration evidence should remain traceable where material.
83. Calibration Boundary
Device Present ≠ Device Validated.
84. Measurement Uncertainty
RCMM should preserve material uncertainty associated with Resource Consumption measurements.
85. Sources of Uncertainty
Uncertainty may arise from:
instrument tolerance; sampling; missing telemetry; estimated variables; conversion; boundary uncertainty; Source attribution; temporal aggregation; model assumptions.
86. Uncertainty Representation
Material uncertainty should be represented explicitly rather than hidden within an apparently exact number.
87. Uncertainty Boundary
Numerical Precision ≠ Measurement Certainty.
88. Measurement Confidence
Where useful, RCMM may establish a governed confidence state based on the available evidence.
89. Minimum Measurement Confidence States
At minimum:
High Confidence
Moderate Confidence
Limited Confidence
Evidence-Limited
Unknown
The exact thresholds should be defined by the applicable implementation context.
90. Measurement Gap
A Measurement Gap exists where materially relevant Consumption cannot be directly measured or sufficiently estimated.
91. Missing Data
Missing measurement data should remain identifiable.
92. Missing-Data Boundary
Missing Measurement ≠ Zero Consumption.
93. Gap Estimation
Where legitimate, missing intervals may be estimated using an established method.
94. Gap Estimation Boundary
Estimated Missing Interval ≠ Observed Interval.
95. Measurement Conflict
Measurement Conflict exists where materially relevant evidence sources produce incompatible Consumption values.
96. Conflict Preservation
Conflicting measurements should not be silently averaged where doing so would conceal a material governance issue.
97. Conflict Resolution
Resolution may require:
measurement-source validation; boundary comparison; time synchronization; unit validation; calibration review; evidence hierarchy; additional measurement.
98. Duplicate Measurement
Multiple measurement systems may observe the same Resource flow.
RCMM should prevent duplicate evidence from being automatically interpreted as additional Consumption.
99. Double-Counting Boundary
Multiple Records of the Same Resource Flow ≠ Multiple Consumption Events.
100. Measurement Synchronization
Where multiple data sources are combined, their temporal alignment may be materially relevant.
101. Measurement Validation
RCMM should validate whether the measurement is sufficiently suitable for the governed Consumption determination.
102. Minimum Validation Dimensions
Validation may include:
Resource identity; measurement boundary; measurement point; unit; method; time interval; Source; location; completeness; calibration where applicable; uncertainty; evidence provenance.
103. Consumption State
RCMM should establish a governed Resource Consumption State.
104. Minimum Consumption States
At minimum:
Not Consumed
Consumption Started
Consumption Active
Partially Consumed
Consumed
Consumption Suspended
Consumption Completed
Consumption Evidence-Limited
Consumption Conflicted
Consumption Unknown
Consumption Unresolved
105. Not Consumed
Sufficient evidence indicates that no Resource Consumption occurred within the defined boundary and period.
106. Zero Consumption Boundary
Measured Zero Consumption ≠ Missing Measurement.
These states must remain distinct.
107. Consumption Started
Evidence indicates that Resource Consumption has begun.
108. Consumption Active
Resource Consumption is currently occurring within the governed interval or operational state.
109. Partially Consumed
Only part of the relevant allocated, expected, available, or defined Resource quantity has been consumed.
110. Consumed
The relevant Resource quantity or governed Consumption condition has been consumed according to the applicable definition.
111. Consumption Suspended
Consumption has temporarily ceased while the Resource-use context remains open.
112. Consumption Completed
The governed Consumption interval or event has concluded.
113. Consumption Evidence-Limited
Available evidence supports only a limited Consumption determination.
114. Consumption Conflicted
Material evidence supports incompatible Consumption determinations.
115. Consumption Unknown
Available evidence is insufficient to determine whether or how much Resource was consumed.
116. Consumption Unresolved
Relevant evidence exists, but the final Consumption determination cannot yet be established.
117. Allocation Reference
Where Resource Consumption follows a governed Allocation, RCMM should preserve the relevant Allocation reference.
118. Allocation Boundary
Allocation Quantity ≠ Consumption Quantity.
Allocation provides context, not proof of Consumption.
119. Reserved Capacity Boundary
Reserved Resource ≠ Consumed Resource.
120. Accessible Resource Boundary
Accessible Resource ≠ Consumed Resource.
121. Available Resource Boundary
Available Resource ≠ Consumed Resource.
122. Demand Boundary
Validated Demand ≠ Actual Consumption.
Demand represents a Resource requirement.
Consumption represents operational Resource use.
123. Expected Consumption
A system may have an expected Consumption level.
Actual Consumption should remain distinguishable.
124. Expectation Boundary
Expected Consumption ≠ Actual Consumption.
125. Consumption Variance
Where an expected or allocated Consumption basis exists:
Consumption Variance = Actual Consumption − Reference Consumption
The reference must be explicit.
126. Variance Interpretation
Variance may support downstream governance but does not itself establish:
efficiency; waste; misuse; Scarcity; Value; Harm.
127. Resource Loss Measurement
Where Resource Loss is materially relevant to Consumption measurement, RCMM may quantify it within the defined boundary.
128. Loss Boundary
Measured Resource Loss ≠ Productive Resource Utilization.
129. Residual Resource Signal
RCMM may identify measurable Resource remaining after the primary Consumption process.
130. Residual Boundary
Measured Residual Resource ≠ Recovered Resource.
Recovery belongs to RRCS.
131. Released Capacity Signal
For capacity-based Resources, RCMM may identify the end of capacity-time Consumption and the resulting release signal.
132. Release Boundary
End of Capacity Consumption ≠ New Capacity Creation.
133. Measurement Evidence
Every material Consumption determination should be supported by sufficient evidence.
134. Evidence Types
Evidence may include:
meter readings; sensor telemetry; system logs; billing records; inventory records; engineering calculations; validated estimates; operational records; other Resource-specific evidence.
135. Evidence Provenance
Where relevant, evidence should preserve:
source; system; device; time; location; Resource; Resource Source; measurement method; version.
136. Evidence Freshness
Evidence should be sufficiently current for the Consumption state being determined.
137. Evidence Sufficiency
RCMM should determine whether available evidence is sufficient for the required Consumption determination.
138. Evidence Sufficiency Boundary
More Data ≠ Automatically Better Consumption Evidence.
Evidence relevance, boundary alignment, quality, and provenance matter.
139. Consumption Measurement Profile
The principal RCMM output is the:
Resource Consumption Measurement Profile
140. Minimum Resource Consumption Measurement Profile Fields
At minimum:
Consumption Measurement ID
Resource ID
Resource Type
Resource Source
Allocation Reference where applicable
Measurement Boundary
Measurement Point
Consumption Definition
Native Resource Unit
Original Measurement Unit
Converted Unit where applicable
Measurement Method
Direct / Calculated / Estimated State
Gross Consumption where applicable
Return Flow where applicable
Net Consumption where applicable
Actual Consumption
Measurement Start Time
Measurement End Time
Measurement Interval
Location
Measurement Coverage
Measurement Completeness State
Measurement Confidence
Measurement Uncertainty
Calibration Evidence where applicable
Evidence Basis
Evidence Sufficiency
Conflict State
Consumption State
Residual Resource Signal where relevant
Released Capacity Signal where relevant
Reassessment Trigger
Version:
141. Minimum Implementation Framework
A minimum operational RCMM implementation should contain eight governed layers.
Layer 1 — Resource & Consumption Definition
Establish:
Resource; Resource Type; Resource Source; what constitutes Consumption.
Layer 2 — Measurement Boundary
Establish:
included Resource flows; excluded flows; measurement point; location; time interval.
Layer 3 — Native Measurement
Establish:
native unit; measurement instrument or data source; gross / net basis; withdrawal / return relationship where relevant.
Layer 4 — Measurement Method
Determine:
direct measurement; calculation; estimation; proxy; model-based method.
Layer 5 — Measurement Validation
Evaluate:
coverage; completeness; unit consistency; calibration; time alignment; Source consistency.
Layer 6 — Uncertainty & Conflict
Determine:
measurement uncertainty; confidence; gaps; conflicting evidence; double-counting risk.
Layer 7 — Consumption Determination
Establish:
Actual Consumption; Consumption State; residual / release signals where relevant.
Layer 8 — Governed Output
Produce:
Resource Consumption Measurement Profile
Canonical machine-readable logic:
Resource → Consumption Definition → Measurement Boundary → Measurement Method → Measurement Evidence → Validation → Uncertainty / Conflict → Actual Consumption → Consumption State → Resource Consumption Measurement Profile
142. Minimum Decision States
At minimum:
Consumption Measured
Consumption Calculated
Consumption Estimated
Consumption Partially Measured
Consumption Evidence-Limited
Consumption Conflicted
Consumption Unknown
Consumption Unresolved
Measurement Reassessment Required
These measurement-decision states may coexist with the operational Consumption states defined above.
143. Minimum Evidence Path
Where actual Consumption cannot be sufficiently determined:
Consumption Unknown / Unresolved → Material Measurement Gap → Required Resource / Boundary / Interval → Minimum Evidence Requirement → Measurement / Evidence Acquisition → Measurement Validation → Consumption Redetermination → Resource Consumption Measurement Profile Update
144. Minimum Reassessment Framework
At minimum:
Current Resource Consumption Measurement Profile → New Evidence / Measurement Change → Materiality Test → Boundary / Method / Unit / Source Review → Evidence Validation → Consumption Recalculation / Re-estimation → Consumption State Confirmation or Modification → Profile Update → Version Update
145. Governance Requirements
A conforming RCMM implementation must:
1. identify the Resource; 2. identify the Resource type; 3. preserve Resource Source where material; 4. define what constitutes Consumption for the Resource; 5. establish the measurement boundary; 6. identify material boundary inclusions; 7. identify material boundary exclusions; 8. preserve boundary changes; 9. preserve boundary comparability; 10. use native Resource measurement where feasible; 11. identify the measurement unit; 12. preserve unit conversions; 13. identify the measurement point; 14. distinguish gross from net Consumption where applicable; 15. distinguish withdrawal from Consumption where applicable; 16. preserve return flows where relevant; 17. preserve Resource depletion where relevant; 18. preserve Resource transformation where relevant; 19. support capacity-time Consumption where relevant; 20. distinguish capacity-time Consumption from physical depletion; 21. preserve throughput where relevant; 22. support Direct Measurement; 23. support metered Consumption; 24. support telemetry-based measurement; 25. validate measurement context; 26. support calculated Consumption; 27. preserve calculation inputs and method; 28. support estimated Consumption where required; 29. preserve the estimation method; 30. support proxy measurement only where the proxy basis is established; 31. distinguish model output from measured Consumption; 32. distinguish historical patterns from current Consumption facts; 33. preserve measurement-method state;
34. identify the measurement interval; 35. support temporal aggregation; 36. preserve peak Consumption where relevant; 37. preserve sufficient temporal granularity; 38. preserve spatial measurement context; 39. preserve sufficient spatial granularity; 40. preserve Source-specific measurement where material; 41. determine measurement completeness; 42. identify partial measurement; 43. preserve measurement coverage; 44. distinguish precision from completeness; 45. preserve accuracy evidence where available; 46. distinguish precision from accuracy; 47. preserve calibration evidence where material; 48. preserve measurement uncertainty; 49. identify material uncertainty sources; 50. prevent numerical precision from being represented as certainty; 51. preserve measurement confidence where used; 52. identify measurement gaps; 53. prevent missing measurements from being interpreted as zero Consumption; 54. preserve estimated missing intervals; 55. distinguish estimated intervals from observed intervals; 56. identify measurement conflicts; 57. preserve unresolved conflicts; 58. prevent inappropriate averaging of materially conflicting evidence; 59. detect double-counting risk; 60. prevent duplicate records from becoming duplicate Consumption; 61. preserve time synchronization where relevant; 62. validate Resource identity; 63. validate measurement boundary; 64. validate measurement point; 65. validate units; 66. validate measurement method; 67. validate temporal context; 68. validate Source context; 69. validate location context; 70. establish Consumption state; 71. distinguish measured zero from missing measurement; 72. preserve Allocation references where applicable; 73. distinguish Allocation from Consumption; 74. distinguish reserved capacity from Consumption; 75. distinguish accessible Resource from Consumption; 76. distinguish available Resource from Consumption; 77. distinguish Demand from Consumption; 78. distinguish expected from actual Consumption; 79. support Consumption variance where applicable; 80. preserve Resource Loss measurement where relevant; 81. identify residual Resource signals where relevant; 82. identify released capacity signals where relevant; 83. preserve evidence provenance; 84. preserve evidence freshness; 85. determine evidence sufficiency; 86. support measurement reassessment; 87. preserve version history; 88. produce a Resource Consumption Measurement Profile.
146. Governance Logic
Canonical RCMM logic:
Resource Identification → Consumption Definition → Measurement Boundary
→ Measurement Point → Native Unit → Measurement Method → Resource-Use Evidence → Gross / Net Determination where applicable → Measurement Validation → Coverage / Completeness → Uncertainty / Conflict → Actual Consumption → Consumption State → Resource Consumption Measurement Profile → Reassessment
147. Governance Outputs
RCMM may produce:
Resource Consumption Measurement Profile
Actual Consumption
Gross Consumption
Net Consumption
Withdrawal Quantity
Return Flow
Resource Depletion
Resource Transformation Quantity
Capacity-Time Consumption
Resource Throughput
Measurement Boundary
Measurement Point
Native Resource Unit
Measurement Method State
Measurement Coverage
Measurement Completeness State
Measurement Confidence
Measurement Uncertainty
Measurement Gap
Measurement Conflict
Consumption Variance
Resource Loss Measurement
Residual Resource Signal
Released Capacity Signal
Consumption State
Evidence Sufficiency State
Reassessment Trigger
Version:
148. Critical Distinctions
Allocated Resource ≠ Consumed Resource
Resource Quantity Without Measurement Boundary ≠ Governed Consumption Evidence
Resource Use ≠ Resource Consumption by definition
Consumption of Resource Type X ≠ Consumption from Every Source of Resource Type X
Native Resource Measurement ≠ Normalized Resource Significance
Converted Quantity ≠ Original Measurement
Same Resource Flow Measured at Different Points ≠ Necessarily Same Consumption Value
Gross Consumption ≠ Net Consumption
Resource Withdrawal ≠ Resource Consumption by definition
Returned Resource ≠ Automatically Equivalent to Original Resource State
Transformation ≠ Disappearance
Capacity-Time Consumption ≠ Physical Resource Depletion
Throughput ≠ Net Consumption by definition
Instrument Output ≠ Automatically Valid Consumption Evidence
Estimated Consumption ≠ Directly Measured Consumption
Correlated Signal ≠ Resource Consumption Measurement by itself
Model Output ≠ Measured Consumption
Historical Consumption Pattern ≠ Current Consumption Fact
Equal Total Consumption ≠ Equal Consumption Pattern
Average Consumption ≠ Peak Consumption
Annual Measurement ≠ Sufficient Evidence for Hourly Constraint by definition
Aggregate Consumption ≠ Local Consumption State
Aggregate Resource Consumption ≠ Source-Neutral Consumption
High Measurement Precision ≠ Complete Measurement Coverage
High Precision ≠ High Accuracy
Device Present ≠ Device Validated
Numerical Precision ≠ Measurement Certainty
Missing Measurement ≠ Zero Consumption
Estimated Missing Interval ≠ Observed Interval
Multiple Records of the Same Resource Flow ≠ Multiple Consumption Events
Measured Zero Consumption ≠ Missing Measurement
Allocation Quantity ≠ Consumption Quantity
Reserved Resource ≠ Consumed Resource
Accessible Resource ≠ Consumed Resource
Available Resource ≠ Consumed Resource
Validated Demand ≠ Actual Consumption
Expected Consumption ≠ Actual Consumption
Measured Resource Loss ≠ Productive Resource Utilization
Measured Residual Resource ≠ Recovered Resource
End of Capacity Consumption ≠ New Capacity Creation
More Data ≠ Automatically Better Consumption Evidence
149. Cross-Architecture Boundary
RCMM may consume:
RCHS — Resource identity, Resource type, Source, state, and context.
RACS — Availability and capacity evidence.
RDGS — Demand evidence without treating Demand as Consumption.
RAGS — Resource Access context.
RPAS — Resource Allocation evidence without treating Allocation as Consumption.
RCUS — Parent Standard governance context for Consumption and Utilization.
RSCS — Scarcity context where Consumption measurement occurs under constrained conditions.
RRCS — downstream Recovery evidence without RCMM governing Recovery.
RIRS — Resource interdependency evidence where measurement boundaries span dependent systems.
ORA™ — operational reality evidence.
PGA™ — predicted Consumption evidence without treating prediction as measurement.
SIMULOS® — simulated Consumption evidence without treating simulation as observed Consumption.
VEGA™ — Resource-use and efficiency analysis where Consumption evidence is required.
RCMM does not absorb these mechanisms.
150. Cross-Architecture Mechanism Principle
An operational mechanism may produce inputs for multiple governance architectures, but it belongs only to the architecture whose governed domain includes that mechanism itself. Other architectures govern only its domain- specific relevance or consequences.
RCMM governs Resource Consumption Measurement.
It may produce evidence for:
Utilization governance; Allocation reassessment; Scarcity governance; Recovery governance; Resilience governance; Sustainability governance; Value governance.
Those mechanisms remain within their competent governance domains.
151. Canonical Boundary
RCMM governs how actual Resource Consumption is defined, bounded, measured, calculated or estimated, temporally and spatially contextualized, validated, evidenced, represented, and reassessed, including native units, measurement points, gross and net Consumption, withdrawal and return flows, capacity-time Consumption, measurement coverage, uncertainty, conflict, and Consumption state.
It does not determine Resource Utilization, Resource-use productivity, Resource Allocation, Resource Priority, Access authorization, Scarcity, Recovery, Sustainability, Value, Harm, or Liability.
Its principal governed output is the Resource Consumption Measurement Profile .
152. Canonical Closing Statement
Resource Consumption cannot be governed merely because a number exists. Governance must know what was measured, within which boundary, at which point, in which unit, during which period, from which Source, by which method, and with what uncertainty.
RCMM establishes that measurement foundation — converting Resource use from an assumed or reported quantity into bounded, evidenced, traceable, and reassessable Resource Consumption.