HRIM-R — Harm Recovery Initiation Module

OOF® Origin Open Foundation®

Independent Methodological Authority

Canonical Definition

The HRIM-R — Harm Recovery Initiation Module governs how the transition
into Recovery from governed Harm is identified, qualified, initiated, and
represented without assuming that Mitigation must be complete, that all
Harm must have stopped, or that the affected subject must be capable of
returning to its pre-Harm condition.


HRIM-R determines when a materially meaningful Recovery process can be
considered to have begun, what condition or capability is entering
Recovery, from what post-Harm condition Recovery begins, toward what
recoverable condition Recovery is directed, what prerequisites and
dependencies materially affect initiation, and whether apparent
improvement constitutes actual Recovery initiation rather than Mitigation,
stabilization, adaptation, compensation, or temporary fluctuation.


It establishes the transition:

Governed Harm Mitigation State + Current Harm State → Recovery Readiness →
Recovery Reference Condition → Recovery Target Formation → Recovery
Initiation Determination → Governed Harm Recovery Initiation State


Its central question is:

When has a materially meaningful process of Recovery from governed Harm
actually begun, and what condition is entering Recovery?


  • Operational Role


The operational role of HRIM-R is:

to establish the legitimate beginning of Recovery as a distinct Harm
lifecycle process.


It prevents Recovery from being assumed merely because:

Mitigation occurred

Harm decreased

Containment succeeded

repair began

support was provided

function temporarily improved

or:

the affected subject adapted to the Harm

HRIM-R establishes:

Recovery has begun

only where there is sufficient basis that a materially relevant harmed
condition, function, capability, stability, integrity, or other
recoverable state has entered an actual Recovery process.


  • Position Within HRRHS


The HRRHS governance flow is:

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


HRIM-R governs the first stage:

Recovery Initiation

It may receive:

Governed Harm Mitigation State

Current Governed Harm State

Governed Harm Boundary

Governed Harm Containment State

and other materially relevant HAGA™ lifecycle information.

It produces:

Governed Harm Recovery Initiation State

for:

HRPM — Harm Recovery Progress Module

  • Governed Object


The primary governed object is:

Initiation of Recovery from Governed Harm

The object is not:

the Recovery action

the recovery program

the repair process

or:

the intention to recover

It is the transition in which an affected condition actually enters a
governable Recovery process.


Canonical distinction:

Recovery Activity Started ≠ Recovery Initiated by Default

  • Foundational Recovery Initiation Principle


The foundational rule is:

Recovery begins when a materially relevant harmed condition enters an
actual process of regaining a governed condition—not merely when
recovery-oriented activity begins.


Therefore:

Recovery Intervention Started ≠ Recovery Started

and:

Recovery Intent ≠ Recovery Initiation

Recovery initiation is consequence-centered.

  • Recovery Initiation Trigger


Recovery initiation may become governable when materially relevant
conditions indicate that the affected subject or object has begun moving
from its post-Harm condition toward a recoverable condition.


Potential triggers may include:

regaining function

regaining capability

restoring stability

re-establishing integrity

rebuilding operational capacity

restoring environmental function

regaining independence

or:

another materially relevant post-Harm improvement

The applicable trigger depends on the governed Harm.

  • Recovery Readiness


HRIM-R distinguishes:

Recovery Readiness

from:

Recovery Initiation

Recovery Readiness means that conditions necessary for Recovery are
sufficiently present for Recovery to begin.


These may include:

sufficient Harm stabilization

sufficient Mitigation

required resources

required access

physical or technical conditions

supporting infrastructure

environmental conditions

or:

other necessary dependencies

But:

Recovery Ready ≠ Recovery Initiated

Readiness enables Recovery.

It does not prove Recovery has begun.

  • Mitigation Completion Is Not Required


Recovery may begin while Mitigation continues.

Conceptually:

Mitigation → Recovery

may operate as:

Mitigation + Recovery

where the Harm lifecycle supports parallel processes.

Therefore:

Mitigation Completion ≠ Mandatory Recovery Start Condition

This is essential for Harm where reduction and Recovery naturally overlap.

  • Containment and Recovery Initiation


Containment may support Recovery by stopping additional Harm.

However, complete Containment is not universally required before Recovery
can begin.


A Harm may simultaneously involve:

Containment of one pathway

Mitigation of existing Harm

and:

Recovery of an already affected condition

Therefore:

Containment Complete ≠ Universal Recovery Prerequisite

Where continuing Harm materially prevents or reverses Recovery, that
condition must remain visible.


  • Harm State and Recovery Initiation


Recovery initiation must remain connected to current Harm State.

A Harm may be:

Active

Stabilized

Reduced

or another applicable state when Recovery begins.

Therefore:

Reduced Harm State ≠ Recovery Initiated by Default

and:

Active Harm State ≠ Recovery Impossible by Default

The relevant question is whether a recoverable condition has actually
entered Recovery.


  • Recovery Reference Condition


HRIM-R establishes the condition from which Recovery begins.

This may be:

Post-Harm Condition

Post-Containment Condition

Post-Mitigation Condition

or:

another materially appropriate current condition

This becomes the:

Recovery Reference Condition

against which subsequent Recovery Progress can be evaluated.

  • Pre-Harm Baseline


The pre-Harm condition may provide valuable context.

However, HRIM-R must not automatically treat it as the required Recovery
endpoint.


Therefore:

Pre-Harm Baseline ≠ Mandatory Recovery Target

The pre-Harm state answers:

What existed before Harm?

The Recovery Target answers:

What condition can legitimately be sought through Recovery now?

  • Recovery Target Formation


Recovery initiation requires sufficient understanding of what condition is
being regained.


The Recovery Target may concern:

function

capability

stability

integrity

independence

performance

operational capacity

environmental function

social function

or:

another materially relevant recoverable condition

The target should describe a condition.

Not merely an activity.

Therefore:

Recovery Program ≠ Recovery Target

  • Recovery Without Return


Recovery may begin even where restoration of the pre-Harm condition is
impossible.


Conceptually:

Pre-Harm State A → Harm → State B → Recovery toward State C

where:

C ≠ A

can still represent legitimate Recovery.

Canonical principle:

Recoverability does not require reversibility.

A permanently changed subject may still recover materially relevant
function or capability.


  • Irreversible Harm and Recovery Initiation


Irreversible Harm does not automatically eliminate Recovery.

Where one Harm dimension cannot be reversed, other affected dimensions may
still recover.


For example:

permanent structural change + recoverable function

or:

permanent loss + recoverable operational capability

Therefore:

Irreversible Harm ≠ No Recovery Potential

HRIM-R must identify what remains recoverable rather than treating
Recovery as all-or-nothing.


  • Recovery Initiation vs Stabilization


A Harm condition may stabilize without beginning to recover.

Conceptually:

Worsening → Stabilized

does not necessarily mean:

Stabilized → Recovering

Therefore:

Harm Stabilization ≠ Recovery Initiation

Stabilization may create Recovery Readiness without establishing Recovery
itself.


  • Recovery Initiation vs Mitigation Effect


Mitigation may reduce the magnitude of Harm.

That reduction may support Recovery.

But:

Mitigation Effect ≠ Recovery Initiation

The distinction is:

Mitigation Effect → Harm decreased

Recovery Initiation → harmed condition began regaining a relevant state

Both may occur simultaneously without becoming the same governance object.

  • Recovery Initiation vs Repair


Repair may be a mechanism supporting Recovery.

But repair activity does not prove that the affected condition has begun
recovering.


Therefore:

Repair Started ≠ Recovery Initiated

and:

Repair Completed ≠ Recovery Achieved

The architecture follows the Harm consequence rather than the repair
process.


  • Recovery Initiation vs Adaptation


An affected subject may adapt to continuing Harm.

Examples include:

behavioral compensation

technical workaround

operational rerouting

substitute capability

or:

changed operating conditions

Adaptation may improve function while Harm remains unchanged.

Therefore:

Adaptation ≠ Recovery by Default

HRIM-R must determine whether the underlying harmed condition is
recovering or whether function is merely being maintained around it.


  • Recovery Initiation vs Compensation


Financial, operational, legal, or other compensation may reduce
consequences associated with Harm.


It does not automatically initiate Recovery of the harmed condition.

Therefore:

Compensation Provided ≠ Recovery Initiated

The two may coexist while remaining methodologically separate.

  • Recovery Initiation vs Temporary Improvement


A temporary fluctuation may resemble early Recovery.

HRIM-R must distinguish materially meaningful Recovery initiation from:

short-lived improvement

measurement variation

temporary suppression of consequences

or:

unstable post-intervention change

Therefore:

Temporary Improvement ≠ Recovery Initiation by Default

Where the distinction cannot yet be established, Recovery initiation may
remain uncertain.


  • Recovery Initiation Threshold


The threshold for Recovery initiation must be appropriate to the governed
Harm.


Recovery should not require complete improvement.

But it should require more than an unsupported expectation of improvement.

Conceptually:

Potential Recovery → Recovery Signal → Recovery Initiation

The precise threshold may differ by domain while preserving the same
methodological logic.


  • Recovery Initiation Under Uncertainty


Recovery initiation may remain uncertain where:

observations are limited

the Harm condition fluctuates

latency exists

the relevant function cannot yet be evaluated

Mitigation effects overlap with Recovery

or:

the recoverable condition is not yet sufficiently understood

HRIM-R must preserve uncertainty rather than forcing a binary
determination.


Therefore:

Recovery Uncertain ≠ Recovery Absent

and:

Recovery Uncertain ≠ Recovery Established

  • Multiple Recovery Targets


One Harm may affect multiple recoverable dimensions.

For example:

physical function

operational capability

independence

and:

stability

may each enter Recovery differently.

HRIM-R must permit:

Target₁ → Recovery Initiated

while:

Target₂ → Recovery Not Initiated

Therefore:

Recovery in One Dimension ≠ Recovery Across All Harm Dimensions

  • Composite Recovery Initiation


Where Harm is composite, Recovery may begin in one component before
another.


For example:

Component A → Recovering

Component B → Stable

Component C → Still Worsening

The complete Recovery condition must preserve those differences.

Therefore:

Component Recovery Initiation ≠ Composite Recovery Initiation by Default

  • Collective Recovery Initiation


Where Harm affects a collective, Recovery initiation must correspond to
the governed collective object.


Recovery among selected individuals cannot automatically establish
collective Recovery.


Therefore:

Individual Recovery Initiation ≠ Collective Recovery Initiation

The architecture must preserve materially different subgroup conditions.

  • Distributed Recovery Initiation


Recovery may begin at different times across:

systems

organizations

locations

infrastructure

communities

or:

operational environments

Local Recovery initiation must not automatically represent the distributed
condition.


Canonical principle:

Recovery begins where the affected condition actually begins to recover.

  • Cross-Domain Recovery Initiation


A Harm spanning several domains may enter Recovery asynchronously.

For example:

Physical → Recovering

Operational → Recovered enough to function

Financial → Unrecovered

Organizational → Recovery Not Initiated

HRIM-R must preserve each materially relevant domain condition.

Therefore:

Recovery Initiation in One Domain ≠ Complete Recovery Initiation

  • Recovery Dependencies


Recovery may depend on conditions outside the harmed object itself.

These may include:

continued Containment

continued Mitigation

resource availability

support systems

environmental stability

infrastructure

external services

or:

other operational dependencies

Where a dependency is material, it should remain visible in the Recovery
Initiation State.


  • Recovery Constraint Conditions


Some conditions may limit how Recovery can proceed.

These may include:

irreversible change

resource limitations

safety constraints

technical limitations

environmental constraints

dependency constraints

or:

remaining active Harm

These do not automatically prevent Recovery.

They define the governed Recovery space within which legitimate Recovery
can occur.


  • Recovery Initiation and New Harm


A recovery-oriented intervention may create new Harm.

HRIM-R must not treat recovery activity as methodologically beneficial
merely because its purpose is Recovery.


Therefore:

Recovery-Oriented Action ≠ Harm-Free Action

New Harm enters the appropriate HAGA™ lifecycle independently.

  • Recovery Initiation and Continuing Harm


Recovery may coexist with continuing Harm.

Conceptually:

Recovery Progress + Continuing Harm Production

may occur simultaneously.

HRIM-R must preserve both.

Therefore:

Recovery Initiated ≠ Harm Production Ended

HCOS and other HAGA™ lifecycle spaces remain active where applicable.

  • Recovery Initiation State


HRIM-R may represent Recovery Initiation through states such as:

Recovery Not Ready

Recovery Ready

Recovery Signal Present

Recovery Initiation Pending

Recovery Initiated

Recovery Initiation Partially Established

or:

Recovery Initiation Uncertain

These states must describe Recovery initiation only.

They must not be used as Recovery Progress or final Recovery conclusions.

  • Initiation Reassessment


Recovery Initiation must be reassessed where:

Harm worsens

Containment fails

Mitigation changes

the Recovery Target changes

dependencies fail

new Harm emerges

the apparent improvement reverses

or:

new information changes the Recovery basis

An initiation determination must remain connected to current Harm reality.

  • Recovery Initiation Record


The governed initiation record should preserve materially relevant:

Harm object

Recovery Reference Condition

Recovery Target

recoverable dimension

Recovery Readiness

initiation basis

initiation timing

scope

dependencies

constraints

uncertainty

and:

reassessment triggers

This supports continuity into Recovery Progress governance.

  • Handoff to Recovery Progress


The principal HRIM-R output is:

Governed Harm Recovery Initiation State

Once Recovery is sufficiently initiated, the lifecycle transfers to:

HRPM — Harm Recovery Progress Module

The handoff asks:

Recovery has begun. How is it progressing?

Therefore:

Recovery Initiation ≠ Recovery Progress

and:

Recovery Initiation ≠ Recovery Achievement

  • Minimum Implementation Framework


A minimum HRIM-R implementation requires eight capabilities.

  • Recovery Readiness Identification


Determine whether materially relevant conditions exist for Recovery to
begin without assuming readiness equals Recovery.


  • Recovery Reference Condition Establishment


Establish the governed post-Harm condition from which Recovery Progress
will be evaluated.


  • Recoverable Condition Identification


Identify the function, capability, stability, integrity, independence,
performance, or other materially relevant condition capable of Recovery.


  • Recovery Target Formation


Define the condition toward which Recovery is directed without
automatically requiring restoration of the pre-Harm state.


  • Recovery Initiation Determination


Distinguish actual Recovery initiation from Mitigation, stabilization,
repair, adaptation, compensation, temporary improvement, or
recovery-oriented activity.


  • Composite, Collective & Distributed Initiation Governance


Preserve Recovery initiation across multiple Harm components, affected
subjects, groups, domains, systems, organizations, and locations.


  • Dependency, Uncertainty & Reassessment Governance


Preserve materially relevant Recovery dependencies, constraints,
uncertainty, continuing Harm, and triggers requiring initiation
reassessment.


  • Governed Output


Produce a traceable Governed Harm Recovery Initiation State suitable for
Recovery Progress governance. 38. Use Case 1 — Recovery Begins Before
Mitigation Ends


A governed Harm remains under active Mitigation.

The Harm has not been completely reduced, but the affected system has
begun materially regaining operational capability.


HRIM-R does not wait for:

Mitigation Complete

before recognizing:

Recovery Initiated

It preserves both lifecycle realities:

Mitigation Continuing + Recovery Initiated

The governing principle is:

Recovery may begin before Harm reduction is complete when the affected
condition has genuinely begun to recover.


  • Use Case 2 — Permanent Change With Recoverable Function


A Harm permanently changes an affected physical or operational structure.

Returning to the exact pre-Harm condition is impossible.

However, the affected subject begins regaining materially relevant
function through a different stable condition.


HRIM-R recognizes Recovery initiation without requiring impossible
restoration.


The Recovery Target is based on the recoverable condition rather than
historical replication.


The governing principle is:

Recoverability does not require reversibility.

  • Governance Requirements


HRIM-R requires that:

  • Recovery initiation remain distinct from recovery-oriented
    activity
  • Recovery Readiness remain distinct from Recovery Initiation
  • Mitigation completion not automatically be required before
    Recovery


begins; - Containment completion not become a universal Recovery
prerequisite; - current Harm State remain visible; - a sufficient Recovery
Reference Condition be established; - the pre-Harm baseline not
automatically become the mandatory Recovery Target; - Recovery Target
describe the condition being regained rather than an activity; -
irreversible Harm not automatically eliminate Recovery potential; -
stabilization remain distinct from Recovery initiation; - Mitigation
Effect remain distinct from Recovery initiation; - repair remain distinct
from Recovery; - adaptation remain distinct from Recovery; - compensation
remain distinct from Recovery; - temporary improvement not automatically
establish Recovery initiation; - domain-appropriate Recovery initiation
thresholds remain possible; - uncertainty remain explicit; - multiple
Recovery Targets remain separately governable where necessary; - component
Recovery not automatically establish composite Recovery; - individual
Recovery not automatically establish collective Recovery; - local Recovery
not automatically establish distributed Recovery; - cross-domain Recovery
differences remain visible; - material dependencies and constraints remain
explicit; - Recovery-oriented actions not hide new Harm; - continuing Harm
remain visible during Recovery; - Recovery Initiation remain reassessable;
- the handoff to Recovery Progress remain explicit.


  • Governance Logic


HRIM-R applies the following logic:

Does governed Harm exist in a condition from which Recovery is materially
possible?


If no:

→ establish Recovery Not Ready or another appropriate state.

If yes:

→ identify the current Recovery Reference Condition.

Then ask:

What condition is recoverable?

→ identify the relevant function, capability, stability, integrity,
independence, or other recoverable dimension.


Then:

What condition should Recovery move toward?

→ establish the Recovery Target.

Next determine:

Are necessary Recovery conditions sufficiently present?

If no:

→ Recovery Readiness remains incomplete.

If yes:

→ establish Recovery Readiness.

Then ask:

Has the affected condition actually begun moving toward the Recovery
Target?


If no:

→ readiness or recovery-oriented activity must not be represented as
Recovery Initiation.


If yes:

→ determine whether the observed change is:

Recovery

rather than:

Mitigation Effect

stabilization

repair activity

adaptation

compensation

or:

temporary fluctuation

Then determine:

What scope has entered Recovery?

Which components?

Which subjects?

Which domains?

Which locations?

What dependencies remain?

What uncertainty remains?

Finally establish:

Governed Harm Recovery Initiation State → Recovery Progress Governance

Throughout:

Readiness ≠ Initiation

Activity ≠ Recovery

Mitigation ≠ Recovery

Stabilization ≠ Recovery

Repair ≠ Recovery

Adaptation ≠ Recovery

Compensation ≠ Recovery

Recoverability ≠ Reversibility

Initiation ≠ Progress

Initiation ≠ Recovery Achievement

  • Governance Outputs


HRIM-R may produce:

Governed Harm Recovery Initiation State

Recovery Readiness State

Recovery Reference Condition

Recovery Target

Recoverable Condition

Recovery Initiation Basis

Recovery Initiation Timing

Recovery Initiation Scope

Component Recovery Initiation State

Collective Recovery Initiation State

Distributed Recovery Initiation State

Cross-Domain Recovery Initiation State

Recovery Dependency Set

Recovery Constraint Set

Recovery Initiation Uncertainty

Recovery Initiation Reassessment Trigger

and:

Recovery Progress Readiness State

The principal output is:

Governed Harm Recovery Initiation State

  • Critical Distinctions


Recovery Activity Started ≠ Recovery Initiated

Recovery Intent ≠ Recovery Initiation

Recovery Ready ≠ Recovery Initiated

Mitigation Completion ≠ Mandatory Recovery Start

Containment Complete ≠ Universal Recovery Prerequisite

Reduced Harm State ≠ Recovery Initiated

Pre-Harm Baseline ≠ Mandatory Recovery Target

Recovery Program ≠ Recovery Target

Recoverability ≠ Reversibility

Irreversible Harm ≠ No Recovery Potential

Harm Stabilization ≠ Recovery Initiation

Mitigation Effect ≠ Recovery Initiation

Repair Started ≠ Recovery Initiated

Repair Completed ≠ Recovery Achieved

Adaptation ≠ Recovery

Compensation Provided ≠ Recovery Initiated

Temporary Improvement ≠ Recovery Initiation

Recovery in One Dimension ≠ Recovery Across All Dimensions

Component Recovery Initiation ≠ Composite Recovery Initiation

Individual Recovery Initiation ≠ Collective Recovery Initiation

Recovery Initiation in One Domain ≠ Complete Recovery Initiation

Recovery-Oriented Action ≠ Harm-Free Action

Recovery Initiated ≠ Harm Production Ended

Recovery Initiation ≠ Recovery Progress

Recovery Initiation ≠ Recovery Achievement

  • Canonical Boundary


The HRIM-R — Harm Recovery Initiation Module governs how Recovery from
governed Harm becomes materially ready, begins, and is represented as a
distinct Harm lifecycle transition. It governs Recovery Readiness,
Recovery Reference Condition, recoverable condition identification,
Recovery Target formation, initiation basis, initiation timing, scope,
dependencies, constraints, composite, collective, distributed and
cross-domain Recovery initiation, uncertainty, continuing Harm
interaction, and initiation reassessment. HRIM-R does not determine
whether Harm originally exists, perform Harm Recognition or Determination,
independently establish the Harm Boundary, govern Harm Change &
Propagation, perform Containment, determine or verify Mitigation, govern
subsequent Recovery Progress or final Recovery Evaluation, 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 does not begin because an intervention has started, a repair is
underway, Harm has stabilized, or someone intends to restore what was
lost.


It begins when the affected condition itself enters a imaterially
meaningful process of regaining function, capability, stability,
integrity, or another governed condition.


That process may begin before Mitigation ends, may proceed without return
to the pre-Harm state, and may coexist with Harm that continues to remain.


Recovery begins when the harmed condition begins to recover—not when
recovery activity begins.