LAAM — Location & Accessibility 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: Resource Location & Practical Accessibility Governance
Module ID: RSGA-RACS-LAAM-05
Origin ID: OOF-RSGA-RACS-LAAM
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
LAAM — Location & Accessibility Module governs how the spatial location, Resource pathway, delivery relationship, infrastructure reachability, transfer conditions, and practical accessibility of available Resource capacity are identified, represented, evidenced, reconciled, and reassessed so that Resource capacity available at one Source, location, network zone, storage point, infrastructure node, or Resource System is not automatically treated as accessible at the location where it is required.
LAAM establishes the final spatial and practical-accessibility layer of RACS.
Resource Availability ≠ Resource Accessibility.
2. Operational Role
RADM establishes what Resource capacity is available.
UCCM establishes what portion is usable.
RVCM establishes what portion is reserved.
TAVM establishes when that capacity is available.
LAAM determines:
where the capacity exists; where it can physically or technically reach; through which Resource pathway; through which infrastructure; with what transfer capacity; with what spatial constraints; and whether it is practically accessible at the relevant destination.
LAAM therefore completes the transition from Resource capacity that exists somewhere to Resource capacity that can actually reach the relevant point of use.
3. Core Question
Where is the relevant Resource capacity located, and what portion can actually reach the required Resource location or point of use under the applicable physical, technical, infrastructural, spatial, and temporal conditions?
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
LAAM is the fifth and final Core Module of RACS.
Its output enables consolidation of the:
Resource Availability & Capacity Profile
5. Governed Space
LAAM governs:
Resource Location & Practical Accessibility Governance
This space concerns the spatial and infrastructural conditions connecting Resource capacity to the location where that capacity is relevant.
6. Governed Object
The primary Governed Object is:
The Location & Practical Accessibility State of Resource capacity.
This may concern:
Physical Resource stock Resource flow Electricity capacity Water capacity Material capacity Compute capacity Storage capacity Network capacity Cooling capacity Transmission capacity Processing capacity Recovered Resource capacity Other spatially constrained Resource capacity
7. Scope
LAAM applies where Resource location or the ability to move, transmit, deliver, connect, route, transfer, access, or otherwise make Resource capacity practically reachable materially affects Resource Availability & Capacity.
Its Scope includes:
Resource location; Source location; storage location; point-of-use location; destination; Resource pathway; delivery pathway; network topology; transmission pathway; distribution pathway; transport pathway; transfer infrastructure; infrastructure reachability; connection state; route availability; transfer capacity; delivery capacity; distance where material; spatial constraints;
geographic constraints; network-zone constraints; location-specific capacity; cross-location transfer; practical accessibility; accessibility evidence; accessibility uncertainty; accessibility change; reassessment.
LAAM does not determine:
legal access rights; institutional authorization; ownership; entitlement; participant eligibility; priority; allocation; consumption; scarcity response; general logistics governance; resilience; sustainability.
8. Entry Requirement
LAAM receives governed outputs from the preceding RACS modules.
Canonical input:
**Resource Availability Profile
Usable Capacity Profile Reserved Capacity Profile Temporal Availability Profile → Location & Accessibility Determination**
9. Resource Location
Every Resource exists, operates, flows, or is represented within a spatial or system location relevant to its Resource reality.
Location may be:
Physical Geographic Infrastructure-based Network-based Logical Distributed Mobile Source-based Storage-based Destination-based
10. Location Is Resource-Specific
Location must follow the Resource reality.
For water, location may concern:
Reservoir Aquifer Pipeline Treatment facility Distribution zone
For electricity:
Generation node Grid zone Transmission network Distribution node
For compute:
Data center Cluster Region Availability zone Physical infrastructure site
For materials:
Mine Warehouse Processing site Port Manufacturing facility
11. Source Location
Source Location identifies where Resource supply originates for the relevant availability determination.
ROSM governs Source identity.
LAAM governs the spatial consequence of that Source.
12. Current Resource Location
Current Resource Location identifies where the Resource or capacity is presently situated.
This may differ from its Origin or Source.
Resource Origin ≠ Resource Source ≠ Current Resource Location.
13. Storage Location
Stored Resource may exist at a location different from both Source and point of use.
Storage location may materially affect practical accessibility.
14. Point of Use
Point of Use represents the location where Resource capacity must become practically accessible for the relevant function.
15. Destination Location
Destination may be:
Facility System Region Network node Infrastructure point Operational process Resource pool
where Resource capacity is required.
16. Distributed Resource
A Resource may exist across multiple locations.
Aggregate Resource quantity must not erase material spatial differences.
17. Concentrated Resource
A Resource may be concentrated in one or a small number of locations.
Spatial concentration may materially affect accessibility.
18. Mobile Resource
Some Resources may change location.
LAAM should preserve location changes where they materially alter accessibility.
19. Fixed Resource
Some Resources or capacities are effectively fixed to infrastructure.
Examples may include:
Generation capacity Compute infrastructure Pipeline capacity Transmission capacity
Their output may move while the capacity itself remains location-bound.
20. Spatial Availability
Spatial Availability represents Resource capacity available within a defined location or spatial boundary.
Global Availability ≠ Local Availability.
21. Local Availability
Resource capacity may be available locally without requiring significant transfer.
Local does not automatically mean accessible.
Infrastructure or technical constraints may still apply.
22. Remote Availability
Resource may be available at a remote Source.
Remote Resource capacity should not automatically be counted at the destination.
23. Resource Pathway
A Resource Pathway is the physical, technical, infrastructural, or network route through which Resource capacity moves or becomes accessible between relevant locations.
24. Direct Pathway
A Direct Pathway connects Source or Resource location to destination without material intermediate transfer stages.
25. Multi-Stage Pathway
A Resource may pass through multiple stages.
Example:
Water Source → Treatment → Main Pipeline → Distribution Network → Facility
Each stage may affect practical accessibility.
26. Resource Pathway Chain
Canonical representation:
Resource Location → Transfer Pathway → Intermediate Node(s) → Destination → Practical Accessibility
27. Pathway Completeness
A Resource pathway is complete where all materially necessary stages between Resource and destination are sufficiently represented.
28. Missing Pathway
Resource may be available at Source while no viable pathway exists to the destination.
Available at Source ≠ Accessible at Destination.
29. Pathway Availability
A Resource pathway itself may be:
Available Partially Available Conditionally Available Temporarily Unavailable Unavailable Unknown
30. Pathway Capacity
A pathway may impose a capacity limit below Resource Source capacity.
Example:
Source: 100 MW Transmission Path: 60 MW Destination Accessible Capacity: maximum 60 MW
subject to other conditions.
31. Source Capacity vs Transfer Capacity
Source Capacity ≠ Transfer Capacity.
The smaller relevant capacity may constrain what reaches the destination.
32. Transfer Capacity
Transfer Capacity represents the quantity, rate, throughput, or capacity capable of moving through the relevant Resource pathway.
33. Transfer Bottleneck
A transfer pathway may contain several capacity limits.
The active bottleneck determines the relevant pathway constraint where the Resource-specific system supports that interpretation.
34. Multi-Stage Bottleneck
Example:
Source Capacity: 100
Processing Capacity: 90
Transport Capacity: 70
Distribution Capacity: 60
The destination cannot automatically be assigned 100 units of accessible Resource capacity.
35. Bottleneck Migration
The active spatial or infrastructure bottleneck may change after:
Expansion Failure Maintenance Repair Route change Source change
LAAM supports reassessment.
36. Infrastructure Reachability
Infrastructure Reachability determines whether the relevant Resource pathway physically or technically connects the Resource to the destination.
37. Connected Resource
A Resource may be connected to the destination through relevant infrastructure.
Connection alone does not establish sufficient transfer capacity.
Connected ≠ Sufficiently Accessible.
38. Disconnected Resource
A Resource may be available but disconnected from the relevant destination.
Such capacity must not be represented as practically accessible.
39. Partial Connectivity
Only part of Resource capacity may have a viable connection.
LAAM must support partial accessibility.
40. Conditional Connectivity
Connectivity may depend upon:
Route activation Infrastructure configuration Temporary infrastructure Switching Processing Transport availability
Conditional connectivity must remain explicit.
41. Network Accessibility
For networked Resources, accessibility may depend upon network topology and capacity.
Examples:
Electricity grid Water distribution network Data network
Compute interconnect Gas pipeline
42. Network Zone
A Resource System may be divided into zones with different accessibility conditions.
Aggregate system capacity must not automatically be treated as capacity available in every zone.
43. Cross-Zone Transfer
Resource transfer between zones may be constrained by interconnection capacity.
Capacity in Zone A ≠ Capacity in Zone B.
44. Interconnection Capacity
Interconnection capacity may limit how much Resource can cross between infrastructure zones.
45. Network Congestion
A Resource pathway may be physically connected but temporarily capacity-constrained by congestion.
LAAM may represent the resulting practical-accessibility reduction.
46. Route Availability
Physical Resources may depend upon a transport or delivery route.
Route availability may change through:
Closure Congestion Damage Weather Infrastructure failure Operational restrictions
47. Alternative Route
An alternative Resource pathway may preserve accessibility when the primary pathway is unavailable.
LAAM records the alternative pathway.
It does not determine broader resilience.
48. Route Substitution
A Resource may be transferred through another route.
Route substitution is distinct from Resource substitution.
49. Single-Path Dependency
A Resource accessible through only one viable pathway may have concentrated spatial dependency.
LAAM preserves the pathway reality.
RIRS governs resilience implications.
50. Multi-Path Accessibility
A Resource may have multiple valid pathways to the destination.
LAAM may represent each pathway and its capacity.
51. Shared Pathway
Multiple Resources or participants may depend upon the same transfer infrastructure.
The full nominal pathway capacity must not automatically be attributed independently to each user.
52. Pathway Capacity Competition
Where multiple Resource flows compete for shared pathway capacity, LAAM may represent the physical or technical constraint.
It does not determine allocation priority.
53. Transport Capacity
Material Resources may depend upon transport capacity.
Examples:
Truck Rail Ship Pipeline Conveyor
Transport capacity may constrain practical accessibility.
54. Delivery Capacity
Delivery Capacity represents the Resource quantity or capacity capable of reaching the relevant destination under applicable pathway conditions.
55. Delivered Availability
Delivered Availability represents Resource capacity that can actually reach the relevant destination.
Source Availability ≠ Delivered Availability.
56. Delivered Capacity
Delivered Capacity may be lower than:
Source Capacity Available Capacity Usable Capacity
because of pathway or location constraints.
57. Transfer Loss
Some Resource transfer mechanisms create physical losses.
Examples may include:
Electricity transmission loss Water leakage Material loss Energy conversion loss
Where material, the destination capacity should reflect the relevant transfer reality.
58. Loss Attribution Boundary
LAAM may represent Resource loss affecting delivered capacity.
It does not independently determine liability for that loss.
59. Distance
Distance may affect accessibility where it materially changes:
Transfer feasibility Capacity Loss Delivery time Infrastructure requirement
Distance itself is not automatically a Resource constraint.
60. Geographic Constraint
Geography may materially affect Resource accessibility.
Examples may include:
Terrain Water basin boundaries Island systems Remote locations Infrastructure corridors
Specialized domains determine the underlying physical effects.
61. Jurisdictional Boundary
A jurisdictional boundary may affect Resource movement through external governance rules.
LAAM may consume the resulting practical restriction.
It does not determine jurisdictional authority.
Jurisdictional Boundary ≠ Resource Boundary.
62. Administrative Boundary
Administrative boundaries may differ from Resource-system boundaries.
LAAM must follow the actual Resource pathway.
63. Infrastructure Boundary
Resource accessibility may terminate at an infrastructure boundary.
Examples:
Grid edge Pipeline endpoint Network edge Distribution limit
64. Point-of-Connection Capacity
A destination may have limited connection capacity even where upstream Resource capacity is abundant.
65. Destination Intake Capacity
A destination may be unable to receive the full Resource flow.
Examples:
Electrical connection limit Pipeline intake limit Port unloading capacity Network interface capacity
Delivered Pathway Capacity ≠ Destination Intake Capacity.
66. Destination Compatibility
UCCM governs general functional usability.
LAAM may preserve whether the destination connection itself can accept the Resource capacity.
67. Practical Accessibility
Practical Accessibility exists where Resource capacity can physically or technically reach the relevant destination under applicable conditions.
68. Fully Accessible Capacity
Fully Accessible Capacity is the portion capable of reaching the relevant destination without a material unresolved accessibility limitation.
69. Partially Accessible Capacity
Only part of otherwise available Resource capacity may be accessible at the destination.
70. Conditionally Accessible Capacity
Capacity is Conditionally Accessible where practical access depends upon explicit conditions.
71. Temporarily Inaccessible Capacity
Resource may remain available and usable while temporarily inaccessible because of pathway or infrastructure conditions.
72. Inaccessible Capacity
Resource capacity is Inaccessible where sufficient evidence establishes that no applicable pathway currently allows it to reach the relevant destination.
73. Accessibility Unknown
Where evidence is insufficient:
Unknown Accessibility ≠ Inaccessible Resource.
74. Accessibility Evidence-Limited
A Resource pathway may be known but insufficiently evidenced to establish reliable accessible capacity.
The limitation must remain visible.
75. Accessibility Conflict
Credible evidence may support incompatible accessibility states.
The conflict must remain explicit until resolved or bounded.
76. Practical Accessibility vs Access Authorization
This is the fundamental boundary of LAAM.
LAAM asks:
Can the Resource physically or technically reach the destination?
RAGS asks:
May the relevant participant legitimately access the Resource?
Therefore:
Practical Accessibility ≠ Resource Access Authorization.
77. Physical Access vs Governance Access
A Resource may be physically accessible while access is not authorized.
A Resource may also be authorized while physically inaccessible.
These states must remain independent.
78. Accessibility vs Ownership
Physical or technical accessibility does not establish ownership.
Accessible Resource ≠ Owned Resource.
79. Accessibility vs Entitlement
A participant's ability to reach Resource does not establish entitlement to use it.
80. Accessibility vs Allocation
Accessible capacity has not necessarily been allocated.
Accessible Capacity ≠ Allocated Capacity.
81. Accessibility vs Reservation
Capacity may be practically accessible while reserved.
RVCM retains reservation state.
82. Accessibility vs Usability
Resource may be accessible but unusable for the required function.
Likewise, Resource may be technically usable but inaccessible at the required destination.
Accessible ≠ Usable.
83. Accessibility vs Availability
Availability and Accessibility are related but distinct.
RADM establishes Resource Availability.
LAAM establishes whether that Resource can reach the relevant destination.
84. Accessibility vs Demand
Practical accessibility does not establish Demand.
RDGS governs Demand.
85. Accessibility vs Scarcity
Inaccessibility may contribute to local scarcity.
LAAM does not determine Scarcity State.
Local Inaccessibility ≠ Scarcity by definition.
86. Accessibility vs Consumption
Accessible Resource has not necessarily been consumed.
Accessible ≠ Consumed.
87. Accessibility vs Sustainability
A Resource may be easily accessible while its use remains unsustainable.
Accessibility ≠ Sustainability.
88. Accessibility vs Value
Practical accessibility does not determine Resource Value.
89. Accessibility vs Authority
Technical ability to access Resource does not create Governance Authority.
Technical Access Capability ≠ Authority.
90. Temporal Accessibility
Resource pathway accessibility may change through time.
TAVM provides the temporal Availability structure.
LAAM applies the spatial pathway at the relevant time.
91. Temporal-Spatial Alignment
Resource must be accessible at the required location at the relevant time.
Available Somewhere at Time T ≠ Accessible Here at Time T.
92. Pathway Timing
Some Resource pathways introduce delivery delay.
This may materially affect practical accessibility.
93. Delivery Time
Delivery Time represents the interval required for Resource to reach the destination.
For some Resources, this may be nearly instantaneous.
For others, it may require hours, days, weeks, or longer.
94. Immediate Accessibility
Immediate Accessibility exists where Resource capacity can reach or already exists at the relevant destination without material delay.
95. Delayed Accessibility
Resource may be practically accessible only after a delivery or transfer interval.
Eventually Accessible ≠ Immediately Accessible.
96. Accessibility Window
A pathway may be accessible only during defined time windows.
LAAM should preserve the relationship with TAVM.
97. Source-to-Destination Mapping
Each material Source may be mapped to one or more destinations.
Canonical representation:
Source → Pathway → Intermediate Nodes → Destination → Accessible Capacity
98. Multi-Source Destination
A destination may receive Resource from several Sources.
LAAM may consolidate accessible capacity where:
Resource identity is compatible; time aligns; pathways are valid; capacity is not double-counted.
99. Multi-Destination Source
One Source may support several destinations.
Its full capacity must not automatically be attributed independently to each destination.
100. Spatial Double-Counting
LAAM must prevent Resource capacity from being counted multiple times because it appears in:
multiple locations; multiple network views; multiple pathway records; multiple destination claims.
101. Capacity Allocation Boundary
Where one Source can physically support several destinations but not all simultaneously, LAAM records the capacity constraint.
RPAS determines allocation.
102. Accessible Capacity Ceiling
The maximum accessible capacity at a destination may be constrained by:
Source capacity Pathway capacity Intermediate capacity Transfer loss Destination intake capacity Time-specific conditions
103. Accessible Capacity Floor
Where evidence supports a minimum reliably accessible capacity, LAAM may represent it.
104. Accessible Capacity Range
Where exact accessible capacity cannot legitimately be established, LAAM may represent a governed range.
Governed Range ≠ False Precision.
105. Accessibility Bottleneck
The active accessibility bottleneck should be identified where evidence supports it.
Possible bottlenecks include:
Source connection Processing node Transport route Transmission line Distribution system Network link Destination connection
106. Accessibility Constraint Interaction
Multiple spatial or infrastructure constraints may interact.
Their combined effect must follow Resource reality rather than an arbitrary universal formula.
107. Accessibility Change
Accessibility may change even where Resource Availability remains constant.
Examples:
Pipeline failure Grid congestion Network outage Transport route closure New interconnection Infrastructure repair
108. Accessibility Change Event
A material event may include:
Connection loss Connection restoration Route closure Route restoration Transfer-capacity reduction Transfer-capacity expansion Source relocation Destination change Infrastructure failure Infrastructure commissioning
109. Accessibility Reassessment Trigger
LAAM reassessment should occur following material:
RADM Availability change UCCM Usability change RVCM Reservation change TAVM Temporal change Source-location change Destination change Pathway change Infrastructure change Network-topology change Transfer-capacity change New evidence Evidence expiry Accessibility conflict
110. Reassessment Logic
Canonical logic:
Existing Location & Accessibility Profile → New Evidence / Material Change → Accessibility Impact Test → State Retained or Revised → Accessible Capacity Recalculation → Version Update → RACS Profile Reassessment
111. Accessibility Evidence
Accessibility determinations should be supported by evidence appropriate to the Resource pathway.
Evidence may include:
Location data Infrastructure maps Network topology Connection records Transfer-capacity measurements Route status Technical records Operational records Sensor data Delivery records
112. Evidence Provenance
Accessibility evidence should remain traceable to:
Resource Source Location Pathway Destination Measurement or record Time Evidence Source Version where relevant
113. Evidence Freshness
Infrastructure and pathway conditions may change.
Evidence freshness must reflect Resource-system volatility.
Previously Accessible ≠ Currently Accessible.
114. Observed Accessibility
Observed Accessibility is supported by direct evidence that Resource can reach or is reaching the relevant destination.
115. Tested Accessibility
A pathway may be tested for transfer or delivery capability.
Test conditions must remain relevant to actual Resource use.
116. Inferred Accessibility
Accessibility may be inferred from sufficiently established infrastructure and Resource conditions.
The inference basis must remain explicit.
117. Declared Accessibility
An operator may declare that Resource capacity is accessible.
Declared Accessibility ≠ Verified Accessibility.
118. Contracted Delivery Capacity
A contract may establish delivery rights or commitments.
It does not prove physical delivery capacity.
Contracted Delivery ≠ Physical Accessibility.
119. Predicted Accessibility
Future pathway accessibility may be predicted.
Predicted Accessibility ≠ Current Accessibility.
PGA™ retains Prediction Governance.
120. Simulated Accessibility
Infrastructure or Resource pathways may be simulated.
Simulated Accessibility ≠ Observed Accessibility.
SIMULOS® retains Simulation Governance.
121. Assumed Accessibility
Assumed Accessibility must remain explicit.
Accessibility Assumption ≠ Accessibility Evidence.
122. Accessibility Uncertainty
Material uncertainty may concern:
Location Pathway Connection Transfer capacity Route state Destination intake Delivery loss Timing
Uncertainty must remain attached to the relevant accessibility determination.
123. Uncertainty Propagation
Uncertain accessibility must remain visible downstream.
Uncertain Accessibility must not become certain allocable capacity without additional evidence.
124. Accessibility Conflict Resolution
Canonical logic:
**Accessibility Claim A
Accessibility Claim B → Resource Boundary Check → Location Check → Pathway Check → Time Check → Capacity-Basis Check → Evidence Comparison → Resolution or Preserved Conflict**
125. Accessibility Sufficiency
Accessibility is sufficiently established when evidence and spatial representation are adequate for downstream Resource governance.
Possible states:
Accessibility Sufficient
Conditionally Sufficient
Partially Sufficient
Evidence-Limited
Conflicted
Insufficient
Unresolved
126. Accessibility Decision States
At minimum, LAAM should distinguish:
Fully Accessible
Partially Accessible
Conditionally Accessible
Temporarily Inaccessible
Inaccessible
Accessibility Evidence-Limited
Accessibility Conflicted
Accessibility Unknown
Accessibility Unresolved
127. Location & Accessibility Profile
The principal LAAM output is the:
Location & Accessibility Profile
It should establish:
where Resource capacity exists; where it is required; which pathway connects those locations; which infrastructure enables transfer; what pathway capacity exists; what capacity can actually reach the destination; which constraints apply; what evidence supports the determination; what uncertainty remains.
128. Minimum Profile Fields
A minimum Location & Accessibility Profile should support:
Resource ID RADM Profile Reference UCCM Profile Reference RVCM Profile Reference TAVM Profile Reference Source Location Current Resource Location Destination / Point of Use Resource Pathway Intermediate Nodes where material Connection State Transfer Capacity Transfer Loss where material Destination Intake Capacity Accessible Capacity Accessibility State Active Accessibility Constraint Evidence Basis Evidence Time Uncertainty Sufficiency State Version
129. Accessible Capacity Accounting
Where Resource reality permits:
Applicable Resource Capacity → Pathway Capacity → Transfer Loss / Constraints → Destination Intake Capacity → Accessible Capacity
No universal arithmetic formula should be imposed across all Resource types.
130. Spatial Aggregation
Resource capacity across locations may be aggregated only where spatial combination is legitimate for the governance purpose.
131. Spatial Disaggregation
Aggregate Resource capacity must be disaggregated where location materially affects accessibility.
132. Location-Specific Capacity
RACS should preserve location-specific capacity where Resource cannot move freely between locations.
133. Cross-Location Comparability
Two locations with identical Resource quantities may have different practical accessibility because of:
Infrastructure Pathway capacity Network topology Transfer loss Destination capacity Distance Time
Same Resource Quantity ≠ Same Accessible Capacity.
134. Global vs Local Resource Reality
A Resource may be abundant globally while inaccessible locally.
Global Resource Abundance ≠ Local Resource Accessibility.
This distinction is central to Resource Sustainability governance.
135. Regional Capacity
Regional Resource totals must not automatically be treated as capacity available at every point within the region.
136. Network-Wide Capacity
Network-wide capacity may substantially exceed capacity accessible at a particular node.
Network Capacity ≠ Node-Accessible Capacity.
137. Source-to-Use Efficiency Boundary
Transfer losses may reduce delivered capacity.
LAAM may represent those losses where necessary for accessibility.
VEGA™ may separately govern efficiency where the relevant consumption/value relationship falls within its domain.
138. Resource Accessibility Profile Consolidation
LAAM consolidates:
Resource location Source location Destination Pathway
Infrastructure Transfer capacity Temporal alignment Accessibility evidence Uncertainty
into a governed Location & Accessibility Profile.
139. RACS Consolidation Role
LAAM completes the fifth RACS Core Module.
Canonical consolidation:
RADM — Resource Availability Profile
UCCM — Usable Capacity Profile
RVCM — Reserved Capacity Profile
TAVM — Temporal Availability Profile
LAAM — Location & Accessibility Profile
→
RACS — Resource Availability & Capacity Profile
140. Potentially Allocable Capacity
Following RACS consolidation, capacity may be represented as Potentially Allocable only where relevant Availability, Usability, Reservation, Temporal, Location, and Practical Accessibility conditions are sufficiently satisfied.
Potentially Allocable Capacity ≠ Allocated Capacity.
RACS stops before allocation.
141. RACS Capacity Logic
Canonical RACS capacity logic:
Characterized Resource → Available Capacity → Usable Capacity → Reserved / Unreserved Capacity → Temporally Applicable Capacity → Location-Specific Practically Accessible Capacity → Potentially Allocable Capacity
This is a governance sequence, not a universal arithmetic formula.
142. RACS Profile Integrity
The final Resource Availability & Capacity Profile must preserve the distinctions established by all five Core Modules.
A single capacity number should not replace materially relevant:
Availability State Usability State Reservation State Temporal State Accessibility State
143. Downstream Handoff
The completed RACS Resource Availability & Capacity Profile becomes a governed input to later RSGA™ stages.
Canonical architecture flow continues:
Resource Availability & Capacity → Resource Demand Governance → Resource Dependency & Criticality → Resource Access Governance → Resource Prioritization & Allocation
144. Downstream Uncertainty
Any material unresolved uncertainty from RACS must propagate into downstream governance.
RACS completion does not convert unresolved Resource uncertainty into certainty.
145. Failure Conditions
LAAM should not be considered sufficiently completed where:
Source availability is treated as destination accessibility; Resource location is materially unknown; point of use is undefined where location matters; pathway capacity is ignored; transfer bottlenecks are ignored; network-zone constraints are ignored; transport capacity is ignored where material; destination intake capacity is ignored; transfer losses are ignored where material; non-connected Resource is treated as accessible; temporary pathway failure is ignored; multiple locations are aggregated in a misleading way; the same capacity is spatially double-counted; physical accessibility is confused with authorization; ownership is inferred from accessibility; entitlement is inferred from accessibility; contracted delivery is represented as physical accessibility; predicted accessibility is represented as current accessibility; unknown accessibility is represented as inaccessibility; material uncertainty is hidden; stale pathway evidence is treated as current.
146. Governance Requirements
A conforming LAAM implementation must:
1. receive governed outputs from preceding RACS modules;
2. identify relevant Resource location; 3. identify Source location where material; 4. identify destination or point of use; 5. identify relevant Resource pathway; 6. represent intermediate nodes where material; 7. determine connection state; 8. determine pathway availability; 9. determine pathway capacity; 10. identify active transfer bottlenecks; 11. preserve network-zone constraints where relevant; 12. preserve transport constraints where relevant; 13. preserve transfer losses where material; 14. preserve destination intake capacity; 15. determine practically accessible capacity; 16. support partial accessibility; 17. support conditional accessibility; 18. distinguish Unknown from Inaccessible; 19. distinguish practical accessibility from Access authorization; 20. prevent spatial double-counting; 21. preserve Source-to-destination relationships; 22. preserve temporal-spatial alignment; 23. preserve evidence provenance; 24. preserve evidence freshness; 25. distinguish observed, tested, inferred, declared, contracted, predicted, simulated, and assumed accessibility where material; 26. preserve uncertainty; 27. preserve conflict; 28. support reassessment; 29. support versioning; 30. produce a governed Location & Accessibility Profile.
147. Governance Logic
Canonical LAAM logic:
RACS Capacity Inputs → Resource Location → Source Location → Destination / Point of Use → Resource Pathway → Connection State → Intermediate Infrastructure → Transfer Capacity → Active Spatial / Infrastructure Constraints → Transfer Loss where relevant → Destination Intake Capacity → Temporal-Spatial Alignment → Practical Accessibility Determination → Accessible Capacity → Evidence & Uncertainty → Sufficiency → Location & Accessibility Profile → RACS Resource Availability & Capacity Profile
Where evidence is insufficient:
Accessibility Question → Evidence Gap → Minimum Evidence Requirement → Evidence Acquisition → Accessibility Reassessment
Where conditions change:
Existing Accessibility State → Material Spatial / Infrastructure Change → Accessibility Impact Test → Revised Accessible Capacity → Version Update → RACS Profile Reassessment
148. Governance Outputs
LAAM may produce:
Location & Accessibility Profile Resource Location State Source Location State Destination State Resource Pathway State Connection State Pathway Availability State Transfer Capacity State Transfer Bottleneck State Delivery Capacity State Destination Intake State Accessible Capacity Accessibility State Accessibility Evidence State Accessibility Uncertainty State Accessibility Conflict State Accessibility Sufficiency State Accessibility Version Reassessment Trigger RACS Consolidation State
149. Minimum Implementation Framework
A minimum operational LAAM implementation must contain at least eight governed layers.
Layer 1 — RACS Capacity Input
Receive:
Resource ID Availability Profile Usable Capacity Profile Reserved Capacity Profile Temporal Availability Profile
Layer 2 — Spatial Definition
Identify:
Resource Location Source Location Destination / Point of Use
Layer 3 — Resource Pathway
Represent:
Pathway Intermediate Nodes Connection State
Layer 4 — Transfer Infrastructure
Assess:
Infrastructure availability Transfer Capacity Network / Transport constraints Transfer loss where material
Layer 5 — Destination Capacity
Assess:
Destination connection Destination intake capacity Relevant technical spatial constraints
Layer 6 — Temporal-Spatial Alignment
Determine whether Resource and pathway capacity coexist:
at the required location at the required time
Layer 7 — Accessibility Evidence & Decision
Preserve:
Evidence Freshness Uncertainty Conflict Accessibility Decision State Accessible Capacity
Layer 8 — Governed Output & RACS Consolidation
Produce:
Location & Accessibility Profile Version Known limitations Reassessment triggers RACS Resource Availability & Capacity Profile input
Minimum machine-readable logic:
Resource → RACS Capacity Inputs → Source Location → Resource Location → Destination → Pathway[] → Connection[] → Transfer Capacity[] → Constraints[] → Temporal Alignment → Evidence[] → Uncertainty[] → Accessible Capacity → Accessibility State → Location & Accessibility Profile
150. Minimum Decision States
At minimum:
Fully Accessible
Partially Accessible
Conditionally Accessible
Temporarily Inaccessible
Inaccessible
Accessibility Evidence-Limited
Accessibility Conflicted
Accessibility Unknown
Accessibility Unresolved
151. Minimum Evidence Path
Where practical accessibility cannot be sufficiently established:
Accessibility Unresolved → Material Missing Evidence → Minimum Evidence Requirement → Evidence Acquisition → Pathway / Capacity Reassessment → Updated Location & Accessibility Profile
The objective is sufficient evidence of Resource reachability, not unlimited infrastructure mapping.
152. Minimum Reassessment Framework
At minimum:
Current Location & Accessibility Profile → New Evidence / Material Change → Accessibility Impact Test → Capacity Retained or Revised → Profile Version Update → RACS Resource Availability & Capacity Profile Reassessment
153. Use Case 1 — Electricity for an AI Data Center
A regional grid contains:
500 MW of available generation capacity.
UCCM establishes that the capacity is technically usable.
TAVM establishes that the capacity is available during the required operating period.
The AI data center, however, is connected through infrastructure supporting only:
120 MW at the relevant connection point.
A transmission constraint further reduces currently deliverable capacity to:
95 MW.
LAAM therefore prevents the system from treating:
500 MW regional availability
as:
500 MW accessible data-center capacity.
The relevant RACS output may establish:
Regional Available Capacity: 500 MW
Connection Capacity: 120 MW
Currently Accessible Capacity: 95 MW
subject to reservation and other applicable RACS conditions.
LAAM does not decide whether the data center is entitled to the 95 MW.
Electricity existing in the grid is not the same as electricity reachable at a specific connection point.
154. Use Case 2 — Water for Industrial Cooling
A regional Resource assessment establishes:
80,000 m³/day of usable water capacity.
The industrial facility requires:
30,000 m³/day.
However:
one Source is outside the connected distribution zone; one pipeline is temporarily capacity-constrained; the facility intake supports a maximum of 24,000 m³/day.
LAAM maps:
Sources → Treatment → Pipelines → Distribution → Facility Intake
and determines the capacity that can actually reach the facility.
The existence of 80,000 m³/day at regional level therefore does not establish 80,000 m³/day of practical accessibility at the facility.
LAAM does not determine whether the facility should receive the accessible Resource.
Resource abundance somewhere does not establish Resource accessibility where it is needed.
155. Critical Distinctions
Resource Availability ≠ Resource Accessibility
Resource Origin ≠ Resource Source ≠ Current Resource Location
Global Availability ≠ Local Availability
Available at Source ≠ Accessible at Destination
Source Capacity ≠ Transfer Capacity
Source Availability ≠ Delivered Availability
Connected ≠ Sufficiently Accessible
Delivered Pathway Capacity ≠ Destination Intake Capacity
Accessible ≠ Usable
Practical Accessibility ≠ Resource Access Authorization
Physical Access ≠ Governance Access
Accessible Resource ≠ Owned Resource
Accessibility ≠ Entitlement
Accessible Capacity ≠ Allocated Capacity
Accessible ≠ Consumed
Accessibility ≠ Sustainability
Technical Access Capability ≠ Authority
Available Somewhere at Time T ≠ Accessible Here at Time T
Eventually Accessible ≠ Immediately Accessible
Contracted Delivery ≠ Physical Accessibility
Predicted Accessibility ≠ Current Accessibility
Simulated Accessibility ≠ Observed Accessibility
Declared Accessibility ≠ Verified Accessibility
Accessibility Assumption ≠ Accessibility Evidence
Unknown Accessibility ≠ Inaccessible Resource
Same Resource Quantity ≠ Same Accessible Capacity
Global Resource Abundance ≠ Local Resource Accessibility
Network Capacity ≠ Node-Accessible Capacity
Potentially Allocable Capacity ≠ Allocated Capacity
156. Cross-Architecture Boundary
LAAM governs practical Resource accessibility within RACS.
It does not govern general:
Governance Authority Legal entitlement Ownership Participant eligibility Access permission Allocation authority Logistics policy Liability
RAGS governs Resource Access Governance.
RPAS governs Resource Prioritization & Allocation.
GOA™ retains Governance Authority.
ORA™ retains general Operational Reality.
PGA™ retains Prediction Governance.
SIMULOS® retains Simulation Governance.
Specialized Resource and infrastructure domains retain the underlying physics, engineering, network, transport, hydrological, electrical, compute, and other domain mechanisms.
157. 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 grid system may determine transmission capacity.
A water system may determine pipeline flow.
A logistics system may determine transport availability.
A network system may determine connectivity.
LAAM consumes those outputs to determine practical Resource accessibility.
It does not absorb the mechanisms that produced them.
158. Canonical Boundary
LAAM governs where Resource capacity exists, how it is connected to the relevant destination, which physical, technical, infrastructural, network, transport, and spatial conditions determine its reachability, and what capacity can actually become practically accessible at the relevant point of use.
It does not determine ownership, entitlement, Access authorization, priority, allocation, consumption, scarcity response, resilience, or sustainability.
Its governed output is the Location & Accessibility Profile , which completes the Core Module inputs required for the RACS Resource Availability & Capacity Profile .
159. Canonical Closing Statement
A Resource is not practically available to a system merely because it exists somewhere within a larger Resource network.
LAAM establishes whether Resource capacity can actually reach the place where it matters.