HMVM — Harm Mitigation Verification Module
OOF® Origin Open Foundation®
Independent Methodological Authority
Canonical Definition
The HMVM — Harm Mitigation Verification Module governs how a claimed HarmMitigation Outcome is verified to determine whether existing governed Harm
or its consequences have actually been materially reduced to the extent
represented.
HMVM establishes the methodological basis for verifying whether the
Mitigation Objective was materially achieved, whether claimed Harm
reduction is supported by sufficient operational reality, whether the
reduction applies across the represented scope, whether materially
relevant remaining or adverse Harm has been preserved, whether the
reduction persists sufficiently for the claim being made, and what
Mitigation State can legitimately be established.
It establishes the transition:
Governed Harm Mitigation Need + Governed Harm Mitigation Action + Governed
Harm Mitigation Effect + Governed Harm Mitigation Outcome → Verification
Basis → Outcome Verification → Remaining Harm Confirmation → Verification
Determination → Governed Harm Mitigation State
Its central question is:
Can the claimed reduction in existing Harm or its consequences be
legitimately established on a sufficient governed basis?
- Operational Role
HMNM determines:
what Harm should be reduced.
HMAM determines:
what action attempts that reduction.
HMEM determines:
what materially changed.
HMOM determines:
what those changes mean as an overall Mitigation Outcome.
HMVM determines:
whether that Outcome can legitimately be accepted as the governed
Mitigation State.
Its operational role is:
to prevent claimed Harm reduction from becoming a governance conclusion
without sufficient verification.
- Position Within HMS
The HMS governance flow is:
Mitigation Need → Mitigation Action → Mitigation Effect → Mitigation
Outcome → Mitigation Verification
HMVM governs the final stage:
Mitigation Verification
It receives the complete materially relevant Mitigation chain and producesthe principal HMS output:
Governed Harm Mitigation State
This output supports transition toward:Harm Recovery & Residual Harm Governance
while further Mitigation or Containment may continue where required.- Governed Object
The primary governed object is:
Verified Harm Mitigation State
HMVM does not merely verify that:an action occurred
an effect was observed
or:
an Outcome was recorded
It verifies whether the claimed Harm reduction is sufficiently supported
to become a governed Mitigation conclusion.
Therefore:
Recorded Mitigation Outcome ≠ Verified Mitigation State
- Foundational Verification Principle
The foundational rule is:
Mitigation is verified by demonstrated material reduction in Harm or its
consequences—not by intervention completion, effort, intention, or
procedural success.
Therefore:
Action Completed ≠ Mitigation Verified
Effect Observed ≠ Mitigation Verified
and:
Outcome Claimed ≠ Mitigation Verified
- Verification Chain
HMVM preserves the complete traceability chain:
Harm → Mitigation Need → Baseline → Objective → Action → Effect → Outcome
→ Verification
A broken material link in this chain may limit the strength of the
Mitigation determination.
Verification must answer not only:
Did something improve?
but:
Did the governed Harm identified for reduction materially improve to the
extent represented by the Mitigation Outcome?
- Verification Basis
The Verification Basis may include materially relevant:
Mitigation Baseline
Mitigation Objective
Mitigation Action State
Mitigation Effect
Effect magnitude
Effect distribution
Effect persistence
remaining Harmadverse effects
current Harm condition
and:
relevant operational observations
The basis must be sufficient for the scope and strength of the Mitigation
claim being made.
- Objective Verification
HMVM verifies the claimed Outcome against the original Mitigation
Objective.
Conceptually:
Mitigation Objective ↔ Verified Harm Condition
The relevant question is:
Was the Harm condition changed to the extent required by the objective?
A positive change may still be insufficient.
Therefore:
Improvement ≠ Objective Achievement by Default
- Baseline Verification
A Harm reduction claim depends on a meaningful comparison basis.
HMVM must determine whether the Mitigation Baseline is sufficiently
reliable for the claimed reduction.
If the baseline is materially uncertain, outdated, incomplete, or
incomparable, the verification conclusion must reflect that limitation.
Canonical principle:
An uncertain baseline cannot support false precision in a Mitigation
claim.
- Action Verification ≠ Mitigation Verification
Evidence that the intervention was correctly executed may support the
verification chain.
It does not prove Harm reduction.
Therefore:
Verified Mitigation Action ≠ Verified Harm Mitigation
HMVM remains consequence-based.
- Effect Verification
HMVM determines whether the material effects used in the Mitigation
Outcome are sufficiently supported.
It should distinguish:
observed effect
inferred effect
predicted effect
simulated effect
and:
verified operational effect
Canonical distinctions:
Predicted Effect ≠ Verified Effect
Simulated Effect ≠ Verified Operational Effect
- Outcome Verification
HMVM evaluates whether the Governed Harm Mitigation Outcome accurately
represents the complete materially relevant effect structure.
It asks:
Were beneficial effects represented correctly?
Was remaining Harm preserved?
Were adverse effects included?
Was Harm displacement preserved?
Was Harm substitution preserved?
Were materially different affected groups represented?
Was uncertainty retained?
A Mitigation Outcome that omits materially adverse information cannot
support a complete verification conclusion.
- Remaining Harm Confirmation
HMVM must explicitly preserve materially relevant Harm remaining after
Mitigation.
This may include:
unreduced Harm
partially reduced Harm
persistent consequences
unaffected components
ongoing impairment
distributed remaining Harm
or:
new Harm
Canonical principle:
Verification of Harm reduction must not erase verification of Harm
remaining.
- Scope Verification
A Mitigation claim must be verified at the scope at which it is made.
If evidence supports:
System A mitigated
it cannot automatically establish:Entire distributed system mitigated
If evidence supports:Group A improved
it cannot automatically establish:Entire affected population mitigated
Therefore:Verified Local Mitigation ≠ Verified Global Mitigation
- Component Verification
Composite Harm may require component-level verification.
If:
Component₁ → Mitigated
Component₂ → Partially Mitigated
Component₃ → Unchanged
then the complete Harm cannot automatically be verified as fully
Mitigated.
Therefore:
Verified Component Mitigation ≠ Verified Composite Mitigation
- Collective Verification
Where Harm is collective, verification must correspond to the collective
governed object.
Selected individual improvements may support the determination but cannot
automatically establish collective Mitigation.
Canonical distinction:
Verified Individual Improvement ≠ Verified Collective Harm Mitigation
- Distributed Verification
Distributed Harm may span:
systems
organizations
agents
providers
locations
infrastructure
or:
domains
Evidence fragmentation must not produce an artificially fragmented Harm
conclusion.
HMVM must determine whether the complete claimed scope has sufficient
verification coverage.
- Cross-Domain Verification
A Harm may improve in one domain while remaining or worsening in another.
Therefore:
Verified Domain-Specific Mitigation ≠ Verified Complete Harm Mitigation
HMVM must preserve cross-domain differences where materially relevant to
the Mitigation claim.
- Temporal Verification
The required verification period depends on the Harm and the claimed
Mitigation Outcome.
Some reduction can be established immediately.
Other reduction requires observation sufficient to distinguish:
temporary improvement
from:
persistent reduction
Therefore:
Immediate Improvement ≠ Persistent Mitigation by Default
- Persistence Verification
Where the Mitigation claim includes durable or persistent reduction, HMVM
must determine whether the effect persisted sufficiently to support that
claim.
A temporary improvement may legitimately be verified as:
Temporary Mitigation
without being represented as:Persistent Mitigation
Canonical principle:Verification strength must not exceed demonstrated effect persistence.
- Delayed Effects
Mitigation may produce delayed beneficial or adverse effects.
HMVM should consider whether the observation period is sufficient for
materially relevant latency.
Therefore:
No Immediate Adverse Effect ≠ No Mitigation-Induced Harm by Default
and:
No Immediate Improvement ≠ No Mitigation Benefit by Default
Verification timing must fit Harm reality.
- Harm Displacement Verification
Where Harm decreases in one location or subject but appears elsewhere,
HMVM must determine whether the claimed Mitigation scope remains
legitimate.
Canonical principle:
Moving Harm outside the observed scope does not verify Harm reduction.
Therefore:
Observed Local Reduction ≠ Verified Overall Reduction
- Harm Substitution Verification
Where Harm₁ decreases while Harm₂ emerges, HMVM must preserve both.
A claim such as:
Harm₁ Mitigated
may be valid.
A broader claim such as:
Overall Harm Mitigated
may not be valid without considering Harm₂.Therefore:
Verified Reduction of Harm₁ ≠ Verified Absence of Harm₂
- Intervention-Induced Harm Verification
Mitigation-induced Harm must remain visible in the verification basis.
HMVM does not require every new Harm to be fully governed through its
complete lifecycle before the original Mitigation can be assessed.
However, materially relevant new Harm cannot be omitted from the claimed
Outcome.
Canonical principle:
A verified benefit cannot make a verified adverse consequence disappear.
- Net Improvement Verification
Net improvement may be useful where multiple beneficial and adverse
effects coexist.
But aggregate improvement cannot substitute for materially important
distributional information.
Therefore:
Verified Positive Net Effect ≠ Verified Harm Absence
and:
Net Benefit ≠ Complete Verification by Default
- Continuing Harm Production
Existing Harm may be materially reduced while additional Harm continues to
be produced.
HMVM must distinguish:
Verified Mitigation
from:Verified Containment
A Harm may therefore be:Partially Mitigated + Not Fully Contained
or:
Mitigated in one dimension + continuing in another
Canonical principle:
Harm Reduction ≠ Harm Production Stopped
- Verification Uncertainty
Uncertainty may arise from:
incomplete baseline
insufficient observation
unknown effect persistence
missing scope coverage
conflicting evidence
distributed Harm
unresolved adverse effects
confounding conditions
or:
measurement limitations
HMVM must preserve uncertainty explicitly.
Therefore:
Insufficient Verification Basis ≠ Verified Mitigation
- Conflicting Evidence
Evidence may indicate different Mitigation conditions.
For example:
one measurement indicates substantial improvement
while:
another materially relevant observation indicates continuing Harm
HMVM must not resolve such conflict through arbitrary selection of the
favorable signal.
It should establish:
Mitigation Uncertain
or another appropriately bounded state until the conflict can be resolved.- Partial Verification
Where some elements of the Mitigation Outcome are sufficiently supported
while others remain uncertain, HMVM may establish:
Partially Verified Mitigation
The verified portion and unresolved portion should remain distinguishable.Canonical principle:
Partial Verification ≠ Complete Verification
- Verification Failure
Verification Failure occurs where the available basis does not support the
Mitigation claim being made.
This may result from:
unsupported effect
invalid comparison basis
insufficient scope coverage
unresolved adverse Harm
insufficient persistence
materially contradictory evidence
or:
incorrect Outcome representation
Verification Failure does not necessarily mean no Mitigation occurred.
It means:
the claimed Mitigation State cannot currently be established on a
sufficient governed basis.
- Mitigation States
HMVM may establish states such as:
Mitigation Required
Mitigation In Progress
Partially Mitigated
Mitigated
Mitigation Insufficient
Mitigation Uncertain
Mitigation Degraded
Mitigation Lost
Mitigation Adverse
or:Further Mitigation Required
The state must reflect the strongest conclusion legitimately supported bythe verification basis.
- Criteria for Mitigated State
A governed Harm may be classified as:
Mitigated
relative to the applicable Mitigation Objective where there is sufficientbasis that:
the targeted Harm or consequence materially decreased
the represented reduction is supported across the claimed scope
material adverse effects have not been omitted
remaining Harm has been preserved
required persistence is sufficiently demonstrated
and:
the Mitigation Outcome is consistent with current Harm reality
This does not mean the Harm no longer exists.
- Verification and Harm State
A verified Mitigation State may trigger Harm State reassessment.
For example:
Active → Reduced
or:
Stabilized → Reduced
However:
Verified Mitigation State ≠ Harm State
HSS retains formal Harm State governance.
- Verification and Further Mitigation
Verification may establish that further Mitigation remains necessary.
For example:
Partially Mitigated → Further Mitigation Required
or:
Mitigation Insufficient → Mitigation Need Reassessment
Verification therefore does not necessarily terminate HMS.
It may restart or continue the Mitigation cycle.
- Verification and Recovery
Verified Mitigation creates a governed basis for transition toward:
Harm Recovery & Residual Harm Governance
But:Verified Mitigation ≠ Recovery
A subject or system may remain significantly impaired despite verified
Harm reduction.
HRRHS owns Recovery determination.
- Verification and Residual Harm
HMVM preserves remaining Harm but does not formally classify it as
Residual Harm.
That requires HRRHS governance.
Therefore:
Verified Remaining Harm ≠ Residual Harm Determination by Default
- Verification and Resolution
A verified Mitigation State does not establish Resolution.
Therefore:
Verified Mitigation ≠ Harm Resolution
The Harm lifecycle continues where relevant through Recovery, Residual
Harm, Resolution, and Finality.
- Verification and Finality
Even complete verified achievement of a Mitigation Objective does not
establish Harm Finality.
Canonical principle:
Verified Harm Reduction ≠ Harm Lifecycle Completion
Finality belongs to HRFS.
- Reverification
Mitigation may require reverification where:
effects decay
Harm returns
new Harm emergesscope changes
new information appears
Recovery reveals remaining Harm
Containment changes
or:the prior Mitigation basis becomes materially outdated
Therefore:
Verification ≠ Permanent Certification of Mitigation
A verified state remains connected to current Harm reality.
- Verification History
HMVM should preserve materially relevant:
Verification Basis
Verification Criteria
Mitigation Objective
Baseline
verified effectsremaining Harm
scope limitations
uncertainty
adverse effects
determination
reverification triggers
and:
state changes
This creates a traceable:
Mitigation Verification History
- Minimum Implementation Framework
A minimum HMVM implementation requires eight capabilities.
- End-to-End Mitigation Traceability
Maintain the governed chain from Harm and Mitigation Need through
Baseline, Objective, Action, Effect, Outcome, and Verification.
- Baseline & Objective Verification
Determine whether the comparison basis is sufficient and whether the
claimed Harm reduction corresponds to the governed Mitigation Objective.
- Effect & Outcome Verification
Verify that material Harm effects occurred and that the Mitigation Outcome
accurately represents those effects.
- Scope, Composite & Distribution Verification
Verify the claimed Mitigation across relevant subjects, Harm components,
collectives, systems, locations, and domains without converting local
success into complete success.
- Remaining, Displaced & New Harm Preservation
Preserve remaining Harm, Harm displacement, Harm substitution,
intervention-induced Harm, and continuing Harm production within the
verification basis.
- Temporal, Persistence & Uncertainty Governance
Ensure verification strength reflects observation duration, effect
persistence, latency, uncertainty, conflicting evidence, and material
limitations.
- State Determination & Reverification
Establish the legitimate Governed Harm Mitigation State and trigger
further Mitigation, Harm State reassessment, or reverification where
material conditions change.
- Governed Output
Produce a traceable Governed Harm Mitigation State suitable for transition
toward Harm Recovery & Residual Harm Governance. 42. Use Case 1 — Strong
Improvement but Insufficient Observation Time
A Mitigation Action produces a substantial immediate reduction in a
governed Harm condition.
The Mitigation Objective requires a durable reduction.
Only a short observation period is currently available.
HMVM may verify:
Immediate Harm Reduction
while preserving:Persistent Mitigation — Not Yet Established
It does not convert early success into a stronger claim than the evidencesupports.
The governing principle is:
Verification strength must not exceed demonstrated effect persistence.
- Use Case 2 — Local Harm Reduction Hides Displacement
A Mitigation Action produces verified Harm reduction within the primary
observed system.
Further assessment shows that part of the harmful consequence has shifted
into another connected system.
HMVM does not verify:
Complete Harm Mitigation
merely because the original system improved.It preserves both:
Verified Local Harm Reduction
and:Remaining / Displaced Harm
within the Mitigation determination.The governing principle is:
Moving Harm outside the observed scope does not verify Harm reduction.
- Governance Requirements
HMVM requires that:
- Mitigation Verification remain consequence-based
- the complete Need-to-Verification chain remain traceable
- the Verification Basis be proportionate to the strength and scope
of
the Mitigation claim; - Mitigation Objective achievement be tested against
the actual Harm condition; - baseline uncertainty limit claim precision; -
Action Verification remain distinct from Mitigation Verification; -
predicted and simulated effects remain distinct from verified operational
effects; - Mitigation Outcome accurately preserve beneficial, adverse,
partial, and uncertain effects; - remaining Harm remain explicit; -
verification scope match the scope of the claim; - component success not
automatically establish composite success; - individual success not
automatically establish collective Mitigation; - local success not
automatically establish distributed Mitigation; - domain-specific success
not automatically establish complete Mitigation; - persistence claims
require sufficient temporal support; - delayed effects remain governable;
- Harm displacement and substitution remain visible; -
intervention-induced Harm remain part of the Verification Basis; -
aggregate improvement not erase materially distinct adverse Harm; -
continuing Harm production remain distinct from Harm reduction; -
uncertainty and conflicting evidence remain explicit; - Partial
Verification remain distinct from complete Verification; - Verification
Failure not be falsely equated with proof that no Mitigation occurred; -
verified Mitigation remain distinct from Harm State; - further Mitigation
remain possible after Verification; - Mitigation remain distinct from
Recovery, Residual Harm, Resolution, and Finality; - material changes
trigger reverification.
- Governance Logic
HMVM applies the following logic:
Does a Governed Harm Mitigation Outcome exist?
If no:
→ final Mitigation Verification cannot be completed.
If yes:
→ reconstruct the governed Mitigation chain:
Harm → Need → Baseline → Objective → Action → Effect → Outcome
Then ask:
Is the Baseline sufficient?
Was the Mitigation Objective explicit?
Did a material Harm Effect actually occur?
Does the Outcome accurately represent that Effect?
What Harm remains?
Did Harm move elsewhere?
Did new Harm emerge?
Does continuing Harm production remain active?
Then test scope:
Is the claim individual, collective, component, composite, local,
distributed, or cross-domain?
Does the Verification Basis cover that scope?
Then test time:
Was the reduction immediate, temporary, persistent, degrading, or
uncertain?
Then ask:
Does the available basis support the Mitigation claim at the strength
being asserted?
If yes:
→ establish the appropriate:
Governed Harm Mitigation State
If partially:→ establish Partial Mitigation / Partial Verification.
If insufficient:
→ establish Mitigation Insufficient or Verification Failure as
appropriate.
If uncertain:
→ preserve Mitigation Uncertainty.
Then determine whether:
Further Mitigation is required
Harm State requires reassessment
or:transition toward Recovery & Residual Harm governance is appropriate
Throughout:
Action ≠ Effect
Effect ≠ Outcome
Outcome ≠ Verification
Local Reduction ≠ Complete Reduction
Temporary Reduction ≠ Persistent Mitigation
Net Benefit ≠ Harm Absence
Mitigation ≠ Recovery
Mitigation ≠ Resolution
Mitigation ≠ Finality
- Governance Outputs
HMVM may produce:
Governed Harm Mitigation State
Mitigation Verification Basis
Mitigation Verification Criteria
Baseline Verification State
Objective Achievement Verification
Effect Verification State
Outcome Verification State
Remaining Harm Confirmation
Scope Verification State
Composite Mitigation Verification
Collective Mitigation Verification
Distributed Mitigation Verification
Cross-Domain Mitigation Verification
Persistence Verification State
Partial Verification
Mitigation Uncertainty
Mitigation Verification Failure
Further Mitigation Requirement
Harm State Reassessment Trigger
Reverification Requirement
Recovery & Residual Harm Governance Handoff
and:Mitigation Verification History
The principal output is:Governed Harm Mitigation State
- Critical Distinctions
Recorded Outcome ≠ Verified Mitigation State
Action Completed ≠ Mitigation Verified
Effect Observed ≠ Mitigation Verified
Outcome Claimed ≠ Mitigation Verified
Improvement ≠ Objective Achievement
Verified Action ≠ Verified Harm Mitigation
Predicted Effect ≠ Verified Effect
Simulated Effect ≠ Verified Operational Effect
Verified Local Mitigation ≠ Verified Global Mitigation
Verified Component Mitigation ≠ Verified Composite Mitigation
Verified Individual Improvement ≠ Verified Collective Harm Mitigation
Domain-Specific Mitigation ≠ Complete Harm Mitigation
Immediate Improvement ≠ Persistent Mitigation
Observed Local Reduction ≠ Verified Overall Reduction
Verified Reduction of Harm₁ ≠ Verified Absence of Harm₂
Verified Positive Net Effect ≠ Verified Harm Absence
Harm Reduction ≠ Harm Production Stopped
Insufficient Verification Basis ≠ Verified Mitigation
Partial Verification ≠ Complete Verification
Verified Mitigation State ≠ Harm State
Verified Mitigation ≠ Recovery
Verified Remaining Harm ≠ Residual Harm Determination
Verified Mitigation ≠ Harm Resolution
Verified Harm Reduction ≠ Harm Lifecycle Completion
Verification ≠ Permanent Certification
- Canonical Boundary
The HMVM — Harm Mitigation Verification Module governs whether a claimed
Harm Mitigation Outcome can legitimately be established as a Governed Harm
Mitigation State on a sufficient methodological and operational basis. It
governs end-to-end Mitigation traceability, Baseline and Objective
verification, Effect and Outcome verification, remaining Harm
confirmation, scope coverage, component, collective, distributed and
cross-domain verification, temporal sufficiency, persistence, Harm
displacement, substitution, intervention-induced Harm, uncertainty,
conflicting evidence, Partial Verification, Verification Failure, state
determination, and reverification. HMVM does not determine whether Harm
originally exists, establish the original Mitigation Need, select or
execute Mitigation Action, independently determine Mitigation Effect or
Outcome, perform Harm Containment, formally determine Recovery or Residual
Harm, establish Resolution or Finality, determine general causation,
assign accountability, responsibility, or liability, or replace evidence,
validation, integrity, or audit governance performed by adjacent OOF®
architectures.
- Canonical Closing Statement
Mitigation becomes a governed conclusion only when the claimed reduction
in Harm can withstand verification.
An action may succeed operationally, an effect may appear beneficial, and
an outcome may look positive while remaining Harm, displaced Harm, limited
scope, insufficient persistence, or uncertainty still prevents the
stronger claim.
HMVM therefore verifies Mitigation at the level at which Harm actually
changed and only to the extent that change can legitimately be
established.
Harm is mitigated not when improvement is claimed, but when material
reduction can be governed as real.