HCNM — Harm Containment Need Module

OOF® Origin Open Foundation®

Independent Methodological Authority

Canonical Definition

The HCNM — Harm Containment Need Module governs how the need to contain an
already governed Harm is identified, qualified, prioritized, maintained,
reassessed, and transferred into actionable Containment governance.


HCNM determines whether existing Harm presents a materially relevant
possibility of further continuation, expansion, accumulation, compounding,
propagation, cascading, or creation of additional Harm such that
intervention is required to bound, interrupt, isolate, restrict, or stop
that development.


It establishes the transition:

Governed Harm Change & Propagation State + Current Harm State →
Containment Need Identification → Containment Need Qualification →
Containment Priority → Containment Objective → Governed Harm Containment
Need


Its central question is:

Does the current Harm dynamic require intervention to prevent materially
relevant additional Harm, and what specifically must Containment prevent
from continuing?


  • Operational Role


HCNM is the entry point into Harm Containment governance.

Its operational role is:

to determine whether Containment is required before selecting or executing
a Containment action.


HCNM separates:

the existence of Harm

from:

the need to prevent additional Harm

A Harm may exist without currently requiring active Containment.

Conversely, a Harm may require immediate Containment even while its
complete downstream consequences remain uncertain.


  • Position Within HCOS


The HCOS governance flow is:

Containment Need → Containment Action → Containment Boundary → Containment
Persistence → Containment Verification


HCNM governs the first stage:

Containment Need

It primarily receives:

Governed Harm State

and:

Governed Harm Change & Propagation State

It produces:

Governed Harm Containment Need

for subsequent Containment Action governance.

  • Governed Object


The primary governed object is:

Need to Prevent Further Harm Development

HCNM does not determine whether Harm exists.

That has already been governed through earlier HAGA™ stages.

It asks whether the established Harm can materially continue developing in
a manner that requires Containment.


Therefore:

Existing Harm ≠ Automatic Containment Need

and:

Containment Need ≠ New Harm Determination

  • Foundational Principle


The foundational rule is:

Containment Need is determined by the material possibility of further Harm
development, not merely by the severity of Harm already present.


A severe Harm that is no longer capable of further expansion may require
Mitigation and Recovery without requiring the same active Containment
response.


A currently limited Harm with rapid Propagation potential may require
immediate Containment.


Therefore:

Current Harm Severity ≠ Containment Need by Default

  • Containment Need Identification


Containment Need should be evaluated where existing Harm may materially:

continue

increase

accumulate

compound

propagate

cascade

reach additional affected scope

or:

produce further Harm

The relevant question is prospective but grounded in current governed Harm
reality:


What additional Harm development remains materially possible if no
Containment occurs?


  • Containment Need Sources


A Containment Need may arise from one or several governed Harm dynamics.

These include:

Active Harm continuation

Accumulation

Compounding

Propagation

Cascading

Boundary expansion

new exposure creation

or:

other materially relevant continuation

HCNM must preserve which Harm dynamic creates the Need.

A generic statement that “Containment is required” is insufficient where
the actual target of Containment is unknown.


  • Harm Dynamics as the Basis


HCNM should use the best available governed representation of Harm
dynamics.


Conceptually:

Harm State + Harm Trajectory + Propagation Pathways + Cascade Development
+ Relevant Uncertainty → Containment Need


The Need must therefore remain linked to actual Harm conditions rather
than only to:


policy preference

organizational concern

public perception

administrative status

or:

completion of an internal process

  • Active Harm ≠ Automatic Containment Need


An Active Harm may already be bounded.

For example, an existing physical injury may remain Active but no longer
be capable of spreading or increasing through the original mechanism.


The Harm may require:

Mitigation

Recovery

and:

Monitoring

without an active Need to contain further expansion.

Therefore:

Active Harm ≠ Active Containment Need by Default

  • Limited Harm May Create High Containment Need


The opposite condition is also possible.

Current Harm may be limited while its propagation potential is
substantial.


For example:

Limited Harm + Rapid Propagation Potential → High Containment Need

HCNM must therefore avoid deriving Containment Need solely from present
Harm magnitude.


Canonical principle:

Small Current Harm ≠ Small Containment Need

  • Accumulation-Based Containment Need


Where repeated or continuing contributions are increasing Harm:

Contribution₁ + Contribution₂ + Contribution₃ + …

HCNM may establish a Need to interrupt further contribution.

The Containment target becomes:

additional accumulation

rather than:

the accumulated Harm already present

Therefore:

Containment of Accumulation Targets Further Contribution, Not Historical
Harm


  • Compounding-Based Containment Need


Where interacting conditions materially amplify existing Harm, the Need
may concern:


preventing further interaction

separating conditions

interrupting a dependency

or:

preventing additional amplification

The Need should identify the materially relevant compounding relationship
without prescribing the eventual Containment action.


  • Propagation-Based Containment Need


Where Harm is spreading, HCNM should identify whether further:

subjects

objects

systems

organizations

locations

domains

infrastructure

environments

or:

populations

may become materially affected.

The Containment Need must remain connected to the actual or sufficiently
governed propagation pathway.


  • Cascade-Based Containment Need


Where Harm is generating further Harm:

Harm₁ → Harm₂ → Harm₃

Containment Need may exist at several points.

HCNM may identify:

upstream Need

pathway Need

branch-specific Need

or:

downstream Need

without deciding which Containment action will ultimately be selected.

  • Continuation After Mechanism Termination


A Containment Need may remain after the originating mechanism has stopped.

For example:

System Stopped → Harm Continues Propagating

or:

Source Removed → Environmental Harm Continues Moving

Therefore:

Mechanism Termination ≠ Containment Need Termination

HCNM follows Harm dynamics rather than mechanism status.

  • Containment Need Under Uncertainty


Containment Need does not require complete knowledge of every future Harm
consequence.


Where credible governed information indicates a materially relevant
possibility of further Harm, uncertainty must be represented rather than
converted into either:


false certainty

or:

false absence of Need

Possible states may include:

Containment Need Established

Containment Need Partially Established

Potential Containment Need

Containment Need Uncertain

No Active Containment Need Established

  • Urgency


Containment Need may carry different urgency.

Relevant factors may include:

Propagation velocity

rate of accumulation

rate of compounding

cascade development

time to additional exposure

irreversibility

difficulty of later Containment

and:

material expansion potential

Urgency concerns:

how quickly Containment governance must act

It does not automatically represent:

Harm severity

or:

liability

  • Containment Priority


Where several Harm dynamics require Containment simultaneously, HCNM may
establish relative operational priority.


Priority may consider:

immediacy

expansion potential

Propagation velocity

cascade potential

additional affected scope

irreversibility

Containment window

and:

dependency between Containment Needs

Priority must be traceable to the governed Harm dynamics.

Canonical distinction:

Containment Priority ≠ Harm Value Ranking

  • Containment Window


Some Harm dynamics may only remain containable within a limited period.

HCNM may identify a:

Containment Window

representing the period within which intervention can materially prevent
further Harm development.


The window may be:

Immediate

Short

Extended

Conditional

or:

Uncertain

A closing Containment Window may increase urgency even where current Harm
remains limited.


  • Containment Objective Formation


HCNM must convert the identified Need into a sufficiently clear
Containment Objective.


Examples include:

prevent further exposure

stop additional accumulation

interrupt a compounding interaction

stop propagation beyond Scope A

prevent Harm₂ from generating Harm₃

or:

prevent additional systems from becoming affected

The objective describes:

what further Harm development must be prevented

It does not prescribe:

how the intervention must be performed

That belongs to subsequent Containment Action governance.

  • Objective Specificity


A Containment Objective must be specific enough to support later
verification.


For example:

“Contain the situation”

is methodologically weak.

Whereas:

“Prevent the governed Harm from propagating from System A into currently
unaffected dependent systems”


creates a verifiable objective.

Canonical principle:

A Containment Need that cannot identify what must stop cannot support
reliable Containment Verification.


  • Multiple Containment Needs


One Harm may produce several simultaneous Containment Needs.

For example:

stop additional exposure

interrupt current propagation

and:

prevent cascade formation

These Needs should not be artificially collapsed where they require
materially different governance.


HCNM may therefore produce a:

Containment Need Set

linked to one governed Harm.

  • Distributed Containment Need


In distributed environments, the Need may span:

multiple agents

systems

providers

organizations

locations

or:

infrastructure

No single component may contain the complete Harm dynamic.

Canonical principle:

Distributed Harm Dynamics Require Distributed Containment Need
Representation.


A local Need must not be mistaken for the complete Containment Need.

  • Composite Containment Need


Composite Harm may require Containment even where no single component
independently creates sufficient Need.


Conceptually:

Limited Dynamic₁ + Limited Dynamic₂ + Limited Dynamic₃ → Material
Composite Containment Need


Therefore:

No Single Dominant Harm Pathway ≠ No Containment Need

The appropriate Harm-object level must govern the conclusion.

  • Collective Containment Need


Collective Harm may require Containment even where no single affected
individual demonstrates the complete Harm dynamic.


HCNM must support Need determination at:

group

population

system

infrastructure

environment

or:

societal

level where appropriate.

Therefore:

No Single Dominant Harmed Subject ≠ No Collective Containment Need

  • Containment Need Reassessment


Containment Need is not permanently fixed.

It must be reassessed where material changes occur in:

Harm State

Accumulation

Compounding

Propagation

Cascading

Boundary

affected scope

intervention capability

or:

operational reality

A Need may:

emerge

increase

decrease

change target

become uncertain

or:

cease

  • Containment Need Persistence


A Need remains active while the material possibility of the targeted
further Harm development remains sufficiently present.


Therefore:

Containment Action Initiated ≠ Containment Need Ended

and:

Temporary Harm Stability ≠ Containment Need Ended by Default

The Need should not close merely because intervention has begun.

  • Containment Need Closure


A Containment Need may cease when:

the targeted Harm dynamic is no longer materially capable of continuing

or:

verified Containment has removed the relevant further-development pathway

subject to appropriate monitoring and uncertainty.

However:

Containment Need Closed ≠ Harm Resolved

The existing Harm may continue through:

Mitigation

Recovery

Residual Harm

Resolution

and:

Finality

  • Prediction and Simulation Boundary


PGA™ may identify possible future Harm trajectories.

SIMULOS® may model potential spread or Containment scenarios.

These may support HCNM.

But:

Predicted Harm Expansion ≠ Actual Harm Expansion

and:

Simulated Containment Need ≠ Established Containment Need

HCNM must anchor its output in the governed operational Harm context while
preserving uncertainty about future development.


  • Accountability and Liability Boundary


Containment Need is independent of whether responsibility or liability has
been established.


Urgent Harm Containment may be necessary before those questions are
resolved.


Therefore:

Unresolved Accountability ≠ No Containment Need

Unresolved Liability ≠ No Containment Need

HCNM governs prevention of additional Harm, not assignment of
responsibility.


  • Minimum Implementation Framework


A minimum HCNM implementation requires eight capabilities.

  • Harm Dynamic Intake


Receive and maintain the relevant Governed Harm State and Harm Change &
Propagation information.


  • Further-Harm Potential Assessment


Determine whether Harm may materially continue, increase, accumulate,
compound, propagate, cascade, or create additional Harm.


  • Containment Need Qualification


Distinguish Established, Partial, Potential, Uncertain, and No Active
Containment Need conditions.


  • Urgency & Containment Window Governance


Represent how quickly intervention may be required and whether the
opportunity for effective Containment is time-limited.


  • Containment Priority Governance


Prioritize multiple Containment Needs using traceable Harm-dynamic factors
without converting priority into Harm value ranking.


  • Containment Objective Formation


Define what further Harm development must be prevented without prematurely
prescribing the intervention mechanism.


  • Reassessment & Need Persistence


Maintain, update, escalate, reduce, or close Containment Need as Harm
dynamics and operational conditions change.


  • Governed Output


Produce a traceable Governed Harm Containment Need suitable for
Containment Action governance. 32. Use Case 1 — Limited Harm With Rapid
Propagation Potential


A digital Harm currently affects only one operational environment.

HCPS establishes that an active pathway could rapidly propagate the Harm
into numerous dependent systems.


The current Harm remains limited, but the opportunity to interrupt the
pathway is short.


HCNM therefore establishes:

Limited Current Harm + High Propagation Potential + Short Containment
Window → High-Urgency Containment Need


It does not wait for widespread Harm before recognizing the Need.

The governing principle is:

Containment Need is determined by the material possibility of additional
Harm, not only by the amount of Harm already present.


  • Use Case 2 — Source Stopped but Cascade Continues


An operational failure produces Harm₁.

The original process is stopped.

However, Harm₁ has already created Harm₂, and Harm₂ remains capable of
producing Harm₃.


HCNM does not conclude:

Source Stopped → No Containment Need

Instead it evaluates the active downstream Harm dynamics and establishes a
Containment Need directed at preventing further cascade development.


The governing principle is:

Mechanism termination does not terminate Containment Need while Harm
remains capable of producing further Harm.


  • Governance Requirements


HCNM requires that:

  • Containment Need be derived from an already governed Harm
  • current Harm severity not be used as the sole proxy for
    Containment


Need; - further-Harm potential remain distinguishable from existing Harm
magnitude; - the Harm dynamic creating the Need be explicitly identified;
- Accumulation-, Compounding-, Propagation-, and Cascade-based Needs
remain distinguishable; - mechanism termination not automatically
terminate Containment Need; - uncertainty not be converted into false
absence of Need; - urgency remain distinguishable from Harm severity; -
priority remain traceable to Harm dynamics; - time-limited Containment
opportunities remain representable; - every Containment Need produce a
sufficiently specific Containment Objective; - multiple Needs remain
separately governable where necessary; - distributed, composite, and
collective Containment Needs remain representable; - Containment Need be
reassessed when Harm dynamics materially change; - action initiation not
automatically close the Need; - Need closure remain separate from Harm
Resolution or Finality; - Prediction and Simulation support but do not
replace actual Need governance; - accountability and liability
determination not be prerequisites for necessary Harm Containment.


  • Governance Logic


HCNM applies the following logic:

Does a governed Harm exist?

If no:

→ HCNM does not establish formal Harm Containment Need.

If yes:

→ assess the current Harm dynamics.

Can the Harm materially continue, increase, accumulate, compound,
propagate, cascade, expand scope, or generate additional Harm?


If no:

→ No Active Containment Need may be established, subject to Monitoring and
uncertainty.


If yes or materially possible:

→ identify the specific dynamic requiring Containment.

Then determine:

What further Harm development must be prevented?

→ establish the Containment Objective.

How quickly may that development occur?

→ establish urgency.

Is effective Containment time-limited?

→ establish the Containment Window.

Are multiple Containment Needs present?

→ preserve and prioritize them where required.

Is the Need distributed, composite, or collective?

→ evaluate it at the appropriate Harm-object level.

Is material uncertainty present?

→ preserve the uncertainty state.

The output becomes:

Governed Harm Containment Need → Containment Action Governance

At every stage:

Existing Harm ≠ Automatic Containment Need

Current Severity ≠ Containment Need

Small Current Harm ≠ Small Containment Need

Mechanism Termination ≠ Containment Need Termination

Action Initiated ≠ Need Ended

Need Closed ≠ Harm Resolved

  • Governance Outputs


HCNM may produce:

Governed Harm Containment Need

Containment Need State

Containment Need Basis

Further-Harm Potential

Target Harm Dynamic

Containment Objective

Containment Urgency

Containment Priority

Containment Window

Containment Need Set

Distributed Containment Need

Composite Containment Need

Collective Containment Need

Containment Need Uncertainty

Containment Need Reassessment Trigger

Containment Need Escalation

Containment Need Reduction

and:

Containment Need Closure

The principal output is:

Governed Harm Containment Need

  • Critical Distinctions


Existing Harm ≠ Automatic Containment Need

Containment Need ≠ New Harm Determination

Current Harm Severity ≠ Containment Need

Active Harm ≠ Active Containment Need

Small Current Harm ≠ Small Containment Need

Containment Priority ≠ Harm Value Ranking

Accumulation ≠ Accumulation-Based Containment Need

Propagation ≠ Propagation-Based Containment Need

Mechanism Termination ≠ Containment Need Termination

Uncertainty ≠ No Containment Need

Prediction ≠ Established Containment Need

Simulation ≠ Established Containment Need

No Single Dominant Harm Pathway ≠ No Composite Containment Need

No Single Dominant Subject ≠ No Collective Containment Need

Containment Action Initiated ≠ Containment Need Ended

Temporary Stability ≠ Need Closure

Containment Need Closed ≠ Harm Resolved

Unresolved Accountability ≠ No Containment Need

Unresolved Liability ≠ No Containment Need

  • Canonical Boundary


The HCNM — Harm Containment Need Module governs whether an already
governed Harm presents a materially relevant need for intervention to
prevent further continuation, expansion, accumulation, compounding,
propagation, cascading, additional exposure, or creation of downstream
Harm. It governs the identification, qualification, urgency, priority,
Containment Window, objective formation, persistence, reassessment,
uncertainty, and closure of that Need. HCNM does not determine whether
Harm originally exists, perform Recognition or Determination,
independently redefine the Governed Harm Boundary, select or execute the
Containment Action, establish the Containment Boundary, verify Containment
effectiveness, perform Mitigation, govern Recovery, Residual Harm,
Resolution or Finality, determine general causation, or assign
accountability, responsibility, or liability.


  • Canonical Closing Statement


Containment should not begin only after Harm has already reached its
largest observable form.


A limited Harm may create an urgent Containment Need when its pathway
remains open, while a severe but fully bounded Harm may require Mitigation
rather than further Containment.


HCNM governs that distinction by asking not only how much Harm exists now,
but what additional Harm remains materially possible if nothing interrupts
its development.


Containment Need begins where existing Harm still has somewhere further to
go.