RRGM — Resource Rights Governance Module
Architecture: RSGA™ — Resource Sustainability Governance Architecture
Parent Standard: Resource Access Governance Standard (RAGS)
Category: Governance & Enforcement
Subcategory: Resource Governance
Type: Core Module
Governed Space: Resource Rights Governance
Module ID: RSGA-RAGS-RRGM-03
Origin ID: OOF-RSGA-RAGS-RRGM
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
RRGM — Resource Rights Governance Module governs how a claimed, established, delegated, transferred, conditional, temporary, shared, exclusive, suspended, expired, or otherwise relevant right or entitlement relating to access to a Resource or Resource capacity is identified, traced to its legitimate basis, bounded, evidenced, validated, maintained, modified, transferred where permitted, suspended, terminated, and reassessed within Resource Access Governance.
RRGM establishes whether a claimed Resource Access right exists as a sufficiently governed right, who or what holds it, what Resource it concerns, what scope it carries, where its authority originates, and under which conditions it remains valid.
Claimed Resource Right ≠ Established Resource Right.
2. Operational Role
RAEM determines:
Is the actor eligible for Resource Access?
RACM determines:
How is legitimate Resource Access operationally controlled?
RRGM determines:
What Resource Access right or entitlement exists, who holds it, where it comes from, what it permits, and whether it remains valid?
RRGM prevents statements such as:
“We have always used this Resource.”
“We own the facility.”
“We need the Resource.”
“The Resource is critical to us.”
from being treated automatically as evidence of an established Resource right.
3. Core Question
What legitimate right or entitlement, if any, does the governed actor hold in relation to access to the defined Resource or Resource capacity, from what authority or governing basis does that right originate, what is its scope, duration, transferability, exclusivity, conditions, and evidence, and does it remain valid under the current governed conditions?
4. Position in RAGS Governance
Resource Access Governance may require several distinct determinations:
Eligibility → Rights / Entitlement → Authorization → Access Control → Restrictions / Conditions → Active Access
These relationships are not universally linear.
Some Resource contexts may require an established right before authorization.
Other contexts may permit authorization without a persistent underlying Resource right.
RRGM therefore governs Resource rights as an independent Access dimension rather than assuming that every authorization is itself a permanent right.
5. Governed Space
RRGM governs:
Resource Rights Governance
This space concerns the existence, legitimacy, origin, holder, scope, conditions, continuity, transferability, modification, suspension, termination, evidence, and reassessment of Resource-related Access rights and entitlements.
6. Governed Object
The primary Governed Object is:
A Resource Right or Resource Access Entitlement held by a sufficiently identified actor in relation to a defined Resource or Resource capacity.
Canonical relationship:
**Right Holder
Resource Rights Basis Authority Origin Rights Scope Conditions Evidence → Resource Right State**
7. Scope
RRGM governs:
Resource Right identification; rights claims; right-holder identification; rights basis; authority origin; rights legitimacy; rights scope; Resource-specific rights; Resource Source-specific rights; quantity and capacity rights; rate-bound rights; temporal rights; spatial rights;
purpose-bound rights; conditional rights; shared rights; exclusive rights; temporary rights; persistent rights; delegated rights; transferred rights; transferability; rights modification; rights restriction; rights suspension; rights termination; rights expiration; rights renewal; rights conflict; rights evidence; rights uncertainty; rights reassessment; rights traceability.
RRGM does not independently:
determine Resource Access eligibility; create external legal rights; issue Resource Access authorization; implement technical Access Controls; determine Resource Priority; allocate Resource capacity; govern actual Resource Consumption; determine Scarcity response; establish long-term Sustainability.
8. Resource Right Principle
A Resource right must have a sufficiently legitimate governing basis.
A Resource right does not arise merely because an actor:
wants the Resource; needs the Resource; depends upon the Resource; has historically consumed the Resource; can technically access the Resource; creates substantial Value from the Resource.
9. Rights Claim
A Rights Claim is an assertion that an actor possesses a Resource-related right or entitlement.
A claim is evidence requiring governance.
It is not the right itself.
Rights Claim ≠ Established Resource Right.
10. Right Holder
Every established Resource right should identify a sufficiently defined Right Holder.
The holder may be:
person; organization; public institution; facility where governance permits; system where appropriately established; other legally or operationally recognized governed actor.
11. Right-Holder Identity
Rights should not be attached to ambiguous identity where identity materially affects ownership, entitlement, transferability, authority, or enforcement.
12. Resource Identity
A Resource right must refer to a sufficiently defined Resource or Resource capacity.
The Resource should remain traceable to RCHS characterization.
13. Rights Basis
The Rights Basis explains why the right exists.
Possible bases may include:
law; regulation; contract; license; permit; ownership; public mandate; service entitlement; delegation; transfer; institutional rule; other legitimate governance basis.
RRGM does not determine the external legal validity of a legal instrument beyond the evidence available to the governed methodology.
14. Authority Origin
A Resource right should remain traceable to the authority capable of creating, recognizing, assigning, or transferring that right where material.
Canonical relationship:
Authority: Origin → Rights Basis → Right Holder → Resource Right
15. Authority Boundary
RRGM identifies and governs the Resource relevance of authority evidence.
It does not manufacture authority where no legitimate authority exists.
Methodological Recognition ≠ Creation of External Legal Authority.
16. Rights Legitimacy
A Resource right is sufficiently established where its:
holder; Resource; basis; authority; scope; conditions; validity; evidence
are sufficient for the intended governance purpose.
17. Rights Scope
A Resource right may be bounded by:
Resource; Resource Source; quantity; capacity; rate; purpose; function; location; time; operating state; transferability; other governed conditions.
18. Scope Principle
A right should not be interpreted beyond the scope established by its legitimate basis.
Limited Resource Right ≠ Unlimited Resource Entitlement.
19. Resource-Specific Right
A right relating to one Resource does not automatically create a right to another.
Right to Resource A ≠ Right to Resource B.
20. Source-Specific Right
A Resource right may apply only to a particular Source.
Right to Source A ≠ Right to Every Source of the Resource.
21. Quantity-Bound Right
A right may establish entitlement to access a defined Resource quantity.
The existence of the right does not guarantee that the quantity is currently physically available.
22. Capacity-Bound Right
A Resource right may concern a defined capacity.
Examples include:
electrical capacity; compute capacity; network capacity; storage capacity; cooling capacity.
23. Rate-Bound Right
Some Resource rights may be limited by:
flow rate; power draw; delivery rate; throughput; other Resource-specific rate.
24. Temporal Right
A Resource right may exist only during a defined period.
Examples include:
fixed contractual period; seasonal period; temporary operating period; emergency period; scheduled Access period.
25. Spatial Right
A Resource right may be valid only at a defined:
facility; delivery point; network node; region; jurisdiction; infrastructure area.
26. Purpose-Bound Right
A Resource right may be valid only for a defined purpose.
A right granted for:
essential service operation
does not automatically establish a right for:
unrelated commercial use.
27. Conditional Right
A Resource right may exist only while specified conditions remain satisfied.
28. Persistent Right
A persistent Resource right continues until:
termination; revocation where permitted; transfer; supersession; material governing condition; other legitimate closure mechanism.
Persistent does not mean unlimited or immutable.
29. Temporary Right
A temporary Resource right must preserve its:
effective time; expiration; scope; conditions; rights basis.
30. Shared Right
Multiple actors may hold legitimate rights relating to the same Resource.
The existence of shared rights does not prove sufficient capacity to satisfy every holder simultaneously.
Multiple Valid Resource Rights ≠ Sufficient Resource Capacity.
31. Exclusive Right
Where a Resource right is exclusive, the basis for exclusivity should be explicit.
Current sole use does not prove exclusive entitlement.
Sole Current Use ≠ Exclusive Resource Right.
32. Rights and Ownership
Ownership may create Resource rights in some contexts.
Ownership should not automatically be interpreted as unlimited authority over every Resource relationship associated with the owned asset.
Ownership ≠ Unlimited Resource Right.
33. Rights and Possession
Possession or physical control of a Resource does not by itself establish a legitimate Resource right.
Possession ≠ Resource Entitlement.
34. Rights and Historical Use
Long-standing Resource use may be relevant evidence depending upon the governing context.
It does not universally establish a current right.
Historical Use ≠ Current Resource Right.
35. Rights and Existing Consumption
Current consumption demonstrates operational Resource use.
It does not independently establish entitlement.
Consumption ≠ Resource Right.
36. Rights and Resource Demand
A valid Demand Profile establishes Resource requirement.
It does not create a Resource right.
Resource Demand ≠ Resource Right.
37. Rights and Dependency
A Resource Dependency establishes reliance.
It does not create a Resource right.
Resource Dependency ≠ Resource Right.
38. Rights and Criticality
Criticality establishes the significance of a Resource Dependency.
It does not create entitlement.
Resource Criticality ≠ Resource Right.
39. Rights and Value
A participant may create substantial Value through a Resource.
That does not independently create entitlement to the Resource.
Resource Value ≠ Resource Right.
40. Rights and Availability
A valid Resource right may exist while the Resource is unavailable.
Likewise, a Resource may be abundant while an actor possesses no right to it.
Resource Right ≠ Resource Availability.
41. Rights and Eligibility
Eligibility determines whether an actor qualifies for Access consideration.
Rights determine whether a legitimate entitlement exists.
These are separate dimensions.
Eligibility ≠ Resource Right.
42. Rights and Authorization
A Resource right may provide a basis for Access authorization.
The right and the authorization remain distinct.
Resource Right ≠ Active Access Authorization.
Some Resource contexts may require a separate authorization step before the right can be exercised.
43. Rights and Access Control
RACM may enforce Access derived from an established right and authorization.
The technical control does not create the right.
Access Control ≠ Resource Right.
44. Rights and Priority
Resource rights may be relevant evidence in Priority Governance.
They do not automatically establish highest Priority.
Resource Right ≠ Highest Resource Priority.
45. Rights and Allocation
A valid Resource right does not guarantee current Allocation where Resource capacity is constrained and the governing system legitimately permits competing claims or limitations.
Resource Right ≠ Current Resource Allocation.
46. Rights and Scarcity
Scarcity does not automatically erase existing Resource rights.
It may create circumstances in which rights, restrictions, Priority, Allocation, and Scarcity Governance interact.
47. Rights Modification
A Resource right may be modified where its governing basis permits.
Modification may affect:
quantity; capacity; rate; purpose; location; duration; conditions; transferability; exclusivity.
48. Modification Authority
A Resource right should not be modified by an actor lacking competent authority to modify it.
49. Rights Restriction
A right may remain valid while its exercise becomes restricted under legitimate governance conditions.
Restriction should not automatically be represented as termination.
50. Rights Suspension
A Resource right may be temporarily suspended where the governing basis permits.
Suspension preserves the distinction between:
temporary inability to exercise the right
and:
termination of the right.
51. Rights Termination
Termination ends the relevant Resource right.
The termination should remain traceable to:
authority; basis; effective time; affected right; evidence.
52. Rights Expiration
A time-limited Resource right expires when its governed validity period ends unless legitimately renewed.
Expired Right ≠ Current Resource Entitlement.
53. Rights Renewal
A Resource right may be renewed where its governing basis permits.
Historical validity does not guarantee renewal.
54. Rights Delegation
A Resource right or authority associated with its exercise may be delegable where permitted.
Delegation should preserve:
original holder; delegate; scope; duration; conditions; Resource; delegation authority.
55. Delegation Boundary
A delegate cannot legitimately exercise a broader Resource right than was delegated.
Delegated Right ≠ Expanded Right.
56. Rights Transfer
Where permitted, a Resource right may be transferred from one holder to another.
Transfer should preserve:
transferor; transferee; Resource; rights basis; scope; effective time; transfer authority; evidence.
57. Transferability
Not every Resource right is transferable.
Transferability must be established rather than assumed.
Resource Right ≠ Transfer Authority.
58. Partial Transfer
Where permitted, only part of a Resource right may be transferred.
The retained and transferred scopes must remain distinguishable.
59. Transfer Finality
A completed transfer should establish whether the original holder:
retains part of the right; retains no right; retains conditional rights; retains delegated authority.
60. Delegation vs Transfer
Delegation and transfer are different mechanisms.
Delegation allows another actor to exercise defined rights or authority while the originating relationship remains relevant.
Transfer changes the holder of the relevant right where permitted.
Delegation ≠ Transfer.
61. Rights Succession
Where Resource rights may continue through organizational, institutional, ownership, or other succession, the continuity basis should be evidenced.
Continuity should not be assumed solely because operational use continues.
62. Rights Conflict
Rights Conflict exists where two or more materially incompatible Resource rights or claims concern the same Resource relationship.
63. Overlapping Rights
Multiple rights may overlap without necessarily conflicting.
Conflict exists when their simultaneous interpretation or exercise becomes materially incompatible.
64. Competing Rights
Two valid Resource rights may compete for insufficient Resource capacity.
RRGM establishes the rights.
It does not resolve downstream Resource Priority or Allocation.
65. Rights Hierarchy
Where a governing system establishes hierarchy among rights, RRGM may preserve that hierarchy as evidence.
RRGM does not invent hierarchy merely to resolve competition.
66. Rights Conflict Resolution
Canonical logic:
Conflicting Rights / Claims → Holder Identity Check → Resource Identity Check
→ Rights Basis Check → Authority Origin Check → Scope Check → Temporal Check → Spatial Check → Validity Check → Competent Resolution → Rights Redetermination
67. Rights Uncertainty
Uncertainty may concern:
holder identity; Resource identity; rights basis; authority; scope; validity; transferability; delegation; duration; termination; conflicting claims.
68. Uncertainty Propagation
Material uncertainty must remain visible in the Resource Right State.
Uncertain Right ≠ Established Right.
69. Rights Evidence
Evidence may include:
law; regulatory record; contract; license; permit; ownership record; service agreement; delegation record; transfer record; institutional mandate; rights register; other competent evidence.
70. Evidence Provenance
Material rights evidence should preserve where relevant:
source; issuer; holder; Resource; scope; effective date; expiration;
version; authority reference.
71. Evidence Validity
The existence of a document does not prove that the right remains valid.
Rights Document Exists ≠ Resource Right Currently Valid.
72. Evidence Freshness
RRGM should distinguish current rights evidence from superseded, expired, revoked, or historical evidence.
73. Evidence Sufficiency
Rights evidence is sufficient when it adequately establishes the Resource Right State required for the intended governance purpose.
74. Rights Evidence Gap
A material Evidence Gap exists where missing evidence could alter:
right existence; holder; scope; authority; duration; transferability; current validity.
75. Rights State
RRGM represents the governed status of the relevant Resource right through a Resource Right State.
76. Minimum Resource Right States
At minimum:
Right Established
Right Conditionally Established
Right Restricted
Right Suspended
Right Transferred
Right Expired
Right Terminated
Right Evidence-Limited
Right Conflicted
Right Unknown
Right Unresolved
77. Right Established
The Resource right is sufficiently supported and currently valid within its governed scope.
78. Right Conditionally Established
The right exists only while explicit conditions remain satisfied.
79. Right Restricted
The right remains valid but its exercise or scope is currently restricted.
80. Right Suspended
The right exists structurally or historically but its exercise is temporarily suspended.
81. Right Transferred
The relevant right has been legitimately transferred to another holder where permitted.
82. Right Expired
The validity period has ended.
83. Right Terminated
The right no longer exists under the relevant governance basis.
84. Right Evidence-Limited
Available evidence does not support a stronger rights determination.
85. Right Conflicted
Credible evidence supports materially incompatible Resource Right States.
86. Right Unknown
Available evidence does not establish whether the relevant Resource right exists.
87. Right Unresolved
Relevant evidence exists but final determination cannot yet be completed.
88. Rights Lifecycle
A Resource right may move through:
Claimed → Evaluated → Established → Active / Conditional / Restricted → Modified / Delegated / Transferred where permitted → Suspended → Renewed / Expired / Terminated
The exact lifecycle depends upon the governing basis.
89. Rights Continuity
A Resource right should remain continuous only while its legitimate basis remains valid.
Operational continuity alone does not establish rights continuity.
90. Rights Reassessment
Resource rights should be reassessed where material changes could alter their existence, holder, scope, or validity.
91. Reassessment Triggers
Triggers may include:
holder change; Resource change; Resource Source change; contract change; license change; ownership change; authority change; delegation; transfer; expiration; restriction; suspension; termination; new rights claim; new conflicting evidence; new governing rule.
92. Targeted Reassessment
Where only one rights dimension changes, RRGM should reassess the affected dimension and its consequences rather than unnecessarily reconstructing unrelated evidence.
93. Rights Versioning
Material changes to a Resource right should create a new governed version where traceability requires it.
94. Historical Rights
Historical rights should remain traceable without being represented as current entitlement.
Former Right ≠ Current Right.
95. Rights Traceability
A Resource Right State should remain traceable through:
Resource Right State → Rights Scope → Rights Basis → Authority Origin → Right Holder → Resource → Evidence.
96. Rights Explainability
A governed Resource right should be able to explain materially:
who holds the right; which Resource it concerns; why the right exists; who or what established it; what scope it carries; which conditions apply; whether it can be delegated or transferred; when it expires or terminates; what evidence supports it.
97. Rights Auditability
Where required, the Resource right should remain reconstructable across:
claim; establishment; modification; restriction; delegation; transfer; suspension; renewal; expiration; termination.
98. Rights Minimality
RRGM should not infer broader rights than the evidence establishes.
Where evidence supports a limited right, the governed representation should remain limited.
99. Rights Expansion
Expansion of a Resource right requires a legitimate basis capable of expanding it.
Increased Resource Need ≠ Rights Expansion.
100. Rights Reduction
Reduction in rights scope should preserve:
authority; basis; effective time; new scope; evidence.
101. Rights Integrity
A Resource right should not be manipulated merely to achieve a preferred downstream Priority or Allocation outcome.
Desired Allocation ≠ Resource Right Evidence.
102. Automated Rights Evaluation
Systems may assist with:
rights evidence retrieval; validity checks; scope comparison; expiration detection; conflict detection; rights-state classification.
Automation does not create the underlying right.
103. Automated Rights Boundary
Machine Recognition of a Right ≠ Creation of the Right.
104. Resource Rights Profile
The principal RRGM output is the:
Resource Rights Profile
It represents the governed state of the relevant Resource right or entitlement.
105. Minimum Resource Rights Profile Fields
At minimum:
Right ID
Right Holder ID
Resource ID
Resource Source where relevant
Rights Basis
Authority: Origin
Rights Type
Rights Scope
Quantity / Capacity / Rate Boundary where relevant
Purpose Boundary
Temporal Boundary
Spatial Boundary
Conditions
Exclusivity State where relevant
Transferability State
Delegation State where relevant
Rights State
Evidence Basis
Evidence Sufficiency
Rights Uncertainty
Effective Time
Expiration where relevant
Termination State where relevant
Reassessment Trigger
Version:
106. Rights Type
Implementations may distinguish Resource rights such as:
statutory; regulatory; contractual; licensed; ownership-based; service-based; institutional; delegated; transferred; temporary; emergency; other legitimately established types.
The classification does not replace examination of the underlying Rights Basis.
107. Rights Relationship Record
Where detailed implementation requires it, each rights relationship may preserve:
Holder Resource Basis Authority Scope Conditions Validity Transferability Evidence State
as a machine-readable governance object.
108. Minimum Implementation Framework
A minimum operational RRGM implementation should contain eight governed layers.
Layer 1 — Rights Claim / Candidate Right
Identify:
Right Holder Resource Claimed Right / Entitlement
Layer 2 — Rights Basis
Establish:
Rights Basis Authority Origin Applicable governing instrument
Layer 3 — Rights Scope
Determine:
Resource scope Quantity / Capacity / Rate Purpose Time Location Conditions
Layer 4 — Rights Characteristics
Determine where relevant:
Exclusivity Transferability Delegability Persistence Restriction conditions
Layer 5 — Evidence
Evaluate:
Evidence provenance Validity Freshness Sufficiency
Layer 6 — Conflict & Uncertainty
Determine:
Competing claims Scope conflict Authority conflict Rights uncertainty
Layer 7 — Rights Determination
Determine:
Resource Right State Effective period Restrictions Transfer / Delegation status
Layer 8 — Governed Output
Produce:
Resource Rights Profile Reassessment Triggers Version
Canonical machine-readable logic:
**Rights Claim
Right Holder Resource → Rights Basis → Authority Origin → Rights Scope → Conditions → Evidence → Conflict / Uncertainty → Resource Right State → Resource Rights Profile**
109. Minimum Decision States
RRGM must support at least:
Right Established
Right Conditionally Established
Right Restricted
Right Suspended
Right Transferred
Right Expired
Right Terminated
Right Evidence-Limited
Right Conflicted
Right Unknown
Right Unresolved
110. Minimum Evidence Path
Where a Resource right cannot be sufficiently determined:
Right Unresolved → Material Rights Evidence Gap → Rights Basis / Authority / Holder / Scope Requirement → Minimum Evidence Requirement → Evidence Acquisition / Verification → Rights Reassessment → Updated Resource Right State → Updated Resource Rights Profile
111. Minimum Reassessment Framework
At minimum:
Current Resource Rights Profile → Material Change / New Evidence → Materiality Test → Affected Rights Dimension → Targeted Reassessment → Rights Redetermination → Profile Retained or Revised → Version Update
112. Governance Requirements
A conforming RRGM implementation must:
1. identify the Right Holder; 2. identify the Resource; 3. preserve Resource identity; 4. identify the claimed or established Resource right; 5. establish the Rights Basis; 6. identify Authority Origin where material; 7. determine Rights Scope; 8. preserve Resource Source boundaries where relevant; 9. preserve quantity boundaries where relevant; 10. preserve capacity boundaries where relevant; 11. preserve rate boundaries where relevant; 12. preserve purpose boundaries where relevant; 13. preserve temporal boundaries; 14. preserve spatial boundaries where relevant; 15. preserve conditions; 16. determine exclusivity where relevant; 17. determine transferability where relevant; 18. determine delegation conditions where relevant; 19. distinguish delegation from transfer; 20. support rights modification; 21. support rights restriction; 22. support rights suspension; 23. support rights transfer where permitted; 24. support rights expiration; 25. support rights termination; 26. preserve rights evidence; 27. preserve evidence provenance; 28. evaluate evidence validity;
29. evaluate evidence freshness; 30. determine evidence sufficiency; 31. preserve material rights conflict; 32. preserve material uncertainty; 33. determine a Resource Right State; 34. support reassessment; 35. support versioning; 36. preserve historical rights; 37. distinguish Resource rights from eligibility; 38. distinguish Resource rights from authorization; 39. distinguish Resource rights from technical Access Control; 40. distinguish Resource rights from Demand; 41. distinguish Resource rights from Dependency; 42. distinguish Resource rights from Criticality; 43. distinguish Resource rights from Priority; 44. distinguish Resource rights from Allocation; 45. prevent operational use from becoming automatic entitlement; 46. produce a Resource Rights Profile.
113. Governance Logic
Canonical RRGM logic:
**Right Holder
Resource Rights Claim / Candidate Right → Rights Basis → Authority Origin → Scope → Conditions → Validity → Evidence → Conflict & Uncertainty → Resource Right State → Resource Rights Profile**
Where the right is unresolved:
Rights Gap → Minimum Evidence Requirement → Authority / Basis / Holder / Scope Verification → Rights Redetermination
114. Governance Outputs
RRGM may produce:
Resource Rights Profile
Resource Right State
Right Holder
Rights Basis
Authority: Origin
Rights Type
Rights Scope
Quantity / Capacity / Rate Boundary
Purpose Boundary
Temporal Boundary
Spatial Boundary
Conditionality State
Exclusivity State
Transferability State
Delegation State
Rights Conflict State
Evidence Sufficiency State
Rights Uncertainty
Effective Time
Expiration
Termination State
Reassessment Trigger
Version:
These outputs become governed evidence for subsequent Resource Access mechanisms.
115. Failure Conditions
RRGM should not be considered sufficiently completed where:
a Rights Claim is treated as an established right; Right Holder identity is materially ambiguous; Resource identity is unclear; Rights Basis is missing; Authority Origin is materially unsupported; Rights Scope is assumed rather than evidenced; a limited right is represented as unlimited; historical use is treated automatically as current entitlement; existing consumption is treated as a Resource right; Resource Demand is treated as a Resource right; Resource Dependency is treated as a Resource right; Criticality is treated as a Resource right; Value is treated as a Resource right; ownership is treated automatically as unlimited Resource entitlement; delegation is confused with transfer; transferability is assumed; expired rights are represented as current; terminated rights remain represented as valid; material rights conflict is hidden; material uncertainty is suppressed; technical Access Control is treated as evidence that a right exists; Resource rights are manipulated to obtain a preferred Priority or Allocation outcome.
116. Use Case 1 — AI Data Center Compute Capacity Rights
An organization operates workloads within a shared AI compute facility.
The organization claims a right to:
500 GPU units of compute capacity
based upon a long-term infrastructure agreement.
RRGM examines:
Right Holder — Organization
Resource — Defined GPU Compute Capacity
Rights Basis — Infrastructure Agreement
Authority: Origin — Competent Facility / Contractual Authority
Capacity Scope — 500 GPU units
Purpose — Defined workload classes
Temporal Boundary — Contract period
Transferability — Restricted
Evidence — Current agreement and rights records
RRGM determines:
Resource Right State — Right Established.
This does not mean that 500 GPUs are currently available.
It does not itself activate technical Access.
It does not establish that the organization receives higher Resource Priority than another legitimate rights holder during a severe Resource constraint.
Those remain separate governance questions.
117. Use Case 2 — Regional Water Rights
A regional agricultural operator claims entitlement to withdraw water from a defined Resource Source.
RRGM evaluates:
Right Holder; Resource Source; Rights Basis; permitted withdrawal quantity; seasonal conditions; location; effective period; transferability; restrictions; evidence.
The evidence establishes that the operator holds a valid seasonal right subject to a defined maximum withdrawal rate.
RRGM therefore determines:
Right Conditionally Established
during the relevant season and conditions.
The operator's historical use above that limit does not expand the right.
During severe water constraint, the existence of the right does not by itself determine the final Allocation.
RRGM establishes the Resource right.
RPAS and other competent Resource governance determine downstream Priority and Allocation.
118. Critical Distinctions
Claimed Resource Right ≠ Established Resource Right
Rights Claim ≠ Resource Right
Methodological Recognition ≠ Creation of External Legal Authority
Limited Resource Right ≠ Unlimited Resource Entitlement
Right to Resource A ≠ Right to Resource B
Right to Source A ≠ Right to Every Source of the Resource
Multiple Valid Resource Rights ≠ Sufficient Resource Capacity
Sole Current Use ≠ Exclusive Resource Right
Ownership ≠ Unlimited Resource Right
Possession ≠ Resource Entitlement
Historical Use ≠ Current Resource Right
Consumption ≠ Resource Right
Resource Demand ≠ Resource Right
Resource Dependency ≠ Resource Right
Resource Criticality ≠ Resource Right
Resource Value ≠ Resource Right
Resource Right ≠ Resource Availability
Eligibility ≠ Resource Right
Resource Right ≠ Active Access Authorization
Access Control ≠ Resource Right
Resource Right ≠ Highest Resource Priority
Resource Right ≠ Current Resource Allocation
Expired Right ≠ Current Resource Entitlement
Delegated Right ≠ Expanded Right
Resource Right ≠ Transfer Authority
Delegation ≠ Transfer
Uncertain Right ≠ Established Right
Rights Document Exists ≠ Resource Right Currently Valid
Former Right ≠ Current Right
Increased Resource Need ≠ Rights Expansion
Desired Allocation ≠ Resource Right Evidence
Machine Recognition of a Right ≠ Creation of the Right
119. Cross-Architecture Boundary
RRGM may consume:
RCHS — Resource identity and characterization.
RACS — Resource Availability and capacity context.
RDGS — Resource Demand context.
RDCS — Resource Dependency and Criticality context.
RAEM — Resource Access Eligibility evidence.
RACM — Access Control evidence where relevant to actual implementation.
GOA™ — Authority, Delegation, Accountability, and governance-boundary evidence.
OBIDENITY® — Origin, Identity, Ownership, Authority, Permission, Provenance, Transfer, and Continuity evidence where relevant.
ORA™ — Operational Reality evidence concerning actual Resource use.
LIGA™ — Liability evidence where rights conflict or misuse becomes liability-relevant.
RRGM does not absorb these mechanisms.
120. 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.
Ownership may provide evidence for a Resource right.
Identity establishes who the Right Holder is.
Authority: establishes whether the Rights Basis is legitimate.
Transfer mechanisms may establish rights continuity.
Operational evidence may establish whether the Resource is actually being used.
RRGM governs only their relevance to the Resource Right State within Resource Access Governance.
121. Canonical Boundary
RRGM governs how Resource-related Access rights and entitlements are identified, traced to a legitimate Rights Basis and Authority Origin, attached to a sufficiently identified Right Holder and Resource, bounded by scope and conditions, evidenced, validated, modified, delegated, transferred where permitted, restricted, suspended, expired, terminated, and reassessed.
RRGM does not create external legal rights, determine Resource Access eligibility, issue Resource Access authorization, implement technical Access Controls, establish Resource Priority, allocate Resource capacity, govern Resource Consumption, determine Scarcity response, or establish long-term Resource Sustainability.
Its principal governed output is the Resource Rights Profile .
122. Canonical Closing Statement
A Resource right does not exist merely because a Resource has been used, is needed, is valuable, or is critical to the actor that depends upon it.
RRGM establishes the rights layer explicitly — determining who holds what Resource entitlement, from which legitimate basis, within what scope and conditions, and with what continuity and evidence — so that Resource Access is governed by established rights rather than assumed entitlement.