About Resource Availability & Capacity Standard
(RACS)
Architecture: RSGA™ — Resource Sustainability Governance Architecture
Category: Governance & Enforcement
Subcategory: Resource Governance
Standard Resource Availability & Capacity Standard (RACS)
Standard Type Parent Standard
Governed Space: Resource Availability & Capacity Governance
Effective Date: 4 October 2026
Authority: OOF® — OriginOpen® Foundation
1. What Is RACS?
The Resource Availability & Capacity Standard (RACS) is the second Parent Standard within RSGA™ — Resource Sustainability Governance Architecture.
RACS governs the determination of how much of a characterized Resource or Resource capacity is actually available, practically accessible, usable, reserved, and potentially capable of entering downstream allocation governance.
Its purpose is to prevent nominal Resource quantities, installed infrastructure, theoretical capacity, Source capacity, inventory records, or stated capacity from being mistaken for Resource capacity that can actually support real dependencies.
RACS therefore asks a fundamental Resource governance question:
What Resource quantity or capacity is actually available, accessible, usable, reserved, and potentially allocable under relevant temporal and spatial conditions?
2. Why Availability & Capacity Governance Matters
Resource systems frequently describe capacity through numbers that do not represent actual Resource reality.
A data center may have installed compute capacity that cannot operate because sufficient electricity or cooling is unavailable.
A water system may contain substantial Resource stock that cannot be delivered to the location where it is required.
A power system may possess substantial generation capacity while transmission constraints prevent that capacity from reaching a specific region.
A warehouse may contain material inventory that is reserved, degraded, inaccessible, or technically unsuitable for the required use.
A Resource may therefore exist without being available.
It may be available without being accessible.
It may be accessible without being usable.
It may be usable while reserved.
And it may be potentially allocable without having been allocated.
RACS exists to preserve these distinctions.
3. The Core Governance Problem
Without Availability & Capacity governance, systems can make decisions from misleading Resource representations such as:
Installed Capacity = Available Capacity
Inventory = Usable Resource
Source Capacity = Delivered Capacity
Stored Resource = Immediately Available Resource
Available Resource = Allocable Resource
These assumptions can propagate through planning, allocation, resilience, investment, infrastructure, and sustainability decisions.
RACS introduces the governance layer between:
Resource existence
and
Resource capacity that can actually participate in downstream governance.
4. What RACS Governs
RACS governs the determination and representation of:
Resource Availability
Resource Capacity
Practical Resource Accessibility
Usable Capacity
Reserved Capacity
Unreserved Capacity
Potentially Allocable Capacity
Temporal Availability
Spatial Availability
Source Availability
Delivered Availability
Flow and Throughput Capacity
Availability Constraints
Availability Evidence
Availability Uncertainty
Availability Reassessment
The exact representation depends upon the governed Resource.
5. What RACS Does Not Govern
RACS does not determine:
who has the right to access a Resource;
which dependency should receive priority;
how Resource capacity should be allocated;
whether Resource consumption is justified;
whether low availability constitutes a governed Scarcity State;
whether recovery should occur;
whether substitution should occur;
whether the Resource System is resilient;
whether current Resource use is sustainable.
These determinations belong to later RSGA™ Parent Standards or other competent OOF® architectures.
RACS establishes the Resource capacity state upon which those determinations may legitimately operate.
6. Scope
RACS applies to the determination of actual Resource availability and capacity across materially constrained Resource systems.
This may include:
Physical Resource stocks
Resource flows
Energy and generation capacity
Water capacity
Storage capacity
Transmission and distribution capacity
Processing capacity
Network capacity
Compute capacity
Cooling capacity
Recovery-derived capacity
Regenerative Resource capacity
Infrastructure-dependent Resource capacity
RACS covers the transition from nominal or existing Resource capacity toward actual available, accessible, usable, reserved, and potentially allocable Resource capacity.
Its Scope ends before access authorization, prioritization, allocation, consumption governance, scarcity response, resilience determination, and sustainability determination.
7. Position in RSGA™ Governance Flow
RACS occupies the second position in the canonical 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
RCHS first establishes:
What Resource are we governing?
RACS then establishes:
How much of that Resource is actually available and capable of participating in governance?
Only after that should RSGA™ determine Demand, Dependency, Access, Priority, Allocation, and subsequent Resource conditions.
8. From Resource Characterization to Resource Availability
RACS does not begin with an undefined Resource.
It receives the Governed Resource Characterization produced through RCHS.
Canonical transition:
Governed Resource Characterization → Availability Conditions → Practical Accessibility → Usability Conditions → Available / Usable Capacity → Reservation State → Potentially Allocable Capacity → Resource Availability & Capacity Profile
This prevents availability calculations from being detached from the actual Resource boundary, state, Source, type, constraints, and Context.
9. Resource Existence Is Not Resource Availability
One of the foundational principles of RACS is:
Resource Existence ≠ Resource Availability.
A Resource can physically exist while being unavailable because of:
location;
infrastructure;
technical condition;
time;
Resource State;
supporting Resource constraints;
Source interruption;
delivery limitations.
Existence is therefore necessary information.
It is not sufficient availability evidence.
10. Capacity Is Not a Single Number
Capacity can represent different Resource realities.
Depending upon the Resource, systems may report:
Theoretical Capacity
Rated Capacity
Installed Capacity
Gross Capacity
Available Capacity
Accessible Capacity
Usable Capacity
Reserved Capacity
Potentially Allocable Capacity
These values may differ materially.
RACS prevents them from being treated as interchangeable.
11. Installed Capacity vs Actual Capacity
Installed Capacity describes what infrastructure or Resource capacity has been installed.
It may include capacity that is:
offline;
under maintenance;
degraded;
unsupported by required Resources;
disconnected;
reserved;
otherwise unusable.
Therefore:
Installed Capacity ≠ Available Capacity ≠ Usable Capacity ≠ Potentially Allocable Capacity.
This distinction is particularly important in infrastructure-intensive Resource systems.
12. Practical Accessibility
A Resource may exist and be available at its Source while remaining inaccessible to the system that requires it.
Practical accessibility may depend upon:
transmission;
distribution;
transport;
pipeline capacity;
network connectivity;
physical location;
processing infrastructure.
RACS governs this practical Resource accessibility.
It does not govern permission.
Resource Accessibility ≠ Resource Access Authorization.
13. Usable Capacity
Resource capacity becomes usable only when it can perform the relevant Resource function under applicable conditions.
Usability may depend upon:
quality;
condition;
technical compatibility;
supporting Resources;
infrastructure;
location;
time;
operational configuration.
A Resource quantity that cannot perform the required function must not automatically be counted as usable capacity.
14. Reserved Capacity
Resource capacity may be available and usable while being reserved for another purpose.
Examples may include:
emergency reserves;
strategic reserves;
continuity capacity;
protected infrastructure capacity;
contractually or institutionally reserved capacity.
RACS records the capacity consequence of reservation.
It does not determine whether the reservation is legitimate.
Reserved Capacity State ≠ Reservation Authority.
15. Potentially Allocable Capacity
Potentially Allocable Capacity represents Resource capacity that has passed the relevant Availability, Accessibility, Usability, and Reservation conditions sufficiently to proceed toward downstream Resource allocation governance.
It does not mean that the Resource has been allocated.
Potentially Allocable Capacity ≠ Allocation Decision.
This distinction prevents RACS from crossing into Resource Prioritization & Allocation governance.
16. Temporal Availability
Resource availability changes through time.
RACS may therefore distinguish:
Immediate Availability
Current Availability
Scheduled Availability
Peak Availability
Seasonal Availability
Conditional Availability
Future Availability
A Resource may be abundant annually yet unavailable during a critical seasonal or peak period.
Annual Resource Quantity ≠ Availability at the required time.
17. Spatial Availability
Resource availability is also spatial.
A Resource may exist:
at the Source;
within a region;
inside storage;
within another network zone;
while remaining unavailable at the point where it is required.
RACS therefore preserves the distinction:
Availability at Source ≠ Availability at Point of Use.
18. Source Capacity vs Delivered Availability
A Source may possess substantial capacity while infrastructure limits what can actually reach the relevant system.
For example:
Generation Capacity → Transmission Constraint → Lower Delivered Electricity Availability
or:
Water Source Capacity → Pipeline Constraint → Lower Delivered Water Availability
RACS therefore distinguishes:
Source Capacity ≠ Delivered Availability.
19. Supporting Resource Dependencies
Resource availability may depend upon other Resources.
Examples:
Compute requires electricity.
Compute may require cooling.
Cooling may require water and electricity.
Water distribution may require electricity.
Material processing may require energy.
The nominal capacity of the Governed Resource may therefore exceed its effective available capacity.
RACS preserves the effect of these dependencies without taking ownership of the supporting Resource domains.
20. Bottlenecks
Resource capacity may pass through multiple capacity layers.
The effective Resource availability may therefore be limited by a bottleneck.
Example:
Installed Compute → Electricity Capacity → Cooling Capacity → Network Capacity → Usable Compute Capacity
Increasing one capacity layer does not necessarily increase final Resource availability if another layer remains constrained.
Capacity expansion at one layer does not guarantee equivalent Resource Availability expansion.
21. Availability Is Dynamic
Availability & Capacity cannot always be determined once and treated as permanent.
Availability may change through:
outage;
maintenance;
degradation;
Source loss;
Source addition;
infrastructure repair;
reservation change;
recovery;
regeneration;
seasonal change;
supporting Resource change.
RACS therefore requires reassessment when material Resource conditions change.
22. Evidence and Uncertainty
Availability determinations must remain connected to evidence.
Evidence may include:
measurements;
inventory;
sensor data;
technical capacity records;
Source records;
operational records;
infrastructure status;
specialized Resource determinations.
RACS also distinguishes:
Observed Availability
Inferred Availability
Declared Availability
Predicted Availability
Simulated Availability
Assumed Availability
These are not methodologically equivalent.
Declared Availability ≠ Verified Availability.
Predicted Availability ≠ Current Availability.
Availability Assumption ≠ Availability Evidence.
23. Availability & Capacity Sufficiency
RACS does not require impossible certainty.
It requires sufficient Resource information for legitimate downstream governance.
Possible conditions include:
Availability & Capacity Sufficient
Conditionally Sufficient
Partially Sufficient
Evidence-Limited
Conflicted
Insufficient
Unresolved
Uncertainty must remain visible when downstream governance proceeds.
24. Relationship to Resource Characterization Standard (RCHS)
RCHS establishes:
What Resource is being governed?
RACS establishes:
How much of that characterized Resource is actually available and usable under the relevant conditions?
RACS must therefore not replace or reconstruct Resource Characterization without reason.
Canonical relationship:
RCHS Governed Resource Characterization → RACS Resource Availability & Capacity Profile
Resource Characterization ≠ Resource Availability Determination.
25. Relationship to Resource Demand Governance
RACS determines the Resource capacity side.
Resource Demand Governance determines the demand side.
These are deliberately separated.
Availability ≠ Demand.
A Resource may have:
high availability and high demand;
high availability and low demand;
low availability and high demand;
low availability and low demand.
Scarcity cannot be inferred legitimately from availability alone.
26. Relationship to Resource Access Governance
This boundary is fundamental.
RACS determines whether Resource is practically accessible.
Resource Access Governance determines whether an actor is legitimately eligible or authorized to access it.
Practical Accessibility ≠ Governance Access Authorization.
A Resource can be technically reachable while access is prohibited.
It can also be authorized while temporarily physically inaccessible.
27. Relationship to Resource Prioritization & Allocation
RACS may determine Potentially Allocable Capacity.
It does not determine:
who receives it;
how much they receive;
which dependency receives priority;
whether Resource should be reallocated.
Those questions belong downstream.
Potentially Allocable Capacity ≠ Allocation Decision.
28. Relationship to Scarcity Governance
Low Resource availability can contribute to scarcity.
It does not automatically establish scarcity.
Scarcity may depend upon:
Availability Demand Dependency Criticality Time Location Substitution Other Resource conditions
Low Availability ≠ Scarcity by definition.
29. Relationship to VEGA™
VEGA™ governs whether Resource consumption by an intelligent system is justified relative to validated Value.
RACS governs whether the Resource capacity actually exists and is available.
A workload may be highly valuable while the required Resource is unavailable.
Likewise, Resource may be abundant while the workload is unjustified.
Resource Availability ≠ Resource Justification.
Resource Justification ≠ Resource Entitlement.
Resource Justification ≠ Resource Allocation Authority.
30. Specialized Resource Domains
RACS is Resource-agnostic.
It does not replace specialized Resource science or engineering.
Specialized domains may establish:
hydrological capacity;
electrical generation or transmission capacity;
battery capacity;
compute capacity;
network throughput;
material processing capacity;
biological stock capacity.
Canonical relationship:
Specialized Resource Determination → RACS Availability & Capacity Input → Governed Resource Availability & Capacity Profile
The specialized domain determines the Resource-specific reality.
RACS governs what that reality means for Resource Availability & Capacity.
31. Who Is This Standard For?
RACS may be relevant to:
Public institutions
Infrastructure operators
Utilities
Energy and water operators
Data centers
AI infrastructure operators
Industrial enterprises
Critical-material and supply-chain operators
Network operators
Storage operators
Resource planning teams
Resilience and continuity teams
Sustainability teams
Technology providers
Governance-system designers
Researchers and methodological practitioners
Its purpose is not limited to one Resource sector.
32. Use Case 1 — AI Data Center Compute Capacity
An AI data center reports:
10,000 installed accelerators.
A conventional infrastructure inventory may treat all installed hardware as available compute capacity.
RACS requires a different question:
How much compute capacity is actually available and usable now?
Relevant conditions may include:
hardware operational state;
electricity availability;
cooling capacity;
network capacity;
storage capacity;
maintenance;
reserved compute;
workload configuration.
The resulting capacity may therefore differ substantially from nominal installed capacity.
Canonical distinction:
Installed Compute → Available Compute → Usable Compute → Reserved / Unreserved Compute → Potentially Allocable Compute
RACS does not determine which AI workload receives that capacity.
It establishes what capacity can legitimately proceed into that decision.
33. Use Case 2 — Regional Water Supply
A regional water system contains substantial water Resource stock.
However, part of that Resource may be:
seasonally unavailable;
outside the relevant distribution zone;
quality-constrained;
limited by treatment capacity;
limited by pipeline capacity;
reserved for essential dependencies.
Reporting only total water stock could therefore materially overstate Resource availability.
RACS distinguishes:
Existing Water Resource
from:
Available Water
from:
Accessible Water
from:
Usable Water Capacity
from:
Reserved Capacity
from:
Potentially Allocable Water Capacity
The standard does not determine who receives the water.
It establishes how much water can legitimately enter that later governance process.
34. Critical Distinctions
Resource Existence ≠ Resource Availability
Resource Stock ≠ Resource Capacity
Nominal Capacity ≠ Available Capacity
Installed Capacity ≠ Available Capacity
Theoretical Capacity ≠ Actual Available Capacity
Available Resource ≠ Accessible Resource
Accessible Resource ≠ Usable Resource
Resource Accessibility ≠ Resource Access Authorization
Usable Capacity ≠ Potentially Allocable Capacity
Potentially Allocable Capacity ≠ Allocated Capacity
Reserved Capacity State ≠ Reservation Authority
Unreserved Capacity ≠ Allocable Capacity
Source Capacity ≠ Delivered Availability
Available Quantity ≠ Available Flow Rate
Stored Resource ≠ Immediately Available Resource
Recoverable Resource ≠ Available Recovered Resource
Current Availability ≠ Future Availability
Average Availability ≠ Peak Availability
Declared Availability ≠ Verified Availability
Predicted Availability ≠ Current Availability
Availability ≠ Demand
Availability ≠ Dependency
Available Capacity ≠ Priority
Available Capacity ≠ Allocation Authority
Low Availability ≠ Scarcity
Current Availability ≠ Sustainability
Availability State ≠ Value State
35. Canonical Statement
An Availability & Capacity Standard is a governance standard that determines which portion of an identified Resource or Resource capacity actually exists in a condition capable of supporting downstream Resource governance under the relevant physical, technical, spatial, temporal, infrastructural, and operational conditions.
Within RSGA™, that function is performed by the Resource Availability & Capacity Standard (RACS).
RACS establishes the governed transition from:
Resource that exists
to:
Resource capacity that is actually available, practically accessible, usable, appropriately represented as reserved or unreserved, and potentially capable of entering downstream allocation governance.
It therefore provides the canonical Availability & Capacity layer between Resource Characterization and the later governance of Demand, Dependency, Access, Priority, Allocation, Consumption, Scarcity, Resilience, and Sustainability.
36. Canonical Closing Statement
A Resource does not become operationally meaningful merely because it exists, appears in inventory, or has been installed.
RACS establishes what capacity is actually there, actually reachable, actually usable, and actually capable of proceeding into governance.
Existence tells us that the Resource is there. RACS tells us how much of it can actually matter.
Governed Links
About Resource Availability & Capacity Standard (RACS)
Resource Availability Determination Module (RADM)
Usable Capacity Condition Module (UCCM)
Reserved Capacity Module (RVCM)
Temporal Availability Module (TAVM)
Location & Accessibility Module (LAAM)