HESM — Harm Exposure Scope Module

OOF® Origin Open Foundation®

Independent Methodological Authority

Canonical Definition

The HESM — Harm Exposure Scope Module governs how the boundary and
coverage of Harm Exposure are established across subjects, objects,
groups, systems, infrastructures, environments, populations, domains,
pathways, and operational contexts after Exposure Identification and
Exposure Conditions have been established, without treating inclusion
within Exposure Scope as proof that Harm exists or that all included
subjects experience equivalent Exposure.

HESM establishes the transition:

Exposure Identification State + Governed Exposure Condition Set → Exposure
Scope Candidates → Inclusion / Exclusion Logic → Subject / Object Coverage
→ Scope Boundary → Governed Harm Exposure Scope

Its central question is:

Who or what legitimately belongs within the governed Exposure Scope, and
where does that Scope end?

  • Operational Role


Exposure governance becomes unreliable when its Scope is either too narrow
or too broad.

A narrow Scope may exclude:

  • indirectly exposed subjects
  • downstream systems
  • affected groups
  • environmental objects
  • dependent infrastructure
  • distributed populations
  • subjects discovered later


An excessively broad Scope may incorrectly include every nearby person,
connected system, organizational unit, or downstream consequence.

HESM prevents both errors.

Its responsibility is:

to establish the legitimate coverage of Harm Exposure without allowing
proximity, association, organizational membership, technical connectivity,
or shared context to become automatic Scope inclusion.

  • Position Within Harm Exposure Standard (HES)


The HES internal flow is:

Exposure Identification → Exposure Conditions → Exposure Scope → Exposure
Duration → Exposure Transition

HEIM identifies which relationships require Exposure governance.

HECM establishes the conditions under which those relationships operate.

HESM establishes which subjects, objects, systems, groups, environments,
or other governed entities fall within the Exposure Scope.

  • Governed Object


The governed object is the Governed Harm Exposure Scope.

It represents the legitimate Exposure coverage of a governed Harm-capable
condition.

The Scope may include:

Individual Subject

Multiple Subjects

Defined Group

Organization

Physical Object

Digital Object

Operational System

Infrastructure

Environment

Population

Cross-Domain Object Set

Distributed Exposure Set

  • Scope Formation


Exposure Scope is formed from three core elements:

Harm-Capable Condition

Governed Exposure Conditions

Potentially Exposed Subject / Object Set

Conceptually:

Condition + Exposure Conditions + Candidate Subjects / Objects → Scope
Qualification → Governed Exposure Scope

Scope must be justified by the Exposure relationship.

It must not be inherited automatically from an administrative or physical
boundary.

  • Scope Inclusion Principle


An entity belongs within Exposure Scope where sufficient governed basis
establishes that it enters a materially relevant Exposure relationship
with the Harm-capable condition.

The inclusion test is:

Would excluding this subject or object materially misrepresent who or what
is exposed under the governed conditions?

If yes:

→ inclusion is required.

If no:

→ exclusion may be legitimate.

  • Scope Exclusion Principle


An entity should remain outside Exposure Scope where no materially
sufficient Exposure relationship exists.

Exclusion may be justified because:

  • no relevant pathway exists
  • effective protection prevents Exposure
  • the subject falls outside the relevant condition
  • the system is not reachable
  • the environmental pathway does not extend to the object
  • the relationship is only administrative
  • inclusion is based only on unsupported assumption


Contextual Association ≠ Scope Inclusion

  • Subject Scope


Subject Scope identifies which human or non-human governed subjects fall
within Exposure.

It may include:

One Individual

Several Individuals

Defined Group

Population Segment

Organization

Population / Society

Subject Scope must reflect the actual Exposure relationship.

It must not automatically follow identity, membership, employment,
residence, ownership, or contractual status.

  • Object Scope


Exposure may involve non-human objects.

These may include:

Physical Assets

Digital Assets

Data Objects

Operational Systems

Infrastructure Components

Environmental Objects

Organizational Processes

Human Exposure is not required.

No Human Subject ≠ No Exposure Scope

  • Individual Scope


An Exposure Scope may legitimately concern one subject.

The Scope must remain limited where only one subject is sufficiently
connected to the Harm-capable condition.

Single Subject Exposure ≠ Narrow Governance by Default

A single subject may still require complex Exposure governance.

  • Multi-Subject Scope


Several subjects may belong within one Exposure Scope.

However:

Multiple Subjects ≠ Equal Exposure

Each subject may experience different:

  • conditions
  • pathways
  • intensity
  • access
  • protection
  • duration
  • recurrence
  • uncertainty


The Scope groups Exposure relevance.

It does not collapse individual differences.

  • Group Scope


A Defined Group may become the Exposure Scope where a legitimate common
Exposure basis exists.

A group should not be formed merely because subjects share a label.

Examples of potential grouping bases include:

Shared Exposure Pathway

Shared Environment

Shared System Dependency

Shared Process

Shared Informational Channel

Shared Operational Condition

Shared Label ≠ Shared Exposure Scope

  • Population Scope


Exposure may exist at population level where the Harm-capable condition
materially reaches a sufficiently defined population or population
segment.

The population need not be reducible to individually named subjects before
governance begins.

However:

Population-Level Exposure ≠ Exposure of Every Individual

HESM must support both population-level and individual uncertainty
simultaneously.

  • Organizational Scope


An organization may be exposed as a governed entity.

Separately, individuals within the organization may have their own
Exposure Scope.

Therefore:

Organizational Exposure ≠ Employee Exposure

Employee Exposure ≠ Organizational Exposure

The two may coexist but must not be conflated.

  • System Scope


A digital, mechanical, operational, or AI-related system may itself fall
within Exposure Scope.

Examples include:

System receives malicious input

Infrastructure receives harmful command

Digital environment receives corrupting process

Operational system enters unsafe interaction

The Scope must identify the actual affected system boundary.

  • Infrastructure Scope


Exposure may involve infrastructure containing multiple interdependent
components.

HESM must determine whether Exposure Scope concerns:

Single Component

Subsystem

Entire Infrastructure

Connected Infrastructure

Dependent External Infrastructure

The Scope must not expand beyond the supported Exposure relationship.

  • Environmental Scope


Environmental Exposure Scope may concern:

Air

Water

Soil

Habitat

Ecosystem

Defined Geographic Area

Distributed Environmental System

The Exposure Scope must follow the environmental pathway, not merely an
arbitrary administrative map.

Administrative Geography ≠ Environmental Exposure Boundary

  • Digital Scope


Digital Exposure may span:

User Account

Device

Dataset

Application

Network Segment

Organization

Platform

Connected System

Distributed Service

Technical connectivity alone does not establish Exposure.

Connected System ≠ Exposed System by Default

  • Informational Scope


Information-related Exposure Scope may concern:

One Recipient

Defined Audience

User Cohort

Organization

Platform Population

Distributed Public Audience

The Scope should follow actual or sufficiently supported information
reach.

Potential Audience ≠ Exposed Audience

  • Cognitive Exposure Scope


Cognitive Exposure Scope may include subjects who actually receive or
materially interact with Harm-capable informational or behavioral
conditions.

HESM does not determine cognitive Harm.

CLIA® governs cognition itself.

The Scope question remains:

Who enters the relevant Exposure relationship?

  • Physical Exposure Scope


Physical Exposure Scope may be determined through:

Reach

Contact Zone

Movement Envelope

Force Path

Material Spread

Physical Environment

Operational Area

A physical site boundary may be relevant.

It is not automatically the Exposure Scope.

Site Boundary ≠ Exposure Boundary

  • AI-Mediated Exposure Scope


AI systems may create Exposure across:

Individual User

User Cohort

Organization

Connected System

Public Audience

Downstream Automated Process

The Scope must follow actual delivery, execution, recommendation, access,
or downstream integration.

AI Output Reach ≠ AI Exposure Scope by Default

  • Autonomous-System Exposure Scope


An autonomous system may create Exposure within:

Operational Reach

Movement Envelope

Action Space

Sensor-Action Environment

Controlled Infrastructure

Downstream System

ASGA™ governs autonomous operation.

HESM governs who or what enters the Exposure Scope resulting from that
operation.

  • Multi-System Exposure Scope


Exposure may span several interacting systems.

Conceptually:

System A → System B → System C → Subject Set

HESM must determine where Exposure begins and where it materially extends.

It must not assume that every connected system belongs within Scope.

System Connectivity ≠ Exposure Inclusion

  • Direct Scope


Direct Scope contains subjects or objects with an immediate relevant
Exposure relationship.

Conceptually:

Condition → Subject

Direct Scope may form the initial Exposure boundary.

It need not be the complete Scope.

  • Indirect Scope


Indirect Scope contains subjects or objects reached through intermediate
elements.

Conceptually:

Condition → Intermediate Element → Subject

Indirectness does not disqualify Scope inclusion.

Indirect Exposure ≠ Outside Scope by Default

  • Mediated Scope


A mediated Scope exists where a human, system, environment, organization,
or information channel carries the Harm-capable condition.

The mediator may also belong within Scope where independently exposed.

Mediator status must therefore be assessed separately.

  • Downstream Scope


Exposure may extend downstream.

Conceptually:

Initial Exposure → Downstream Relationship → Additional Subject / Object

HESM may include downstream subjects where the Exposure relationship is
sufficiently supported.

It must not convert speculative downstream possibilities into actual
Scope.

  • Upstream Scope Boundary


Entities involved in producing the Harm-capable condition are not
automatically exposed entities.

For example:

Developer

Manufacturer

Operator

Owner

Organization

may be upstream actors without belonging to the Exposure Scope.

Involvement in Condition Production ≠ Exposure Inclusion

  • Shared Exposure Scope


A Shared Exposure Scope may contain several entities linked to one
condition.

HESM must preserve subject-specific differences.

Conceptually:

Condition → {A, B, C, D}

with:

A ≠ B ≠ C ≠ D in Exposure characteristics

Scope establishes membership.

It does not establish equivalence.

  • Overlapping Exposure Scopes


A subject or object may belong to multiple simultaneous Exposure Scopes.

Example:

Environmental Exposure Scope

and:

Digital Exposure Scope

and:

Organizational Exposure Scope

may overlap.

HESM must permit overlapping Scopes without forcing them into one
artificial Exposure object.

  • Nested Exposure Scope


Exposure Scopes may be nested.

Conceptually:

Population Scope → Organization Scope → Group Scope → Individual Scope

Nested Scope should preserve the relationship between broader and narrower
governance levels.

Broader Scope ≠ Complete Knowledge of Nested Subjects

  • Composite Exposure Scope


A complex Exposure may require several subject and object classes
simultaneously.

Example:

People + Digital Systems + Infrastructure + Environment

HESM must support Composite Exposure Scope where one Harm-capable
condition materially reaches several governed object types.

  • Cross-Domain Exposure Scope


The same Exposure may span multiple Harm domains.

For example:

Physical Subject Scope + Medical Scope + Digital Object Scope + Financial
Subject Scope

HESM governs coverage.

HDCM governs the Harm Domain Context.

Cross-Domain Scope ≠ Harm Propagation Determination

  • Scope Boundary Formation


The Exposure Boundary is established where the material Exposure
relationship ends.

The boundary may be:

Physical

Digital

Operational

Organizational

Environmental

Informational

Subject-Based

System-Based

Composite

The relevant boundary follows the Exposure mechanism and conditions.

  • Boundary Inclusion


Boundary inclusion should be based upon sufficient governed relationship.

A subject near the boundary may be:

Included

Conditionally Included

Uncertain

Excluded

Binary classification should not be forced where reality is uncertain.

  • Boundary Uncertainty


Exposure boundaries may be uncertain because:

  • environmental spread is unknown
  • network reach is incomplete
  • data distribution is uncertain
  • subject location is unclear
  • organizational scope is disputed
  • indirect pathways remain unresolved


Possible states may include:

Established Boundary

Estimated Boundary

Partial Boundary

Disputed Boundary

Open Boundary

Unable to Determine

  • Open Exposure Scope


Some Exposure Scopes cannot initially be closed.

Example:

Distributed digital content continues spreading

or:

Environmental condition continues moving

HESM must support:

Open Exposure Scope

until sufficient governance permits closure or stabilization.

  • Dynamic Exposure Scope


Exposure Scope may change over time.

Conceptually:

Scope₁ → Scope₂ → Scope₃

Changes may include:

Expansion

Contraction

Fragmentation

Merger

Reclassification

Reopening

Dynamic Scope is essential for distributed and evolving Harm Exposure.

  • Exposure Scope Expansion


Scope expands when additional subjects or objects legitimately enter the
Exposure relationship.

Triggers may include:

  • new pathway
  • changing environment
  • system expansion
  • information redistribution
  • repeated process
  • autonomous movement
  • infrastructure interconnection
  • newly discovered historical Exposure


Expansion must remain traceable.

  • Exposure Scope Contraction


Scope contracts where subjects or objects cease to belong to the active
Exposure relationship or earlier inclusion becomes unsupported.

Contraction does not erase historical Exposure.

Current Scope Exclusion ≠ Historical Non-Exposure

  • Scope Fragmentation


One Exposure Scope may divide into several distinct Scopes where
materially different Exposure relationships emerge.

Conceptually:

Scope A → Scope A1 + Scope A2

This may be necessary where pathways, conditions, domains, or subjects
diverge materially.

  • Scope Merger


Separate Exposure Scopes may later be understood as one connected Exposure
structure.

Conceptually:

Scope A + Scope B → Governed Composite Scope

A merger must be supported by materially relevant Exposure relationships.

  • Late Subject Discovery


A subject or object may be discovered after the active Exposure period.

HESM must support retrospective Scope inclusion where justified.

Late Discovery ≠ New Exposure Origin

  • Unknown Subjects


The existence of exposed subjects may be known before their identities are
known.

Example:

Unknown number of users received output

or:

Population affected but individuals unidentified

HESM must support unidentified Exposure Scope.

Unknown Identity ≠ Unknown Exposure Scope

  • Duplicate Subject Prevention


One subject may appear through several identifiers, systems, records, or
roles.

HESM must avoid inflating Exposure Scope through duplication.

Multiple Records ≠ Multiple Exposed Subjects

  • Subject Equivalence Boundary


Subjects that appear similar must not be treated as equivalent without
sufficient basis.

Similarity ≠ Exposure Equivalence

This becomes particularly important in population, group, digital, and
organizational Scope governance.

  • Exposure Scope and Harm Boundary


Exposure Scope and Harm Boundary are fundamentally different.

Exposure Scope asks:

Who or what is exposed?

Harm Boundary later asks:

What belongs to the governed Harm?

Therefore:

Exposure Scope ≠ Harm Boundary

A broad Exposure Scope may later produce a much narrower Harm Boundary.

  • Exposure Scope and Harm Determination


Inclusion within Exposure Scope does not establish that Harm exists for
the included entity.

Within Exposure Scope ≠ Harmed

This distinction must remain visible throughout HAGA™.

  • Exposure Scope and Causation


Scope inclusion establishes a governed Exposure relationship.

It does not establish that the Harm-capable condition caused later Harm.

Exposure Scope Inclusion ≠ Causal Attribution

  • Exposure Scope and Risk Population


Risk models may define a population potentially at risk.

HESM defines the governed Exposure Scope based on materially supported
Exposure relationships.

Population at Risk ≠ Exposed Population

  • Exposure Scope and Organizational Boundary


An organization's legal or administrative structure may provide useful
context.

It must not automatically define Exposure Scope.

Organization Boundary ≠ Exposure Scope

Exposure may extend outside the organization or affect only part of it.

  • Exposure Scope and Jurisdiction


Jurisdictional boundaries may matter for legal governance.

They do not automatically define Harm Exposure Scope.

An environmental, digital, informational, or system Exposure may cross
jurisdictions.

Jurisdiction Boundary ≠ Exposure Boundary

  • Exposure Scope and Identity Governance


OBIDENITY® may establish identity, ownership, authority, and continuity of
subjects or objects.

HESM may consume those governed identities.

It does not own Identity governance.

Scope Membership ≠ Identity Determination

  • Exposure Scope and Operational Reality


ORA™ may establish which entities were actually present, connected,
active, or operating.

HESM determines which of those entities belong to Exposure Scope.

Operational Presence ≠ Exposure Scope Inclusion

  • Exposure Scope and Evidence


ADIT® may govern evidence supporting Scope inclusion or exclusion.

HESM determines the governed Exposure Scope from appropriate evidence and
context.

Evidence of Presence ≠ Exposure Scope by Itself

  • Scope Reassessment


HESM must reassess Scope when:

  • new subjects are identified
  • pathways change
  • Exposure conditions change
  • environmental reach changes
  • digital distribution changes
  • organizational relationships change
  • autonomous action extends operational reach
  • new evidence changes inclusion
  • previous inclusion becomes unsupported


Reassessment must preserve historical Scope states.

  • Historical Scope Integrity


Exposure Scope must remain reconstructable across time.

Conceptually:

Scope₁ → Scope Expansion → Scope₂ → Scope Contraction → Scope₃

The historical record should preserve:

  • included entities
  • excluded entities
  • uncertainty states
  • basis for inclusion
  • basis for exclusion
  • material Scope changes


Current Exposure Scope ≠ Historical Exposure Scope

  • Scope Sufficiency


Exposure Scope is sufficiently governed when downstream Exposure Duration
governance can proceed without material uncertainty about who or what
belongs within the Exposure relationship.

The test is:

Would omission or unsupported inclusion of any subject or object
materially distort subsequent Exposure governance?

If yes:

→ Scope remains incomplete, disputed, or open.

  • Scope Proportionality


Scope governance should match the complexity of the Exposure.

A direct one-person Exposure may require a narrow Scope.

A distributed environmental or digital Exposure may require:

Population + System + Geography + Multiple Pathways + Uncertain Boundary

The governing rule is:

Scope Complexity Should Follow Exposure Reality

not:

Largest Possible Scope by Default

  • Enterprise Application


HESM can be applied across:

  • healthcare
  • workplace and industrial environments
  • environmental governance
  • digital platforms
  • cybersecurity
  • AI systems
  • autonomous systems
  • robotics
  • transportation
  • financial systems
  • infrastructure
  • organizational governance
  • public-sector systems
  • population-scale exposure
  • human-AI environments
  • multi-system operations


Its function remains constant:

establish who or what legitimately belongs within Harm Exposure governance
and where that Exposure Scope ends.

  • Minimum Implementation Framework


A minimum implementation of HESM should provide eight capabilities.

  • Governed Input


Receive the Exposure Identification State, Governed Exposure Condition
Set, Harm Subject Map, applicable Harm Domain Context, and relevant
temporal/contextual relationships.

  • Scope Candidate Formation


Identify subjects, objects, groups, systems, infrastructures,
environments, or populations potentially belonging within Exposure Scope.

  • Inclusion / Exclusion Logic


Require a materially supported Exposure relationship for Scope inclusion
and a traceable basis for material exclusions.

  • Multi-Level Scope Representation


Support individual, group, population, organizational, system,
infrastructure, environmental, digital, composite, nested, and overlapping
Exposure Scopes.

  • Boundary & Uncertainty Governance


Represent established, estimated, partial, disputed, open, or
unable-to-determine Scope boundaries.

  • Dynamic Scope Management


Support Scope expansion, contraction, fragmentation, merger, reopening,
and late subject discovery.

  • Historical Continuity


Preserve prior Scope states, inclusion decisions, uncertainty states, and
material changes.

  • Governed Output


Produce a traceable Governed Harm Exposure Scope capable of supporting
Exposure Duration governance.

A system that defines Exposure Scope only by physical location, legal
entity, technical network, or administrative membership does not fully
implement HESM.

  • Use Case 1 — Distributed Environmental Exposure Across an
    Uncertain


Population

A Harm-capable environmental condition spreads across an area containing:

Residents

Workers

Infrastructure

Water System

Ecosystem

Transient Population

A simplistic system defines Exposure Scope using one administrative
district.

HESM instead follows the actual exposure pathway.

It may establish:

Confirmed Exposure Area

Probable Exposure Area

Uncertain Boundary

Defined Population Scope

Environmental Object Scope

Infrastructure Scope

Subjects outside the administrative district may belong within Scope,
while some entities inside it may legitimately remain outside.

The governing principle is:

Administrative Geography ≠ Environmental Exposure Boundary

  • Use Case 2 — AI Output Reaches Only Part of a Connected User


Population

An AI-generated output exists within a platform used by a large
population.

A simplistic model defines:

Platform Users = Exposed Population

HESM instead examines actual Exposure coverage.

The output may have reached:

User Cohort A → Displayed

User Cohort B → Recommended repeatedly

User Cohort C → Filtered

User Cohort D → Never received

Connected Downstream System E → Automatically processed

The Governed Exposure Scope therefore follows actual or sufficiently
supported delivery and processing relationships rather than total platform
membership.

The governing distinctions are:

Potential Audience ≠ Exposed Audience

Platform Membership ≠ Exposure Scope Inclusion

  • Governance Requirements


HESM requires that:

  • Exposure Scope be derived from materially supported Exposure


relationships; - Scope inclusion remain distinct from Harm Determination;
- subject and object Scope both remain supportable; - individual,
multi-subject, group, population, organizational, system, infrastructure,
environmental, digital, informational, and cognitive Exposure Scopes
remain representable; - population-level Exposure not imply Exposure of
every individual; - organizational Exposure remain distinguishable from
employee Exposure; - technical connectivity remain distinct from Exposure
Scope; - upstream actors remain distinct from exposed subjects; - direct,
indirect, mediated, downstream, nested, overlapping, composite, and
cross-domain Scopes remain supportable; - boundary uncertainty remain
explicitly representable; - open and dynamic Exposure Scopes remain
governable; - Scope expansion, contraction, fragmentation, merger, and
late discovery remain traceable; - unknown subject identity remain
distinguishable from unknown Exposure Scope; - duplicate subjects not
inflate Scope; - Exposure Scope remain distinct from Harm Boundary; -
Exposure Scope remain distinct from causation; - risk population remain
distinct from exposed population; - administrative, organizational, site,
jurisdictional, and network boundaries not automatically define Exposure
Scope; - historical Scope states remain reconstructable.

  • Governance Logic


HESM applies the following logic:

Has a legitimate Exposure relationship been identified?

If no:

→ no Exposure Scope should be established.

If yes:

→ identify Scope candidates.

Does each candidate have a materially supported Exposure relationship
under the Governed Exposure Conditions?

If no:

→ exclude or qualify the candidate.

If yes:

→ include the candidate within the appropriate Scope.

Is the Scope individual, group, population, organizational, system,
infrastructure, environmental, digital, or composite?

→ represent the appropriate Scope structure.

Are multiple Exposure Scopes overlapping or nested?

If yes:

→ preserve those relationships.

Is the Scope boundary fully known?

If no:

→ represent the appropriate uncertainty or Open Scope state.

Has Exposure expanded or contracted?

If yes:

→ update Scope without erasing previous states.

Were subjects discovered later?

If yes:

→ support retrospective inclusion where the Exposure relationship is
sufficiently established.

Is Scope sufficiently governed for Exposure Duration analysis?

If no:

→ maintain Partial / Open / Disputed Scope.

If yes:

→ produce Governed Harm Exposure Scope.

At every stage:

Scope Inclusion ≠ Harm

Scope Inclusion ≠ Causation

Exposure Scope ≠ Harm Boundary

Administrative Boundary ≠ Exposure Boundary

  • Governance Outputs


HESM may produce:

  • Governed Harm Exposure Scope
  • Exposure Scope Candidate Set
  • Included Subject / Object Set
  • Excluded Subject / Object Set
  • Individual Exposure Scope
  • Group Exposure Scope
  • Population Exposure Scope
  • Organizational Exposure Scope
  • System Exposure Scope
  • Infrastructure Exposure Scope
  • Environmental Exposure Scope
  • Digital / Informational Exposure Scope
  • Direct / Indirect / Mediated Scope
  • Nested Exposure Scope
  • Overlapping Exposure Scope
  • Composite Exposure Scope
  • Open Exposure Scope
  • Exposure Scope Boundary
  • Exposure Scope Uncertainty State
  • Exposure Scope Change Record
  • Historical Exposure Scope
  • Scope Sufficiency State


The principal output is:

Governed Harm Exposure Scope

for the next HES governance stage.

  • Critical Distinctions


Contextual Association ≠ Scope Inclusion

No Human Subject ≠ No Exposure Scope

Multiple Subjects ≠ Equal Exposure

Shared Label ≠ Shared Exposure Scope

Population-Level Exposure ≠ Exposure of Every Individual

Organizational Exposure ≠ Employee Exposure

Employee Exposure ≠ Organizational Exposure

Administrative Geography ≠ Environmental Exposure Boundary

Connected System ≠ Exposed System by Default

Potential Audience ≠ Exposed Audience

Site Boundary ≠ Exposure Boundary

AI Output Reach ≠ AI Exposure Scope by Default

System Connectivity ≠ Exposure Inclusion

Indirect Exposure ≠ Outside Scope by Default

Involvement in Condition Production ≠ Exposure Inclusion

Broader Scope ≠ Complete Knowledge of Nested Subjects

Cross-Domain Scope ≠ Harm Propagation Determination

Current Scope Exclusion ≠ Historical Non-Exposure

Late Discovery ≠ New Exposure Origin

Unknown Identity ≠ Unknown Exposure Scope

Multiple Records ≠ Multiple Exposed Subjects

Similarity ≠ Exposure Equivalence

Exposure Scope ≠ Harm Boundary

Within Exposure Scope ≠ Harmed

Exposure Scope Inclusion ≠ Causal Attribution

Population at Risk ≠ Exposed Population

Organization Boundary ≠ Exposure Scope

Jurisdiction Boundary ≠ Exposure Boundary

Operational Presence ≠ Exposure Scope Inclusion

Current Exposure Scope ≠ Historical Exposure Scope

  • Canonical Boundary


The HESM — Harm Exposure Scope Module governs the formation, inclusion,
exclusion, structure, boundary, uncertainty, expansion, contraction,
fragmentation, merger, reassessment, and historical preservation of the
subjects, objects, groups, systems, infrastructures, environments,
populations, and other governed entities legitimately belonging within
Harm Exposure Scope. It does not determine that included entities have
been harmed, establish Harm Boundary, determine Harm Emergence, determine
causation, assign accountability or liability, define risk populations
generally, establish identity itself, reconstruct Operational Reality in
its entirety, or allow administrative, organizational, geographic,
technical, or jurisdictional boundaries to substitute automatically for
Exposure Scope.

HEIM determines:

Which relationship requires Exposure governance?

HECM determines:

Under what conditions does that relationship operate?

HESM determines:

Who or what belongs within that Exposure?

The next HES module determines:

For how long, how often, and in what temporal pattern does that Exposure
exist?

  • Canonical Closing Statement


Exposure Scope must follow the reach of the governed Exposure relationship
— not the convenience of an organizational chart, site map, network
diagram, jurisdiction, or first-visible subject.

HESM prevents narrow Scope from hiding legitimately exposed subjects and
prevents broad Scope from turning every connected entity into an exposed
one.

A credible Harm Exposure model must know not only that Exposure exists,
but exactly who or what belongs within its reach — and where that reach
legitimately ends.