RCBM — Resource Consumption Boundary 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 Boundary Governance

Module ID: RSGA-RCUS-RCBM-03

Origin ID: OOF-RSGA-RCUS-RCBM

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

RCBM — Resource Consumption Boundary Module governs how the system, process, activity, infrastructure, Resource flow, Source, location, temporal interval, organizational scope, functional scope, and other materially relevant inclusion and exclusion boundaries used to determine Resource Consumption are established, evidenced, maintained, compared, and reassessed.

RCBM determines what belongs inside a Resource Consumption determination and what remains outside it .

It prevents Resource Consumption evidence from becoming misleading through:

undefined boundaries; selective exclusions; boundary shifting; duplicate inclusion; uncontrolled aggregation; inconsistent temporal scopes; inconsistent spatial scopes; Source substitution; direct–indirect Consumption confusion; or comparison between materially different Consumption boundaries.

Its foundational principle is:

Resource Quantity Without a Defined Consumption Boundary ≠ Governed Resource Consumption.

Its comparability principle is:

Equal Resource Quantity Across Different Boundaries ≠ Equivalent Resource Consumption Evidence.

2. Operational Role

RCMM determines actual Resource Consumption.

RUSM determines actual Resource Utilization State.

RCBM establishes the boundary within which Resource Consumption evidence is interpreted.

A Consumption value may be numerically correct while still being governance-incomplete if its boundary is unclear.

For example, electricity Consumption attributed to an AI workload may include only direct compute electricity or may also include:

cooling; storage; networking; power conversion; facility overhead; other supporting infrastructure.

Both measurements may be legitimate.

They do not represent the same Consumption boundary.

RCBM makes that difference explicit.

Its operational role is to establish:

which Resource flows are included; which Resource flows are excluded; which system or process is governed; which infrastructure is included; which Resource Sources are included; which locations are included; which time interval applies; which organizational and functional scope applies; whether direct and indirect Consumption are included; how shared Resource Consumption is bounded; whether boundary changes have occurred; whether two Consumption measurements are sufficiently comparable.

3. Operational Question

What system, process, activity, infrastructure, Resource flow, Source, location, time interval, organizational scope, functional scope, and direct or indirect Resource-use components must be included or excluded so that the relevant Resource Consumption determination is bounded, traceable, non-duplicative, and sufficiently comparable for its intended governance purpose?

4. Position in RCUS Governance

Canonical progression:

Governed Resource Allocation → Actual Resource Use → Resource Consumption Measurement → Resource Utilization State → Resource Consumption Boundary → Resource-Use Attribution → Allocation-to-Use Comparison → Resource-Use Condition → Residual / Released Resource State → Reassessment

RCBM governs:

Resource Consumption Context → Inclusion / Exclusion Logic → Governed Resource Consumption Boundary

5. Governed Space

RCBM governs:

Resource Consumption Boundary Governance

This governed space concerns the definition, maintenance, comparison, and reassessment of the boundaries within which Resource Consumption is measured, attributed, aggregated, compared, and interpreted.

6. Governed Object

The primary Governed Object is:

A Resource Consumption Boundary defining the included and excluded Resource flows, systems, processes, activities, infrastructure, Sources, locations, time intervals, organizational entities, functions, and other materially relevant elements associated with a Resource Consumption determination.

Canonical relationship:

**Governance Purpose

Resource Governed System / Process Resource Flows Infrastructure Source Context Spatial Context Temporal Context Organizational / Functional Context → Inclusion / Exclusion Determination → Resource Consumption Boundary**

7. Scope

RCBM governs:

Consumption-boundary definition; boundary purpose; system boundaries; process boundaries; activity boundaries; infrastructure boundaries; Resource-flow boundaries; Resource Source boundaries; spatial boundaries; temporal boundaries; organizational boundaries; functional boundaries; purpose boundaries; direct Consumption boundaries; indirect Consumption boundaries; upstream and downstream inclusion where applicable; shared-infrastructure boundaries; shared-Resource boundaries; measurement-point alignment; boundary inclusion; boundary exclusion; material exclusions; boundary completeness; boundary consistency; boundary hierarchy; nested boundaries; boundary aggregation; boundary decomposition; double-counting prevention; boundary overlap; boundary gaps; boundary conflict; boundary equivalence; comparability; boundary normalization where legitimate; boundary change; boundary drift; boundary versioning; boundary evidence; boundary uncertainty; reassessment; traceability.

RCBM does not independently:

measure Resource Consumption; determine Resource Utilization State; determine final Resource-use attribution; determine Resource Demand; authorize Resource Access; determine Resource Priority or Allocation; determine Scarcity; govern Recovery; determine Value; determine Harm; determine Liability; determine long-term Sustainability.

8. Consumption Boundary

A Resource Consumption Boundary defines the scope within which Resource Consumption is determined.

It establishes:

what is counted; what is not counted; where counting begins; where counting ends; when the boundary applies; which Resource flows belong to it; which systems and activities belong to it.

9. Boundary Purpose

Every material Consumption Boundary should have an identifiable governance purpose.

Possible purposes include:

operational monitoring; Allocation review; Demand reassessment; capacity planning; Scarcity analysis; efficiency evaluation; Value evaluation; Sustainability analysis; comparative benchmarking.

10. Purpose Boundary

Same Resource System + Different Governance Purpose ≠ Automatically Same Appropriate Consumption Boundary.

The appropriate boundary may depend upon the governance question.

11. Boundary Definition Principle

Resource Quantity Without a Defined Consumption Boundary ≠ Governed Resource Consumption.

A numerical Consumption value should not be interpreted independently of the boundary that produced it.

12. System Boundary

A System Boundary defines which technical or operational systems are included in the Consumption determination.

Examples may include:

single machine; server; AI cluster; data center; factory; water-treatment plant; transport network; regional Resource system.

13. System Boundary Distinction

Component Consumption ≠ System Consumption.

A component may represent only part of the Resource use required by the larger system.

14. Process Boundary

A Process Boundary defines which operational processes belong to the Consumption determination.

15. Process Boundary Distinction

Primary Process Consumption ≠ Total Operational Consumption by definition.

Supporting processes may materially consume Resources.

16. Activity Boundary

An Activity Boundary identifies which activities are included in Resource Consumption.

Examples may include:

production; training; inference; cooling; storage; transport; maintenance; monitoring; standby operation.

17. Activity Boundary Distinction

Primary Activity ≠ Entire Resource-Use System.

18. Infrastructure Boundary

Resource Consumption may depend upon infrastructure supporting the governed activity.

Relevant infrastructure may include:

cooling systems; power conversion; networking; storage; pumps; ventilation; transport; control systems; other support infrastructure.

19. Infrastructure Inclusion

Infrastructure Consumption should be included where the selected Consumption Boundary requires it and sufficient attribution is possible.

20. Infrastructure Exclusion

Infrastructure may legitimately remain outside a boundary where the governance purpose requires a narrower measurement.

The exclusion should remain explicit where material.

21. Infrastructure Boundary Principle

Excluded Infrastructure Consumption ≠ Nonexistent Infrastructure Consumption.

22. Resource-Flow Boundary

RCBM should identify the Resource flows entering, leaving, circulating within, or returning from the governed boundary where materially relevant.

23. Inflow

Resource entering the governed boundary should be identifiable where relevant.

24. Outflow

Resource leaving the governed boundary should be identifiable where relevant.

25. Return Flow

Resource returned after use may cross the Consumption Boundary again.

RCBM should prevent return flows from being confused with new Consumption.

26. Internal Resource Flow

Resource movement entirely within the defined boundary should not automatically be counted as new Resource Consumption.

27. Internal-Flow Principle

Internal Resource Transfer ≠ New Resource Consumption.

28. Boundary Crossing

A Resource crossing a boundary does not automatically mean it was consumed.

29. Boundary-Crossing Principle

Resource Entry ≠ Resource Consumption.

Resource Exit ≠ Resource Recovery.

30. Resource Source Boundary

A Consumption Boundary may include:

one Source; multiple Sources; Source classes; all Sources supplying the governed system.

31. Source-Specific Boundary

Where Source materially affects governance, Consumption should remain distinguishable by Source.

32. Source Aggregation

Multiple Sources may be aggregated only where aggregation is appropriate for the governance purpose.

33. Source Boundary Principle

Same Resource Type ≠ Same Resource Source.

34. Source Substitution

Where one Source replaces another during the measurement period, the boundary should preserve the change where material.

35. Source-Shifting Boundary

Stable Total Consumption ≠ Stable Source Composition.

36. Spatial Boundary

RCBM should define the physical or geographic area within which Consumption is governed.

Possible boundaries include:

device; room; building; facility; campus; district; city; region; country; network; other defined area.

37. Spatial Aggregation

Consumption may be aggregated across multiple locations where legitimate.

38. Spatial Aggregation Principle

Aggregate Consumption ≠ Local Consumption Condition.

39. Spatial Boundary Shift

Moving Resource-intensive activity from one location to another may reduce Consumption inside one boundary while leaving total Consumption unchanged or increased.

40. Spatial-Shifting Principle

Reduced Consumption Within Boundary A ≠ Reduced Total Resource Consumption.

41. Temporal Boundary

Every Consumption Boundary should define the applicable time interval.

Examples include:

event; second; minute; hour; day; month; season; year; operational lifecycle.

42. Temporal Alignment

Consumption comparisons should use sufficiently aligned temporal boundaries.

43. Temporal Boundary Principle

Equal Resource Quantity Across Different Time Windows ≠ Equivalent Resource-Use Pattern.

44. Partial-Period Boundary

A partial measurement period should not be represented as a complete period without an explicit basis.

45. Temporal Boundary Shift

Changing the start or end of a measurement interval may materially alter the reported Consumption.

46. Temporal-Shifting Principle

Reduced Consumption in One Reporting Period ≠ Reduced Consumption Across the Full Operational Period.

47. Organizational Boundary

A Consumption Boundary may correspond to:

organization; business unit; department; operator; facility owner; service provider; other responsible organizational scope.

48. Organizational Transfer

Moving Resource-consuming activity to another organization may alter organizational Consumption without changing total Resource Consumption.

49. Organizational-Shifting Principle

Transferred Consumption ≠ Eliminated Consumption.

50. Functional Boundary

Consumption may be bounded by operational function.

Examples include:

production; safety; cooling; compute; transport; storage; maintenance.

51. Functional Separation

Where materially possible, different functions should remain distinguishable.

52. Functional Aggregation

Functions may be aggregated where the governance purpose permits.

53. Functional Boundary Principle

Total Facility Consumption ≠ Consumption of Every Individual Function.

54. Purpose Boundary

A Consumption Boundary may be defined around a governed purpose.

55. Purpose-Specific Consumption

Where Resource use is purpose-specific, the boundary should preserve the relevant purpose where evidence permits.

56. Purpose Boundary Principle

Same Resource + Same System ≠ Same Consumption Purpose.

57. Direct Consumption Boundary

Direct Consumption represents Resource use occurring directly within the governed system, process, activity, or participant boundary.

58. Indirect Consumption Boundary

Indirect Consumption may arise through supporting systems or upstream/downstream processes materially associated with the governed activity.

59. Direct–Indirect Distinction

Direct Consumption ≠ Total Resource Dependency Footprint by definition.

60. Indirect Inclusion

Indirect Consumption should be included only where:

the governance purpose requires it; the causal or allocation basis is sufficiently established; double counting can be controlled; evidence is sufficiently reliable.

61. Indirect Attribution Boundary

Association ≠ Sufficient Basis for Indirect Consumption Attribution.

62. Upstream Consumption

A Resource-use boundary may include upstream Resource Consumption where the governance purpose explicitly requires it.

63. Downstream Consumption

Downstream Resource Consumption may similarly be included where justified.

64. Lifecycle Boundary

A broader Consumption Boundary may span multiple lifecycle stages.

65. Lifecycle Boundary Principle

Operational Consumption ≠ Lifecycle Consumption.

66. Embedded Resource Use

Products, services, infrastructure, or materials may contain embedded Resource Consumption from prior processes.

RCBM may define whether such Resource use belongs within the relevant boundary.

67. Embedded-Use Principle

Embedded Resource Consumption ≠ Current Operational Consumption.

68. Shared Infrastructure

Multiple governed activities may depend upon the same Resource-consuming infrastructure.

69. Shared-Infrastructure Boundary

RCBM should determine whether and how shared infrastructure falls within each relevant Consumption Boundary.

70. Shared-Infrastructure Principle

Shared Infrastructure Consumption ≠ Automatically Full Consumption of Every Participant.

71. Shared Resource Pool

Multiple participants may draw Resource from a common Resource pool.

The Consumption Boundary should prevent shared pool Consumption from being duplicated across participants.

72. Double Counting

Double Counting occurs when the same Resource Consumption is represented more than once within an aggregate governance result.

73. Double-Counting Principle

Multiple Attribution Records ≠ Multiple Physical Consumption Events.

74. Double-Counting Prevention

RCBM should identify:

Resource flow identity; measurement point; time interval; Source; participant; system; aggregation relationship

where necessary to prevent duplicate inclusion.

75. Boundary Overlap

Two Consumption Boundaries may overlap.

Overlap should be identified where combined results could double count Resource use.

76. Boundary Overlap Principle

Overlapping Consumption Boundaries ≠ Additive Consumption by default.

77. Boundary Gap

A Boundary Gap exists where materially relevant Resource Consumption falls outside all intended measurement boundaries.

78. Boundary-Gap Principle

Unassigned Consumption ≠ Zero Consumption.

79. Boundary Completeness

RCBM should determine whether the defined boundary sufficiently covers the Resource Consumption relevant to the governance purpose.

80. Completeness Boundary

Complete Measurement Inside an Incomplete Boundary ≠ Complete Resource Consumption Evidence.

81. Boundary Materiality

Not every excluded Resource flow is materially relevant.

RCBM should distinguish material from immaterial exclusions where appropriate.

82. Material Exclusion

A Material Exclusion is an excluded Resource-use component capable of materially affecting the intended governance interpretation.

83. Materiality Principle

Small Number of Exclusions ≠ Immaterial Boundary Effect.

One excluded component may dominate Resource Consumption.

84. Boundary Hierarchy

Consumption Boundaries may form a hierarchy.

Example:

Device → Rack → Data Hall → Data Center → Campus → Regional Infrastructure

or:

Process → Production Line → Facility → Company → Supply Network

85. Parent Boundary

A Parent Boundary may contain multiple subordinate Consumption Boundaries.

86. Child Boundary

A Child Boundary represents a narrower governed Consumption scope within a Parent Boundary.

87. Hierarchy Principle

Sum of Child Boundaries ≠ Parent Boundary Automatically.

Shared Resource use, losses, infrastructure, and unassigned Consumption may prevent direct equivalence.

88. Nested Boundaries

Nested Consumption Boundaries should preserve their inclusion relationships where relevant.

89. Boundary Decomposition

A broader boundary may be decomposed into smaller Resource-use components.

90. Decomposition Principle

Boundary Decomposition ≠ Automatic Attribution Accuracy.

91. Boundary Aggregation

Multiple Consumption Boundaries may be aggregated into a broader Resource Consumption view.

92. Aggregation Requirements

Aggregation should consider:

unit compatibility; temporal alignment; spatial relationship;

Source relationship; overlap; shared Resource flows; double-counting risk; boundary completeness.

93. Aggregation Principle

Mathematically Addable Consumption Values ≠ Governance-Compatible Consumption Values.

94. Boundary Equivalence

Two Consumption Boundaries are equivalent only when their materially relevant inclusion and exclusion logic is sufficiently aligned for the intended governance purpose.

95. Boundary Comparability

Boundaries may be:

Equivalent

Comparable with Adjustment

Partially Comparable

Not Comparable

Comparability Unknown

96. Comparability Principle

Same Unit ≠ Same Boundary.

97. Boundary Adjustment

Where legitimate, Consumption evidence may be adjusted to create a sufficiently comparable boundary.

The adjustment method should remain explicit.

98. Adjustment Boundary

Adjusted Consumption ≠ Original Consumption Measurement.

99. Boundary Normalization

Normalization may support comparison across different Consumption Boundaries where a valid methodology exists.

100. Normalization Principle

Normalized Consumption ≠ Physical Boundary Equivalence.

101. Boundary Consistency

Repeated measurements intended for trend analysis should preserve sufficiently consistent boundaries.

102. Boundary Drift

Boundary Drift occurs when the practical inclusion or exclusion scope changes over time without an explicit governance decision.

103. Boundary-Drift Principle

Stable Boundary Label ≠ Stable Boundary Definition.

104. Boundary Change

A Consumption Boundary may legitimately change because of:

system expansion; infrastructure change; Source change; organizational change; process redesign; measurement improvement; governance-purpose change; Resource-flow change.

105. Boundary Change Control

Material boundary changes should be:

identified; justified; dated; versioned; traceable.

106. Historical Comparability

When boundaries change, historical comparisons should indicate whether prior Consumption remains directly comparable.

107. Historical Boundary Principle

Historical Consumption Under Boundary A ≠ Current Consumption Under Boundary B by default.

108. Boundary Version

Each materially distinct Consumption Boundary should have a version or equivalent traceable state.

109. Boundary Validity Period

A boundary should preserve the period during which it applies where temporal validity matters.

110. Boundary Evidence

Boundary decisions should be supported by evidence appropriate to the Resource and governance purpose.

111. Boundary Evidence Types

Evidence may include:

system architecture; Resource-flow diagrams; meter topology; facility plans; process maps; Source records; organizational records; operational telemetry; measurement documentation; allocation records; other relevant evidence.

112. Boundary Evidence Sufficiency

RCBM should determine whether available evidence sufficiently supports the boundary definition.

113. Boundary Uncertainty

Where inclusion or exclusion cannot be established with sufficient confidence, uncertainty should remain visible.

114. Boundary Conflict

Boundary Conflict exists where legitimate evidence or governance requirements support incompatible boundary definitions.

115. Conflict Principle

Boundary Conflict ≠ Permission to Select the Most Favorable Boundary.

116. Boundary Unknown

Where the Consumption Boundary cannot be sufficiently established, RCBM should support an Unknown state.

117. Unknown Boundary Principle

Undefined Boundary ≠ Zero Consumption.

118. Boundary Manipulation

A Consumption Boundary should not be narrowed, widened, shifted, or otherwise modified solely to produce a preferred Resource Consumption result.

119. Boundary-Shifting Risk

Boundary shifting may make Resource performance appear improved without reducing total Resource Consumption.

120. Boundary-Shifting Principle

Consumption Moved Outside the Reporting Boundary ≠ Consumption Eliminated.

121. Outsourcing Boundary

Outsourcing a Resource-intensive activity may reduce direct organizational Consumption while leaving broader system Consumption unchanged.

122. Outsourcing Principle

Outsourced Consumption ≠ Eliminated Consumption.

123. Cloud / External Infrastructure Boundary

Use of external infrastructure may move Resource Consumption outside the user's physical facility.

RCBM should preserve whether such Consumption is inside or outside the selected boundary.

124. Externalization Principle

Externally Consumed Resource ≠ Zero Resource Consumption.

125. Efficiency Boundary Integrity

Resource efficiency comparisons require sufficiently aligned Consumption Boundaries.

126. Efficiency Comparison Principle

Lower Consumption Under a Narrower Boundary ≠ Demonstrated Resource Efficiency Improvement.

127. Value Comparison Boundary

Where Consumption is compared with Value, both the Resource Consumption Boundary and Value context should be sufficiently explicit.

128. Value Boundary Principle

Same Value Output + Different Consumption Boundaries ≠ Directly Comparable Resource Productivity by default.

129. Scarcity Boundary Context

Resource Consumption boundaries may affect Scarcity analysis.

Local Consumption can matter even when aggregate Resource Consumption appears manageable.

RCBM supplies boundary evidence but does not determine Scarcity.

130. Recovery Boundary Context

Residual Resource may cross the Consumption Boundary after primary use.

RCBM identifies the boundary relationship without governing Recovery.

131. Interdependency Boundary Context

Resource Consumption may depend upon other Resource systems.

RCBM may preserve those boundary relationships without absorbing interdependency governance.

132. Prediction Boundary

Predicted Consumption may use a defined future boundary.

133. Prediction Distinction

Predicted Consumption Boundary ≠ Observed Consumption Boundary unless explicitly aligned.

134. Simulation Boundary

Simulation may model alternative Resource Consumption boundaries.

135. Simulation Distinction

Simulated Boundary ≠ Operational Boundary by default.

136. Automated Boundary Assignment

Software may automatically classify Resource flows into boundaries.

137. Automation Boundary

Automated Classification ≠ Boundary Authority.

138. Boundary Authority

Where boundary definition materially affects governance decisions, the authority or methodology under which the boundary is established should remain identifiable.

139. Technical Configuration Boundary

A technical system may enforce or implement a boundary.

That does not itself establish governance legitimacy.

Technical Boundary Configuration ≠ Governance Boundary Authority.

140. Resource Consumption Boundary Profile

The principal RCBM output is the:

Resource Consumption Boundary Profile

141. Minimum Resource Consumption Boundary Profile Fields

At minimum:

Boundary ID

Resource ID

Governance Purpose

Boundary Name

Boundary Type

Governed System / Process / Activity

Included Resource Flows

Excluded Resource Flows

Material Exclusions

Included Infrastructure

Excluded Infrastructure

Resource Source Scope

Spatial Scope

Temporal Scope

Organizational Scope

Functional Scope

Purpose Scope

Direct Consumption Inclusion

Indirect Consumption Inclusion

Upstream Scope where applicable

Downstream Scope where applicable

Measurement Points

Parent Boundary where applicable

Child Boundaries where applicable

Overlap References

Boundary Gap State

Double-Counting Risk

Completeness State

Comparability State

Evidence Basis

Evidence Sufficiency

Uncertainty State

Conflict State

Effective Time

Reassessment Trigger

Version:

142. Minimum Boundary States

At minimum:

Boundary Established

Boundary Conditionally Established

Boundary Incomplete

Boundary Overlapping

Boundary Gap Identified

Boundary Under Review

Boundary Changed

Boundary Evidence-Limited

Boundary Conflicted

Boundary Unknown

Boundary Unresolved

Boundary Reassessment Required

Boundary Expired

143. Minimum Implementation Framework

A minimum operational RCBM implementation should contain eight governed layers.

Layer 1 — Governance Purpose

Establish:

why Resource Consumption is being bounded; which governance question the boundary must support.

Layer 2 — Governed Resource Context

Establish:

Resource; Resource Source; system; process; activity; infrastructure.

Layer 3 — Inclusion / Exclusion

Determine:

included Resource flows; excluded Resource flows; direct Consumption; indirect Consumption; material exclusions.

Layer 4 — Spatial / Temporal / Organizational Scope

Establish:

location; time interval; organizational scope; functional scope; purpose scope.

Layer 5 — Boundary Relationships

Determine:

parent boundaries; child boundaries; overlaps; gaps; shared infrastructure; shared Resource flows.

Layer 6 — Integrity & Comparability

Evaluate:

double counting; boundary completeness; boundary equivalence; comparability; boundary shifting; externalization.

Layer 7 — Evidence & Validity

Evaluate:

evidence basis; uncertainty; conflict; effective period; change; reassessment.

Layer 8 — Governed Output

Produce:

Resource Consumption Boundary Profile

Canonical machine-readable logic:

Governance Purpose → Resource Context → System / Process / Activity Scope → Resource Flows → Inclusion / Exclusion → Spatial / Temporal / Source / Organizational Scope → Overlap / Gap / Double-Counting Review → Comparability / Integrity → Resource Consumption Boundary Profile

144. Minimum Decision States

At minimum:

Boundary Accepted

Boundary Conditionally Accepted

Boundary Adjustment Required

Boundary Expansion Required

Boundary Narrowing Required

Boundary Overlap Resolution Required

Boundary Gap Resolution Required

Boundary Comparability Adjustment Required

Boundary Evidence-Limited

Boundary Conflicted

Boundary Unknown

Boundary Unresolved

Boundary Reassessment Required

145. Minimum Evidence Path

Where a Consumption Boundary cannot be sufficiently established:

Boundary Unknown / Unresolved → Missing System / Flow / Source / Spatial / Temporal / Organizational Evidence → Minimum Evidence Requirement → Evidence Acquisition → Inclusion / Exclusion Review → Overlap / Gap Review → Boundary Validation → Resource Consumption Boundary Profile Update

146. Minimum Reassessment Framework

At minimum:

Current Resource Consumption Boundary Profile → System / Process / Source / Infrastructure / Purpose / Time Change → Materiality Test → Inclusion / Exclusion Review → Overlap / Gap / Double-Counting Review → Comparability Review → Boundary Confirmation or Modification → Profile Update → Version Update

147. Governance Requirements

A conforming RCBM implementation must:

1. identify the governance purpose of the Consumption Boundary; 2. identify the governed Resource; 3. identify the governed system where applicable; 4. identify the governed process where applicable; 5. identify the governed activity where applicable; 6. identify materially relevant infrastructure; 7. identify Resource flows entering the boundary; 8. identify Resource flows leaving the boundary; 9. identify relevant internal Resource flows; 10. prevent internal transfers from becoming new Consumption automatically; 11. distinguish Resource entry from Resource Consumption; 12. distinguish Resource exit from Resource Recovery; 13. identify included Resource flows; 14. identify excluded Resource flows; 15. identify material exclusions; 16. preserve Resource Source scope; 17. distinguish Resource type from Resource Source; 18. preserve Source changes where material; 19. preserve spatial scope; 20. prevent aggregate Consumption from replacing local Consumption context where local context matters; 21. identify spatial boundary shifts; 22. preserve temporal scope; 23. preserve temporal alignment; 24. identify partial-period boundaries; 25. identify temporal boundary shifts; 26. preserve organizational scope where relevant; 27. identify organizational transfer of Resource-consuming activity; 28. preserve functional scope; 29. preserve purpose scope where relevant; 30. distinguish direct from indirect Consumption boundaries; 31. require a sufficient basis for indirect Consumption inclusion; 32. preserve upstream scope where applicable; 33. preserve downstream scope where applicable; 34. distinguish operational from lifecycle Consumption boundaries; 35. distinguish embedded from current operational Consumption; 36. preserve shared-infrastructure context; 37. prevent shared infrastructure from being fully attributed to every participant automatically; 38. preserve shared Resource-pool context; 39. detect double counting; 40. prevent multiple attribution records from becoming multiple physical Consumption events; 41. identify overlapping boundaries; 42. prevent overlapping boundaries from being treated automatically as additive; 43. identify boundary gaps; 44. prevent unassigned Consumption from becoming zero Consumption; 45. determine boundary completeness; 46. distinguish complete measurement from complete boundary coverage; 47. determine materiality of exclusions where applicable; 48. preserve boundary hierarchy; 49. preserve parent and child relationships;

50. prevent child-boundary sums from becoming parent Consumption automatically; 51. support boundary decomposition; 52. prevent decomposition from implying attribution accuracy; 53. support boundary aggregation; 54. validate unit compatibility before aggregation; 55. validate temporal alignment before aggregation; 56. evaluate overlap before aggregation; 57. evaluate double-counting risk before aggregation; 58. determine boundary equivalence where required; 59. determine boundary comparability; 60. distinguish same units from same boundaries; 61. preserve boundary adjustments; 62. distinguish adjusted from original Consumption evidence; 63. preserve normalization methods where used; 64. distinguish normalized Consumption from physical boundary equivalence; 65. preserve boundary consistency for trend analysis; 66. identify boundary drift; 67. prevent stable labels from concealing changed definitions; 68. identify material boundary changes; 69. justify material boundary changes; 70. date and version material boundary changes; 71. preserve historical comparability; 72. prevent historical Boundary A results from being treated automatically as current Boundary B results; 73. preserve boundary validity periods; 74. preserve boundary evidence; 75. determine evidence sufficiency; 76. preserve boundary uncertainty; 77. identify boundary conflict; 78. prevent conflict from enabling selection of the most favorable boundary; 79. support Unknown boundary states; 80. prevent undefined boundaries from being interpreted as zero Consumption; 81. identify boundary-manipulation risk; 82. identify boundary-shifting risk; 83. prevent moved Consumption from being represented automatically as eliminated Consumption; 84. preserve outsourcing effects where material; 85. preserve external infrastructure Consumption boundary context; 86. prevent external Consumption from becoming zero Resource Consumption; 87. require sufficiently aligned boundaries for efficiency comparison; 88. prevent narrower boundaries from creating unsupported efficiency claims; 89. preserve Consumption Boundary context in Value comparisons; 90. preserve local boundary context for Scarcity analysis; 91. preserve residual Resource boundary context for Recovery; 92. preserve interdependency boundary context where relevant; 93. distinguish predicted from observed Consumption boundaries; 94. distinguish simulated from operational boundaries; 95. prevent automated classification from becoming boundary authority; 96. preserve applicable boundary authority or methodology; 97. distinguish technical configuration from governance authority; 98. support boundary reassessment; 99. preserve version history; 100. produce a Resource Consumption Boundary Profile.

148. Governance Logic

Canonical RCBM logic:

Governance Purpose → Resource Identification → System / Process / Activity Definition → Infrastructure Context → Resource-Flow Mapping → Source Boundary → Spatial Boundary

→ Temporal Boundary → Organizational / Functional / Purpose Boundary → Direct / Indirect Inclusion → Inclusion / Exclusion Determination → Overlap / Gap / Double-Counting Review → Boundary Completeness → Comparability / Integrity Review → Resource Consumption Boundary Profile → Reassessment

149. Governance Outputs

RCBM may produce:

Resource Consumption Boundary Profile

System Boundary

Process Boundary

Activity Boundary

Infrastructure Boundary

Resource-Flow Boundary

Resource Source Boundary

Spatial Boundary

Temporal Boundary

Organizational Boundary

Functional Boundary

Purpose Boundary

Direct Consumption Boundary

Indirect Consumption Boundary

Lifecycle Boundary where applicable

Included Resource Flow Set

Excluded Resource Flow Set

Material Exclusion Set

Boundary Hierarchy

Boundary Overlap State

Boundary Gap State

Double-Counting Risk State

Boundary Completeness State

Boundary Equivalence State

Boundary Comparability State

Boundary Drift State

Boundary Change Record

Evidence Sufficiency State

Boundary Uncertainty State

Boundary Conflict State

Reassessment Trigger

Version:

150. Critical Distinctions

Resource Quantity Without a Defined Consumption Boundary ≠ Governed Resource Consumption

Equal Resource Quantity Across Different Boundaries ≠ Equivalent Resource Consumption Evidence

Same Resource System + Different Governance Purpose ≠ Automatically Same Appropriate Consumption Boundary

Component Consumption ≠ System Consumption

Primary Process Consumption ≠ Total Operational Consumption by definition

Primary Activity ≠ Entire Resource-Use System

Excluded Infrastructure Consumption ≠ Nonexistent Infrastructure Consumption

Internal Resource Transfer ≠ New Resource Consumption

Resource Entry ≠ Resource Consumption

Resource Exit ≠ Resource Recovery

Same Resource Type ≠ Same Resource Source

Stable Total Consumption ≠ Stable Source Composition

Aggregate Consumption ≠ Local Consumption Condition

Reduced Consumption Within Boundary A ≠ Reduced Total Resource Consumption

Equal Resource Quantity Across Different Time Windows ≠ Equivalent Resource-Use Pattern

Reduced Consumption in One Reporting Period ≠ Reduced Consumption Across the Full Operational Period

Transferred Consumption ≠ Eliminated Consumption

Total Facility Consumption ≠ Consumption of Every Individual Function

Same Resource + Same System ≠ Same Consumption Purpose

Direct Consumption ≠ Total Resource Dependency Footprint by definition

Association ≠ Sufficient Basis for Indirect Consumption Attribution

Operational Consumption ≠ Lifecycle Consumption

Embedded Resource Consumption ≠ Current Operational Consumption

Shared Infrastructure Consumption ≠ Automatically Full Consumption of Every Participant

Multiple Attribution Records ≠ Multiple Physical Consumption Events

Overlapping Consumption Boundaries ≠ Additive Consumption by default

Unassigned Consumption ≠ Zero Consumption

Complete Measurement Inside an Incomplete Boundary ≠ Complete Resource Consumption Evidence

Sum of Child Boundaries ≠ Parent Boundary Automatically

Boundary Decomposition ≠ Automatic Attribution Accuracy

Mathematically Addable Consumption Values ≠ Governance-Compatible Consumption Values

Same Unit ≠ Same Boundary

Adjusted Consumption ≠ Original Consumption Measurement

Normalized Consumption ≠ Physical Boundary Equivalence

Stable Boundary Label ≠ Stable Boundary Definition

Historical Consumption Under Boundary A ≠ Current Consumption Under Boundary B by default

Boundary Conflict ≠ Permission to Select the Most Favorable Boundary

Undefined Boundary ≠ Zero Consumption

Consumption Moved Outside the Reporting Boundary ≠ Consumption Eliminated

Outsourced Consumption ≠ Eliminated Consumption

Externally Consumed Resource ≠ Zero Resource Consumption

Lower Consumption Under a Narrower Boundary ≠ Demonstrated Resource Efficiency Improvement

Same Value Output + Different Consumption Boundaries ≠ Directly Comparable Resource Productivity by default

Predicted Consumption Boundary ≠ Observed Consumption Boundary unless explicitly aligned

Simulated Boundary ≠ Operational Boundary by default

Automated Classification ≠ Boundary Authority

Technical Boundary Configuration ≠ Governance Boundary Authority

151. Cross-Architecture Boundary

RCBM may consume:

RCHS — Resource identity, type, Source, state, and context.

RACS — Resource Availability and capacity boundaries.

RDGS — Demand boundaries where Demand and Consumption require comparison.

RDCS — Dependency and Criticality context.

RAGS — Access and rights boundaries.

RPAS — Allocation scope, Allocation limits, and Resource distribution context.

RCMM — Resource Consumption Measurements requiring explicit Consumption boundaries.

RUSM — Utilization evidence requiring sufficiently aligned capacity and Resource-use boundaries.

RSCS — Scarcity and Constraint context where spatial, temporal, or Source boundaries materially affect Scarcity.

RRCS — Recovery context where residual Resource crosses the Consumption boundary.

RIRS — Resource interdependency evidence where Consumption boundaries interact across Resource systems.

RCSS — continuity and sustainability context.

ORA™ — operational reality evidence.

PGA™ — predicted Resource-use boundaries without treating prediction as observed Consumption.

SIMULOS® — simulated Resource boundaries without treating simulation as operational reality.

VEGA™ — Value and efficiency analysis requiring sufficiently aligned Resource Consumption boundaries.

RCBM does not absorb these mechanisms.

152. 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.

RCBM governs the boundaries within which Resource Consumption is represented and compared.

Its outputs may support:

Consumption Measurement; Utilization analysis; Allocation reassessment; Scarcity analysis; Recovery analysis; efficiency evaluation; Value evaluation; Resilience governance; Sustainability governance.

Those mechanisms remain governed by their competent architectures.

153. Canonical Boundary

RCBM governs how the system, process, activity, infrastructure, Resource flow, Source, spatial, temporal, organizational, functional, purpose, direct, indirect, and other materially relevant boundaries of Resource Consumption are established, evidenced, maintained, compared, versioned, and reassessed, including inclusion, exclusion, overlap, gaps, double counting, boundary hierarchy, boundary shifting, completeness, and comparability.

It does not measure Resource Consumption itself, determine Resource Utilization State, establish Resource Allocation, authorize Access, determine Scarcity, govern Recovery, or determine Value, Harm, Liability, or long-term Sustainability.

Its principal governed output is the Resource Consumption Boundary Profile .

154. Canonical Closing Statement

Resource Consumption cannot be meaningfully governed by quantity alone. Every quantity exists inside a boundary, and changing that boundary can change the apparent Resource reality without changing the underlying Resource use.

RCBM governs that boundary — ensuring that Resource Consumption remains explicit about what is counted, what is excluded, where and when the measurement applies, how boundaries relate, and whether apparent reductions represent genuine Resource change or merely movement beyond the edge of measurement.