RPDM — Resource Priority Determination 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 Priority Determination Governance
Module ID: RSGA-RPAS-RPDM-01
Origin ID: OOF-RSGA-RPAS-RPDM
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
RPDM — Resource Priority Determination Module governs how competing legitimate Resource claims are evaluated against applicable governance criteria and evidence to determine their relative Resource Priority before Resource capacity is allocated.
RPDM transforms heterogeneous Resource claims into explicit, comparable, evidence-based Priority determinations without treating Demand, Dependency, Criticality, Access, rights, Value, historical use, technical capability, or willingness to pay as automatic Priority.
Its foundational distinction is:
Criticality ≠ Priority.
And its operational boundary is:
Priority Determination ≠ Resource Allocation.
2. Operational Role
RPDM operates after upstream RSGA™ mechanisms have established sufficient context concerning:
the Resource; available and relevant capacity; Resource Demand; Dependency; Criticality; Resource Access; Resource rights where relevant.
Its role is to answer the question that must precede Allocation:
When legitimate claims compete for the same constrained Resource, what relative governance Priority should each claim receive?
RPDM establishes Priority.
Downstream RPAS mechanisms determine how that Priority affects actual Resource Allocation.
3. Operational Question
What relative Resource Priority should each competing legitimate Resource claim receive, based on the applicable governance criteria, evidence, dependencies, consequences, rights, Access conditions, alternatives, temporal context, and other materially relevant factors?
4. Position in RPAS Governance
Canonical progression:
Allocable Resource Context → Legitimate Competing Claims → Priority Criteria → Evidence Evaluation → Comparative Assessment → Resource Priority Determination → Resource Priority Profile → Allocation Decision
RPDM governs:
Competing Claims → Resource Priority Determination
It does not determine the final Resource Allocation.
5. Governed Space
RPDM governs:
Resource Priority Determination Governance
This space concerns the explicit evaluation and relative ordering or classification of legitimate competing Resource claims before Resource capacity is distributed.
6. Governed Object
The primary Governed Object is:
A Resource Priority relationship between a legitimate Resource claim and other competing legitimate claims upon the same relevant Resource capacity.
Canonical relationship:
**Legitimate Resource Claim
Applicable Priority Criteria Governance Evidence Competing Claims Current Context → Resource Priority State**
7. Scope
RPDM governs:
Priority candidate identification; claim legitimacy input; Priority criteria identification; criteria applicability; Dependency relevance; Criticality relevance; consequence relevance; minimum functional requirement relevance; continuity relevance; substitutability relevance; time sensitivity; rights relevance; Access relevance; safety relevance; operational necessity; validated Value relevance where competent; Priority comparison; Priority classification; Priority ordering; equal Priority; Priority ties; Priority conflict; Priority uncertainty; Priority evidence; Priority traceability; Priority reassessment; Priority versioning.
RPDM does not independently:
establish Resource Demand; determine Resource Dependency; determine Resource Criticality; create Resource rights; authorize Resource Access; determine allocable capacity; assign Resource quantity or capacity; implement Allocation;
control Resource Access; govern Resource Consumption; govern Scarcity response; determine long-term Resource Sustainability.
8. Priority Candidate
A Priority Candidate is a legitimate Resource claim that qualifies for comparative Priority determination within the relevant Allocation context.
A Resource request does not become a Priority Candidate merely because it has been expressed.
9. Candidate Legitimacy
RPDM should receive sufficient upstream evidence that the claim has a legitimate basis for consideration.
Relevant evidence may include:
validated Demand; Dependency; Criticality; Access authorization; Resource rights; purpose; authority; other competent governance basis.
10. Candidate Boundary
Resource Request ≠ Priority Candidate.
A desired Resource quantity without sufficient governance basis should not automatically compete with legitimate claims.
11. Competing Claims
Priority becomes materially relevant where two or more legitimate claims compete directly or indirectly for constrained Resource capacity.
Claims may compete across:
participants; functions; systems; infrastructures; locations; purposes; time periods.
12. Competition Boundary
Two claims are not necessarily competing merely because they concern the same Resource type.
They must materially interact with the same relevant constrained Resource capacity or Allocation context.
13. Priority Criteria
Priority Criteria are the governed factors used to determine relative Resource Priority.
Criteria must be relevant to the Resource and governance context.
14. Criteria Applicability
Not every possible criterion applies to every Resource decision.
RPDM should determine which criteria are materially relevant before using them.
15. Criticality Criterion
Resource Criticality established through RDCS may be a major Priority input.
It does not independently determine Priority.
High Criticality ≠ Automatic Highest Priority.
16. Consequence Criterion
The consequence of insufficient or absent Resource Allocation may affect Priority.
Relevant consequences may concern:
safety; continuity; operational failure; service loss; system degradation; other governed outcomes.
17. Consequence Boundary
Severe claimed consequences should be sufficiently evidenced.
Claimed Consequence ≠ Established Consequence.
18. Minimum Functional Requirement
Some dependent functions require a minimum Resource level below which they cannot perform their required function.
This threshold may materially affect Priority.
19. Minimum Requirement Boundary
A minimum functional requirement identifies a functional threshold.
It does not itself determine how much Resource will ultimately be allocated.
20. Continuity Criterion
Priority may reflect the importance of preserving continuity of a legitimate function or system.
Continuity relevance should remain explicit rather than assumed.
21. Substitutability Criterion
A claim may have lower immediate Priority where a sufficiently viable alternative Resource or operating mode exists.
Conversely, low substitutability may strengthen Priority where other governance conditions support it.
22. Substitutability Boundary
Low Substitutability ≠ Automatic Highest Priority.
It remains one input within the applicable governance context.
23. Time-Sensitivity Criterion
Some Resource requirements lose operational relevance if the Resource is delivered too late.
Time sensitivity may therefore materially affect Priority.
24. Temporal Priority
Resource Priority may change across time.
A claim may be high priority during one operational window and lower priority later.
Priority at Time A ≠ Priority at Time B.
25. Safety Criterion
Where Resource insufficiency creates established safety consequences, safety relevance may materially influence Priority.
26. Safety Boundary
Safety terminology should not be used merely to elevate a claim.
Material safety relevance should be evidenced.
27. Rights Relevance
Resource rights may constrain or influence Priority determination.
RPDM should preserve the distinction between:
holding a Resource right
and:
receiving highest Resource Priority.
28. Rights Boundary
Valid Resource Right ≠ Automatic Highest Priority.
The legal or governance effect of the right depends upon the applicable governing framework.
29. Access Relevance
Only legitimate Access positions should ordinarily participate in Allocation where Access authorization is required.
Access legitimacy does not determine relative Priority.
Authorized Access ≠ Priority.
30. Operational Necessity
A Resource may be operationally necessary for a defined function.
Operational necessity may affect Priority when sufficiently evidenced.
31. Dependency Depth
Priority analysis may consider whether Resource loss propagates through multiple dependent systems.
Dependency-chain evidence from RDCS may therefore be relevant.
32. Cascading Consequence
A Resource claim supporting multiple downstream dependencies may carry broader consequences than an isolated claim.
The cascade should be evidenced rather than inferred solely from network position.
33. Interdependency Relevance
Where Resource systems depend upon one another, Priority determination may require evidence from RIRS concerning interdependency and resilience.
34. Value Relevance
Validated Value may be relevant where the competent Allocation framework recognizes it as a Priority criterion.
VEGA™ may provide such evidence for intelligent systems.
35. Value Boundary
High Value ≠ Highest Resource Priority.
Economic Value, operational Value, strategic Value, or modeled ROI does not independently establish Resource entitlement.
36. Economic Capacity Boundary
Ability to Pay ≠ Resource Priority by definition.
Market mechanisms may legitimately influence Resource distribution where the governing framework establishes them, but purchasing power is not a universal Priority rule.
37. Historical Use
Historical Resource use may provide context concerning operations, dependencies, or continuity.
It does not automatically establish current Priority.
Historical Use ≠ Current Priority.
38. Existing Consumption
Current Resource Consumption may reflect earlier decisions, legacy infrastructure, or uncontrolled technical conditions.
It should not automatically become a Priority criterion.
39. Technical Capability
An actor capable of acquiring or consuming Resource rapidly does not thereby acquire higher governance Priority.
Technical Capability ≠ Resource Priority.
40. Scale Boundary
A larger actor, workload, facility, or system does not automatically receive higher Priority merely because its Resource Demand is larger.
Scale ≠ Priority.
41. Demand Magnitude
Demand magnitude is relevant to understanding the claim.
It does not establish its relative Priority.
Highest Demand ≠ Highest Priority.
42. Priority Comparison
RPDM compares legitimate claims using the applicable criteria and evidence.
The comparison should preserve both:
shared criteria
and:
material claim-specific context.
43. Comparable Representation
Claims should be represented sufficiently consistently to permit meaningful comparison.
This does not require their dependencies, purposes, or consequences to be identical.
44. Multi-Criteria Priority
Priority may depend upon multiple criteria simultaneously.
RPDM should preserve the contribution of materially relevant criteria rather than collapsing them prematurely into a single unexplained score.
45. Criteria Interaction
Criteria may reinforce or counterbalance one another.
For example:
high Criticality + low substitutability
may strengthen a Priority case.
But:
high Criticality + readily available alternative Resource
may produce a different Priority outcome.
46. Criteria Weighting
Where numerical or categorical weights are used, they should remain:
explicit; governed; traceable; reassessable.
47. Weighting Boundary
Numerical Weight ≠ Objective Truth.
Weights encode governance choices or evidence relationships.
They do not eliminate those choices.
48. Priority Score
An implementation may calculate a Priority Score.
The score should remain subordinate to the underlying governance criteria and evidence.
49. Score Boundary
Priority Score ≠ Resource Allocation.
A score represents comparative Priority evidence or state.
It does not assign Resource capacity.
50. Non-Numerical Priority
RPDM does not require numerical scoring.
Priority may be determined through:
classes; tiers; ordered states; decision rules; structured qualitative evaluation; hybrid mechanisms.
51. Priority Class
A Priority Class groups claims with similar governance precedence.
Possible implementation-specific examples include:
Critical
High
Standard
Deferrable
Conditional
The specific classification system must fit the governed Resource context.
52. Priority Ordering
Priority Ordering establishes the relative position of competing claims.
Example:
Claim A > Claim B > Claim C
where the applicable evidence supports that ordering.
53. Equal Priority
Claims may legitimately receive equal Priority.
Equal Priority ≠ Identical Claim.
Different claims may reach the same relative governance precedence through different evidence.
54. Priority Tie
A Priority Tie exists where the applicable governance logic does not establish a material precedence between competing claims.
55. Tie Preservation
RPDM should not manufacture artificial differences merely to force an ordering.
Unresolved Equality ≠ Governance Failure.
A downstream governed tie-resolution mechanism may be required.
56. Tie Resolution Boundary
RPDM identifies the tie and relevant evidence.
Where RPAS defines a separate Allocation-balancing mechanism, that mechanism may determine how Resource capacity is distributed among tied claims.
57. Absolute Priority
Some governance contexts may establish an overriding Priority rule for a defined class of Resource claim.
Such Priority must arise from competent governance authority rather than assumption.
58. Conditional Priority
A claim may hold higher Priority only while a defined condition exists.
Examples include:
emergency state; specific operational window; Resource Source failure; critical infrastructure condition.
59. Priority Escalation
A claim may move to a higher Priority when material conditions worsen.
60. Priority De-Escalation
A claim may move to a lower Priority when:
critical conditions resolve; alternatives become available; Dependency decreases; consequences decrease; time sensitivity ends.
61. Priority Stability
Priority should remain stable while materially relevant conditions remain unchanged.
Continuous arbitrary reprioritization can undermine Resource continuity.
62. Priority Adaptability
Priority must also remain capable of changing when governed reality changes materially.
Priority Stability ≠ Priority Permanence.
63. Priority Conflict
Priority Conflict exists where credible governance criteria or authorities support materially incompatible Priority determinations.
64. Criteria Conflict
Examples include:
safety vs continuity; rights vs emergency requirements; local necessity vs system-wide resilience; short-term consequence vs long-term sustainability.
Such conflicts should remain visible.
65. Conflict Resolution
Where RPDM cannot resolve a conflict using established criteria and authority, the conflict should be escalated through the competent governance mechanism.
66. Priority Uncertainty
Priority Uncertainty exists where evidence is insufficient, unstable, disputed, predictive, or materially incomplete.
67. Uncertainty Sources
Uncertainty may arise from:
Demand uncertainty; Dependency uncertainty; Criticality uncertainty; consequence uncertainty; Resource Availability uncertainty; rights uncertainty; Access uncertainty; future-condition uncertainty.
68. Uncertainty Preservation
Uncertain Evidence ≠ Certain Priority.
Material uncertainty should propagate into the Priority determination.
69. Evidence Sufficiency
RPDM should determine whether available evidence is sufficient for the required Priority decision.
70. Evidence Freshness
Priority evidence should remain sufficiently current for the relevant Resource decision horizon.
71. Evidence Provenance
Material Priority evidence should preserve where relevant:
source; time; claim; Resource; criterion; originating governance mechanism; version.
72. Prediction Evidence
PGA™ may provide governed predictions concerning:
future Demand; future Resource Availability; future consequence; future operational conditions.
Predictions may inform Priority where relevant.
73. Prediction Boundary
Predicted Criticality ≠ Current Criticality.
Predicted Priority Need ≠ Current Priority State.
Future-state evidence should remain temporally explicit.
74. Simulation Evidence
SIMULOS® may simulate consequences of alternative Priority or Allocation scenarios.
Simulation may support Priority determination.
It does not determine Priority authority.
75. Simulation Boundary
Simulated Best Outcome ≠ Governed Priority Decision.
76. Priority Authority
Priority criteria and decision logic should originate from competent governance authority.
A computational mechanism may apply those rules.
It does not create them.
77. Algorithmic Priority
An algorithm may classify, score, rank, or compare claims.
Its output remains governed by:
criteria; authority; evidence; methodology; boundary conditions.
78. Automation Boundary
Automated Ranking ≠ Governance Authority.
79. Human Override
Where competent governance permits human override of a calculated Priority, the override should preserve:
authority; reason; affected claims; evidence; time; resulting Priority.
80. Override Boundary
Human involvement does not eliminate the need for traceability.
81. Priority State
RPDM should represent the current governed Priority condition of each claim.
82. Minimum Priority States
At minimum:
Priority Established
Priority Conditionally Established
Equal Priority
Priority Escalated
Priority De-Escalated
Priority Under Review
Priority Evidence-Limited
Priority Conflicted
Priority Unknown
Priority Unresolved
Priority Expired
83. Priority Established
Available evidence sufficiently supports the current Priority determination.
84. Priority Conditionally Established
Priority remains valid only while specified conditions remain satisfied.
85. Equal Priority
No material precedence exists between the relevant claims under the applicable criteria.
86. Priority Escalated
Material changes justify increased relative Priority.
87. Priority De-Escalated
Material changes justify reduced relative Priority.
88. Priority Under Review
A material change or evidence update requires reassessment.
89. Priority Evidence-Limited
Available evidence supports only a limited-confidence Priority determination.
90. Priority Conflicted
Credible evidence or governance criteria support materially incompatible Priority outcomes.
91. Priority Unknown
Available evidence cannot establish the relevant Priority.
92. Priority Unresolved
Relevant evidence exists, but a final Priority determination cannot yet be completed.
93. Priority Expired
A time-bounded Priority determination is no longer current.
94. Resource Priority Profile
The principal RPDM output is the:
Resource Priority Profile
It represents the governed relative Priority of a legitimate Resource claim within the relevant competing-claim context.
95. Minimum Resource Priority Profile Fields
At minimum:
Priority ID
Claim ID
Access Subject ID
Resource ID
Resource Source where relevant
Demand Reference
Dependency Reference
Criticality Reference
Access Reference
Rights Reference where relevant
Purpose
Applicable Priority Criteria
Criteria Evidence
Minimum Functional Requirement where relevant
Substitutability Context
Time-Sensitivity Context
Consequence Context
Priority Class / Position
Priority State
Priority Conflict State
Priority Uncertainty
Evidence Sufficiency
Effective Time
Expiration where relevant
Reassessment Trigger
Version:
96. Comparative Priority Set
Where multiple claims compete, RPDM may also produce a:
Comparative Priority Set
representing the relative Priority relationship among the claims.
Example:
Claim A — Critical
Claim B — High
Claim C — High
Claim D — Deferrable
The set remains a Priority output, not an Allocation.
97. Priority Traceability
A Priority determination should remain traceable through:
Priority State → Priority Criteria → Criteria Evidence → Claim → Demand / Dependency / Criticality / Access / Rights Context → Resource Context → Governing Priority Logic
98. Priority Explainability
A governed system should be able to explain materially:
which claim received which Priority; which claims it was compared against; which criteria applied; which evidence supported those criteria; which material uncertainty remained; why the resulting Priority was established.
99. Priority Versioning
Material changes to a Priority determination should create an updated version where required for traceability.
100. Priority Reassessment
Priority should be reassessed where material changes can affect relative governance precedence.
101. Reassessment Triggers
Triggers may include:
Demand change; Dependency change; Criticality change; consequence change; Access change; rights change; Resource Availability change; substitution change; time-criticality change;
emergency state; new competing claim; new evidence.
102. Reassessment Boundary
Changed Input ≠ Automatic Priority Change.
The material effect must be evaluated.
103. Targeted Reassessment
Where only one Priority dimension changes, RPDM should reassess the affected criteria and comparative relationships without unnecessarily rebuilding unrelated evidence.
104. Comparative Reassessment
A change to one claim may alter the relative Priority of other competing claims even when their own underlying conditions remain unchanged.
RPDM should therefore evaluate material comparative effects.
105. Priority Lifecycle
Canonical lifecycle:
Candidate Claim → Criteria Applicability → Evidence Evaluation → Comparative Assessment → Priority Determination → Priority Active → Reassessment → Confirm / Escalate / De-Escalate / Conflict / Expire
106. Minimum Implementation Framework
A minimum operational RPDM implementation should contain eight governed layers.
Layer 1 — Candidate Claims
Establish:
Resource Competing Claims Claim Legitimacy Relevant Allocation Context
Layer 2 — Priority Criteria
Identify:
applicable criteria; governance basis; criteria boundaries.
Layer 3 — Evidence Assembly
Collect relevant:
Demand; Dependency; Criticality; consequence; Access; rights; substitutability; time; other competent evidence.
Layer 4 — Criteria Evaluation
Evaluate each claim against the applicable Priority criteria.
Layer 5 — Comparative Assessment
Compare legitimate claims while preserving:
differences; ties; conflicts; uncertainty.
Layer 6 — Priority Determination
Establish:
Priority Class; Priority Position; Priority State.
Layer 7 — Evidence & Reassessment
Preserve:
evidence sufficiency; uncertainty; conflict; reassessment triggers; version.
Layer 8 — Governed Output
Produce:
Resource Priority Profile Comparative Priority Set where relevant
Canonical machine-readable logic:
Legitimate Claims → Applicable Priority Criteria → Governance Evidence → Criteria Evaluation → Comparative Assessment → Resource Priority Determination → Resource Priority Profile
107. Minimum Decision States
RPDM must support at least:
Priority Established
Priority Conditionally Established
Equal Priority
Priority Escalated
Priority De-Escalated
Priority Under Review
Priority Evidence-Limited
Priority Conflicted
Priority Unknown
Priority Unresolved
Priority Expired
108. Minimum Evidence Path
Where Priority cannot be sufficiently determined:
Priority Unresolved → Material Priority Evidence Gap → Affected Criterion → Minimum Evidence Requirement → Evidence Acquisition / Verification → Comparative Reassessment → Priority Redetermination → Updated Resource Priority Profile
109. Minimum Reassessment Framework
At minimum:
Current Resource Priority Profile → Material Change / New Competing Claim → Materiality Test → Affected Priority Criteria → Evidence Refresh → Comparative Reassessment → Priority Confirmation / Escalation / De-Escalation / Conflict → Profile Update → Version Update
110. Governance Requirements
A conforming RPDM implementation must:
1. identify the relevant Resource; 2. identify legitimate Priority Candidates; 3. identify materially competing claims; 4. preserve claim identity; 5. preserve relevant Demand evidence; 6. preserve relevant Dependency evidence; 7. preserve relevant Criticality evidence; 8. preserve Access evidence; 9. preserve rights evidence where relevant;
10. identify applicable Priority criteria; 11. establish criteria applicability; 12. preserve criteria authority or governance basis; 13. evaluate Criticality relevance; 14. evaluate consequence relevance; 15. evaluate minimum functional requirements where relevant; 16. evaluate continuity relevance where applicable; 17. evaluate substitutability where relevant; 18. evaluate time sensitivity where relevant; 19. evaluate safety relevance where relevant; 20. evaluate rights relevance where applicable; 21. evaluate operational necessity where relevant; 22. evaluate validated Value only where legitimately applicable; 23. distinguish Criticality from Priority; 24. distinguish Demand magnitude from Priority; 25. distinguish Access from Priority; 26. distinguish rights from automatic Priority; 27. distinguish Value from automatic Priority; 28. distinguish historical use from current Priority; 29. distinguish technical capability from Priority; 30. support multi-criteria evaluation; 31. preserve criteria interactions; 32. govern weighting where used; 33. support numerical and non-numerical Priority methods; 34. support Priority classification; 35. support Priority ordering; 36. support equal Priority; 37. identify Priority ties; 38. preserve Priority conflict; 39. preserve Priority uncertainty; 40. determine evidence sufficiency; 41. preserve evidence provenance; 42. preserve temporal context; 43. support conditional Priority; 44. support Priority escalation; 45. support Priority de-escalation; 46. preserve Priority stability where conditions remain unchanged; 47. support material Priority reassessment; 48. evaluate comparative effects of changed claims; 49. preserve Priority traceability; 50. support Priority versioning; 51. produce Resource Priority Profiles; 52. produce Comparative Priority Sets where relevant.
111. Governance Logic
Canonical RPDM logic:
Legitimate Resource Claim → Competing Claim Context → Applicable Priority Criteria → Demand Evidence → Dependency Evidence → Criticality Evidence → Consequence Evidence → Access / Rights Context → Substitutability / Time / Other Relevant Evidence → Comparative Evaluation → Resource Priority Determination → Resource Priority Profile
Across multiple claims:
Claim A + Claim B + Claim C → Common Governance Context → Criteria Evaluation → Comparative Assessment → Priority Relationship → Comparative Priority Set
112. Governance Outputs
RPDM may produce:
Resource Priority Profile
Comparative Priority Set
Priority Candidate State
Priority Criteria Set
Criteria Applicability State
Priority Class
Priority Position
Equal-Priority State
Priority Tie State
Priority Escalation State
Priority De-Escalation State
Priority Conflict State
Priority Uncertainty
Evidence Sufficiency State
Reassessment Trigger
Version:
113. Failure Conditions
RPDM should not be considered sufficiently completed where:
Resource requests are treated automatically as legitimate Priority Candidates; claims that do not compete are falsely compared; Criticality is treated as Priority; highest Demand automatically receives highest Priority; Resource rights automatically create highest Priority; Access authorization automatically creates Priority; historical use automatically creates current Priority; current Consumption is treated as Priority; technical capability determines Priority; actor size determines Priority; ability to pay is treated as a universal Priority rule; Value automatically determines Priority; Priority criteria are hidden; irrelevant criteria are applied; criteria weighting is opaque; a numerical score is treated as governance truth; ties are artificially broken without governance basis;
material criteria conflict is hidden; material uncertainty is suppressed; predicted future states are represented as current states; simulation output is treated as governance authority; algorithmic ranking is treated as authority; Priority is confused with Allocation; Priority cannot be traced to evidence; material changes occur without reassessment.
114. Use Case 1 — AI Data Center GPU Priority Determination
A data center has constrained GPU capacity and four workloads with legitimate Access:
Workload A — real-time safety monitoring
Workload B — customer production inference
Workload C — model training
Workload D — experimental research
RDGS establishes validated Demand for each workload.
RDCS establishes their respective Dependency and Criticality.
RAGS confirms legitimate Access.
RPDM then evaluates the claims using applicable criteria including:
Criticality; consequence of non-allocation; minimum functional requirement; time sensitivity; substitutability; operational necessity.
The result may establish:
Workload A — Critical Priority
Workload B — High Priority
Workload C — Standard Priority
Workload D — Deferrable Priority
RPDM does not determine how many GPUs each workload receives.
It establishes the governed Priority evidence required for the downstream Allocation decision.
115. Use Case 2 — Regional Water Priority Determination
A region faces constrained water capacity.
Legitimate claims include:
essential household supply; healthcare facilities; agricultural irrigation; industrial production.
Each claim may possess valid Demand and legitimate Access.
RPDM evaluates the applicable Priority criteria.
Healthcare may show:
high Dependency; high consequence of interruption; low short-term substitutability; high time sensitivity.
Agriculture may show:
seasonal time sensitivity; significant economic and food-production consequences; variable substitution possibilities.
Industrial production may show different:
continuity requirements; economic consequences; alternative Source possibilities.
RPDM produces explicit Resource Priority Profiles and a Comparative Priority Set.
It does not assume that:
the largest Demand; the highest economic Value; the largest historical user; or the actor capable of extracting water fastest
must receive the highest Priority.
116. Critical Distinctions
Criticality ≠ Priority
Priority Determination ≠ Resource Allocation
Resource Request ≠ Priority Candidate
High Criticality ≠ Automatic Highest Priority
Claimed Consequence ≠ Established Consequence
Low Substitutability ≠ Automatic Highest Priority
Valid Resource Right ≠ Automatic Highest Priority
Authorized Access ≠ Priority
High Value ≠ Highest Resource Priority
Ability to Pay ≠ Resource Priority by definition
Historical Use ≠ Current Priority
Technical Capability ≠ Resource Priority
Scale ≠ Priority
Highest Demand ≠ Highest Priority
Numerical Weight ≠ Objective Truth
Priority Score ≠ Resource Allocation
Equal Priority ≠ Identical Claim
Priority Stability ≠ Priority Permanence
Uncertain Evidence ≠ Certain Priority
Predicted Priority Need ≠ Current Priority State
Simulated Best Outcome ≠ Governed Priority Decision
Automated Ranking ≠ Governance Authority
Changed Input ≠ Automatic Priority Change
117. Cross-Architecture Boundary
RPDM may consume:
RCHS — Resource identity, Source, type, state, and context.
RACS — Resource Availability and capacity context.
RDGS — validated Resource Demand.
RDCS — Resource Dependency, Criticality, consequence, and dependency-chain evidence.
RAGS — Resource Access, rights, eligibility, and authorization evidence.
RSFS — Resource substitution and flexibility evidence where relevant.
RIRS — interdependency and resilience evidence.
RCSS — continuity and sustainability evidence where relevant.
GOA™ — governance authority and decision-boundary evidence.
OBIDENITY® — identity, rights, ownership, authority, and provenance evidence.
ORA™ — current Operational Reality evidence.
PGA™ — governed prediction evidence.
SIMULOS® — simulated consequence evidence.
VEGA™ — validated Value evidence where legitimately applicable.
RPDM does not absorb these mechanisms.
118. 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.
RDGS establishes Resource Demand.
RDCS establishes Dependency and Criticality.
RAGS establishes legitimate Access and relevant Resource rights.
VEGA™ may establish validated Value.
PGA™ may establish governed prediction evidence.
SIMULOS® may evaluate possible consequences.
RPDM uses those inputs only to determine the relative Resource Priority of competing legitimate claims.
119. Canonical Boundary
RPDM governs the determination of relative Resource Priority among legitimate competing Resource claims through explicit, applicable, evidenced, traceable, and reassessable Priority criteria.
It does not establish Resource Demand, Dependency, Criticality, rights, Access authorization, allocable capacity, Resource Allocation, technical enforcement, Consumption, Scarcity response, or long-term Sustainability.
Its principal governed output is the Resource Priority Profile , with a Comparative Priority Set where multiple claims are evaluated together.
120. Canonical Closing Statement
Resource Priority should not belong automatically to the actor that asks first, demands most, pays most, consumes most, or possesses the greatest technical ability to capture the Resource.
RPDM establishes Priority as an explicit governance determination — comparing legitimate Resource claims through their dependencies, consequences, rights, alternatives, timing, and other competent evidence before any constrained Resource capacity is allocated.