RSEM — Resource Scarcity Evaluation Module
Architecture: RSGA™ — Resource Sustainability Governance Architecture
Parent Standard: Resource Scarcity & Constraint Standard (RSCS)
Category: Governance & Enforcement
Subcategory: Resource Governance
Type: Core Module
Governed Space: Resource Scarcity Evaluation Governance
Module ID: RSGA-RSCS-RSEM-03
Origin ID: OOF-RSGA-RSCS-RSEM
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
RSEM — Resource Scarcity Evaluation Module governs how the magnitude, severity, materiality, scope, duration, concentration, dependency exposure, operational consequence, and overall governance significance of an established or emerging Resource Scarcity or Resource Constraint state are evaluated, evidenced, classified, monitored, and reassessed.
RSEM determines how significant the constrained Resource condition is .
It evaluates Resource Scarcity and Constraint evidence against the operational context in which the Resource is required.
Its foundational distinctions are:
Scarcity State ≠ Scarcity Severity.
Constraint Magnitude ≠ Constraint Severity.
Large Resource Deficit ≠ High Governance Severity by definition.
Small Resource Deficit ≠ Low Governance Severity by definition.
Resource Criticality ≠ Scarcity Severity by itself.
2. Operational Role
RSSM establishes whether and in what state a Resource is scarce .
RCTM establishes how the Resource is constrained .
RSEM evaluates:
how large the Resource limitation is; how severe it is; how materially it affects the governed Resource System; how long it persists; how broadly it applies; how concentrated it is; which dependencies are exposed; what operational consequences may result; whether the condition is escalating or becoming critical; and with what evidence the evaluation can be supported.
RSEM transforms:
**Resource Scarcity State
Resource Constraint Type Resource Gap / Limitation Resource Criticality Dependency Exposure Duration Scope Operational Consequence Evidence**
into:
a governed Resource Scarcity Evaluation.
3. Operational Question
How significant is the established or emerging Resource Scarcity or Constraint state when evaluated across magnitude, severity, materiality, duration, scope, concentration, affected dependencies, available buffers, operational consequences, and other materially relevant Resource conditions, and with what evidence and confidence can that evaluation be established?
4. Position in RSCS Governance
Canonical progression:
Governed Resource State → Legitimate Resource Requirement → Resource Sufficiency Comparison → Resource Scarcity State → Constraint Type → Constraint Magnitude → Constraint Severity → Materiality → Scope / Duration / Concentration → Dependency Exposure → Operational Consequence → Resource Scarcity Evaluation → Response / Monitoring → Resolution Assessment → Reassessment
RSEM governs:
Scarcity / Constraint Evidence → Resource Scarcity Evaluation
5. Governed Space
RSEM governs:
Resource Scarcity Evaluation Governance
This governed space concerns the evaluation of the governance significance of an established, emerging, localized, widespread, temporary, recurring, persistent, structural, or anticipated Resource Scarcity or Constraint condition.
6. Governed Object
The primary Governed Object is:
A Resource Scarcity Evaluation associated with a defined Resource Scarcity State, Resource Constraint Type, Resource limitation, operational context, affected dependencies, and evidence basis.
Canonical relationship:
**Scarcity State
Constraint Type Constraint Magnitude Duration Scope Concentration Dependency Exposure Operational Consequence Evidence → Scarcity Severity & Materiality Evaluation → Resource Scarcity Evaluation**
7. Scope
RSEM governs:
Constraint Magnitude evaluation; Scarcity magnitude evaluation; Constraint Severity; Scarcity Severity; Resource deficit evaluation; capacity deficit evaluation; rate deficit evaluation; temporal insufficiency evaluation; Resource materiality; duration significance; scope significance; concentration significance; dependency exposure; Criticality relevance; reserve relevance; buffer relevance; substitutability relevance; recoverability relevance; operational consequence relevance; interdependency relevance; severity classification; severity escalation;
severity stabilization; severity reduction; severity uncertainty; severity conflict; evaluation confidence; evaluation evidence; evaluation monitoring; evaluation reassessment; traceability; versioning.
RSEM does not independently:
determine Resource identity; determine Resource Demand; determine Resource Scarcity State; classify the underlying Constraint Type; determine Resource Dependency or Criticality as originating mechanisms; grant Resource Access; determine Resource Priority; allocate Resources; measure Resource Consumption; authorize intervention; govern Resource Recovery; authorize substitution; determine resilience; determine long-term Sustainability; determine Value; determine Harm; determine Liability.
8. Resource Scarcity Evaluation
A Resource Scarcity Evaluation represents the governed assessment of the significance of a Resource Scarcity or Constraint condition.
It answers:
How serious is this Resource condition within its actual governance context?
9. Evaluation Principle
A Scarcity evaluation should not be reduced to a single physical quantity.
The governance significance of Scarcity may depend on:
magnitude; duration; scope; concentration; Resource Criticality; dependency exposure; available reserves; available buffers; substitutability; recoverability; operational consequences; interdependency effects; evidence quality.
10. Quantity Principle
Resource Quantity Alone ≠ Scarcity Severity.
11. Constraint Magnitude
Constraint Magnitude represents the measurable extent of the Resource limitation.
Where methodologically appropriate:
Constraint Gap = Legitimate Resource Requirement − Applicable Resource Capacity
The Resource-specific method may differ according to the governed Resource.
12. Magnitude Boundary
Constraint Gap ≠ Constraint Severity.
Magnitude describes the extent of the Resource limitation.
Severity describes its governance significance.
13. Absolute Magnitude
Absolute Magnitude represents the Resource deficit in the applicable native or governed measurement unit.
Examples:
m³ of water; MW of electrical capacity; GPU-hours; tonnes of material; GB/s of bandwidth.
14. Relative Magnitude
Relative Magnitude represents the Resource deficit relative to an applicable reference basis.
Conceptually:
Relative Constraint Magnitude = Constraint Gap / Legitimate Resource Requirement
where methodologically valid.
15. Relative-Magnitude Boundary
Equal Percentage Deficit ≠ Equal Scarcity Severity.
The affected Resource context matters.
16. Capacity Deficit
A Capacity Deficit exists where applicable usable capacity is below the capacity required by the legitimate Resource requirement.
17. Rate Deficit
A Rate Deficit exists where the Resource cannot be supplied, processed, delivered, or otherwise made available at the required rate.
18. Temporal Deficit
A Temporal Deficit exists where Resource capacity is insufficient during the time interval in which the Resource is required.
19. Spatial Deficit
A Spatial Deficit exists where Resource capacity is insufficient at the required location despite capacity elsewhere.
20. Quality Deficit
A Quality Deficit exists where Resource quantity exists but the usable quantity meeting required quality conditions is insufficient.
21. Multi-Dimensional Deficit
A Resource may simultaneously experience:
quantity deficit; capacity deficit; rate deficit; temporal deficit; spatial deficit; quality deficit.
These should not automatically be collapsed into one number.
22. Multi-Dimensional Principle
One Numerical Deficit ≠ Complete Resource Scarcity Evaluation.
23. Constraint Severity
Constraint Severity represents the governance significance of the Resource Constraint.
Severity should be determined from relevant evidence rather than directly inferred from Constraint Type or Magnitude.
24. Scarcity Severity
Scarcity Severity represents the governance significance of the Resource Scarcity State relative to affected Resource requirements and dependencies.
25. Scarcity and Constraint Severity
Constraint Severity and Scarcity Severity may overlap but need not be identical.
A significant operational Constraint may exist before full Scarcity develops.
Conversely, multiple moderate constraints may collectively produce severe Scarcity.
26. Severity Principle
Constraint Magnitude ≠ Constraint Severity.
27. Deficit-Severity Principle
Large Resource Deficit ≠ High Governance Severity by definition.
A large deficit affecting a flexible or non-critical Resource use may remain manageable.
28. Small-Deficit Principle
Small Resource Deficit ≠ Low Governance Severity by definition.
A small deficit affecting a critical Resource dependency may produce severe governance significance.
29. Minimum Severity States
At minimum:
No Material Severity
Low Severity
Moderate Severity
High Severity
Critical Severity
Severity Evidence-Limited
Severity Conflicted
Severity Unknown
Severity Unresolved
30. Severity Basis
Severity may consider:
Constraint Magnitude; Resource Criticality; Dependency exposure; duration; scope; concentration; available reserve; available buffer; substitutability; recoverability; operational consequence; interdependency effects; trend.
31. Materiality
Resource Scarcity Materiality represents whether the Scarcity or Constraint condition is significant enough to require governance attention within the applicable context.
32. Materiality Principle
Detected Constraint ≠ Material Constraint by definition.
A technically measurable constraint may be operationally immaterial.
33. Materiality States
At minimum:
Immaterial
Low Materiality
Material
High Materiality
Critical Materiality
Materiality Unknown
34. Severity and Materiality
Severity and Materiality should remain distinguishable.
Severity ≠ Materiality.
A severe but extremely narrow event may have different governance significance from a moderate condition affecting an entire Resource System.
35. Duration
Duration measures how long the Resource Scarcity or Constraint condition exists or is expected to exist.
36. Duration Significance
The governance significance of duration depends on Resource context.
A short electricity interruption may be critical for some functions.
A longer reduction may be manageable for another Resource.
37. Duration Principle
Short Duration ≠ Low Severity.
38. Long-Duration Principle
Long Duration ≠ Critical Severity by definition.
39. Scope
Scope represents the breadth of the Resource System affected by the constrained condition.
Possible scope includes:
single participant; single function; single system; single facility; single Source; network segment; local area; region; multiple regions; system-wide.
40. Scope Principle
Large Geographic Scope ≠ High Severity automatically.
Affected dependencies and consequences matter.
41. Concentration
Concentration represents whether Scarcity or Constraint effects are disproportionately focused on specific:
participants; functions; systems; locations; Sources; dependencies.
42. Concentration Principle
Low Aggregate Deficit ≠ Low Local Severity.
43. Distribution
RSEM should preserve materially unequal distribution of Resource Scarcity or Constraint where evidence supports it.
44. Aggregate-Evaluation Boundary
Aggregate Resource Condition ≠ Condition Experienced by Every Affected Entity.
45. Resource Criticality
Resource Criticality may materially affect Scarcity Severity.
However:
Resource Criticality ≠ Scarcity Severity by itself.
RDCS governs Resource Criticality.
RSEM consumes the relevant Criticality evidence.
46. Criticality Interaction
The same Constraint Magnitude may produce different severity depending on Resource Criticality.
47. Dependency Exposure
Dependency Exposure represents the extent to which systems, participants, functions, infrastructure, or other Resources depend on the constrained Resource.
48. Dependency Principle
Resource Dependency ≠ Scarcity Severity by itself.
The actual exposure and consequences must be evaluated.
49. Dependency Breadth
RSEM may evaluate how many material dependencies are exposed to the Resource Constraint.
50. Dependency Depth
RSEM may evaluate whether the constrained Resource supports:
direct dependencies; downstream dependencies; multi-level dependency chains; critical enabling dependencies.
51. Dependency-Depth Boundary
Long Dependency Chain ≠ High Severity automatically.
The actual significance of affected dependencies matters.
52. Reserve Context
Available reserves may reduce the immediate governance severity of a Resource Constraint.
53. Reserve Principle
Resource Reserve ≠ Absence of Scarcity.
A Resource may remain scarce while reserve capacity temporarily protects critical functions.
54. Reserve Adequacy
RSEM may evaluate whether available reserve is:
sufficient; partially sufficient; insufficient; unavailable; unknown.
55. Reserve-Duration Relationship
Reserve significance may depend on how long the reserve can support the applicable Resource requirement.
56. Buffer Context
Operational buffers may reduce immediate exposure to Resource Scarcity.
Examples include:
stored Resource; battery capacity; water storage; inventory; redundant compute capacity; operational slack.
57. Buffer Principle
Available Buffer ≠ Constraint Resolution.
58. Substitutability Relevance
Availability of legitimate substitutes may reduce Scarcity Severity.
RSEM may consume substitution evidence.
It does not determine whether substitution is authorized or valid.
59. Substitution Principle
Potential Substitute ≠ Available Substitute.
Available Substitute ≠ Authorized Substitute.
60. Recoverability Relevance
Recoverable Resource potential may reduce future Scarcity exposure.
However:
Recoverable Resource ≠ Currently Available Resource.
61. Recovery Boundary
RRCS governs Resource Recovery & Circularity.
RSEM evaluates only the relevance of available Recovery evidence to Scarcity significance.
62. Operational Consequence
RSEM may evaluate the operational consequences associated with the Resource Scarcity or Constraint state.
Consequences may include:
reduced throughput; delayed operation; degraded performance; loss of redundancy; reduced safety margin; partial service interruption; complete service interruption; dependency failure; continuity risk.
63. Consequence Principle
Resource Constraint ≠ Operational Failure by definition.
Systems may continue functioning under constrained conditions.
64. Potential Consequence
A Resource Constraint may create the possibility of operational consequence without that consequence having occurred.
Potential Consequence ≠ Observed Consequence.
65. Observed Consequence
Observed operational consequences should remain distinguishable from predicted or simulated consequences.
66. Consequence Boundary
Predicted Operational Consequence ≠ Observed Operational Consequence.
67. Interdependency Relevance
Resource Scarcity may propagate through interdependent Resource Systems.
RSEM may consume evidence of such exposure when evaluating severity.
RIRS governs Resource Interdependency & Resilience.
68. Interdependency Principle
Potential Constraint Propagation ≠ Actual Constraint Propagation.
69. Constraint Accumulation
Several moderate constraints may collectively create a severe Resource condition.
70. Accumulation Principle
Individual Constraint Severity ≠ Combined Constraint Severity.
Combined effects require evaluation.
71. Constraint Interaction
RSEM should consider materially relevant interaction among Constraint Types identified by RCTM.
Interactions may be:
additive; amplifying; cascading; conditional; mutually reinforcing.
72. Interaction Boundary
Multiple Constraint Types ≠ High Severity automatically.
Their actual combined effect must be evaluated.
73. Scarcity Concentration
Scarcity may be severe for a narrow group while aggregate Resource conditions remain relatively stable.
74. Concentration Boundary
System-Wide Stability ≠ Low Severity for Every Local Context.
75. Temporal Concentration
Resource Scarcity may be concentrated within critical periods.
Examples:
peak electricity hours; drought periods; training windows; emergency operations; seasonal demand periods.
76. Temporal-Concentration Principle
Short Scarcity Window ≠ Low Governance Significance.
77. Severity Escalation
Severity Escalation exists where the governance significance of the Resource Scarcity or Constraint condition materially increases.
78. Escalation Drivers
Severity may escalate because of:
larger deficit; longer duration; broader scope; greater concentration; loss of reserve; loss of buffer; increased Criticality exposure; additional dependencies; worsening operational consequences; constraint interaction; reduced substitutability; reduced recoverability.
79. Escalation Principle
Worsening Scarcity State ≠ Severity Escalation automatically.
Severity must be evaluated against the complete context.
80. Severity Stabilization
Severity is Stabilized where the governance significance of the constrained condition remains materially bounded and is no longer worsening.
81. Stabilization Principle
Severity Stabilization ≠ Scarcity Resolution.
82. Severity Reduction
Severity Reduction exists where the governance significance of the constrained Resource condition materially decreases.
83. Reduction Principle
Reduced Severity ≠ Resolved Scarcity.
84. Critical Severity
Critical Severity should indicate a Resource condition with exceptional governance significance relative to the applicable Resource System.
Critical Severity may arise from:
extreme deficit; critical dependency exposure; loss of essential function; absence of reserve;
absence of substitute; rapid escalation; systemic propagation; other Resource-specific conditions.
85. Critical-Severity Boundary
Critical Severity ≠ Complete Resource Exhaustion.
86. Severity Thresholds
Where thresholds are used, RSEM should preserve their methodological basis.
Thresholds may be:
Resource-specific; context-specific; dependency-specific; temporal; dynamic; fixed.
87. Threshold Principle
Severity Threshold ≠ Universal Resource Threshold by default.
88. Threshold Provenance
Every material severity threshold should preserve:
basis; applicable Resource; applicable context; methodology or authority source; effective period; version.
89. Dynamic Severity
Scarcity Severity may change even where the physical Resource deficit remains unchanged.
For example, severity may rise because:
a reserve is exhausted; a critical dependency becomes active; a substitute becomes unavailable; the constraint persists longer than expected.
90. Dynamic-Severity Principle
Stable Physical Deficit ≠ Stable Governance Severity.
91. Severity Comparison
Severity comparisons across different Resources should be performed only where the comparison method is explicitly governed.
92. Cross-Resource Comparison Boundary
Equal Physical Deficit Across Different Resources ≠ Equal Governance Severity.
93. Native Measurement
RSEM should preserve Resource-native measurements wherever they remain relevant.
Examples:
litres; m³; MW; MWh; GPU-hours; tonnes; bandwidth; storage capacity.
94. Normalization Boundary
Normalized severity may support comparison where a valid methodology exists.
However:
Normalized Resource Significance ≠ Physical Resource Equivalence.
95. Cross-Resource Normalization
RSEM does not establish a universal physical conversion between unlike Resources.
Cross-resource comparability does not require physical equivalence.
96. Evidence Basis
RSEM should preserve the evidence supporting Scarcity Magnitude, Severity, and Materiality determinations.
Evidence may include:
Scarcity State evidence; Constraint Type evidence; capacity evidence; Demand evidence; Dependency evidence; Criticality evidence; reserve evidence; Consumption evidence; Utilization evidence; operational consequence evidence; interdependency evidence; other relevant governed evidence.
97. Evidence Sufficiency
RSEM should determine whether evidence is sufficient for the asserted evaluation.
98. Evidence Principle
Scarcity Evidence ≠ Severity Evidence by default.
Evidence sufficient to establish Scarcity may be insufficient to establish its severity.
99. Severity Evidence-Limited
Severity Evidence-Limited applies where Scarcity or Constraint is established but available evidence is insufficient to reliably determine severity.
100. Severity Unknown
Severity Unknown applies where severity cannot be adequately established.
Severity Unknown ≠ Low Severity.
101. Severity Conflicted
Severity Conflicted applies where material evidence supports incompatible severity evaluations.
102. Conflict Principle
Conflicting Severity Evidence ≠ Permission to Select the Most Convenient Severity.
103. Measurement Uncertainty
Uncertainty in Constraint Magnitude should remain visible in the evaluation.
104. Context Uncertainty
Uncertainty regarding duration, scope, concentration, Criticality, Dependency, reserve, substitution, or operational consequence should remain visible where material.
105. Evaluation Confidence
RSEM may preserve evaluation confidence.
Confidence concerns the strength of the evidence supporting the evaluation.
106. Confidence Principle
High Evaluation Confidence ≠ High Scarcity Severity.
107. Predicted Severity
Prediction may estimate future Scarcity Severity.
However:
Predicted Severity ≠ Current Severity.
PGA™ governs Prediction methodology where applicable.
108. Simulated Severity
Simulation may evaluate Resource Scarcity under hypothetical conditions.
Simulated Severity ≠ Observed Severity.
SIMULOS® governs simulation.
109. Historical Severity
Historical severity may support trend, recurrence, or comparative analysis.
Historical Severity ≠ Current Severity.
110. Severity Trend
RSEM should support at minimum:
Improving
Stable
Worsening
Volatile
Unknown
111. Trend Principle
Current Severity ≠ Severity Direction.
A Resource condition may remain Critical while improving.
112. Evaluation Monitoring
Material Scarcity evaluations should support monitoring appropriate to their significance.
113. Monitoring Inputs
Monitoring may include:
Constraint Magnitude; Scarcity State; Constraint Type; duration; scope; concentration;
Criticality; Dependency exposure; reserve; buffer; substitutability; recoverability; operational consequence; interdependency effects; severity trend.
114. Reassessment Trigger
RSEM should support reassessment where materially relevant conditions change.
Triggers may include:
Scarcity-State change; Constraint-Type change; magnitude change; duration threshold; scope change; reserve depletion; buffer depletion; Criticality change; Dependency change; substitute availability change; Recovery change; operational consequence; new evidence; evidence conflict.
115. Scarcity-State Boundary
RSSM determines Resource Scarcity State.
RSEM evaluates its significance.
Scarcity Evaluation ≠ Scarcity-State Creation.
116. Constraint-Type Boundary
RCTM identifies Resource Constraint Type.
RSEM evaluates the significance of the resulting Resource condition.
Scarcity Evaluation ≠ Constraint-Type Classification.
117. Demand Boundary
RDGS governs Resource Demand.
RSEM may consume legitimate Resource requirement evidence.
It does not redefine Demand.
118. Dependency Boundary
RDCS governs Resource Dependency and Criticality.
RSEM consumes their relevance to Scarcity Severity.
It does not redefine Dependency or Criticality.
119. Access Boundary
RSEM may identify severe Resource pressure relevant to Access review.
Scarcity Severity ≠ Access Authority.
120. Priority Boundary
Scarcity Severity may materially inform Resource Priority governance.
However:
Scarcity Severity ≠ Resource Priority.
RPAS retains Priority governance.
121. Allocation Boundary
Scarcity Severity may justify Allocation reassessment.
However:
Scarcity Severity ≠ Allocation Authority.
122. Consumption Boundary
RCUS governs actual Resource Consumption & Utilization.
RSEM may consume that evidence without redefining Consumption.
123. Recovery Boundary
Recovery may reduce future Scarcity Severity.
RSEM does not authorize Recovery.
124. Substitution Boundary
Substitutability may reduce Scarcity Severity.
RSEM does not authorize substitution.
125. Resilience Boundary
Scarcity Severity may expose resilience weakness.
RIRS governs Resource Interdependency & Resilience.
126. Sustainability Boundary
Persistent severe Scarcity may provide important Sustainability evidence.
However:
Scarcity Severity ≠ Sustainability Determination.
127. Value Boundary
Resource Value may be relevant to downstream decisions.
However:
High Value ≠ Low Scarcity Severity.
High Value ≠ Automatic Resource Priority.
VEGA™ governs Value relationships.
128. Harm Boundary
Severe Resource Scarcity may contribute to Harm.
However:
Scarcity Severity ≠ Harm Severity.
HAGA™ governs Harm.
129. Liability Boundary
Resource Scarcity evidence may become relevant to Liability.
However:
Scarcity Severity ≠ Liability.
LIGA™ governs Liability.
130. Automated Evaluation Boundary
Software may calculate or classify Scarcity Severity.
However:
Automated Severity Evaluation ≠ Governance Authority.
131. Intervention Boundary
A High or Critical Severity state may trigger governance review.
It does not independently authorize intervention.
Critical Scarcity Evaluation ≠ Intervention Authority.
132. Resource Scarcity Evaluation Profile
The principal RSEM output is the:
Resource Scarcity Evaluation Profile
133. Minimum Resource Scarcity Evaluation Profile Fields
At minimum:
Evaluation ID
Resource ID
Resource Type
Resource Source
Location
Applicable Time Horizon
Scarcity State Reference
Constraint Type Reference
Legitimate Resource Requirement Reference
Applicable Resource Capacity Reference
Absolute Constraint Magnitude
Relative Constraint Magnitude where applicable
Capacity Deficit
Rate Deficit where applicable
Temporal Deficit where applicable
Spatial Deficit where applicable
Quality Deficit where applicable
Constraint Severity
Scarcity Severity
Materiality State
Duration
Scope
Concentration
Distribution State
Resource Criticality Reference
Dependency Exposure
Reserve State
Reserve Adequacy
Buffer State
Substitutability Reference
Recoverability Reference
Operational Consequence State
Interdependency Exposure
Constraint Interaction State
Severity Trend
Severity Escalation State
Severity Stabilization State
Severity Reduction State
Evidence Basis
Evidence Provenance
Evidence Sufficiency
Measurement Uncertainty
Context Uncertainty
Evaluation Confidence
Conflict State
Monitoring State
Reassessment Trigger
Effective Time
Version:
134. Minimum Implementation Framework
A minimum operational RSEM implementation should contain eight governed layers.
Layer 1 — Scarcity & Constraint Reference
Establish:
Resource; Scarcity State; Constraint Type; Source; location; time horizon.
Layer 2 — Magnitude Evaluation
Determine where applicable:
absolute deficit; relative deficit; capacity deficit; rate deficit; temporal deficit; spatial deficit; quality deficit.
Layer 3 — Contextual Significance
Evaluate:
duration; scope; concentration; distribution; Resource Criticality; Dependency exposure.
Layer 4 — Mitigating Capacity
Evaluate:
reserve; buffer; substitutability; recoverability.
Layer 5 — Operational Consequence
Evaluate:
current consequence; potential consequence; interdependency exposure.
Layer 6 — Severity & Materiality
Determine:
Constraint Severity; Scarcity Severity; Materiality; trend.
Layer 7 — Evidence & Reassessment
Establish:
evidence sufficiency; uncertainty; conflict; confidence; monitoring; reassessment.
Layer 8 — Governed Output
Produce:
Resource Scarcity Evaluation Profile
Canonical machine-readable logic:
**Scarcity State
Constraint Type Magnitude Duration / Scope / Concentration Criticality / Dependency Exposure Reserve / Buffer / Substitutability / Recoverability Operational Consequence → Severity & Materiality Evaluation → Evidence / Uncertainty / Conflict → Resource Scarcity Evaluation Profile**
135. Minimum Decision States
At minimum:
No Material Severity
Low Severity
Moderate Severity
High Severity
Critical Severity
Immaterial
Material
High Materiality
Critical Materiality
Severity Escalating
Severity Stable
Severity Reducing
Severity Evidence-Limited
Severity Conflicted
Severity Unknown
Severity Unresolved
Scarcity Evaluation Reassessment Required
136. Minimum Evidence Path
Where Scarcity Severity cannot be sufficiently evaluated:
Established / Emerging Scarcity or Constraint → Severity Unknown / Evidence-Limited / Conflicted → Missing Magnitude / Duration / Scope / Criticality / Dependency / Reserve / Consequence Evidence → Minimum Evidence Requirement → Evidence Acquisition → Magnitude Evaluation → Contextual Significance Evaluation → Severity / Materiality Determination → Resource Scarcity Evaluation Profile Update
137. Minimum Reassessment Framework
At minimum:
Current Resource Scarcity Evaluation Profile → New Scarcity / Constraint / Capacity / Criticality / Dependency / Reserve / Buffer / Consequence Evidence → Materiality Test → Magnitude Reassessment → Context Reassessment → Severity Reassessment
→ Materiality Reassessment → Trend Review → Monitoring Review → Profile Update → Version Update
138. Governance Requirements
A conforming RSEM implementation must:
1. identify the governed Resource; 2. preserve Resource Source where material; 3. preserve location where material; 4. preserve the applicable time horizon; 5. preserve the applicable Scarcity State reference; 6. preserve the applicable Constraint Type reference; 7. identify Constraint Magnitude where methodologically valid; 8. preserve absolute Constraint Magnitude where relevant; 9. preserve relative Constraint Magnitude where valid; 10. distinguish Constraint Magnitude from Constraint Severity; 11. support capacity-deficit evaluation; 12. support rate-deficit evaluation where relevant; 13. support temporal-deficit evaluation where relevant; 14. support spatial-deficit evaluation where relevant; 15. support quality-deficit evaluation where relevant; 16. preserve multi-dimensional deficits; 17. prevent one numerical deficit from becoming complete Scarcity evaluation; 18. determine Constraint Severity; 19. determine Scarcity Severity where applicable; 20. distinguish Constraint Severity from Scarcity Severity where material; 21. prevent large Resource deficit from becoming High Severity automatically; 22. prevent small Resource deficit from becoming Low Severity automatically; 23. support No Material Severity; 24. support Low Severity; 25. support Moderate Severity; 26. support High Severity; 27. support Critical Severity; 28. support Severity Evidence-Limited; 29. support Severity Conflicted; 30. support Severity Unknown; 31. support Severity Unresolved; 32. determine Resource Scarcity Materiality; 33. distinguish detected Constraint from Material Constraint; 34. support Immaterial state; 35. support Low Materiality; 36. support Material state; 37. support High Materiality; 38. support Critical Materiality; 39. distinguish Severity from Materiality; 40. preserve Constraint Duration; 41. evaluate duration significance; 42. prevent short duration from becoming Low Severity automatically; 43. prevent long duration from becoming Critical Severity automatically; 44. preserve Constraint Scope; 45. evaluate scope significance; 46. prevent large geographic scope from becoming High Severity automatically; 47. preserve Constraint Concentration; 48. distinguish aggregate deficit from local severity; 49. preserve materially unequal Constraint distribution; 50. distinguish aggregate Resource condition from condition experienced by every entity; 51. consume Resource Criticality evidence where relevant; 52. prevent Resource Criticality from becoming Scarcity Severity by itself; 53. preserve Criticality interaction;
54. preserve Dependency exposure; 55. prevent Resource Dependency from becoming Scarcity Severity by itself; 56. evaluate Dependency breadth where relevant; 57. evaluate Dependency depth where relevant; 58. prevent long Dependency chain from becoming High Severity automatically; 59. preserve reserve context; 60. prevent Resource reserve from becoming absence of Scarcity; 61. evaluate reserve adequacy; 62. preserve reserve-duration relationship where material; 63. preserve buffer context; 64. prevent available buffer from becoming Constraint Resolution; 65. preserve substitutability relevance; 66. distinguish potential substitute from available substitute; 67. distinguish available substitute from authorized substitute; 68. preserve recoverability relevance; 69. distinguish recoverable Resource from currently available Resource; 70. preserve Recovery governance boundary; 71. evaluate operational consequences where relevant; 72. distinguish Resource Constraint from operational failure; 73. distinguish potential consequence from observed consequence; 74. distinguish predicted consequence from observed consequence; 75. preserve interdependency relevance; 76. distinguish potential Constraint propagation from actual propagation; 77. evaluate Constraint accumulation; 78. distinguish individual Constraint Severity from combined Constraint Severity; 79. evaluate material Constraint interactions; 80. prevent multiple Constraint Types from becoming High Severity automatically; 81. preserve Scarcity concentration; 82. distinguish system-wide stability from low local severity; 83. preserve temporal concentration where relevant; 84. prevent short Scarcity window from becoming Low Governance Significance automatically; 85. identify Severity Escalation; 86. preserve material escalation drivers; 87. prevent worsening Scarcity State from becoming Severity Escalation automatically; 88. support Severity Stabilization; 89. distinguish Severity Stabilization from Scarcity Resolution; 90. support Severity Reduction; 91. distinguish reduced Severity from resolved Scarcity; 92. support Critical Severity; 93. prevent Critical Severity from requiring complete Resource exhaustion; 94. preserve severity thresholds where used; 95. preserve threshold provenance; 96. distinguish severity threshold from universal Resource threshold; 97. support dynamic Severity; 98. recognize that Severity may change while physical deficit remains stable; 99. distinguish stable physical deficit from stable governance Severity; 100. govern severity comparison where performed; 101. prevent equal physical deficits across Resources from becoming equal governance Severity; 102. preserve Resource-native measurements; 103. preserve normalization methodology where used; 104. distinguish normalized Resource significance from physical equivalence; 105. preserve Cross-Resource comparability without requiring physical equivalence; 106. preserve evaluation evidence; 107. preserve evidence provenance; 108. determine evidence sufficiency; 109. distinguish Scarcity evidence from Severity evidence; 110. support Severity Evidence-Limited; 111. support Severity Unknown; 112. prevent Severity Unknown from becoming Low Severity; 113. support Severity Conflicted; 114. prevent convenient severity selection under evidence conflict; 115. preserve measurement uncertainty; 116. preserve context uncertainty; 117. preserve evaluation confidence where used; 118. distinguish evaluation confidence from Scarcity Severity;
119. distinguish predicted Severity from current Severity; 120. distinguish simulated Severity from observed Severity; 121. distinguish historical Severity from current Severity; 122. preserve Severity Trend; 123. support Improving trend; 124. support Stable trend; 125. support Worsening trend; 126. support Volatile trend; 127. support Unknown trend; 128. distinguish current Severity from Severity Direction; 129. support evaluation monitoring; 130. preserve relevant monitoring inputs; 131. preserve reassessment triggers; 132. preserve RSSM Scarcity-State boundary; 133. preserve RCTM Constraint-Type boundary; 134. preserve RDGS Demand boundary; 135. preserve RDCS Dependency and Criticality boundary; 136. preserve RAGS Access boundary; 137. preserve RPAS Priority and Allocation boundary; 138. preserve RCUS Consumption & Utilization boundary; 139. preserve RRCS Recovery boundary; 140. preserve RSFS substitution boundary; 141. preserve RIRS resilience boundary; 142. preserve RCSS Sustainability boundary; 143. distinguish Scarcity Severity from Value; 144. distinguish Scarcity Severity from Harm Severity; 145. distinguish Scarcity Severity from Liability; 146. distinguish automated Severity evaluation from governance authority; 147. distinguish Critical Scarcity Evaluation from intervention authority; 148. preserve effective time; 149. preserve version history; 150. produce a Resource Scarcity Evaluation Profile.
139. Governance Logic
Canonical RSEM logic:
Resource Scarcity State → Resource Constraint Type → Constraint Magnitude → Duration / Scope / Concentration → Resource Criticality / Dependency Exposure → Reserve / Buffer / Substitutability / Recoverability → Operational Consequence / Interdependency Exposure → Constraint Severity → Scarcity Severity → Materiality → Severity Trend → Evidence / Uncertainty / Conflict → Resource Scarcity Evaluation Profile → Monitoring → Reassessment
140. Governance Outputs
RSEM may produce:
Resource Scarcity Evaluation Profile
Absolute Constraint Magnitude
Relative Constraint Magnitude
Capacity Deficit
Rate Deficit
Temporal Deficit
Spatial Deficit
Quality Deficit
Constraint Severity
Scarcity Severity
Resource Scarcity Materiality
Duration Significance
Scope Significance
Constraint Concentration
Dependency Exposure
Reserve Adequacy
Buffer State
Operational Consequence State
Interdependency Exposure
Combined Constraint Severity
Severity Trend
Severity Escalation State
Severity Stabilization State
Severity Reduction State
Evidence Sufficiency State
Evaluation Confidence
Uncertainty State
Conflict State
Monitoring State
Reassessment Trigger
Version:
141. Critical Distinctions
Scarcity State ≠ Scarcity Severity
Constraint Magnitude ≠ Constraint Severity
Large Resource Deficit ≠ High Governance Severity by definition
Small Resource Deficit ≠ Low Governance Severity by definition
Resource Criticality ≠ Scarcity Severity by itself
Resource Quantity Alone ≠ Scarcity Severity
Constraint Gap ≠ Constraint Severity
Equal Percentage Deficit ≠ Equal Scarcity Severity
One Numerical Deficit ≠ Complete Resource Scarcity Evaluation
Detected Constraint ≠ Material Constraint by definition
Severity ≠ Materiality
Short Duration ≠ Low Severity
Long Duration ≠ Critical Severity by definition
Large Geographic Scope ≠ High Severity automatically
Low Aggregate Deficit ≠ Low Local Severity
Aggregate Resource Condition ≠ Condition Experienced by Every Affected Entity
Resource Dependency ≠ Scarcity Severity by itself
Long Dependency Chain ≠ High Severity automatically
Resource Reserve ≠ Absence of Scarcity
Available Buffer ≠ Constraint Resolution
Potential Substitute ≠ Available Substitute
Available Substitute ≠ Authorized Substitute
Recoverable Resource ≠ Currently Available Resource
Resource Constraint ≠ Operational Failure by definition
Potential Consequence ≠ Observed Consequence
Predicted Operational Consequence ≠ Observed Operational Consequence
Potential Constraint Propagation ≠ Actual Constraint Propagation
Individual Constraint Severity ≠ Combined Constraint Severity
Multiple Constraint Types ≠ High Severity automatically
System-Wide Stability ≠ Low Severity for Every Local Context
Short Scarcity Window ≠ Low Governance Significance
Worsening Scarcity State ≠ Severity Escalation automatically
Severity Stabilization ≠ Scarcity Resolution
Reduced Severity ≠ Resolved Scarcity
Critical Severity ≠ Complete Resource Exhaustion
Severity Threshold ≠ Universal Resource Threshold by default
Stable Physical Deficit ≠ Stable Governance Severity
Equal Physical Deficit Across Different Resources ≠ Equal Governance Severity
Normalized Resource Significance ≠ Physical Resource Equivalence
Scarcity Evidence ≠ Severity Evidence by default
Severity Unknown ≠ Low Severity
Conflicting Severity Evidence ≠ Permission to Select the Most Convenient Severity
High Evaluation Confidence ≠ High Scarcity Severity
Predicted Severity ≠ Current Severity
Simulated Severity ≠ Observed Severity
Historical Severity ≠ Current Severity
Current Severity ≠ Severity Direction
Scarcity Evaluation ≠ Scarcity-State Creation
Scarcity Evaluation ≠ Constraint-Type Classification
Scarcity Severity ≠ Access Authority
Scarcity Severity ≠ Resource Priority
Scarcity Severity ≠ Allocation Authority
Scarcity Severity ≠ Sustainability Determination
High Value ≠ Low Scarcity Severity
High Value ≠ Automatic Resource Priority
Scarcity Severity ≠ Harm Severity
Scarcity Severity ≠ Liability
Automated Severity Evaluation ≠ Governance Authority
Critical Scarcity Evaluation ≠ Intervention Authority
142. Use Case 1 — AI Data Center Power Constraint
An AI data center requires 100 MW of electrical capacity during a critical workload period.
Operationally usable electrical capacity falls to 94 MW .
The absolute Constraint Magnitude is therefore:
6 MW
and the relative deficit is:
6% of the legitimate Resource requirement.
A percentage-only evaluation could classify the deficit as moderate.
RSEM evaluates the wider context.
Evidence shows:
the affected workloads include safety-critical infrastructure services; reserve generation can provide only 2 MW; battery buffer supports the remaining gap for 20 minutes; no immediate grid-capacity substitute is available; cooling capacity also depends on the same electrical supply; the Constraint is worsening.
RSEM therefore determines that the apparently limited 6% physical deficit has High to Critical governance significance because of Criticality, Dependency exposure, limited reserve duration, interdependency, and escalation.
RSEM does not reallocate power or terminate workloads.
It produces the governed Scarcity Evaluation required by the competent downstream mechanisms.
143. Use Case 2 — Regional Water Scarcity
A region requires 100,000 m³/day of treated water during a dry period.
Available deliverable capacity falls to 82,000 m³/day .
The physical deficit is:
18,000 m³/day
or:
18% of the legitimate requirement.
RSEM evaluates more than the percentage.
Evidence shows:
municipal drinking-water requirements are exposed; industrial users retain partial substitution capability; agricultural demand can be temporally adjusted; stored reserves can support essential functions for a limited period; one municipality experiences substantially greater shortage than the regional average; groundwater regeneration continues to decline.
RSEM therefore distinguishes:
regional Constraint Magnitude; localized Scarcity concentration; critical drinking-water Dependency exposure; available reserve protection; different substitution conditions across users; worsening regenerative conditions.
The result may classify overall regional Scarcity as High Severity while identifying a Critical localized evaluation for the most exposed municipality.
This prevents a single regional percentage from hiding materially different Resource realities.
144. Cross-Architecture Boundary
RSEM may consume:
RCHS — Resource identity, Source, state, and context.
RACS — Availability and capacity evidence.
RDGS — legitimate Resource requirement and Demand evidence.
RDCS — Dependency, Criticality, consequence, and dependency-chain evidence.
RAGS — Access evidence relevant to Resource exposure.
RPAS — Priority, Allocation, reserve, and reallocation context.
RCUS — Consumption and Utilization evidence.
RSSM — Resource Scarcity State.
RCTM — Resource Constraint Type and mechanism.
RSEM may provide evaluation evidence to:
RRCS — Resource Recovery & Circularity.
RSFS — Resource Substitution & Flexibility.
RIRS — Resource Interdependency & Resilience.
RCSS — Resource Continuity & Sustainability.
ORA™ — operational reality relationships.
PGA™ — predicted Scarcity relationships.
SIMULOS® — simulated Scarcity relationships.
VEGA™ — Value and efficiency governance.
HAGA™ — Harm governance.
LIGA™ — Liability governance.
RSEM does not absorb those mechanisms.
145. 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.
RSEM governs the evaluation of the significance of Resource Scarcity and Constraint .
It does not govern the downstream authority to reallocate, restrict, recover, substitute, interrupt, or otherwise intervene in Resource use.
146. Canonical Boundary
RSEM governs how the magnitude, severity, materiality, scope, duration, concentration, Dependency exposure, reserve and buffer context, substitutability and recoverability relevance, operational consequence, interdependency exposure, trend, evidence sufficiency, uncertainty, conflict, and overall governance significance of an established or emerging Resource Scarcity or Constraint state are evaluated, classified, monitored, and reassessed.
It does not independently establish the Resource Scarcity State, classify the underlying Constraint Type, determine Resource Demand, Dependency or Criticality, grant Access, determine Priority or Allocation, measure Resource Consumption, authorize Recovery or substitution, determine resilience or long-term Sustainability, determine Value, Harm, Liability, or authorize intervention.
Its principal governed output is the Resource Scarcity Evaluation Profile .
147. Canonical Closing Statement
The size of a Resource shortage does not determine its importance. A small deficit can threaten a critical system, while a larger deficit may remain manageable where reserves, buffers, substitutes, flexibility, and low-criticality dependencies exist.
RSEM makes Resource Scarcity evaluable in context — separating physical magnitude from governance severity and determining how duration, concentration, dependency, Criticality, reserves, operational consequences, and interdependencies transform a Resource limitation into a materially governed condition.