Harm Context Mapping Module (HCM)

OOF® Origin Open Foundation®

Independent Methodological Authority

Canonical Definition

The Harm Context Mapping Module (HCM) governs how the circumstances
materially relevant to a potential, emerging, recognized, or existing Harm
are identified, organized, related, bounded, and represented as a coherent
Harm Context Map without prematurely determining that Harm exists, why it
occurred, who is responsible for it, or what liability may follow.

HCM establishes the contextual structure necessary to answer:

What surrounding reality must be understood in order for this
Harm-relevant situation to be governed correctly?

The Module governs the transition:

Harm-Relevant Information → Context Element Identification → Context
Relationship Mapping → Context Boundary → Context Qualification → Governed
Harm Context Map

  • Operational Role


Harm rarely exists as an isolated fact.

A Harm-relevant situation may involve subjects, objects, systems,
environments, actions, conditions, time periods, relationships,
dependencies, prior states, continuing processes, and uncertain
information.

Without structured context mapping, downstream Harm governance may begin
from an incomplete or distorted representation of reality.

HCM provides that structure.

Its responsibility is:

to map the circumstances necessary to understand Harm without converting
those circumstances into premature conclusions about Harm.

  • Core Function


HCM transforms fragmented Harm-relevant information into an organized
contextual representation.

Conceptually:

Fragmented Context → Identified Elements → Material Relationships →
Context Structure → Governed Harm Context Map

The map represents context.

It does not determine Harm.

  • Position Within Harm Context Standard (HCS)


The internal Harm Context governance sequence is:

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

HCM establishes the initial contextual structure upon which the remaining
Harm Context Standard (HCS) functions can operate.

  • Governance Trigger


HCM may activate when available information indicates that Harm-specific
context should be established.

Triggers may include:

  • an occurrence
  • adverse signal
  • physical interaction
  • AI output
  • autonomous action
  • system condition
  • complaint
  • allegation
  • detected anomaly
  • possible exposure
  • observed consequence
  • environmental change
  • repeated pattern
  • delayed discovery


A trigger creates a mapping requirement.

It does not establish Harm.

Context Mapping Trigger ≠ Harm Determination

  • Mapping Object


The governed object of HCM is the Harm Context Map.

The map represents the materially relevant circumstances surrounding a
Harm-relevant situation.

It may contain subjects, objects, environments, systems, conditions,
events, states, relationships, time references, uncertainties, and
external governance references.

  • Context Element Identification


HCM must identify the contextual elements materially relevant to Harm
governance.

An element should be included because it contributes to understanding the
Harm-relevant situation, not merely because information about it exists.

The governing rule is:

Available Information ≠ Relevant Context

  • Material Relevance


Context mapping should be proportionate to the governance question.

An element is materially relevant where its inclusion may affect:

  • understanding of potential Harm
  • affected subject or object identification
  • Harm domain interpretation
  • temporal understanding
  • exposure interpretation
  • downstream Harm boundary
  • Harm determination readiness
  • propagation understanding
  • later mitigation or recovery context


HCM should not become an unlimited reconstruction of Operational Reality.

  • Minimum Sufficient Context


HCM should seek the minimum contextual structure sufficient for legitimate
Harm governance.

This does not mean minimum information in an absolute sense.

It means:

enough context to support the intended governance step without requiring
unsupported assumptions.

Therefore:

More Context ≠ Better Governance by Default

  • Context Scope


The Harm Context Map may be narrow or broad depending upon the
Harm-relevant situation.

It may concern:

One Subject

Multiple Subjects

One System

Multiple Systems

One Environment

Interconnected Environments

Localized Conditions

Distributed Conditions

Scope must follow Harm relevance rather than administrative convenience.

  • Context Boundary


HCM must distinguish between:

Inside Harm Context

and:

Outside Current Harm Context

The boundary is methodological rather than necessarily physical,
organizational, legal, or geographic.

An element outside the initial boundary may later enter the governed
context if new information makes it materially relevant.

  • Boundary Expansion


A Harm Context Map must permit controlled expansion.

Example:

Local Effect → Additional Affected Subjects → Wider System Relationship →
Expanded Harm Context

Boundary expansion must remain traceable.

The original context must not disappear merely because the map becomes
broader.

  • Boundary Contraction


Context may also be narrowed when information demonstrates that previously
included elements are not materially relevant.

Removal must not silently rewrite historical context.

Current Context Boundary ≠ Historical Context Boundary

  • Subject Presence


HCM may identify persons, groups, organizations, populations, systems,
infrastructure, environments, or other entities that appear materially
relevant.

Detailed subject governance belongs to the Harm Subject Mapping Module.

HCM establishes their contextual presence.

  • Object Presence


Physical objects, digital objects, information objects, systems,
infrastructure, assets, environmental objects, or other governed objects
may be represented where materially relevant.

Their inclusion does not establish that they caused or suffered Harm.

  • System Context


Where systems are involved, HCM may map their contextual role.

This may include:

Source System → Interacting System → Affected System → Downstream System

HCM does not govern the internal operation of those systems.

  • Human Context


Human participation may be represented where relevant as:

Actor

Operator

User

Affected Subject

Observer

Decision Participant

Intervening Participant

or another sufficiently defined contextual role.

Role presence does not establish responsibility.

  • AI Context


Where AI is involved, HCM may represent the AI system, relevant output,
interaction, deployment context, or system relationship necessary for Harm
governance.

AI Involvement ≠ AI-Caused Harm

AIG® governs AI behavior where applicable.

  • Autonomous-System Context


Autonomous systems may produce Harm-relevant circumstances through
perception, selection, authorization, action, or continued autonomous
execution.

HCM may represent those circumstances where relevant.

ASGA™ remains responsible for autonomous-operation governance.

Autonomous Action ≠ Established Harm

  • Physical Interaction Context


Where Harm relevance involves embodied interaction, HCM may represent:

Approach → Proximity → Contact → Force / Motion → Physical Effect →
Response

This is contextual representation.

It is not a Harm finding.

Physical Contact ≠ Harm

  • Digital Interaction Context


Digital Harm-relevant contexts may involve:

System → Information → Interaction → Distribution → Access → Modification
→ Consequence

The exact mechanism depends upon the situation.

HCM maps only what is materially necessary for Harm governance.

  • Organizational Context


Organizational structures may materially affect Harm Context.

Relevant elements may include:

  • process
  • organizational relationship
  • operational responsibility
  • workflow
  • escalation structure
  • organizational dependency
  • institutional environment


HCM does not convert organizational position into accountability.

  • Environmental Context


Environmental conditions may constitute part of Harm Context independently
of a discrete human or machine action.

HCM must therefore support situations in which relevant context is formed
by:

Condition → Persistence → Exposure Environment → Effect

rather than by a single incident.

  • Multi-System Context


Modern Harm may emerge from interactions among multiple systems even where
no individual system independently produces the complete harmful
condition.

HCM must support:

System A + System B + Human / Environment + Interaction → Harm-Relevant
Context

No Single Dominant System ≠ No Governable Context

  • Context Relationship Mapping


Context elements gain meaning through relationships.

HCM may map relationships such as:

Interaction

Dependency

Sequence

Proximity

Containment

Transfer

Exposure

Operational Association

Information Flow

Environmental Association

Relationship mapping must remain distinct from causal determination.

  • Relationship Strength


Not every mapped relationship carries equal significance.

Where useful, relationships may be qualified as:

Established

Strongly Supported

Supported

Possible

Disputed

Unknown

Such states concern contextual support.

They do not constitute legal or causal findings.

  • Direct Context


Direct Context concerns circumstances immediately associated with the
Harm-relevant situation.

Examples may include the affected subject, interacting system, immediate
environment, relevant action, or observable consequence.

  • Indirect Context


Indirect Context concerns circumstances that are not immediately part of
the observed interaction but materially affect interpretation.

Examples may include upstream conditions, downstream dependencies,
historical states, environmental factors, or system relationships.

Indirect ≠ Irrelevant

  • Upstream Context


HCM may preserve upstream circumstances necessary to understand the
Harm-relevant state.

However:

Upstream Relationship ≠ Established Cause

The purpose is contextual continuity, not retrospective blame assignment.

  • Downstream Context


HCM may represent downstream circumstances where the original
Harm-relevant condition may affect additional subjects, systems,
environments, or consequences.

Detailed propagation governance belongs downstream within HAGA™.

HCM establishes contextual visibility.

  • Discrete Context


A Harm-relevant situation may center on a distinct occurrence.

HCM must support:

Pre-Occurrence Context → Occurrence Context → Immediate Post-Occurrence
Context

without assuming that the occurrence itself equals Harm.

  • Continuous Context


Where relevant conditions persist:

Condition t1 → Condition t2 → Condition t3 → Continuing Condition

HCM must represent continuity rather than forcing the situation into a
single artificial event.

  • Accumulated Context


Repeated low-level conditions may become meaningful only collectively.

HCM must therefore support:

C1 + C2 + C3 + … + Cn → Accumulated Harm-Relevant Context

No individual component must be falsely treated as the complete Harm
event.

  • Latent Context


Relevant Harm may remain unrecognized after the circumstances producing it
have occurred.

HCM must permit later information to connect current observations with
earlier contextual conditions.

Late Recognition ≠ Late Context Origin

  • Propagated Context


A Harm-relevant effect may extend beyond its original environment.

HCM must support contextual expansion where effects move across:

Subjects

Systems

Organizations

Locations

Domains

Time

Termination of the originating mechanism does not automatically terminate
relevant context.

  • Context Sequence


Where order matters, HCM should preserve sequence.

For example:

Condition → Interaction → State Change → Consequence Signal

Sequence may be governance-relevant without proving causation.

Sequence ≠ Causation

  • Parallel Context


Multiple relevant conditions may occur simultaneously.

HCM must not force parallel processes into an artificial single chain.

This is particularly important for distributed systems, multi-agent
environments, organizations, and collective Harm.

  • Context Convergence


Independent contextual paths may converge upon the same Harm-relevant
state.

HCM should permit:

Context A + Context B + Context C → Shared Harm-Relevant State

without prematurely deciding the causal contribution of each path.

  • Context Divergence


One Harm-relevant condition may produce multiple contextual branches.

Originating Condition → Context A / Context B / Context C

This structure becomes important where consequences later diverge across
subjects, systems, domains, or environments.

  • Context Uncertainty


HCM must represent uncertainty where relevant information is incomplete.

Possible contextual states may include:

Established

Partially Established

Conditionally Established

Disputed

Unknown

Unable to Determine

Uncertainty must remain visible rather than being silently converted into
certainty for mapping convenience.

  • Competing Context Representations


Different plausible interpretations of the same Harm-relevant situation
may coexist.

HCM may preserve:

Context Representation A

Context Representation B

Context Representation C

until sufficient governance supports reconciliation, exclusion, or
continued coexistence.

One Narrative ≠ Governed Reality

  • Missing Context


Missing information must be representable as a governance condition.

HCM should distinguish:

Not Relevant

from:

Not Available

and:

Unknown

and:

Unable to Determine

Missing information must not automatically invalidate the entire Harm
Context Map.

  • Context Source Separation


HCM should preserve where material context originated without becoming an
evidence-governance system.

Relevant context may originate from:

  • Operational Reality
  • human observation
  • system state
  • sensor state
  • AI output
  • organizational records
  • affected subjects
  • external governed sources


ADIT® governs evidence where applicable.

HCM governs contextual use.

  • Fact, Claim & Interpretation Separation


HCM should prevent materially different information states from being
collapsed.

Where relevant:

Observed State

Reported State

Claimed State

Inferred Context

Disputed Context

should remain distinguishable.

Claimed Context ≠ Established Context

  • Context Integrity


A Harm Context Map must remain internally coherent enough to support
downstream governance.

Contradictory information should be exposed rather than silently
harmonized.

HCM does not resolve every contradiction.

It ensures that unresolved contradiction remains visible.

  • Context Versioning


Materially changed Harm Context Maps should remain historically
distinguishable.

Conceptually:

HCM₁ → HCM₂ → HCM₃

Each material state should preserve what was understood at that time.

This is essential where later information substantially changes the
interpretation of earlier events.

  • Context Update


New information may:

Add Context

Correct Context

Qualify Context

Expand Context

Narrow Context

Dispute Context

Supersede a Contextual Interpretation

Updates must not silently destroy earlier governed states.

  • Context Reopening


A previously stable Harm Context may require reopening where new
information reveals:

  • additional affected subjects
  • latent consequences
  • longer exposure
  • wider propagation
  • previously unknown relationships
  • corrected Operational Reality
  • materially different temporal conditions


Context Closure ≠ Permanent Context Finality

  • Context Mapping Sufficiency


A Harm Context Map becomes sufficiently governed when it supports the
intended downstream governance step without requiring material unsupported
assumptions.

The governing test is:

Can the next Harm governance question be asked legitimately from this map?

If no:

→ context remains incomplete, pending, disputed, or otherwise qualified.

If yes:

→ the map may proceed to the relevant downstream HAGA™ function.

  • Context Mapping Proportionality


The depth of mapping should correspond to Harm governance needs.

A simple Harm-relevant situation may require limited context.

A distributed, latent, systemic, or multi-domain Harm may require
substantially broader mapping.

Governance Complexity Should Follow Harm Context Complexity

not:

Every Harm Context Requires Maximum Mapping

  • Context Mapping and Operational Reality


ORA™ may establish what operationally occurred.

HCM does not replace that function.

The relationship is:

Governed Operational Reality → Harm-Relevant Context Selection → Harm
Context Map

HCM asks:

What parts of Operational Reality matter for Harm governance?

It does not ask:

What is Operational Reality in its entirety?

  • Context Mapping and Evidence


ADIT® may govern evidence supporting contextual claims.

HCM may reference that governed evidence.

Therefore:

Evidence Governance → Context Support

not:

HCM → Independent Evidence Governance

Context Map ≠ Evidence Record

  • Context Mapping and Identity


OBIDENITY® may establish governed origin-bound identity, ownership,
authority, permission, provenance, or continuity where relevant.

HCM may consume those relationships when they materially affect Harm
Context.

It does not independently establish them.

  • Context Mapping and Accountability


AGA™ may govern accountability relationships.

HCM may identify roles and contextual relationships necessary for later
governance.

But:

Contextual Role ≠ Accountability Determination

Presence ≠ Responsibility

Responsibility ≠ Liability

  • Context Mapping and Causation


HCM may map circumstances potentially relevant to causal understanding.

It does not own general causal determination.

The distinction is fundamental:

Context Association ≠ Causation

Temporal Sequence ≠ Causation

System Dependency ≠ Causation

Proximity ≠ Causation

HAGA™ may later require sufficient causal association for specific Harm
governance questions without turning HCM into an incident-investigation or
forensic methodology.

  • Context Mapping and Harm Determination


HCM must never convert contextual richness into an assumption that Harm
has been established.

A detailed map can still lead to:

Harm Not Established

Harm Partially Established

Pending

Insufficient Basis

or another legitimate downstream state.

Complete Context ≠ Established Harm

  • Context Mapping and Liability


HCM does not determine legal liability.

A context map may eventually support liability governance by preserving
relevant Harm circumstances, but it must not be designed backward from a
desired liable party.

Harm Context ≠ Liability Context

Context Mapping ≠ Search for a Guilty Party

  • AI & Autonomous Application


HCM must remain applicable where intelligent systems operate without
explicit linguistic reasoning.

Relevant Harm context may arise from:

Sensor State → Perceived State → Operational State → Action →
Environmental Response

rather than from:

Prompt → Text Reasoning → Output

HCM therefore maps the context in which consequence becomes Harm-relevant
regardless of whether intelligence passed through language.

Absence of Explainable Language ≠ Absence of Governable Harm Context

  • Multi-Agent & Multi-System Application


Where multiple agents or systems contribute to the surrounding context,
HCM must avoid forcing one-agent attribution.

The context may involve:

Agent A → Agent B → System C → Human Interaction → Environmental Effect

or parallel relationships with no single dominant chain.

Distributed Context ≠ Single-Agent Context

HCM preserves the structure required for later governance without
assigning responsibility.

  • Enterprise Application


HCM can be applied across:

  • industrial operations
  • healthcare
  • infrastructure
  • financial systems
  • digital platforms
  • AI systems
  • autonomous systems
  • robotics
  • transportation
  • public-sector operations
  • environmental governance
  • organizational processes
  • human-AI interaction
  • multi-agent systems
  • distributed operational environments


Its function remains constant:

identify and preserve the context necessary to govern Harm without
prematurely converting context into Harm, causation, accountability, or
liability.

  • Governance Requirements


HCM requires that:

  • context elements be included according to Harm relevance
  • available information remain distinguishable from relevant
    context
  • mapping scope remain proportionate to the governance purpose
  • subjects, objects, systems, environments, and material conditions


remain identifiable where relevant; - operational mechanisms remain
distinguishable from Harm; - direct and indirect context remain
supportable; - upstream and downstream context remain distinguishable from
causation; - discrete, continuous, accumulated, latent, and propagated
contexts remain representable; - sequence not be treated automatically as
causation; - parallel, convergent, and divergent contextual structures
remain supportable; - uncertainty remain visible; - competing contextual
representations remain preservable; - facts, claims, observations, and
interpretations remain distinguishable where material; - missing
information remain explicitly governable; - material context changes
remain traceable; - historical context states remain reconstructable; -
Context Mapping Sufficiency be established before downstream reliance; -
context mapping remain distinct from Operational Reality, evidence,
identity, accountability, causation, Harm Determination, and liability
governance.

  • Governance Logic


HCM applies the following operational logic:

Has a legitimate Harm Context Mapping trigger arisen?

If no:

→ no Harm Context Map is required.

If yes:

→ identify materially relevant context elements.

What subjects, objects, systems, environments, conditions, and
relationships are relevant?

→ establish the initial map.

Is the mapping boundary proportionate to the Harm governance question?

If no:

→ expand or narrow the context.

Are material contextual relationships known?

If yes:

→ represent them without converting association into causation.

Is information incomplete, disputed, or contradictory?

If yes:

→ preserve the appropriate uncertainty or competing context states.

Does the map support the next legitimate Harm governance question without
material unsupported assumptions?

If no:

→ maintain a qualified or incomplete context state.

If yes:

→ establish the Governed Harm Context Map.

Where material new information appears:

Existing Map → Context Impact → Controlled Update / Reopening → New
Governed Map State

At every stage:

Context ≠ Harm

Association ≠ Causation

Causation ≠ Accountability

Accountability ≠ Liability

  • Governance Outputs


HCM may produce:

  • Governed Harm Context Map
  • Context Element Set
  • Context Boundary
  • Context Scope State
  • Subject / Object Context Reference
  • System Context Representation
  • Operational Mechanism Context
  • Physical Interaction Context
  • Continuous / Accumulated Context Representation
  • Latent Context Representation
  • Propagation-Relevant Context
  • Context Relationship Map
  • Context Uncertainty State
  • Competing Context Representation
  • Missing Context Record
  • Context Sufficiency State
  • Context Version Record
  • Context Update Record
  • Context Reopening State


The principal output is:

Governed Harm Context Map

capable of supporting subsequent Harm Context governance without
predetermining Harm.

  • Critical Distinctions


Context ≠ Harm

Context Mapping Trigger ≠ Harm Determination

Available Information ≠ Relevant Context

More Context ≠ Better Governance by Default

Context Scope ≠ Harm Boundary

Current Context Boundary ≠ Historical Context Boundary

Subject Presence ≠ Harmed Subject Determination

AI Involvement ≠ AI-Caused Harm

Autonomous Action ≠ Established Harm

Physical Contact ≠ Harm

Indirect Context ≠ Irrelevant Context

Upstream Relationship ≠ Established Cause

Late Recognition ≠ Late Context Origin

Sequence ≠ Causation

One Narrative ≠ Governed Reality

Claimed Context ≠ Established Context

Context Map ≠ Evidence Record

Contextual Role ≠ Accountability Determination

Presence ≠ Responsibility

Context Association ≠ Causation

Temporal Sequence ≠ Causation

System Dependency ≠ Causation

Proximity ≠ Causation

Complete Context ≠ Established Harm

Harm Context ≠ Liability Context

Context Mapping ≠ Search for a Guilty Party

Absence of Explainable Language ≠ Absence of Governable Harm Context

Distributed Context ≠ Single-Agent Context

  • Canonical Boundary


The Harm Context Mapping Module (HCM) governs the identification,
selection, organization, relationship mapping, scoping, qualification,
updating, and historical preservation of circumstances materially
necessary to represent Harm Context. It governs the construction of the
Governed Harm Context Map across human, organizational, physical, digital,
AI, autonomous, multi-system, environmental, continuous, accumulated,
latent, and propagated conditions. It does not determine that Harm exists,
establish Harm Exposure, determine Harm Emergence, establish causal
responsibility, reconstruct Operational Reality in its entirety, govern
evidence, determine identity, assign accountability, determine liability,
or search for a guilty party.

HCM establishes the contextual map.

Subsequent Harm Context Standard (HCS) functions determine the affected
subject structure, domain context, temporal context, and Harm-specific
contextual relationships in greater depth.

  • Canonical Closing Statement


Harm cannot be governed from an isolated event when the reality
surrounding that event determines what the event actually means.

The Harm Context Mapping Module (HCM) preserves the subjects, systems,
environments, conditions, relationships, uncertainty, and historical
context necessary to understand a Harm-relevant situation without turning
proximity into causation, participation into responsibility, or context
into proof of Harm.

Before HAGA™ determines what Harm exists, it must first know the reality
within which Harm could meaningfully exist.