RSSM — Resource Scarcity State 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 State Governance
Module ID: RSGA-RSCS-RSSM-01
Origin ID: OOF-RSGA-RSCS-RSSM
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
RSSM — Resource Scarcity State Module governs how the Scarcity State of a defined Resource or Resource capacity is determined, represented, evidenced, localized, temporally bounded, classified, monitored, and reassessed relative to the legitimate Resource requirements and applicable Resource conditions of the governed Resource System.
RSSM establishes whether the Resource is:
sufficient; approaching Scarcity; actively scarce; locally scarce; widely scarce; severely scarce; critically scarce; stabilizing; relaxing; resolved; or insufficiently evidenced for a reliable Scarcity determination.
Its foundational distinctions are:
Resource Scarcity ≠ Resource Absence.
Resource Availability ≠ Resource Sufficiency.
Resource Constraint ≠ Resource Scarcity.
Unknown Scarcity State ≠ No Scarcity.
2. Operational Role
RSSM establishes the governed Resource Scarcity State.
It answers a narrower question than the RSCS Parent Standard.
RSCS governs the broader Scarcity and Constraint domain.
RSSM determines whether the actual Resource conditions applicable to a defined Resource requirement constitute Scarcity and, if so, what Scarcity State currently applies.
RSSM therefore transforms:
**Resource-condition evidence
legitimate Resource requirement applicable context**
into:
a governed Resource Scarcity State.
It does not independently determine the complete cause, severity mechanism, escalation response, Recovery action, substitution decision, Allocation response, or long-term Sustainability condition.
3. Operational Question
What is the current governed Scarcity State of the Resource relative to the applicable legitimate Resource requirement, Source, location, time horizon, usable and accessible capacity, and operational context, and with what evidence and confidence can that state be established?
4. Position in RSCS Governance
Canonical progression:
Governed Resource State → Legitimate Resource Requirement → Applicable Resource Capacity → Resource Sufficiency Comparison → Scarcity State Determination → Constraint Characterization → Severity Evaluation → Scarcity Response / Monitoring → Resolution Assessment → Reassessment
RSSM governs:
Resource Sufficiency Evidence → Resource Scarcity State
5. Governed Space
RSSM governs:
Resource Scarcity State Governance
This governed space concerns the determination and representation of whether a defined Resource is sufficient or scarce relative to the legitimate Resource requirements applicable within a defined Source, location, time horizon, capacity basis, and operational context.
6. Governed Object
The primary Governed Object is:
A Resource Scarcity State associated with a defined Resource, legitimate Resource requirement, Resource capacity basis, Source, location, time horizon, and operational context.
Canonical relationship:
**Resource Identity
Legitimate Resource Requirement Applicable Resource Capacity Resource Context Evidence → Resource Sufficiency Determination → Resource Scarcity State**
7. Scope
RSSM governs:
Resource Scarcity State determination; Resource sufficiency determination; Scarcity-state classification; Resource requirement reference; available-capacity reference; usable-capacity reference; accessible-capacity reference; allocable-capacity relevance; Source context; location context; temporal context; quality relevance; rate relevance; delivery relevance; Scarcity localization; Scarcity breadth; Scarcity persistence; Scarcity-state transition; Scarcity-state evidence; Scarcity-state uncertainty; Scarcity-state conflict; Scarcity-state confidence; Scarcity-state monitoring; Scarcity-state reassessment; traceability; versioning.
RSSM does not independently:
determine Resource Demand; determine Resource Dependency or Criticality; create Resource Access rights; determine Resource Priority; allocate Resources; measure Resource Consumption; determine the complete Constraint mechanism; determine the complete Constraint Severity model; authorize Scarcity responses; govern Resource Recovery; authorize Resource substitution; determine resilience; determine long-term Sustainability; determine Value; determine Harm; determine Liability.
8. Resource Scarcity State
A Resource Scarcity State represents the governed condition of Resource sufficiency relative to legitimate Resource requirements within a defined context.
Scarcity is therefore relational.
It cannot be established solely from the existence or quantity of a Resource.
9. Scarcity-State Principle
Resource Quantity Alone ≠ Resource Scarcity State.
A Scarcity determination requires both:
Resource-condition evidence
and
a legitimate Resource requirement against which sufficiency can be evaluated.
10. Resource Requirement Reference
Every Scarcity State should identify the Resource requirement against which sufficiency is evaluated.
The requirement may derive from:
validated Demand; critical dependency; minimum operational requirement; continuity requirement; governed Allocation commitment; other legitimate Resource requirement.
11. Requirement Legitimacy
RSSM should not treat every expressed Resource request as a legitimate Resource requirement.
Requested Resource Quantity ≠ Legitimate Resource Requirement by default.
RDGS governs Resource Demand.
12. Requirement Version
Where the applicable Resource requirement changes over time, RSSM should preserve the version or state applicable to the Scarcity determination.
Current Requirement ≠ Historical Requirement.
13. Resource Capacity Basis
RSSM should identify which Resource-capacity basis is relevant to the Scarcity determination.
Possible capacity bases include:
Available Capacity; Usable Capacity; Accessible Capacity; Allocable Capacity; deliverable capacity; other Resource-specific capacity.
14. Capacity-Basis Principle
Nominal Capacity ≠ Scarcity-Relevant Capacity by default.
The capacity basis must reflect the Resource conditions applicable to the legitimate requirement.
15. Available Capacity
Available Capacity may provide an input to Scarcity determination.
However:
Available Capacity ≠ Sufficient Capacity.
16. Usable Capacity
Where Resource condition, quality, compatibility, infrastructure, or operational restrictions reduce actual usability, RSSM should use the relevant usable capacity.
Physical Availability ≠ Operational Usability.
17. Accessible Capacity
A Resource may be available and usable in principle while inaccessible to the relevant requirement.
Usable Resource Somewhere ≠ Accessible Resource Here.
18. Allocable Capacity
Where Resource capacity is reserved, protected, already committed, or otherwise unavailable for additional Allocation, allocable capacity may materially affect the Scarcity State.
Available Capacity ≠ Allocable Capacity.
19. Resource Sufficiency
Resource Sufficiency exists where the Resource conditions applicable to the governed context are sufficient to support the legitimate Resource requirement.
20. Sufficiency Principle
Resource Sufficiency ≠ Resource Abundance.
A Resource may be sufficient without being abundant.
21. Sufficiency Margin
Where quantitatively meaningful, RSSM may preserve the margin between applicable Resource capacity and legitimate Resource requirement.
Conceptually:
Resource Sufficiency Margin = Applicable Resource Capacity − Legitimate Resource Requirement
A positive margin may indicate sufficient Resource conditions.
A negative margin may indicate Scarcity.
A near-zero margin may indicate vulnerability to Scarcity.
The exact calculation remains Resource-specific.
22. Sufficiency-Margin Boundary
Positive Sufficiency Margin ≠ Guaranteed Absence of Scarcity.
Location, Source, timing, quality, rate, accessibility, delivery, or other Resource conditions may still create Scarcity.
23. Negative Sufficiency Margin
A negative Resource Sufficiency Margin may provide evidence of Scarcity where the compared values are methodologically compatible.
24. Numerical-Gap Boundary
Negative Resource Sufficiency Margin ≠ Complete Scarcity Determination by itself.
The comparison must remain valid within the governed Resource context.
25. Comparison Compatibility
RSSM should establish whether Resource requirement and capacity evidence are sufficiently compatible for Scarcity determination.
Compatibility: may require alignment of:
Resource identity; Resource type; unit; capacity basis; Source; location; time horizon; quality; rate; operational context.
26. Compatibility Principle
Numerically Comparable Resource Values ≠ Governance-Compatible Resource Values by default.
27. Resource Identity Alignment
The Resource represented by capacity evidence should correspond sufficiently to the Resource required.
28. Resource-Type Boundary
Availability of Resource Type A ≠ Sufficiency of Resource Type B.
29. Source Alignment
Scarcity may be Source-specific.
RSSM should preserve the applicable Source where Source materially affects Resource sufficiency.
30. Source Principle
Availability From Another Source ≠ Absence of Source-Specific Scarcity.
31. Location Alignment
Scarcity determination should preserve the location applicable to the Resource requirement.
32. Location Principle
Resource Sufficiency Somewhere ≠ Resource Sufficiency Where Required.
33. Temporal Alignment
Resource capacity and Resource requirement should be compared across compatible time horizons.
34. Temporal Principle
Annual Resource Sufficiency ≠ Hourly Resource Sufficiency.
A Resource may be sufficient over a long period while scarce during critical intervals.
35. Rate Alignment
A Resource may exist in sufficient total quantity but remain insufficient at the rate required.
Quantity Sufficiency ≠ Rate Sufficiency.
36. Quality Alignment
Resource quality may determine whether Resource capacity is relevant to a particular requirement.
Quantity Available at Inadequate Quality ≠ Sufficient Usable Resource.
37. Delivery Alignment
A Resource may exist and satisfy quality conditions while delivery limitations prevent operational sufficiency.
Resource Existence ≠ Resource Deliverability.
38. Accessibility Alignment
Scarcity determination should preserve whether the Resource can actually be accessed by the relevant participant, system, function, or location.
39. Accessibility Principle
Inaccessible Resource Capacity ≠ Available Capacity for the Affected Requirement.
40. Scarcity Context
Every Scarcity State should preserve the materially relevant context in which Scarcity is determined.
This may include:
Resource; Source; location; time horizon; capacity basis; quality requirement; rate requirement; delivery condition; participant; system; function; operational state.
41. Context Principle
Scarcity Outside the Applicable Context ≠ Scarcity Within the Applicable Context.
42. Localized Scarcity
Localized Scarcity exists where Resource insufficiency applies within a bounded operational or geographic context while broader Resource conditions may remain sufficient.
43. Localized Scarcity Principle
Localized Scarcity ≠ System-Wide Scarcity.
44. Widespread Scarcity
Widespread Scarcity exists where Resource insufficiency materially affects multiple locations, participants, systems, Sources, or operational areas.
45. Widespread Scarcity Boundary
Multiple Local Scarcity States ≠ Widespread Scarcity automatically.
The breadth and relationship among affected areas must be established.
46. System-Level Scarcity
A Resource Scarcity State may become systemically significant where insufficiency materially affects the broader governed Resource System.
47. Aggregate Sufficiency
Aggregate Resource sufficiency may conceal local Scarcity.
Aggregate Resource Sufficiency ≠ Local Resource Sufficiency.
48. Aggregate Scarcity
Aggregate shortage may coexist with sufficient Resource conditions for some specific locations or functions.
Aggregate Scarcity ≠ Scarcity for Every Participant or Function.
49. Scarcity Emerging
Scarcity Emerging exists where evidence indicates that Resource sufficiency is deteriorating toward an active Scarcity State.
50. Emerging-State Principle
Scarcity Emerging ≠ Scarcity Active.
51. Scarcity Active
Scarcity Active exists where sufficient evidence establishes that applicable Resource conditions are insufficient relative to the legitimate Resource requirement.
52. Active-Scarcity Principle
Scarcity Active ≠ Resource Exhaustion.
A Resource may remain partially available while still being scarce.
53. Severe Scarcity
Severe Scarcity represents a Resource Scarcity State with substantial governance significance.
The complete severity mechanism remains governed elsewhere within RSCS.
RSSM may consume the resulting severity classification.
54. Critical Scarcity
Critical Scarcity represents a Scarcity State whose severity has reached the applicable critical governance level.
Critical Scarcity ≠ Zero Resource Remaining.
55. Scarcity Stabilized
Scarcity Stabilized exists where the Scarcity condition remains active but is no longer materially worsening within the applicable observation period.
56. Stabilization Principle
Scarcity Stabilized ≠ Scarcity Resolved.
57. Scarcity Relaxing
Scarcity Relaxing exists where Resource sufficiency is materially improving while Scarcity remains active.
58. Relaxation Principle
Improving Resource Conditions ≠ Scarcity Resolution.
59. Scarcity Resolved
Scarcity Resolved exists where sufficient evidence establishes that the relevant Resource conditions once again satisfy the applicable legitimate Resource requirement.
60. Resolution Principle
Temporary Resource Improvement ≠ Scarcity Resolution.
61. No Scarcity
No Scarcity should be established only where sufficient evidence supports Resource sufficiency within the applicable governed context.
62. No-Scarcity Evidence Principle
No Detected Scarcity ≠ Evidence of No Scarcity.
Evidence sufficiency remains necessary.
63. Scarcity Evidence-Limited
Scarcity Evidence-Limited applies where available evidence suggests a possible Scarcity condition but remains insufficient for a reliable determination.
64. Scarcity Unknown
Scarcity Unknown applies where Resource sufficiency cannot be adequately established.
Scarcity Unknown ≠ No Scarcity.
65. Scarcity Conflicted
Scarcity Conflicted applies where material evidence supports incompatible Scarcity determinations.
66. Conflict Principle
Conflicting Evidence ≠ Permission to Select the Most Convenient Scarcity State.
67. Scarcity Unresolved
Scarcity Unresolved applies where relevant evidence exists but a sufficiently supported Scarcity determination cannot yet be completed.
68. Minimum Scarcity States
RSSM should support at minimum:
No Scarcity
Scarcity Emerging
Scarcity Active
Scarcity Localized
Scarcity Widespread
Scarcity Severe
Scarcity Critical
Scarcity Stabilized
Scarcity Relaxing
Scarcity Resolved
Scarcity Evidence-Limited
Scarcity Conflicted
Scarcity Unknown
Scarcity Unresolved
Scarcity Reassessment Required
69. Scarcity-State Dimensions
A Scarcity State may require multiple dimensions rather than a single label.
These may include:
activation state; spatial state; temporal state; severity state; evidence state; trend state.
For example:
**Scarcity Active
Localized Temporary High Severity Evidence Sufficient Worsening**
may represent one governed Resource condition.
70. Multi-Dimensional Principle
One Scarcity Label ≠ Complete Scarcity State by default.
71. Temporal Scarcity State
Scarcity may be:
instantaneous; short-duration; temporary; recurring; persistent; other Resource-specific temporal state.
72. Recurring Scarcity
Scarcity may repeatedly emerge under similar conditions.
Examples include:
daily peaks; seasonal shortage; recurring infrastructure saturation; periodic Source limitation.
73. Recurrence Principle
Scarcity Resolution Between Events ≠ Absence of Recurring Scarcity Pattern.
74. Persistent Scarcity
Persistent Scarcity exists where Resource insufficiency remains materially active across the applicable governance horizon.
75. Persistence Boundary
Persistent Scarcity ≠ Structural Scarcity by definition.
The underlying Constraint mechanism determines whether the condition is structural.
76. Scarcity Trend
RSSM should preserve the direction of the Scarcity State where evidence permits.
Minimum trend states:
Improving
Stable
Worsening
Volatile
Unknown
77. Trend Principle
Current Scarcity State ≠ Scarcity Direction.
A Resource may remain critically scarce while improving.
78. Scarcity Transition
RSSM should preserve material transitions between Scarcity States.
Examples:
No Scarcity → Scarcity Emerging
Scarcity Emerging → Scarcity Active
Scarcity Active → Scarcity Severe
Scarcity Severe → Scarcity Stabilized
Scarcity Stabilized → Scarcity Relaxing
Scarcity Relaxing → Scarcity Resolved
79. Transition Evidence
A Scarcity-State transition should be supported by evidence appropriate to the Resource and governance context.
80. State Persistence
A Scarcity State should not be changed merely because one observation differs from the preceding trend where the Resource requires sustained evidence.
81. State-Persistence Principle
Single Improved Observation ≠ Scarcity Resolution by default.
82. Scarcity-State Monitoring
Active, Emerging, Recurring, Persistent, Evidence-Limited, Conflicted, or otherwise material Scarcity States should support monitoring appropriate to their governance significance.
83. Monitoring Inputs
Monitoring may consume:
Resource availability; usable capacity; accessible capacity; allocable capacity; Resource requirement; Consumption; Utilization; Source state; location state; quality state; delivery state; rate state;
reserve state; other relevant Resource evidence.
84. Evidence Basis
RSSM should preserve the evidence supporting the Scarcity State.
Evidence may include outputs from:
RCHS; RACS; RDGS; RDCS; RAGS; RPAS; RCUS; operational Resource systems; other governed evidence sources.
85. Evidence Provenance
Material Scarcity evidence should preserve sufficient provenance for traceability and reassessment.
86. Evidence Sufficiency
RSSM should determine whether available evidence is sufficient for the Scarcity State being asserted.
Missing Resource Evidence ≠ Evidence of Scarcity.
87. Evidence Sufficiency Boundary
Missing Resource Evidence ≠ Evidence of Resource Sufficiency.
Insufficient evidence supports uncertainty, not an invented Resource state.
88. Evidence Freshness
Scarcity determinations should use evidence sufficiently current for the applicable Resource and time horizon.
89. Historical Evidence
Historical Scarcity evidence may support trend or recurrence analysis.
However:
Historical Scarcity ≠ Current Scarcity.
90. Measurement Uncertainty
Material uncertainty in Resource-capacity or requirement evidence should propagate into the Scarcity State.
Uncertain Resource Capacity ≠ Certain Scarcity Determination.
91. Requirement Uncertainty
Uncertainty in the legitimate Resource requirement should remain visible.
Uncertain Requirement ≠ Precise Scarcity Gap.
92. Context Uncertainty
Uncertainty regarding Source, location, timing, quality, accessibility, or other context should remain visible where material.
93. Scarcity Confidence
RSSM may preserve a confidence state or evidence-confidence representation appropriate to the implementation.
Confidence must remain distinct from the Scarcity State itself.
High Confidence ≠ High Scarcity Severity.
94. Conflicting Capacity Evidence
Where multiple Resource-capacity measurements conflict materially, RSSM should preserve the conflict until sufficiently resolved.
95. Conflicting Requirement Evidence
Where legitimate Resource requirement evidence conflicts materially, the Scarcity determination should preserve the unresolved state.
96. Prediction Boundary
Predicted future Scarcity may support monitoring and early warning.
However:
Predicted Scarcity ≠ Current Scarcity.
PGA™ governs Prediction methodology where applicable.
97. Simulation Boundary
Simulation may test Resource sufficiency under hypothetical conditions.
Simulated Scarcity ≠ Observed Scarcity.
SIMULOS® governs simulation.
98. Early-Warning Boundary
A Resource may receive an Early-Warning signal while remaining currently sufficient.
Early Warning ≠ Active Scarcity.
99. Constraint Boundary
RSSM determines the Scarcity State.
It does not need to fully determine every underlying Constraint mechanism.
Scarcity State ≠ Complete Constraint Diagnosis.
100. Severity Boundary
RSSM may consume or represent Scarcity severity.
It does not replace the dedicated RSCS mechanism responsible for evaluating Constraint Severity.
Scarcity State ≠ Constraint Severity Model.
101. Access Boundary
Scarcity may trigger Access review.
However:
Scarcity State ≠ Access Decision.
RAGS retains Resource Access governance.
102. Priority Boundary
Scarcity may materially affect Priority governance.
However:
Scarcity State ≠ Priority Determination.
RPAS retains Priority governance.
103. Allocation Boundary
Scarcity may justify Allocation reassessment.
However:
Scarcity State ≠ Allocation Authority.
104. Recovery Boundary
Scarcity may increase the importance of Recovery.
However:
Scarcity State ≠ Recovery Decision.
RRCS governs Resource Recovery & Circularity.
105. Substitution Boundary
Scarcity may increase the need to evaluate alternative Resources.
However:
Scarcity State ≠ Substitution Authorization.
RSFS governs Resource Substitution & Flexibility.
106. Resilience Boundary
Scarcity may expose resilience weakness.
RSSM may provide Scarcity-state evidence to RIRS.
It does not determine Resource-system resilience.
107. Sustainability Boundary
A current Scarcity State may be relevant to Sustainability.
However:
Current Scarcity ≠ Long-Term Sustainability Determination.
RCSS governs Resource Continuity & Sustainability.
108. Value Boundary
A Resource may be scarce regardless of the Value produced through its use.
High Value ≠ Absence of Scarcity.
VEGA™ governs Value relationships where applicable.
109. Price Boundary
Market price may correlate with Resource pressure.
However:
High Price ≠ Scarcity State.
Low Price ≠ No Scarcity.
110. Ownership Boundary
Resource ownership does not determine Scarcity.
Ownership ≠ Resource Sufficiency.
111. Optimization Boundary
Optimization may improve Resource sufficiency.
However:
Optimization ≠ Scarcity Resolution.
112. Automated Scarcity Determination
Software may support Scarcity-state calculation and classification.
However:
Automated Scarcity Classification ≠ Governance Authority.
113. Scarcity-State Intervention Boundary
RSSM may produce evidence supporting intervention.
It does not independently authorize:
reallocation; Access restriction; reserve release; Recovery; substitution; shutdown; other Resource intervention.
Scarcity Evidence ≠ Intervention Authority.
114. Resource Scarcity State Profile
The principal RSSM output is the:
Resource Scarcity State Profile
115. Minimum Resource Scarcity State Profile Fields
At minimum:
Scarcity State ID
Resource ID
Resource Type
Resource Source
Location
Applicable Time Horizon
Resource Requirement Reference
Resource Requirement Version
Applicable Capacity Basis
Available Capacity Reference
Usable Capacity Reference
Accessible Capacity Reference
Allocable Capacity Reference where relevant
Resource Sufficiency Margin where applicable
Source State
Location State
Temporal State
Quality State where relevant
Rate State where relevant
Delivery State where relevant
Scarcity State
Localized / Widespread State
Temporal Scarcity State
Scarcity Trend
Scarcity Transition
Severity Reference where available
Evidence Basis
Evidence Provenance
Evidence Sufficiency
Measurement Uncertainty
Requirement Uncertainty
Context Uncertainty
Evidence Confidence
Conflict State
Monitoring State
Reassessment Trigger
Effective Time
Version:
116. Minimum Implementation Framework
A minimum operational RSSM implementation should contain eight governed layers.
Layer 1 — Resource Reference
Establish:
Resource identity; Resource type; Source; location; time horizon.
Layer 2 — Legitimate Requirement
Establish:
applicable Resource requirement; requirement basis; requirement version.
Layer 3 — Capacity Basis
Establish:
available; usable; accessible; allocable; or other applicable Resource capacity.
Layer 4 — Comparison Alignment
Validate:
Resource identity; unit; Source; location; time; quality; rate; capacity basis; operational context.
Layer 5 — Sufficiency Determination
Determine:
sufficient; near-constrained; insufficient; unknown; conflicted.
Layer 6 — Scarcity State
Establish:
activation; localization; temporal state; trend; evidence state.
Layer 7 — Monitoring & Reassessment
Establish:
monitoring requirement; state-transition trigger; reassessment trigger.
Layer 8 — Governed Output
Produce:
Resource Scarcity State Profile
Canonical machine-readable logic:
**Resource Evidence
Legitimate Resource Requirement Applicable Capacity → Comparison Alignment → Resource Sufficiency Determination → Scarcity State → Evidence / Uncertainty / Conflict → Monitoring / Reassessment → Resource Scarcity State Profile**
117. Minimum Decision States
At minimum:
Resource Sufficient
Resource Near Scarcity
Scarcity Emerging
Scarcity Active
Scarcity Localized
Scarcity Widespread
Scarcity Severe
Scarcity Critical
Scarcity Stabilized
Scarcity Relaxing
Scarcity Resolved
Scarcity Evidence-Limited
Scarcity Conflicted
Scarcity Unknown
Scarcity Unresolved
Scarcity Reassessment Required
118. Minimum Evidence Path
Where the Scarcity State cannot be sufficiently determined:
Scarcity Unknown / Evidence-Limited / Conflicted → Missing or Conflicting Requirement / Capacity / Source / Location / Time / Quality / Rate Evidence → Minimum Evidence Requirement → Evidence Acquisition → Comparison Alignment → Resource Sufficiency Determination → Scarcity-State Determination → Resource Scarcity State Profile Update
119. Minimum Reassessment Framework
At minimum:
Current Resource Scarcity State Profile → New Resource Evidence / Requirement Change / Capacity Change / Source Change / Location Change / Operational Change → Materiality Test → Comparison Revalidation → Resource Sufficiency Reassessment → Scarcity-State Reassessment → Trend / Transition Review → Monitoring Review → Profile Update → Version Update
120. Governance Requirements
A conforming RSSM implementation must:
1. identify the governed Resource; 2. preserve Resource type; 3. preserve Resource Source where material; 4. preserve location where material; 5. preserve the applicable time horizon; 6. identify the legitimate Resource requirement; 7. preserve the requirement basis; 8. preserve the applicable requirement version; 9. distinguish requested Resource quantity from legitimate Resource requirement; 10. identify the applicable Resource-capacity basis; 11. preserve Available Capacity evidence; 12. preserve Usable Capacity evidence where relevant; 13. preserve Accessible Capacity evidence where relevant; 14. preserve Allocable Capacity evidence where relevant; 15. distinguish nominal capacity from Scarcity-relevant capacity; 16. distinguish Resource availability from Resource sufficiency; 17. distinguish physical availability from operational usability; 18. distinguish usable Resource from accessible Resource; 19. distinguish available capacity from allocable capacity; 20. establish Resource Sufficiency; 21. distinguish Resource Sufficiency from Resource abundance; 22. preserve Resource Sufficiency Margin where methodologically valid; 23. prevent positive Sufficiency Margin from proving absence of Scarcity automatically; 24. preserve negative Sufficiency Margin where methodologically valid; 25. prevent numerical gap from becoming complete Scarcity determination; 26. validate comparison compatibility; 27. align Resource identity; 28. align Resource type; 29. align measurement units; 30. align capacity basis; 31. align Source where material; 32. align location where material; 33. align time horizon; 34. align quality where material; 35. align rate where material; 36. align delivery conditions where material; 37. preserve accessibility context; 38. prevent numerically comparable values from becoming governance-compatible automatically; 39. preserve Scarcity context; 40. distinguish Scarcity outside the applicable context from Scarcity within it; 41. support Localized Scarcity; 42. distinguish Localized Scarcity from System-Wide Scarcity; 43. support Widespread Scarcity; 44. prevent multiple local Scarcity states from becoming Widespread Scarcity automatically; 45. support system-level Scarcity where evidenced; 46. distinguish aggregate Resource sufficiency from local sufficiency; 47. distinguish aggregate Scarcity from Scarcity for every participant or function;
48. support Scarcity Emerging; 49. distinguish Scarcity Emerging from Scarcity Active; 50. support Scarcity Active; 51. distinguish Scarcity Active from Resource exhaustion; 52. support Scarcity Severe; 53. support Scarcity Critical; 54. prevent Critical Scarcity from requiring zero Resource remaining; 55. support Scarcity Stabilized; 56. distinguish Scarcity Stabilization from Scarcity Resolution; 57. support Scarcity Relaxing; 58. distinguish improving Resource conditions from Scarcity Resolution; 59. support Scarcity Resolved; 60. prevent temporary improvement from becoming Scarcity Resolution; 61. support No Scarcity; 62. require sufficient evidence for No Scarcity where material; 63. distinguish no detected Scarcity from evidence of No Scarcity; 64. support Scarcity Evidence-Limited; 65. support Scarcity Unknown; 66. prevent Scarcity Unknown from becoming No Scarcity; 67. support Scarcity Conflicted; 68. preserve conflicting evidence; 69. prevent convenient state selection under evidence conflict; 70. support Scarcity Unresolved; 71. support Scarcity Reassessment Required; 72. support multi-dimensional Scarcity representation; 73. distinguish one Scarcity label from complete Scarcity State; 74. preserve temporal Scarcity state; 75. support Recurring Scarcity; 76. preserve Scarcity recurrence; 77. distinguish resolution between events from absence of recurring Scarcity pattern; 78. support Persistent Scarcity; 79. distinguish Persistent Scarcity from Structural Scarcity; 80. preserve Scarcity Trend; 81. support Improving trend; 82. support Stable trend; 83. support Worsening trend; 84. support Volatile trend; 85. support Unknown trend; 86. distinguish current Scarcity State from Scarcity Direction; 87. preserve Scarcity-State transitions; 88. preserve transition evidence; 89. prevent isolated observations from changing Scarcity State without sufficient basis; 90. support Scarcity-state monitoring; 91. preserve relevant monitoring inputs; 92. preserve Scarcity evidence; 93. preserve evidence provenance; 94. determine evidence sufficiency; 95. prevent missing evidence from becoming evidence of Scarcity; 96. prevent missing evidence from becoming evidence of Resource sufficiency; 97. preserve evidence freshness; 98. distinguish historical Scarcity from current Scarcity; 99. propagate material capacity uncertainty; 100. propagate material requirement uncertainty; 101. propagate material context uncertainty; 102. prevent uncertain capacity from becoming certain Scarcity; 103. prevent uncertain requirement from becoming precise Scarcity gap; 104. preserve evidence confidence where used; 105. distinguish evidence confidence from Scarcity Severity; 106. preserve conflicting capacity evidence; 107. preserve conflicting requirement evidence; 108. distinguish predicted Scarcity from current Scarcity; 109. distinguish simulated Scarcity from observed Scarcity; 110. distinguish Early Warning from Active Scarcity; 111. distinguish Scarcity State from complete Constraint diagnosis; 112. distinguish Scarcity State from Constraint Severity model;
113. prevent Scarcity State from becoming Access decision; 114. prevent Scarcity State from becoming Priority determination; 115. prevent Scarcity State from becoming Allocation authority; 116. prevent Scarcity State from becoming Recovery decision; 117. prevent Scarcity State from becoming substitution authorization; 118. prevent Scarcity State from becoming resilience determination; 119. prevent current Scarcity from becoming long-term Sustainability determination; 120. distinguish high Value from absence of Scarcity; 121. distinguish price from Scarcity State; 122. distinguish ownership from Resource sufficiency; 123. distinguish optimization from Scarcity Resolution; 124. distinguish automated Scarcity classification from governance authority; 125. distinguish Scarcity evidence from intervention authority; 126. preserve reassessment triggers; 127. preserve effective time; 128. preserve version history; 129. maintain traceability to supporting Resource evidence; 130. produce a Resource Scarcity State Profile.
121. Governance Logic
Canonical RSSM logic:
Governed Resource → Legitimate Resource Requirement → Applicable Resource Capacity → Source / Location / Time / Quality / Rate / Accessibility Context → Comparison Compatibility → Resource Sufficiency Determination → Resource Scarcity State → Localization / Temporal State / Trend → Evidence / Uncertainty / Conflict → Monitoring → Resource Scarcity State Profile → Reassessment
122. Governance Outputs
RSSM may produce:
Resource Scarcity State Profile
Resource Sufficiency Determination
Resource Sufficiency Margin
Scarcity Activation State
Scarcity Localization State
Scarcity Temporal State
Scarcity Trend
Scarcity Transition
Scarcity Evidence State
Scarcity Confidence State
Scarcity Conflict State
Scarcity Monitoring State
Scarcity Reassessment Trigger
Effective Time
Version:
123. Critical Distinctions
Resource Scarcity ≠ Resource Absence
Resource Availability ≠ Resource Sufficiency
Resource Constraint ≠ Resource Scarcity
Unknown Scarcity State ≠ No Scarcity
Resource Quantity Alone ≠ Resource Scarcity State
Requested Resource Quantity ≠ Legitimate Resource Requirement by default
Current Requirement ≠ Historical Requirement
Nominal Capacity ≠ Scarcity-Relevant Capacity by default
Available Capacity ≠ Sufficient Capacity
Physical Availability ≠ Operational Usability
Usable Resource Somewhere ≠ Accessible Resource Here
Available Capacity ≠ Allocable Capacity
Resource Sufficiency ≠ Resource Abundance
Positive Sufficiency Margin ≠ Guaranteed Absence of Scarcity
Negative Resource Sufficiency Margin ≠ Complete Scarcity Determination by itself
Numerically Comparable Resource Values ≠ Governance-Compatible Resource Values by default
Availability From Another Source ≠ Absence of Source-Specific Scarcity
Resource Sufficiency Somewhere ≠ Resource Sufficiency Where Required
Annual Resource Sufficiency ≠ Hourly Resource Sufficiency
Quantity Sufficiency ≠ Rate Sufficiency
Quantity Available at Inadequate Quality ≠ Sufficient Usable Resource
Resource Existence ≠ Resource Deliverability
Inaccessible Resource Capacity ≠ Available Capacity for the Affected Requirement
Scarcity Outside the Applicable Context ≠ Scarcity Within the Applicable Context
Localized Scarcity ≠ System-Wide Scarcity
Multiple Local Scarcity States ≠ Widespread Scarcity automatically
Aggregate Resource Sufficiency ≠ Local Resource Sufficiency
Aggregate Scarcity ≠ Scarcity for Every Participant or Function
Scarcity Emerging ≠ Scarcity Active
Scarcity Active ≠ Resource Exhaustion
Critical Scarcity ≠ Zero Resource Remaining
Scarcity Stabilized ≠ Scarcity Resolved
Improving Resource Conditions ≠ Scarcity Resolution
Temporary Resource Improvement ≠ Scarcity Resolution
No Detected Scarcity ≠ Evidence of No Scarcity
Scarcity Unknown ≠ No Scarcity
Conflicting Evidence ≠ Permission to Select the Most Convenient Scarcity State
One Scarcity Label ≠ Complete Scarcity State by default
Scarcity Resolution Between Events ≠ Absence of Recurring Scarcity Pattern
Persistent Scarcity ≠ Structural Scarcity by definition
Current Scarcity State ≠ Scarcity Direction
Single Improved Observation ≠ Scarcity Resolution by default
Missing Resource Evidence ≠ Evidence of Scarcity
Missing Resource Evidence ≠ Evidence of Resource Sufficiency
Historical Scarcity ≠ Current Scarcity
Uncertain Resource Capacity ≠ Certain Scarcity Determination
Uncertain Requirement ≠ Precise Scarcity Gap
High Confidence ≠ High Scarcity Severity
Predicted Scarcity ≠ Current Scarcity
Simulated Scarcity ≠ Observed Scarcity
Early Warning ≠ Active Scarcity
Scarcity State ≠ Complete Constraint Diagnosis
Scarcity State ≠ Constraint Severity Model
Scarcity State ≠ Access Decision
Scarcity State ≠ Priority Determination
Scarcity State ≠ Allocation Authority
Scarcity State ≠ Recovery Decision
Scarcity State ≠ Substitution Authorization
Current Scarcity ≠ Long-Term Sustainability Determination
High Value ≠ Absence of Scarcity
High Price ≠ Scarcity State
Low Price ≠ No Scarcity
Ownership ≠ Resource Sufficiency
Optimization ≠ Scarcity Resolution
Automated Scarcity Classification ≠ Governance Authority
Scarcity Evidence ≠ Intervention Authority
124. Use Case 1 — AI Data Center Compute Scarcity
An AI data center has:
12,000 installed GPUs
but only:
9,000 GPUs are operationally usable; 7,500 are accessible to the relevant workload environment; 6,800 satisfy the required accelerator specification.
A validated workload requirement requires capacity equivalent to 7,200 compatible GPUs during a defined training period.
A simple inventory view would report 12,000 GPUs and conclude that capacity is sufficient.
RSSM instead establishes the applicable Scarcity context:
Resource — compatible accelerator capacity
Location — governed data center environment
Time — required training period
Legitimate Requirement — 7,200 compatible GPUs
Applicable Capacity — 6,800 usable and accessible compatible GPUs
The resulting Resource condition is insufficient relative to the legitimate requirement.
RSSM therefore establishes an Active Localized Resource Scarcity State , preserves the relevant evidence and uncertainty, and produces a Resource Scarcity State Profile.
It does not independently decide whether another workload should be suspended, whether capacity should be reallocated, or whether alternative compute should be substituted.
125. Use Case 2 — Regional Water Scarcity
A region contains enough annual water supply to exceed aggregate annual Demand.
During a six-week dry period, however:
Source A experiences reduced inflow; groundwater regeneration falls; treatment capacity is limited; one municipality experiences peak Demand; transport capacity prevents sufficient water from being transferred from another part of the region.
Annual Resource quantity therefore suggests sufficiency.
The operational context does not.
RSSM establishes the applicable Scarcity determination using:
the municipality as the relevant location; the six-week period as the relevant time horizon; treated and deliverable water as the relevant Resource capacity; validated municipal requirements as the legitimate Resource requirement.
The evidence establishes a Localized Active Scarcity State even though aggregate annual regional water quantity remains sufficient.
RSSM preserves that distinction without converting the local Scarcity State into a claim of system-wide regional water Scarcity.
126. Cross-Architecture Boundary
RSSM may consume:
RCHS — Resource identity, type, Source, state, and context.
RACS — Available, usable, reserved, temporal, location, and accessibility capacity evidence.
RDGS — governed Resource Demand and legitimate requirement evidence.
RDCS — Dependency and Criticality evidence relevant to Scarcity context.
RAGS — Access conditions affecting accessible Resource capacity.
RPAS — Allocation and reserve context.
RCUS — actual Consumption and Utilization evidence.
Other RSCS mechanisms may provide:
Constraint mechanism; Constraint Severity; escalation; resolution; other Scarcity-governance evidence.
RSSM may provide Scarcity-state evidence to:
RRCS — Resource Recovery & Circularity.
RSFS — Resource Substitution & Flexibility.
RIRS — Resource Interdependency & Resilience.
RCSS — Resource Continuity & Sustainability.
ORA™ — operational reality relationships.
PGA™ — prediction relationships without treating Prediction as current Scarcity.
SIMULOS® — simulation relationships without treating simulation as observed Scarcity.
VEGA™ — Value and efficiency relationships.
HAGA™ — Harm governance.
LIGA™ — Liability governance.
RSSM does not absorb these mechanisms.
127. 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.
RSSM governs the Resource Scarcity State .
It does not govern the downstream decisions that Scarcity evidence may trigger.
128. Canonical Boundary
RSSM governs how the Scarcity State of a defined Resource or Resource capacity is determined, represented, evidenced, localized, temporally bounded, classified, monitored, and reassessed relative to the legitimate Resource requirement and applicable Resource conditions, including capacity basis, Source, location, time horizon, quality, rate, accessibility, delivery, evidence sufficiency, uncertainty, conflict, trend, and state transition.
It does not independently determine Resource Demand, Resource Dependency or Criticality, Access rights, Resource Priority or Allocation, Resource Consumption measurement, complete Constraint diagnosis or Severity, Recovery action, substitution authorization, resilience, long-term Sustainability, Value, Harm, or Liability.
Its principal governed output is the Resource Scarcity State Profile .
129. Canonical Closing Statement
Scarcity cannot be established by counting how much Resource exists. It must be determined against what is legitimately required, what capacity is actually usable and accessible, where and when that capacity is needed, and whether the evidence supports the resulting Resource state.
RSSM turns Scarcity from a broad claim of shortage into a governed Resource state — distinguishing existence from sufficiency, aggregate availability from local reality, emerging pressure from active Scarcity, and uncertainty from evidence of absence.