RVCM — Reserved Capacity Module
Architecture: RSGA™ — Resource Sustainability Governance Architecture
Parent Standard: Resource Availability & Capacity Standard (RACS)
Category: Governance & Enforcement
Subcategory: Resource Governance
Type: Core Module
Governed Space: Reserved Resource Capacity Governance
Module ID: RSGA-RACS-RVCM-03
Origin ID: OOF-RSGA-RACS-RVCM
Version: 1.0
Status: Draft Module
Effective Date: 4 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
RVCM — Reserved Capacity Module governs how available and usable Resource capacity that is withheld, protected, designated, committed, buffered, or otherwise reserved from general Resource availability is identified, represented, quantified, evidenced, temporally bounded, reconciled, released, and reassessed without confusing the existence of a reservation with the authority or legitimacy that created it.
RVCM establishes the Reserved Capacity State within RACS.
Reserved Capacity State ≠ Reservation Authority.
2. Operational Role
RADM determines what Resource capacity is available.
UCCM determines what portion is usable.
RVCM determines what portion of that capacity is already represented as reserved and therefore cannot automatically be treated as generally available for downstream allocation.
Its operational role is to distinguish:
Usable Capacity
from:
Reserved Capacity
and:
Unreserved Capacity
without determining whether the reservation itself is legitimate, justified, or authorized.
3. Core Question
What portion of available and usable Resource capacity is currently reserved, for what represented purpose, under what conditions, for what period, and with what evidence?
4. Position in RACS Module Flow
RADM — Resource Availability Determination Module → UCCM — Usable Capacity Condition Module → RVCM — Reserved Capacity Module
→ TAVM — Temporal Availability Module → LAAM — Location & Accessibility Module
RVCM receives governed Availability and Usability states.
It establishes which capacity remains reserved before final temporal, spatial, and accessibility conditions are consolidated.
5. Governed Space
RVCM governs:
Reserved Resource Capacity Governance
This space concerns the capacity consequence of existing reservation states within the Governed Resource.
6. Governed Object
The primary Governed Object is:
The Reserved Capacity State of available and usable Resource capacity.
This may concern:
Physical Resource stock Generation capacity Storage capacity Transmission capacity Processing capacity Compute capacity Cooling capacity Network capacity Water capacity Material capacity Emergency capacity Strategic Resource capacity Other constrained Resource capacity
7. Scope
RVCM applies to Resource capacity that is represented as reserved, withheld, protected, committed, buffered, designated, contingent, or otherwise excluded from general Resource availability for a defined purpose or condition.
Its Scope includes:
reservation identification; reserved quantity or capacity; reservation type; reservation purpose reference; reservation beneficiary or protected function reference where relevant; reservation conditions; reservation activation; reservation duration; reservation priority reference; reservation overlap; reservation dependency; reservation conflict; reservation evidence; reservation uncertainty; reservation expiry; reservation release;
reservation change; reservation reconciliation; reservation reassessment; unreserved capacity determination.
RVCM does not determine:
whether reservation authority exists; whether a reservation is legally or institutionally legitimate; whether a beneficiary deserves priority; whether the reservation should originally have been created; general Resource access authorization; final allocation; consumption; scarcity response; resilience; sustainability.
8. Entry Requirement
RVCM begins with governed Resource Availability and Usable Capacity profiles.
Canonical input:
**Resource Availability Profile
Usable Capacity Profile → Reserved Capacity Determination**
The input should preserve:
Resource ID Available Capacity Usable Capacity Resource function Native measurement Relevant location Relevant time Evidence Uncertainty
9. Reservation Definition
A Reservation is a represented condition under which defined Resource capacity is withheld, protected, designated, committed, buffered, or otherwise excluded from unrestricted downstream allocation for a defined purpose, beneficiary, function, contingency, or condition.
RVCM governs the Resource-capacity consequence of that reservation.
10. Reserved Capacity Definition
Reserved Capacity is the portion of Resource capacity represented as subject to an active or applicable reservation condition.
Reserved Capacity remains Resource capacity even when it is unavailable for general allocation.
11. Reservation State vs Authority
RVCM must distinguish the factual Resource state from the authority that created it.
A system may establish that:
20 MW is reserved
without RVCM determining whether the actor reserving it possessed legitimate authority.
Reservation Existence ≠ Reservation Authority.
12. Reservation State vs Legitimacy
A reservation may exist operationally while its legitimacy remains disputed.
RVCM must preserve that distinction.
Existing Reservation ≠ Legitimate Reservation.
Where legitimacy matters, the competent Access, Authority, legal, contractual, or institutional governance domain must determine it.
13. Reservation State vs Priority
A reservation may reflect a prior priority decision.
RVCM records the resulting capacity state.
It does not independently determine the underlying priority.
Reserved Capacity ≠ Priority Determination.
14. Reservation State vs Allocation
Reservation and allocation are not identical.
Reservation protects or withholds capacity.
Allocation assigns capacity through downstream Resource governance.
Reserved Capacity ≠ Allocated Capacity.
15. Reservation State vs Consumption
Reserved capacity may never be consumed.
Reserved ≠ Consumed.
Reservation describes a capacity state, not actual Resource use.
16. Reservation State vs Availability
Reserved capacity may remain physically available and technically usable.
Its reservation changes its downstream governance status.
Reserved Resource may remain Available Resource.
17. Reservation State vs Usability
Capacity may be both:
Available Usable Reserved
simultaneously.
These are separate governed dimensions.
18. Unreserved Capacity
Unreserved Capacity is capacity not currently represented as subject to an applicable reservation.
Unreserved does not automatically mean allocable.
Unreserved Capacity ≠ Potentially Allocable Capacity.
Other RACS and downstream governance conditions may still apply.
19. Reservation Purpose
A reservation should identify its represented purpose where material.
Examples may include:
Emergency response Continuity protection Strategic reserve Maintenance contingency Critical infrastructure support Operational buffer System stabilization Contractual commitment Protected dependency
RVCM records the purpose reference.
It does not determine whether that purpose is justified.
20. Purpose-Specific Reservation
Capacity may be reserved for a defined function.
The reservation must remain linked to that function where material.
21. Beneficiary Reference
A reservation may identify a:
System Function Dependency Facility Participant Population Institution Operational process
for whose benefit capacity is represented as reserved.
RVCM may preserve this reference without establishing entitlement.
22. Protected Function Reservation
Capacity may be reserved to protect a critical or continuity-sensitive function.
RVCM records the capacity state.
RDCS, RIRS, RCSS, or other competent governance domains determine the significance of the protected dependency.
23. Emergency Reserve
Emergency Reserve is capacity protected for activation under defined emergency conditions.
It must not automatically be treated as ordinary unreserved capacity.
Emergency Reserve ≠ General Allocation Capacity.
24. Strategic Reserve
Strategic Reserve is Resource capacity protected for defined strategic conditions or horizons.
RVCM governs its capacity representation.
It does not determine strategic policy.
25. Operational Reserve
Operational Reserve is capacity retained to support operational variability, stability, or contingency.
It may be active continuously or conditionally.
26. Buffer Capacity
Buffer Capacity may be maintained between ordinary Resource use and critical Resource limits.
A buffer may support operational stability or continuity.
RVCM records the capacity state without independently determining resilience.
27. Contingency Reserve
Contingency Reserve is capacity protected against a defined possible event or failure.
The triggering contingency should remain explicit where material.
28. Maintenance Reserve
Capacity may be withheld to support maintenance, replacement, repair, or system restoration.
The reservation should remain linked to its maintenance condition.
29. Contractual Reservation
Capacity may be represented as reserved under a contractual arrangement.
RVCM records the Resource consequence.
Contractual Reservation ≠ Physical Consumption.
RVCM does not determine contractual validity.
30. Institutional Reservation
Capacity may be reserved under an institutional or administrative mechanism.
RVCM records the resulting capacity state.
It does not determine institutional authority.
31. Physical Reservation
Resource may be physically separated or isolated for a defined purpose.
Physical separation may provide strong evidence of reservation state.
It does not itself establish legitimacy.
32. Logical Reservation
Digital or system-controlled Resource capacity may be reserved logically without physical separation.
Examples include:
Compute capacity Network capacity Storage capacity Grid capacity
The reservation must remain traceable to the relevant system representation.
33. Dedicated Capacity
Capacity permanently or semi-permanently dedicated to a function may be represented separately from general reserve capacity where appropriate.
Dedicated Capacity ≠ Automatically Available General Capacity.
34. Shared Reserved Capacity
A single reserved capacity pool may support several potential protected functions.
RVCM must identify whether the functions can draw upon the capacity:
simultaneously; mutually exclusively; conditionally; sequentially.
This prevents double-counting.
35. Reservation Quantity
Every material reservation should identify the quantity or capacity reserved where it can be meaningfully quantified.
The native Resource measurement should be preserved.
36. Reservation Capacity Basis
Reservation may be expressed as:
Absolute quantity Capacity Flow Throughput Percentage Minimum reserve level Variable reserve requirement Conditional capacity
The basis must remain explicit.
37. Fixed Reservation
A Fixed Reservation protects a defined Resource quantity or capacity.
Example:
20 MW reserved
or:
10,000 m³ reserved
subject to the applicable Resource conditions.
38. Variable Reservation
A Variable Reservation changes according to a defined condition.
Examples may include:
Demand level Season Operational state Contingency level System load
The governing variable should remain explicit.
39. Minimum Reservation
A reservation may establish a minimum protected Resource capacity.
Actual reserved capacity may exceed that minimum under defined conditions.
40. Maximum Reservation
A reservation may establish a maximum capacity that may be withheld under the represented reservation condition.
41. Percentage Reservation
A reservation may be expressed as a percentage of an applicable capacity base.
The capacity base must remain explicit.
Reservation Percentage without Capacity Base is incomplete.
42. Dynamic Reservation
Reserved Capacity may change dynamically.
Dynamic reservations require a traceable rule or condition governing the change.
43. Reservation Activation
Some reservations exist continuously.
Others activate only when defined conditions occur.
RVCM must distinguish:
Active Reservation
from:
Conditional / Standby Reservation
44. Active Reservation
An Active Reservation currently removes or protects Resource capacity from general availability for downstream allocation.
45. Standby Reservation
Standby Reservation represents capacity that becomes reserved only upon activation of a defined condition.
It must not automatically reduce ordinary unreserved capacity unless the applicable Resource-system logic requires pre- protection.
46. Triggered Reservation
A Triggered Reservation activates following a defined event.
Possible triggers may include:
Emergency System failure Demand threshold Resource constraint Infrastructure outage Continuity event
The trigger source should remain traceable.
47. Reservation Trigger
A reservation trigger must be sufficiently defined to distinguish activation from assumption.
Possible Trigger ≠ Active Reservation.
48. Reservation Deactivation
When activation conditions cease, the reservation may deactivate according to the governing reservation mechanism.
RVCM must not assume automatic release unless the relevant reservation condition supports it.
49. Reservation Duration
Reservations may be:
Immediate Temporary Fixed-term Recurring Seasonal Conditional Indefinite Event-dependent
Duration must remain explicit where material.
50. Reservation Start
The effective start of a reservation should be recorded where temporal sequence matters.
51. Reservation End
A reservation may have:
Defined end Conditional end Event-based end Unknown end
Expired reservation must not remain active without evidence.
52. Reservation Expiry
Reservation expiry occurs when its defined validity ends.
Expired Reservation ≠ Active Reservation.
53. Reservation Renewal
A reservation may be renewed.
Renewal must create a traceable continuation or new reservation state where material.
54. Reservation Release
Reservation Release returns previously reserved capacity toward an unreserved state where other conditions permit.
Canonical logic:
Reserved Capacity → Release Condition → Release Evidence → Unreserved Capacity
55. Partial Release
Only part of Reserved Capacity may be released.
RVCM must support partial release.
56. Conditional Release
Release may depend upon:
Event resolution Replacement capacity Threshold recovery Time Authorization from the competent governance domain System-state change
RVCM records the resulting capacity transition.
57. Reservation Withdrawal
A reservation may be withdrawn by the competent mechanism.
RVCM records the capacity consequence.
It does not determine whether withdrawal authority was legitimate.
58. Reservation Conversion
Reserved Capacity may transition from one reservation purpose to another.
The transition must preserve:
Prior purpose New purpose Effective time Capacity amount Evidence
where material.
59. Reservation Transfer
Reservation may transfer between relevant functions, beneficiaries, locations, or Resource pools where permitted by the competent governance mechanism.
RVCM records the Resource-capacity consequence.
60. Reservation Overlap
Reservation Overlap occurs when two or more reservations claim the same Resource capacity.
Overlap must be identified before Reserved Capacity is aggregated.
61. Reservation Double-Counting
The same Resource capacity must not be counted multiple times merely because multiple reservation claims reference it.
Multiple Reservation Claims ≠ Multiple Reserved Capacities.
62. Overlapping Reserve Functions
One capacity pool may support multiple contingency purposes but may not be capable of satisfying them simultaneously.
RVCM must preserve this limitation.
63. Simultaneous Reservation
Where multiple reservations can legitimately coexist on distinct capacity portions, RVCM may aggregate them without double-counting.
64. Mutually Exclusive Reservation
Where two reservation functions cannot use the same capacity simultaneously, their relationship must remain explicit.
65. Reservation Hierarchy
A Resource System may contain nested or hierarchical reservations.
Example:
Total Capacity → Strategic Reserve → Emergency Sub-Reserve
Nested capacity must not be counted independently in a way that inflates total Reserved Capacity.
66. Parent Reservation
A Parent Reservation may contain one or more subordinate reservation states.
The total subordinate capacity must remain reconciled with the parent reservation boundary.
67. Reservation Conflict
Reservation Conflict exists where:
multiple reservations exceed available capacity; reservation claims overlap incompatibly; capacity basis differs materially; reservation state evidence conflicts; reservation timing conflicts; reservation boundaries conflict.
68. Capacity Over-Reservation
Over-Reservation occurs where represented active reservations exceed the Resource capacity capable of supporting them.
Reserved Claims > Applicable Capacity
is a governance conflict requiring resolution or explicit preservation.
69. Reservation Feasibility
RVCM may determine whether represented reservations can coexist within the available and usable capacity.
This is capacity feasibility.
It is not legitimacy assessment.
Reservation Feasibility ≠ Reservation Legitimacy.
70. Reservation Reconciliation
Canonical reconciliation:
Available / Usable Capacity → Reservation Claims → Boundary Alignment → Time Alignment → Capacity-Basis Alignment → Overlap Check → Conflict Check → Reconciled Reserved Capacity
71. Reservation Priority Reference
Where reservations have externally established priority, RVCM may preserve that priority reference for capacity-state interpretation.
RVCM does not create the priority.
72. Priority Conflict
If reservation priorities conflict, RVCM records the conflict.
The competent priority or access governance mechanism resolves it.
73. Reservation Dependency
A reservation may depend upon another Resource, infrastructure component, or capacity state.
Example:
An emergency compute reserve may depend upon electricity and cooling reserves.
RVCM may preserve the dependency.
74. Reservation Dependency Failure
A reservation may remain administratively represented while the underlying Resource capacity becomes physically or technically unavailable.
Reserved Capacity Claim ≠ Guaranteed Available Capacity.
RADM and UCCM remain authoritative for actual availability and usability.
75. Reservation Capacity Reduction
If available or usable capacity declines, the effective Reserved Capacity may require reassessment.
A reservation cannot physically preserve capacity that no longer exists or is no longer usable.
76. Reservation Capacity Increase
If Resource capacity increases, existing reservations do not automatically expand unless their governing conditions specify such behavior.
77. Reservation and Resource State
A Resource-State change may affect Reserved Capacity.
Examples:
Stored → Degraded
Usable → Temporarily Unusable
Available → Unavailable
The reservation may persist conceptually while its effective Resource capacity changes.
78. Reservation and Availability
RADM determines actual Availability.
RVCM must not count Reserved Capacity beyond what is actually available.
Reservation Claim cannot create Resource Availability.
79. Reservation and Usability
UCCM determines Usable Capacity.
RVCM must preserve whether reserved capacity is actually usable for the represented reserved function.
Reserved Capacity ≠ Necessarily Usable Reserved Capacity.
80. Effective Reserved Capacity
Effective Reserved Capacity is the portion of represented Reserved Capacity that remains available and sufficiently usable for the relevant reserved function.
This may differ from nominal reservation quantity.
81. Nominal Reserved Capacity
Nominal Reserved Capacity is the quantity stated by the reservation mechanism.
Nominal Reserved Capacity ≠ Effective Reserved Capacity.
82. Reservation Coverage
Reservation Coverage may represent how much of a defined protected capacity requirement is supported by effective Reserved Capacity.
Where the underlying requirement comes from another governance domain, RVCM consumes it rather than redefining it.
83. Reservation Shortfall
A Reservation Shortfall exists where effective Reserved Capacity is below the represented reservation requirement.
RVCM may identify the capacity shortfall.
It does not determine the broader consequence or priority response.
84. Reservation Surplus
Reserved capacity may exceed the currently represented reservation requirement.
RVCM may identify this condition.
It does not automatically release the surplus.
85. Reservation Utilization
Reserved Capacity may eventually be activated and used.
Actual consumption or utilization belongs to RCUS.
Reserve Activation ≠ Consumption by itself.
86. Reservation Consumption Transition
When reserved Resource begins to be consumed, the relevant capacity and Resource states must transition appropriately.
RVCM preserves the reservation-state consequence.
RCUS governs actual Consumption & Utilization.
87. Reservation Exhaustion
A consumable reserve may be partially or fully exhausted.
The Reserved Capacity State must be updated accordingly.
88. Replenished Reserve
Reserved capacity may be replenished through:
New supply Recovery Regeneration Reallocation Capacity restoration
The replenished capacity must pass applicable Availability and Usability governance.
89. Temporal Reservation Context
Reservation capacity may differ across time.
TAVM governs detailed Temporal Availability.
RVCM must nevertheless preserve reservation start, duration, activation, expiry, and release where material.
90. Spatial Reservation Context
Reservation may apply only at a defined:
Facility Location Region Network zone Resource pool
Location must remain explicit where capacity cannot move freely.
91. Cross-Location Reservation
A reservation at one location must not automatically be treated as protected capacity at another location.
LAAM governs practical accessibility.
Reserved Somewhere ≠ Available Everywhere.
92. Source-Specific Reservation
Reservation may apply to Resource capacity from a particular Source.
The Source relationship should remain traceable where material.
93. Multi-Source Reservation
A reservation may draw upon several Sources.
RVCM must avoid counting the same underlying Source capacity multiple times.
94. Reservation Substitution
One Resource Source or capacity pool may potentially replace another reserved capacity.
RVCM may record the existence of replacement capacity.
RSFS governs substitution decisions where Resource substitution is involved.
95. Reservation Evidence
Reserved Capacity must be supported by evidence proportionate to governance significance.
Evidence may include:
System records Capacity controls Operational records Reservation records Contracts Institutional records Technical configuration Physical separation Resource-management systems
96. Evidence of Reservation State
Evidence should establish at minimum where material:
Resource Capacity Reservation condition Effective time Applicable location Relevant purpose Status
97. Reservation Evidence Provenance
Evidence should remain traceable to:
Source Actor or system Resource Time Location Reservation mechanism Version
where applicable.
98. Reservation Evidence Freshness
Reservation states may change rapidly.
Evidence freshness must follow the Resource and reservation mechanism.
Previously Reserved ≠ Currently Reserved.
99. Declared Reservation
An actor may declare Resource capacity reserved.
The declaration may establish an operational claim.
It does not independently establish legitimacy.
100. System-Enforced Reservation
A Resource-management system may technically enforce a reservation.
System enforcement provides strong evidence of capacity-state implementation.
Technical Enforcement ≠ Governance Legitimacy.
101. Physical Reservation Evidence
Physical separation may support evidence that capacity is reserved.
It must remain associated with the relevant Resource boundary and purpose.
102. Inferred Reservation
Reservation may sometimes be inferred from Resource-system behavior.
Inference must remain distinguishable from explicit reservation evidence.
Inferred Reservation ≠ Explicit Reservation.
103. Assumed Reservation
An assumed reservation must remain identified as an assumption.
Reservation Assumption ≠ Reservation Evidence.
104. Reservation Uncertainty
Material uncertainty may concern:
Capacity amount Purpose Activation Duration Location Beneficiary reference Reservation overlap Release state Evidence freshness
Uncertainty must remain visible.
105. Reservation Conflict Evidence
Where evidence supports incompatible reservation states, the conflict must remain explicit until resolved or legitimately bounded.
106. Unknown Reservation State
Where evidence is insufficient:
Unknown Reservation State ≠ Unreserved Capacity.
This distinction is essential.
Absence of evidence of reservation is not always evidence that capacity is unreserved.
107. Reservation Sufficiency
Reservation State is sufficiently established when enough evidence exists to represent its material capacity consequence for downstream RACS governance.
Possible states:
Reservation Sufficient
Conditionally Sufficient
Partially Sufficient
Evidence-Limited
Conflicted
Insufficient
Unresolved
108. Reservation Decision States
At minimum, RVCM should distinguish:
Reserved
Partially Reserved
Conditionally Reserved
Standby Reserved
Released
Expired
Unreserved
Reservation Evidence-Limited
Reservation Conflicted
Reservation Unknown
Reservation Unresolved
109. Reservation State Transition
Canonical transitions may include:
Unreserved → Reserved
Reserved → Partially Released
Reserved → Released
Reserved → Expired
Standby Reserved → Active Reserved
Reserved Purpose A → Reserved Purpose B
Transitions should remain evidenced.
110. Reservation Change Event
A material change may include:
Reservation creation Activation Capacity increase Capacity reduction Partial release Full release Expiry Renewal Purpose change Location change Source change Conflict discovery Availability reduction Usability reduction
111. Reservation Reassessment Trigger
RVCM reassessment should occur following material:
RADM Availability change UCCM Usable Capacity change Reservation activation Reservation expiry Reservation release Reservation renewal Reservation-purpose change Resource-State change Location change Source change Supporting Resource change New evidence Evidence expiry Conflict discovery
112. Reassessment Logic
Canonical logic:
Existing Reserved Capacity State → New Evidence / Material Change → Reservation Impact Test → State Retained or Revised → Capacity Reconciliation → Version Update → Downstream RACS Reassessment
113. Reservation Versioning
Material reservation changes should preserve:
Previous state New state Capacity difference Purpose difference Effective time Evidence Known uncertainty
114. Reservation History
Reservation History may support:
Audit Capacity planning Continuity analysis Conflict investigation Resource accounting Governance reassessment
Historical reservations must not be represented as current reservations.
115. Reserved Capacity Accounting
Where capacity can be meaningfully quantified:
Usable Capacity − Effective Reserved Capacity = Remaining Unreserved Capacity
only where the Resource structure permits direct subtraction and no overlapping or conditional capacity requires more complex treatment.
This is not a universal formula.
116. Non-Additive Reservation
Some Resource systems cannot represent reservations through simple arithmetic because:
capacity is shared; functions are mutually exclusive; reservation is conditional; capacity is flow-dependent; availability varies through time.
RVCM must follow Resource reality.
117. Reservation Reconciliation with Usable Capacity
Reserved Capacity must be reconciled against UCCM output.
Canonical logic:
Usable Capacity → Reservation Claims → Effective Reservation Test → Overlap Reconciliation → Effective Reserved Capacity → Remaining Unreserved Capacity
118. Reservation Reconciliation with Availability
If RADM Availability declines below nominal Reserved Capacity, RVCM must represent the resulting shortfall.
Reservation claims must not manufacture missing Resource.
119. Unreserved Capacity Determination
RVCM may establish Remaining Unreserved Capacity after valid reservation states are represented.
Unreserved Capacity remains subject to:
Temporal Availability Location & Accessibility Access Governance Prioritization Allocation
120. Potentially Allocable Boundary
RVCM does not independently determine final Potentially Allocable Capacity.
Its Unreserved Capacity output becomes one input to the remaining RACS modules.
121. Reservation Comparability
Reservation states should be compared only where relevant conditions align sufficiently.
Relevant conditions may include:
Resource Capacity basis Function Time Location Reservation type Activation state
122. Cross-System Reservation Comparability
Two systems may report identical reserve percentages while protecting very different Resource realities.
Same Reserve Percentage ≠ Same Reserved Resource Condition.
123. Reservation Ratio
Where useful:
Reserved Capacity / Applicable Capacity Base
may be represented as a reservation ratio.
The denominator must be explicit.
The ratio does not determine whether the reservation is appropriate.
124. Effective Reserve Ratio
Where Nominal Reserved Capacity differs from Effective Reserved Capacity, the distinction should remain visible.
125. Native Measurement
Reserved Capacity should remain expressed in the Resource's native or technically appropriate measurement wherever possible.
Examples:
m³ MW MWh tonnes units GPU-hours bandwidth throughput
126. Normalization Boundary
RVCM does not replace native Reserved Capacity with a universal normalized Resource metric.
Native Reserved Capacity ≠ Normalized Resource Significance.
127. Reserved Capacity Profile
The principal RVCM output is the:
Reserved Capacity Profile
It should establish:
what Resource capacity is reserved; how much; for what represented purpose; under what conditions; when; where; whether active or conditional; whether effective capacity differs from nominal reservation; what evidence supports it; what uncertainty or conflict remains.
128. Minimum Profile Fields
A minimum Reserved Capacity Profile should support:
Resource ID RADM Availability Profile Reference UCCM Usable Capacity Profile Reference Reservation ID Reservation Type Reservation State Reservation Purpose Reference Nominal Reserved Capacity Effective Reserved Capacity Native Measurement Activation State Start Time End / Expiry Condition Location Reference Source Reference where relevant Evidence Basis Uncertainty Conflict State Sufficiency State Version
129. RACS Handoff
RVCM output becomes an input to the remaining RACS modules.
Canonical handoff:
Resource Availability Profile → Usable Capacity Profile → Reserved Capacity Profile → Temporal Availability Profile → Location & Accessibility Profile → Resource Availability & Capacity Profile
130. Downstream Release Condition
RVCM output may proceed when Reserved Capacity is sufficiently established for subsequent RACS governance.
Conditional progression may occur where uncertainty remains explicit.
Progression does not erase Reservation uncertainty.
131. Failure Conditions
RVCM should not be considered sufficiently completed where:
reservation existence is treated as proof of reservation authority; reservation existence is treated as proof of legitimacy; Reserved Capacity is confused with Allocated Capacity; Reserved Capacity is confused with Consumed Resource; nominal reservation is treated as effective reserve without Availability and Usability checks; expired reservations remain active without evidence; standby reservations are represented as active without activation; overlapping reservations are double-counted; shared reserve pools are counted multiple times; nested reservations inflate total Reserved Capacity;
reservation claims exceed applicable capacity without conflict being represented; unknown reservation state is treated as unreserved; reservation release is assumed without evidence; Resource Availability reduction is ignored; Usable Capacity reduction is ignored; material uncertainty is hidden; reservation evidence is materially stale.
132. Governance Requirements
A conforming RVCM implementation must:
1. receive governed Availability and Usable Capacity profiles; 2. identify applicable reservation states; 3. distinguish Reserved Capacity from reservation authority; 4. distinguish Reserved Capacity from reservation legitimacy; 5. identify reservation type; 6. preserve reservation purpose reference; 7. preserve beneficiary or protected-function reference where material; 8. quantify reservation capacity where possible; 9. distinguish nominal from effective Reserved Capacity; 10. preserve activation conditions; 11. preserve reservation duration; 12. preserve expiry conditions; 13. preserve release conditions; 14. support partial release; 15. support reservation renewal; 16. support reservation change; 17. identify overlapping reservations; 18. prevent reservation double-counting; 19. preserve shared-capacity relationships; 20. preserve nested reservation relationships; 21. identify over-reservation; 22. identify reservation shortfall; 23. reconcile Reserved Capacity with actual Availability; 24. reconcile Reserved Capacity with Usable Capacity; 25. preserve evidence provenance; 26. preserve evidence freshness; 27. preserve uncertainty and conflict; 28. support reassessment; 29. support versioning; 30. produce a governed Reserved Capacity Profile.
133. Governance Logic
Canonical RVCM logic:
**Resource Availability Profile
Usable Capacity Profile → Reservation Identification → Reservation Type → Reservation Purpose Reference → Nominal Reserved Capacity → Activation State → Temporal / Spatial Conditions → Availability & Usability Reconciliation → Overlap Check → Conflict Check → Effective Reserved Capacity → Remaining Unreserved Capacity → Evidence & Uncertainty
→ Sufficiency → Reserved Capacity Profile**
Where evidence is insufficient:
Reservation Question → Evidence Gap → Minimum Evidence Requirement → Evidence Acquisition → Reservation Reassessment
Where capacity changes:
Existing Reserved Capacity → Availability / Usability Change → Effective Reservation Test → Revised Reserved Capacity → Version Update
134. Governance Outputs
RVCM may produce:
Reserved Capacity Profile Reservation State Reservation Type Reservation Purpose Reference Nominal Reserved Capacity Effective Reserved Capacity Unreserved Capacity Reservation Activation State Reservation Expiry State Reservation Release State Reservation Overlap State Reservation Conflict State Reservation Shortfall State Reservation Surplus State Reservation Evidence State Reservation Uncertainty State Reservation Sufficiency State Reservation Version Reassessment Trigger RACS Handoff State
135. Minimum Implementation Framework
A minimum operational RVCM implementation must contain at least eight governed layers.
Layer 1 — Capacity Input
Receive:
Resource ID Resource Availability Profile Usable Capacity Profile Applicable Capacity Base
Layer 2 — Reservation Identification
Identify:
Reservation ID Reservation Type Purpose Reference Protected Function / Beneficiary Reference where relevant
Layer 3 — Reservation Capacity
Determine:
Nominal Reserved Capacity Capacity Basis Native Measurement
Layer 4 — Reservation Conditions
Represent:
Activation Duration Start Expiry Release conditions Location Source where relevant
Layer 5 — Capacity Reconciliation
Compare reservation claims with:
Available Capacity Usable Capacity Other Reservations
Layer 6 — Conflict & Overlap
Determine:
Overlap Double-counting Over-Reservation Shortfall Conflict
Layer 7 — Evidence & Decision
Preserve:
Evidence Freshness Uncertainty Reservation Decision State Effective Reserved Capacity
Layer 8 — Governed Output & Reassessment
Produce:
Reserved Capacity Profile Remaining Unreserved Capacity Version Known limitations Reassessment triggers RACS handoff state
Minimum machine-readable logic:
Resource → Availability Profile → Usable Capacity Profile → Reservation[] → Purpose[] → Capacity[] → Conditions[] → Overlap[] → Conflict[] → Evidence[] → Uncertainty[] → Effective Reserved Capacity → Unreserved Capacity → Reserved Capacity Profile
136. Minimum Decision States
At minimum:
Reserved
Partially Reserved
Conditionally Reserved
Standby Reserved
Released
Expired
Unreserved
Reservation Evidence-Limited
Reservation Conflicted
Reservation Unknown
Reservation Unresolved
137. Minimum Evidence Path
Where Reserved Capacity cannot be sufficiently established:
Reservation Unresolved → Material Missing Evidence → Minimum Evidence Requirement → Evidence Acquisition → Reservation Reconciliation → Updated Reserved Capacity Profile
The objective is sufficient capacity-state evidence, not determination of reservation legitimacy.
138. Minimum Reassessment Framework
At minimum:
Current Reserved Capacity Profile → New Evidence / Material Change → Reservation Impact Test → Availability & Usability Reconciliation
→ State Retained or Revised → Profile Version Update → Downstream RACS Reassessment
139. Use Case 1 — AI Compute Emergency Reserve
RADM establishes:
8,900 accelerator-equivalent units of available compute capacity.
UCCM establishes:
8,100 units usable for the defined workload class.
The facility reports:
1,500 units reserved for emergency and continuity workloads.
RVCM does not simply subtract 1,500.
It first establishes:
whether the reservation is active; which capacity pool it references; whether the reserved units remain available; whether they remain usable for the protected workload; whether another reservation overlaps the same units; when the reservation expires or releases.
Evidence establishes:
Nominal Reserved Capacity: 1,500 units
but:
100 reserved units are temporarily unusable.
The effective Resource state may therefore be represented as:
Usable Capacity: 8,100
Nominal Reserved Capacity: 1,500
Effective Reserved Capacity: 1,400
with the applicable uncertainty and conditions preserved.
RVCM does not decide whether the emergency reservation is justified.
It establishes its actual capacity consequence.
A reservation claim can protect capacity; it cannot create capacity that does not exist.
140. Use Case 2 — Regional Water Emergency Reserve
A regional water system has:
120,000 m³/day of usable water capacity.
The system records:
30,000 m³/day reserved for hospitals, emergency services, and other protected continuity functions during defined emergency conditions.
RVCM determines:
reservation capacity; activation status; protected-function references; time conditions; Source relationships; whether reservations overlap; whether the capacity remains physically available and usable.
If only 25,000 m³/day of the nominal reserve remains effectively available because of a Source constraint, RVCM must preserve:
Nominal Reserved Capacity: 30,000 m³/day
and:
Effective Reserved Capacity: 25,000 m³/day
rather than representing the nominal reservation as guaranteed physical capacity.
RVCM does not determine which protected function has the highest priority.
It establishes the governed Reserved Capacity State on which that later decision can rely.
Protected intent does not manufacture missing Resource capacity.
141. Critical Distinctions
Reserved Capacity State ≠ Reservation Authority
Reservation Existence ≠ Reservation Authority
Existing Reservation ≠ Legitimate Reservation
Reserved Capacity ≠ Priority Determination
Reserved Capacity ≠ Allocated Capacity
Reserved ≠ Consumed
Reserved Capacity ≠ Unavailable Capacity
Reserved Capacity ≠ Necessarily Usable Reserved Capacity
Nominal Reserved Capacity ≠ Effective Reserved Capacity
Emergency Reserve ≠ General Allocation Capacity
Dedicated Capacity ≠ General Capacity
Possible Trigger ≠ Active Reservation
Standby Reservation ≠ Active Reservation
Expired Reservation ≠ Active Reservation
Unknown Reservation State ≠ Unreserved Capacity
Reservation Feasibility ≠ Reservation Legitimacy
Reservation Claim ≠ Guaranteed Available Capacity
Reservation Claim cannot create Resource Availability
Multiple Reservation Claims ≠ Multiple Reserved Capacities
Multiple Reserve Functions ≠ Independent Reserve Pools
Unreserved Capacity ≠ Potentially Allocable Capacity
Reserve Activation ≠ Consumption
Same Reserve Percentage ≠ Same Reserved Resource Condition
Reserved Somewhere ≠ Available Everywhere
Native Reserved Capacity ≠ Normalized Resource Significance
142. Cross-Architecture Boundary
RVCM governs the Resource-capacity consequence of reservations.
It does not govern general:
Authority: Legal entitlement Contract validity Priority determination Access authorization Allocation authority Liability
GOA™ retains Governance Authority.
RAGS governs Resource Access.
RPAS governs Resource Prioritization & Allocation.
Other competent architectures or institutional systems may determine the legitimacy of the reservation mechanism itself.
RVCM consumes those determinations where necessary and governs the resulting Resource-capacity state.
143. 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.
A contract may create a reservation claim.
An authority mechanism may authorize a reserve.
A continuity system may establish a reserve requirement.
An infrastructure system may technically enforce a reservation.
RVCM does not absorb those mechanisms.
It governs what their resulting reservation means for Resource Availability & Capacity.
144. Canonical Boundary
RVCM governs how Resource capacity represented as reserved is identified, quantified, reconciled with actual Availability and Usability, protected from double-counting, evidenced, released, and reassessed so that Reserved Capacity is accurately represented within RACS.
It does not determine whether the reservation was legitimately authorized, whether the beneficiary deserves priority, how final allocation should occur, whether Resource should be consumed, or whether the Resource System is resilient or sustainable.
Its governed output is the Reserved Capacity Profile required for subsequent RACS governance.
145. Canonical Closing Statement
A reservation can change which capacity remains available for general governance, but it cannot create Resource capacity, prove authority, or guarantee that the reserved Resource still exists.
RVCM makes the difference between capacity that is merely claimed as reserved and capacity that is actually reserved, available, usable, and governable visible.