HCRM — Harm Context Relationship Module

OOF® Origin Open Foundation®

Independent Methodological Authority

Canonical Definition

The HCRM — Harm Context Relationship Module governs how materially
relevant relationships among Harm Context elements are identified,
distinguished, qualified, structured, updated, and preserved so that
subjects, objects, systems, domains, temporal states, environmental
conditions, operational mechanisms, and other Harm-relevant elements can
be understood in relation to one another without converting contextual
association into causation, accountability, responsibility, or liability.

HCRM establishes the transition:

Governed Harm Context + Harm Subject Map + Harm Domain Context + Harm
Temporal Context → Relationship Identification → Relationship
Qualification → Relationship Structure → Relationship Sufficiency →
Governed Harm Context Relationship Map

Its central question is:

Which relationships among Harm-relevant elements must be governed in order
to understand the Harm Context without overstating what those
relationships prove?

Operational Role

Harm Context does not become meaningful merely because its elements have
been identified.

A person may be present.

A machine may be operating.

An AI system may have produced an output.

A harmful consequence may appear later.

An organization may control the relevant process.

An environmental condition may persist.

These facts become methodologically useful only when their relevant
relationships are understood.

HCRM provides that relational structure.

Its responsibility is:

to govern how Harm Context elements relate without allowing relationship
to become an unsupported conclusion about cause, responsibility, or
liability.

Position Within Harm Context Standard (HCS)

The internal flow is:

Harm Context Mapping → Harm Subject Mapping → Harm Domain Context → Harm
Temporal Context → Harm Context Relationships

HCRM completes the Harm Context Standard by linking the elements already
established by the preceding modules.

Its output provides the relational foundation required for subsequent Harm
Exposure governance.

Governed Object

The governed object is the Harm Context Relationship Map.

It represents materially relevant relationships among Harm Context
elements.

These may include relationships between:

subject and object
subject and system
subject and environment
system and system
system and condition
domain and domain
condition and time period
event and effect
organization and process
action and operational state
exposure condition and subject
upstream and downstream elements

Relationship Governance Trigger

HCRM activates where understanding the Harm Context requires more than
knowing that individual elements exist.

The trigger arises when the relation between two or more elements could
materially affect downstream Harm governance.

Co-Presence ≠ Material Relationship

A relationship should be governed because it matters, not merely because
elements occur within the same broader context.

Relationship Identification

HCRM identifies which contextual elements are meaningfully connected.

A relationship may be:

Direct

Indirect

Sequential

Concurrent

Dependent

Conditional

Operational

Physical

Digital

Organizational

Environmental

Informational

Temporal

Domain-Based

or otherwise materially relevant.

Relationship Relevance

A relationship is materially relevant where its inclusion may affect:

Harm Exposure interpretation
Harm Emergence understanding
Harm Boundary formation
Harm Determination readiness
Harm Change or Propagation analysis
Containment or Mitigation context
recovery understanding
downstream governance handoffs

Observable Relationship ≠ Governance-Relevant Relationship by Default

Direct Relationship

A Direct Relationship exists where two elements have an immediate
Harm-relevant connection.

Examples may include:

Subject ↔ Physical Object

User ↔ AI Output

System ↔ Affected System

Person ↔ Environmental Condition

Directness concerns relationship structure.

It does not establish Harm or causation.

Indirect Relationship

An Indirect Relationship exists through one or more intermediate elements.

Conceptually:

A → B → C

The relationship between A and C may still be materially relevant.

Indirect Relationship ≠ Weak Relationship by Default

Multi-Step Relationship

Some contexts require several relational steps.

Example:

AI System → Organizational Process → Decision → Subject → Consequence

HCRM must preserve multi-step structure without collapsing it into:

AI System → Harm

unless downstream governance legitimately supports that conclusion.

Physical Relationship

Physical relationships may include:

Proximity

Contact

Force Transfer

Movement Interaction

Shared Physical Environment

Material Transfer

These relationships may be Harm-relevant.

They do not themselves establish Harm.

Physical Relationship ≠ Physical Harm

Digital Relationship

Digital relationships may include:

Data Flow

Access

System Interaction

Information Transfer

Control Signal

Digital Dependency

Shared Digital Environment

A digital relationship may produce no physical interaction while remaining
highly relevant to Harm governance.

Informational Relationship

Information may create contextual relationships between:

Source

Content

Recipient

Decision Process

Downstream Action

HCRM may represent this structure where information contributes materially
to Harm Context.

Information Flow ≠ Decision Authority

Organizational Relationship

Organizational relationships may include:

Employment

Management

Control

Delegation

Supervision

Process Ownership

Service Relationship

Contractual Relationship

HCRM may represent these relationships contextually.

It does not determine accountability or legal responsibility.

Operational Relationship

Operational relationships describe how elements participate within a
real-world process.

Examples:

Operator ↔ Machine

System ↔ Workflow

Agent ↔ Tool

Process ↔ Environment

ORA™ governs Operational Reality.

HCRM governs the relationship only insofar as it becomes relevant to Harm
Context.

Environmental Relationship

Environmental Harm Context may involve relationships among:

Source Condition

Medium

Environment

Population

Infrastructure

Ecosystem

HCRM must support such structures even where no single actor is
immediately identifiable.

Subject-to-Subject Relationship

Subjects may be related through:

Shared Exposure

Dependency

Shared Environment

Common Process

Transmission

Collective Condition

Common Downstream Effect

The existence of a relationship does not establish identical Harm.

Shared Relationship ≠ Shared Harm State

Subject-to-System Relationship

A subject may:

Operate

Use

Depend Upon

Be Exposed To

Be Controlled By

Receive Output From

Be Affected By

a system.

These relationships must remain semantically distinct.

System Use ≠ System Dependence

System Dependence ≠ System Causation

System-to-System Relationship

Modern Harm may arise within interconnected systems.

HCRM should support:

Upstream System

Dependent System

Interacting System

Coordinated System

Downstream System

External System

without assuming which system caused Harm.

Human-AI Relationship

Human-AI Harm Context may include:

Human → AI Input

AI → Output

Human → Interpretation

Human → Decision

System → Execution

or other configurations.

HCRM preserves the actual relationship structure.

It must not assume that the presence of a human transfers all
responsibility to the human or that AI involvement transfers all
responsibility to the AI provider.

Autonomous-System Relationship

Autonomous systems may operate through:

Perception → Interpretation → Decision → Authorization → Action →
Observation

HCRM may represent materially relevant relationships between system,
environment, affected subject, and consequence.

ASGA™ governs autonomous operation.

HCRM governs Harm Context relationships.

Relationship to Operational Mechanism

An operational mechanism may be contextually related to a Harm-relevant
consequence.

HCRM may represent:

Mechanism ↔ Condition ↔ Effect

but must preserve:

Operational Mechanism Relationship ≠ Harm Causation Determination

Relationship to Harm Domain

A Harm Context relationship may connect different domains.

Example:

Digital Condition ↔ Financial Consequence

or:

Physical Exposure ↔ Medical Consequence

HDCM governs the domain structure.

HCRM governs the relationship among those domain-specific elements.

Relationship to Time

Relationships may exist only during certain temporal intervals.

Conceptually:

Relationship Active: t1–t2

Relationship Inactive: t2–t3

Relationship Re-established: t3–t4

HCRM must remain compatible with HTCM temporal governance.

Persistent Relationship

Some relationships continue over time.

Examples may include:

Dependency

Organizational Control

Long-Term Exposure Relationship

Service Relationship

Infrastructure Dependence

Persistence may materially affect Harm Context.

Persistent Relationship ≠ Persistent Harm

Temporary Relationship

A short-lived relationship may still be Harm-relevant.

For example:

Brief Contact

Temporary System Access

Short Exposure

One-Time Data Transfer

Duration alone does not determine importance.

Recurrent Relationship

A relationship may repeatedly reappear.

Conceptually:

R₁ → gap → R₂ → gap → R₃

Recurrent relationships may contribute to accumulated or repeated Harm
Context.

HCRM preserves recurrence.

Conditional Relationship

Some relationships exist only if specified conditions are met.

Conceptually:

If Condition X → Relationship Y becomes active

This is important where system, organizational, or environmental
relationships are contingent rather than permanent.

Dependency Relationship

A Dependency Relationship exists where one subject, system, organization,
or infrastructure component relies materially upon another.

Dependency may shape Harm consequence or propagation.

But:

Dependency ≠ Causation

Dependency ≠ Accountability

Control Relationship

A Control Relationship may be relevant where one actor, system, or
organization materially directs or constrains another.

HCRM may represent the relationship.

AGA™ governs accountability and authority questions where applicable.

Control Relationship ≠ Liability Determination

Authority Relationship

Where authority matters contextually, HCRM may represent that
relationship.

GOA™ or AGA™ may govern authority itself.

HCRM consumes the governed relationship where it is materially relevant to
Harm Context.

Authority Relationship ≠ Harm Responsibility

Delegation Relationship

Delegation may create a Harm-relevant relational structure.

For example:

Authority Holder → Delegate → Operational Action

HCRM may preserve the contextual chain.

It does not determine whether delegation was legitimate or whether
liability follows.

Ownership Relationship

Ownership may materially affect Harm Context where an object, asset,
system, or infrastructure is involved.

OBIDENITY® may govern ownership and origin-bound identity where
applicable.

HCRM may consume that relationship.

Ownership ≠ Responsibility

Permission Relationship

Permission may determine whether an action was permitted within the
relevant context.

Where this relationship is material, HCRM may represent it.

Permission governance remains outside HCRM.

Permission ≠ Safety

Permission ≠ No Harm

Exposure Relationship

HCRM may identify that a potentially affected subject is connected to a
Harm-relevant condition in a manner requiring Exposure governance.

Conceptually:

Subject ↔ Harm-Relevant Condition

HES subsequently determines whether and under what conditions exposure
exists.

Contextual Exposure Relationship ≠ Established Exposure

Proximity Relationship

Physical, temporal, operational, digital, or organizational proximity may
be relevant.

However:

Proximity ≠ Causation

Proximity ≠ Harm

HCRM must not allow nearness to substitute for substantive relationship.

Sequential Relationship

Where A precedes B, HCRM may preserve:

A → B

This is a temporal and structural fact.

It does not establish:

A caused B

Before ≠ Because

Concurrent Relationship

Two elements may occur simultaneously.

Concurrent states may be materially relevant.

But:

Concurrent ≠ Causal

Parallel occurrence must remain distinct from causal dependence.

Correlated Relationship

Where two conditions vary together, correlation may be relevant context.

HCRM may preserve that relationship where sufficiently supported.

Correlation ≠ Causation

This distinction must remain explicit.

Association Relationship

Association is the broadest contextual relationship.

It may reflect:

shared environment
shared process
temporal connection
operational connection
informational connection
repeated co-occurrence

Association must never be treated automatically as cause.

Association ≠ Causation

Possible Causal Relevance

HCRM may flag a relationship as potentially relevant to future causal
analysis.

This does not establish causation.

Possible states may include:

Causally Relevant for Further Governance

Possible Causal Relationship

Disputed Causal Relationship

No Causal Position Established

HCRM stops before independent causal determination.

Relationship Strength

Where useful, HCRM may qualify contextual relationships as:

Established

Strongly Supported

Supported

Possible

Disputed

Unsupported

Unknown

The qualification must reflect the relationship itself.

It must not be interpreted automatically as Harm probability.

Relationship Direction

Some relationships are directional.

Example:

A → B

Others may be bidirectional:

A ↔ B

Direction should be represented only where legitimately supported.

Relationship Direction ≠ Causal Direction by Default

Relationship Asymmetry

Two elements may have an unequal relationship.

For example:

System A depends on System B

does not imply:

System B depends on System A

HCRM must preserve asymmetry where material.

Relationship Multiplicity

Two elements may have more than one relationship simultaneously.

For example:

Person ↔ Organization

may involve:

Employment + Supervision + Dependency + Exposure

HCRM must preserve materially different relationship types rather than
collapsing them into one generic link.

Relationship Conflict

Different sources may describe the same relationship differently.

Example:

Source A: Direct Control

Source B: Advisory Relationship

HCRM must preserve material disagreement.

Conflicting Relationship Claims ≠ Permission to Select Preferred Narrative

Relationship Uncertainty

Where relationship existence, type, strength, direction, or duration is
uncertain, that uncertainty must remain explicit.

Possible states may include:

Established

Partially Established

Claimed

Disputed

Unknown

Unable to Determine

Missing Relationship

A Harm Context may contain known elements whose relationship remains
unknown.

This must be representable.

Known Elements ≠ Known Relationship

Missing relationship knowledge should not be silently filled through
inference.

Relationship Boundary

HCRM must distinguish the relationships that belong to current Harm
Context from those that are merely background information.

The relationship boundary should follow material Harm relevance.

Existing Relationship ≠ Harm-Relevant Relationship by Default

Relationship Expansion

New information may reveal additional material relationships.

Conceptually:

R₁ → R₁ + R₂ → R₁ + R₂ + R₃

Expansion should remain traceable.

The earlier map must remain reconstructable.

Relationship Contraction

A previously mapped relationship may later be removed or downgraded where
sufficient governance shows that it is unsupported or immaterial.

Current Relationship Map ≠ Historical Relationship Map

Relationship Reassessment

Reassessment may be required where:

new subjects appear
new systems are identified
temporal understanding changes
domain interpretation expands
new evidence supports or weakens a relationship
an operational dependency is discovered
an assumed relationship is disproven
Harm propagation reveals downstream links

Reassessment must preserve historical states.

Relationship Versioning

Materially changed relationship maps should remain reconstructable.

Conceptually:

Relationship Map₁ → Relationship Map₂ → Relationship Map₃

Each material state should preserve what relationships were understood at
the time.

Relationship Sufficiency

The relationship structure is sufficiently governed when downstream Harm
governance can proceed without relying on material unstated, conflated, or
unsupported relationships.

The governing test is:

Would the next Harm governance step materially change if one of the
currently assumed relationships were wrong, missing, or misunderstood?

If yes:

→ further relationship governance is required.

Cross-Architecture Relationship Boundary

HCRM may consume governed relationships from adjacent architectures.

Examples:

ORA™ — operational relationships
AGA™ — accountability and authority relationships
AIG® — AI behavioral relationships
ASGA™ — autonomous-operation relationships
OBIDENITY® — identity, ownership, authority, permission,
provenance

relationships; - ADIT® — evidence supporting relationship claims; -
VALIDOS™ — validation of relationship claims where applicable.

HCRM does not take ownership of those governed spaces.

Its purpose is to determine how such relationships matter within Harm
Context.

Enterprise Application

HCRM can be applied across:

healthcare
industrial operations
construction
transportation
financial systems
digital platforms
AI systems
autonomous systems
robotics
organizational governance
infrastructure
environmental governance
supply chains
public services
human-AI interaction
multi-agent and multi-system environments

Its function remains constant:

preserve the relationships that make Harm Context intelligible without
allowing association, proximity, sequence, dependency, control, or
participation to become unsupported conclusions about causation,
responsibility, or liability.

Minimum Implementation Framework

A minimum implementation of HCRM should provide eight capabilities.

Governed Input

Receive the applicable Governed Harm Context, Harm Subject Map, Harm
Domain Context, Harm Temporal Context, and relevant governed relationships
from adjacent systems or architectures.

Relationship Identification

Identify which relationships among Harm Context elements are materially
relevant.

Relationship Typing

Distinguish physical, digital, informational, organizational, operational,
environmental, dependency, control, authority, delegation, ownership,
permission, exposure, temporal, and other materially different
relationship types.

Relationship Qualification

Represent whether a relationship is established, supported, possible,
disputed, unsupported, unknown, or otherwise appropriately qualified.

Relationship Structure

Support direction, asymmetry, multiplicity, sequence, concurrency,
recurrence, conditionality, and multi-step relationships.

Boundary Protection

Prevent association, correlation, sequence, proximity, dependency,
control, authority, participation, or ownership from being silently
transformed into causation, accountability, responsibility, or liability.

Reassessment & Historical Continuity

Permit relationship addition, removal, qualification, and correction while
preserving prior governed relationship states.

Governed Output

Produce a traceable Governed Harm Context Relationship Map capable of
supporting subsequent HAGA™ governance.

A system that merely connects contextual elements with generic links
without preserving relationship type, qualification, uncertainty, and
boundary does not fully implement HCRM.

Use Case 1 — Complex Harm Context with Multiple Connected Actors
and

Systems

A Harm-relevant situation involves:

Person → AI System → Organizational Process → Human Decision → Operational
System → Affected Subject

A simplistic governance model compresses this into:

AI caused Harm

HCRM instead preserves the actual relationship structure.

It distinguishes:

AI Output Relationship

Organizational Process Relationship

Human Interpretation Relationship

Decision Relationship

Operational Execution Relationship

Affected Subject Relationship

This does not determine which relationship ultimately carries causal,
accountability, or liability significance.

It ensures that downstream governance starts from the actual relational
structure rather than from a simplified narrative.

The governing principle is:

Relationship Structure ≠ Liability Structure

Use Case 2 — Shared Exposure Without Shared Causation or
Identical

Harm

Multiple subjects occupy the same Harm-relevant environment.

They share:

Location + Time Period + Environmental Condition

A simplistic system concludes:

Same Environment → Same Exposure → Same Harm

HCRM preserves:

Shared Environmental Relationship

while distinguishing subject-specific dependencies, durations, proximity,
protective conditions, and other relevant relationships.

HES may later determine Exposure.

Subsequent HAGA™ standards may determine Harm.

HCRM prevents shared context from becoming an unsupported universal
conclusion.

The critical distinctions are:

Shared Relationship ≠ Shared Exposure

Shared Exposure ≠ Shared Harm

Shared Harm Context ≠ Identical Harm State

Governance Requirements

HCRM requires that:

materially relevant relationships remain distinguishable from
simple

Governance Logic

HCRM applies the following logic:

Are multiple Harm Context elements present?

If no:

→ preserve the absence of material contextual relationships.

If yes:

→ identify candidate relationships.

Is each candidate relationship materially relevant to Harm governance?

If no:

→ exclude it from the governed relationship map.

If yes:

→ determine its relationship type.

Is the relationship direct, indirect, sequential, concurrent, dependent,
conditional, or multi-step?

→ preserve the appropriate structure.

Is direction or asymmetry supported?

If yes:

→ represent it.

If no:

→ avoid unsupported directional interpretation.

Is the relationship established, uncertain, disputed, or unknown?

→ qualify it explicitly.

Would the relationship be interpreted as causation, responsibility,
accountability, or liability if left unqualified?

If yes:

→ apply the appropriate governance boundary.

Has new information materially changed the relationship structure?

If yes:

→ reassess while preserving historical versions.

Is the relationship map sufficient for the next legitimate Harm governance
step?

If no:

→ preserve a qualified or incomplete relationship state.

If yes:

→ produce the Governed Harm Context Relationship Map.

At every stage:

Association ≠ Causation

Control ≠ Liability

Participation ≠ Responsibility

Relationship ≠ Harm

Governance Outputs

HCRM may produce:

Governed Harm Context Relationship Map
Direct Relationship Record
Indirect Relationship Record
Multi-Step Relationship Chain
Physical Relationship Record
Digital Relationship Record
Informational Relationship Record
Organizational Relationship Record
Operational Relationship Record
Environmental Relationship Record
Dependency Relationship
Control Relationship
Authority / Delegation Context Relationship
Ownership / Permission Context Relationship
Exposure-Relevant Relationship
Sequential / Concurrent Relationship
Correlation / Association Record
Relationship Qualification State
Relationship Conflict Record
Relationship Uncertainty State
Relationship Reassessment Record
Historical Relationship Map
Relationship Sufficiency State

The principal output is:

Governed Harm Context Relationship Map

linked to the full Governed Harm Context.

Critical Distinctions

Co-Presence ≠ Material Relationship

Observable Relationship ≠ Governance-Relevant Relationship by Default

Indirect Relationship ≠ Weak Relationship by Default

Physical Relationship ≠ Physical Harm

Information Flow ≠ Decision Authority

Shared Relationship ≠ Shared Harm State

System Use ≠ System Dependence

System Dependence ≠ System Causation

Operational Mechanism Relationship ≠ Harm Causation Determination

Persistent Relationship ≠ Persistent Harm

Dependency ≠ Causation

Dependency ≠ Accountability

Control Relationship ≠ Liability Determination

Authority Relationship ≠ Harm Responsibility

Ownership ≠ Responsibility

Permission ≠ Safety

Permission ≠ No Harm

Contextual Exposure Relationship ≠ Established Exposure

Proximity ≠ Causation

Proximity ≠ Harm

Before ≠ Because

Concurrent ≠ Causal

Correlation ≠ Causation

Association ≠ Causation

Relationship Direction ≠ Causal Direction by Default

Conflicting Relationship Claims ≠ Permission to Select Preferred Narrative

Known Elements ≠ Known Relationship

Existing Relationship ≠ Harm-Relevant Relationship by Default

Current Relationship Map ≠ Historical Relationship Map

Relationship Structure ≠ Liability Structure

Shared Relationship ≠ Shared Exposure

Shared Exposure ≠ Shared Harm

Canonical Boundary

The HCRM — Harm Context Relationship Module governs the identification,
typing, qualification, direction, structure, uncertainty, evolution,
reassessment, and historical preservation of materially relevant
relationships among Harm Context elements. It supports direct, indirect,
multi-step, physical, digital, informational, organizational, operational,
environmental, temporal, dependency, control, authority, delegation,
ownership, permission, exposure-relevant, sequential, concurrent,
correlated, and associated relationships while preventing those
relationships from being converted automatically into Harm, causation,
responsibility, accountability, or liability. It does not independently
determine causation, establish Harm Exposure, determine Harm Emergence,
reconstruct Operational Reality in its entirety, govern authority or
accountability itself, establish evidence integrity, determine legal
responsibility, assign liability, or identify a guilty party.

HCM establishes the contextual elements.

HSM establishes who or what may be affected.

HDCM establishes the relevant Harm domains.

HTCM establishes the temporal structure.

HCRM establishes how those elements materially relate to one another
without allowing relationship to become conclusion.

Its principal output completes the contextual foundation required for the
next HAGA™ lifecycle stage:

Governed Harm Context → Harm Exposure Governance

Canonical Closing Statement

Harm Context is not merely a collection of facts. It is a governed
structure of relationships whose meaning must remain separate from the
conclusions those relationships may later support.

The HCRM — Harm Context Relationship Module prevents proximity from
becoming causation, control from becoming liability, participation from
becoming responsibility, and association from becoming proof.

HAGA™ can govern Harm legitimately only when it knows not just what exists
within the context, but how those elements relate — and exactly what those
relationships do not yet prove.