RAEM — Resource Access Eligibility 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 Access Eligibility Governance
Module ID: RSGA-RAGS-RAEM-01
Origin ID: OOF-RSGA-RAGS-RAEM
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
RAEM — Resource Access Eligibility Module governs how a participant, system, function, organization, infrastructure component, autonomous system, or other governed actor is evaluated against the conditions required to become an eligible candidate for access to a defined Resource or Resource capacity, including how identity, role, purpose, qualification, location, operational conditions, technical conditions, and other materially relevant eligibility requirements are established, evidenced, assessed, and reassessed.
RAEM determines whether the governed actor qualifies to proceed within Resource Access Governance.
It does not itself grant Resource Access authorization.
Resource Access Eligibility ≠ Resource Access Authorization.
2. Operational Role
RAGS must determine who or what may legitimately access a Resource.
Before authority can authorize that Access, the relevant actor must be sufficiently identified and evaluated against applicable eligibility conditions.
RAEM establishes:
who or what is seeking Resource Access; which Resource is involved;
for what purpose Access is sought; which eligibility requirements apply; whether those requirements are satisfied; which conditions remain unresolved; what evidence supports the result; and when eligibility must be reassessed.
RAEM therefore establishes the qualification layer of Resource Access Governance.
3. Core Question
Does the sufficiently identified actor satisfy the conditions required to become an eligible candidate for access to the defined Resource or Resource capacity, for the stated purpose and under the relevant operational, temporal, spatial, technical, and governance conditions?
4. Position in RAGS Governance
Canonical RAGS progression:
Access Subject → Eligibility → Authority → Authorization → Scope & Limits → Conditions & Restrictions → Resource Access State
RAEM governs the:
Access Subject → Eligibility
transition.
It does not convert eligibility into permission.
5. Governed Space
RAEM governs:
Resource Access Eligibility Governance
This space concerns the identification, qualification, evidence, determination, maintenance, and reassessment of eligibility for Resource Access.
6. Governed Object
The primary Governed Object is:
A Resource Access Eligibility Relationship between a sufficiently identified actor and a defined Resource or Resource capacity for a defined purpose and context.
Canonical relationship:
**Actor
Resource Access Purpose Applicable Eligibility Requirements Evidence
Context → Resource Access Eligibility State**
7. Scope
RAEM governs:
Access Subject identification; Resource reference; Access purpose; eligibility criteria; role eligibility; functional eligibility; technical eligibility; operational eligibility; spatial eligibility; temporal eligibility; qualification requirements; condition-dependent eligibility; Resource-specific eligibility; evidence requirements; eligibility evidence; evidence sufficiency; eligibility conflict; eligibility uncertainty; Eligibility State; eligibility expiration; eligibility reassessment.
RAEM does not independently:
grant Resource Access authorization; establish Access Authority; determine final Access scope; allocate Resource capacity; determine Resource Priority; govern Resource Consumption; determine Scarcity response; establish long-term Sustainability.
8. Eligibility Principle
Eligibility answers:
May this actor legitimately be considered for this Resource Access?
It does not answer:
Has this actor been authorized to access the Resource?
Therefore:
Eligible Candidate ≠ Authorized Resource User.
9. Eligibility Is Relational
Eligibility is not necessarily a permanent property of an actor.
An actor may be eligible:
for Resource A but not Resource B; for Purpose A but not Purpose B; at Location A but not Location B; during Period A but not Period B; under Operating State A but not Operating State B.
Eligibility must therefore remain attached to its Resource and context.
10. Access Subject
RAEM begins with the Access Subject.
The Access Subject may be:
person; organization; public institution; facility; system; machine; autonomous system; AI system; operational function; infrastructure component; other governable actor.
11. Subject Identification
The Access Subject must be identified with sufficient precision for the relevant eligibility decision.
Required identity strength should reflect the Resource and governance context.
12. Identity Sufficiency
Identity is sufficient when the actor can be distinguished adequately for the intended eligibility determination.
Not every Resource context requires the same identity assurance.
13. Identity Ambiguity
Where materially different actors could be represented by the same identifier or identity record, eligibility should not be treated as established until the ambiguity is resolved or appropriately bounded.
14. Identity Boundary
RAEM uses identity evidence where required.
It does not absorb broader Identity Governance.
Where specialized Identity Governance is required, appropriate external mechanisms may supply the identity evidence.
15. Resource Identification
Eligibility must refer to a sufficiently characterized Resource.
The Resource should remain traceable to upstream RCHS characterization.
16. Resource-Specific Eligibility
Eligibility for one Resource does not automatically establish eligibility for another.
Eligible for Resource A ≠ Eligible for Resource B.
17. Resource Capacity Eligibility
Eligibility may apply to a defined class or amount of Resource capacity rather than the entire Resource.
Example:
an actor may be eligible for:
up to 5 MW of electricity access
without being eligible for unrestricted electrical capacity.
18. Resource Source Eligibility
Where governance requirements differ between Resource Sources, eligibility may be Source-specific.
Eligibility for Resource Source A ≠ Eligibility for Resource Source B.
19. Access Purpose
RAEM should establish the purpose for which Resource Access is sought where purpose materially affects eligibility.
Examples may include:
normal operations; essential service; production; maintenance; testing; research; emergency response; recovery; standby operation.
20. Purpose-Bound Eligibility
An actor may be eligible for Resource Access for one purpose but not another.
Eligibility for Purpose A ≠ Eligibility for Purpose B.
21. Declared Purpose
A declared purpose should not automatically be treated as validated eligibility evidence.
Where material, the purpose must be sufficiently evidenced.
22. Eligibility Requirements
Eligibility requirements are the conditions an actor must satisfy to qualify for consideration for Resource Access.
They may originate from:
law; regulation; policy; contract; Resource governance rules; infrastructure rules; safety requirements; technical requirements; organizational requirements; operational requirements; other competent governance sources.
23. Requirement Traceability
A material eligibility requirement should remain traceable to its governing basis where required.
This prevents arbitrary eligibility criteria from being introduced without legitimate origin.
24. Requirement Applicability
Not every eligibility requirement applies to every Access Subject.
RAEM should determine which requirements are applicable to the specific:
actor; Resource; purpose; location; time; operating condition.
25. Role Eligibility
Access may require the actor to hold a particular role.
Examples may include:
authorized operator; registered customer; public-service provider; maintenance provider; emergency responder; system controller.
Role must be sufficiently evidenced where material.
26. Functional Eligibility
Eligibility may depend upon the function for which the Resource is required.
A function should not be considered eligible merely because the actor operating it has broader Resource Access elsewhere.
27. Technical Eligibility
Some Resources may require technical conditions before an actor qualifies for Access.
Examples may include:
compatible interface; connection capability; required equipment; technical certification; safe operating configuration; metering capability.
28. Technical Eligibility Boundary
Technical capability may be necessary for eligibility.
It does not establish Access authorization.
Technical Eligibility ≠ Resource Access Authority.
29. Operational Eligibility
Eligibility may depend upon current operational conditions.
An actor may qualify only during:
normal operation; maintenance; emergency; recovery; specific production state; other defined operating conditions.
30. Spatial Eligibility
Resource Access eligibility may depend upon location.
Examples include:
service territory; facility; network node; infrastructure zone; jurisdiction; delivery region.
31. Temporal Eligibility
Eligibility may apply only within a defined period.
Examples include:
contract period; season; scheduled window; emergency period; temporary operating period.
32. Conditional Eligibility
Eligibility may exist only while defined conditions remain satisfied.
Examples:
valid certification; active role; technical compliance; location requirement; operational condition; contract status.
33. Persistent Eligibility
Some eligibility relationships may remain valid until a material change occurs.
Persistent eligibility still requires reassessment when relevant conditions change.
34. Temporary Eligibility
Temporary eligibility should preserve:
start condition; end condition; purpose; Resource; actor; evidence.
35. Emergency Eligibility
Emergency conditions may create a special eligibility pathway.
Emergency status does not itself create authorization.
Emergency Eligibility ≠ Emergency Access Authorization.
36. Qualification
Qualification is evidence that an actor possesses a required capability, status, role, certification, or other condition relevant to eligibility.
Qualification is one possible component of eligibility.
It is not synonymous with eligibility itself.
37. Qualification Boundary
Qualification ≠ Eligibility by definition.
An actor may hold a required qualification while failing another applicable eligibility requirement.
38. Multiple Eligibility Requirements
Eligibility may depend upon several requirements simultaneously.
Canonical logic:
**Requirement A
Requirement B Requirement C → Eligibility only where the applicable combination is satisfied.**
39. Mandatory Requirement
A mandatory requirement must be satisfied before eligibility can be established unless competent governance explicitly provides an alternative pathway.
40. Conditional Requirement
A conditional requirement applies only when its triggering condition is present.
41. Alternative Eligibility Path
Some Resource Access systems may permit multiple legitimate pathways to eligibility.
Example:
Eligibility Path A
or:
Eligibility Path B
may each independently establish candidate eligibility.
The applicable pathway must remain explicit.
42. Eligibility Exception
Where legitimate governance permits an exception to a normal eligibility requirement, the exception should preserve:
authority; reason; scope; Resource; actor; duration; conditions; evidence.
43. Exception Boundary
Eligibility Exception ≠ Removal of Governance.
An exception is itself a governed state.
44. Eligibility and Resource Demand
A valid Resource Demand Profile may support the eligibility purpose.
It does not establish eligibility automatically.
Validated Resource Demand ≠ Resource Access Eligibility.
45. Eligibility and Dependency
A Resource Dependency may explain why an actor seeks Access.
It does not establish eligibility automatically.
Resource Dependency ≠ Resource Access Eligibility.
46. Eligibility and Criticality
Criticality may increase the operational importance of obtaining Resource Access.
It does not establish eligibility.
Resource Criticality ≠ Resource Access Eligibility.
47. Eligibility and Availability
Resource capacity may be available even when no actor is currently eligible to access it.
Conversely, an actor may remain eligible while Resource capacity is unavailable.
Resource Availability ≠ Resource Access Eligibility.
48. Eligibility and Practical Accessibility
Physical or technical Resource accessibility may be relevant to the practical usefulness of eligibility.
It does not itself establish eligibility.
Practical Accessibility ≠ Resource Access Eligibility.
49. Eligibility and Ownership
Ownership may form part of an eligibility basis in some contexts.
It does not automatically establish eligibility for every Resource use.
Ownership ≠ Universal Resource Access Eligibility.
50. Eligibility and Historical Use
Historical Resource use may provide evidence.
It does not automatically establish current eligibility.
Historical Access ≠ Current Eligibility.
51. Eligibility and Existing Consumption
An actor already consuming the Resource may still lack valid eligibility under current governance requirements.
Existing Consumption ≠ Eligibility Evidence by itself.
52. Eligibility and Value
Economic or operational Value does not create Resource Access eligibility.
High Value ≠ Eligibility.
53. Eligibility and Priority
Eligibility establishes whether an actor may proceed within Resource Access Governance.
It does not determine comparative Resource Priority.
Eligibility ≠ Priority.
54. Eligibility and Allocation
An eligible actor has not necessarily received any Resource.
Eligibility ≠ Allocation.
55. Eligibility and Authorization
Authorization requires competent Access Authority.
RAEM does not issue that authorization merely because eligibility is established.
Eligibility ≠ Authorization.
56. Eligibility Evidence
RAEM should preserve evidence supporting each material eligibility requirement.
Evidence may include:
identity records; role records; qualification records; technical certification; operational status; contractual evidence; location evidence; purpose evidence; institutional evidence; other relevant records.
57. Evidence Provenance
Material eligibility evidence should preserve where relevant:
source; issuer; subject; Resource relevance; time; version;
validity; scope.
58. Evidence Validity
Evidence may exist while no longer being valid.
Examples include:
expired certification; terminated contract; changed role; obsolete technical approval.
Evidence Existence ≠ Evidence Validity.
59. Evidence Freshness
Eligibility should not rely upon stale evidence where a material condition may have changed.
60. Evidence Sufficiency
Evidence is sufficient where it adequately supports the eligibility determination required for the intended Access context.
Maximum possible evidence is not required.
Materially sufficient evidence is required.
61. Evidence Gap
An Evidence Gap is material where missing evidence could change the Eligibility State.
62. Non-Material Evidence Gap
Missing information that cannot materially affect eligibility should not automatically prevent determination.
63. Evidence Conflict
Credible evidence may disagree regarding an eligibility condition.
Material conflict must remain visible until resolved or legitimately bounded.
64. Eligibility Conflict
Eligibility Conflict may arise from:
identity disagreement; role disagreement; qualification disagreement; purpose disagreement; location disagreement; technical-status disagreement; contract-status disagreement; requirement interpretation conflict.
65. Conflict Resolution
Canonical logic:
Conflicting Eligibility Evidence → Subject Check → Resource Check → Requirement Check → Scope Check → Time Check → Evidence Validity Check → Competent Resolution → Eligibility Redetermination
66. Eligibility Uncertainty
Uncertainty may concern:
identity; requirement applicability; qualification; purpose; location; technical condition; operational state; evidence validity.
67. Uncertainty Propagation
Material uncertainty must remain visible in the Eligibility State.
RAEM must not convert unresolved eligibility into confirmed eligibility merely because downstream Resource Access is operationally desirable.
68. Eligibility State
RAEM expresses its determination through a governed Resource Access Eligibility State.
69. Minimum Eligibility States
At minimum:
Eligible
Conditionally Eligible
Partially Eligible
Not Eligible
Eligibility Evidence-Limited
Eligibility Conflicted
Eligibility Unknown
Eligibility Unresolved
70. Eligible
The actor satisfies the applicable eligibility requirements for the defined Resource Access context.
71. Conditionally Eligible
Eligibility is established only while explicit conditions remain satisfied.
72. Partially Eligible
Some applicable eligibility requirements are satisfied while other material requirements remain incomplete.
Partial eligibility does not establish full eligibility.
73. Not Eligible
The actor fails one or more requirements necessary for the relevant eligibility pathway.
74. Eligibility Evidence-Limited
Available evidence does not support a stronger determination.
75. Eligibility Conflicted
Credible evidence supports materially incompatible Eligibility States.
76. Eligibility Unknown
Available evidence does not permit the relevant eligibility conditions to be established.
77. Eligibility Unresolved
Relevant evidence exists but final eligibility cannot yet be determined.
78. Eligibility State Context
An Eligibility State should remain attached to:
actor; Resource; purpose; location where relevant; time where relevant; operating conditions where relevant.
Removing this context may materially change its meaning.
79. Eligibility Duration
Eligibility may have:
defined duration; conditional duration; open duration subject to reassessment; event-bound duration.
80. Eligibility Expiration
Eligibility may expire when:
qualification expires; contract ends; role ends; time window closes; emergency ends; technical condition changes; another governing condition ceases.
81. Eligibility Continuation
Eligibility should continue only while material requirements remain satisfied.
82. Eligibility Reassessment
Eligibility must be reassessed where material conditions change.
83. Reassessment Triggers
Triggers may include:
identity change; role change; purpose change; Resource change; Resource Source change; location change; qualification expiration; technical change; operational-state change; contract change; policy change; new evidence; evidence conflict; emergency activation or termination.
84. Reassessment Proportionality
Not every contextual change requires complete eligibility reconstruction.
Only changes capable of materially affecting the Eligibility State require relevant reassessment.
85. Targeted Reassessment
Where one eligibility condition changes, RAEM should reassess the affected condition and its impact rather than mechanically rebuilding every unrelated element.
86. Eligibility Versioning
A material change to the Eligibility State should create a new governed version where traceability requires it.
87. Historical Eligibility
Previous Eligibility States should remain distinguishable from current eligibility.
Previously Eligible ≠ Currently Eligible.
88. Eligibility Traceability
A Resource Access Eligibility determination should remain traceable through:
Eligibility State → Applicable Requirements → Eligibility Evidence → Access Purpose → Resource → Access Subject.
89. Eligibility Explainability
A governed eligibility determination should be able to explain materially:
who or what was evaluated; for which Resource; for what purpose; against which requirements; which requirements were satisfied; which were not; which evidence was used; what uncertainty remains.
90. Eligibility Auditability
Where required, historical eligibility decisions should remain reconstructable.
This includes changes in:
requirements; evidence; conditions; Eligibility State; reassessment outcome.
91. Eligibility Minimality
RAEM should request only evidence necessary to establish materially relevant eligibility conditions.
Eligibility Governance should not become unrestricted information collection.
92. Requirement Minimality
Only requirements legitimately relevant to the Resource Access context should influence eligibility.
Arbitrary requirements should not be introduced merely to include or exclude a preferred actor.
93. Outcome Independence
Eligibility must follow applicable requirements and evidence rather than the preferred downstream Resource decision.
Desired Access Outcome ≠ Eligibility Evidence.
94. Non-Discretionary Integrity
Where eligibility requirements are objective, equivalent evidence should produce equivalent eligibility treatment under equivalent conditions.
95. Contextual Difference
Equivalent treatment does not require identical eligibility outcomes where material context differs.
Different:
Resources; purposes; locations; technical conditions; time periods
may legitimately produce different Eligibility States.
96. Automated Eligibility Evaluation
Eligibility may be evaluated partially or fully by automated systems.
Automation does not create eligibility requirements or Access authority.
It executes the governed methodology.
97. Automated Evaluation Boundary
Automated Eligibility Determination ≠ Resource Access Authorization.
The downstream authorization mechanism remains separate.
98. Machine-Readable Eligibility
Where machine implementation is used, RAEM should permit structured representation of:
actor; Resource; purpose; requirements; evidence; conditions;
Eligibility State; uncertainty; validity; version.
99. Eligibility Rule Change
When an eligibility rule changes, affected existing Eligibility States should be identified for reassessment where the change is material.
100. Retroactivity Boundary
A new eligibility requirement should not automatically be assumed to invalidate historical Eligibility States unless the governing authority establishes that effect.
101. Access Eligibility Profile
The principal RAEM output is the:
Resource Access Eligibility Profile
It represents the governed eligibility relationship between the actor and Resource.
102. Minimum Resource Access Eligibility Profile Fields
At minimum:
Eligibility ID
Access Subject ID
Resource ID
Resource Source where relevant
Access Purpose
Eligibility Requirement Set
Applicable Requirements
Satisfied Requirements
Unsatisfied Requirements
Conditional Requirements
Qualification State where relevant
Technical Eligibility State where relevant
Operational Eligibility State where relevant
Spatial Eligibility State where relevant
Temporal Eligibility State where relevant
Evidence Basis
Evidence Sufficiency
Eligibility Uncertainty
Eligibility State
Effective Time
Expiration where relevant
Reassessment Trigger
Version:
103. Eligibility Requirement Record
Where implementation requires detailed traceability, each material requirement may preserve:
Requirement ID; Requirement Source; Requirement Description; Applicability; Evidence Reference; Requirement State; Validity Period; Uncertainty.
104. Requirement States
A minimum implementation may distinguish:
Satisfied
Conditionally Satisfied
Unsatisfied
Evidence-Limited
Conflicted
Unknown
Not Applicable
105. Aggregate Eligibility
The final Eligibility State should reflect the combination of applicable requirement states according to the governed eligibility logic.
106. Aggregate Boundary
A numerical average of eligibility requirements should not automatically establish eligibility.
A single mandatory unsatisfied requirement may be decisive.
107. Eligibility Scoring
Implementations may use scores where useful.
A score must not override mandatory eligibility conditions.
Eligibility Score ≠ Eligibility Authority.
108. Minimum Implementation Framework
A minimum operational RAEM implementation should contain seven governed layers.
Layer 1 — Subject & Resource Identification
Establish:
Access Subject Resource Resource Source where relevant
Layer 2 — Purpose
Establish:
Access Purpose Function Relevant operating context
Layer 3 — Requirement Identification
Determine:
Applicable eligibility requirements Requirement source Mandatory / conditional status
Layer 4 — Evidence
Collect and validate:
Identity evidence Role evidence Qualification evidence Technical evidence Operational evidence Other required evidence
Layer 5 — Requirement Evaluation
Determine:
Satisfied Conditionally Satisfied Unsatisfied Evidence-Limited Conflicted Unknown Not Applicable
Layer 6 — Eligibility Determination
Determine:
Eligibility State Conditions Uncertainty Validity period
Layer 7 — Governed Output
Produce:
Resource Access Eligibility Profile Evidence Sufficiency State Reassessment Triggers Version
Canonical machine-readable logic:
**Actor
Resource Purpose → Applicable Eligibility Requirements → Evidence → Requirement States → Conflict / Uncertainty → Eligibility State → Resource Access Eligibility Profile**
109. Minimum Decision States
RAEM must support at least:
Eligible
Conditionally Eligible
Partially Eligible
Not Eligible
Eligibility Evidence-Limited
Eligibility Conflicted
Eligibility Unknown
Eligibility Unresolved
These states should remain distinguishable in downstream Resource Access Governance.
110. Minimum Evidence Path
Where eligibility cannot be determined:
Eligibility Unresolved → Material Eligibility Gap → Applicable Requirement → Minimum Evidence Requirement → Evidence Acquisition / Verification → Requirement Reassessment → Eligibility Redetermination → Updated Resource Access Eligibility Profile
RAEM should request only evidence capable of materially resolving eligibility.
111. Minimum Reassessment Framework
At minimum:
Current Eligibility Profile → Material Change / New Evidence → Materiality Test → Affected Requirement Identification → Targeted Reassessment → Eligibility Redetermination → Profile Retained or Revised → Version Update
112. Governance Requirements
A conforming RAEM implementation must:
1. identify the Access Subject; 2. identify the Resource; 3. preserve Resource identity from upstream characterization; 4. identify Resource Source where eligibility is Source-specific; 5. establish Access purpose where material; 6. identify applicable eligibility requirements; 7. preserve requirement origin where material; 8. distinguish mandatory from conditional requirements; 9. identify applicable alternative eligibility pathways; 10. evaluate role eligibility where relevant; 11. evaluate functional eligibility where relevant; 12. evaluate technical eligibility where relevant; 13. evaluate operational eligibility where relevant; 14. evaluate spatial eligibility where relevant; 15. evaluate temporal eligibility where relevant; 16. preserve qualification evidence; 17. preserve evidence provenance; 18. evaluate evidence validity; 19. evaluate evidence freshness; 20. determine evidence sufficiency; 21. preserve material Evidence Gaps; 22. preserve material evidence conflicts; 23. preserve material uncertainty; 24. determine requirement states; 25. determine an Eligibility State; 26. preserve conditional eligibility; 27. preserve eligibility duration; 28. support expiration; 29. support reassessment; 30. support versioning; 31. preserve historical Eligibility States; 32. distinguish eligibility from authorization; 33. distinguish eligibility from Resource Demand; 34. distinguish eligibility from Resource Dependency; 35. distinguish eligibility from Criticality; 36. distinguish eligibility from Resource Priority; 37. distinguish eligibility from Resource Allocation; 38. prevent technical capability from becoming Access Authority; 39. prevent historical use from becoming automatic eligibility; 40. produce a Resource Access Eligibility Profile.
113. Governance Logic
Canonical RAEM logic:
**Access Subject
Resource
Access Purpose → Applicable Eligibility Requirements → Requirement Evidence → Evidence Validity → Requirement Evaluation → Conflict & Uncertainty → Eligibility Determination → Resource Access Eligibility Profile**
Where evidence is insufficient:
Eligibility Gap → Minimum Evidence Requirement → Evidence Acquisition → Requirement Reassessment → Eligibility Redetermination
114. Governance Outputs
RAEM may produce:
Resource Access Eligibility Profile
Eligibility State
Eligibility Requirement Set
Requirement States
Qualification State
Technical Eligibility State
Operational Eligibility State
Spatial Eligibility State
Temporal Eligibility State
Eligibility Condition
Evidence Sufficiency State
Evidence Conflict State
Eligibility Uncertainty
Effective Time
Expiration
Reassessment Trigger
Version:
These outputs become governed inputs to subsequent Resource Access mechanisms.
115. Failure Conditions
RAEM should not be considered sufficiently completed where:
Access Subject identity is materially ambiguous; Resource identity is unclear; Access purpose is missing where purpose affects eligibility;
eligibility requirements lack legitimate basis; inapplicable requirements are used to exclude an actor; mandatory requirements are ignored; technical capability is treated as authorization; Resource Demand is treated as eligibility; Resource Dependency is treated as eligibility; Criticality is treated as eligibility; Value is treated as eligibility; historical Access is treated as current eligibility; existing consumption is treated as sufficient eligibility evidence; expired evidence is treated as valid; material evidence conflict is hidden; material uncertainty is suppressed; conditional eligibility is represented as unconditional; partial eligibility is represented as full eligibility; an eligibility score overrides a mandatory requirement; eligibility is manipulated to produce a preferred downstream Allocation; eligibility is treated as Resource Access authorization.
116. Use Case 1 — AI Data Center Compute Access Eligibility
An AI data center provides multiple compute environments.
A research workload requests access to a high-capacity GPU cluster.
RAEM identifies:
Access Subject — Research Workload / Responsible Operator
Resource — Defined GPU Compute Capacity
Purpose — Model Training
Applicable eligibility requirements may include:
recognized workload identity; approved workload category; technical compatibility; facility eligibility; security requirements; permitted operating environment; valid project status.
The workload satisfies all mandatory requirements.
RAEM determines:
Eligibility State — Eligible
and produces a:
Resource Access Eligibility Profile.
This does not grant GPU capacity.
The relevant Access Authority must still authorize Access, and downstream governance may still determine Resource Priority and Allocation.
117. Use Case 2 — Regional Water Access Eligibility
An industrial facility seeks access to a regional water system.
RAEM evaluates:
facility identity; Resource requested; location; intended use; technical connection requirements; applicable eligibility conditions; required qualifications or permits where relevant; evidence validity.
The facility satisfies the general location and technical requirements, but one required condition remains pending.
RAEM determines:
Eligibility State — Partially Eligible
rather than representing the facility as fully eligible.
Once the missing requirement is sufficiently established, RAEM may reassess the profile.
Even after:
Eligibility State — Eligible
is reached, Resource Access authorization remains a separate RAGS mechanism.
118. Critical Distinctions
Resource Access Eligibility ≠ Resource Access Authorization
Eligible Candidate ≠ Authorized Resource User
Eligibility for Resource A ≠ Eligibility for Resource B
Eligibility for Purpose A ≠ Eligibility for Purpose B
Technical Eligibility ≠ Resource Access Authority
Emergency Eligibility ≠ Emergency Access Authorization
Qualification ≠ Eligibility by definition
Eligibility Exception ≠ Removal of Governance
Validated Resource Demand ≠ Resource Access Eligibility
Resource Dependency ≠ Resource Access Eligibility
Resource Criticality ≠ Resource Access Eligibility
Resource Availability ≠ Resource Access Eligibility
Practical Accessibility ≠ Resource Access Eligibility
Ownership ≠ Universal Resource Access Eligibility
Historical Access ≠ Current Eligibility
Existing Consumption ≠ Eligibility Evidence by itself
High Value ≠ Eligibility
Eligibility ≠ Priority
Eligibility ≠ Allocation
Eligibility ≠ Authorization
Evidence Existence ≠ Evidence Validity
Previously Eligible ≠ Currently Eligible
Desired Access Outcome ≠ Eligibility Evidence
Automated Eligibility Determination ≠ Resource Access Authorization
Eligibility Score ≠ Eligibility Authority
119. Cross-Architecture Boundary
RAEM may consume:
RCHS — Resource identity and characterization.
RACS — Resource Availability and practical accessibility context.
RDGS — Resource Demand context.
RDCS — Resource Dependency and Criticality context.
GOA™ — Authority and governance-boundary evidence where relevant.
OBIDENITY® — Identity, Origin, Ownership, Authority, Permission, and Provenance evidence where relevant.
AGI™ / ASGA™ — autonomous agent or autonomous-system identity and authority context where relevant.
ORA™ — Operational Reality evidence.
PGA™ — predicted future conditions where eligibility is future-dependent.
RAEM does not absorb those 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.
Identity evidence may support eligibility.
Technical evidence may support eligibility.
Resource Demand may explain the purpose of Access.
Criticality may explain the operational significance of Access.
None of these mechanisms independently establish Resource Access Eligibility unless the applicable eligibility requirements are satisfied.
121. Canonical Boundary
RAEM governs whether a sufficiently identified actor satisfies the applicable conditions required to become an eligible candidate for access to a defined Resource or Resource capacity for a defined purpose and context, including the identification of applicable requirements, evidence, qualification, conditions, uncertainty, conflict, validity, and reassessment.
RAEM does not grant Resource Access authorization, create Access Authority, determine final Resource Access scope, 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 Access Eligibility Profile .
122. Canonical Closing Statement
A Resource need does not make an actor eligible, and eligibility does not make the actor authorized.
RAEM establishes the qualification boundary first — determining who or what legitimately qualifies to proceed toward Resource Access, for which Resource, for what purpose, under which requirements, and on what evidence — before permission to access that Resource can be granted.