RSAM — Resource Substitution Assessment Module
Architecture:
RSGA™ — Resource Sustainability Governance Architecture
Parent Standard:
RSFS — Resource Substitution & Flexibility Standard
Category:
Governance & Enforcement
Subcategory:
Resource Governance
Type:
Core Module
Governed Space:
Resource Substitution Need & Alternative Assessment Governance
Module ID:
RSGA-RSFS-RSAM-01
Origin ID:
OOF-RSGA-RSFS-RSAM
Version:
1.0
Status:
Canonical Open
Effective Date:
8 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
RSAM — Resource Substitution Assessment Module is the Core Module within RSFS that governs how an original Resource requirement, its substitution need, relevant operational context, existing Resource dependency, candidate alternative Resources, and preliminary substitution conditions are identified, bounded, evidenced, classified, and prepared for subsequent compatibility and feasibility assessment.
RSAM establishes the governance basis for determining what Resource requirement is being considered for substitution, why substitution is being considered, which alternatives may warrant further assessment, and what evidence is required before those alternatives can be evaluated as potential substitutes.
The module does not determine final compatibility, operational feasibility, substitution readiness, authorization, or effectiveness.
Its foundational distinctions are:
Substitution Need ≠ Substitution Feasibility.
Alternative Resource Identified ≠ Alternative Resource Validated.
Candidate Alternative ≠ Approved Substitute.
Resource Requirement Defined ≠ Resource Replacement Justified.
2. Operational Role
RSAM governs the initial assessment stage of Resource Substitution & Flexibility Governance.
Its operational role is to establish a traceable relationship between an existing Resource requirement and the alternatives proposed to satisfy, supplement, reduce, or reorganize that requirement.
RSAM ensures that substitution does not begin with an unsupported assumption that another Resource is equivalent.
Instead, the assessment begins with the actual operational requirement.
The module establishes:
The identity of the original Resource requirement. The operational function supported by that requirement. The Resource currently used or expected to be used. The relevant Resource dependency. The reason substitution is being considered. The intended substitution objective. The boundaries of the proposed change. Candidate alternative Resources or configurations. Preliminary Resource characteristics. Preliminary availability and capacity references. Material known restrictions. Initial supporting Resource dependencies. Missing or conflicting evidence. The assessment state. The handoff to subsequent compatibility and feasibility governance.
RSAM does not convert candidate alternatives into validated substitutes.
3. Operational Question
What legitimate Resource requirement is being considered for substitution, why is substitution being considered, which alternative Resources or configurations warrant further assessment, and under what defined operational boundaries and evidence conditions can those alternatives enter the substitution governance process without prematurely establishing compatibility, feasibility, authorization, or expected benefit?
4. Position in Architecture Governance Flow
RSGA™ Governance Flow
Resource Characterization → Availability & Capacity → Demand → Dependency & Criticality → Access → Prioritization & Allocation → Consumption & Utilization → Scarcity & Constraint → Recovery & Circularity → Substitution & Flexibility → Interdependency & Resilience → Continuity & Sustainability
RSFS Governance Flow
1. Resource Substitution Assessment — RSAM 2. Resource Substitution Compatibility — RSCM 3. Resource Transition & Substitution — RTSM 4. Resource Dependency Flexibility — RDFM 5. Resource Substitution & Flexibility Monitoring — RSWM
RSAM occupies the first governance position within RSFS.
It establishes the assessment basis required before candidate alternatives can undergo compatibility evaluation.
Its output is not a substitution decision.
It is a governed assessment of the original requirement, substitution need, candidate alternatives, and preliminary evidence.
5. Governed Space
Resource Substitution Need & Alternative Assessment Governance
This governed space concerns the initial recognition, definition, contextualization, identification, classification, and evidence-based assessment of Resource substitution needs and candidate alternatives.
It includes the boundary between identifying a possible substitution and determining whether that substitution is actually valid.
The governed space is not limited to Resource scarcity.
Substitution assessment may occur during normal operations, strategic planning, technological change, infrastructure modernization, Resource Recovery reintegration, or anticipated operational constraints.
6. Governed Object
The primary Governed Object is:
A Resource Substitution Assessment Case connecting an identifiable original Resource requirement with a defined substitution need, operational context, candidate alternatives, preliminary conditions, and an evidence- based assessment state.
A single assessment case may contain multiple candidate alternatives.
Each alternative must remain individually identifiable.
Canonical relationship:
Original Resource Requirement → Operational Context → Substitution Need → Substitution Objective → Assessment Boundary → Candidate Alternative Identification → Preliminary Resource Characterization → Preliminary Dependency & Constraint Identification → Evidence Sufficiency → Candidate Assessment State → Resource Substitution Assessment Profile → Compatibility Assessment Handoff
7. Scope
RSAM governs:
Original Resource requirement identification. Existing Resource dependency references. Operational context. Substitution need. Substitution objective. Assessment boundary. Candidate alternative identification.
Candidate Resource characterization. Candidate Resource provenance. Preliminary capacity references. Preliminary availability references. Preliminary location and timing conditions. Known Resource restrictions. Preliminary supporting Resource dependencies. Initial substitution-related constraints. Candidate relevance. Candidate assessment states. Evidence sufficiency. Missing and conflicting evidence. Assessment reassessment. Compatibility assessment handoff.
RSAM does not govern final compatibility validation, technical certification, operational feasibility determination, substitution authorization, transition execution, operational flexibility activation, or actual substitution effectiveness.
8. Foundational Governance Principles
8.1 Requirement-First Principle
Substitution assessment must begin with the Resource requirement, not with the attractiveness of an alternative.
An alternative cannot be meaningfully assessed without understanding the function it is expected to support.
8.2 Need–Feasibility Separation
Substitution Need ≠ Substitution Feasibility.
A legitimate reason to seek substitution does not establish that substitution is possible.
8.3 Candidate–Substitute Separation
Candidate Alternative ≠ Validated Substitute.
Identification establishes assessment eligibility, not substitution validity.
8.4 Function–Resource Separation
Resource Requirement ≠ Existing Resource Identity.
The operational requirement may remain legitimate even when the Resource currently satisfying it becomes unavailable or undesirable.
8.5 Evidence Boundary Principle
Preliminary Evidence ≠ Conclusive Substitution Evidence.
8.6 Scarcity Independence Principle
Resource Scarcity Is Not a Prerequisite for Substitution Assessment.
8.7 Authority Separation Principle
Assessment Recommendation ≠ Substitution Authorization.
9. Original Resource Requirement
Every RSAM assessment must identify the original Resource requirement.
The requirement should be expressed independently of any proposed alternative wherever operationally possible.
Minimum characteristics include:
Requirement ID
Required Function
Resource Type
Required Quantity
Required Quality
Required Capacity
Required Location
Required Time
Required Duration
Applicable Restrictions
Operational Dependency
Evidence Basis
The assessment must preserve whether a requirement is established, provisional, disputed, or insufficiently evidenced.
10. Requirement Identity
The original requirement must remain traceable throughout the substitution assessment.
Changes to the requirement may materially change which alternatives are relevant.
Changed Requirement ≠ Same Substitution Assessment by default.
Where the requirement changes, the assessment must preserve the previous requirement version and the reason for change.
11. Operational Function
RSAM must identify the function the original Resource is expected to support.
Examples include:
Cooling
Electricity Supply
Material Strength
Water Supply
Computational Processing
Transport Capacity
Storage Capacity
Other Resource-Specific Functions
The function must not be reduced to the name of the currently used Resource.
12. Functional Requirement Principle
Replacing a Resource ≠ Automatically Preserving Its Function.
A proposed alternative must later be evaluated against the actual functional requirement.
RSAM establishes that requirement but does not validate the alternative's performance.
13. Existing Resource Context
RSAM should identify the Resource currently satisfying, or originally intended to satisfy, the requirement.
Relevant context may include:
Current Resource Identity
Current Resource Type
Current Quantity
Current Quality
Current Capacity
Current Location
Current Availability
Current Operational Role
Current Restrictions
Current Dependency
14. Existing Resource Dependency
The original Resource may support multiple operational functions.
RSAM should preserve the dependencies relevant to the proposed substitution.
The assessment must distinguish the specific requirement being considered from unrelated uses of the same Resource.
One Resource Replaced in One Function ≠ Entire Resource Dependency Eliminated.
15. Substitution Need Recognition
RSAM must establish why substitution is being considered.
Possible reasons include:
Resource Scarcity
Resource Unavailability
Capacity Limitation
Reliability Concern
Cost or Efficiency Objective
Resource Recovery Opportunity
Infrastructure Transition
Operational Resilience Objective
Environmental Constraint
Technological Change
Planned Resource Diversification
Other Legitimate Operational Needs
The reason must remain distinguishable from the proposed solution.
16. Substitution Need Principle
Problem Identified ≠ Solution Validated.
17. Substitution Objective
The substitution objective defines the intended outcome of the proposed change.
Examples include:
Maintain Existing Function
Reduce Primary Resource Dependency
Increase Available Capacity
Improve Operational Flexibility
Support Recovery-Based Resource Use
Reduce Exposure to Resource Constraints
Enable Infrastructure Transition
Support Alternative Resource Configuration
Objectives must be expressed in terms that can later be evaluated.
18. Objective–Outcome Separation
Intended Substitution Benefit ≠ Demonstrated Substitution Benefit.
RSAM records the objective.
Subsequent modules establish compatibility, implementation, and observed effectiveness.
19. Assessment Boundary
Every assessment must define its operational boundary.
Relevant boundaries include:
Resource Requirement
Operational Function
Resource System
Location
Time Period
Capacity Range
Quality Requirements
Included Dependencies
Excluded Dependencies
Applicable Restrictions
Without a defined boundary, candidate comparison may become misleading.
20. Boundary Principle
Substitution Valid Within One Boundary ≠ Substitution Valid Across All Boundaries.
21. Candidate Alternative Identification
RSAM identifies Resources, capacities, configurations, or operational pathways that may warrant further assessment.
Candidate alternatives may include:
Alternative Primary Resources
Recovered Resources
Secondary Resources
Alternative Energy Sources
Alternative Water Sources
Alternative Materials
Alternative Computing Capacity
Alternative Infrastructure Capacity
Alternative Operational Configurations
Other Resource-Specific Alternatives
Identification must not imply equivalence.
22. Candidate Identity
Each candidate alternative should have an identifiable reference.
Minimum elements include:
Candidate ID
Candidate Type
Resource or Configuration Reference
Source
Proposed Function
Preliminary Characteristics
Known Restrictions
Evidence Source
Assessment State
23. Candidate Relevance
Candidate relevance concerns whether an alternative has a reasonable relationship to the defined Resource requirement and substitution objective.
Relevance may be established through:
Potential Functional Relationship
Resource Type
Known Capability
Preliminary Capacity
Location
Timing
Existing Technical Evidence
Other Relevant Conditions
Relevance does not establish compatibility.
24. Candidate Relevance Principle
Candidate Relevant ≠ Candidate Compatible.
25. Candidate Source and Provenance
RSAM should preserve the origin of each candidate.
Possible sources include:
Existing Resource Inventory
Recovered Resource Records
External Resource Supply
Alternative Infrastructure
Operational Planning
Technical Documentation
Resource Discovery
Other Traceable Sources
Candidate provenance should remain available for subsequent assessment.
26. Preliminary Resource Characterization
RSAM should preserve available Resource characteristics without duplicating the full Resource Characterization mechanism governed by RCHS.
Relevant characteristics may include:
Resource Type
Physical or Functional Properties
Quantity
Quality
Capacity
Location
Condition
Relevant Restrictions
Known Limitations
27. Preliminary Capacity Reference
A candidate may have apparent capacity that has not been validated for the intended requirement.
RSAM should preserve preliminary capacity evidence and its uncertainty.
Nominal Candidate Capacity ≠ Usable Substitution Capacity.
RACS governs Resource Availability & Capacity.
28. Preliminary Availability Reference
A candidate may exist without being available at the required time or location.
RSAM should preserve available evidence without independently determining final availability.
Candidate Exists ≠ Candidate Available.
29. Preliminary Access Reference
A candidate may be identified without establishing legitimate Access.
RSAM should preserve known Access conditions and restrictions.
Candidate Identified ≠ Resource Access Granted.
RAGS governs Resource Access.
30. Preliminary Allocation Reference
A candidate may have sufficient capacity but already be committed elsewhere.
RSAM should preserve known Allocation references.
Candidate Capacity Exists ≠ Capacity Allocable to the Proposed Requirement.
RPAS governs Resource Prioritization & Allocation.
31. Preliminary Temporal Conditions
RSAM should identify whether the candidate is potentially relevant within the required time.
Relevant conditions include:
Availability Window
Lead Time
Duration
Operational Scheduling
Transition Period
Known Timing Restrictions
32. Preliminary Spatial Conditions
RSAM should identify relevant location constraints.
Examples include:
Resource Location
Receiving System Location
Transport Requirement
Infrastructure Connection
Geographic Restriction
Other Spatial Dependencies
33. Known Technical Restrictions
RSAM should preserve technical restrictions already established by competent evidence.
Examples include:
Material Limitations
Temperature Restrictions
Capacity Restrictions
Interface Requirements
Quality Limitations
Known Incompatibilities
These restrictions inform subsequent compatibility assessment.
RSAM does not independently certify technical suitability.
34. Known Operational Restrictions
RSAM should preserve operational restrictions affecting candidate assessment.
Examples include:
Limited Operating Hours
Infrastructure Constraints
Maintenance Requirements
Personnel Requirements
Operational Dependencies
Restricted Operating Modes
35. Preliminary Supporting Resource Dependencies
A candidate may require supporting Resources.
Examples include:
Electricity
Water
Heat
Chemicals
Materials
Transport
Infrastructure Capacity
Computational Capacity
RSAM records known dependencies for later detailed assessment.
36. Dependency Recognition Principle
Alternative Resource Identified ≠ Supporting Resource Dependencies Understood.
37. Preliminary Constraint Recognition
RSAM should identify known constraints associated with candidate alternatives.
Examples include:
Capacity Constraints
Availability Constraints
Location Constraints
Timing Constraints
Quality Constraints
Infrastructure Constraints
Known Supporting Resource Shortages
This is preliminary constraint recognition, not a final assessment of constraint transfer or resolution.
38. Constraint Recognition Principle
Constraint Identified ≠ Constraint Impact Quantified.
39. Candidate Comparison Basis
Where multiple alternatives are identified, RSAM should establish a consistent basis for subsequent comparison.
The comparison basis may include:
Required Function
Required Quantity
Required Quality
Required Capacity
Location
Timing
Known Restrictions
Relevant Dependencies
RSAM does not assign final substitution validity.
40. Comparison Principle
Candidate Comparison ≠ Substitution Selection.
41. Candidate Assessment Classification
RSAM may classify candidates as:
Identified
Preliminarily Relevant
Conditionally Relevant
Insufficiently Characterized
Outside Assessment Boundary
Known Ineligible for Further Assessment
Evidence-Limited
Conflicted
Unknown
Reassessment Required
These states concern candidate assessment, not technical equivalence.
42. Candidate Exclusion
A candidate may be excluded from further assessment where reliable evidence establishes that it falls outside the defined requirement or assessment boundary.
Exclusion should preserve:
Candidate Identity
Exclusion Reason
Evidence Basis
Applicable Boundary
Decision Time
Reassessment Conditions
Exclusion must not be used to conceal uncertainty or avoid legitimate alternatives without a defined basis.
43. Candidate Exclusion Principle
Candidate Excluded From One Assessment ≠ Candidate Universally Invalid.
44. Candidate Assessment Evidence
RSAM should preserve evidence concerning:
Original Requirement
Operational Function
Existing Resource Context
Substitution Need
Substitution Objective
Assessment Boundary
Candidate Identity
Candidate Characteristics
Preliminary Capacity
Preliminary Availability
Known Restrictions
Known Dependencies
Candidate Relevance
45. Evidence Provenance
Evidence should preserve:
Source
Method
Time
Location
Resource Reference
Assessment Case Reference
Responsible Evidence Origin
Version:
Evidence Content ≠ Methodology Instruction.
46. Evidence Sufficiency
RSAM should determine whether available evidence is sufficient to support candidate assessment and handoff.
Evidence sufficiency must be evaluated relative to the assessment purpose.
A candidate may be sufficiently characterized for preliminary consideration but not for compatibility validation.
Sufficient for Candidate Identification ≠ Sufficient for Substitution Validation.
47. Missing Evidence
Missing evidence may concern:
Original Requirement
Candidate Identity
Resource Quantity
Resource Quality
Capacity
Location
Timing
Known Restrictions
Dependency
Provenance
Missing evidence must remain visible.
48. Evidence Conflict
Conflicting evidence may concern:
Requirement Identity
Resource Characteristics
Candidate Capacity
Candidate Availability
Known Restrictions
Operational Context
Candidate Provenance
RSAM must preserve unresolved material conflicts.
49. Evidence Conflict Principle
Conflicting Candidate Evidence ≠ Permission to Declare Candidate Valid.
50. Assessment Uncertainty
RSAM should preserve uncertainty concerning:
Requirement Definition
Substitution Need
Candidate Relevance
Resource Characteristics
Capacity
Availability
Restrictions
Dependencies
Evidence Sufficiency
Uncertainty should not be converted into unsupported confidence.
51. Assessment Decision
RSAM determines whether a candidate has an adequately defined assessment basis for subsequent compatibility evaluation.
The decision may be:
Proceed to Compatibility Assessment
Proceed Conditionally
Additional Evidence Required
Candidate Outside Scope
Candidate Excluded With Evidence
Assessment Conflicted
Assessment Unknown
Reassessment Required
A decision to proceed does not establish compatibility.
52. Assessment Handoff
The RSAM output should provide RSCM with:
Original Resource Requirement
Operational Function
Substitution Objective
Assessment Boundary
Candidate Alternative Identity
Candidate Resource Characteristics
Known Restrictions
Known Dependencies
Preliminary Capacity References
Preliminary Availability References
Evidence Sufficiency
Uncertainty
Conflicts
Assessment State
53. Handoff Principle
Candidate Accepted for Compatibility Assessment ≠ Candidate Compatible.
54. Resource Substitution Assessment Profile
The principal governed output is the:
Resource Substitution Assessment Profile
It establishes the traceable relationship between an original Resource requirement, the need for substitution, the assessment boundary, identified alternatives, preliminary Resource conditions, evidence, and the decision to proceed with further evaluation.
55. Minimum Profile Fields
At minimum:
Assessment Profile ID
Original Resource Requirement ID
Original Resource Type
Required Function
Required Quantity
Required Quality
Required Capacity
Required Location
Required Time
Required Duration
Existing Resource Reference
Existing Resource Dependency
Substitution Need
Substitution Objective
Assessment Boundary
Candidate Alternative ID
Candidate Resource Type
Candidate Source
Candidate Provenance
Candidate Preliminary Characteristics
Candidate Preliminary Quantity
Candidate Preliminary Quality
Candidate Preliminary Capacity
Candidate Location
Candidate Timing Conditions
Preliminary Availability Reference
Preliminary Access Reference
Preliminary Allocation Reference
Known Technical Restrictions
Known Operational Restrictions
Known Supporting Resource Dependencies
Known Constraints
Candidate Relevance State
Candidate Assessment State
Evidence Sufficiency
Missing Evidence
Evidence Uncertainty
Evidence Conflict
Compatibility: Assessment Handoff State
Reassessment Trigger
Effective Time
Version:
56. Minimum Implementation Framework
A minimum operational RSAM implementation should contain eight governed layers.
Layer 1 — Original Requirement Identity
Establish the Resource requirement, supported function, required capacity, quality, location, time, and applicable restrictions.
Layer 2 — Substitution Need
Identify why substitution is being considered and preserve the evidence supporting that need.
Layer 3 — Substitution Objective & Boundary
Define the intended substitution outcome and the operational boundary of the assessment.
Layer 4 — Candidate Alternative Identification
Identify candidate Resources, capacities, configurations, or pathways without prematurely validating them.
Layer 5 — Preliminary Resource Assessment
Preserve available candidate characteristics, capacity, availability, location, timing, restrictions, and dependencies.
Layer 6 — Evidence Evaluation
Evaluate evidence sufficiency, uncertainty, missing information, and material conflicts.
Layer 7 — Candidate Assessment Decision
Determine whether each candidate can proceed to compatibility assessment, requires additional evidence, or falls outside the defined assessment boundary.
Layer 8 — Governed Output
Produce the Resource Substitution Assessment Profile and the applicable compatibility assessment handoff.
57. Minimum Decision States
At minimum:
Assessment Not Initiated
Requirement Identification Pending
Requirement Defined
Requirement Evidence-Limited
Substitution Need Identified
Substitution Objective Defined
Assessment Boundary Defined
Candidate Identified
Candidate Preliminarily Relevant
Candidate Conditionally Relevant
Candidate Insufficiently Characterized
Candidate Outside Scope
Candidate Excluded With Evidence
Additional Evidence Required
Ready for Compatibility Assessment
Conditionally Ready for Compatibility Assessment
Assessment Evidence-Limited
Assessment Conflicted
Assessment Unknown
Reassessment Required
58. Minimum Evidence Path
Where a candidate cannot be sufficiently assessed:
Original Resource Requirement → Substitution Need → Candidate Identification → Preliminary Resource Assessment → Evidence-Limited / Conflicted / Unknown State → Missing Evidence Identification → Evidence Acquisition → Requirement & Candidate Review → Candidate Assessment Decision → Resource Substitution Assessment Profile → Compatibility Assessment Handoff Where Supported
Missing evidence must not be replaced by assumed compatibility.
59. Minimum Reassessment Framework
Current Resource Substitution Assessment Profile → New Requirement / Resource / Capacity / Availability / Restriction / Dependency Evidence → Materiality Assessment → Assessment Boundary Review → Candidate Relevance Review → Evidence Reassessment → Assessment Decision Update → Profile Update → Version Update
Reassessment may be triggered by:
Changed original Resource requirement. Changed substitution objective. New candidate alternative. Candidate Resource degradation. Changed Resource capacity. Changed Resource availability. Changed location or timing. Newly identified technical restriction. Newly identified operational dependency. New conflicting evidence. Changed assessment boundary. New Recovery-based alternative. Material change in Resource constraints.
60. Governance Requirements
A conforming RSAM implementation must satisfy the following requirements.
Requirement Identification
1. Identify the original Resource requirement. 2. Preserve the operational function. 3. Preserve required Resource Type.
4. Preserve required quantity. 5. Preserve required quality. 6. Preserve required capacity. 7. Preserve required location. 8. Preserve required time and duration. 9. Preserve applicable restrictions. 10. Preserve the evidence basis.
Substitution Need and Objective
11. Identify the substitution need. 12. Preserve the reason for substitution. 13. Define the substitution objective. 14. Distinguish need from feasibility. 15. Distinguish objective from achieved benefit. 16. Preserve relevant operational context. 17. Define the assessment boundary. 18. Preserve changes to the requirement.
Candidate Identification
19. Identify candidate alternatives. 20. Preserve candidate identity. 21. Preserve candidate source. 22. Preserve candidate provenance. 23. Preserve candidate Resource Type. 24. Preserve preliminary characteristics. 25. Preserve preliminary capacity references. 26. Preserve preliminary availability references. 27. Preserve preliminary location and timing. 28. Preserve known restrictions. 29. Preserve known supporting Resource dependencies. 30. Preserve known constraints.
Candidate Assessment
31. Evaluate preliminary candidate relevance. 32. Preserve conditional relevance. 33. Preserve insufficient characterization. 34. Support evidence-based exclusion. 35. Preserve exclusion reasons. 36. Prevent candidate identification from establishing compatibility. 37. Prevent preliminary capacity from establishing usable capacity. 38. Prevent availability assumptions from establishing Access. 39. Prevent candidate comparison from establishing selection. 40. Preserve the basis for subsequent compatibility assessment.
Evidence Governance
41. Preserve evidence provenance. 42. Evaluate evidence sufficiency. 43. Preserve missing evidence. 44. Support Evidence-Limited states. 45. Support Conflicted states. 46. Support Unknown states. 47. Preserve material uncertainty. 48. Prevent unsupported candidate validation. 49. Preserve assessment decisions. 50. Preserve evidence supporting candidate exclusion.
Lifecycle and Boundaries
51. Support reassessment. 52. Preserve reassessment triggers.
53. Preserve material version history. 54. Preserve effective time. 55. Preserve original requirement continuity. 56. Preserve candidate identity continuity. 57. Maintain RCHS characterization boundaries. 58. Maintain RACS availability boundaries. 59. Maintain RAGS Access boundaries. 60. Maintain RPAS Allocation boundaries. 61. Maintain RDCS dependency boundaries. 62. Maintain RSCS scarcity boundaries. 63. Maintain RRCS Recovery boundaries. 64. Maintain RSCM compatibility boundaries. 65. Prevent assessment recommendations from creating authorization. 66. Produce a Resource Substitution Assessment Profile.
61. Governance Logic
Canonical RSAM logic:
Original Resource Requirement → Operational Function → Existing Resource Context → Substitution Need → Substitution Objective → Assessment Boundary → Candidate Alternative Identification → Candidate Resource Characterization → Preliminary Capacity / Availability / Location / Timing → Known Restrictions & Dependencies → Candidate Relevance → Evidence Sufficiency / Uncertainty / Conflict → Candidate Assessment Decision → Resource Substitution Assessment Profile → Compatibility Assessment Handoff → Reassessment Where Required
62. Governance Outputs
RSAM may produce:
Resource Substitution Assessment Profile
Original Resource Requirement Record
Operational Function Record
Existing Resource Context Record
Substitution Need Record
Substitution Objective Record
Assessment Boundary Record
Candidate Alternative Register
Candidate Resource Identity Record
Candidate Provenance Record
Preliminary Resource Characterization
Preliminary Capacity Reference
Preliminary Availability Reference
Preliminary Access Reference
Preliminary Allocation Reference
Known Restriction Record
Known Dependency Record
Candidate Relevance State
Candidate Exclusion Record
Evidence Sufficiency State
Missing Evidence Record
Evidence Uncertainty
Evidence Conflict
Compatibility: Assessment Handoff Record
Reassessment Trigger
Version:
63. Practical Applications
RSAM may support:
Energy Infrastructure
Identification of candidate alternative energy sources or capacity configurations before detailed technical and operational compatibility assessment.
Water Systems
Recognition of alternative water sources, recovered water candidates, and operational water-demand configurations for subsequent suitability evaluation.
AI Data Centers
Identification of alternative cooling resources, electricity sources, computational capacity, or infrastructure configurations.
Industrial Manufacturing
Identification of alternative materials, recovered Resource candidates, equipment configurations, or production pathways.
Critical Infrastructure
Identification of alternative Resource arrangements intended to support continuity under changing Resource availability or operational conditions.
64. Use Case 1 — AI Data Center Cooling Substitution Assessment
An AI data center seeks to reduce dependency on freshwater-intensive cooling.
The existing Resource requirement is not simply “freshwater.”
The actual operational requirement is to maintain adequate cooling capacity under defined equipment, temperature, reliability, and operating conditions.
RSAM establishes:
Original Requirement: Maintain required thermal conditions for computing infrastructure.
Existing Resource Context: Freshwater-dependent cooling configuration.
Substitution Need: Reduce freshwater dependency.
Substitution Objective: Identify alternative cooling Resource arrangements.
Candidate Alternatives:
Recovered industrial water. Alternative cooling configuration. Other technically relevant cooling Resource arrangements.
Assessment Boundary: Defined data center infrastructure, location, cooling load, time period, and operational conditions.
Preliminary Dependencies: Electricity, water treatment, infrastructure capacity, and supporting equipment.
RSAM identifies and characterizes the alternatives.
It does not determine whether recovered water satisfies the required cooling quality or whether a different cooling configuration can maintain the required thermal performance.
Those determinations belong to subsequent compatibility and feasibility governance.
Cooling Alternative Identified ≠ Cooling Requirement Satisfied.
65. Use Case 2 — Industrial Material Substitution Assessment
A manufacturer seeks an alternative to a primary material whose supply has become constrained.
RSAM establishes:
Original Requirement: Material with defined mechanical, chemical, dimensional, and operational properties.
Existing Resource Context: Primary material used in the production process.
Substitution Need: Reduce dependency on constrained primary material supply.
Substitution Objective: Identify alternative materials capable of supporting the same production requirement.
Candidate Alternatives:
Validated recovered material. Alternative primary material. Modified material configuration.
Assessment Boundary: Defined manufacturing process, product requirements, production volume, location, and time.
Preliminary Dependencies: Processing energy, material preparation, production equipment, and supply availability.
RSAM identifies the candidates and preserves the available evidence.
It does not declare the recovered material equivalent merely because it belongs to the same material family.
Material Alternative Identified ≠ Material Substitution Validated.
66. Critical Distinctions
Substitution Need ≠ Substitution Feasibility.
Alternative Resource Identified ≠ Alternative Resource Validated.
Candidate Alternative ≠ Approved Substitute.
Resource Requirement Defined ≠ Resource Replacement Justified.
Resource Requirement ≠ Existing Resource Identity.
Replacing a Resource ≠ Automatically Preserving Its Function.
Problem Identified ≠ Solution Validated.
Intended Substitution Benefit ≠ Demonstrated Substitution Benefit.
Substitution Valid Within One Boundary ≠ Substitution Valid Across All Boundaries.
Candidate Relevant ≠ Candidate Compatible.
Nominal Candidate Capacity ≠ Usable Substitution Capacity.
Candidate Exists ≠ Candidate Available.
Candidate Identified ≠ Resource Access Granted.
Candidate Capacity Exists ≠ Capacity Allocable to the Proposed Requirement.
Alternative Resource Identified ≠ Supporting Resource Dependencies Understood.
Constraint Identified ≠ Constraint Impact Quantified.
Candidate Comparison ≠ Substitution Selection.
Candidate Excluded From One Assessment ≠ Candidate Universally Invalid.
Sufficient for Candidate Identification ≠ Sufficient for Substitution Validation.
Candidate Accepted for Compatibility Assessment ≠ Candidate Compatible.
Assessment Recommendation ≠ Substitution Authorization.
67. Cross-Architecture Boundary
RSAM may consume 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
RSCS — Resource Scarcity & Constraint Standard
RRCS — Resource Recovery & Circularity Standard
Its principal downstream handoff is to:
RSCM — Resource Substitution Compatibility Module
Relevant external architectural relationships include:
ORA™ — Operational Reality Architecture
VEGA™ — Value Execution Governance Architecture
PGA™ — Prediction Governance Architecture
HAGA™ — Harm Governance Architecture
LIGA™ — Liability Governance Architecture
RSAM governs the initial Resource substitution assessment.
It does not absorb independent Resource characterization, Availability, Access, Allocation, technical compatibility, operational execution, Value, Harm, Liability, or Sustainability governance.
68. 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.
RSAM may use Resource characterization, availability, dependency, and Recovery evidence.
It governs only their relevance to the initial substitution assessment.
It does not redefine the mechanisms that produced those inputs.
69. Canonical Boundary
RSAM governs how an original Resource requirement, its substitution need, relevant operational context, existing Resource dependency, candidate alternative Resources, and preliminary substitution conditions are identified, bounded, evidenced, classified, and prepared for subsequent compatibility and feasibility assessment.
It does not determine final compatibility, operational feasibility, substitution readiness, authorization, transition execution, flexibility activation, or actual substitution effectiveness.
Its principal governed output is the Resource Substitution Assessment Profile .
70. Canonical Closing Statement
Resource substitution cannot begin with the assumption that an alternative is a replacement. It must begin with a clearly established Resource requirement, a legitimate reason for considering change, and traceable evidence identifying which alternatives deserve further evaluation.
RSAM establishes the governance foundation for Resource substitution — ensuring that alternatives enter the assessment process as candidates supported by defined requirements and evidence, not as presumed solutions whose compatibility, feasibility, or authority has yet to be established.