HMNM — Harm Mitigation Need Module
OOF® Origin Open Foundation®
Independent Methodological Authority
Canonical Definition
The HMNM — Harm Mitigation Need Module governs how the need to materiallyreduce an existing governed Harm or its consequences is identified,
qualified, prioritized, maintained, reassessed, and translated into an
explicit Mitigation Objective.
HMNM determines what existing Harm remains materially relevant for
reduction, which Harm condition or consequence requires intervention, what
reduction is sought, how urgent or important that reduction is, and
whether the Mitigation Need changes as the governed Harm evolves.
It establishes the transition:
Governed Harm Containment State + Current Harm State → Mitigation Need
Identification → Mitigation Need Qualification → Mitigation Priority →
Mitigation Objective → Governed Harm Mitigation Need
Its central question is:
What existing Harm or consequence requires material reduction, and what
governed improvement must Mitigation seek to achieve?
- Operational Role
The operational role of HMNM is:
to determine whether Mitigation is required and define what existing Harm
condition must materially improve before any Mitigation action is
selected.
HMNM governs:
the need for Harm reduction
not:
the intervention used to produce it.
This distinction prevents available actions from defining the problem they
are supposed to solve.
- Position Within HMS
The HMS governance flow is:
Mitigation Need → Mitigation Action → Mitigation Effect → Mitigation
Outcome → Mitigation Verification
HMNM governs the first stage:
Mitigation Need
It may receive:Governed Harm Containment State
Governed Harm State
Governed Harm Boundary
Governed Harm Change & Propagation State
and other materially relevant HAGA™ lifecycle information.It produces:
Governed Harm Mitigation Need
for the Harm Mitigation Action Module.- Governed Object
The primary governed object is:
Need for Material Reduction of Existing Harm or Its Consequences
The existence of Harm does not automatically define what Mitigation should
target.
A governed Harm may contain:
multiple consequences
different affected subjects
different Harm components
different persistence conditions
or:
different levels of reducibility
HMNM identifies which of these require governed reduction.
- Foundational Mitigation Need Principle
The foundational rule is:
Mitigation Need must be defined by the Harm condition requiring reduction,
not by the intervention that happens to be available.
Therefore:
Available Intervention ≠ Established Mitigation Need
and:
Existing Harm ≠ Fully Defined Mitigation Need
The Harm must first be translated into a governable reduction requirement.
- Mitigation Need Identification
Mitigation Need may arise where existing governed Harm or its consequences
remain materially present and reduction is:
necessary
possible
required
beneficial within the governed Harm lifecycle
or:
necessary to support later Recovery
Identification should determine:
what remains harmed
what consequence remains
where the Harm remains
who or what remains affected
and:
what materially requires improvement
- Containment State and Mitigation Need
Containment is an important input but not a universal prerequisite for
Mitigation.
A Harm may be:
Contained
Partially Contained
Containment Uncertain
or even:still undergoing Containment
while Mitigation becomes necessary.
Therefore:
Incomplete Containment ≠ No Mitigation Need
Containment and Mitigation may operate in parallel where operational
reality requires it.
- Containment Need ≠ Mitigation Need
The two needs answer different questions.
Containment Need:
What additional Harm must be prevented?
Mitigation Need:
What existing Harm must be reduced?
A single Harm may generate both simultaneously.
Therefore:
Containment Need ≠ Mitigation Need
and:
Containment Need Ended ≠ Mitigation Need Ended
- Harm State and Mitigation Need
Current Harm State informs Mitigation Need but does not automatically
determine it.
A Harm classified as:
Active
Stabilized
Reduced
or:Residual
may each produce different Mitigation requirements.Likewise:
High Harm Severity ≠ Automatically High Mitigation Priority
unless the broader governed conditions support that determination.
HMNM must evaluate the actual reduction requirement.
- Mitigation Need Qualification
Once identified, a Mitigation Need must be qualified sufficiently for
action governance.
Qualification may include:
affected Harm component
affected subject or object
current Harm condition
material consequence
reducibility
urgency
priority
scope
timing
dependencies
uncertainty
and:
expected direction of improvement
Qualification must remain proportionate to the Harm context.
- Harm Reducibility
HMNM must distinguish between Harm that is:
fully reducible
partially reducible
conditionally reducible
currently non-reducible
or:
reducibility uncertain
A Harm does not cease to exist merely because complete reduction is
impossible.
Therefore:
Not Fully Reversible ≠ No Mitigation Need
Mitigation may legitimately seek partial reduction.
- Irreversible Harm
Some Harm cannot be reversed.
HMNM must not create a false objective of restoring a condition that can
no longer exist.
Instead, Mitigation Need may target reducible consequences such as:
continuing impairment
secondary consequences
ongoing burden
severity
persistence
or:
preventable deterioration of the existing Harm condition
Canonical principle:
Irreversible Harm may still contain reducible consequences.
- Mitigation Target Formation
HMNM identifies what aspect of existing Harm requires reduction.
Potential targets include:
Harm magnitude
severityduration
persistence
affected scope
functional impairment
material consequence
specific manifestation
or:
another materially relevant Harm condition
The target must describe the Harm condition rather than the operational
intervention.
- Mitigation Objective Formation
The Mitigation Objective defines the governed improvement sought.
A weak objective is:
Perform Intervention X.
A governed Mitigation Objective is:
Reduce Harm Condition A toward materially improved Condition B.
Therefore:
Action Description ≠ Mitigation Objective
The objective must remain outcome-oriented.
- Baseline Harm Condition
Meaningful Mitigation requires sufficient understanding of the condition
from which reduction is being sought.
HMNM should establish an appropriate:
Mitigation Baseline
The baseline may describe:current magnitude
current severity
affected scope
current functional condition
current persistence
or:
another relevant Harm characteristic
Without a sufficient baseline, later claims of Harm reduction may become
unreliable.
- Baseline Uncertainty
The Harm baseline may itself contain uncertainty.
HMNM must preserve that uncertainty rather than create false precision.
Therefore:
Uncertain Baseline ≠ No Mitigation Need
but also:
Uncertain Baseline ≠ Precise Reduction Target by Default
The objective should reflect the level of certainty actually available.
- Mitigation Priority
Multiple Mitigation Needs may exist simultaneously.
HMNM must support prioritization based on materially relevant factors such
as:
Harm severity
affected scopepersistence
reducibility
time sensitivity
risk of deterioration
dependency relationships
vulnerability of affected subjects
or:
relationship to Recovery
Priority must remain grounded in the governed Harm context.
- Urgency and Priority
Urgency and priority are related but distinct.
A Harm consequence may require rapid intervention because delay materially
reduces Mitigation potential.
Another consequence may be more significant overall but less
time-sensitive.
Therefore:
Urgency ≠ Priority
HMNM should preserve both where the distinction matters.
- Mitigation Window
Some Harm can be reduced only, or substantially more effectively, within a
particular period.
HMNM may therefore establish:
Mitigation Window
representing the materially relevant period within which Mitigation actionshould occur.
A closing Mitigation Window may increase urgency even where Harm severity
has not changed.
- Multiple Mitigation Needs
A single Harm object may generate several Mitigation Needs.
For example:
Need₁ — reduce physical consequence
Need₂ — reduce functional impairment
Need₃ — reduce persistent downstream effect
These needs may require:
different priorities
different timing
different objectives
and later:
different actions
HMNM must not collapse materially distinct reduction needs into one
generic intervention requirement.
- Composite Harm
Where Harm is composite, Mitigation Need must be assessed at both
component and complete Harm levels.
A major reduction opportunity in one component may coexist with severe
non-reducible Harm elsewhere.
Therefore:
Component Mitigation Need ≠ Complete Harm Mitigation Need
The complete Harm object must remain governable.
- Collective Harm
Where the Harm affects:
multiple individuals
a defined group
an organization
an environment
a population
or:
society
Mitigation Need must not be inferred only from selected individual
outcomes.
Canonical principle:
Individual Mitigation Need ≠ Collective Mitigation Need by Default
Collective Harm may require a collective reduction objective.
- Distributed Harm
Mitigation Need may span several:
systems
locations
organizations
providers
agents
infrastructure components
or:
domains
Fragmented operational ownership must not fragment the governed Harm
object.
HMNM must preserve the complete Mitigation Need across distributed
environments.
- Cross-Domain Mitigation Need
One Harm may produce reducible consequences in several domains.
For example:
Physical → Organizational → Financial
or:
Digital → Cognitive → Societal
Reduction in one domain may not address the others.
Therefore:
One Domain Mitigation Need ≠ Complete Harm Mitigation Need
Cross-domain needs should remain distinguishable but related.
- Mitigation Need Under Continuing Harm
Existing Harm may require Mitigation while new Harm is still being
produced.
HMNM must preserve both realities:
Existing Harm → Mitigation Need
and:
Continuing Harm Development → Containment Need
Neither should erase the other.
Canonical principle:
Continuing Harm production does not make existing Harm unworthy of
reduction.
- Mitigation Need and Recovery
Mitigation Need should support, but not replace, Recovery governance.
A reduction objective may be necessary to make Recovery possible.
However:
Mitigation Objective ≠ Recovery Objective by Default
HMS governs reduction of Harm.
HRRHS governs what has recovered and what Residual Harm remains.
- Mitigation Need and Residual Harm
The possibility that some Harm will remain does not eliminate Mitigation
Need.
A realistic Mitigation Objective may seek:
maximum materially achievable reduction
without claiming complete elimination.
Therefore:
Expected Residual Harm ≠ No Mitigation Need
- Mitigation Need Under Uncertainty
Uncertainty may concern:
current Harm magnitude
reducibility
affected scope
future persistence
available reduction pathways
or:
expected outcome
HMNM must distinguish:
Mitigation Need Established
from:Mitigation Outcome Predictable
A need may be clear even where the eventual reduction remains uncertain.- Predicted Benefit
Forecasts may inform Mitigation prioritization.
They do not establish actual Mitigation.
Therefore:
Predicted Mitigation Benefit ≠ Actual Harm Reduction
PGA™ may govern prediction where applicable.
HMNM uses predictions only as supporting inputs where methodologically
appropriate.
- Simulated Mitigation
SIMULOS® may support testing of possible interventions or expected Harm
reduction.
Simulation may inform:
reducibility
priority
timing
or:
objective feasibility
But:
Simulated Mitigation Success ≠ Actual Harm Mitigation
HMNM governs the Need, not simulated proof of outcome.
- Accountability and Liability Independence
Mitigation Need may exist before responsibility or liability is
determined.
Harm should not remain unnecessarily unreduced merely because those
questions remain unresolved.
Therefore:
Unresolved Accountability ≠ No Mitigation Need
Unresolved Liability ≠ No Mitigation Need
HMS does not determine who is legally required to perform or fund
Mitigation.
- Mitigation Need States
HMNM may represent Mitigation Need through states such as:
Mitigation Need Established
Mitigation Need Partially Established
Potential Mitigation Need
Mitigation Need Uncertain
Mitigation Need Deferred
No Current Mitigation Need Established
or:Mitigation Need Closed
The state should reflect current governed Harm reality.- Mitigation Need Persistence
Mitigation Need may continue after:
Containment succeeds
initial Mitigation beginssome Harm is reduced
or:
Recovery starts
The Need remains active while materially relevant reducible Harm orconsequences continue to require reduction.
Therefore:
Mitigation Started ≠ Mitigation Need Ended
- Mitigation Need Reassessment
HMNM must support reassessment where:
Harm State changes
Containment changes
Harm scope changes
reducibility changesnew consequences emerge
Mitigation effects appear
Recovery begins
or:new information materially changes the Harm understanding
Reassessment may:
increase
decrease
reprioritize
divide
combine
defer
or:
close
a Mitigation Need.
- Mitigation Need Closure
A Mitigation Need may be closed where:
the targeted Harm has been sufficiently reduced
the targeted consequence no longer exists
further material reduction is not possible
the Need has legitimately transitioned into Recovery / Residual Harm
governance
or:
the Need is superseded by a more accurate governed formulation
Closure must have an explicit basis.
Therefore:
No Further Mitigation Action Planned ≠ Mitigation Need Closed
- Minimum Implementation Framework
A minimum HMNM implementation requires eight capabilities.
- Existing Harm Identification
Identify the governed Harm or consequence that remains materially relevant
for reduction.
- Mitigation Need Qualification
Determine the Harm condition, affected scope, reducibility, dependencies,
uncertainty, and other factors necessary to define the reduction
requirement.
- Mitigation Baseline Establishment
Establish a sufficient current Harm baseline against which later Harm
reduction can be evaluated.
- Mitigation Target & Objective Formation
Translate the Harm condition into an explicit outcome-oriented Mitigation
Target and Mitigation Objective without prescribing the action itself.
- Priority, Urgency & Timing Governance
Determine Mitigation priority, urgency, and any materially relevant
Mitigation Window.
- Composite, Collective & Distributed Need Governance
Preserve Mitigation Need across multiple Harm components, affected
subjects, domains, systems, organizations, and locations.
- Reassessment & Closure Governance
Maintain, reprioritize, adapt, divide, combine, defer, or close Mitigation
Need as the Harm condition materially changes.
- Governed Output
Produce a traceable Governed Harm Mitigation Need suitable for Mitigation
Action governance. 37. Use Case 1 — Harm Is Contained but Existing
Consequences Remain
A digital Harm has been successfully contained.
No additional systems are being affected.
However, already affected systems remain materially impaired.
HMNM identifies:
Containment Need → substantially ended
while:
Mitigation Need → remains active
It establishes the existing impairment as the Mitigation Target and
defines the required material improvement without yet selecting the
intervention.
The governing principle is:
Stopping additional Harm does not eliminate the need to reduce Harm
already produced.
- Use Case 2 — Irreversible Harm With Reducible Consequences
A Harm has produced a permanent change that cannot be reversed.
Complete restoration is impossible.
However, several continuing consequences can still be materially reduced.
HMNM does not create an impossible objective of restoring the pre-Harm
condition.
Instead, it establishes Mitigation Needs for the consequences that remain
reducible and preserves the irreversible condition for later Recovery and
Residual Harm governance.
The governing principle is:
Irreversible Harm may still contain reducible consequences.
- Governance Requirements
HMNM requires that:
- Mitigation Need be grounded in existing governed Harm or its
consequences; - the Need remain distinct from Containment Need; -
available interventions not define the Mitigation Need; - Harm
reducibility be explicitly considered; - irreversible Harm not
automatically eliminate Mitigation Need; - Mitigation Targets describe
Harm conditions rather than interventions; - Mitigation Objectives remain
outcome-oriented; - a sufficient Mitigation Baseline be established where
necessary; - baseline uncertainty remain explicit; - urgency and priority
remain distinguishable; - materially relevant Mitigation Windows remain
governable; - multiple Mitigation Needs remain separately identifiable
where necessary; - component, composite, individual, collective,
distributed, and cross-domain Harm remain appropriately distinguished; -
continuing Harm production not erase existing Mitigation Need; - expected
Residual Harm not eliminate legitimate Mitigation Need; - prediction and
simulation not be treated as actual Harm reduction; - unresolved
accountability or liability not automatically prevent Mitigation Need
determination; - Mitigation Need remain reassessable; - Need closure
require an explicit governed basis.
- Governance Logic
HMNM applies the following logic:
Does an existing governed Harm or Harm consequence remain?
If no:
→ no current Mitigation Need may exist.
If yes:
→ identify what Harm condition remains.
Then ask:
Is the Harm or consequence materially reducible?
If yes:
→ establish the relevant Mitigation Need.
If partially:
→ establish a bounded or partial Mitigation Need.
If uncertain:
→ preserve reducibility uncertainty while determining whether action
planning remains justified.
If irreversible:
→ identify whether materially reducible consequences remain.
Then determine:
What Harm condition should improve?
→ establish the Mitigation Target.
From what current condition?
→ establish the Mitigation Baseline.
Toward what materially improved condition?
→ establish the Mitigation Objective.
Then determine:
How urgent is the Need?
What priority does it carry?
Does a Mitigation Window exist?
Does the Need span multiple subjects, components, domains, systems, or
locations?
→ preserve the complete governed structure.
Finally:
Governed Harm Mitigation Need → Harm Mitigation Action
Throughout:
Existing Harm ≠ Fully Defined Mitigation Need
Containment Need ≠ Mitigation Need
Available Intervention ≠ Mitigation Need
Action Description ≠ Mitigation Objective
Irreversible Harm ≠ No Reducible Consequence
Mitigation Started ≠ Mitigation Need Ended
No Planned Action ≠ Mitigation Need Closed
- Governance Outputs
HMNM may produce:
Governed Harm Mitigation Need
Mitigation Need State
Mitigation Target
Mitigation Baseline
Mitigation Objective
Harm Reducibility State
Mitigation Priority
Mitigation Urgency
Mitigation Window
Composite Mitigation Need
Collective Mitigation Need
Distributed Mitigation Need
Cross-Domain Mitigation Need
Mitigation Need Uncertainty
Mitigation Need Reassessment Trigger
and:Mitigation Need Closure State
The principal output is:Governed Harm Mitigation Need
- Critical Distinctions
Existing Harm ≠ Fully Defined Mitigation Need
Containment Need ≠ Mitigation Need
Containment Need Ended ≠ Mitigation Need Ended
Available Intervention ≠ Established Mitigation Need
Mitigation Mechanism ≠ Mitigation Target
Action Description ≠ Mitigation Objective
Not Fully Reversible ≠ No Mitigation Need
Irreversible Harm ≠ No Reducible Consequence
Uncertain Baseline ≠ No Mitigation Need
Urgency ≠ Priority
Component Mitigation Need ≠ Complete Harm Mitigation Need
Individual Mitigation Need ≠ Collective Mitigation Need
Expected Residual Harm ≠ No Mitigation Need
Predicted Mitigation Benefit ≠ Actual Harm Reduction
Simulated Mitigation Success ≠ Actual Harm Mitigation
Unresolved Liability ≠ No Mitigation Need
Mitigation Started ≠ Mitigation Need Ended
No Further Action Planned ≠ Mitigation Need Closed
- Canonical Boundary
The HMNM — Harm Mitigation Need Module governs how the need to materially
reduce an existing governed Harm or its consequences is identified,
qualified, prioritized, bounded, maintained, reassessed, and translated
into a governed Mitigation Target and Mitigation Objective. It governs
Harm reducibility, Mitigation baseline, priority, urgency, timing,
multiple and distributed Mitigation Needs, uncertainty, persistence,
reassessment, and closure. HMNM does not determine whether Harm originally
exists, perform Harm Recognition or Determination, independently define
the Governed Harm Boundary, perform Harm Containment, select or execute
Mitigation actions, determine Mitigation Effect or Outcome, perform final
Mitigation Verification, govern Recovery or Residual Harm, establish
Resolution or Finality, determine general causation, or assign
accountability, responsibility, or liability.
- Canonical Closing Statement
Mitigation should begin with the Harm that needs to change—not with the
intervention already available.
Some Harm can be reduced, some can only be partially reduced, and
irreversible Harm may still leave consequences that can materially
improve.
HMNM turns those realities into explicit, prioritized, and governable
reduction objectives before action begins.
A Mitigation Need exists wherever governed Harm still contains something
that can and should materially improve.