HCAM-C — Harm Containment Action Module
OOF® Origin Open Foundation®
Independent Methodological Authority
Canonical Definition
The HCAM-C — Harm Containment Action Module governs how an establishedHarm Containment Need is translated into a defined, authorized, targeted,
proportionate, executable, and traceable Containment action capable of
materially interrupting the Harm dynamic that created the Need.
HCAM-C establishes what the Containment action is intended to stop, which
Harm pathway or dynamic it must affect, whether the action can
operationally reach that target, what dependencies and conditions are
required for execution, what additional Harm the intervention itself may
create, and what action state must be transferred into Containment
Boundary and Persistence governance.
It establishes the transition:
Governed Harm Containment Need → Action Objective → Action Selection →
Reachability → Action Authorization → Action Execution → Governed Harm
Containment Action
Its central question is:
What intervention can materially reach and interrupt the Harm dynamic that
created the Containment Need without creating an unjustified new Harm
condition?
- Operational Role
HCNM establishes:
what further Harm must be prevented.
HCAM-C determines:
what intervention can operationally act against that Harm development.
Its operational role is:
to translate Containment Need into an executable intervention while
preserving the distinction between selecting an action, executing an
action, and actually containing Harm.
The foundational sequence is:
Need → Objective → Action → Reach → Authorization → Execution
But:
Execution ≠ Containment
- Position Within HCOS
The HCOS governance flow is:
Containment Need → Containment Action → Containment Boundary → Containment
Persistence → Containment Verification
HCAM-C governs the second stage:
Containment Action
It receives:Governed Harm Containment Need
and produces:Governed Harm Containment Action
for subsequent Containment Boundary governance.- Governed Object
The primary governed object is:
Intervention Intended to Prevent Further Harm Development
The intervention may target:continuing Harm production
additional exposure
Accumulation
Compounding
Propagation
Cascade development
or another materially relevant Harm pathway.HCAM-C does not govern the underlying operational system generally.
It governs the intervention specifically insofar as it serves Harm
Containment.
- Foundational Action Principle
The foundational rule is:
A Containment action is governed by the Harm dynamic it must interrupt,
not merely by the mechanism available to perform it.
Organizations may possess many intervention capabilities.
Their existence does not establish that they are suitable for the Harm in
question.
Therefore:
Available Intervention ≠ Appropriate Containment Action
- Containment Objective Alignment
Every action must remain linked to the Containment Objective established
by HCNM.
Conceptually:
Containment Need → Containment Objective → Containment Action
If the Need is:
prevent additional Propagation
the selected action must materially affect the relevant Propagation
pathway.
If the Need is:
prevent further Accumulation
the action must materially interrupt additional Harm contribution.
Canonical principle:
An action that does not address the governed Containment Objective is not
an adequate Containment action merely because it constitutes intervention.
- Action Selection
HCAM-C must support selection among materially appropriate intervention
types.
These may include:
Isolation
Restriction
Separation
Suspension
Shutdown
Quarantine
Segmentation
Access Limitation
Execution Interruption
Dependency Interruption
Physical Bounding
Environmental Containment
Process Restriction
or another context-appropriate mechanism.The module does not prescribe a universal intervention type.
The selected action must fit the governed Harm dynamic.
- Action Target
Every Containment action requires an explicit target.
The target may be:
Harm-producing mechanism
Propagation pathway
Accumulation source
Compounding interaction
cascade pathwayexposure pathway
dependency
execution node
affected interface
or:
another materially relevant Containment point
Canonical distinction:
Intervention Target ≠ Harm Object by Default
The intervention may target a mechanism or pathway in order to contain the
Harm.
- Action Reachability
A selected action must be capable of reaching its intended target.
Reachability asks:
Can the intervention actually affect the pathway through which further
Harm is developing?
A theoretically suitable action that cannot reach the relevant target is
operationally insufficient.
Canonical principle:
A Containment action that cannot reach the Harm pathway it is intended to
interrupt cannot establish effective Containment.
- Reachability in Distributed Systems
In distributed environments, intervention may reach:
System A
while Harm continues through:System B
Agent C
Sub-Agent D
External Tool E
or:replicated execution elsewhere
Therefore:
Reach to One Component ≠ Reach to the Complete Harm Dynamic
HCAM-C must evaluate materially relevant execution and Harm pathways
rather than merely the visible interface.
- Composite Action
One Containment Need may require several coordinated actions.
Conceptually:
Action₁ + Action₂ + Action₃ → Composite Containment Intervention
For example:
isolate source
block pathway
restrict downstream execution
and:
protect unaffected scope
may all be required.
Therefore:
Single Action ≠ Complete Containment Strategy by Default
- Distributed Action
Containment may require actions across:
multiple systems
organizations
providers
agents
locations
jurisdictions
or:
infrastructure components
HCAM-C must preserve the relationship between these actions as one
governed intervention structure where they address the same Containment
Need.
Operational fragmentation must not fragment the Containment objective.
- Action Timing
The effectiveness of a Containment action may depend on when it occurs.
HCAM-C should preserve materially relevant:
required action time
actual action time
delay
Containment Window
and:timing uncertainty
An appropriate action executed too late may fail to prevent additional
Harm.
Therefore:
Correct Action ≠ Effective Action When Executed Outside the Relevant
Containment Window
- Action Urgency
Where HCNM establishes high urgency, HCAM-C must preserve that urgency
through action selection and execution.
The action process must not silently convert:
Immediate Containment Need
into:ordinary administrative workflow
where delay materially increases Harm.
Canonical principle:
Governance procedure must not become a mechanism through which preventable
Harm continues.
- Action Authorization
Containment actions may affect:
systems
people
property
data
operations
access
infrastructure
or:
organizational processes
The selected action must therefore have appropriate authority where
required.
HCAM-C must distinguish:
technical capability to act
from:
authority to act
Canonical distinction:
Capability ≠ Authority
- Emergency Action
Some Harm dynamics may require immediate intervention before normal
governance processes can be completed.
Where an emergency Containment mechanism exists, HCAM-C must preserve:
the basis for emergency action
the authority invoked
the action performed
its scope
its duration
and:
required subsequent review
Emergency status must not erase governance.
- Action Proportionality
A Containment action may itself affect subjects, systems, organizations,
environments, or infrastructure.
HCAM-C therefore requires the intervention to be proportionate to the
governed Containment Need where alternatives exist.
The objective is not:
minimum intervention at any cost
nor:
maximum intervention by default
It is:
sufficient intervention to materially address the Containment Need without
unnecessary additional Harm.
- Intervention-Induced Harm
Containment itself may create Harm.
For example:
emergency shutdown
may prevent catastrophic Propagation while causing operational or
financial Harm.
physical isolation
may prevent environmental spread while affecting other systems.
HCAM-C must therefore preserve:
Containment Benefit
and:Potential Intervention-Induced Harm
without confusing them.Canonical principle:
Preventing one Harm does not make Harm created by the intervention
methodologically invisible.
Where new Harm emerges, it enters appropriate HAGA™ lifecycle governance.
- Harm Trade-Off Boundary
HCAM-C may require explicit recognition that several action options create
different Harm consequences.
However, HCAM-C does not become a general value-optimization architecture.
It must identify whether an intervention:
materially addresses the Containment Need
and:
creates materially relevant additional Harm
Any broader value comparison remains within appropriate governance spaces.
- Action Dependencies
Containment actions may depend on:
permissions
access
technical capability
human availability
external providers
infrastructure
communications
physical resources
or:
other actions
These dependencies must be identified where their failure could prevent
execution.
Canonical principle:
Planned Action Without Required Capability ≠ Executable Containment Action
- Action Preconditions
Some actions require conditions to be satisfied before execution.
HCAM-C should govern materially relevant preconditions such as:
target identification
access availability
authority confirmation
dependency state
safety conditions
or:
required coordination
Preconditions must not become invisible assumptions.
- Action Coordination
Where multiple actors must intervene, HCAM-C must preserve:
who or what executes each action
which actions depend on others
required sequence
timing relationships
and:
coordination status
Coordination is particularly important where partial execution could leave
Harm pathways active.
- Action Sequence
Containment actions may need to occur in a specific order.
For example:
Isolate → Disable → Block Dependency → Confirm Execution
Executing the same actions in another order may create additional Harm or
allow temporary Propagation.
Therefore:
Correct Actions in the Wrong Sequence ≠ Correct Containment Execution
- Action State
HCAM-C may represent action states such as:
Proposed
Selected
Authorized
Ready
Executing
Executed
Partially Executed
Blocked
Failed
Withdrawn
or:Superseded
These are action states.They are not Containment effectiveness states.
Canonical distinction:
Action State ≠ Containment State
- Partial Execution
Where only part of a Composite Containment Action is executed, the
incomplete condition must remain explicit.
For example:
Action₁ — Executed
Action₂ — Blocked
Action₃ — Pending
must not become:
Containment Action Completed
if the composite intervention requires all three.- Action Failure
Action Failure may result from:
lack of reach
lack of authority
technical failure
dependency failure
timing failure
coordination failure
incorrect target
changed Harm dynamics
or:
intervention bypass
Failure must generate reassessment rather than administrative closure.
- Action Adaptation
Harm may change while intervention is being prepared or executed.
HCAM-C must support action adaptation where:
Propagation changes
new pathways appearthe target moves
the Containment Window changes
a cascade develops
or:
the selected intervention becomes insufficient
Canonical principle:
Containment Action must remain aligned with current Harm reality, not only
with the Harm state that existed when the action was selected.
- Action Replacement and Escalation
An ineffective or insufficient action may need to be:
modified
supplemented
replaced
or:
escalated
HCAM-C should preserve the relationship between:
original action
reason for change
and:
replacement action
This maintains intervention continuity and traceability.
- Execution Verification Boundary
HCAM-C may establish whether the selected action was actually executed.
But execution verification does not establish that Harm was contained.
Conceptually:
Action Selected → Action Executed → Containment Effect Evaluated Later
Therefore:
Verified Execution ≠ Verified Containment
HCVM owns Containment Verification.
- Action Traceability
Every material Containment action should remain traceable to:
the Containment Need
Containment Objective
target Harm dynamicselected intervention
authority where required
execution state
dependencies
material changes
and:
subsequent Containment governance
This creates a coherent chain:
Need → Objective → Action → Execution → Containment Evaluation
- Minimum Implementation Framework
A minimum HCAM-C implementation requires eight capabilities.
- Objective-to-Action Mapping
Translate the Governed Harm Containment Need and Containment Objective
into candidate interventions addressing the correct Harm dynamic.
- Action Selection & Targeting
Select a materially appropriate intervention and identify the exact
mechanism, pathway, dependency, interaction, or other Containment target.
- Reachability Assessment
Determine whether the intervention can operationally reach the relevant
Harm pathway, including distributed and composite environments.
- Authority & Executability Control
Establish required authority, capability, dependencies, preconditions,
timing, and resources necessary for execution.
- Intervention Harm & Proportionality Governance
Identify materially relevant Harm that the intervention itself may create
and preserve proportionality between Need and action.
- Composite & Distributed Action Coordination
Govern multi-action, multi-system, multi-agent, multi-organization, and
sequenced Containment interventions.
- Execution State & Adaptation
Preserve execution state, partial execution, failure, replacement,
escalation, and adaptation to changing Harm dynamics.
- Governed Output
Produce a traceable Governed Harm Containment Action suitable for
Containment Boundary and subsequent HCOS governance. 32. Use Case 1 —
Distributed Autonomous Execution
A Harm-producing autonomous process has been delegated across several
agents and external execution environments.
Stopping the visible primary agent does not reach several already
delegated execution paths.
HCAM-C rejects:
Primary Agent Stopped → Adequate Containment Action
and instead evaluates the complete Harm pathway.
A Composite Containment Action is established to reach the materially
relevant execution paths.
The governing principle is:
An intervention that reaches the interface but not the execution capable
of continuing Harm is not an adequate Containment action.
- Use Case 2 — Containment Action Creates Secondary Harm
An infrastructure system must be shut down immediately to prevent rapidly
propagating physical Harm.
Shutdown is capable of interrupting the relevant pathway, but it will also
create materially relevant service disruption affecting other subjects.
HCAM-C does not ignore that consequence.
It governs the shutdown as the Containment action while preserving the
resulting Harm-relevant consequences for appropriate HAGA™ lifecycle
governance.
The governing principle is:
Necessary Containment does not make Harm created by the intervention cease
to be Harm.
- Governance Requirements
HCAM-C requires that:
- every action remain linked to a Governed Harm Containment Need
- every action address an explicit Containment Objective
- available intervention remain distinguishable from appropriate
intervention; - the action target remain explicit; - reachability be
established before action adequacy is assumed; - local reach not be
mistaken for distributed reach; - Composite Containment actions remain
governable as coordinated structures; - timing and Containment Window
remain operationally relevant; - urgency not be lost through
administrative delay; - capability remain distinguishable from authority;
- emergency action preserve subsequent governance and traceability; -
intervention-induced Harm remain visible; - proportionality remain
governable; - dependencies and preconditions remain explicit; -
multi-party actions preserve coordination and sequence; - action state
remain separate from Containment state; - partial execution remain
visible; - failure trigger reassessment; - actions remain adaptable to
changing Harm dynamics; - replacement and escalation preserve intervention
history; - execution verification remain separate from Containment
Verification; - all material actions remain traceable to the Need and
Objective that justified them.
- Governance Logic
HCAM-C applies the following logic:
Does a Governed Harm Containment Need exist?
If no:
→ no formal HCAM-C Containment Action is established.
If yes:
→ identify the Containment Objective.
Then ask:
What Harm dynamic must the intervention interrupt?
→ identify the Containment target.
Which candidate action can materially affect that target?
→ evaluate action suitability.
Can the action reach the relevant pathway?
If no:
→ reject or supplement the action.
If yes:
→ evaluate authority, capability, dependencies, preconditions, timing, and
execution feasibility.
Then ask:
Could the intervention itself create materially relevant Harm?
If yes:
→ preserve that Harm-relevant consequence and apply appropriate
governance.
Does the Need require several coordinated actions?
If yes:
→ establish a Composite or Distributed Containment Action.
Then:
Is the action authorized and executable?
If yes:
→ execute and record the actual action state.
If partially:
→ preserve Partial Execution.
If failed:
→ reassess, replace, supplement, or escalate.
The output becomes:
Governed Harm Containment Action → Containment Boundary Governance
Throughout:
Available Action ≠ Appropriate Action
Capability ≠ Authority
Reach to One Component ≠ Reach to Complete Harm Dynamic
Action Selected ≠ Action Executed
Action Executed ≠ Harm Contained
Verified Execution ≠ Verified Containment
- Governance Outputs
HCAM-C may produce:
Governed Harm Containment Action
Containment Action Objective
Containment Action Target
Selected Containment Action
Composite Containment Action
Distributed Containment Action
Action Reachability State
Action Authority State
Action Executability State
Action Timing Requirement
Action Dependency Set
Action Preconditions
Action Coordination State
Action Sequence
Potential Intervention-Induced Harm
Action Execution State
Partial Execution State
Action Failure
Action Adaptation Requirement
Action Replacement
and:Action Escalation
The principal output is:Governed Harm Containment Action
- Critical Distinctions
Available Intervention ≠ Appropriate Containment Action
Intervention Target ≠ Harm Object
Capability ≠ Authority
Reach to One Component ≠ Reach to Complete Harm Dynamic
Single Action ≠ Complete Containment Strategy
Correct Action ≠ Timely Action
Action Selected ≠ Action Authorized
Action Authorized ≠ Action Executed
Action Executed ≠ Harm Contained
Action State ≠ Containment State
Partial Execution ≠ Complete Execution
Intervention Harm ≠ Original Harm
Emergency Action ≠ Ungoverned Action
Planned Action ≠ Executable Action
Correct Actions in Wrong Sequence ≠ Correct Containment Execution
Verified Execution ≠ Verified Containment
- Canonical Boundary
The HCAM-C — Harm Containment Action Module governs how a Governed Harm
Containment Need is translated into an appropriate, targeted, reachable,
authorized, executable, proportionate, coordinated, adaptable, and
traceable intervention intended to prevent further Harm development. It
governs action selection, targeting, reachability, authority, timing,
dependencies, preconditions, proportionality, intervention-induced Harm,
composite and distributed action, coordination, sequence, execution state,
partial execution, failure, adaptation, replacement, and escalation.
HCAM-C does not determine whether Harm originally exists, establish
Containment Need, independently define the Containment Boundary, establish
persistent Containment effectiveness, verify that Harm has actually been
contained, perform Harm Mitigation, govern Recovery, Residual Harm,
Resolution or Finality, determine general causation, or assign
accountability, responsibility, or liability.
- Canonical Closing Statement
Containment is not created by the existence of an intervention capability,
nor by the decision to use it.
The action must reach the Harm dynamic that matters, at the time it
matters, with sufficient authority and operational capability to interrupt
it.
Even then, execution proves only that an intervention occurred—not that
Harm was contained.
A Containment action becomes meaningful only when it is connected to the
Harm it is intended to stop.