HRSM-F — Harm Resolution State Module

OOF® Origin Open Foundation®

Independent Methodological Authority

Canonical Definition

The HRSM-F — Harm Resolution State Module governs how the current
Resolution condition of governed Harm is identified, represented,
maintained, and reassessed after Recovery and Residual Harm have been
sufficiently governed for Resolution evaluation.


HRSM-F determines whether the Harm lifecycle is not ready for Resolution,
ready for Resolution evaluation, pending Resolution, conditionally
resolved, resolved, uncertain, degraded, or no longer legitimately
resolved because the Harm condition or Resolution basis has materially
changed.


It establishes the transition:

Governed Harm Recovery & Residual Harm State → Resolution Readiness →
Resolution Condition Assessment → Resolution State Formation → Resolution
State Maintenance → Governed Harm Resolution State


Its central question is:

What is the current Resolution state of the governed Harm, and is that
state sufficiently supported by current Harm reality?


  • Operational Role


The preceding HRRHS lifecycle establishes:

what recovered

and:

what Harm remains.

HRSM-F establishes:

where the Harm currently stands in relation to Resolution.

Its operational role is:

to convert the governed post-Recovery Harm condition into an explicit
Resolution State without prematurely treating Recovery, Residual Harm
stability, administrative completion, or absence of immediate Harm
manifestation as Resolution.


The foundational distinction is:

Resolution State must represent the Harm lifecycle—not the status of an
external process associated with it.


  • Position Within HRFS


The HRFS governance flow is:

Resolution State → Resolution Criteria → Closure → Reopening → Finality

HRSM-F governs the first stage:

Resolution State

It receives principally:

Governed Harm Recovery & Residual Harm State

It produces:

Governed Harm Resolution State

for the next HRFS stage:

HRCM-F — Harm Resolution Criteria Module

  • Governed Object


The primary governed object is:

Current Harm Resolution Condition

HRSM-F does not primarily govern:

Recovery

Residual Harm

Closure

or:

Finality

It determines the current relationship between the governed Harm condition
and Resolution.


Therefore:

Post-Recovery State ≠ Resolution State by Default

  • Foundational Resolution State Principle


The foundational rule is:

A Harm Resolution State must reflect whether the governed Harm has
actually reached a condition capable of supporting Resolution—not whether
surrounding activities or processes have ended.


Therefore:

Process Ended ≠ Harm Resolved

Intervention Ended ≠ Harm Resolved

Recovery Completed ≠ Harm Resolved

  • Resolution Readiness


Before a Harm can enter Resolution evaluation, its lifecycle must be
sufficiently mature for the question of Resolution to be meaningfully
asked.


Resolution Readiness may depend on materially relevant understanding of:

current Harm State

Mitigation

Recovery

Residual Harm

continuing Harm pathways

dependencies

and:

uncertainty

Resolution Readiness is itself a governed condition.

  • Resolution Readiness ≠ Resolution


A Harm may be sufficiently understood for Resolution evaluation without
satisfying Resolution requirements.


Therefore:

Resolution Ready ≠ Resolved

This distinction prevents readiness from becoming an implicit Resolution
decision.


  • Resolution Not Ready


A Harm may remain:

Resolution Not Ready

where materially relevant lifecycle conditions remain insufficiently
governed.


Examples may include:

Recovery still materially indeterminate

Residual Harm insufficiently understood

Harm still actively propagating

current Harm Boundary materially uncertain

or:

post-Harm reality insufficiently established

This state means Resolution evaluation would be premature.

  • Resolution Pending


Resolution Pending may apply where the Harm has entered Resolution
evaluation but a legitimate Resolution determination has not yet been
completed.


Therefore:

Resolution Evaluation Started ≠ Resolution Established

Pending status preserves the distinction between process and outcome.

  • Conditionally Resolved State


A Harm may reach:

Conditionally Resolved

where Resolution is legitimate only while specified materially relevant
conditions remain satisfied.


Conditions may include:

continued support

monitoring

dependency maintenance

protective controls

environmental conditions

or:

defined Harm stability requirements

Canonical distinction:

Conditional Resolution ≠ Unconditional Resolution

  • Resolved State


A Harm may be represented as:

Resolved

where the current governed Harm condition sufficiently supports Resolution
under the applicable Resolution basis.


Resolved does not mean:

the Harm never occurred

all consequences disappeared

every subject returned to the pre-Harm state

Residual Harm is zero

or:

Finality has been reached

Therefore:

Resolved Harm ≠ Harm Erased

  • Resolution Uncertain


A Harm Resolution State must remain uncertain where materially relevant
uncertainty prevents a stronger determination.


This may arise from:

conflicting Recovery information

uncertain Residual Harm

latent Harm

insufficient observation

unstable dependencies

distributed conditions

or:

uncertain current Harm reality

Canonical principle:

Uncertainty must remain visible when it materially affects Resolution.

  • Resolution Degraded


A previously stronger Resolution State may degrade where its supporting
condition weakens.


For example:

Resolved → Resolution Degraded

may occur where:

Residual Harm begins increasing

Recovery deteriorates

dependencies weaken

or:

previous assumptions become materially uncertain

Resolution State must follow current Harm reality.

  • Resolution Lost


A previously resolved Harm may cease to satisfy the basis supporting
Resolution.


Conceptually:

Resolved → Resolution Degraded → Resolution Lost

or directly:

Resolved → Resolution Lost

where a material change is sufficiently significant.

Therefore:

Historical Resolution ≠ Permanent Current Resolution

  • Resolution State Model


HRSM-F may represent the Harm through states such as:

Resolution Not Ready

Resolution Readiness Established

Resolution Pending

Conditionally Resolved

Resolved

Resolution Uncertain

Resolution Degraded

or:

Resolution Lost

These states are methodological representations of the Harm lifecycle.

They are not administrative workflow labels.

  • Resolution State and Residual Harm


Residual Harm may coexist with multiple Resolution States.

For example:

Residual Harm + Resolution Not Ready

Residual Harm + Conditional Resolution

or:

Residual Harm + Resolved

may each be legitimate depending on the governed Harm condition.

Therefore:

Residual Harm Exists ≠ Resolution State Predetermined

  • No Residual Harm and Resolution State


The absence of identified Residual Harm does not automatically establish
Resolution.


Other conditions may remain unresolved.

Therefore:

No Residual Harm ≠ Resolved

HRSM-F evaluates the broader Harm Resolution condition.

  • Resolution State and Recovery


Recovery materially informs Resolution State but does not determine it
automatically.


A Harm may have:

Substantial Recovery + Resolution Not Ready

or:

Partial Recovery + Conditional Resolution

where legitimate.

Therefore:

Recovery State ≠ Resolution State

  • Resolution State Without Historical Restoration


Resolution does not require:

Post-Harm State = Pre-Harm State

A new stable post-Harm condition may support Resolution.

Canonical principle:

Resolution is determined by the legitimacy of the current Harm condition,
not by restoration of historical reality.


  • Resolution State and Continuing Harm


Where Harm remains actively:

emerging

accumulating

compounding

propagating

or:

cascading

a strong Resolution State may be inappropriate.

The relevant earlier HAGA™ lifecycle governance must remain active.

Therefore:

Active Harm Progression ≠ Resolved Harm

  • Resolution State and Harm Stability


Stability may support Resolution.

But:

Stable Harm ≠ Resolved Harm

Stability answers whether Harm is materially changing.

Resolution asks whether the Harm lifecycle has reached a legitimate
resolved condition.


  • Resolution State and Harm Absence


No currently observable harmful effect may support Resolution evaluation.

It does not establish Resolution by itself.

Therefore:

No Immediate Harm Observed ≠ Resolved

Latent, intermittent, distributed, or insufficiently observed Harm may
remain.


  • Resolution State and Dependencies


A Resolution State may depend on continuing external conditions.

Material dependencies should remain visible.

Examples may include:

ongoing treatment

technical support

protective infrastructure

environmental controls

human supervision

or:

operational safeguards

Therefore:

Resolved Under Dependency ≠ Dependency-Free Resolution

  • Dependency Failure


Where a material dependency supporting Resolution fails, the Resolution
State must be reassessed.


Conceptually:

Conditionally Resolved + Dependency Failure → Resolution Reassessment

The state may remain valid, degrade, or be lost depending on the resulting
Harm condition.


  • Resolution State and Adaptation


Adaptation may support a legitimate post-Harm condition.

However:

Successful Adaptation ≠ Resolution by Default

HRSM-F must preserve whether Harm itself has reached a
Resolution-supporting condition.


  • Resolution State and Compensation


Compensation does not determine Resolution State.

Therefore:

Compensated Harm ≠ Resolved Harm

and:

Uncompensated Harm ≠ Unresolved Harm by Default

The objects are separate.

  • Resolution State and External Closure


External processes may close while the Harm remains unresolved.

These may include:

incident management

claims

legal proceedings

insurance cases

internal investigations

service tickets

or:

administrative processes

Therefore:

External Closure ≠ Harm Resolution State

  • Resolution State Scope


Every Resolution State must correspond to a defined Harm scope.

The scope may specify:

which Harm

which subjects

which objects

which Harm Boundary

which domains

which locations

and:

which materially relevant conditions

Canonical principle:

A Resolution State without scope can conceal unresolved Harm.

  • Composite Resolution State


Composite Harm may contain different Resolution conditions.

For example:

Component A → Resolved

Component B → Conditionally Resolved

Component C → Resolution Not Ready

The composite state must preserve materially relevant differences.

Therefore:

Resolved Component ≠ Resolved Composite Harm

  • Collective Resolution State


Collective Harm may resolve differently across affected subjects or
subgroups.


A majority may recover while a materially significant subgroup remains
unresolved.


Therefore:

Majority Resolution ≠ Collective Resolution

HRSM-F must preserve material distribution.

  • Distributed Resolution State


Distributed Harm may have different Resolution States across:

locations

systems

organizations

infrastructure components

or:

environments

Therefore:

Local Resolution ≠ Distributed Resolution

  • Cross-Domain Resolution State


Harm may span multiple domains with different Resolution conditions.

For example:

Physical → Resolved

Operational → Resolved

Financial → Resolution Pending

Environmental → Conditional Resolution

The complete Resolution State must preserve these differences where
materially relevant.


  • Resolution State Aggregation


Where an aggregate Resolution State is required, aggregation must not
erase material unresolved conditions.


Therefore:

Strong Aggregate Resolution ≠ Universal Resolution

The methodology must preserve the components that materially constrain the
aggregate conclusion.


  • Resolution State Persistence


A Resolution State remains legitimate only while its material basis
remains sufficiently valid.


Therefore:

Resolved Once ≠ Resolved Forever

Before Finality, Resolution remains capable of change.

  • Resolution State Reassessment


Reassessment may be required where:

Recovery regresses

Residual Harm changes

Residual Harm increases

latent Harm becomes manifest

new materially relevant Harm is discovered

the Harm Boundary changes

dependencies fail

new evidence materially changes the Harm condition

or:

the previous Resolution basis becomes unreliable

  • Historical Resolution State


Resolution State history must remain preserved.

A Harm may move through:

Resolution Not Ready → Resolution Ready → Pending → Resolved → Degraded →
Lost


and later:

Pending → Resolved

The current state must not erase legitimate historical states.

Therefore:

Current Resolution State ≠ Complete Resolution History

  • Resolution State Traceability


The Resolution State should remain traceable to the relevant HAGA™
lifecycle.


Conceptually:

Governed Harm → Harm State → Containment → Mitigation → Recovery →
Residual Harm → Resolution State


This prevents Resolution from becoming an isolated declaration detached
from the Harm it claims to resolve.


  • Evidence Boundary


Evidence may support the Resolution State.

But:

Evidence ≠ Resolution State

ADIT® governs evidence and auditability.

HRSM-F governs what the supported information means for the Harm
Resolution condition.


  • Validation Boundary


VALIDOS™ may validate relevant evidence, methods, or determinations.

But:

Validated Basis ≠ Resolved Harm by Default

Validation supports the governance determination.

It does not replace it.

  • Operational Reality Boundary


ORA™ may establish relevant current operational reality.

HRSM-F determines what that reality means for the Harm Resolution State.

Therefore:

Operational Stability ≠ Harm Resolution by Default

  • Accountability and Liability Boundary


Resolution State must remain independent from:

accountability

responsibility

and:

liability

Therefore:

Accountability Established ≠ Harm Resolved

Liability Settled ≠ Harm Resolved

Harm Resolved ≠ Liability Resolved

  • Prediction and Simulation Boundary


Predicted future Resolution does not establish current Resolution.

Likewise, simulated Recovery or Resolution does not establish actual
Resolution.


Therefore:

Predicted Resolution ≠ Current Resolution

Simulated Resolution ≠ Operational Resolution

  • Resolution State Handoff


HRSM-F does not itself establish the complete criteria by which Resolution
becomes legitimate.


It determines the current Resolution condition and prepares that condition
for:


HRCM-F — Harm Resolution Criteria Module

The handoff is:

Governed Harm Resolution State → Resolution Criteria Evaluation

This preserves:

State ≠ Criteria

  • Minimum Implementation Framework


A minimum HRSM-F implementation requires exactly eight capabilities.

  • Resolution Readiness Determination


Determine whether the governed Harm lifecycle is sufficiently mature for
Resolution evaluation.


  • Resolution State Formation


Represent the current Harm as Resolution Not Ready, Ready, Pending,
Conditionally Resolved, Resolved, Uncertain, Degraded, Lost, or another
methodologically equivalent governed state.


  • Harm-State & Residual-Harm Integration


Maintain sufficient relationship between the Resolution State and current
Harm, Recovery, and Residual Harm conditions.


  • Dependency & Conditional Resolution Governance


Identify materially relevant dependencies and distinguish conditional from
dependency-free Resolution conditions.


  • Composite, Collective, Distributed & Cross-Domain State
    Governance


Preserve materially different Resolution conditions across components,
subjects, groups, locations, systems, and Harm domains.


  • Resolution Scope & Traceability


Maintain explicit Resolution scope and sufficient traceability to the
governed Harm lifecycle.


  • Reassessment, Uncertainty & State History


Preserve uncertainty, trigger reassessment when Harm reality materially
changes, and maintain material Resolution State history.


  • Governed Output


Produce a traceable Governed Harm Resolution State suitable for Resolution
Criteria governance. 45. Use Case 1 — Stable Residual Harm With Resolution
Readiness


A system experiences significant Harm and subsequently undergoes
Containment, Mitigation, and Recovery.


Most operational capability is restored, while a limited, stable,
well-understood Residual Harm condition remains.


HRSM-F does not automatically classify the Harm as unresolved merely
because Residual Harm exists.


It may establish:

Resolution Readiness Established

and transfer the Harm condition for Resolution Criteria evaluation.

The governing principle is:

Residual Harm may remain while the Harm lifecycle becomes ready for
Resolution.


  • Use Case 2 — Previously Resolved Harm Deteriorates


A governed Harm reaches Resolution and remains stable for a period.

Later, Recovery regresses and previously stable Residual Harm materially
increases.


HRSM-F does not preserve:

Resolved

merely because that state was historically legitimate.

It may transition:

Resolved → Resolution Degraded → Resolution Lost

and return the condition to appropriate active governance.

The governing principle is:

A Resolution State remains legitimate only while it continues to represent
current Harm reality.


  • Governance Requirements


HRSM-F requires that:

  • Resolution State remain distinct from Recovery, Residual Harm,


Closure, and Finality; - Resolution Readiness precede stronger Resolution
determinations where materially required; - Resolution Readiness remain
distinct from Resolution; - external process completion not determine Harm
Resolution State; - Residual Harm not automatically determine the
Resolution State; - absence of Residual Harm not automatically establish
Resolution; - Recovery State remain distinct from Resolution State; -
historical restoration not become a universal Resolution requirement; -
active Harm progression remain incompatible with unsupported strong
Resolution claims; - Harm stability not automatically establish
Resolution; - absence of immediate manifestation not automatically
establish Resolution; - materially relevant dependencies remain visible; -
dependency failure trigger reassessment where appropriate; - adaptation
not automatically establish Resolution; - compensation remain separate
from Resolution State; - Resolution State remain explicitly scoped; -
composite, collective, distributed, and cross-domain differences remain
visible; - aggregate Resolution not erase materially unresolved
conditions; - Resolution State remain capable of degradation or loss; -
reassessment follow material Harm reality changes; - historical Resolution
States remain preserved; - Resolution remain traceable to the Harm
lifecycle; - evidence, validation, Operational Reality, accountability,
liability, prediction, and simulation remain methodologically distinct; -
the output remain suitable for Resolution Criteria governance.


  • Governance Logic


HRSM-F applies the following logic:

Is the governed post-Recovery Harm condition sufficiently established?

If no:

→ Resolution Not Ready

If yes:

→ determine:

Is Resolution evaluation methodologically appropriate now?

If no:

→ maintain:

Resolution Not Ready

If yes:

→ establish:

Resolution Readiness

Then evaluate the current condition:

Does active Harm progression continue?

What Recovery has been achieved?

What Residual Harm remains?

Is the Harm condition stable?

Are material dependencies present?

Is the condition distributed or composite?

What uncertainty remains?

Based on the current governed basis, establish the applicable:

Resolution State

Then ask:

Is the Resolution State conditional?

Is it dependent on continuing support?

Does it apply to the entire Harm Boundary?

Are any components, subjects, locations, or domains materially unresolved?

Has the state changed since the previous determination?

If material change occurs:

→ reassess.

If the state remains sufficiently supported:

→ preserve it.

Then produce:

Governed Harm Resolution State

for:

HRCM-F — Harm Resolution Criteria Module

Throughout:

Ready ≠ Resolved

Recovery ≠ Resolution

Residual Harm ≠ Unresolved by Default

Stable ≠ Resolved

External Closure ≠ Resolution

Historical Resolution ≠ Current Resolution

State ≠ Criteria

  • Governance Outputs


HRSM-F may produce:

Governed Harm Resolution State

Resolution Readiness State

Resolution Not Ready State

Resolution Pending State

Conditional Resolution State

Resolved Harm State

Resolution Uncertainty State

Resolution Degraded State

Resolution Lost State

Resolution Dependency Condition

Resolution Scope

Composite Resolution State

Collective Resolution State

Distributed Resolution State

Cross-Domain Resolution State

Resolution Reassessment Trigger

Resolution State History

Resolution State Traceability

and:

Resolution Criteria Readiness State

The principal output is:

Governed Harm Resolution State

  • Critical Distinctions


Post-Recovery State ≠ Resolution State

Process Ended ≠ Harm Resolved

Intervention Ended ≠ Harm Resolved

Recovery Completed ≠ Harm Resolved

Resolution Ready ≠ Resolved

Resolution Evaluation Started ≠ Resolution Established

Conditional Resolution ≠ Unconditional Resolution

Resolved Harm ≠ Harm Erased

Historical Resolution ≠ Permanent Current Resolution

Residual Harm Exists ≠ Resolution State Predetermined

No Residual Harm ≠ Resolved

Recovery State ≠ Resolution State

Active Harm Progression ≠ Resolved Harm

Stable Harm ≠ Resolved Harm

No Immediate Harm Observed ≠ Resolved

Resolved Under Dependency ≠ Dependency-Free Resolution

Successful Adaptation ≠ Resolution

Compensated Harm ≠ Resolved Harm

External Closure ≠ Harm Resolution State

Resolved Component ≠ Resolved Composite Harm

Majority Resolution ≠ Collective Resolution

Local Resolution ≠ Distributed Resolution

Resolved Once ≠ Resolved Forever

Current Resolution State ≠ Complete Resolution History

Evidence ≠ Resolution State

Validated Basis ≠ Resolved Harm

Operational Stability ≠ Harm Resolution

Liability Settled ≠ Harm Resolved

Predicted Resolution ≠ Current Resolution

Simulated Resolution ≠ Operational Resolution

State ≠ Criteria

  • Canonical Boundary


The HRSM-F — Harm Resolution State Module governs the current Resolution
condition of governed Harm after Recovery and Residual Harm have been
sufficiently represented for Resolution evaluation. It governs Resolution
Readiness, Resolution State formation, Conditional Resolution, Resolution
uncertainty, degradation and loss, Resolution scope, material
dependencies, composite, collective, distributed and cross-domain
Resolution conditions, state reassessment, history, and traceability.
HRSM-F does not define the complete Resolution Criteria, perform Harm
lifecycle Closure, govern Reopening or Finality, independently govern
Recovery or Residual Harm, determine general causation, accountability,
responsibility, liability, claims, compensation, value consequences,
audit, validation, prediction, simulation, or jurisdiction-specific legal
resolution.


  • Canonical Closing Statement


Resolution is not a reward for completing a process and not a label
attached to the end of an intervention. It is a governed state of the Harm
itself.


That state may become ready, remain pending, depend on continuing
conditions, become legitimate, degrade, or be lost as Harm reality
changes.


HRSM-F keeps Resolution attached to that reality before any criteria are
allowed to convert it into lifecycle Closure.


A Harm is ready to move toward Resolution only when its governed
condition—not the surrounding process—supports that transition.