RCAM — Resource Continuity Assessment Module
Architecture:
RSGA™ — Resource Sustainability Governance Architecture
Parent Standard:
RCSS — Resource Continuity & Sustainability Standard
Category:
Governance & Enforcement
Subcategory:
Resource Governance
Type:
Core Module
Governed Space:
Resource Continuity Assessment Governance
Module ID:
RSGA-RCSS-RCAM-01
Origin ID:
OOF-RSGA-RCSS-RCAM
Version:
1.0
Status:
Canonical Open
Effective Date:
9 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
RCAM — Resource Continuity Assessment Module is the Core Module within RCSS that governs how the continued availability, accessibility, adequacy, and operational usability of Resources required to sustain defined operational functions are identified, evaluated, evidenced, classified, monitored, and reassessed across specified temporal, geographic, operational, capacity, demand, dependency, and disturbance conditions.
RCAM establishes the methodological conditions under which Resource continuity may be evaluated as a bounded operational capability rather than inferred from present Resource availability, installed capacity, contractual supply arrangements, historical performance, or documented contingency plans.
It evaluates whether the Resources supporting required operational functions can remain available and usable throughout the applicable assessment horizon, including periods of changing demand, supply variability, capacity degradation, dependency disruption, and Resource constraints.
RCAM distinguishes continuity of Resource supply from continuity of required operational functions.
It also distinguishes projected Resource continuity from demonstrated operational continuity and preserves the conditions under which either conclusion remains applicable.
Resource Available Now ≠ Resource Continuously Available.
Resource Supply Maintained ≠ Required Operational Function Maintained.
Installed Resource Capacity ≠ Continuously Usable Resource Capacity.
Resource Continuity Demonstrated ≠ Resource Sustainability Demonstrated.
2. Operational Role
RCAM governs the assessment of Resource continuity across defined operational and temporal conditions.
Its operational role is to establish:
Resource System continuity identity. Required operational functions. Resource continuity assessment boundary. Assessment horizon. Resource continuity requirements. Resource availability continuity. Resource capacity continuity. Resource demand continuity. Resource access continuity. Resource dependency continuity. Supporting infrastructure continuity. Resource quality continuity. Resource delivery continuity. Resource timing requirements. Resource supply variability. Resource capacity degradation. Resource demand growth. Resource competition. Resource scarcity exposure. Resource disturbance exposure. Resource resilience references. Resource continuity gaps. Resource continuity uncertainty. Resource continuity classification. Resource continuity monitoring. Reassessment conditions. Downstream Sustainability handoff.
RCAM does not independently establish Resource Sustainability, determine Resource allocation priorities, grant Resource Access, execute operational interventions, or guarantee future Resource availability.
3. Core Question
How should Resource continuity be assessed so that the Resources required to sustain defined operational functions remain demonstrably available, accessible, adequate, and usable across the relevant assessment horizon without confusing present availability, installed capacity, contractual supply, theoretical backup arrangements, or short-term operational success with validated future Resource continuity?
4. Position in Architecture Governance Flow
RSGA™ Governance Flow
Resource Characterization → Resource Availability & Capacity → Resource Demand → Resource Dependency & Criticality → Resource Access → Resource Prioritization & Allocation → Resource Consumption & Utilization → Resource Scarcity & Constraint → Resource Recovery & Circularity → Resource Substitution & Flexibility → Resource Interdependency & Resilience → Resource Continuity & Sustainability
RCSS Core Module Flow
1. RCAM — Resource Continuity Assessment Module 2. Resource Consumption & Replenishment Sustainability 3. Resource Sustainability Impact & Tradeoff 4. Resource Sustainability Validation 5. Resource Continuity & Sustainability Monitoring
RCAM occupies the first Core Module position within RCSS.
It establishes the Resource continuity assessment foundation upon which subsequent Resource Sustainability evaluations depend.
Resource Continuity Identity → Required Operational Functions → Assessment Horizon → Resource Continuity Requirements → Availability & Capacity Continuity → Demand & Dependency Continuity → Access & Delivery Continuity → Resource Continuity Constraints → Evidence Assessment → Resource Continuity Classification → Resource Continuity Assessment Profile → Sustainability Governance Handoff
5. Governed Space
Resource Continuity Assessment Governance
This governed space concerns the evidence-supported ability of an identifiable Resource System to maintain the Resource conditions required for defined operational functions throughout a specified assessment horizon.
It includes:
Continuity identity. Continuity boundaries. Assessment horizons. Required operational functions. Resource requirements. Resource availability continuity. Resource capacity continuity. Resource demand continuity. Resource access continuity. Resource dependency continuity. Supporting infrastructure. Resource quality. Resource delivery. Temporal variability. Resource constraints.
Continuity gaps. Evidence sufficiency. Continuity classification. Monitoring and reassessment.
It does not independently govern Resource characterization, Resource supply creation, allocation execution, disturbance propagation, resilience validation, or long-term Sustainability determination.
6. Governed Object
The primary Governed Object is:
A Resource Continuity Assessment State representing the evidence-supported ability of an identifiable Resource System to maintain the Resource availability, access, usable capacity, quality, delivery, and supporting dependencies required for specified operational functions throughout a defined assessment horizon.
The state must preserve:
Resource System Identity
Assessment Boundary
Assessment Horizon
Required Operational Functions
Required Resource Conditions
Expected Resource Availability
Usable Resource Capacity
Resource Demand
Resource Access Conditions
Supporting Dependencies
Continuity Constraints
Evidence Sufficiency
Continuity Classification
Validity Conditions
Reassessment Requirements
7. Scope
RCAM governs:
Resource continuity identity. Resource System boundaries. Temporal assessment horizons. Operational function continuity requirements. Resource requirement continuity. Resource availability continuity. Resource capacity continuity. Resource demand continuity. Resource access continuity. Resource dependency continuity. Supporting infrastructure continuity. Resource quality continuity.
Resource delivery continuity. Resource timing. Resource variability. Resource scarcity exposure. Resource disturbance exposure. Resource continuity gaps. Resource continuity evidence. Continuity uncertainty. Continuity classification. Monitoring. Reassessment.
RCAM does not independently establish environmental Sustainability, economic Sustainability, replenishment sustainability, intergenerational Sustainability, Harm, Liability, or jurisdiction-specific compliance.
8. Foundational Governance Principles
8.1 Present Availability Principle
Resource Available Now ≠ Resource Continuously Available.
8.2 Functional Continuity Principle
Resource Supply Maintained ≠ Required Operational Function Maintained.
8.3 Capacity Continuity Principle
Installed Resource Capacity ≠ Continuously Usable Resource Capacity.
8.4 Temporal Adequacy Principle
Resource Adequate Today ≠ Resource Adequate Throughout the Assessment Horizon.
8.5 Dependency Continuity Principle
Resource Source Available ≠ Supporting Resource Dependencies Available.
8.6 Access Continuity Principle
Resource Access Granted ≠ Resource Access Continuously Maintained.
8.7 Evidence Principle
Resource Continuity Planned ≠ Resource Continuity Demonstrated.
8.8 Sustainability Boundary Principle
Resource Continuity Demonstrated ≠ Resource Sustainability Demonstrated.
9. Resource System Continuity Identity
Every RCAM assessment must establish the identity of the Resource System being evaluated.
Minimum elements include:
Resource System ID
Continuity Assessment ID
Operational Context
Required Operational Functions
Resource Categories
Assessment Boundary
Assessment Horizon
Geographic Context
Evidence Basis
Version:
10. Resource Continuity Assessment Boundary
The assessment boundary establishes the extent of the Resource continuity conclusion.
Relevant dimensions include:
Resource System Boundary
Operational Function Boundary
Resource Category Boundary
Supply Boundary
Capacity Boundary
Demand Boundary
Dependency Boundary
Access Boundary
Delivery Boundary
Temporal Boundary
Geographic Boundary
Evidence Boundary
11. Boundary Integrity
Continuity Established Within a Defined Boundary ≠ Continuity Established Across the Entire Resource System.
A Resource System may maintain continuity for selected operational functions while other functions remain exposed to Resource shortages or dependency failures.
12. Assessment Horizon
The assessment horizon defines the period across which Resource continuity is evaluated.
Relevant horizons may include:
Immediate Operational Horizon
Short-Term Continuity Horizon
Medium-Term Planning Horizon
Long-Term Operational Horizon
The applicable duration must be explicitly defined.
RCAM does not impose a universal continuity horizon across all Resource Systems.
13. Temporal Integrity
Continuity Demonstrated for One Period ≠ Continuity Demonstrated for Every Future Period.
14. Required Operational Functions
RCAM must identify the operational functions requiring Resource continuity.
Relevant elements include:
Function Identity
Function Purpose
Required Resource Inputs
Required Resource Quantity
Required Resource Quality
Required Resource Availability
Required Resource Timing
Permitted Functional Degradation
Evidence Basis
15. Functional Requirement Integrity
Operational Function Identified ≠ Resource Requirements Completely Established.
16. Resource Continuity Requirements
Resource continuity requirements define the conditions necessary to maintain required operational functions.
Relevant elements include:
Required Resource Quantity
Required Resource Capacity
Required Resource Quality
Required Resource Accessibility
Required Resource Delivery Rate
Required Resource Timing
Required Resource Duration
Supporting Resource Dependencies
17. Requirement Integrity
Resource Quantity Sufficient ≠ All Resource Continuity Requirements Satisfied.
18. Resource Availability Continuity
Resource availability continuity concerns whether required Resources are expected to remain available throughout the assessment horizon.
Relevant elements include:
Current Availability
Expected Availability
Availability Duration
Availability Variability
Supply Constraints
Supply Reliability Evidence
Supporting Dependencies
Uncertainty
Availability assessment mechanisms remain governed by RACS.
19. Availability Continuity Principle
Current Resource Availability ≠ Future Resource Availability.
20. Resource Capacity Continuity
Resource capacity continuity concerns whether usable Resource capacity can remain sufficient over the assessment horizon.
Relevant elements include:
Installed Capacity
Usable Capacity
Capacity Degradation
Capacity Maintenance
Capacity Expansion
Capacity Competition
Supporting Infrastructure
Capacity Constraints
21. Capacity Continuity Principle
Capacity Installed ≠ Capacity Continuously Usable.
22. Resource Demand Continuity
Resource demand may change throughout the assessment horizon.
Relevant elements include:
Current Demand
Projected Demand
Demand Variability
Peak Demand
Demand Growth
Demand Reduction
Operational Changes
Evidence Uncertainty
Demand governance remains within RDGS.
23. Demand Continuity Principle
Current Demand Covered ≠ Future Demand Covered.
24. Resource Adequacy Over Time
Resource adequacy concerns whether expected usable Resource availability and capacity remain sufficient for required demand.
Relevant elements include:
Expected Resource Availability
Usable Capacity
Required Demand
Peak Demand
Capacity Margins
Resource Quality
Delivery Conditions
Temporal Variability
25. Adequacy Principle
Average Resource Adequacy ≠ Resource Adequacy During Critical Periods.
26. Resource Access Continuity
Resource Access continuity concerns whether the Resource System can continue obtaining or using required Resources under applicable access conditions.
Relevant elements include:
Access Basis
Access Duration
Access Conditions
Access Restrictions
Competing Access
Institutional Dependencies
Contractual Conditions
Access Uncertainty
Access governance remains within RAGS.
27. Access Continuity Principle
Resource Access Currently Permitted ≠ Resource Access Guaranteed Throughout the Assessment Horizon.
28. Resource Dependency Continuity
Resource dependency continuity concerns whether supporting Resources and infrastructure can remain available and operationally relevant.
Relevant elements include:
Supporting Resource Identity
Dependency Type
Dependency Duration
Shared Dependencies
Indirect Dependencies
Infrastructure Dependencies
Dependency Variability
Evidence Basis
Dependency governance remains within RDCS and RIRS according to their respective governed domains.
29. Dependency Continuity Principle
Primary Resource Available ≠ Supporting Dependency Chain Continuously Available.
30. Supporting Infrastructure Continuity
Supporting infrastructure may determine whether Resources remain usable.
Relevant elements include:
Electricity Infrastructure
Water Infrastructure
Transport Infrastructure
Storage Infrastructure
Distribution Infrastructure
Control Infrastructure
Processing Infrastructure
Communication Infrastructure
31. Infrastructure Continuity Principle
Resource Supply Exists ≠ Resource Delivery Infrastructure Continuously Operational.
32. Resource Quality Continuity
Resource continuity requires the preservation of quality conditions relevant to operational use.
Relevant elements include:
Required Quality
Expected Quality
Quality Variability
Quality Degradation
Treatment Requirements
Processing Requirements
Quality Evidence
33. Quality Continuity Principle
Resource Quantity Available ≠ Resource Quality Operationally Sufficient.
34. Resource Delivery Continuity
Resource delivery continuity concerns whether required Resources can reach the relevant operational function under applicable conditions.
Relevant elements include:
Delivery Pathway
Delivery Capacity
Delivery Rate
Delivery Timing
Delivery Infrastructure
Delivery Constraints
Alternative Delivery Conditions
35. Delivery Continuity Principle
Resource Available at Source ≠ Resource Delivered Where Required.
36. Resource Timing Continuity
Resource continuity depends on Resource availability at the time of operational need.
Relevant elements include:
Required Time
Expected Availability Time
Delivery Delay
Supply Interruption
Peak Demand Timing
Buffer Duration
Operational Timing Constraints
37. Timing Principle
Resource Available Eventually ≠ Resource Available When Required.
38. Resource Supply Variability
Resource supply may vary across the assessment horizon.
Relevant conditions include:
Seasonal Variability
Operational Variability
Geographic Variability
Environmental Variability
Infrastructure Variability
Market Variability
Regulatory or Institutional Changes
39. Variability Principle
Average Resource Supply ≠ Resource Supply During Critical Operating Conditions.
40. Resource Capacity Degradation
Usable Resource capacity may decline over time.
Relevant mechanisms include:
Equipment Wear
Infrastructure Degradation
Resource Quality Decline
Maintenance Constraints
Supporting Resource Shortage
Environmental Conditions
Operational Overload
41. Degradation Principle
Capacity Available at Assessment Time ≠ Capacity Maintained Throughout the Assessment Horizon.
42. Resource Demand Growth
Increasing Resource demand may undermine continuity even where supply remains stable.
Relevant drivers include:
Production Expansion
Computational Growth
Population Growth
Operational Intensification
New Resource-Dependent Functions
Increased Quality Requirements
43. Growth Principle
Supply Stable ≠ Resource Continuity Stable When Demand Increases.
44. Resource Competition
Competing Resource demand may affect continuity.
Relevant elements include:
Competing Users
Shared Resource Sources
Allocation Constraints
Access Restrictions
Demand Peaks
Priority References
Supply Competition
RCAM evaluates continuity implications without determining allocation authority.
45. Competition Principle
Resource Physically Available ≠ Resource Available to Every Competing User.
46. Resource Scarcity Exposure
Resource scarcity may threaten continuity.
Relevant elements include:
Scarcity Type
Scarcity Duration
Scarcity Severity
Scarcity Frequency
Affected Resources
Affected Functions
Supporting Constraints
Scarcity mechanisms remain governed by RSCS.
47. Scarcity Continuity Principle
Resource Scarcity Not Present Today ≠ Resource Scarcity Absent Throughout the Assessment Horizon.
48. Resource Disturbance Exposure
Resource disturbances may affect continuity through direct or indirect Resource dependencies.
Relevant elements include:
Disturbance Scenario
Affected Resource
Disturbance Duration
Propagation Pathways
Supporting Infrastructure
Required Functions
Response & Recovery References
Disturbance propagation remains governed by RIRS.
49. Disturbance Continuity Principle
Resource System Resilient to a Defined Disturbance ≠ Resource Continuity Guaranteed Throughout the Assessment Horizon.
50. Resource Buffer Contribution
Resource buffers may support continuity during temporary supply interruptions or demand increases.
Relevant elements include:
Buffer Identity
Usable Quantity
Usable Duration
Quality Conditions
Replenishment Requirements
Activation Conditions
Supporting Dependencies
51. Buffer Principle
Resource Buffer Exists ≠ Resource Continuity Established.
52. Alternative Resource Arrangements
Alternative Resource arrangements may support continuity.
Relevant elements include:
Alternative Resource Source
Substitution Compatibility
Availability
Usable Capacity
Access Conditions
Supporting Dependencies
Transition Timing
Operational Limitations
Substitution mechanisms remain governed by RSFS.
53. Alternative Arrangement Principle
Alternative Resource Identified ≠ Alternative Resource Continuously Available and Usable.
54. Resource Recovery Contribution
Recovered Resources may contribute to Resource continuity.
Relevant elements include:
Recovered Resource Quantity
Recovered Resource Quality
Recovery Timing
Recovery Capacity
Supporting Resource Requirements
Operational Usability
Recovery Constraints
Recovery mechanisms remain governed by RRCS.
55. Recovery Contribution Principle
Resource Recovery Capability Exists ≠ Resource Continuity Requirement Satisfied.
56. Resource Resilience Contribution
Resource resilience may support continuity under defined disturbance conditions.
RCAM may use the Resource Resilience Validation & Monitoring Profile established by RIRS.
Relevant elements include:
Validated Disturbance Tolerance
Usable Protective Capacity
Response Readiness
Recovery Capability
Residual Vulnerability
Validation Conditions
57. Resilience Contribution Principle
Resilience Validated for a Disturbance Scenario ≠ Long-Term Resource Continuity Validated.
58. Resource Continuity Gap
A Resource continuity gap exists where expected Resource conditions do not satisfy required operational conditions within the assessment horizon.
Relevant elements include:
Affected Resource
Required Condition
Expected Condition
Gap Magnitude
Gap Duration
Affected Operational Function
Evidence Basis
59. Continuity Gap Principle
Continuity Gap Identified ≠ Continuity Gap Resolved.
60. Continuity Constraint Interaction
Multiple constraints may interact.
Examples include:
Capacity Degradation Combined with Demand Growth
Resource Scarcity Combined with Access Restrictions
Supply Variability Combined with Limited Storage
Infrastructure Degradation Combined with Dependency Concentration
Delivery Constraints Combined with Peak Demand
61. Constraint Interaction Principle
Individual Constraints Manageable ≠ Combined Constraints Manageable.
62. Continuity Scenario Assessment
RCAM may evaluate continuity under defined scenarios.
Relevant scenarios include:
Stable Resource Conditions
Demand Growth
Reduced Supply
Capacity Degradation
Access Restriction
Infrastructure Interruption
Persistent Scarcity
Combined Resource Constraints
Scenario assumptions must remain explicit.
63. Scenario Integrity
Continuity Projected Under a Scenario ≠ Continuity Operationally Demonstrated.
64. Resource Continuity Evidence
RCAM may use:
Resource Availability Records
Capacity Assessments
Demand Records
Dependency Profiles
Access Records
Delivery Performance
Infrastructure Assessments
Scarcity Profiles
Resilience Validation Profiles
Operational Observations
Scenario Analyses
65. Evidence Provenance
Continuity evidence must preserve:
Evidence ID
Source
Origin
Collection Method
Time
Location
Resource Identity
Operational Context
Assessment Horizon
Evidence Content
Known Limitations
Version:
66. Evidence Sufficiency
Evidence sufficiency concerns whether the available evidence supports the continuity conclusion.
Relevant dimensions include:
Resource Coverage
Operational Function Coverage
Temporal Coverage
Demand Coverage
Capacity Coverage
Dependency Coverage
Access Coverage
Delivery Coverage
Scenario Relevance
Evidence Reliability
67. Evidence Sufficiency Principle
Resource Continuity Data Available ≠ Resource Continuity Demonstrated.
68. Continuity Uncertainty
Uncertainty may arise from:
Future Supply
Future Demand
Capacity Degradation
Resource Access
Infrastructure Availability
Environmental Conditions
Dependency Changes
Scarcity Conditions
Operational Requirements
69. Uncertainty Principle
Future Resource Conditions Uncertain ≠ Resource Continuity Automatically Supported.
70. Resource Continuity Classification
RCAM may classify Resource continuity as:
Not Assessed
Assessment Pending
Continuity Supported Within Defined Conditions
Continuity Conditionally Supported
Continuity Partially Supported
Continuity At Risk
Continuity Insufficient
Evidence-Limited
Conflicted
Unknown
Reassessment Required
Every classification must preserve the assessment horizon, relevant operational functions, and evidence limitations.
71. Classification Integrity
Continuity Supported Within Defined Conditions ≠ Continuity Guaranteed Under All Conditions.
72. Conditional Continuity
Conditional continuity applies where operational Resource support depends on explicitly identified conditions.
Examples include:
Alternative Supply Remains Available
Demand Remains Below Defined Capacity
Supporting Infrastructure Remains Operational
Resource Access Remains Valid
Required Resource Quality Is Maintained
Conditions must remain attached to the continuity classification.
73. Conditional Continuity Principle
Continuity Conditionally Supported ≠ Continuity Unconditionally Established.
74. Resource Continuity Assessment Profile
The principal governed output is the:
Resource Continuity Assessment Profile
It establishes the evidence-supported Resource conditions required to maintain specified operational functions throughout a defined assessment horizon.
The profile preserves:
Resource System identity. Assessment boundary. Assessment horizon. Required operational functions. Resource requirements. Availability continuity. Capacity continuity. Demand continuity. Access continuity. Dependency continuity. Infrastructure continuity. Quality continuity. Delivery continuity. Temporal variability. Continuity constraints. Continuity gaps. Evidence sufficiency.
Uncertainty. Classification. Monitoring requirements. Reassessment triggers. Downstream Sustainability references.
75. Minimum Profile Fields
At minimum:
Resource Continuity Assessment Profile ID
Resource System ID
Assessment ID
Assessment Boundary
Assessment Horizon
Required Operational Functions
Resource Categories
Resource Continuity Requirements
Availability Continuity Assessment
Capacity Continuity Assessment
Demand Continuity Assessment
Access Continuity Assessment
Dependency Continuity Assessment
Supporting Infrastructure Assessment
Quality Continuity Assessment
Delivery Continuity Assessment
Timing Requirements
Supply Variability
Capacity Degradation
Demand Growth
Resource Competition
Scarcity Exposure
Disturbance Exposure
Buffer Contribution
Alternative Resource Arrangements
Recovery Contribution
Resilience Contribution
Continuity Gaps
Constraint Interactions
Scenario References
Evidence Provenance
Evidence Sufficiency
Missing Evidence
Uncertainty
Continuity Classification
Validity Conditions
Monitoring Signals
Reassessment Triggers
Downstream Sustainability Handoff
Effective Time
Version:
76. Minimum Implementation Framework
A minimum operational RCAM implementation should contain ten governed layers.
Layer 1 — Resource System & Continuity Identity
Establish the Resource System, assessment identity, operational context, and continuity boundary.
Layer 2 — Required Operational Functions
Identify the functions that must remain supported and their Resource requirements.
Layer 3 — Assessment Horizon
Define the temporal period across which continuity is evaluated.
Layer 4 — Availability & Capacity Continuity
Evaluate whether expected Resource availability and usable capacity remain sufficient.
Layer 5 — Demand & Adequacy Continuity
Evaluate current and projected demand, peak requirements, and temporal adequacy.
Layer 6 — Access, Dependency & Delivery Continuity
Evaluate Resource Access, supporting dependencies, infrastructure, quality, delivery, and timing.
Layer 7 — Constraint & Disturbance Exposure
Evaluate scarcity, variability, degradation, competing demand, disturbance exposure, and combined constraints.
Layer 8 — Continuity Evidence & Classification
Evaluate evidence sufficiency, uncertainty, continuity gaps, and the resulting continuity state.
Layer 9 — Monitoring & Reassessment
Establish monitoring signals, material change conditions, and reassessment triggers.
Layer 10 — Governed Output & Handoff
Produce the Resource Continuity Assessment Profile and preserve the downstream handoff to Resource Consumption & Replenishment Sustainability Governance.
77. Minimum Decision States
At minimum:
Assessment Not Initiated
Resource System Identified
Assessment Boundary Defined
Assessment Horizon Established
Operational Functions Identified
Resource Requirements Established
Availability Assessment Pending
Availability Assessment Complete
Capacity Assessment Pending
Capacity Assessment Complete
Demand Assessment Pending
Demand Assessment Complete
Dependency Assessment Pending
Dependency Assessment Complete
Access Assessment Pending
Access Assessment Complete
Continuity Gaps Identified
Evidence Sufficiency Pending
Evidence-Limited
Continuity Supported Within Defined Conditions
Continuity Conditionally Supported
Continuity Partially Supported
Continuity At Risk
Continuity Insufficient
Conflicted
Unknown
Monitoring Active
Material Change Detected
Reassessment Required
Reassessment Completed
78. Minimum Evidence Path
Where continuity cannot be established:
Resource System → Required Operational Functions → Assessment Horizon → Resource Requirements → Availability Evidence → Capacity Evidence → Demand Evidence → Access & Dependency Evidence → Delivery & Timing Evidence → Continuity Gap Identification → Evidence-Limited / Conflicted / Unknown State → Evidence Acquisition → Continuity Reassessment → Continuity Classification → Resource Continuity Assessment Profile → Monitoring → Sustainability Governance Handoff
Missing evidence must not be replaced by assumed continuity.
79. Minimum Reassessment Framework
Current Resource Continuity Assessment Profile → New Availability / Capacity / Demand / Access / Dependency / Delivery Evidence → Materiality Assessment → Assessment Boundary Review → Assessment Horizon Review → Operational Function Review → Resource Requirement Review → Continuity Gap Review → Evidence Sufficiency Review → Classification Update → Monitoring Conditions Update → Profile Update → Version Update
Reassessment must preserve the difference between:
Resource Conditions Changed
Evidence Updated
Continuity Gap Newly Identified
Continuity Gap Resolved
Continuity Classification Revised
80. Governance Requirements
A conforming RCAM implementation must satisfy the following requirements.
Resource System Identity & Boundaries
1. Identify the Resource System. 2. Establish a continuity assessment identity. 3. Define the assessment boundary. 4. Establish the assessment horizon. 5. Identify required operational functions. 6. Identify relevant Resource categories. 7. Preserve geographic context. 8. Preserve operational context. 9. Preserve the evidence basis. 10. Prevent partial boundary coverage from establishing complete system continuity.
Resource Requirements
11. Establish required Resource quantities. 12. Establish required usable capacity. 13. Establish required Resource quality. 14. Establish required Resource availability. 15. Establish required delivery conditions. 16. Establish required Resource timing. 17. Establish required Resource duration. 18. Preserve supporting Resource dependencies. 19. Prevent Resource quantity from substituting for complete operational requirements.
Availability & Capacity Continuity
20. Evaluate current Resource availability. 21. Evaluate expected Resource availability. 22. Evaluate availability duration. 23. Evaluate availability variability. 24. Evaluate installed capacity. 25. Evaluate usable capacity. 26. Evaluate capacity degradation. 27. Preserve capacity maintenance conditions. 28. Preserve capacity competition. 29. Prevent current availability from establishing future continuity. 30. Prevent installed capacity from establishing continuously usable capacity.
Demand & Adequacy Continuity
31. Evaluate current demand. 32. Evaluate projected demand. 33. Evaluate peak demand. 34. Evaluate demand variability. 35. Evaluate demand growth. 36. Evaluate temporal Resource adequacy. 37. Preserve capacity margins where applicable. 38. Identify periods of insufficient Resource adequacy. 39. Prevent average adequacy from establishing adequacy during critical periods.
Access, Dependency & Infrastructure Continuity
40. Evaluate Resource Access continuity. 41. Preserve access conditions. 42. Preserve access duration. 43. Evaluate supporting Resource dependencies. 44. Identify shared dependencies. 45. Identify indirect dependencies. 46. Evaluate supporting infrastructure continuity. 47. Evaluate Resource delivery continuity. 48. Evaluate Resource quality continuity. 49. Evaluate Resource timing continuity. 50. Prevent primary Resource availability from establishing supporting dependency continuity. 51. Prevent Resource availability at source from establishing delivery continuity.
Constraints & Disturbances
52. Evaluate supply variability. 53. Evaluate capacity degradation. 54. Evaluate Resource competition. 55. Preserve scarcity exposure. 56. Preserve disturbance exposure. 57. Evaluate Resource buffer contributions. 58. Evaluate alternative Resource arrangements. 59. Evaluate recovery contributions. 60. Preserve resilience validation references. 61. Identify continuity gaps. 62. Evaluate material constraint interactions. 63. Prevent individual constraint manageability from establishing combined constraint manageability.
Evidence Governance
64. Preserve evidence provenance. 65. Evaluate evidence sufficiency. 66. Preserve missing evidence. 67. Preserve uncertainty. 68. Preserve conflicting evidence. 69. Preserve scenario assumptions.
70. Support Evidence-Limited states. 71. Support Conflicted states. 72. Support Unknown states. 73. Distinguish projected from demonstrated continuity. 74. Prevent continuity plans from establishing operational continuity. 75. Prevent evidence volume from replacing evidence relevance.
Classification Governance
76. Establish evidence-based continuity classifications. 77. Preserve conditional continuity. 78. Preserve partial continuity. 79. Preserve continuity risk. 80. Preserve insufficient continuity findings. 81. Preserve the assessment horizon. 82. Preserve validity conditions. 83. Preserve known limitations. 84. Prevent bounded continuity conclusions from establishing universal continuity. 85. Prevent continuity classification from establishing Sustainability.
Monitoring & Reassessment
86. Establish relevant monitoring signals. 87. Preserve material Resource changes. 88. Preserve changed Resource availability. 89. Preserve changed capacity. 90. Preserve changed demand. 91. Preserve changed access conditions. 92. Preserve changed dependency conditions. 93. Preserve changed infrastructure conditions. 94. Preserve changed delivery conditions. 95. Establish reassessment triggers. 96. Preserve reassessment scope. 97. Preserve effective time. 98. Preserve material version history. 99. Prevent historical continuity conclusions from automatically remaining current.
Architecture: Boundaries
100. Maintain RCHS characterization boundaries. 101. Maintain RACS availability and capacity boundaries. 102. Maintain RDGS demand governance boundaries. 103. Maintain RDCS dependency and criticality boundaries. 104. Maintain RAGS Access governance boundaries. 105. Maintain RPAS Allocation governance boundaries. 106. Maintain RSCS scarcity and constraint boundaries. 107. Maintain RRCS recovery and circularity boundaries. 108. Maintain RSFS substitution and flexibility boundaries. 109. Maintain RIRS interdependency and resilience boundaries. 110. Preserve the downstream RCSS Sustainability assessment handoff. 111. Prevent RCAM from creating operational authority. 112. Prevent RCAM from independently determining Resource Sustainability. 113. Prevent RCAM from independently determining Harm or Liability. 114. Produce a Resource Continuity Assessment Profile.
81. Governance Logic
Canonical RCAM logic:
Resource System Identity → Continuity Assessment Boundary → Required Operational Functions → Assessment Horizon → Resource Continuity Requirements → Resource Availability Continuity → Resource Capacity Continuity → Resource Demand Continuity → Resource Adequacy Over Time → Resource Access Continuity → Resource Dependency Continuity → Supporting Infrastructure Continuity → Resource Quality
Continuity → Resource Delivery & Timing Continuity → Resource Supply Variability → Capacity Degradation → Resource Competition → Scarcity & Disturbance Exposure → Resource Buffer / Alternative / Recovery / Resilience Contributions → Continuity Gap Assessment → Evidence Sufficiency → Continuity Classification → Resource Continuity Assessment Profile → Monitoring → Reassessment → Sustainability Governance Handoff
82. Governance Outputs
RCAM may produce:
Resource Continuity Assessment Profile
Resource System Continuity Identity Record
Continuity Assessment Boundary
Assessment Horizon Record
Required Operational Function Register
Resource Continuity Requirement Register
Resource Availability Continuity Assessment
Resource Capacity Continuity Assessment
Resource Demand Continuity Assessment
Resource Adequacy Assessment
Resource Access Continuity Assessment
Resource Dependency Continuity Assessment
Supporting Infrastructure Continuity Assessment
Resource Quality Continuity Assessment
Resource Delivery Continuity Assessment
Resource Timing Assessment
Resource Supply Variability Assessment
Capacity Degradation Assessment
Resource Demand Growth Assessment
Resource Competition Assessment
Scarcity Exposure Record
Disturbance Exposure Record
Resource Buffer Contribution Assessment
Alternative Resource Arrangement Assessment
Resource Recovery Contribution Assessment
Resource Resilience Contribution Assessment
Resource Continuity Gap Register
Constraint Interaction Assessment
Continuity Scenario Record
Evidence Sufficiency State
Missing Evidence Record
Evidence Uncertainty
Evidence Conflict
Continuity Classification
Validity Condition Register
Monitoring Signal Register
Reassessment Trigger
Sustainability Governance Handoff
Version:
83. Practical Applications
AI Data Centers
Assessing whether electricity, cooling, water, computing infrastructure, and supporting Resource dependencies can remain available and adequate throughout defined operating and expansion horizons.
Energy Infrastructure
Assessing the continuity of energy supply, fuel availability, usable capacity, delivery infrastructure, and supporting Resource dependencies.
Water Systems
Assessing water availability, storage, pumping, treatment, distribution, demand growth, and seasonal Resource continuity.
Industrial Manufacturing
Assessing whether materials, electricity, water, production infrastructure, and supply arrangements can support required manufacturing functions over time.
Critical Infrastructure
Assessing the continuity of Resources required to maintain essential operational functions under changing availability, demand, access, dependency, and disturbance conditions.
84. Use Case 1 — AI Data Center Electricity & Cooling Continuity
An AI data center plans to increase computational capacity over a defined operating horizon.
The expansion increases electricity and cooling requirements.
RCAM establishes:
Resource System: AI data center.
Required Functions: Computational processing and thermal control.
Assessment Horizon: Defined operational and expansion period.
Resource Requirements: Electricity, cooling capacity, water where applicable, and supporting infrastructure.
Availability Continuity: Expected electricity and cooling Resource availability.
Capacity Continuity: Usable electrical and cooling capacity over time.
Demand Continuity: Current and projected computing demand.
Dependency Continuity: Electricity distribution, cooling infrastructure, water supply, and control systems.
Access Continuity: Applicable Resource access and supply conditions.
Delivery Continuity: Required electricity and cooling delivery.
Constraint Exposure: Demand growth, capacity degradation, supply variability, and shared dependencies.
Evidence Basis: Availability records, capacity assessments, demand projections, infrastructure evidence, and relevant resilience profiles.
Output: Resource Continuity Assessment Profile.
The assessment may establish that current electricity capacity is adequate while projected demand exceeds future usable capacity.
Current Computing Operations Supported ≠ Future Computing Expansion Continuity Established.
85. Use Case 2 — Industrial Water Supply Continuity
An industrial facility depends on water for production and plans to maintain operations through seasonal supply variation.
RCAM establishes:
Resource System: Industrial production facility.
Required Function: Water-supported production.
Assessment Horizon: Defined operating period.
Resource Requirements: Required water quantity, quality, delivery rate, and timing.
Availability Continuity: Expected water availability across seasonal conditions.
Capacity Continuity: Storage, treatment, pumping, and distribution capacity.
Demand Continuity: Production water requirements and expected variability.
Dependency Continuity: Electricity, pumping infrastructure, treatment systems, and delivery pathways.
Access Continuity: Applicable water access conditions.
Constraint Exposure: Seasonal scarcity, infrastructure degradation, and competing water demand.
Buffer Contribution: Usable water storage and its duration.
Alternative Resource Arrangements: Alternative water sources where available and operationally compatible.
Output: Resource Continuity Assessment Profile.
A facility may possess sufficient water storage for short interruptions while remaining exposed to persistent water scarcity.
Short-Term Water Supply Continuity ≠ Long-Term Water Sustainability.
86. Critical Distinctions
Resource Available Now ≠ Resource Continuously Available.
Resource Supply Maintained ≠ Required Operational Function Maintained.
Installed Resource Capacity ≠ Continuously Usable Resource Capacity.
Resource Continuity Demonstrated ≠ Resource Sustainability Demonstrated.
Resource Adequate Today ≠ Resource Adequate Throughout the Assessment Horizon.
Resource Source Available ≠ Supporting Resource Dependencies Available.
Resource Access Granted ≠ Resource Access Continuously Maintained.
Resource Continuity Planned ≠ Resource Continuity Demonstrated.
Continuity Established Within a Defined Boundary ≠ Continuity Established Across the Entire Resource System.
Continuity Demonstrated for One Period ≠ Continuity Demonstrated for Every Future Period.
Operational Function Identified ≠ Resource Requirements Completely Established.
Resource Quantity Sufficient ≠ All Resource Continuity Requirements Satisfied.
Current Resource Availability ≠ Future Resource Availability.
Capacity Installed ≠ Capacity Continuously Usable.
Current Demand Covered ≠ Future Demand Covered.
Average Resource Adequacy ≠ Resource Adequacy During Critical Periods.
Resource Access Currently Permitted ≠ Resource Access Guaranteed Throughout the Assessment Horizon.
Primary Resource Available ≠ Supporting Dependency Chain Continuously Available.
Resource Supply Exists ≠ Resource Delivery Infrastructure Continuously Operational.
Resource Quantity Available ≠ Resource Quality Operationally Sufficient.
Resource Available at Source ≠ Resource Delivered Where Required.
Resource Available Eventually ≠ Resource Available When Required.
Average Resource Supply ≠ Resource Supply During Critical Operating Conditions.
Capacity Available at Assessment Time ≠ Capacity Maintained Throughout the Assessment Horizon.
Supply Stable ≠ Resource Continuity Stable When Demand Increases.
Resource Physically Available ≠ Resource Available to Every Competing User.
Resource Scarcity Not Present Today ≠ Resource Scarcity Absent Throughout the Assessment Horizon.
Resource System Resilient to a Defined Disturbance ≠ Resource Continuity Guaranteed Throughout the Assessment Horizon.
Resource Buffer Exists ≠ Resource Continuity Established.
Alternative Resource Identified ≠ Alternative Resource Continuously Available and Usable.
Resource Recovery Capability Exists ≠ Resource Continuity Requirement Satisfied.
Resilience Validated for a Disturbance Scenario ≠ Long-Term Resource Continuity Validated.
Continuity Gap Identified ≠ Continuity Gap Resolved.
Individual Constraints Manageable ≠ Combined Constraints Manageable.
Continuity Projected Under a Scenario ≠ Continuity Operationally Demonstrated.
Resource Continuity Data Available ≠ Resource Continuity Demonstrated.
Future Resource Conditions Uncertain ≠ Resource Continuity Automatically Supported.
Continuity Supported Within Defined Conditions ≠ Continuity Guaranteed Under All Conditions.
Continuity Conditionally Supported ≠ Continuity Unconditionally Established.
87. Cross-Architecture Boundary
RCAM may consume governed evidence from:
RCHS — Resource Characterization Standard
RACS — Resource Availability & Capacity Standard
RDGS — Resource Demand Governance Standard
RDCS — Resource Dependency & Criticality Standard
RAGS — Resource Access Governance Standard
RPAS — Resource Prioritization & Allocation Standard
RCUS — Resource Consumption & Utilization Standard
RSCS — Resource Scarcity & Constraint Standard
RRCS — Resource Recovery & Circularity Standard
RSFS — Resource Substitution & Flexibility Standard
RIRS — Resource Interdependency & Resilience Standard
Its principal downstream relationship is to the remaining RCSS Core Modules governing Resource Sustainability.
RCAM evaluates Resource continuity using the outputs of these mechanisms.
It does not replace their independent governance functions.
88. 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.
RCAM may use Resource availability, capacity, demand, dependency, access, scarcity, recovery, substitution, and resilience evidence.
It governs the relevance of those inputs to Resource continuity across the assessment horizon.
It does not redefine the mechanisms that produced them.
89. Canonical Boundary
RCAM governs how the continued availability, accessibility, adequacy, and operational usability of Resources required to sustain defined operational functions are identified, evaluated, evidenced, classified, monitored, and reassessed across specified temporal, geographic, operational, capacity, demand, dependency, and disturbance conditions.
It does not independently create Resource supply, grant Resource Access, execute Resource Allocation, authorize operational interventions, determine Harm or Liability, or establish long-term Resource Sustainability.
Its principal governed output is the Resource Continuity Assessment Profile .
90. Canonical Closing Statement
Resource continuity cannot be established merely because Resources are currently available, infrastructure capacity exists, supply contracts remain active, or operations have historically continued without interruption. Continuity becomes a supportable conclusion only when the Resource quantities, capacities, qualities, access conditions, delivery pathways, supporting dependencies, and timing requirements necessary for defined operational functions remain adequately evidenced across the relevant assessment horizon.
RCAM establishes the first governance layer of RCSS — ensuring that present Resource availability is never mistaken for future adequacy, installed capacity is not confused with continuously usable capacity, and operational continuity remains a bounded, evidence-dependent conclusion rather than an unsupported promise of Resource Sustainability.