HRPM — Harm Recovery Progress Module

OOF® Origin Open Foundation®

Independent Methodological Authority

Canonical Definition

The HRPM — Harm Recovery Progress Module governs how Recovery from
governed Harm progresses after Recovery has been initiated, including how
material movement toward a Recovery Target is observed, represented,
compared, tracked, and reassessed across time.


HRPM governs the Recovery trajectory rather than merely recording Recovery
activity. It determines whether the affected condition is materially
improving, remaining stable, plateauing, fluctuating, regressing,
progressing unevenly, or becoming uncertain, while preserving differences
across affected components, subjects, groups, systems, locations, and Harm
domains.


It establishes the transition:

Governed Harm Recovery Initiation State + Recovery Reference Condition +
Recovery Target → Recovery Observation → Recovery Change → Recovery
Trajectory → Recovery Stability / Plateau / Regression → Governed Harm
Recovery Progress State


Its central question is:

How is the affected condition actually progressing after Recovery has
begun?


  • Operational Role


HRIM-R establishes:

Recovery has begun.

HRPM establishes:

how Recovery is moving.

Its operational role is:

to convert Recovery from a declared process into a governed trajectory of
actual change in the affected condition.


Recovery Progress is therefore not measured by:

time spent recovering

number of interventions

resources consumed

recovery activities completed

or:

effort applied

unless those factors materially correspond to actual Recovery change.

Canonical principle:

Recovery Progress is governed by change in the affected condition—not by
activity performed around it.


  • Position Within HRRHS


The HRRHS governance flow is:

Recovery Initiation → Recovery Progress → Recovery Evaluation → Residual
Harm Identification → Residual Harm State


HRPM governs the second stage:

Recovery Progress

It receives principally:

Governed Harm Recovery Initiation State

together with:

Recovery Reference Condition

Recovery Target

Current Harm State

and materially relevant Recovery information.

It produces:

Governed Harm Recovery Progress State

for:

HREM — Harm Recovery Evaluation Module

  • Governed Object


The primary governed object is:

Recovery Trajectory of the Affected Condition

The governed object is not the Recovery program itself.

HRPM follows what is happening to:

function

capability

stability

integrity

independence

performance

operational capacity

environmental condition

or another materially relevant recoverable dimension.

Therefore:

Recovery Process Activity ≠ Recovery Progress

  • Foundational Progress Principle


The foundational rule is:

Recovery Progress exists only where the affected condition materially
moves through its Recovery trajectory.


Therefore:

Recovery Activity ↑ ≠ Recovery Progress ↑

and:

Time in Recovery ≠ Recovery Progress

A Recovery process may remain active while actual Recovery Progress:

accelerates

slows

stops

or:

reverses

  • Recovery Reference Continuity


HRPM maintains continuity with the:

Recovery Reference Condition

established at Recovery Initiation.

Conceptually:

Recovery Reference Condition → Current Recovery Condition → Recovery
Target


Progress must be interpreted relative to a meaningful governed reference.

Where material conditions change, the reference may require reassessment.

However:

Reference Change ≠ Historical Recovery Erasure

Earlier Recovery Progress remains part of the lifecycle record.

  • Recovery Target Continuity


Recovery Progress must remain connected to the relevant Recovery Target.

HRPM asks:

Where did Recovery begin?

Where is the affected condition now?

Toward what condition is Recovery moving?

The Recovery Target may evolve where operational reality materially
changes.


But target changes must remain traceable.

Otherwise, a deteriorating Recovery process could appear successful merely
because the target was weakened.


Canonical principle:

Changing the Recovery Target must not rewrite the Recovery already
observed.


  • Recovery Observation


HRPM requires materially relevant observation of the affected condition.

Observation may concern:

functional change

capability change

stability

structural condition

operational performance

independence

environmental function

collective condition

or another relevant Recovery dimension.

The observation method may differ by domain.

The governance requirement remains constant:

Recovery must be observed where Recovery is claimed to occur.

  • Recovery Change


Recovery Change represents a materially relevant difference between
Recovery conditions across time.


Conceptually:

Recovery Conditionₜ₁ → Recovery Conditionₜ₂

The change may represent:

Improvement

No Material Change

Fluctuation

Regression

or:

Uncertain Change

Not every measurable difference constitutes meaningful Recovery Progress.

Therefore:

Measured Change ≠ Material Recovery Change by Default

  • Recovery Trajectory


HRPM represents Recovery as a trajectory.

A trajectory may be:

Improving

Accelerating

Decelerating

Stable

Plateaued

Fluctuating

Regressing

Interrupted

or:

Uncertain

This prevents binary treatment of Recovery as:

Recovering / Not Recovering

where the actual lifecycle is more complex.

  • Recovery Velocity


Where methodologically appropriate, Recovery may be evaluated not only by
direction but by rate.


Conceptually:

Recovery Change / Relevant Time → Recovery Velocity

Velocity may indicate:

rapid improvement

gradual improvement

deceleration

stagnation

or:

deterioration

However:

Fast Recovery ≠ Better Final Recovery by Default

and:

Slow Recovery ≠ Recovery Failure

Rate and achieved condition remain distinct.

  • Recovery Acceleration and Deceleration


Recovery may change speed.

A rapidly improving condition may later slow.

A slow process may accelerate.

HRPM may therefore preserve:

Recovery Acceleration

and:

Recovery Deceleration

where materially useful.

A slowing Recovery trajectory does not automatically mean Recovery has
stopped.


Therefore:

Recovery Deceleration ≠ Recovery Plateau

  • Recovery Stability


Progress may appear beneficial but remain unstable.

HRPM distinguishes:

Improvement

from:

Stable Improvement

A condition repeatedly moving between improvement and deterioration may
not support the same Progress State as a consistently improving condition.


Canonical distinction:

Observed Improvement ≠ Stable Recovery Progress

  • Recovery Fluctuation


Recovery may naturally fluctuate.

Short-term deterioration does not automatically constitute overall
Recovery Regression.


Likewise, short-term improvement does not automatically establish a
positive Recovery trajectory.


HRPM evaluates materially appropriate temporal patterns.

Therefore:

Temporary Deterioration ≠ Recovery Failure

and:

Temporary Improvement ≠ Sustained Recovery Progress

  • Recovery Plateau


A Recovery Plateau occurs where materially meaningful progress ceases for
a relevant period while the affected condition remains approximately
stable.


Conceptually:

Improvement → Reduced Improvement → No Material Progress

A plateau may be:

Temporary

Persistent

Expected

Unexpected

or:

Uncertain

Canonical principle:

Recovery Plateau is a Recovery condition requiring evaluation—not
automatic proof that Recovery has reached its legitimate endpoint.


  • Recovery Regression


Recovery Regression occurs where the affected condition materially moves
away from the achieved Recovery condition or relevant Recovery Target.


Conceptually:

Recovered Conditionₜ₁ → Deteriorated Conditionₜ₂

Regression may be:

Temporary

Progressive

Localized

Distributed

Cross-Domain

or:

Uncertain

Canonical principle:

Historical Recovery does not override present deterioration.

  • Recovery Interruption


Recovery may be interrupted without being permanently terminated.

Interruption may result from:

new Harm

resource loss

dependency failure

renewed exposure

failed Containment

changed operating conditions

or:

other materially relevant disruption

HRPM preserves:

Recovery Interrupted

without automatically concluding:

Recovery Failed

  • Recovery Restart


An interrupted, plateaued, or regressed Recovery process may later resume.

Therefore:

Recovery Interruption ≠ Recovery Termination

HRPM must support:

Recovery → Interruption → Restart

without treating the restarted process as unrelated to the earlier Harm
lifecycle.


  • Partial Recovery Progress


Some Recovery dimensions may improve while others do not.

For example:

Function ↑

Independence ↑

Structural Condition unchanged

Stability uncertain

HRPM must preserve this structure.

Therefore:

Progress in One Recovery Dimension ≠ Complete Recovery Progress

  • Uneven Recovery


Recovery may be uneven across:

components

subjects

groups

locations

systems

or:

domains

An aggregate improvement must not erase materially important non-recovery
or regression.


Canonical principle:

Average Recovery Progress ≠ Recovery Progress for Every Affected Element

  • Composite Recovery Progress


Composite Harm may produce multiple Recovery trajectories.

For example:

Component A → Improving

Component B → Plateaued

Component C → Regressing

The complete Progress State must preserve these differences.

Therefore:

Component Progress ≠ Composite Recovery Progress by Default

  • Collective Recovery Progress


Where the governed Harm affects a group or population, HRPM must evaluate
Recovery at the relevant collective level.


Selected individuals may recover quickly while other affected populations
remain unchanged.


Therefore:

Individual Recovery Progress ≠ Collective Recovery Progress

Material distribution remains part of the Recovery trajectory.

  • Distributed Recovery Progress


Distributed systems, organizations, infrastructure, or environments may
recover asynchronously.


For example:

Location A → Recovered rapidly

Location B → Recovering slowly

Location C → Regressing

A local trajectory must not automatically become the distributed
conclusion.


Therefore:

Local Recovery Progress ≠ System-Wide Recovery Progress

  • Cross-Domain Recovery Progress


Recovery may differ materially across Harm domains.

For example:

Physical Recovery ↑

Operational Recovery ↑

Financial Recovery → Plateau

Cognitive Recovery ↓

HRPM must preserve those domain differences.

Therefore:

Cross-Domain Recovery cannot be represented by the strongest Recovery
trajectory alone.


  • Recovery Dependencies


Recovery Progress may depend on continuing conditions such as:

Mitigation

Containment

support

resources

infrastructure

environmental stability

external services

or:

other operational dependencies

HRPM must preserve materially relevant dependencies where their loss could
alter Recovery Progress.


  • Dependency-Supported Recovery


A subject may appear recovered only while an external dependency remains
active.


For example:

temporary technical support

substitute infrastructure

continuous treatment

external operational assistance

or:

manual intervention

may maintain function.

This does not invalidate Recovery Progress.

But it changes what the Progress State means.

Canonical distinction:

Dependency-Supported Function ≠ Independent Recovery by Default

  • Adaptation During Recovery


Adaptation may occur alongside genuine Recovery.

Conceptually:

Recovery + Adaptation

may jointly improve operational function.

HRPM must distinguish:

condition actually recovering

from:

function preserved through adaptation

where the distinction materially affects the Recovery trajectory.

Therefore:

Improved Function ≠ Recovery Progress by Default

  • New Harm During Recovery


New Harm may emerge while Recovery progresses.

This may:

slow Recovery

interrupt Recovery

reverse Recovery

change the Recovery Target

or:

create a separate Harm lifecycle

HRPM must not absorb new Harm into Recovery terminology.

Canonical principle:

Recovery does not make new Harm methodologically invisible.

  • Continuing Original Harm


Recovery may progress while original Harm remains active.

Therefore:

Recovery Progress ≠ Original Harm Ended

HRPM preserves the relationship between:

Current Harm State

and:

Recovery Progress State

without collapsing them.

  • Recovery Progress Uncertainty


Recovery Progress may remain uncertain because of:

insufficient observation

measurement limitations

natural fluctuation

latent effects

distributed conditions

conflicting indicators

dependency effects

or:

uncertain Recovery reference conditions

HRPM must represent uncertainty explicitly.

Therefore:

Uncertain Progress ≠ No Progress

and:

Uncertain Progress ≠ Positive Progress

  • Conflicting Recovery Signals


Different observations may point in different directions.

For example:

functional capability improves

while:

underlying stability deteriorates

or:

average group condition improves

while:

a materially affected subgroup worsens

HRPM must preserve materially relevant conflict rather than selecting only
the favorable signal.


  • Recovery Progress States


HRPM may represent Progress through states such as:

Recovery Initiated

Recovery Improving

Recovery Accelerating

Recovery Decelerating

Recovery Stable

Recovery Plateaued

Recovery Fluctuating

Recovery Interrupted

Recovery Regressing

Recovery Restarted

or:

Recovery Progress Uncertain

These states describe trajectory.

They do not determine final Recovery achievement.

  • Recovery Progress Reassessment


Progress must be reassessed where materially relevant:

trajectory changes

regression occurs

dependencies change

new Harm emerges

Containment changes

Mitigation changes

Recovery Target changes

scope changes

or:

new observations materially alter the Recovery picture

Canonical principle:

Recovery Progress must follow current Recovery reality rather than
preserve an outdated trajectory classification.


  • Progress History


HRPM should preserve materially relevant Recovery history.

Conceptually:

Initiation → Improvement → Plateau → Restart → Improvement → Regression →
…


This prevents the current state from erasing earlier lifecycle
information.


Therefore:

Current Recovery State ≠ Complete Recovery History

  • Handoff to Recovery Evaluation


HRPM produces:

Governed Harm Recovery Progress State

for:

HREM — Harm Recovery Evaluation Module

The handoff asks:

Given the Recovery trajectory observed, what Recovery condition has
actually been achieved?


Therefore:

Recovery Progress ≠ Recovery Evaluation

and:

Positive Recovery Trajectory ≠ Recovery Achieved

  • Minimum Implementation Framework


A minimum HRPM implementation requires eight capabilities.

  • Recovery Condition Observation


Observe materially relevant changes in the function, capability,
stability, integrity, independence, performance, or other governed
condition entering Recovery.


  • Reference & Target Continuity


Maintain traceability between the Recovery Reference Condition, current
Recovery condition, and Recovery Target without allowing target changes to
rewrite historical Progress.


  • Recovery Change & Trajectory Determination


Determine whether Recovery is improving, stable, plateaued, fluctuating,
interrupted, regressing, restarting, or uncertain.


  • Stability, Plateau & Regression Governance


Distinguish sustained progress from temporary improvement and govern
material plateau, interruption, deterioration, and restart.


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


Preserve materially different Recovery trajectories across components,
subjects, groups, systems, locations, and Harm domains.


  • Dependency, Adaptation & Continuing Harm Governance


Preserve materially relevant dependencies, adaptation, continuing original
Harm, and new Harm without misrepresenting them as Recovery Progress.


  • Uncertainty, Reassessment & History


Preserve conflicting signals and uncertainty, trigger reassessment when
Recovery reality changes, and maintain material Recovery trajectory
history.


  • Governed Output


Produce a traceable Governed Harm Recovery Progress State suitable for
Recovery Evaluation. 37. Use Case 1 — Recovery Improves and Then Plateaus


An affected subject begins Recovery and shows substantial early
improvement.


After a period of progress, the relevant condition stops materially
improving while remaining below the Recovery Target.


HRPM represents:

Recovery Initiated → Recovery Improving → Recovery Plateaued

It does not automatically classify the plateau as:

Recovery Complete

or:

Recovery Failed

The governing principle is:

A plateau describes the Recovery trajectory; it does not determine the
final Recovery condition.


  • Use Case 2 — Distributed Recovery With Opposing Trajectories


A distributed operational system is recovering from governed Harm.

Several locations regain capability, while another materially important
location begins to deteriorate after initial improvement.


HRPM preserves:

Location A → Improving

Location B → Improving

Location C → Regressing

rather than representing the entire system through its positive average
trajectory.


The governing principle is:

Recovery Progress must preserve where Recovery is occurring, where it has
stopped, and where it is reversing.


  • Governance Requirements


HRPM requires that:

  • Recovery Progress remain distinct from Recovery activity
  • Progress be grounded in material change in the affected condition
  • Recovery Reference continuity be preserved
  • Recovery Target changes remain traceable
  • measurable change not automatically become material Recovery
    Progress
  • Recovery be represented as a trajectory rather than only a binary


state; - Recovery velocity not be confused with final Recovery quality; -
deceleration remain distinct from plateau; - observed improvement remain
distinct from stable progress; - temporary fluctuation remain
distinguishable from sustained trajectory; - plateau not automatically
establish Recovery completion; - regression remain visible despite earlier
improvement; - interruption remain distinct from Recovery termination; -
Recovery restart remain lifecycle-continuous; - partial and uneven
Progress remain representable; - component Progress not automatically
establish composite Progress; - individual Progress not automatically
establish collective Progress; - local Progress not automatically
establish distributed Progress; - cross-domain differences remain visible;
- materially relevant dependencies remain explicit; - dependency-supported
function remain distinguishable from independent Recovery; - adaptation
remain distinguishable from actual Recovery Progress; - new Harm remain
independently visible; - continuing original Harm remain visible; -
uncertainty and conflicting signals remain explicit; - current Progress
remain reassessable; - material Recovery history remain preserved; -
Recovery Progress remain distinct from Recovery Evaluation.


  • Governance Logic


HRPM applies the following logic:

Has Recovery been initiated?

If no:

→ Recovery Progress should not be established.

If yes:

→ establish continuity with:

Recovery Reference Condition + Recovery Target

Then observe:

What materially relevant condition has changed?

Determine:

Direction

Magnitude

Timing

Stability

and where useful:

Rate

Then classify the trajectory:

Improving?

Accelerating?

Decelerating?

Stable?

Plateaued?

Fluctuating?

Interrupted?

Regressing?

Restarted?

Uncertain?

Then ask:

Does the trajectory differ across components?

subjects?

groups?

systems?

locations?

domains?

Then determine:

Is the apparent Progress dependent on external support?

Is adaptation being confused with Recovery?

Does original Harm continue?

Has new Harm emerged?

Are materially relevant signals conflicting?

Has the Recovery Target or reference condition changed?

Then establish:

Governed Harm Recovery Progress State

and hand off:

Recovery Progress → Recovery Evaluation

Throughout:

Activity ≠ Progress

Time ≠ Progress

Measured Change ≠ Material Progress

Improvement ≠ Stable Progress

Plateau ≠ Recovery Completion

Regression ≠ Erasure of Historical Recovery

Adaptation ≠ Recovery by Default

Local Progress ≠ Complete Progress

Progress ≠ Recovery Achievement

  • Governance Outputs


HRPM may produce:

Governed Harm Recovery Progress State

Current Recovery Condition

Recovery Change State

Recovery Trajectory

Recovery Velocity

Recovery Acceleration / Deceleration State

Recovery Stability State

Recovery Plateau State

Recovery Fluctuation State

Recovery Interruption State

Recovery Regression State

Recovery Restart State

Partial Recovery Progress State

Composite Recovery Progress State

Collective Recovery Progress State

Distributed Recovery Progress State

Cross-Domain Recovery Progress State

Recovery Dependency State

Recovery Progress Uncertainty

Recovery Reassessment Trigger

Recovery Progress History

and:

Recovery Evaluation Readiness State

The principal output is:

Governed Harm Recovery Progress State

  • Critical Distinctions


Recovery Process Activity ≠ Recovery Progress

Recovery Activity ↑ ≠ Recovery Progress ↑

Time in Recovery ≠ Recovery Progress

Reference Change ≠ Historical Recovery Erasure

Measured Change ≠ Material Recovery Change

Fast Recovery ≠ Better Final Recovery

Slow Recovery ≠ Recovery Failure

Recovery Deceleration ≠ Recovery Plateau

Observed Improvement ≠ Stable Recovery Progress

Temporary Deterioration ≠ Recovery Failure

Temporary Improvement ≠ Sustained Recovery Progress

Recovery Plateau ≠ Recovery Completion

Historical Recovery ≠ Current Recovery State

Recovery Interruption ≠ Recovery Termination

Progress in One Dimension ≠ Complete Recovery Progress

Component Progress ≠ Composite Recovery Progress

Individual Recovery Progress ≠ Collective Recovery Progress

Local Recovery Progress ≠ System-Wide Recovery Progress

Dependency-Supported Function ≠ Independent Recovery

Improved Function ≠ Recovery Progress by Default

Recovery Progress ≠ Original Harm Ended

Uncertain Progress ≠ No Progress

Current Recovery State ≠ Complete Recovery History

Recovery Progress ≠ Recovery Evaluation

Positive Recovery Trajectory ≠ Recovery Achieved

  • Canonical Boundary


The HRPM — Harm Recovery Progress Module governs how an initiated Recovery
process materially progresses through time, including Recovery
observation, change, trajectory, velocity where relevant, stability,
fluctuation, plateau, interruption, regression, restart, partial and
uneven Progress, composite, collective, distributed and cross-domain
Progress, materially relevant dependencies, adaptation, continuing and new
Harm interactions, uncertainty, reassessment, and Recovery history. HRPM
does not determine whether Harm originally exists, perform Harm
Recognition or Determination, independently establish the Harm Boundary,
perform Harm Containment or Mitigation, establish initial Recovery
Initiation, determine final Recovery achievement, formally identify or
classify Residual Harm, establish Resolution or Finality, determine
general causation, or assign accountability, responsibility, liability,
claims, or compensation.


  • Canonical Closing Statement


Recovery is not a timestamp between Harm and resolution. It is a
trajectory.


That trajectory may accelerate, slow, plateau, fluctuate, regress,
restart, or move differently across affected components while the Recovery
process remains active.


HRPM keeps those changes visible so that Recovery cannot be inferred from
elapsed time, completed activity, or the strongest improving signal.


Recovery Progress is governed by where the affected condition is actually
moving.