RABM — Resource Allocation Basis Module
Architecture: RSGA™ — Resource Sustainability Governance Architecture
Parent Standard: Resource Prioritization & Allocation Standard (RPAS)
Category: Governance & Enforcement
Subcategory: Resource Governance
Type: Core Module
Governed Space: Resource Allocation Basis Governance
Module ID: RSGA-RPAS-RABM-02
Origin ID: OOF-RSGA-RPAS-RABM
Version: 1.0
Status: Draft Module
Effective Date: 6 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
RABM — Resource Allocation Basis Module governs how the legitimate basis, authority, applicable rules, allocable Resource context, Priority inputs, constraints, boundaries, and decision conditions required to make a Resource Allocation decision are established, evidenced, validated, and maintained before Resource capacity is assigned to competing legitimate claims.
RABM establishes the governance basis upon which Allocation may legitimately occur.
Its foundational distinction is:
Resource Priority ≠ Allocation Basis.
And its operational boundary is:
Allocation Basis ≠ Resource Allocation.
2. Operational Role
RPDM determines the relative Resource Priority of competing legitimate claims.
That Priority alone is not sufficient to produce an Allocation.
Before Resource capacity can be assigned, governance must establish:
what capacity is allocable; who has authority to allocate it; which Allocation rules apply; which Resource claims are included; which constraints bind the decision; which minimum and maximum boundaries apply; which time and Source boundaries apply; which evidence supports the decision context.
RABM establishes this Allocation Basis.
Downstream Allocation mechanisms use that governed basis to determine the actual Resource assignment.
3. Operational Question
What legitimate authority, Resource capacity, Priority evidence, Allocation rules, constraints, boundaries, conditions, and supporting evidence form the valid basis upon which the relevant Resource may be allocated among competing legitimate claims?
4. Position in RPAS Governance
Canonical progression:
Legitimate Competing Claims → Resource Priority Determination → Allocation Basis → Allocation Limits & Boundaries → Resource Allocation → Reallocation / Balancing → Reassessment
RABM governs:
Priority & Resource Context → Allocation Basis
It does not itself assign the Resource.
5. Governed Space
RABM governs:
Resource Allocation Basis Governance
This space concerns the legitimacy and completeness of the decision foundation required before constrained Resource capacity is distributed.
6. Governed Object
The primary Governed Object is:
A Resource Allocation Basis governing a defined Allocation decision or Allocation context.
Canonical relationship:
**Allocable Resource Capacity
Allocation Authority Legitimate Claims Resource Priority Evidence Applicable Allocation Rules Constraints Boundaries Conditions Evidence → Resource Allocation Basis**
7. Scope
RABM governs:
Allocation Basis identification; Allocation Authority; authority origin; delegated Allocation Authority; allocable Resource context; Allocation pool definition; Priority input validation; claim inclusion; claim exclusion basis; Allocation rules; Allocation criteria; minimum Allocation boundaries;
maximum Allocation boundaries; quantity boundaries; capacity boundaries; rate boundaries; temporal boundaries; spatial boundaries; Resource Source boundaries; purpose boundaries; reservation constraints; rights constraints; Access constraints; technical feasibility constraints; continuity constraints; Scarcity-related constraints where applicable; Allocation conditions; Allocation Basis evidence; conflict; uncertainty; validity; expiration; reassessment; versioning.
RABM does not independently:
determine Resource Demand; determine Dependency or Criticality; determine Resource Priority; create Resource rights; authorize Resource Access; determine physical Resource Availability; assign final Resource quantities or capacity; implement Allocation technically; govern Consumption or Utilization; govern Scarcity as a system state; determine long-term Sustainability.
8. Allocation Basis Principle
A Resource Allocation decision should not begin with the question:
Who receives the Resource?
It should first establish:
On what legitimate basis may this Resource be allocated?
Without a governed Allocation Basis, Resource distribution risks becoming arbitrary, opaque, technically determined, historically inherited, or dominated by uncontrolled Resource capture.
9. Allocation Basis Components
A complete Allocation Basis may include:
Resource identity; Resource Source; allocable capacity; Allocation Authority; eligible Allocation claims; Priority evidence; Allocation rules; rights constraints;
Access constraints; reservation constraints; minimum and maximum boundaries; technical constraints; temporal conditions; spatial conditions; purpose conditions; evidence; uncertainty.
Not every component is required in every Resource context.
10. Allocation Context
Every Allocation Basis should identify the context within which Allocation is being determined.
This may include:
Resource; Resource Source; location; Allocation period; Resource pool; participating claims; governance state.
11. Allocation Pool
An Allocation Pool is the defined Resource capacity from which competing claims may receive Allocation.
12. Allocation Pool Boundary
The Allocation Pool should remain distinct from total Resource existence or total physical capacity.
Total Resource Capacity ≠ Allocation Pool.
13. Allocable Capacity
RABM should establish or consume the relevant Allocable Capacity for the Allocation context.
Allocable Capacity is the Resource capacity that may legitimately enter the Allocation decision.
14. Availability Boundary
Available Capacity ≠ Allocable Capacity.
Available Resource may be excluded from Allocation because it is:
reserved; protected; technically inaccessible for the relevant claims; committed; outside authority; outside the relevant Source; outside the relevant time horizon; otherwise constrained.
15. Usable Capacity Boundary
Usable Capacity ≠ Allocable Capacity.
A Resource may be physically usable but unavailable for legitimate Allocation within the relevant governance context.
16. Accessible Capacity Boundary
Accessible Capacity ≠ Allocable Capacity.
Technical or practical accessibility does not itself establish Allocation eligibility.
17. Reserved Capacity
RABM should identify capacity that is already reserved or protected where that reservation affects the Allocation Pool.
18. Reservation Boundary
Reserved Capacity ≠ Freely Allocable Capacity.
Physical non-use does not eliminate a legitimate reservation.
19. Allocation Authority
Every material Allocation Basis should identify the authority under which Resource capacity may be distributed.
20. Authority Origin
Where relevant, Allocation Authority should remain traceable through:
Authority: Origin → Delegation where applicable → Allocation Authority → Allocation Basis
21. Delegated Allocation Authority
Allocation Authority may be delegated.
The delegation should preserve:
delegating authority; delegate; Resource; scope; duration; limits; conditions.
22. Authority Scope
The Allocation Basis should remain within the Resource and decision scope of the competent Allocation Authority.
23. Authority Boundary
Technical Control of a Resource ≠ Allocation Authority.
The actor capable of distributing a Resource operationally is not automatically authorized to determine its Allocation.
24. Algorithmic Authority Boundary
An algorithm may implement Allocation rules.
It does not become the origin of Allocation Authority.
Allocation Algorithm ≠ Allocation Authority.
25. Legitimate Claims
RABM should identify which claims legitimately enter the Allocation decision.
Claims should be supported by sufficient upstream governance evidence.
26. Claim Inclusion
Claim inclusion may depend upon:
validated Demand; relevant Resource Dependency; legitimate Access; rights where applicable; purpose; Allocation period; Resource Source; other competent conditions.
27. Claim Exclusion
A claim may be excluded from a specific Allocation context where it falls outside:
the relevant Resource; Resource Source; time period; location; Access scope; rights scope; Allocation Authority; other applicable boundary.
28. Exclusion Boundary
Claim exclusion should have a governance basis.
Claim Exclusion ≠ Arbitrary Denial.
29. Priority Input
RABM consumes Resource Priority determinations from RPDM.
Priority is an Allocation input.
It is not the complete Allocation Basis.
30. Priority Boundary
Highest Priority ≠ Unlimited Allocation.
Allocation remains constrained by:
Demand; capacity; minimum requirements; maximum limits; rights; Access; Resource conditions; other competing claims.
31. Equal Priority
Equal-Priority claims may require an Allocation rule capable of resolving distribution without inventing false Priority differences.
32. Priority Validity
RABM should confirm that the Priority evidence used for Allocation remains valid for the relevant:
Resource; claims; time; context.
33. Allocation Rule
An Allocation Rule defines how governed inputs are translated into Resource distribution.
34. Allocation Rule Types
Depending upon the Resource context, rules may be:
Priority-sequential; proportional; minimum-needs-first; threshold-based; tiered; rotational; reservation-based; optimization-based; market-mediated where legitimately governed; hybrid.
RABM does not prescribe one universal Allocation rule.
35. Rule Legitimacy
An Allocation Rule should originate from competent governance authority or an authorized methodology.
36. Rule Applicability
A legitimate rule may still be inappropriate for a particular Resource or Allocation context.
RABM should establish that the rule applies to the relevant decision.
37. Rule Transparency
The material logic of the Allocation Rule should remain sufficiently explainable.
38. Rule Consistency
Equivalent Allocation conditions should not receive materially different treatment without a legitimate reason.
39. Rule Exception
Where an Allocation Rule permits exceptions, the exception conditions and authority should remain explicit.
40. Allocation Criteria vs Priority Criteria
Priority Criteria determine relative precedence.
Allocation Criteria determine how Resource capacity is distributed once Priority and other constraints are known.
Priority Criteria ≠ Allocation Criteria.
41. Minimum Allocation Boundary
Some claims may require a minimum Resource level to remain functionally meaningful.
Where applicable, RABM should preserve that minimum as an Allocation boundary.
42. Minimum Boundary Source
Minimum Allocation may originate from:
functional requirements; safety requirements; continuity requirements; technical thresholds; rights conditions; other competent evidence.
43. Minimum Boundary Distinction
Minimum Functional Requirement ≠ Guaranteed Minimum Allocation.
A minimum requirement identifies what is needed for function.
Whether that amount can or must be allocated depends upon the broader Allocation Basis.
44. Maximum Allocation Boundary
A claim may be subject to a maximum Allocation.
Maximum limits may arise from:
validated Demand; Access authorization; rights; technical capacity; Resource policy; Scarcity conditions; other legitimate constraints.
45. Maximum Boundary Principle
High Priority ≠ Permission to Exceed Maximum Allocation Boundaries.
46. Demand Boundary
Allocation should not ordinarily exceed validated Demand unless a competent Resource mechanism establishes a legitimate reason.
47. Access Boundary
Allocation should remain within legitimate Resource Access boundaries.
Allocation ≠ Expansion of Access Authority.
48. Rights Boundary
Allocation should respect applicable Resource rights without assuming that every right establishes unlimited Allocation.
49. Resource Source Boundary
Where Access or rights apply only to a defined Resource Source, the Allocation Basis should preserve that Source boundary.
Right to Source A ≠ Allocation from Source B.
50. Quantity Boundary
RABM may establish the range of Resource quantity that may legitimately be allocated.
51. Capacity Boundary
For capacity-based Resources, the Allocation Basis may establish:
minimum capacity; maximum capacity; reserved capacity;
shared capacity; available allocable capacity.
52. Rate Boundary
Allocation may be limited by:
flow rate; power draw; bandwidth; processing rate; delivery rate; other throughput constraint.
53. Temporal Boundary
The Allocation Basis should establish the relevant time horizon.
This may include:
start; end; duration; schedule; rotation; renewal point.
54. Temporal Validity
An Allocation Basis valid for one period should not automatically govern another.
Allocation Basis at Time A ≠ Allocation Basis at Time B.
55. Spatial Boundary
Allocation may be limited to a defined:
facility; region; delivery point; network node; infrastructure segment; other location.
56. Purpose Boundary
Where Resource Access or rights are purpose-specific, Allocation should preserve that purpose boundary.
57. Technical Feasibility
The Allocation Basis should preserve relevant physical or technical constraints.
A governance preference cannot make an impossible Resource distribution feasible.
58. Feasibility Boundary
Governance Preference ≠ Physical Feasibility.
59. Delivery Constraint
Resource delivery infrastructure may constrain Allocation even where aggregate capacity appears sufficient.
Examples include:
grid limits; pipeline limits; network bottlenecks; cooling distribution; compute topology; storage interface limits.
60. Local vs Aggregate Capacity
Aggregate Resource capacity may exceed total Demand while a local constraint still prevents a proposed Allocation.
Aggregate Capacity Sufficiency ≠ Local Allocation Feasibility.
61. Concurrency Constraint
Claims that require Resource simultaneously may create different Allocation conditions from claims that can operate sequentially.
RDGS concurrent-demand evidence may therefore affect the Allocation Basis.
62. Temporal Flexibility
Where claims can shift Resource use across time, the Allocation Basis may preserve that flexibility for downstream Allocation.
63. Substitution Relevance
Where viable substitutes exist, Allocation rules may legitimately account for them if the governing framework permits.
RSFS may provide relevant evidence.
64. Continuity Constraint
Some Resource capacity may need to remain protected to preserve continuity.
This constraint should be explicit.
65. Resilience Constraint
Resource Allocation may need to preserve reserve capacity or distribution diversity for system resilience.
RIRS may provide relevant evidence.
66. Sustainability Constraint
Long-term sustainability constraints may limit the Resource quantity that may legitimately enter Allocation even where greater short-term extraction is physically possible.
67. Sustainability Boundary
Physically Extractable Capacity ≠ Sustainably Allocable Capacity.
68. Scarcity Relevance
Scarcity may alter:
Allocation Pool; Allocation rules; minimum boundaries; maximum boundaries; reservation requirements; decision urgency.
RSCS governs the Scarcity state itself.
RABM governs its relevance to the Allocation Basis.
69. Emergency Context
Emergency conditions may activate a different legitimate Allocation Basis.
The emergency basis should remain explicit.
70. Emergency Boundary
Emergency Context ≠ Unlimited Allocation Authority.
71. Market Mechanisms
Market mechanisms may form part of an Allocation Basis where legitimately established.
Examples may include:
pricing; auction; contractual capacity; market-clearing rules.
72. Market Boundary
Market Outcome ≠ Universal Governance Legitimacy.
Market allocation remains subject to the applicable rights, Access, safety, continuity, authority, and other governance constraints.
73. Value Relevance
Validated Value may form part of the Allocation Basis where competent governance recognizes it.
VEGA™ may provide relevant evidence.
74. Value Boundary
Validated Value ≠ Allocation Authority.
High Value ≠ Unlimited Allocation.
75. Fairness Basis
Where fairness is an explicit Allocation objective, RABM should establish what fairness means in that governance context.
Possible definitions include:
equal distribution; proportional distribution; need-based distribution; rights-based distribution; minimum-needs protection; other governed approach.
76. Fairness Boundary
Fairness Claim ≠ Defined Fairness Rule.
The applicable fairness principle should be explicit.
77. Optimization Basis
Optimization may be used within the Allocation Basis.
The objective function and constraints should remain governed.
78. Optimization Boundary
Optimization Objective ≠ Governance Authority.
Optimization may select among legitimate possibilities.
It must not silently redefine rights, Priority, Access, or mandatory constraints.
79. Multi-Objective Allocation Basis
Some Allocation contexts must balance:
continuity; safety; efficiency; Value; fairness; resilience; sustainability; other legitimate objectives.
80. Objective Conflict
Where legitimate objectives conflict, RABM should preserve the conflict rather than conceal it within an opaque decision function.
81. Allocation Condition
An Allocation Basis may specify conditions under which an Allocation remains valid.
Examples include:
minimum Resource Availability; emergency state; operational state; evidence validity; time window; Source availability.
82. Conditional Basis
Where a condition fails, the Allocation Basis may require reassessment before further Allocation.
83. Oversubscription Basis
Some Resource systems may permit nominal allocations exceeding simultaneous physical capacity.
Where permitted, RABM should establish the legitimate oversubscription basis.
84. Oversubscription Conditions
Oversubscription may require:
non-concurrent use assumptions; probabilistic demand evidence; control mechanisms; fallback capacity; defined failure handling; monitoring.
85. Oversubscription Boundary
Technical Oversubscription Capability ≠ Legitimate Oversubscription Basis.
86. Allocation Basis State
RABM should represent whether the current Allocation Basis is sufficiently established for Allocation to proceed.
87. Minimum Allocation Basis States
At minimum:
Allocation Basis Established
Allocation Basis Conditionally Established
Allocation Basis Incomplete
Allocation Basis Evidence-Limited
Allocation Basis Conflicted
Allocation Basis Unknown
Allocation Basis Unresolved
Allocation Basis Expired
Allocation Basis Reassessment Required
88. Allocation Basis Established
The relevant authority, Resource context, claims, Priority evidence, rules, constraints, and evidence are sufficiently established for Allocation.
89. Allocation Basis Conditionally Established
Allocation may proceed only while defined conditions remain satisfied.
90. Allocation Basis Incomplete
One or more required Allocation Basis components are absent.
91. Allocation Basis Evidence-Limited
Relevant evidence exists but supports only limited-confidence establishment of the Allocation Basis.
92. Allocation Basis Conflicted
Credible evidence or governance rules support materially incompatible Allocation Bases.
93. Allocation Basis Unknown
Available evidence cannot establish the relevant Allocation Basis.
94. Allocation Basis Unresolved
Relevant evidence exists, but the Allocation Basis cannot yet be finalized.
95. Allocation Basis Expired
The Allocation Basis is no longer valid for the current Resource decision context.
96. Allocation Basis Reassessment Required
Material changes require the current Allocation Basis to be reassessed.
97. Evidence Basis
RABM should preserve evidence supporting:
Allocable Capacity; Allocation Authority; claim inclusion; Priority inputs; Allocation rules; constraints; boundaries; conditions.
98. Evidence Provenance
Material evidence should preserve where relevant:
source; time; Resource; claim; authority; rule; constraint; version.
99. Evidence Sufficiency
Evidence is sufficient when it supports establishment of the Allocation Basis required for the relevant Allocation decision.
100. Evidence Freshness
The Allocation Basis should rely upon evidence sufficiently current for the Allocation horizon.
101. Basis Conflict
Conflict may arise where:
authorities disagree; Allocation rules conflict; capacity evidence conflicts; rights conflict with proposed Allocation rules; Priority evidence conflicts; reservation states conflict; technical feasibility evidence conflicts.
102. Conflict Preservation
Material conflict should remain explicit until resolved by competent governance.
103. Basis Uncertainty
Uncertainty may concern:
capacity; authority; claims; Priority; rules; rights; Access; technical feasibility; future conditions.
104. Uncertainty Principle
Uncertain Allocation Basis ≠ Certain Allocation Foundation.
Material uncertainty should propagate downstream.
105. Allocation Basis Validity
An Allocation Basis should be valid only for the Resource context for which it was established.
106. Validity Dimensions
Validity may be bounded by:
Resource; Source; claims; authority; location; time; operational state; Scarcity state; emergency state.
107. Basis Reuse
A prior Allocation Basis may be reused only where its material assumptions, authority, Resource context, rules, and constraints remain valid.
108. Historical Basis Boundary
Historical Allocation Basis ≠ Current Allocation Basis.
109. Basis Reassessment
RABM should reassess the Allocation Basis when material changes can affect its validity.
110. Reassessment Triggers
Triggers may include:
Resource Availability change; Allocable Capacity change; reservation change; new claim; claim removal; Priority change; rights change; Access change; Allocation Authority change; rule change; technical constraint change; Scarcity change; emergency change; evidence conflict.
111. Targeted Reassessment
Where only one Allocation Basis component changes, RABM should reassess the affected dimensions and their dependencies.
112. Full Basis Reassessment
A full reassessment may be required where:
Allocation Authority changes fundamentally; Resource pool changes materially; Allocation rules change; multiple claims change; Priority framework changes; evidence integrity becomes unreliable.
113. Allocation Basis Traceability
Canonical traceability:
Allocation Basis → Allocation Authority → Allocation Pool → Legitimate Claims → Resource Priority Profiles → Allocation Rules → Constraints → Conditions → Evidence
114. Allocation Basis Explainability
A governed system should be able to explain:
what Resource may be allocated; how much is allocable; which claims participate; which claims do not; which Priority evidence applies; which rules govern distribution; which constraints bind the decision; who has authority to allocate; for what period the basis remains valid.
115. Allocation Basis Versioning
Material changes should create a new Allocation Basis version where required for traceability.
116. Resource Allocation Basis Profile
The principal RABM output is the:
Resource Allocation Basis Profile
It represents the governed foundation upon which a Resource Allocation decision may legitimately proceed.
117. Minimum Resource Allocation Basis Profile Fields
At minimum:
Allocation Basis ID
Resource ID
Resource Source where relevant
Allocation Pool ID
Allocation Authority
Authority: Origin
Authority: Scope
Allocation Period
Available Capacity Reference
Allocable Capacity
Reserved Capacity Reference where relevant
Included Claim IDs
Excluded Claim IDs and Basis where relevant
Resource Priority Profile References
Allocation Rule
Allocation Criteria
Minimum Allocation Boundaries where relevant
Maximum Allocation Boundaries where relevant
Quantity / Capacity / Rate Constraints
Temporal Boundary
Spatial Boundary where relevant
Purpose Boundary where relevant
Rights Constraints
Access Constraints
Technical Constraints
Continuity / Resilience Constraints where relevant
Scarcity / Emergency Context where relevant
Allocation Conditions
Allocation Basis State
Evidence Basis
Evidence Sufficiency
Conflict State
Uncertainty
Effective Time
Expiration / Reassessment Point
Version:
118. Minimum Implementation Framework
A minimum operational RABM implementation should contain eight governed layers.
Layer 1 — Allocation Context
Establish:
Resource Resource Source Allocation Period Allocation Pool
Layer 2 — Authority
Establish:
Authority: Origin Allocation Authority Delegation Authority Scope
Layer 3 — Claims & Priority Inputs
Establish:
Legitimate Claims Claim Inclusion / Exclusion Resource Priority Profiles
Layer 4 — Allocation Rules
Establish:
Allocation Rule Allocation Criteria Exceptions Applicable Objectives
Layer 5 — Constraints & Boundaries
Establish:
Allocable Capacity Reservations Minimum / Maximum Boundaries Rights Access Technical Temporal Spatial Purpose constraints
Layer 6 — Basis Validation
Evaluate:
rule applicability; authority validity; capacity feasibility; evidence sufficiency; conflict; uncertainty.
Layer 7 — Validity & Reassessment
Establish:
effective time; expiration; conditions; reassessment triggers; version.
Layer 8 — Governed Output
Produce:
Resource Allocation Basis Profile
Canonical machine-readable logic:
Allocation Context → Authority → Claims & Priority → Allocation Rules → Constraints & Boundaries → Evidence Validation → Allocation Basis State → Resource Allocation Basis Profile
119. Minimum Decision States
RABM must support at least:
Allocation Basis Established
Allocation Basis Conditionally Established
Allocation Basis Incomplete
Allocation Basis Evidence-Limited
Allocation Basis Conflicted
Allocation Basis Unknown
Allocation Basis Unresolved
Allocation Basis Expired
Allocation Basis Reassessment Required
120. Minimum Evidence Path
Where the Allocation Basis cannot be sufficiently established:
Allocation Basis Unresolved → Material Basis Gap → Affected Basis Component → Minimum Evidence Requirement → Evidence Acquisition / Verification → Basis Reassessment → Allocation Basis Redetermination → Updated Resource Allocation Basis Profile
121. Minimum Reassessment Framework
At minimum:
Current Resource Allocation Basis Profile → Material Change → Materiality Test → Affected Basis Component → Evidence Refresh → Targeted / Full Reassessment → Basis Confirmation / Modification / Expiration → Profile Update → Version Update
122. Governance Requirements
A conforming RABM implementation must:
1. identify the Resource; 2. identify the relevant Resource Source where applicable; 3. establish the Allocation context; 4. establish the Allocation Pool; 5. distinguish total capacity from Allocable Capacity; 6. preserve reserved capacity; 7. identify Allocation Authority; 8. preserve Authority Origin; 9. preserve delegated authority where applicable; 10. validate Authority Scope; 11. identify legitimate participating claims; 12. establish claim inclusion; 13. preserve claim-exclusion basis where applicable; 14. consume current Resource Priority evidence; 15. validate Priority applicability; 16. identify the Allocation Rule; 17. establish rule legitimacy; 18. establish rule applicability; 19. preserve rule exceptions where applicable; 20. distinguish Priority Criteria from Allocation Criteria; 21. establish minimum Allocation boundaries where relevant; 22. establish maximum Allocation boundaries where relevant; 23. preserve validated Demand boundaries;
24. preserve Resource Access boundaries; 25. preserve Resource rights constraints where applicable; 26. preserve Resource Source boundaries; 27. preserve quantity constraints; 28. preserve capacity constraints; 29. preserve rate constraints; 30. preserve temporal boundaries; 31. preserve spatial boundaries where relevant; 32. preserve purpose boundaries where relevant; 33. preserve technical feasibility constraints; 34. preserve local delivery constraints where relevant; 35. preserve concurrency constraints where relevant; 36. preserve continuity constraints where relevant; 37. preserve resilience constraints where relevant; 38. preserve sustainability constraints where applicable; 39. preserve Scarcity context where relevant; 40. preserve emergency context where relevant; 41. govern market mechanisms where applicable; 42. govern optimization objectives where applicable; 43. preserve fairness definitions where applicable; 44. govern oversubscription basis where permitted; 45. establish Allocation Basis validity; 46. preserve evidence provenance; 47. determine evidence sufficiency; 48. preserve material conflict; 49. preserve material uncertainty; 50. support reassessment; 51. support versioning; 52. preserve Allocation Basis traceability; 53. produce a Resource Allocation Basis Profile.
123. Governance Logic
Canonical RABM logic:
Resource & Allocation Context → Allocation Pool → Allocable Capacity → Allocation Authority → Legitimate Claims → Resource Priority Profiles → Allocation Rule → Allocation Criteria → Rights / Access / Reservation / Technical Constraints → Temporal / Spatial / Purpose Boundaries → Evidence Validation → Allocation Basis State → Resource Allocation Basis Profile
Only after that basis is sufficiently established should downstream Resource Allocation proceed.
124. Governance Outputs
RABM may produce:
Resource Allocation Basis Profile
Allocation Pool
Allocable Capacity
Allocation Authority State
Claim Inclusion Set
Claim Exclusion Set
Applicable Priority Input Set
Allocation Rule
Allocation Criteria
Minimum Allocation Boundary
Maximum Allocation Boundary
Rights Constraint Set
Access Constraint Set
Reservation Constraint Set
Technical Constraint Set
Temporal Boundary
Spatial Boundary
Purpose Boundary
Scarcity / Emergency Context
Allocation Basis State
Evidence Sufficiency State
Conflict State
Uncertainty
Reassessment Trigger
Version:
125. Failure Conditions
RABM should not be considered sufficiently completed where:
total Resource capacity is treated as the Allocation Pool; available capacity is treated automatically as Allocable Capacity; reserved capacity is treated as freely allocable; Allocation Authority is absent; technical control is treated as Allocation Authority; algorithmic execution is treated as Authority Origin; claims are included without sufficient governance basis; claims are excluded arbitrarily; Priority is treated as the complete Allocation Basis; highest Priority is treated as unlimited entitlement; Priority Criteria are confused with Allocation Criteria; Allocation rules are hidden; Allocation rules lack legitimate basis; minimum functional requirement is treated automatically as guaranteed Allocation; maximum boundaries are ignored; Allocation expands Access Authority; Resource Source boundaries are ignored; technical feasibility is ignored; aggregate capacity is treated as proof of local feasibility; continuity or reservation constraints are omitted;
market outcome is treated as universal governance legitimacy; Value is treated as Allocation Authority; fairness is invoked without defining the applicable fairness rule; optimization silently overrides rights or mandatory constraints; technical oversubscription capability is treated as legitimate oversubscription authority; historical Allocation Basis is treated automatically as current; material conflict is hidden; material uncertainty is suppressed; material changes occur without reassessment.
126. Use Case 1 — AI Data Center GPU Allocation Basis
A data center has:
2,000 GPUs physically installed
but only:
1,500 GPUs available for the relevant operating period.
Of those:
200 GPUs are reserved for infrastructure resilience and emergency workloads.
The Allocation Pool is therefore not automatically 2,000 or even 1,500 GPUs.
RABM establishes the relevant allocable capacity and consumes RPDM Priority Profiles for:
real-time safety workloads; production inference; model training; experimental research.
It then establishes:
Allocation Authority; participating claims; Priority inputs; minimum functional GPU requirements; maximum authorized GPU limits; time boundaries; technical topology constraints; reservation requirements; applicable Allocation Rule.
The resulting Resource Allocation Basis Profile establishes the legitimate foundation for GPU distribution.
RABM does not decide the final number of GPUs assigned to each workload.
127. Use Case 2 — Regional Water Allocation Basis
A regional water system has a defined daily usable supply.
Part of that capacity is:
reserved for emergency services; protected for minimum network operation; unavailable through specific local delivery constraints.
Legitimate claims include:
household supply; healthcare;
agriculture; industrial production.
RPDM has established their Resource Priority Profiles.
RABM determines:
which water capacity is actually allocable; which authority may distribute it; which claims participate; which rights and Access limits apply; which minimum supply boundaries must be preserved; which Source and location constraints apply; which Allocation Rule governs distribution; how long the Allocation Basis remains valid.
The resulting Allocation Basis allows downstream Allocation to occur without treating total physical water availability as freely distributable capacity.
128. Critical Distinctions
Resource Priority ≠ Allocation Basis
Allocation Basis ≠ Resource Allocation
Total Resource Capacity ≠ Allocation Pool
Available Capacity ≠ Allocable Capacity
Usable Capacity ≠ Allocable Capacity
Accessible Capacity ≠ Allocable Capacity
Reserved Capacity ≠ Freely Allocable Capacity
Technical Control of a Resource ≠ Allocation Authority
Allocation Algorithm ≠ Allocation Authority
Claim Exclusion ≠ Arbitrary Denial
Highest Priority ≠ Unlimited Allocation
Priority Criteria ≠ Allocation Criteria
Minimum Functional Requirement ≠ Guaranteed Minimum Allocation
High Priority ≠ Permission to Exceed Maximum Allocation Boundaries
Allocation ≠ Expansion of Access Authority
Right to Source A ≠ Allocation from Source B
Governance Preference ≠ Physical Feasibility
Aggregate Capacity Sufficiency ≠ Local Allocation Feasibility
Physically Extractable Capacity ≠ Sustainably Allocable Capacity
Emergency Context ≠ Unlimited Allocation Authority
Market Outcome ≠ Universal Governance Legitimacy
Validated Value ≠ Allocation Authority
Fairness Claim ≠ Defined Fairness Rule
Optimization Objective ≠ Governance Authority
Technical Oversubscription Capability ≠ Legitimate Oversubscription Basis
Historical Allocation Basis ≠ Current Allocation Basis
Uncertain Allocation Basis ≠ Certain Allocation Foundation
129. Cross-Architecture Boundary
RABM may consume:
RCHS — Resource identity, Source, type, state, and context.
RACS — Availability, usable capacity, reserved capacity, temporal availability, and accessibility.
RDGS — validated Demand and concurrent Demand evidence.
RDCS — Dependency, Criticality, and consequence evidence.
RAGS — Resource rights, Access authorization, limits, conditions, and continuity evidence.
RPDM — Resource Priority Profiles and Comparative Priority Sets.
RSCS — Scarcity and Constraint states affecting the Allocation Basis.
RSFS — substitution and flexibility evidence.
RIRS — interdependency, reserve, and resilience evidence.
RCSS — continuity and sustainability constraints.
GOA™ — Allocation Authority and Delegation evidence.
OBIDENITY® — identity, ownership, authority, permission, provenance, and transfer evidence.
ORA™ — current operational Resource and infrastructure conditions.
PGA™ — future-condition evidence where relevant.
SIMULOS® — candidate Allocation consequence simulations.
VEGA™ — validated Value and efficiency evidence where legitimately applicable.
RABM does not absorb these mechanisms.
130. 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.
RACS determines Resource Availability and capacity states.
RPDM determines Resource Priority.
RAGS determines Resource Access and rights boundaries.
GOA™ provides authority evidence.
RSCS provides Scarcity context.
RIRS and RCSS may provide resilience, continuity, and sustainability constraints.
RABM combines only the relevant governed inputs necessary to establish the legitimate basis upon which Allocation may proceed.
131. Canonical Boundary
RABM governs the establishment, validation, maintenance, and reassessment of the legitimate basis upon which Resource Allocation may occur, including Allocation Authority, allocable Resource context, participating claims, Priority inputs, Allocation rules, constraints, boundaries, conditions, evidence, validity, conflict, and uncertainty.
It does not determine Resource Demand, Dependency, Criticality, Resource Priority, rights, Access authorization, physical Availability, final Resource Allocation, technical enforcement, Consumption, Scarcity Governance as a whole, or long-term Sustainability.
Its principal governed output is the Resource Allocation Basis Profile .
132. Canonical Closing Statement
Resource Allocation should never begin merely because capacity exists and competing claims are waiting. Before distribution can be legitimate, the basis for distribution must itself be governed.
RABM establishes that foundation — defining what Resource is genuinely allocable, who has authority to allocate it, which claims may participate, which rules and constraints apply, and what evidence must support the Allocation decision before any Resource capacity is assigned.